You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
, which picks up the "SingleOrAromaticBond" queries between the aromatic atoms, so that the implicit valences for these atoms are set to 0, which causes problems in the detection of potentially aromatizable bonds.
I think we should either:
Add a check to KekulizeFragment() to fail / exit early if bond order queries are detected.
Make the code in markDbondCands() more flexible, at
My two cents on this, after a conversation with @ricrogz: We shouldn't be trying to kekulize query bonds.
The question is whether we should throw an execption (perhaps a ValueError since the input is not valid) or just ignore those bonds during kekulization
I was leaning towards the exception approach, but now favor ignoring them since I'm concerned that throwing an exception may be very disruptive.
There's cases in which doing this completely fails:
And other that succeed with only slight differences in the structure, although the result is nonsense (note the bond orders):
I think this is due to the code at
rdkit/Code/GraphMol/Atom.cpp
Line 448 in 0e7871d
I think we should either:
KekulizeFragment()
to fail / exit early if bond order queries are detected.markDbondCands()
more flexible, atrdkit/Code/GraphMol/Kekulize.cpp
Lines 205 to 208 in 0e7871d
The text was updated successfully, but these errors were encountered: