1
MD simulations / Re: Failed Downloading MD Ruby Scripts of 3DNA
« on: September 16, 2020, 09:22:21 am »
Hi Xiang-jun,
Sorry for the late post. I was doing some other things and also understanding the usage of DSSR last week.
I am glad that I found out a way to apply DSSR on my trajectory without taking too much space.
The protocol is:
1. Divide the whole trajectory into let's say 1000 parts, and I would like to have 100 frames in one trajectory file. In my case, the simulation already divided the entire trajectory into small sections.
2. Use cpptraj to convert a single trajectory file into PDB file. Here, I only focus on DNA so I strip water and ions.
3. Run DSSR like
4. Following the manual, I used jq tool to extract information from the json file I got on step 3. E.g.
5. Repeat the steps 2 to 4, and then I can retrieve helical axis information of the whole trajectory. Then I just need to concatenate them. Just make sure I only keep the useful files during the iteration so that I would not occupy too much space.
Meanwhile, I notice that, when numbering the stems, I guess the program number the stems by their residue number (from 5' to 3'), namely, the helix with smaller resid at 5' side will be numbered first... Is this correct?
Thanks so much:)
Best regards,
Moi
Sorry for the late post. I was doing some other things and also understanding the usage of DSSR last week.
I am glad that I found out a way to apply DSSR on my trajectory without taking too much space.
The protocol is:
1. Divide the whole trajectory into let's say 1000 parts, and I would like to have 100 frames in one trajectory file. In my case, the simulation already divided the entire trajectory into small sections.
2. Use cpptraj to convert a single trajectory file into PDB file. Here, I only focus on DNA so I strip water and ions.
3. Run DSSR like
Code: [Select]
x3dna-dssr -i=production500.pdb -o=pro500.json --more --nmr --json
. Like what you suggested, I use json output here.4. Following the manual, I used jq tool to extract information from the json file I got on step 3. E.g.
Code: [Select]
jq '.models | .[] | .parameters.stems | .[] | {stem: .index, helical_direction: .helical_axis}’ <json file>
.5. Repeat the steps 2 to 4, and then I can retrieve helical axis information of the whole trajectory. Then I just need to concatenate them. Just make sure I only keep the useful files during the iteration so that I would not occupy too much space.
Meanwhile, I notice that, when numbering the stems, I guess the program number the stems by their residue number (from 5' to 3'), namely, the helix with smaller resid at 5' side will be numbered first... Is this correct?
Thanks so much:)
Best regards,
Moi