config¶
This submodule defines constant values and definitions from the OPTIMADE specification for use by the validator.
The VALIDATOR_CONFIG
object can be imported and modified
before calling the validator inside a Python script to customise
the hardcoded values.
ENTRY_INFO_SCHEMAS: dict[str, type[EntryResource]] = {'structures': StructureResource, 'references': ReferenceResource}
module-attribute
¶
This dictionary is used to define the /info/<entry_type>
endpoints.
VALIDATOR_CONFIG = ValidatorConfig()
module-attribute
¶
_ENTRY_ENDPOINTS = ('structures', 'references', 'calculations')
module-attribute
¶
_ENTRY_SCHEMAS = {endp: retrieve_queryable_properties(ENTRY_INFO_SCHEMAS[endp], ('id', 'type', 'attributes'))for endp in ENTRY_INFO_SCHEMAS}
module-attribute
¶
_ENUM_DUMMY_VALUES = {'structures': {'structure_features': [allowed.value for allowed in StructureFeatures]}}
module-attribute
¶
_EXCLUSIVE_OPERATORS = {DataType.STRING: exclusive_ops, DataType.TIMESTAMP: (), DataType.FLOAT: (), DataType.INTEGER: exclusive_ops, DataType.LIST: ()}
module-attribute
¶
_FIELD_SPECIFIC_OVERRIDES = {'chemical_formula_anonymous': {SupportLevel.OPTIONAL: substring_operators}, 'chemical_formula_reduced': {SupportLevel.OPTIONAL: substring_operators}, 'immutable_id': {SupportLevel.OPTIONAL: [op for op in substring_operators + inclusive_ops + exclusive_ops if op != '=']}, 'structure_features': {SupportLevel.OPTIONAL: 'LENGTH'}}
module-attribute
¶
_INCLUSIVE_OPERATORS = {DataType.STRING: inclusive_ops + substring_operators, DataType.TIMESTAMP: ('>='), DataType.INTEGER: inclusive_ops, DataType.FLOAT: (), DataType.LIST: ('HAS', 'HAS ALL', 'HAS ANY', 'LENGTH')}
module-attribute
¶
_NON_ENTRY_ENDPOINTS = ('info', 'links', 'versions')
module-attribute
¶
_RESPONSE_CLASSES = {'references': ValidatorReferenceResponseMany, 'references/': ValidatorReferenceResponseOne, 'structures': ValidatorStructureResponseMany, 'structures/': ValidatorStructureResponseOne, 'info': InfoResponse, 'links': ValidatorLinksResponse}
module-attribute
¶
_RESPONSE_CLASSES_INDEX = {'info': IndexInfoResponse, 'links': ValidatorLinksResponse}
module-attribute
¶
_UNIQUE_PROPERTIES = ('id', 'immutable_id')
module-attribute
¶
__all__ = ('ValidatorConfig', 'VALIDATOR_CONFIG')
module-attribute
¶
exclusive_ops = ('!=', '<', '>')
module-attribute
¶
inclusive_ops = ('=', '<=', '>=')
module-attribute
¶
substring_operators = ('CONTAINS', 'STARTS WITH', 'STARTS', 'ENDS WITH', 'ENDS')
module-attribute
¶
BaseResourceMapper
¶
Generic Resource Mapper that defines and performs the mapping between objects in the database and the resource objects defined by the specification.
Attributes:
Name | Type | Description |
---|---|---|
ALIASES |
tuple[tuple[str, str], ...]
|
a tuple of aliases between
OPTIMADE field names and the field names in the database ,
e.g. |
LENGTH_ALIASES |
tuple[tuple[str, str], ...]
|
a tuple of aliases between
a field name and another field that defines its length, to be used
when querying, e.g. |
ENTRY_RESOURCE_CLASS |
type[EntryResource]
|
The entry type that this mapper corresponds to. |
PROVIDER_FIELDS |
tuple[str, ...]
|
a tuple of extra field names that this mapper should support when querying with the database prefix. |
TOP_LEVEL_NON_ATTRIBUTES_FIELDS |
set[str]
|
the set of top-level field names common to all endpoints. |
SUPPORTED_PREFIXES |
set[str]
|
The set of prefixes registered by this mapper. |
ALL_ATTRIBUTES |
set[str]
|
The set of attributes defined across the entry resource class and the server configuration. |
ENTRY_RESOURCE_ATTRIBUTES |
dict[str, Any]
|
A dictionary of attributes and their definitions defined by the schema of the entry resource class. |
ENDPOINT |
str
|
The expected endpoint name for this resource, as defined by
the |
Source code in optimade/server/mappers/entries.py
36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 |
|
ALL_ATTRIBUTES()
¶
Returns all attributes served by this entry.
Source code in optimade/server/mappers/entries.py
134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 |
|
ENDPOINT()
cached
¶
Returns the expected endpoint for this mapper, corresponding
to the type
property of the resource class.
Source code in optimade/server/mappers/entries.py
161 162 163 164 165 166 167 168 169 170 171 |
|
ENTRY_RESOURCE_ATTRIBUTES()
¶
Returns the dictionary of attributes defined by the underlying entry resource class.
Source code in optimade/server/mappers/entries.py
154 155 156 157 158 159 |
|
SUPPORTED_PREFIXES()
cached
¶
A set of prefixes handled by this entry type.
Note
This implementation only includes the provider prefix, but in the future this property may be extended to include other namespaces (for serving fields from, e.g., other providers or domain-specific terms).
Source code in optimade/server/mappers/entries.py
118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 |
|
alias_for(field)
cached
classmethod
¶
Return aliased field name.
Deprecated
This method is deprecated could be removed without further warning. Please use
get_backend_field()
.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
field |
str
|
OPTIMADE field name. |
required |
Returns:
Type | Description |
---|---|
str
|
Aliased field as found in |
Source code in optimade/server/mappers/entries.py
239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 |
|
alias_of(field)
cached
classmethod
¶
Return de-aliased field name, if it exists, otherwise return the input field name.
Deprecated
This method is deprecated could be removed without further warning. Please use
get_optimade_field()
.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
field |
str
|
Field name to be de-aliased. |
required |
Returns:
Type | Description |
---|---|
str
|
De-aliased field name, falling back to returning |
Source code in optimade/server/mappers/entries.py
289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 |
|
all_aliases()
cached
classmethod
¶
Returns all of the associated aliases for this entry type, including those defined by the server config. The first member of each tuple is the OPTIMADE-compliant field name, the second is the backend-specific field name.
Returns:
Type | Description |
---|---|
Iterable[tuple[str, str]]
|
A tuple of alias tuples. |
Source code in optimade/server/mappers/entries.py
79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 |
|
all_length_aliases()
cached
classmethod
¶
Returns all of the associated length aliases for this class, including those defined by the server config.
Returns:
Type | Description |
---|---|
tuple[tuple[str, str], ...]
|
A tuple of length alias tuples. |
Source code in optimade/server/mappers/entries.py
173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 |
|
deserialize(results)
classmethod
¶
Converts the raw database entries for this class into serialized models, mapping the data along the way.
Source code in optimade/server/mappers/entries.py
367 368 369 370 371 372 373 374 375 376 377 378 |
|
get_backend_field(optimade_field)
cached
classmethod
¶
Return the field name configured for the particular underlying database for the passed OPTIMADE field name, that would be used in an API filter.
Aliases are read from
all_aliases()
.
If a dot-separated OPTIMADE field is provided, e.g., species.mass
, only the first part will be mapped.
This means for an (OPTIMADE, DB) alias of (species
, kinds
), get_backend_fields("species.mass")
will return kinds.mass
.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
optimade_field |
str
|
The OPTIMADE field to attempt to map to the backend-specific field. |
required |
Examples:
>>> get_backend_field("chemical_formula_anonymous")
'formula_anon'
>>> get_backend_field("formula_anon")
'formula_anon'
>>> get_backend_field("_exmpl_custom_provider_field")
'custom_provider_field'
Returns:
Type | Description |
---|---|
str
|
The mapped field name to be used in the query to the backend. |
Source code in optimade/server/mappers/entries.py
204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 |
|
get_optimade_field(backend_field)
cached
classmethod
¶
Return the corresponding OPTIMADE field name for the underlying database field, ready to be used to construct the OPTIMADE-compliant JSON response.
Aliases are read from
all_aliases()
.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
backend_field |
str
|
The backend field to attempt to map to an OPTIMADE field. |
required |
Examples:
>>> get_optimade_field("chemical_formula_anonymous")
'chemical_formula_anonymous'
>>> get_optimade_field("formula_anon")
'chemical_formula_anonymous'
>>> get_optimade_field("custom_provider_field")
'_exmpl_custom_provider_field'
Returns:
Type | Description |
---|---|
str
|
The mapped field name to be used in an OPTIMADE-compliant response. |
Source code in optimade/server/mappers/entries.py
261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 |
|
get_required_fields()
cached
classmethod
¶
Get REQUIRED response fields.
Returns:
Type | Description |
---|---|
set
|
REQUIRED response fields. |
Source code in optimade/server/mappers/entries.py
312 313 314 315 316 317 318 319 320 321 |
|
length_alias_for(field)
cached
classmethod
¶
Returns the length alias for the particular field,
or None
if no such alias is found.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
field |
str
|
OPTIMADE field name. |
required |
Returns:
Type | Description |
---|---|
Optional[str]
|
Aliased field as found in |
Source code in optimade/server/mappers/entries.py
189 190 191 192 193 194 195 196 197 198 199 200 201 202 |
|
map_back(doc)
classmethod
¶
Map properties from MongoDB to OPTIMADE.
Starting from a MongoDB document doc
, map the DB fields to the corresponding OPTIMADE fields.
Then, the fields are all added to the top-level field "attributes",
with the exception of other top-level fields, defined in cls.TOP_LEVEL_NON_ATTRIBUTES_FIELDS
.
All fields not in cls.TOP_LEVEL_NON_ATTRIBUTES_FIELDS
+ "attributes" will be removed.
Finally, the type
is given the value of the specified cls.ENDPOINT
.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
doc |
dict
|
A resource object in MongoDB format. |
required |
Returns:
Type | Description |
---|---|
dict
|
A resource object in OPTIMADE format. |
Source code in optimade/server/mappers/entries.py
323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 |
|
DataType
¶
Bases: Enum
Optimade Data types
See the section "Data types" in the OPTIMADE API specification for more information.
Source code in optimade/models/optimade_json.py
28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 |
|
from_json_type(json_type)
classmethod
¶
Get OPTIMADE data type from a named JSON type
Source code in optimade/models/optimade_json.py
93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 |
|
from_python_type(python_type)
classmethod
¶
Get OPTIMADE data type from a Python type
Source code in optimade/models/optimade_json.py
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 |
|
get_values()
classmethod
¶
Get OPTIMADE data types (enum values) as a (sorted) list
Source code in optimade/models/optimade_json.py
43 44 45 46 |
|
IndexInfoResponse
¶
Bases: Success
Source code in optimade/models/responses.py
53 54 55 56 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
InfoResponse
¶
Bases: Success
Source code in optimade/models/responses.py
66 67 68 69 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
StructureFeatures
¶
Bases: Enum
Enumeration of structure_features values
Source code in optimade/models/structures.py
55 56 57 58 59 60 61 |
|
SupportLevel
¶
Bases: Enum
OPTIMADE property/field support levels
Source code in optimade/models/utils.py
31 32 33 34 35 36 |
|
ValidatorConfig
¶
Bases: BaseSettings
This class stores validator config parameters in a way that can be easily modified for testing niche implementations. Many of these fields are determined by the specification directly, but it may be desirable to modify them in certain cases.
Source code in optimade/validator/config.py
119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 |
|
ValidatorLinksResponse
¶
Bases: Success
Source code in optimade/validator/utils.py
404 405 406 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorReferenceResponseMany
¶
Bases: ValidatorEntryResponseMany
Source code in optimade/validator/utils.py
425 426 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorReferenceResponseOne
¶
Bases: ValidatorEntryResponseOne
Source code in optimade/validator/utils.py
421 422 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorStructureResponseMany
¶
Bases: ValidatorEntryResponseMany
Source code in optimade/validator/utils.py
433 434 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
ValidatorStructureResponseOne
¶
Bases: ValidatorEntryResponseOne
Source code in optimade/validator/utils.py
429 430 |
|
model_config = ConfigDict(json_encoders={datetime: lambda : v.astimezone(timezone.utc).strftime('%Y-%m-%dT%H:%M:%SZ')})
class-attribute
instance-attribute
¶
The specification mandates that datetimes must be encoded following RFC3339, which does not support fractional seconds, thus they must be stripped in the response. This can cause issues when the underlying database contains fields that do include microseconds, as filters may return unexpected results.
either_data_meta_or_errors_must_be_set()
¶
Overwriting the existing validation function, since 'errors' MUST NOT be set.
Source code in optimade/models/optimade_json.py
387 388 389 390 391 392 393 394 395 396 397 398 399 400 |
|
retrieve_queryable_properties(schema, queryable_properties=None, entry_type=None)
¶
Recursively loops through a pydantic model, returning a dictionary of all the OPTIMADE-queryable properties of that model.
Parameters:
Name | Type | Description | Default |
---|---|---|---|
schema |
type[EntryResource]
|
The pydantic model. |
required |
queryable_properties |
Optional[Iterable[str]]
|
The list of properties to find in the schema. |
None
|
entry_type |
Optional[str]
|
An optional entry type for the model. Will be used to lookup schemas for any config-defined fields. |
None
|
Returns:
Type | Description |
---|---|
QueryableProperties
|
A flat dictionary with properties as keys, containing the field |
QueryableProperties
|
description, unit, sortability, support level, queryability |
QueryableProperties
|
and type, where provided. |
Source code in optimade/server/schemas.py
53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 |
|