Bug #2483

gmx dump writes mdp files that can not be parsed by grompp

Added by Paul Bauer almost 3 years ago. Updated over 2 years ago.

preprocessing (pdb2gmx,grompp)
Target version:
Affected version - extra info:
properly affecting a number of versions previously as well, but haven't checked this
Affected version:


While checking some tpr files for an unrelated bug I found out that grompp is unable to process mdp files provided by gmx dump -om.
The issue seems to be with some (now unrecognised) fields being written to the file, as well as using the wrong name syntax for a number of options.


#1 Updated by Paul Bauer almost 3 years ago

From checking the code for readir and pr_inputrec it seems to be a conflict between the input bool values accepted ("yes" or "no", as defined by yesno_names), and what is written out as a result of the EBOOL macro (and the boolToString function) that is either "true" or "false".
One proposed fix would be to update the definitions for yesno_names, or refactor the variable reading to use the boolFromString function instead.

#2 Updated by Gerrit Code Review Bot over 2 years ago

Gerrit received a related patchset '1' for Issue #2483.
Uploader: Paul Bauer ()
Change-Id: gromacs~master~I8e0540c415eceddfd43db1a243509f8a4c22b50b
Gerrit URL:

#3 Updated by Mark Abraham over 2 years ago

If we want this to continue to work, then we need e.g. an integration test case that shows that grompp then dump produces a valid input to grompp.

#4 Updated by Mark Abraham over 2 years ago

  • Target version set to 2019

Can we fix this before the final release?

#5 Updated by Paul Bauer over 2 years ago

  • Target version changed from 2019 to future

I don't think so. The issue was that the writing needs info about the group names being used, and I couldn't find any reasonable way to get the information into the write method. Also, it looks like the group names are not stored properly in the symtab (as far as my offline work for modifying this has shown).

Also available in: Atom PDF