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
Computing environment (please complete the following information):
Operating system
Output of running conda list
toolkit version: 0.11.4
Additional context
The example given here isn't too bad. However, it's a tad inconvenient because it means users can't use element symbol smarts (.to_smiles) but have to use atomic numbers instead (have to pass through RDKit's Chem.MolToSmarts). It's also surprising, as I think SMIRKS allows you to use symbols as element specifications. However, parameters like the LibraryCharge below get interpreted as an unholy mishmash of coulomb and farad.
Describe the bug
Loading a ForceField from file substitutes units inappropriately. For example, "F" seems to get converted into
1 * farad
, and K to1 * kelvin
.To Reproduce
The easiest way to see this is to load base Sage:
Output
Checking https://github.com/openforcefield/openff-forcefields/blob/e2cb3b0746a173eb18d499bc680d9758ccaae657/openforcefields/offxml/openff-2.0.0.offxml#L363 shows the original name was just
K+
.Computing environment (please complete the following information):
conda list
Additional context
The example given here isn't too bad. However, it's a tad inconvenient because it means users can't use element symbol smarts (
.to_smiles
) but have to use atomic numbers instead (have to pass through RDKit'sChem.MolToSmarts
). It's also surprising, as I think SMIRKS allows you to use symbols as element specifications. However, parameters like the LibraryCharge below get interpreted as an unholy mishmash of coulomb and farad.And an aliphatic smarts would be interpreted as 1 ampere.
Loading a file that contains the above gets me:
One solution could be to restrict this parameter interpretation to not apply to known keywords, like
smirks
andname
.The text was updated successfully, but these errors were encountered: