question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Trouble parsing `gro` and `top` files

See original GitHub issue

I’m trying to run a YANK calculation using gromacs system inputs. Following the example here, my yaml script includes the following entries:

systems:
  gromacs-system:
    phase1_path: [HV149/System/topol.top, HV149/System/6md_mol.gro]
    phase2_path: [HV149/ligand/lig.top, HV149/ligand/ions.gro]
    ligand_dsl: resname V49
    solvent_dsl: resname SOL 
    gromacs_include_dir: /cbio/jclab/home/rossg/gromacs/share/top/amber99sb-ildn.ff/ 

However, there seems to be a problem with the file types as I get the following error message when I run yank:

Wrong system file types provided.
Extensions provided: ['gro', 'top']
Expected extensions: ['inpcrd', 'prmtop']

Wrong system file types provided.
Extensions provided: ['gro', 'top']
Expected extensions: ['inpcrd', 'prmtop']

Correctly recognized files ['HV149/System/topol.top', 'HV149/System/6md_mol.gro'] as ['gro', 'top']
Correctly recognized files ['HV149/ligand/lig.top', 'HV149/ligand/ions.gro'] as ['gro', 'top']
Correctly recognized files ['HV149/System/topol.top', 'HV149/System/6md_mol.gro'] as ['gro', 'top']
Correctly recognized files ['HV149/ligand/lig.top', 'HV149/ligand/ions.gro'] as ['gro', 'top']
Correctly recognized files ['HV149/System/topol.top', 'HV149/System/6md_mol.gro'] as ['gro', 'top']
Correctly recognized files ['HV149/ligand/lig.top', 'HV149/ligand/ions.gro'] as ['gro', 'top']
Wrong system file types provided.
Extensions provided: ['gro', 'top']
Expected extensions: ['pdb', 'xml']

2017-05-04 11:45:20,121: ERROR - yank.yamlbuild - System gromacs-system: _system_files(['HV149/System/topol.top', 'HV149/System/6md_mol.gro']) raised RuntimeError("Wrong system file types provided.\nExtensions provided: ['gro', 'top']\nExpected extensions: ['pdb', 'xml']\n",)
Traceback (most recent call last):
  File "/cbio/jclab/home/rossg/miniconda2/bin/yank", line 11, in <module>
    load_entry_point('yank==0.15.2', 'console_scripts', 'yank')()
  File "/cbio/jclab/home/rossg/miniconda2/lib/python2.7/site-packages/yank/cli.py", line 71, in main
    dispatched = getattr(commands, command).dispatch(command_args)
  File "/cbio/jclab/home/rossg/miniconda2/lib/python2.7/site-packages/yank/commands/script.py", line 97, in dispatch
    yaml_builder = YamlBuilder(yaml_source=yaml_path)
  File "/cbio/jclab/home/rossg/miniconda2/lib/python2.7/site-packages/yank/yamlbuild.py", line 1221, in __init__
    self.parse(yaml_source)
  File "/cbio/jclab/home/rossg/miniconda2/lib/python2.7/site-packages/yank/yamlbuild.py", line 1314, in parse
    self._db.systems = self._validate_systems(yaml_content.get('systems', {}))
  File "/cbio/jclab/home/rossg/miniconda2/lib/python2.7/site-packages/yank/yamlbuild.py", line 1861, in _validate_systems
    raise YamlParseError('System {}: {}'.format(system_id, e.autos[-1]))
yank.yamlbuild.YamlParseError: System gromacs-system: _system_files(['HV149/System/topol.top', 'HV149/System/6md_mol.gro']) raised RuntimeError("Wrong system file types provided.\nExtensions provided: ['gro', 'top']\nExpected extensions: ['pdb', 'xml']\n",)

Are gromacs files not yet supported?

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
gregoryrosscommented, May 4, 2017

Thanks @andrrizzi! Adding solvents key removed that error. I’ll close this issue.

0reactions
andrrizzicommented, May 4, 2017

Also, notice that if you specify solvent_dsl: resname SOL you need to have counterions named SOL too or yank won’t treat them as solvent counterions. SOL is among the names automatically recognized by Yank so you can remove the solvent_dsl altogether. Alternatively you’ll need to add manually the DSL of your counterions.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Parsing a .gro file - Julia Discourse
The main “problem” I have with this is how I have to deal with digits and strings touching each other without a whitespace...
Read more >
Import Profile fails with error "Failed during Parsing record"
Resolution 1: Review the input file's extension (*.xml or *.mrc); Select Alma > Resources > Manage Import Profiles; Find the Import Profile ...
Read more >
Parse Error: What It Is and How to Fix It - Lifewire
Here are some of the most common causes of the Android parse error: The app is not compatible with your device.
Read more >
Common errors when using GROMACS
This error arises if the format of the gro file is broken in some way. The most common explanation is that the second...
Read more >
Chrome GPO Encountered an error while parsing
If an error occurs, it's usually because the files are in an incorrect location. Check the locations and confirm again.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found