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
For forcefields such as tip4p, we can read the forcefield, and virtual sites are treated just the same as a site. The virtual site is then assigned an atomtype just the same via the forcefield, and this is great. However, for our writers, these virtual sites need to be identified (and differentiated from coarse grained systems) in order to be handled specially. For example, Gromacs has a [ dummies ] section that needs to be written if a lone pair is included. Currently, since we have no special implementation for it, the top writer will throw an error.
We need to add some logic into the writers that can handle virtual sites, potentially some changes logic into the gmso.Site to assist with that, and make sure any readers that could have virtual sites would also properly bring that into a gmso.Topology.
For forcefields such as tip4p, we can read the forcefield, and virtual sites are treated just the same as a site. The virtual site is then assigned an atomtype just the same via the forcefield, and this is great. However, for our writers, these virtual sites need to be identified (and differentiated from coarse grained systems) in order to be handled specially. For example, Gromacs has a
[ dummies ]
section that needs to be written if a lone pair is included. Currently, since we have no special implementation for it, the top writer will throw an error.We need to add some logic into the writers that can handle virtual sites, potentially some changes logic into the
gmso.Site
to assist with that, and make sure any readers that could have virtual sites would also properly bring that into a gmso.Topology.Errors as:
The text was updated successfully, but these errors were encountered: