-
Notifications
You must be signed in to change notification settings - Fork 71
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
Setup will fail if .mol2 atom substructure ID matches filename #703
Comments
Thanks! @andrrizzi : Can you take a look at this at some point? |
Sure! I'll punt it for post-1.0 release if this is not urgent (feel free to change the issue tag). |
Okay, to shine some more light on this, it turns out that if the molecule name in the e.g. Considering we dont really use the molecule name beyond just ID'ing it, its a pretty easy work around. Why its doing this, I don't know. |
I actually fixed this case in #465 with the addition of the |
Leap may also have problems with residue names that start/contain a digit. |
DOES have such problems. |
Can't we just temporarily rename the ligand residue when feeding it into Antechamber/LEAP? |
We can definitely change it, but I'm not sure we can do it temporarily unless we modify the |
Where precisely are things going wrong? Are we somehow generating an MDTraj or OpenMM |
I believe it's this. |
What if we
The residue name in the prmtop file doesn't matter, since we don't use that for anything---it's just the PDB files generated from that we end up using for DSL searches, analysis, etc. |
We do actually because at the moment we use that topology for all the DSL expressions we have in the YAML file (e.g., ligand_DSL, receptor/ligand atoms for restraints). We would have to switch to a system where we read the system from the |
I see---the problem is that we create the
|
This is very likely a niche issue (my very sloppy work found this error), but it may be worth sanitizing .mol2 files during setup--
If the substructure id for a atom in a mol2 file matches the filename, e.g.
Then setup will fail with the following:
This occurs with the following:
The text was updated successfully, but these errors were encountered: