-
Notifications
You must be signed in to change notification settings - Fork 4
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
SOF-7136: property manifest for Hubbard V nearest neighbors #284
Conversation
1735899
to
da3483b
Compare
…stricter validation
da3483b
to
0baa0e8
Compare
"$schema": "http://json-schema.org/draft-04/schema#", | ||
"title": "Hubbard V parameters for nearest neighbors", | ||
"description": "Hubbard V value in eV for nearest neighbors used in hp.x output parsing", | ||
"properties": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe let's just reuse allOf:
"allOf": [
{
"$ref": "hubbard_v.json"
}
And keep description
@@ -24,6 +24,7 @@ | |||
"id2", | |||
"atomicSpecies", | |||
"atomicSpecies2", | |||
"distance", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's have v and v_nn to be identical from the data structure standpoint, the latter is just for convenience purposes.
We could do one of the following:
- get the default highest occupied orbital for each element per https://github.com/Exabyte-io/periodic-table.js/blob/dev/periodic-table.json and insert during parsing
- try to read this information from XML file when dealing with QE
keep the datastructures same, remove properties in difference set from being required
6da8ce8
to
5503b9b
Compare
No description provided.