You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating 3dSets (e.g., conformers, molecular dynamics, following an optimization or IRC) it is useful to retain multiple properties - particularly relative energies.
It's not clear the best way to do handle this.
The text was updated successfully, but these errors were encountered:
The difference is that if we avoid nested objects (dictionaries, maps) in properties the parsing code just handles properties as one key/value store (e.g. energies is an array of numbers).
Thus properties would be a VariantMap for Avogadro:
booleans
numbers
strings
numeric arrays
2D matrices (e.g., polarizabilities or lists of numeric arrays)
The schema can then specify a few well-defined keys (e.g., totalCharge, spinMultiplicity, energies, totalEnergy, etc.)
When creating 3dSets (e.g., conformers, molecular dynamics, following an optimization or IRC) it is useful to retain multiple properties - particularly relative energies.
It's not clear the best way to do handle this.
The text was updated successfully, but these errors were encountered: