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

Enhancement: Leave structural ions in file #534

Open
KasperBuskPedersen opened this issue Aug 7, 2023 · 6 comments
Open

Enhancement: Leave structural ions in file #534

KasperBuskPedersen opened this issue Aug 7, 2023 · 6 comments

Comments

@KasperBuskPedersen
Copy link

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

@KasperBuskPedersen
Copy link
Author

Oh, maybe this can just be done with the -ignore flag according #74. Sorry if that is the case.
Could possibly add a little more text to the -h documentation about this :)
Cheers
Kasper

@pckroon
Copy link
Member

pckroon commented Aug 14, 2023

Hmmn I can't reproduce this I think. On the master branch we don't drop/ignore any residues by default.
Running martinize2 -f 1ubq.pdb produces a lot (116) of warning about the HOH residues for which no datafiles are available. So to preserve the ions and solvent you'd need to add the data files (as if adding a new residue). The mapping to Martini is going to be hard/impossible though, since multiple molecules will correspond to one bead... I played around with it, but never finished anything along those lines.

I'm not sure how to improve the --help message, I'm open to suggestions.

@fgrunewald
Copy link
Member

@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. ;)

@KasperBuskPedersen
Copy link
Author

@fgrunewald Yes exactly, and maybe some control over which should stay (i dont know how this would be best done).
For example, you demonstrated a high-througput set up in the martinize2 pre-print where you could (in principle) simulate thousands of proteins. However, so many would have structural ions, which means that a large part of those simulations would be possible wrong without having these crucial ions - it is only because that elastic networks hide these problems right now, but with increased accuracy in the protein model, these things will eventually show.

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
Kasper

@yummy-hat
Copy link

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?

@pckroon
Copy link
Member

pckroon commented Dec 13, 2023

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! :)

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

No branches or pull requests

4 participants