Thanks a lot for your very fast reply!
To investigate this issue further, could you elaborate on how you calculated the backbone parameters using do_x3dna? Does do_x3dna call the 'analyze -t' (for torsion angles) option?
I do run do_x3dna on a native RNA (no abasic site) trajectory with
do_x3dna -f ../mod.pdb -s ../mod.pdb -o test -hbond
and extract the dihedral information from "BackBoneCHiDihedrals_g.dat"
To investigate this further, I started the analysis an hour ago and 53,000 frames are currently analyzed with do_x3dna.
In contrast, I run DSSR now with the latest version (downloaded today) on the same pdb-trajectory with
x3dna-dssr -i=mod.pdb -o=output.json --more --json --nmr
and currently it runs for frame 2,100.
Based on my impression, DSSR and do_x3dna are approx. similar in analyzing the first ~1000 structures and DSSR gets slower and slower with every following structure.
As a workaround, I could cut my trajectory into 1000 structure fragments and analyze them independently, but I think the performance issue is important especially for the MD community to work with DSSR.
For your second question, what version of DSSR were you using? This bug should have been fixed in the later releases of DSSR, as shown below:
Processing file 'frame1630.pdb'
X.U.7 0.121
X.U.42 0.143
total number of nucleotides: 44
total number of base pairs: 20
total number of helices: 1
total number of stems: 3
total number of internal loops: 2
Also, note that you do not need to specify the --abasic option anymore. This feature is taken into consideration by default in recent releases of DSSR.
Thank you very much. Indeed, I was using an older version of DSSR and it seems to work with your latest version (frame 1630 does not crash). And thank you for the hint with the default --abasic command. I just followed the manual to this:
http://x3dna.org/articles/handling-of-abasic-sites-in-dssrBest,
Marcel