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

Alternatives for GROMACS output files #73

Open
fidelrmz opened this issue Nov 22, 2020 · 1 comment
Open

Alternatives for GROMACS output files #73

fidelrmz opened this issue Nov 22, 2020 · 1 comment

Comments

@fidelrmz
Copy link

Hi!
I have recently installed PyContact to analyze some trajectories performed with GROMACS. However, I am aware neither topology nor trajectory output files obtained with GROMACS have any defined segment ID (segid) to use for selection in PyContact (already checked by MDAnalysis). Tried transforming .gro to .pdb files in order to attempt using chains ID but eventually failed. After some reading I found VMD is a possible solution through psfgen but also failed due to an 'apparently not so uncommon' error while running and which has also been reported in VMD's mailing-list for a long time. Anyway, I was wondering if maybe there is any other alternative for selection data to evaluate GROMACS trajectory files with PyContact since looks like the precise tool for what I need right now. Thank you in advance!

@maxscheurer
Copy link
Owner

Hi,
yeah this is a common problem I've encountered as well 😦
Except for making use of the existing MDAnalysis selection language, I have no other alternative in mind.

About the conversion: maybe it could work with parmed?

I think in the long run it would be best to be able to load pure pdb trajectories into PyContact, but I won't have time to implement that in the near future...

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

2 participants