Skip to content

Conversation

PhaniD
Copy link

@PhaniD PhaniD commented May 2, 2017

No description provided.

"access": {
"...": "include(../security/access_legacy.json)"
"type": 10,
"level": 10
Copy link
Member

Choose a reason for hiding this comment

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

We shouldnt change this

Copy link
Author

Choose a reason for hiding this comment

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

Don't know the reason why this include is not working.

8.15
]
],
"coordNumber":[
Copy link
Member

Choose a reason for hiding this comment

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

coordinationNumber

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 use full names below too

"equilibrium": "0",
"matType": "0",
"vatom": 0.15
}
Copy link
Member

Choose a reason for hiding this comment

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

The above keys are not clear from first sight

"type": "array",
"items": {
"description": "array of s,p,d,f contributions for individual element ",
"ref": "file:../../../primitive/1d_data_series.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 make this into an object?

{
's': 0.5,
'f': 0.5
}

@@ -0,0 +1,3 @@
{
Copy link
Member

@timurbazhirov timurbazhirov May 10, 2017

Choose a reason for hiding this comment

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

Let's try to refer to subfield of lattice_bravais?

"$ref": "file:../../../primitive/1d_data_series.json"
},
"localEnvironment": {
"description": "Represents the atom type each element is bonded to in the list [H, O, S, F, Cl, X]. X means an element is either non-bonded or bonded to any atom other than the atoms in the list",
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 use enum to set the list items

@@ -0,0 +1,2600 @@
{
"elements": [
{
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 leave one example only

@@ -0,0 +1,15 @@
{
"type": "compound-specific",
Copy link
Member

Choose a reason for hiding this comment

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

Element-specific

"description": "structure representation.",
"allOf": [
{
"$ref": "file:primary/_primary.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 include this file only once at the top?

"type": "compound-specific",
"subtype": "stoichiometric",
"variableType": "numeric",
"dimensions": [
Copy link
Member

@timurbazhirov timurbazhirov May 13, 2017

Choose a reason for hiding this comment

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

values

"variableType": "numeric",
"dimensions": [
{
"name": "p3",
Copy link
Member

Choose a reason for hiding this comment

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

dimensionality

"valenceOrbitalOccupancy": {
"...": "include(primary/valence_orbital_occupancy.json)"
},
"pNorm": {
Copy link
Member

Choose a reason for hiding this comment

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

pNorms

@timurbazhirov
Copy link
Member

Let's adjust with the following in mind:

type: element-specific / compound-specific OR E/C
subtype: "nominal", "ordinal", "numeric" OR NO/OR/NU
category: "electronic", "chemical"

1 E NO => schema1

{
    "elements": [
        {
            "name": "Si",
            "value": "O"
        },
        {
            "name": "O",
            "value": "X"
        }
    ]
}

2 E OR => schema1

{
    "elements": [
        {
            "name": "Si",
            "value": "low"
        },
        {
            "name": "O",
            "value": "high"
        }
    ]
}

3 E NU => schema1

{
    "elements": [
        {
            "name": "Si",
            "value": 1
        },
        {
            "name": "O",
            "value": 2
        }
    ]
}

4 C NO => schema2

{
    "value": "crystal"
}

5 C OR => schema2

{
    "value": "low"
}

6 C NU => schema2

{
    "value": 1
}

7 C NU ARRAY => schema3

{
    "data": [
        {
            "name": "p3",
            "value": 1
        },
        {
            "name": "p2",
            "value": 2
        }
    ]
}

"element": "Si",
"valenceElectrons": {
"value": 6,
"name": "valence_electrons"
Copy link
Member

Choose a reason for hiding this comment

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

Remove the names

{
"id": 1,
"value": "Si"
"value": "Si",
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 not add into elements, into the data instead

@@ -0,0 +1,3 @@
{
Copy link
Author

Choose a reason for hiding this comment

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

We need to discuss regarding elements schema.

Elements schema is to store elemental properties for a specific element. If I include atomic_data in elements json, I unnecessarily store the ids of the elements.

Copy link
Member

Choose a reason for hiding this comment

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

OK

@PhaniD PhaniD changed the base branch from dev to epic/SOF-2008 May 15, 2017 22:04
@PhaniD PhaniD merged commit 15479a7 into epic/SOF-2008 May 22, 2017
@timurbazhirov timurbazhirov deleted the feature/SOF-2168 branch June 1, 2017 05:23
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