Models
baseinfo
¶
AvailableApiVersion (BaseModel)
pydantic-model
¶
A JSON object containing information about an available API version
url: AnyHttpUrl
pydantic-field
required
¶
a string specifying a versioned base URL that MUST adhere to the rules in section Base URL
version: ConstrainedStrValue
pydantic-field
required
¶
a string containing the full version number of the API served at that versioned base URL. The version number string MUST NOT be prefixed by, e.g., 'v'.
crosscheck_url_and_version(values)
classmethod
¶
Check that URL version and API version are compatible.
Source code in optimade/models/baseinfo.py
@root_validator(pre=False, skip_on_failure=True)
def crosscheck_url_and_version(cls, values):
""" Check that URL version and API version are compatible. """
url_version = (
values["url"]
.split("/")[-2 if values["url"].endswith("/") else -1]
.replace("v", "")
)
url_version = tuple(int(val) for val in url_version.split("."))
api_version = tuple(int(val) for val in values["version"].split("."))
if any(a != b for a, b in zip(url_version, api_version)):
raise ValueError(
f"API version {api_version} is not compatible with url version {url_version}."
)
return values
url_must_be_versioned_base_url(v)
classmethod
¶
The URL must be a valid versioned Base URL
Source code in optimade/models/baseinfo.py
@validator("url")
def url_must_be_versioned_base_url(cls, v):
"""The URL must be a valid versioned Base URL"""
if not re.match(r".+/v[0-1](\.[0-9]+)*/?$", v):
raise ValueError(f"url MUST be a versioned base URL. It is: {v}")
return v
BaseInfoAttributes (BaseModel)
pydantic-model
¶
Attributes for Base URL Info endpoint
api_version: str
pydantic-field
required
¶
Presently used version of the OPTIMADE API
available_api_versions: List[optimade.models.baseinfo.AvailableApiVersion]
pydantic-field
required
¶
A list of dictionaries of available API versions at other base URLs
available_endpoints: List[str]
pydantic-field
required
¶
List of available endpoints (i.e., the string to be appended to the versioned base URL).
entry_types_by_format: Dict[str, List[str]]
pydantic-field
required
¶
Available entry endpoints as a function of output formats.
formats: List[str]
pydantic-field
¶
List of available output formats.
is_index: bool
pydantic-field
¶
If true, this is an index meta-database base URL (see section Index Meta-Database). If this member is not provided, the client MUST assume this is not an index meta-database base URL (i.e., the default is for is_index to be false).
entries
¶
EntryInfoProperty (BaseModel)
pydantic-model
¶
description: str
pydantic-field
required
¶
description of the entry property
sortable: bool
pydantic-field
¶
defines whether the entry property can be used for sorting with the "sort" parameter. If the entry listing endpoint supports sorting, this key MUST be present for sortable properties with value true
.
unit: str
pydantic-field
¶
the physical unit of the entry property
EntryInfoResource (BaseModel)
pydantic-model
¶
description: str
pydantic-field
required
¶
description of the entry
formats: List[str]
pydantic-field
required
¶
list of available output formats.
output_fields_by_format: Dict[str, List[str]]
pydantic-field
required
¶
a dictionary of available output fields for this entry type, where the keys are the values of the formats
list and the values are the keys of the properties
dictionary.
properties: Dict[str, optimade.models.entries.EntryInfoProperty]
pydantic-field
required
¶
a dictionary describing queryable properties for this entry type, where each key is a property ID.
EntryRelationships (Relationships)
pydantic-model
¶
This model wraps the JSON API Relationships to include type-specific top level keys.
EntryResourceAttributes (Attributes)
pydantic-model
¶
Contains key-value pairs representing the entry's properties.
immutable_id: str
pydantic-field
¶
The entry's immutable ID (e.g., an UUID). This is important for databases having preferred IDs that point to "the latest version" of a record, but still offer access to older variants. This ID maps to the version-specific record, in case it changes in the future. - Type: string. - Requirements/Conventions:
- Support: OPTIONAL, i.e., MAY be :val:
null
. -
Query: MUST be a queryable property with support for all mandatory filter features.
-
Examples:
-
:val:
"8bd3e750-b477-41a0-9b11-3a799f21b44f"
- :val:
"fjeiwoj,54;@=%<>#32"
(Strings that are not URL-safe are allowed.)
last_modified: datetime
pydantic-field
required
¶
Date and time representing when the entry was last modified. - Type: timestamp. - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: MUST be a queryable property with support for all mandatory filter features.
-
Response: REQUIRED in the response unless the query parameter :query-param:
response_fields
is present and does not include this property. -
Example:
-
As part of JSON response format: :VAL:
"2007-04-05T14:30Z"
(i.e., encoded as anRFC 3339 Internet Date/Time Format <https://tools.ietf.org/html/rfc3339#section-5.6>
__ string.)
index_metadb
¶
IndexInfoAttributes (BaseInfoAttributes)
pydantic-model
¶
Attributes for Base URL Info endpoint for an Index Meta-Database
IndexInfoResource (BaseInfoResource)
pydantic-model
¶
Index Meta-Database Base URL Info endpoint resource
IndexRelationship (BaseModel)
pydantic-model
¶
Index Meta-Database relationship
data: RelatedLinksResource
pydantic-field
required
¶
JSON API resource linkage. It MUST be either null or contain a single Links identifier object with the fields 'id' and 'type'
RelatedLinksResource (BaseResource)
pydantic-model
¶
A related Links resource object
jsonapi
¶
This module should reproduce JSON API v1.0 https://jsonapi.org/format/1.0/
Attributes (BaseModel)
pydantic-model
¶
Members of the attributes object ("attributes") represent information about the resource object in which it's defined. The keys for Attributes MUST NOT be: relationships links id type
BaseResource (BaseModel)
pydantic-model
¶
Error (BaseModel)
pydantic-model
¶
An error response
code: str
pydantic-field
¶
an application-specific error code, expressed as a string value.
detail: str
pydantic-field
¶
A human-readable explanation specific to this occurrence of the problem.
id: str
pydantic-field
¶
A unique identifier for this particular occurrence of the problem.
links: ErrorLinks
pydantic-field
¶
A links object storing about
meta: Meta
pydantic-field
¶
a meta object containing non-standard meta-information about the error.
source: ErrorSource
pydantic-field
¶
An object containing references to the source of the error
status: str
pydantic-field
¶
the HTTP status code applicable to this problem, expressed as a string value.
title: str
pydantic-field
¶
A short, human-readable summary of the problem. It SHOULD NOT change from occurrence to occurrence of the problem, except for purposes of localization.
__hash__(self)
special
¶
Return hash(self).
Source code in optimade/models/jsonapi.py
def __hash__(self):
return hash(self.json())
ErrorLinks (BaseModel)
pydantic-model
¶
A Links object specific to Error objects
about: Union[pydantic.networks.AnyUrl, optimade.models.jsonapi.Link]
pydantic-field
¶
A link that leads to further details about this particular occurrence of the problem.
ErrorSource (BaseModel)
pydantic-model
¶
an object containing references to the source of the error
JsonApi (BaseModel)
pydantic-model
¶
Link (BaseModel)
pydantic-model
¶
Meta (BaseModel)
pydantic-model
¶
Non-standard meta-information that can not be represented as an attribute or relationship.
Relationship (BaseModel)
pydantic-model
¶
Representation references from the resource object in which it’s defined to other resource objects.
data: Union[optimade.models.jsonapi.BaseResource, List[optimade.models.jsonapi.BaseResource]]
pydantic-field
¶
Resource linkage
links: RelationshipLinks
pydantic-field
¶
a links object containing at least one of the following: self, related
meta: Meta
pydantic-field
¶
a meta object that contains non-standard meta-information about the relationship.
RelationshipLinks (BaseModel)
pydantic-model
¶
A resource object MAY contain references to other resource objects ("relationships"). Relationships may be to-one or to-many. Relationships can be specified by including a member in a resource's links object.
Relationships (BaseModel)
pydantic-model
¶
Members of the relationships object ("relationships") represent references from the resource object in which it's defined to other resource objects. Keys MUST NOT be: type id
Resource (BaseResource)
pydantic-model
¶
Resource objects appear in a JSON:API document to represent resources.
attributes: Attributes
pydantic-field
¶
an attributes object representing some of the resource’s data.
links: ResourceLinks
pydantic-field
¶
a links object containing links related to the resource.
meta: Meta
pydantic-field
¶
a meta object containing non-standard meta-information about a resource that can not be represented as an attribute or relationship.
relationships: Relationships
pydantic-field
¶
a relationships object describing relationships between the resource and other JSON:API resources.
ResourceLinks (BaseModel)
pydantic-model
¶
A Resource Links object
self: Union[pydantic.networks.AnyUrl, optimade.models.jsonapi.Link]
pydantic-field
¶
A link that identifies the resource represented by the resource object.
Response (BaseModel)
pydantic-model
¶
A top-level response
data: Union[NoneType, optimade.models.jsonapi.Resource, List[optimade.models.jsonapi.Resource]]
pydantic-field
¶
Outputted Data
errors: List[optimade.models.jsonapi.Error]
pydantic-field
¶
A list of unique errors
included: List[optimade.models.jsonapi.Resource]
pydantic-field
¶
A list of unique included resources
jsonapi: JsonApi
pydantic-field
¶
Information about the JSON API used
links: ToplevelLinks
pydantic-field
¶
Links associated with the primary data or errors
meta: Meta
pydantic-field
¶
A meta object containing non-standard information related to the Success
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
ToplevelLinks (BaseModel)
pydantic-model
¶
A set of Links objects, possibly including pagination
first: AnyUrl
pydantic-field
¶
The first page of data
last: AnyUrl
pydantic-field
¶
The last page of data
next: AnyUrl
pydantic-field
¶
The next page of data
prev: AnyUrl
pydantic-field
¶
The previous page of data
related: Union[pydantic.networks.AnyUrl, optimade.models.jsonapi.Link]
pydantic-field
¶
A related resource link
self: Union[pydantic.networks.AnyUrl, optimade.models.jsonapi.Link]
pydantic-field
¶
A link to itself
links
¶
LinksResource (EntryResource)
pydantic-model
¶
A Links endpoint resource object
LinksResourceAttributes (Attributes)
pydantic-model
¶
Links endpoint resource object attributes
base_url: Union[pydantic.networks.AnyUrl, optimade.models.jsonapi.Link]
pydantic-field
required
¶
JSON API links object, pointing to the base URL for this implementation
description: str
pydantic-field
required
¶
Human-readable description for the OPTIMADE API implementation a client may provide in a list to an end-user.
homepage: Union[pydantic.networks.AnyUrl, optimade.models.jsonapi.Link]
pydantic-field
required
¶
JSON API links object, pointing to a homepage URL for this implementation
link_type: str
pydantic-field
required
¶
The link type of the represented resource in relation to this implementation. MUST be one of these values: 'child', 'root', 'external', 'providers'.
name: str
pydantic-field
required
¶
Human-readable name for the OPTIMADE API implementation a client may provide in a list to an end-user.
optimade_json
¶
Modified JSON API v1.0 for OPTIMADE API
BaseRelationshipMeta (Meta)
pydantic-model
¶
Specific meta field for base relationship resource
description: str
pydantic-field
required
¶
OPTIONAL human-readable description of the relationship
BaseRelationshipResource (BaseResource)
pydantic-model
¶
Minimum requirements to represent a relationship resource
meta: BaseRelationshipMeta
pydantic-field
¶
Relationship meta field. MUST contain 'description' if supplied.
Implementation (BaseModel)
pydantic-model
¶
Information on the server implementation
maintainer: ImplementationMaintainer
pydantic-field
¶
A dictionary providing details about the maintainer of the implementation.
name: str
pydantic-field
¶
name of the implementation
source_url: AnyUrl
pydantic-field
¶
URL of the implementation source, either downloadable archive or version control system
version: str
pydantic-field
¶
version string of the current implementation
ImplementationMaintainer (BaseModel)
pydantic-model
¶
Details about the maintainer of the implementation
email: EmailStr
pydantic-field
required
¶
the maintainer's email address
Provider (BaseModel)
pydantic-model
¶
Information on the database provider of the implementation.
description: str
pydantic-field
required
¶
a longer description of the database provider
homepage: Union[pydantic.networks.AnyHttpUrl, optimade.models.jsonapi.Link]
pydantic-field
¶
a JSON API links object pointing to homepage of the database provider, either directly as a string, or as a link object.
index_base_url: Union[pydantic.networks.AnyHttpUrl, optimade.models.jsonapi.Link]
pydantic-field
¶
a JSON API links object pointing to the base URL for the index
meta-database as specified in Appendix 1, either directly as a string, or as a link object.
name: str
pydantic-field
required
¶
a short name for the database provider
prefix: str
pydantic-field
required
¶
database-provider-specific prefix as found in Appendix 1.
Relationship (Relationship)
pydantic-model
¶
Similar to normal JSON API relationship, but with addition of OPTIONAL meta field for a resource
ResponseMeta (Meta)
pydantic-model
¶
A JSON API meta member that contains JSON API meta objects of non-standard meta-information.
OPTIONAL additional information global to the query that is not specified in this document, MUST start with a database-provider-specific prefix.
api_version: str
pydantic-field
required
¶
a string containing the version of the API implementation, e.g. v0.9.5
data_available: int
pydantic-field
¶
an integer containing the total number of data objects available in the database
data_returned: ConstrainedIntValue
pydantic-field
required
¶
an integer containing the number of data objects returned for the query.
implementation: Implementation
pydantic-field
¶
a dictionary describing the server implementation
last_id: str
pydantic-field
¶
a string containing the last ID returned
more_data_available: bool
pydantic-field
required
¶
false
if all data has been returned, and true
if not.
provider: Provider
pydantic-field
required
¶
information on the database provider of the implementation.
query: ResponseMetaQuery
pydantic-field
required
¶
information on the query that was requested
response_message: str
pydantic-field
¶
response string from the server
time_stamp: datetime
pydantic-field
required
¶
a string containing the date and time at which the query was exexcuted
warnings: List[optimade.models.optimade_json.Warnings]
pydantic-field
¶
List of warning resource objects representing non-critical errors or warnings. A warning resource object is defined similarly to a JSON API error object, but MUST also include the field type, which MUST have the value "warning". The field detail MUST be present and SHOULD contain a non-critical message, e.g., reporting unrecognized search attributes or deprecated features. The field status, representing a HTTP response status code, MUST NOT be present for a warning resource object. This is an exclusive field for error resource objects.
ResponseMetaQuery (BaseModel)
pydantic-model
¶
Information on the query that was requested.
representation: str
pydantic-field
required
¶
a string with the part of the URL that follows the base URL. Example: '/structures?'
Success (Response)
pydantic-model
¶
errors are not allowed
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
either_data_meta_or_errors_must_be_set(values)
classmethod
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set
Source code in optimade/models/optimade_json.py
@root_validator(pre=True)
def either_data_meta_or_errors_must_be_set(cls, values):
"""Overwriting the existing validation function, since 'errors' MUST NOT be set"""
required_fields = ("data", "meta")
if not any(values.get(field) for field in required_fields):
raise ValueError(
f"At least one of {required_fields} MUST be specified in the top-level response"
)
# errors MUST be skipped
if values.get("errors", None) is not None:
raise ValueError("'errors' MUST be skipped for a successful response")
return values
Warnings (OptimadeError)
pydantic-model
¶
OPTIMADE-specific warning class based on OPTIMADE-specific JSON API Error. From the specification:
A warning resource object is defined similarly to a JSON API
error object, but MUST also include the field type, which MUST
have the value "warning". The field detail MUST be present and
SHOULD contain a non-critical message, e.g., reporting
unrecognized search attributes or deprecated features.
Note: Must be named "Warnings", since "Warning" is a built-in Python class.
type: str
pydantic-field
¶
Warnings must be of type "warning"
references
¶
Person (BaseModel)
pydantic-model
¶
ReferenceResource (EntryResource)
pydantic-model
¶
The :entry:references
entries describe bibliographic references.
The following properties are used to provide the bibliographic details:
-
address, annote, booktitle, chapter, crossref, edition, howpublished, institution, journal, key, month, note, number, organization, pages, publisher, school, series, title, type, volume, year: Meanings of these properties match the
BibTeX specification <http://bibtexml.sourceforge.net/btxdoc.pdf>
__, values are strings; -
authors and editors: lists of person objects which are dictionaries with the following keys:
-
name: Full name of the person, REQUIRED.
-
firstname, lastname: Parts of the person's name, OPTIONAL.
-
doi and url: values are strings.
-
Requirements/Conventions:
-
Support: OPTIONAL, i.e., any of the properties MAY be :val:
null
. - Query: Support for queries on any of these properties is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
- Every references entry MUST contain at least one of the properties.
ReferenceResourceAttributes (EntryResourceAttributes)
pydantic-model
¶
Model that stores the attributes of a reference. Many properties match the meaning described in the BibTeX specification.
address: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
annote: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
authors: List[optimade.models.references.Person]
pydantic-field
¶
List of person objects containing the authors of the reference.
bib_type: str
pydantic-field
¶
Type of the reference, corresponding to the type property in the BiBTeX specification.
booktitle: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
chapter: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
crossref: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
doi: str
pydantic-field
¶
The digital object identifier of the reference.
edition: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
editors: List[optimade.models.references.Person]
pydantic-field
¶
List of person objects containing the editors of the reference.
howpublished: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
institution: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
journal: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
key: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
month: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
note: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
number: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
organization: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
pages: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
publisher: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
school: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
series: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
title: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
url: AnyUrl
pydantic-field
¶
The URL of the reference.
volume: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
year: str
pydantic-field
¶
Meaning of property matches the BiBTeX specification.
responses
¶
EntryInfoResponse (Success)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
EntryResponseMany (Success)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
EntryResponseOne (Success)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
ErrorResponse (Response)
pydantic-model
¶
errors MUST be present and data MUST be skipped
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
IndexInfoResponse (Success)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
InfoResponse (Success)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
LinksResponse (EntryResponseMany)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
ReferenceResponseMany (EntryResponseMany)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
ReferenceResponseOne (EntryResponseOne)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
StructureResponseMany (EntryResponseMany)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
StructureResponseOne (EntryResponseOne)
pydantic-model
¶
__json_encoder__(obj)
special
staticmethod
¶
partial(func, args, *keywords) - new function with partial application of the given arguments and keywords.
structures
¶
Assembly (BaseModel)
pydantic-model
¶
A description of groups of sites that are statistically correlated.
-
Examples (for each entry of the assemblies list):
- :val:
{"sites_in_groups": [[0], [1]], "group_probabilities: [0.3, 0.7]}
: the first site and the second site never occur at the same time in the unit cell. Statistically, 30 % of the times the first site is present, while 70 % of the times the second site is present. - :val:
{"sites_in_groups": [[1,2], [3]], "group_probabilities: [0.3, 0.7]}
: the second and third site are either present together or not present; they form the first group of atoms for this assembly. The second group is formed by the fourth site. Sites of the first group (the second and the third) are never present at the same time as the fourth site. 30 % of times sites 1 and 2 are present (and site 3 is absent); 70 % of times site 3 is present (and sites 1 and 2 are absent).
- :val:
group_probabilities: List[float]
pydantic-field
required
¶
Statistical probability of each group. It MUST have the same length as :property:sites_in_groups
.
It SHOULD sum to one.
See below for examples of how to specify the probability of the occurrence of a vacancy.
The possible reasons for the values not to sum to one are the same as already specified above for the :property:concentration
of each :property:species
, see property species
_.
sites_in_groups: List[List[int]]
pydantic-field
required
¶
Index of the sites (0-based) that belong to each group for each assembly.
Example: :val:[[1], [2]]
: two groups, one with the second site, one with the third.
Example: :val:[[1,2], [3]]
: one group with the second and third site, one with the fourth.
Periodicity (IntEnum)
¶
An enumeration.
Species (BaseModel)
pydantic-model
¶
A list describing the species of the sites of this structure. Species can be pure chemical elements, or virtual-crystal atoms representing a statistical occupation of a given site by multiple chemical elements.
-
Examples:
- :val:
[ {"name": "Ti", "chemical_symbols": ["Ti"], "concentration": [1.0]} ]
: any site with this species is occupied by a Ti atom. - :val:
[ {"name": "Ti", "chemical_symbols": ["Ti", "vacancy"], "concentration": [0.9, 0.1]} ]
: any site with this species is occupied by a Ti atom with 90 % probability, and has a vacancy with 10 % probability. - :val:
[ {"name": "BaCa", "chemical_symbols": ["vacancy", "Ba", "Ca"], "concentration": [0.05, 0.45, 0.5], "mass": 88.5} ]
: any site with this species is occupied by a Ba atom with 45 % probability, a Ca atom with 50 % probability, and by a vacancy with 5 % probability. The mass of this site is (on average) 88.5 a.m.u. - :val:
[ {"name": "C12", "chemical_symbols": ["C"], "concentration": [1.0], "mass": 12.0} ]
: any site with this species is occupied by a carbon isotope with mass 12. - :val:
[ {"name": "C13", "chemical_symbols": ["C"], "concentration": [1.0], "mass": 13.0} ]
: any site with this species is occupied by a carbon isotope with mass 13.
- :val:
chemical_symbols: List[str]
pydantic-field
required
¶
MUST be a list of strings of all chemical elements composing this species.
-
It MUST be one of the following:
-
a valid chemical-element name, or
- the special value :val:
"X"
to represent a non-chemical element, or -
the special value :val:
"vacancy"
to represent that this site has a non-zero probability of having a vacancy (the respective probability is indicated in the :property:concentration
list, see below). -
If any one entry in the :property:
species
list has a :property:chemical_symbols
list that is longer than 1 element, the correct flag MUST be set in the list :property:structure_features
(see propertystructure_features
_).
concentration: List[float]
pydantic-field
required
¶
MUST be a list of floats, with same length as :property:chemical_symbols
. The numbers represent the relative concentration of the corresponding chemical symbol in this species.
The numbers SHOULD sum to one. Cases in which the numbers do not sum to one typically fall only in the following two categories:
- Numerical errors when representing float numbers in fixed precision, e.g. for two chemical symbols with concentrations :val:
1/3
and :val:2/3
, the concentration might look something like :val:[0.33333333333, 0.66666666666]
. If the client is aware that the sum is not one because of numerical precision, it can renormalize the values so that the sum is exactly one. - Experimental errors in the data present in the database. In this case, it is the responsibility of the client to decide how to process the data.
Note that concentrations are uncorrelated between different site (even of the same species).
mass: float
pydantic-field
¶
If present MUST be a float expressed in a.m.u.
original_name: str
pydantic-field
¶
Can be any valid Unicode string, and SHOULD contain (if specified) the name of the species that is used internally in the source database.
Note: With regards to "source database", we refer to the immediate source being queried via the OPTIMADE API implementation.
The main use of this field is for source databases that use species names, containing characters that are not allowed (see description of the list property species_at_sites
_).
StructureResource (EntryResource)
pydantic-model
¶
Representing a structure.
StructureResourceAttributes (EntryResourceAttributes)
pydantic-model
¶
This class contains the Field for the attributes used to represent a structure, e.g. unit cell, atoms, positions.
assemblies: List[optimade.models.structures.Assembly]
pydantic-field
¶
A description of groups of sites that are statistically correlated. - Type: list of dictionary with keys:
- :property:
sites_in_groups
: list of list of integers (REQUIRED) -
:property:
group_probabilities
: list of floats (REQUIRED) -
Requirements/Conventions:
-
Support: OPTIONAL support in implementations, i.e., MAY be :val:
null
. - Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
- If present, the correct flag MUST be set in the list :property:
structure_features
(see propertystructure_features
_). - Client implementations MUST check its presence (as its presence changes the interpretation of the structure).
-
If present, it MUST be a list of dictionaries, each of which represents an assembly and MUST have the following two keys:
- sites_in_groups: Index of the sites (0-based) that belong to each group for each assembly.
Example: :val:
[[1], [2]]
: two groups, one with the second site, one with the third.Example: :val:
[[1,2], [3]]
: one group with the second and third site, one with the fourth. -
group_probabilities: Statistical probability of each group. It MUST have the same length as :property:
sites_in_groups
. It SHOULD sum to one. See below for examples of how to specify the probability of the occurrence of a vacancy. The possible reasons for the values not to sum to one are the same as already specified above for the :property:concentration
of each :property:species
, see propertyspecies
_. -
If a site is not present in any group, it means that it is present with 100 % probability (as if no assembly was specified).
-
A site MUST NOT appear in more than one group.
-
Examples (for each entry of the assemblies list):
-
:val:
{"sites_in_groups": [[0], [1]], "group_probabilities: [0.3, 0.7]}
: the first site and the second site never occur at the same time in the unit cell. Statistically, 30 % of the times the first site is present, while 70 % of the times the second site is present. -
:val:
{"sites_in_groups": [[1,2], [3]], "group_probabilities: [0.3, 0.7]}
: the second and third site are either present together or not present; they form the first group of atoms for this assembly. The second group is formed by the fourth site. Sites of the first group (the second and the third) are never present at the same time as the fourth site. 30 % of times sites 1 and 2 are present (and site 3 is absent); 70 % of times site 3 is present (and sites 1 and 2 are absent). -
Notes:
-
Assemblies are essential to represent, for instance, the situation where an atom can statistically occupy two different positions (sites).
- By defining groups, it is possible to represent, e.g., the case where a functional molecule (and not just one atom) is either present or absent (or the case where it it is present in two conformations)
-
Considerations on virtual alloys and on vacancies: In the special case of a virtual alloy, these specifications allow two different, equivalent ways of specifying them. For instance, for a site at the origin with 30 % probability of being occupied by Si, 50 % probability of being occupied by Ge, and 20 % of being a vacancy, the following two representations are possible:
- Using a single species:
.. code:: jsonc
{ "cartesian_site_positions": [[0,0,0]], "species_at_sites": ["SiGe-vac"], "species": [ { "name": "SiGe-vac", "chemical_symbols": ["Si", "Ge", "vacancy"], "concentration": [0.3, 0.5, 0.2] } ] // ... }
- Using multiple species and the assemblies:
.. code:: jsonc
{ "cartesian_site_positions": [ [0,0,0], [0,0,0], [0,0,0] ], "species_at_sites": ["Si", "Ge", "vac"], "species": { "Si": { "chemical_symbols": ["Si"], "concentration": [1.0] }, "Ge": { "chemical_symbols": ["Ge"], "concentration": [1.0] }, "vac": { "chemical_symbols": ["vacancy"], "concentration": [1.0] } }, "assemblies": [ { "sites_in_groups": [ [0], [1], [2] ], "group_probabilities": [0.3, 0.5, 0.2] } ] // ... }
-
It is up to the database provider to decide which representation to use, typically depending on the internal format in which the structure is stored. However, given a structure identified by a unique ID, the API implementation MUST always provide the same representation for it.
-
The probabilities of occurrence of different assemblies are uncorrelated. So, for instance in the following case with two assemblies:
.. code:: jsonc
{ "assemblies": [ { "sites_in_groups": [ [0], [1] ], "group_probabilities": [0.2, 0.8], }, { "sites_in_groups": [ [2], [3] ], "group_probabilities": [0.3, 0.7] } ] }
Site 0 is present with a probability of 20 % and site 1 with a probability of 80 %. These two sites are correlated (either site 0 or 1 is present). Similarly, site 2 is present with a probability of 30 % and site 3 with a probability of 70 %. These two sites are correlated (either site 2 or 3 is present). However, the presence or absence of sites 0 and 1 is not correlated with the presence or absence of sites 2 and 3 (in the specific example, the pair of sites (0, 2) can occur with 0.20.3 = 6 % probability; the pair (0, 3) with 0.20.7 = 14 % probability; the pair (1, 2) with 0.80.3 = 24 % probability; and the pair (1, 3) with 0.80.7 = 56 % probability).
cartesian_site_positions: List[Tuple[Union[float, NoneType], Union[float, NoneType], Union[float]]]
pydantic-field
required
¶
Cartesian positions of each site. A site is an atom, a site potentially occupied by an atom, or a placeholder for a virtual mixture of atoms (e.g., in a virtual crystal approximation). - Type: list of list of floats and/or unknown values - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
- It MUST be a list of length N times 3, where N is the number of sites in the structure.
- An entry MAY have multiple sites at the same Cartesian position (for a relevant use of this, see e.g., the property
assemblies
_). - If a component of the position is unknown, the :val:
null
value should be provided instead (see sectionProperties with unknown value
). Otherwise, it should be a float value, expressed in angstrom (Å). If at least one of the coordinates is unknown, the correct flag in the list propertystructure_features
MUST be set. -
Notes: (for implementers) While this is unrelated to this OPTIMADE specification: If you decide to store internally the :property:
cartesian_site_positions
as a float array, you might want to represent :val:null
values with :field-val:NaN
values. The latter being valid float numbers in the IEEE 754 standard inIEEE 754-1985 <https://doi.org/10.1109/IEEESTD.1985.82928>
and in the updated versionIEEE 754-2008 <https://doi.org/10.1109/IEEESTD.2008.4610935>
. -
Examples:
-
:val:
[[0,0,0],[0,0,2]]
indicates a structure with two sites, one sitting at the origin and one along the (positive) z-axis, 2 Å away from the origin.
chemical_formula_anonymous: str
pydantic-field
required
¶
The anonymous formula is the :property:chemical_formula_reduced
, but where the elements are instead first ordered by their chemical proportion number, and then, in order left to right, replaced by anonymous symbols A, B, C, ..., Z, Aa, Ba, ..., Za, Ab, Bb, ... and so on.
- Type: string
- Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. -
Query: MUST be a queryable property. However, support for filters using partial string matching with this property is OPTIONAL (i.e., BEGINS WITH, ENDS WITH, and CONTAINS).
-
Examples:
-
:val:
"A2B"
-
:val:
"A42B42C16D12E10F9G5"
-
Querying:
- A filter that matches an exactly given formula is :filter:
chemical_formula_anonymous="A2B"
.
chemical_formula_descriptive: str
pydantic-field
required
¶
The chemical formula for a structure as a string in a form chosen by the API implementation. - Type: string - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: MUST be a queryable property with support for all mandatory filter operators.
- The chemical formula is given as a string consisting of properly capitalized element symbols followed by integers or decimal numbers, balanced parentheses, square, and curly brackets
(
,)
,[
,]
,{
,}
, commas, the+
,-
,:
and=
symbols. The parentheses are allowed to be followed by a number. Spaces are allowed anywhere except within chemical symbols. The order of elements and any groupings indicated by parentheses or brackets are chosen freely by the API implementation. - The string SHOULD be arithmetically consistent with the element ratios in the :property:
chemical_formula_reduced
property. -
It is RECOMMENDED, but not mandatory, that symbols, parentheses and brackets, if used, are used with the meanings prescribed by
IUPAC's Nomenclature of Organic Chemistry <https://www.qmul.ac.uk/sbcs/iupac/bibliog/blue.html>
__. -
Examples:
-
:val:
"(H2O)2 Na"
- :val:
"NaCl"
- :val:
"CaCO3"
- :val:
"CCaO3"
-
:val:
"(CH3)3N+ - [CH2]2-OH = Me3N+ - CH2 - CH2OH"
-
Query examples:
-
Note: the free-form nature of this property is likely to make queries on it across different databases inconsistent.
- A filter that matches an exactly given formula: :filter:
chemical_formula_descriptive="(H2O)2 Na"
. - A filter that does a partial match: :filter:
chemical_formula_descriptive CONTAINS "H2O"
.
chemical_formula_hill: str
pydantic-field
¶
The chemical formula for a structure in Hill form <https://dx.doi.org/10.1021/ja02046a005>
__ with element symbols followed by integer chemical proportion numbers.
The proportion number MUST be omitted if it is 1.
- Type: string
- Requirements/Conventions:
- Support: OPTIONAL, i.e., MAY be :val:
null
. - Query: Support for queries on these properties are OPTIONAL. If supported, only a subset of filter operators MAY be supported.
- The overall scale factor of the chemical proportions is chosen such that the resulting values are integers that indicate the most chemically relevant unit of which the system is composed.
For example, if the structure is a repeating unit cell with four hydrogens and four oxygens that represents two hydroperoxide molecules, :property:
chemical_formula_hill
is :val:"H2O2"
(i.e., not :val:"HO"
, nor :val:"H4O4"
). - If the chemical insight needed to ascribe a Hill formula to the system is not present, the property MUST be handled as unset.
- Element names MUST have proper capitalization (e.g., :val:
"Si"
, not :VAL:"SI"
for "silicon"). - Elements MUST be placed in
Hill order <https://dx.doi.org/10.1021/ja02046a005>
__, followed by their integer chemical proportion number. Hill order means: if carbon is present, it is placed first, and if also present, hydrogen is placed second. After that, all other elements are ordered alphabetically. If carbon is not present, all elements are ordered alphabetically. - If the system has sites with partial occupation and the total occupations of each element do not all sum up to integers, then the Hill formula SHOULD be handled as unset.
-
No spaces or separators are allowed.
-
Examples:
-
:val:
"H2O2"
-
Query examples:
-
A filter that matches an exactly given formula is :filter:
chemical_formula_hill="H2O2"
.
chemical_formula_reduced: str
pydantic-field
required
¶
The reduced chemical formula for a structure as a string with element symbols and integer chemical proportion numbers. The proportion number MUST be omitted if it is 1. - Type: string - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: MUST be a queryable property.
However, support for filters using partial string matching with this property is OPTIONAL (i.e., BEGINS WITH, ENDS WITH, and CONTAINS).
Intricate querying on formula components are instead recommended to be formulated using set-type filter operators on the multi valued :property:
elements
and :property:elements_proportions
properties. - Element names MUST have proper capitalization (e.g., :val:
"Si"
, not :VAL:"SI"
for "silicon"). - Elements MUST be placed in alphabetical order, followed by their integer chemical proportion number.
- For structures with no partial occupation, the chemical proportion numbers are the smallest integers for which the chemical proportion is exactly correct.
- For structures with partial occupation, the chemical proportion numbers are integers that within reasonable approximation indicate the correct chemical proportions. The precise details of how to perform the rounding is chosen by the API implementation.
-
No spaces or separators are allowed.
-
Examples:
-
:val:
"H2NaO"
- :val:
"ClNa"
-
:val:
"CCaO3"
-
Query examples:
-
A filter that matches an exactly given formula is :filter:
chemical_formula_reduced="H2NaO"
.
dimension_types: Tuple[optimade.models.structures.Periodicity, optimade.models.structures.Periodicity, optimade.models.structures.Periodicity]
pydantic-field
required
¶
List of three integers.
For each of the three directions indicated by the three lattice vectors (see property lattice_vectors
).
This list indicates if the direction is periodic (value :val:1
) or non-periodic (value :val:0
).
Note: the elements in this list each refer to the direction of the corresponding entry in property lattice_vectors
and not the Cartesian x, y, z directions.
- Type: list of integers.
- Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: MUST be a queryable property. Support for equality comparison is REQUIRED, support for other comparison operators are OPTIONAL.
- MUST be a list of length 3.
-
Each integer element MUST assume only the value 0 or 1.
-
Examples:
-
For a molecule: :val:
[0, 0, 0]
- For a wire along the direction specified by the third lattice vector: :val:
[0, 0, 1]
- For a 2D surface/slab, periodic on the plane defined by the first and third lattice vectors: :val:
[1, 0, 1]
- For a bulk 3D system: :val:
[1, 1, 1]
elements: List[str]
pydantic-field
required
¶
Names of the different elements present in the structure. - Type: list of strings. - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: MUST be a queryable property with support for all mandatory filter operators.
- The strings are the chemical symbols, written as uppercase letter plus optional lowercase letters.
- The order MUST be alphabetical.
-
Note: This may not contain the "x" that is suggested in chemical_symbols for the :property:
species
property. -
Examples:
-
:val:
["Si"]
-
:val:
["Al","O","Si"]
-
Query examples:
- A filter that matches all records of structures that contain Si, Al and O, and possibly other elements: :filter:
elements HAS ALL "Si", "Al", "O"
. - To match structures with exactly these three elements, use :filter:
elements HAS ALL "Si", "Al", "O" AND LENGTH elements = 3
.
elements_ratios: List[float]
pydantic-field
required
¶
Relative proportions of different elements in the structure. - Type: list of floats - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: MUST be a queryable property with support for all mandatory filter operators.
- Composed by the proportions of elements in the structure as a list of floating point numbers.
-
The sum of the numbers MUST be 1.0 (within floating point accuracy)
-
Examples:
-
:val:
[1.0]
-
:val:
[0.3333333333333333, 0.2222222222222222, 0.4444444444444444]
-
Query examples:
-
Note: useful filters can be formulated using the set operator syntax for correlated values. However, since the values are floating point values, the use of equality comparisons is generally not recommended.
- A filter that matches structures where approximately 1/3 of the atoms in the structure are the element Al is: :filter:
elements:elements_ratios HAS ALL "Al":>0.3333, "Al":<0.3334
.
lattice_vectors: Tuple[Tuple[Union[float, NoneType], Union[float, NoneType], Union[float, NoneType]], Tuple[Union[float, NoneType], Union[float, NoneType], Union[float, NoneType]], Tuple[Union[float, NoneType], Union[float, NoneType], Union[float]]]
pydantic-field
¶
The three lattice vectors in Cartesian coordinates, in ångström (Å). - Type: list of list of floats. - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
- MUST be a list of three vectors a, b, and c, where each of the vectors MUST BE a list of the vector's coordinates along the x, y, and z Cartesian coordinates. (Therefore, the first index runs over the three lattice vectors and the second index runs over the x, y, z Cartesian coordinates).
- For databases that do not define an absolute Cartesian system (e.g., only defining the length and angles between vectors), the first lattice vector SHOULD be set along x and the second on the xy-plane.
- This property MUST be an array of dimensions 3 times 3 regardless of the elements of :property:
dimension_types
. The vectors SHOULD by convention be chosen so the determinant of the :property:lattice_vectors
matrix is different from zero. The vectors in the non-periodic directions have no significance beyond fulfilling these requirements. -
All three elements of the inner lists of floats MAY be :val:
null
for non-periodic dimensions, i.e., those dimensions for which :property:dimension_types
is :val:0
. -
Examples:
-
:val:
[[4.0,0.0,0.0],[0.0,4.0,0.0],[0.0,1.0,4.0]]
represents a cell, where the first vector is :val:(4, 0, 0)
, i.e., a vector aligned along the :val:x
axis of length 4 Å; the second vector is :val:(0, 4, 0)
; and the third vector is :val:(0, 1, 4)
.
nelements: int
pydantic-field
required
¶
Number of different elements in the structure as an integer. - Type: integer - Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. -
Query: MUST be a queryable property with support for all mandatory filter operators.
-
Example: :val:
3
-
Querying:
-
Note: queries on this property can equivalently be formulated using :filter-fragment:
LENGTH elements
. - A filter that matches structures that have exactly 4 elements: :filter:
nelements=4
. - A filter that matches structures that have between 2 and 7 elements: :filter:
nelements>=2 AND nelements<=7
.
nsites: int
pydantic-field
required
¶
An integer specifying the length of the :property:cartesian_site_positions
property.
- Type: integer
- Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. -
Query: MUST be a queryable property with support for all mandatory filter operators.
-
Examples:
-
:val:
42
-
Query examples:
-
Match only structures with exactly 4 sites: :filter:
nsites=4
- Match structures that have between 2 and 7 sites: :filter:
nsites>=2 AND nsites<=7
species: List[optimade.models.structures.Species]
pydantic-field
required
¶
A list describing the species of the sites of this structure. Species can be pure chemical elements, or virtual-crystal atoms representing a statistical occupation of a given site by multiple chemical elements. - Type: list of dictionary with keys:
- :property:
name
: string (REQUIRED) - :property:
chemical_symbols
: list of strings (REQUIRED) - :property:
concentration
: list of float (REQUIRED) - :property:
mass
: float (OPTIONAL) -
:property:
original_name
: string (OPTIONAL). -
Requirements/Conventions:
-
Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
-
Each list member MUST be a dictionary with the following keys:
-
name: REQUIRED; gives the name of the species; the name value MUST be unique in the :property:
species
list; -
chemical_symbols: REQUIRED; MUST be a list of strings of all chemical elements composing this species.
-
It MUST be one of the following:
- a valid chemical-element name, or
- the special value :val:
"X"
to represent a non-chemical element, or - the special value :val:
"vacancy"
to represent that this site has a non-zero probability of having a vacancy (the respective probability is indicated in the :property:concentration
list, see below).
-
If any one entry in the :property:
species
list has a :property:chemical_symbols
list that is longer than 1 element, the correct flag MUST be set in the list :property:structure_features
(see propertystructure_features
_). -
concentration: REQUIRED; MUST be a list of floats, with same length as :property:
chemical_symbols
. The numbers represent the relative concentration of the corresponding chemical symbol in this species. The numbers SHOULD sum to one. Cases in which the numbers do not sum to one typically fall only in the following two categories: -
Numerical errors when representing float numbers in fixed precision, e.g. for two chemical symbols with concentrations :val:
1/3
and :val:2/3
, the concentration might look something like :val:[0.33333333333, 0.66666666666]
. If the client is aware that the sum is not one because of numerical precision, it can renormalize the values so that the sum is exactly one. - Experimental errors in the data present in the database. In this case, it is the responsibility of the client to decide how to process the data.
Note that concentrations are uncorrelated between different site (even of the same species).
- mass: OPTIONAL. If present MUST be a float expressed in a.m.u.
-
original_name: OPTIONAL. Can be any valid Unicode string, and SHOULD contain (if specified) the name of the species that is used internally in the source database.
With regards to "source database", we refer to the immediate source being queried via the OPTIMADE API implementation.
The main use of this field is for source databases that use species names, containing characters that are not allowed (see description of the list property
species_at_sites
_).
-
-
For systems that have only species formed by a single chemical symbol, and that have at most one species per chemical symbol, SHOULD use the chemical symbol as species name (e.g., :val:
"Ti"
for titanium, :val:"O"
for oxygen, etc.) However, note that this is OPTIONAL, and client implementations MUST NOT assume that the key corresponds to a chemical symbol, nor assume that if the species name is a valid chemical symbol, that it represents a species with that chemical symbol. This means that a species :val:{"name": "C", "chemical_symbols": ["Ti"], "concentration": [1.0]}
is valid and represents a titanium species (and not a carbon species). -
It is NOT RECOMMENDED that a structure includes species that do not have at least one corresponding site.
-
Examples:
-
:val:
[ {"name": "Ti", "chemical_symbols": ["Ti"], "concentration": [1.0]} ]
: any site with this species is occupied by a Ti atom. - :val:
[ {"name": "Ti", "chemical_symbols": ["Ti", "vacancy"], "concentration": [0.9, 0.1]} ]
: any site with this species is occupied by a Ti atom with 90 % probability, and has a vacancy with 10 % probability. - :val:
[ {"name": "BaCa", "chemical_symbols": ["vacancy", "Ba", "Ca"], "concentration": [0.05, 0.45, 0.5], "mass": 88.5} ]
: any site with this species is occupied by a Ba atom with 45 % probability, a Ca atom with 50 % probability, and by a vacancy with 5 % probability. The mass of this site is (on average) 88.5 a.m.u. - :val:
[ {"name": "C12", "chemical_symbols": ["C"], "concentration": [1.0], "mass": 12.0} ]
: any site with this species is occupied by a carbon isotope with mass 12. - :val:
[ {"name": "C13", "chemical_symbols": ["C"], "concentration": [1.0], "mass": 13.0} ]
: any site with this species is occupied by a carbon isotope with mass 13.
species_at_sites: List[str]
pydantic-field
required
¶
Name of the species at each site (where values for sites are specified with the same order of the property cartesian_site_positions
).
The properties of the species are found in the property species
.
- Type: list of strings.
- Requirements/Conventions:
- Support: SHOULD be supported, i.e., SHOULD NOT be :val:
null
. Is REQUIRED in this implementation, i.e., MUST NOT be :val:null
. - Query: Support for queries on this property is OPTIONAL. If supported, filters MAY support only a subset of comparison operators.
- MUST have length equal to the number of sites in the structure (first dimension of the list property
cartesian_site_positions
_). - Each species MUST have a unique name.
- Each species name mentioned in the :property:
species_at_sites
list MUST be described in the list propertyspecies
_ (i.e. for each value in the :property:species_at_sites
list there MUST exist exactly one dictionary in the :property:species
list with the :property:name
attribute equal to the corresponding :property:species_at_sites
value). -
Each site MUST be associated only to a single species. Note: However, species can represent mixtures of atoms, and multiple species MAY be defined for the same chemical element. This latter case is useful when different atoms of the same type need to be grouped or distinguished, for instance in simulation codes to assign different initial spin states.
-
Examples:
-
:val:
["Ti","O2"]
indicates that the first site is hosting a species labeled :val:"Ti"
and the second a species labeled :val:"O2"
.
structure_features: List[str]
pydantic-field
required
¶
A list of strings that flag which special features are used by the structure. - Type: list of strings - Requirements/Conventions:
- Support: REQUIRED, MUST NOT be :val:
null
. - Query: MUST be a queryable property. Filters on the list MUST support all mandatory HAS-type queries. Filter operators for comparisons on the string components MUST support equality, support for other comparison operators are OPTIONAL.
- MUST be an empty list if no special features are used.
- MUST be sorted alphabetically.
- If a special feature listed below is used, the list MUST contain the corresponding string.
- If a special feature listed below is not used, the list MUST NOT contain the corresponding string.
-
List of strings used to indicate special structure features:
- :val:
disorder
: This flag MUST be present if any one entry in the :property:species
list has a :property:chemical_symbols
list that is longer than 1 element. - :val:
unknown_positions
: This flag MUST be present if at least one component of the :property:cartesian_site_positions
list of lists has value :val:null
. - :val:
assemblies
: This flag MUST be present if the propertyassemblies
_ is present.
- :val:
-
Examples: A structure having unknown positions and using assemblies: :val:
["assemblies", "unknown_positions"]