I am not sure if this is too much to ask you.
No, it's not; I always welcome user questions such as this one, and I strive to be as helpful as I could.
Now I see the problem you are experiencing. Strictly speaking, and as I mentioned in my previous reply, it's not a 3DNA problem but at the interface between 3DNA and Curves+. Since the purpose of providing the
find_pair c+ option is to build a bridge between the two commonly used software programs for analyzing nucleic acid structures, I'd like to dig the issue further to see if anything can be done from 3DNA's perspective.
Your Curves+ input file
curves.inp, as generated with
find_pair -c+, has the following content:
&inp file=sel.pdb,
lis=sel,
fit=.t.,
lib=./standard,
isym=1,
&end
2 1 -1 0 0
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25
which has 23 base pairs (note that bases 1 and 48 are not paired). Yet when the file is fed to Curves+, only the first 15 bps are recognized.
Combined strands have 15 levels ...
Strand 1 has 15 bases (5'-3'): GTGTGAGCGTGGGCG
Strand 2 has 15 bases (3'-5'): CACACTCGCACCCGC
To help solve the problem, could you try the following and report back (in detail) what you get?
Xiang-Jun