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
This issue was discovered by @marjanalb: Basically when creating a gsd file from an mbuild compound--the bonds and particles information is present in the gsd, but the angle and dihedral information is not.
(Angle and dihedral information in create_hoomd_simulation and create_hoomd_forcefield works just fine. I think this is due to those functions using a parmed structure--the mbuild to parmed conversion handles the angle/dihedral detection.)
Code to reproduce the behavior
Please include a code snippet that can be used to reproduce this bug.
Yeah, I think that is correct, an mBuild compound itself has no idea about angles and dihedrals, those information only get populated during the atomtyping step with OpenMM and Parmed. I am not sure what would be the best route to fix this issue (either convert it to gmso and identify all the angles and dihedrals before writing out, or go through parmed, but we can figure something out)
Closing this as you can now populate angle and dihedrals when writing a gsd file if you use gmso.identify_connections() along with gmso's GSD writer as opposed to gsd writer in mBuild.
Quick example:
comp = mb.load("CCCC", smiles=True)
system = mb.fill_box(comp, n_compounds=3, density=100)
top = from_mbuild(system)
top.identify_connections()
top.save("out.gsd")
Bug summary
This issue was discovered by @marjanalb: Basically when creating a gsd file from an mbuild compound--the
bonds
andparticles
information is present in the gsd, but the angle and dihedral information is not.(Angle and dihedral information in
create_hoomd_simulation
andcreate_hoomd_forcefield
works just fine. I think this is due to those functions using a parmed structure--the mbuild to parmed conversion handles the angle/dihedral detection.)Code to reproduce the behavior
Please include a code snippet that can be used to reproduce this bug.
This prints 0 when it should print 36 (I think).
Software versions
python -c "import mbuild as mb; print(mb.__version__)"
) 0.10.13python --version
)? 3.7.10The text was updated successfully, but these errors were encountered: