On Thu, 2015-01-15 at 12:19 +0330, Atila Petrosian wrote:
> Dear amber users
> After heating, when I saw heat.mdcrd file using VMD, unfortunately, I
> encountered with unusual structure (please note the figure in the following
> link: (https://www.dropbox.com/s/tlsmhoaflpftzgc/b.png?dl=0).
>
>
> What is the reason of this issue?
This is caused by loading the mdcrd file as an "Amber Coordinates"
instead of "Amber Coordinates with box".
See the discussion in the 2nd basic tutorial (on VMD):
http://ambermd.org/tutorials/basic/tutorial2/section6.htm
> I am beginner in amber, please help me to resolve this problem.
Then I will make another suggestion. Set the input variable "ioutfm=1"
in the &cntrl section of the sander/pmemd input file. This will cause
the trajectories to be written in "NetCDF" format. These files are
better than ASCII trajectories in almost every way:
1. They are smaller than ASCII trajectories and take up less space
2. They store coordinates with much higher precision
3. They read (and write) MUCH faster
4. They are more fault-tolerant if a frame is corrupted
5. They are extensible
So there is only one "Amber NetCDF trajectory" format in VMD (since it
is easy to determine whether box information is present or not without
needing to tell VMD so).
Hope this helps,
Jason
--
Jason M. Swails
BioMaPS,
Rutgers University
Postdoctoral Researcher
_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Thu Jan 15 2015 - 05:00:03 PST
