-
Notifications
You must be signed in to change notification settings - Fork 116
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 requests if not already existing? #247
Comments
I don't understand what you mean by the first suggestion. For the second one, it can add hydrogens to ligands, but you need to give it some help to tell it where to add them. This cookbook entry describes how to do it. |
Yeah I understand the chain Termination but sometimes these TER have an |
The index numbers on TER records are actually required by the spec:
Don't ask me why they did it that way! But any program that can't deal with them is broken. |
Yea I know now that maybe since I was missing hydrogens on 5-FU plus I have crystal structure with 4 chains and 4 molecules of 5-FU that was probably the issue. Polytype2's |
Thanks for sending notes on xml for non-standard residues. I believe it worked |
I think pdbfixer will benefit from and I am willing to work on at least the first (the easier of the 2 😄 ) and eventually the second one if these don't already exist.
First:
Some PDB files may have a chain termination
TER
(see TER inChimera PDB Format
) atoms. Example 3NBQ.pdb. It would be great to 1) be able to remove these chain terminators since we don't simulate these and 2) to reindex the rest of the atoms ifTER
is numbered in the PDB files. Let me know where in the code this would be best or I can just find a nice place :) and I will create a pull request.Second:
It would also be great to be able to have hydrogens added to ligands as well since when running Tinker/Poltype2 we would want to model these in our simulations and the SDF/MOL2 files have hydrogens that we are optimizing in Poltype2. This might need import from openbabel.
Brian
The text was updated successfully, but these errors were encountered: