i would suggest you could just run the trajectory through moil-view to
find out where moil-view stops due to corrupted frame or something like
that. and it's gonna be visualized where thing goes wrong... good luck..
yan
On 3 Dec 2002, Guanglei Cui wrote:
> Dear AMBER experts,
> I have a corrupted trajectory file. Possibly one or two frames in
> the middle were not written properly. Is there a way (fast and
> efficient) to pick out (delete) bad frames from thousands? Thanks for
> any suggestions.
>
> Regards,
>
> --
> Guanglei Cui <cuigl_at_morita.chem.sunysb.edu>
> SUNY at Stony Brook
>
Received on Tue Dec 03 2002 - 15:36:37 PST
