I can confirm that this patch fixes 'average' for me. Thanks very much!
--Tom
2010/4/16 Daniel Roe <daniel.r.roe.gmail.com>:
> The weird behavior with the average command has to do with the new paradigm
> of setting the trajectory stop value to -1 when the total number of frames
> is unknown. After processing coordinates, the actual number of frames read
> was not being passed to actions (so this bug may have been affecting more
> than just the average command). Anyway, I've attached a patch that updates
> each action with the total number of frames read. Patch works on both
> current RC and AmberTools-1.3 versions of ptraj.c, so it can be used as a
> bugfix. Patch as is needs to be applied in the /src/ptraj/ directory.
>
> -Dan
_______________________________________________
AMBER-Developers mailing list
AMBER-Developers.ambermd.org
http://lists.ambermd.org/mailman/listinfo/amber-developers
Received on Fri Apr 16 2010 - 15:00:04 PDT