Replies: 1 comment
-
|
Hi @ldx022, you should be able to pair any topology format with any trajectory format basically, with the only constraint that the number of particles in each matches. For your use case (sounds like you used GROMACS) using a .gro and a .xtc file sounds like a good option. MDAnalysis does read .xtc files. The topology parsing from a import MDAnalysis as mda
u = mda.Universe("system.gro", "trajectory.xtc")should work. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone!
I've encountered some issues while processing my coarse-grained system with MDAnalysis. In general, my system is quite unique, not a very standard MD system, but a coarse-grained system I built manually. Overall, this system's topology files include only
.top,.gro, and.psffiles. However, I previously tried reading the.topformat topology file with MDAnalysis and failed (I guess it might be due to non-standard amino acid names?). The.psffile seems like doesn't pair with the.xtctrajectory (although in VMD, the.xtctrajectory can load the.psftopology file for visualization, but not in MDAnalysis), so only.grois used as the topology file. Could you please tell me MDAnalysis reads.xtctrajectories, what would be the most appropriate format for the accompanying topology file? How can MDAnalysis be used to solve problems like the ones I'm experiencing?Beta Was this translation helpful? Give feedback.
All reactions