-
Notifications
You must be signed in to change notification settings - Fork 46
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
Enhancement: Leave structural ions in file #534
Comments
Oh, maybe this can just be done with the -ignore flag according #74. Sorry if that is the case. |
Hmmn I can't reproduce this I think. On the master branch we don't drop/ignore any residues by default. I'm not sure how to improve the |
@KasperBuskPedersen do you want to keep the ions in the output? We could do this quite easily if the mapping files are provided. That's something you could even do yourself and the contribute to martinize2. ;) |
@fgrunewald Yes exactly, and maybe some control over which should stay (i dont know how this would be best done). All the common structural ions will just be a 1-1 mapping to either a Q or D bead, so super simple. I'll note it down for when im done with the PhD and i might come back. Cheers |
Hello, Has anyone thought more about this issue? I have several structural ions in my protein, but I'm not sure how to adjust the positions of the CG ions. I have some calcium ions that are being coordinated. Is there a strategy to try to maintain that coordination in Martini3? |
Not actively. I'm not sure what the state of the model is in this regard (I'm not part of the Marrink lab any more :'( ), but I am pretty sure we don't have the mapping files yet. PR welcome! :) |
Dear Martinize2 devs
Structural ions are quite common, however martinize2 currently deletes all ions from the input pdb so the user need to add them back in.
A nice quality of life fix would be to detect ions in the input file and just leave them be in the output or have a flag that toggle this behavior if the current is intended.
Best regards
Kasper
The text was updated successfully, but these errors were encountered: