Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix the definition of cartesian_site_positions length #216

Merged
merged 3 commits into from
Dec 4, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion optimade.rst
Original file line number Diff line number Diff line change
Expand Up @@ -1676,7 +1676,7 @@ cartesian\_site\_positions

- **Response**: REQUIRED in the response unless explicitly excluded.
- **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.
- It MUST be a list of length equal to the number of sites in the structure.
merkys marked this conversation as resolved.
Show resolved Hide resolved
- 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 section `Properties with unknown value`_).
Otherwise, it should be a float value, expressed in angstrom (Å).
Expand Down