-
Notifications
You must be signed in to change notification settings - Fork 845
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
ResonanceMolSupplier potentially stuck in infinite loop #2597
Comments
I'm going to label this as a bug, there should be some max number of resonance structures to prevent this behavior. This might take some time to resolve, however. |
Here is a more detailed reason why I consider this a bug:
This code hangs in that the user can't terminate after, say, 1000 structures are generated. |
it's true that a limit can be useful to avoid infinite loops |
@ptosco : I just noticed that this is still here and seems to still be a problem.
Trying with the SMILES Is this something you'd be able to look at? |
@greglandrum Yes, I'll try and take a look over the weekend. |
maybe also a memory leak somewhere ? |
- adds support for C++ and Python callbacks to monitor progress - cumulated bonds should not appear in rings - UNCONSTRAINED_CATIONS now implies ALLOW_CHARGE_SEPARATION and ALLOW_INCOMPLETE_OCTETS as it should already have - UNCONSTRAINED_ANIONS now implies ALLOW_CHARGE_SEPARATION as it should already have
* - major refactoring (fixes #2597) - adds support for C++ and Python callbacks to monitor progress - cumulated bonds should not appear in rings - UNCONSTRAINED_CATIONS now implies ALLOW_CHARGE_SEPARATION and ALLOW_INCOMPLETE_OCTETS as it should already have - UNCONSTRAINED_ANIONS now implies ALLOW_CHARGE_SEPARATION as it should already have * removed spurious debugging messag * changes in response to review
Description:
ResonanceMolSupplier takes an extremely long time (or possibly is stuck in an infinite loop) when trying to process the Mol object with SMILES string
ClC1=NC(NC2=CC=CC3=C2C(=O)C2=CC=CC=C2C3=O)=NC(NC2=CC=CC3=C2C(=O)C2=CC=CC=C2C3=O)=N1
The text was updated successfully, but these errors were encountered: