Re: corrupted trajectory

From: CUI, Guanglei <>
Date: Tue 3 Dec 2002 21:04:13 -0500 (EST)

No, it's not the asterisks. Some frames were corrupted and became
shorter than what it should due to job crashes. It's too bad that AMBER
trajectory doesn't have a frame identifier or something like that.

On Tue, 3 Dec 2002, Bill Ross wrote:

> Probably write an awk or perl script that knows how many
> lines in a frame, checks for *'s if that's the problem,
> and writes the frame if there are none.
> Bill Ross

Guanglei Cui
Dept. of Chemistry
SUNY at Stony Brook
Stony Brook, NY 11790
Received on Tue Dec 03 2002 - 18:04:13 PST
Custom Search