Open wavefunction91 opened 21 hours ago
On the Molecule
vs. AtomicInput.specification.model
choice, I think solvation falls on model
. For Molecule, besides identifiers, we've been roughly keeping it limited to things having to do with the atom center coordinates.
EDIT: Also, float or string for epsilon?
Also, float or string for epsilon?
Good catch
Is your feature request related to a problem? Please describe.
QCSchema (and friends) do not currently expose the ability to (transparently) specify solvation settings. This is a highly desirable feature for the community.
Describe the solution you'd like
It would be desirable to extend the schema to include a
solvent
data structure to allow for IO specification of solvation settings. Where this lives is not immediately obvious to me - I could see it extending either themolecule
schema (to the extent thatmolecule
defines the physical system) or themodel
schema (to the extent to which one is modifying the model physics - alamethod
andbasis
). Wherever this should live, the following items should be made variablename
model
epsilon
Describe alternatives you've considered
It is generally the case that one can specify solvent settings in a program-specific
keyword
setting, but this is not a satisfying solution for interoperability between codes nor for archiving of data.