From: Joshua D. Moore (joshuadmoore_at_gmail.com)
Date: Thu Jun 14 2012 - 13:39:52 CDT
According to the website
http://www.ks.uiuc.edu/Development/MDTools/flipdcd/
"This conversion is not reversible so you may wish to make a backup
copy of your file(s)."
VMD can read either endiness now on any endiness machine, so unless
you are trying to read the file with your home grown code, I'm not
sure why you even need to use flipdcd anymore?
On Thu, Jun 14, 2012 at 7:30 AM, <peter.schmidtke_at_fr.netgrs.com> wrote:
> Dear NAMD mailing list readers,
>
>
>
> I’m experiencing some problems with flipping endianess of my trajectories
> (32 bit DCD format written by NAMD 2.9 CUDA in little endian) using the
> flipdcd program coming with the NAMD binaries.
>
> When I do the flipdcd going to big endian and back again to little and so
> on, after some time my trajectory file gets corrupted (VMD can only read
> some frames in the beginning, but not the end anymore). It’s mostly the end
> of the trajectory that becomes “unreadable”.
>
>
>
> Are these issues known using flipdcd? My dcd files are 2.1Gb big, by the
> way.
>
>
>
> Thanks in advance for your reply.
>
>
>
> Best regards.
>
>
>
> Peter Schmidtke
This archive was generated by hypermail 2.1.6 : Tue Dec 31 2013 - 23:22:07 CST