Previous Thread
Next Thread
Print Thread
Page 2 of 2 1 2
Joined: Jun 2007
Posts: 17
S
Forum Member
Offline
Forum Member
S
Joined: Jun 2007
Posts: 17
I would like to know, weather I can use above script for truncated octahedren box or not. If not what are the changes should I make in the script. My second question is " what does this "good estimate of Dtransl" means or what is the range of good estimate."

I will really appreciate if some one can help me.

Joined: Sep 2003
Posts: 4,883
Likes: 12
lennart Offline OP
Forum Member
OP Offline
Forum Member
Joined: Sep 2003
Posts: 4,883
Likes: 12
Sorry, truncated octahedron is also not directly supported by this code. See previous posts in this thread for suggestions what to do.
"good" means to within a few percent of the value that would be obtained using much longer times for the fit of the straight line to the MSD(t) curve.


Lennart Nilsson
Karolinska Institutet
Stockholm, Sweden
Joined: Dec 2007
Posts: 10
Forum Member
Offline
Forum Member
Joined: Dec 2007
Posts: 10
Dear all,

I am sorry that my question repeats something that was already wrote in a post above concerning the calculation of water diffusion coefficient based on MSD using coor anal command, but I am having trouble understanding the connection between the:
- number of frames of a trajectory,
- the frequency of saving coordinates in the trajectory,
- the timestep used in the dynamics simulation,
- the skip value used when reading the trajectory in coor anal command and
- ncors value in coor anal.
Are there any guidelines on selecting skip and ncors values depending on the analyzed trajectory features mentioned above (timestep, frequency of saving coordinates, number of frames of the analyzed trajectory)?
Thank you!

Joined: Sep 2003
Posts: 4,883
Likes: 12
lennart Offline OP
Forum Member
OP Offline
Forum Member
Joined: Sep 2003
Posts: 4,883
Likes: 12
A trajectory of 1 ns simulated with a 2 fs time step, and with coordinates saved every 500 steps (NSAVC 500 in the dynamics command) will contain 1000 frames (1000*0.002ps*500=1000ps=1ns).
If you read this trajectory with NSKIP 2500 only every fifth frame (ie, every 5ps) will be read.
NCORS is the number of points in the MSD(t) curve.

For the above trajectory the NCORS 100 and NSKIP 1000 would compute MSD(t) from t=0 to t= 100 * 1000 * 0.002ps=200ps

You have to compute MSD(t) to a large enough t that you clearly see the linear part. Using a small NSKIP increases the computational time, but this is usually not a problem.


Lennart Nilsson
Karolinska Institutet
Stockholm, Sweden
Joined: Dec 2007
Posts: 10
Forum Member
Offline
Forum Member
Joined: Dec 2007
Posts: 10
Dear Sir,

Thank you for your answer, I hope I understand it now.
I calculated the MSD for the same trajectory using different combinations of ncors and nskip, each time charmm gives a different estimate of diffusion coefficient, of the order E00 to E-06, and even negative values. I want to ask how reliable this estimation is, or maybe I should plot the data and do the linear fit myself.
I attached such a plot of MSD vs time and the plot is not that linear. Do you think it looks OK? Should I fit only the first 10 ps? In any way I fit it, I can not reproduce the estimated diffusion coefficient from charmm output.
I would be very grateful if you could help me on this matter.

Attached Images
Graph2.jpg (356.01 KB, 490 downloads)
Joined: Sep 2003
Posts: 4,883
Likes: 12
lennart Offline OP
Forum Member
OP Offline
Forum Member
Joined: Sep 2003
Posts: 4,883
Likes: 12
You should of course do the fit yourself, especially with curve like the one in the graph you attached, which does look a bit strange.
Try to reproduce some published diffusion coefficient calculation for a box of water.

Last edited by lennart; 06/12/18 02:47 PM.

Lennart Nilsson
Karolinska Institutet
Stockholm, Sweden
Page 2 of 2 1 2

Moderated by  lennart, rmv 

Link Copied to Clipboard
Powered by UBB.threads™ PHP Forum Software 7.7.5
(Release build 20201027)
Responsive Width:

PHP: 7.3.31-1~deb10u5 Page Time: 0.015s Queries: 27 (0.011s) Memory: 0.7614 MB (Peak: 0.8376 MB) Data Comp: Off Server Time: 2023-12-03 00:42:04 UTC
Valid HTML 5 and Valid CSS