Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential Issue with GROMACS gro writer #773

Open
daico007 opened this issue Oct 10, 2023 · 0 comments
Open

Potential Issue with GROMACS gro writer #773

daico007 opened this issue Oct 10, 2023 · 0 comments

Comments

@daico007
Copy link
Member

I bumped into an interesting case in using GMSO gro writer. The system of interest is a monolayer sandwiched between 2 box of water on top and bottom. This system is created by mbuild, starting by building the top water box, the monolayer, and the bottom monolayer box separately. The three mbuild Compound is then added to a new container and convert to GMSO Topology to be parameterized and saved out. The failed/interesting case popped up when I tried to put 2 or more species in the solvent boxes. When it's done that way, the order of each species in each object is conserved and stacked on top of each other, (e.g., Water_in_box1, ET_in_box_1, Monolayer, Water_in_box2, ET_in_box2), this order is conserved when saving out to the gro file. GROMACS, however, need every residues to be lumped together (e.g., Water_in_box1, water_in_box2, monolayer, ET_in_box1, ET_in_box2) or else it would lead to some unexpected errors during grompp and mdrun. Hence, to avoid bumping into such case (quite hard to detect if people, including myself, were not aware about the gro requirement about residue order), I think GMSO could do some additional checks, or even utility to rearrange the topology.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant