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

[BUG] Relaxation of DNA structures behaves differently between recent oxDNA versions and the old one on oxServe #63

Open
ErikPoppleton opened this issue Aug 21, 2023 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@ErikPoppleton
Copy link
Collaborator

Describe the bug
When pulling structures into desired starting configurations using mutual traps, the version of oxDNA running on the oxServe plugin of oxView is significantly more stable than the current version here (or this fork by @Jonahowns). I have not been able to successfully compile the old version used by oxServe for local testing (which is using code from this repository. I don't know the specific checkout, maybe @zoombya can double check?). This implies that one or more of the following is different between this older version of oxDNA and the current (post move to GitHub) implementations:

  • Mutual traps or external forces in general
  • FENE potentials
  • The way max_backbone_force and max_backbone_far work

To Reproduce
pull_test.zip
The attached zip file contains a simulation where this behavior occurs. This structure is stable with the default oxServe input file, but the very similar input file in the example will explode within the first 10000 steps if run on the current oxDNA. The structure can be made stable by decreasing the dt 10x and the max_backbone_force 100x.

Expected behavior
It would be nice to know what changed between the two versions. It would also be nice if the older oxDNA_anm version of relaxation turns out to be physically reasonable and the current behavior could be updated to match because it is much more successful at producing starting structures for simulations.

Desktop (please complete the following information):

  • OS: SUSE Linux Enterprise Server 15 SP4, MacOS 13.4.1
  • Tested with the latest version of the oat_dev branch (using new topology) and the latest version of oxpy_anm. I haven't been able to get it to compile on the server, but I think the latest version of anm-oxdna is close to what oxServe is running.
  • cmake/make/compiler versions - probably not relevant because the behavior is the same whether I use a GPU-compiled version on the server or the CPU-compiled one on my laptop.
@ErikPoppleton ErikPoppleton added the bug Something isn't working label Aug 21, 2023
@lorenzo-rovigatti
Copy link
Owner

I actually cannot reproduce this issue, since the latest oxDNA version and the one compiled from here give me very similar energies and similiar stretched configurations such as this one:
Screenshot_20230822_122541

@lorenzo-rovigatti lorenzo-rovigatti self-assigned this Aug 22, 2023
@lorenzo-rovigatti
Copy link
Owner

Erik, any news on this one?

@lorenzo-rovigatti
Copy link
Owner

@ErikPoppleton has this ever been understood, worked on or fixed?

@ErikPoppleton
Copy link
Collaborator Author

No, I haven't made any progress on understanding this one...

@zoombya
Copy link
Collaborator

zoombya commented Jul 26, 2024

in case we can allocate someone to this, we have to search for differences between the Nanobase ANM version and the recent github one.

@lorenzo-rovigatti
Copy link
Owner

I find this difference a bit unsettling, so let me know if you find some time to craft a minimal reproducible example that shows that there are striking differences between two oxDNA versions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants