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
I am using mbuild/foyer in a workflow in planckton. We have a couple older input mol2 files which were typed with antechamber, and for these the particle name will match the type name in a gaff (custom) forcefield. The element in the compound is manually set, and this transfers to the parmed structure, but when the apply function is used, the atomic number is not carried over from the input structure.
Code to reproduce the behavior
I'm using the example I described from planckton--if needed, I can work up a simpler example.
- foyer.Forcefield.apply does not carry over the set atomic_number info
from the pmd_structure. mosdef-hub/foyer/issues/466 This workaround will
fix it.
Bug summary
I am using mbuild/foyer in a workflow in planckton. We have a couple older input mol2 files which were typed with antechamber, and for these the particle name will match the type name in a gaff (custom) forcefield. The element in the compound is manually set, and this transfers to the parmed structure, but when the apply function is used, the atomic number is not carried over from the input structure.
Code to reproduce the behavior
I'm using the example I described from planckton--if needed, I can work up a simpler example.
output:
Software versions
NOTE: The below template should have dunder around version:
python -c "import foyer; print(foyer.__version__)"
)0.9.4
python --version
)?Python 3.7.11
CentOS Linux release 7.8.2003 (Core)
The text was updated successfully, but these errors were encountered: