Open schmolly opened 3 years ago
Thanks for submitting this!
This code path still exists in the latest release (0.9.0), and is used unless we specify use_given_geometries=True
to RelativeFEPSetup
in that release. The code that fails here is trying to identify torsions in ring systems that should be used to add biasing potentials to ensure the rings will close. My guess is this can go wrong with complex multi-ring or bridged-ring systems.
Any chance you have a non-proprietary pair of compounds that could trigger this error?
I can confirm they have been multi-ring and/or bridged-ring systems. I don't currently have a share-able example, but I can probably generate a few if that would help.
I can confirm they have been multi-ring and/or bridged-ring systems. I don't currently have a share-able example, but I can probably generate a few if that would help.
Yes! It would be super helpful if you can come up with anything that shows the same behavior.
Here are a couple!
ClC1=CC=CC(=C1)C1=CC=CC=C1
CC1CC2CC2CC1C1=CC(Cl)=CC=C1
OC1CC2CCC1(C2)C1=CC(Cl)=CC=C1
You rock, @schmolly! Thanks so much---this is super helpful!
I've updated the issue with a more accurate description of what needs to be fixed.
@schmolly : Can you let us know whether this is a super high priority issue to include before we release 0.9.1, or whether we could include this fix in 0.10.0?
It's not super high priority
One of the recurring errors I've seen (using Perses 0.8.1, in my slightly janky Docker container)
Result: the atom mapping fails, and the edge does not run