From: Harish Srinivasan (harishlglk1992_at_gmail.com)
Date: Mon Dec 26 2016 - 23:44:52 CST
Sorry, forgot to attach a link. Here you go
<goog_2082149595>
http://www.ks.uiuc.edu/Development/MDTools/flipdcd/
Regards
On 27 December 2016 at 11:14, Harish Srinivasan <harishlglk1992_at_gmail.com>
wrote:
> Hi,
>
> Did you try to find the endianness (little and big) of the DCD file. Use
> flipdcd program (available in the NAMD exectuable folder) to check this.
> The same program will also help you in changing from big to little and vice
> versa.
>
> Regards
> Harish
>
>
> On 26 December 2016 at 10:48, Amit Kumar <amit.bio_at_iitg.ernet.in> wrote:
>
>> Hi,
>>
>> I am using NAMD in two different machines. I am not able to analyze
>> Trajectory files (dcd) generated by one machine while Trajectory files
>> generated by other machine are working fine. So, what can be the problem ?
>> Note: Using same software (NMAD), same script, only machines are
>> different.
>>
>> Thank you very much.
>>
>> Amit Kumar
>>
>>
>
This archive was generated by hypermail 2.1.6 : Sun Dec 31 2017 - 23:20:55 CST