Skip to content

Conversation

"name",
"values"
]
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be outside structural/basis folder

"allOf": [
{
"$ref": "hubbard_v.json"
"$ref": "../../core/reusable/hubbard_parameters.json"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add reusable inside properties_directory?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

}
]
},
"source": {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We could reuse source for meta and proto holders

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure we need this structure for Meta and Proto holders, as they contain an empty source:

"source" : {
        "info" : {

        },
        "type" : "exabyte"
    }

And holder has:

"source" : {
        "type" : "exabyte",
        "info" : {
            "jobId" : "HKPDxdJgGX5FrXLCy",
            "unitId" : "f23e15fa1304b005d942d64c-2ba70021fabbc28cbfb7cee0"
        }
    }

"type": "object",
"allOf": [
{
"$ref": "../../material.json"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need to store material here too?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Material exists in all in_relaxed properties in the production database

"units": "kbar",
"value": -149.03
"value": -149.03,
"repetition": 0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not be here

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

"name": "pressure",
"units": "kbar",
"value": -149.03
"value": -149.03,
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the name of the file could be holder.json instead of base

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

{
"type": "null"
}
]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should keep compute

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

"legend": {
"description": "Legend of y Axis data series",
"minItems": 1,
"type": "array"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we need legend anymore?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Based on production databases, we need legend only for the density_of_states property. Even more, the legend is required in the density_of_states property. It is already properly defined in density_of_states.json, file so I just removed it from here.

- Add new coordinate condition schemas (cylinder, plane, sphere, triangular_prism)
- Add hubbard_parameters schema and jupyter_notebook_endpoint property
- Add final_structure and is_relaxed properties
- Add boundary_conditions and workflow properties
- Refactor property schemas: rename base.json to holder.json, add meta_holder and proto_holder
- Remove exabyteml and related ML schemas
- Update property schemas with required fields and improved validation
- Add repetition field to property schemas
- Improve band structure, phonon DOS, and other property schemas
- Update workflow schemas with better input/output handling
- Regenerate all Python models and TypeScript types
- Update package dependencies
class Name657(Enum):
=======
class Name573(Enum):
>>>>>>> 8664c20e94ca9d52fce78f266358a60c7d88fb37
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Somethins malfunctioned here - let's clean up the merge artifacts, pls.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should all be fine now

class Name804(Enum):
=======
class Name717(Enum):
>>>>>>> 8664c20e94ca9d52fce78f266358a60c7d88fb37
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above

class Name739(Enum):
=======
class Name653(Enum):
>>>>>>> 8664c20e94ca9d52fce78f266358a60c7d88fb37
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above

class Type75(Enum):
>>>>>>> 8664c20e94ca9d52fce78f266358a60c7d88fb37
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here, too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants