This email has been sent before on the mailing list but I couldn’t reply, so I wrote the complete question again, sorry for that.
I want to visualize the initial structure and also the structures between the different simulation steps to know if anything wrong happened. I can’t visualize my structure after the energy minimization due to the PBC. I know how to solve that at the end after finishing the simulation using the below commands
gmx trjconv -s md_0_1.tpr -f md_0_1.xtc -o md_noPBC.xtc -pbc mol
mx trjconv -s md_0_1.tpr -f md_noPBC.xtc -o md_noPBC.pdbds:
Justin has replied previously that “Trajectories” from energy minimization are generally unreadable as the interval of saved frames is uneven. Is there another way to solve or visualize my structure without the PBC after the energy minimization without the trajectories ?
I have attached below an image of my structure after the energy minimization with the PBC.
What do you mean you can’t visualise it? Why not?
If it is simply because the movement of molecules/atoms across the PBC have made it difficult to see what you want, then simply recenter as appropriate and make sure all molecules are whole again.
Note that PBC means that if something leaves say the left hand face of the simulation box, then it then enters in the right hand side and you essentially have an infinite system. Because of this where the “box” is “drawn” when you visualise it is entirely arbitrary. So you adjust things as you see fit to give the visualisation you required.
Also see http://manual.gromacs.org/documentation/current/user-guide/terminology.html#gmx-pbc
Thanks for your reply :)
Yes, my problem is that the molecules are not whole and parts of the substrate have been moved from the bottom to the top as in the image I have attached and as your description.
How can I solve these problem after the energy minimization if I don’t have the .xtc file ? Is there another way to fix them without using the .xtc file ?
You don’t need a trajectory file, gmx trjconv will run fine on coordination files too.
It worked with the .gro file. Many thanks :)