Date: Thu Jun 14 2012 - 06:30:48 CDT
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
Thanks in advance for your reply.
This archive was generated by hypermail 2.1.6 : Mon Dec 31 2012 - 23:21:39 CST