Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

External forces inconsistent with Create from base pairs #87

Open
RodenLuo opened this issue Sep 17, 2022 · 3 comments
Open

External forces inconsistent with Create from base pairs #87

RodenLuo opened this issue Sep 17, 2022 · 3 comments

Comments

@RodenLuo
Copy link

Hi,

I used tacoxDNA/src/cadnano_oxDNA.py 7_icosahedron.json he -o to generate a 7_icosahedron.json.oxview file (attached below). Drag and drop it into oxview, and then Dynamics -> Forces -> Create from base pairs, the window shows the correct base pairs. However, if I File -> Save -> External forces, I get totally different base pairs. Could you please take a look?

7_icosahedron.json.oxview

image

@zoombya
Copy link
Collaborator

zoombya commented Sep 19, 2022

Hi Roden, my best guess for your problem is that you changed smth in the scene,
like nicking or ligating. This changes the strand length and we need to generate all indices new
because of that. This is done in oxview when you do the export to oxDNA configurations.
I just tried to load the example icosahedron and reproduce the issue and for me the indices are the same.
Could you please try again ?

@RodenLuo
Copy link
Author

Hi Michael, Thanks! I tried just now on both Win10 and Mac chrome. The problem still exists. I did not do anything after drag and drop the .oxview file I attached in the original post before the screenshot. The base pairs info is already in the oxview file (generated by the tacoxdna converter), so I did not even use any findBasePairs func.

@RodenLuo
Copy link
Author

If I load oxdna-viewer/tree/master/examples/icosahedron, and then do the following, it is indeed consistent. I didn't choose this way in the first place because this method has given me none-complete base pairs in a few cases before.

Is what shown in the screenshot the "findBasePairs" you mentioned in the other thread?

Snipaste_2022-09-19_23-09-33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants