Re: [AMBER] Different print behavior for mdcrd and ncsu modules

From: David A Case <case.biomaps.rutgers.edu>
Date: Thu, 10 Nov 2011 11:22:19 -0500

On Wed, Nov 09, 2011, Brian Radak wrote:
>
> - sander begins writing trajectory frames after ntwx steps, that is:
> frame1 = ntwx and frameN = nstlim for a total of N = (nstlim/ntwx) frames
> (assuming nstlim mod ntwx = 0)
> - the NCSU modules begin writing frames immediately, that is: frame1 = 0
> and frameN = (nstlim - output_freq) for the same total of N steps (assuming
> ntwx = output_freq)

Sounds like we ought to modify the NCSU stuff to print frames more like
what sander's mdcrd output does.

....dac


_______________________________________________
AMBER mailing list
AMBER.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber
Received on Thu Nov 10 2011 - 08:30:07 PST
Custom Search