-
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
Bug: The residue order between the input all-atom model and the output coarse-grained model is different. #551
Comments
Hellohello! |
Yes, the output is given. And the number of residues is same. The mistake I find is that the order of residues in the output is different from the input atomic model. |
Have you repeated this bug? |
Sorry, I meant to ask if martinize2 prints anything to screen (and what). I haven't had time yet to run it myself, hopefully I can find some time tomorrow. |
OK. The output of martinize2 is the following lines.
|
Ok, it's awkward. For some reason your chain C (starting with resid 27) gets put in between your chain Bs. My initial suspicion was that the MergeAllMolecules processor was shuffling the order (for some reason). When I run Further digging revealed that there are 3 molecules: The last spans resids 854-1146; second resids 689-827; and the first 567-43 (!). So the first molecule contains chain C. I need to brood on this a bit more before I declare this a real bug. Maybe the real bug is actually in the atom sorting ( Either way, your atomistic structure is problematic |
Thank you for your reply. I find that it works well after the energy of the atomistic model is minimized. And it's true that there is some crash in the sidechains of my model. I think it will be much better if Martinize2 can give some warnings for these crash in the future. Thank you very much. |
Happy to hear things are working by now. We're in the progress of overhauling the whole Go flow (#550). Maybe that will improve matters a bit, but issuing warnings for clashes sounds like an excellent plan. |
I'm trying to create a coarse-grained model with an all-atom model. When I use the following command for coarse-graining,
martinize2 -f test_at.pdb -o system.top -x test_cg.pdb -dssp dssp -p backbone -ff martini3001 -govs-include -govs-moltype open -cys auto -scfix
the coarse-grained model I get has the different residue order when compared to the atomic model. It may be something wrong with the script processing the order of molecules, in which the script puts some molecules ahead with a mistake.
I have appended the all-atom model (test_at.pdb.txt) in this issue. The version of Vermouth I use is vermouth-0.9.7.dev4.
Hope you can repeat this bug.
All-atom model (part):
Coarse-grained model (part):
The text was updated successfully, but these errors were encountered: