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
Actual behavior
After automapping the reaction with automap("discard"), the oxygen atoms labeled as 9 and 12 in the reactants and product appear mismatched. Specifically:
Oxygen 9 in the reactant maps to 12 in the product.
Oxygen 12 in the reactant maps to 9 in the product.
This behavior can be visualized in the attached molecule images.
Expected behavior
Oxygen atoms in the reactants and product should retain consistent mapping based on chemical equivalence. Specifically:
Reactant oxygen labeled 9 should map to product oxygen 9.
Reactant oxygen labeled 12 should map to product oxygen 12.
Additional context
This issue could potentially impact downstream applications that rely on accurate atom mappings for reaction modeling. Could you confirm if this is expected behavior or a bug in the mapping logic?
TL;DR it is expected behavior the the atom mapping
TL;DR2 are you sure that disconnecting carbon chain is lower energy than disconnecting hydroxyl group - is your expected behavior is actually true in real chemistry?
Yes, it is expected behavior for the Atom mapping using MCSS algorithms. MCS - maximum common substructure approach tries to find maximum structure in both reactant and product, then "removes" it and continues to find other maximum parts until all atoms matched. In this case it finds this substructure first
Then this one
So basically - the reaction just disconnect one hydroxyl group and connects to other. One should not look at atom number (it is just taken from the input order) but look at bond connections.
Yes MCSS algorithm can be not perfect in some cases but in this case I don't understand how do you expect that 9th oxygen matches to 12 - it means that one should remove a carbon in between? And that is I don't sure how what is more possible (in terms of atom electronegativities, covalent bonds stabilities, etc) unless you know exactly how this reaction should be processed
Summary
Automapping of a reaction using the Indigo library appears to mismatch oxygen atom labels (9 and 12) between the reactants and product.
Steps to Reproduce
Actual behavior
After automapping the reaction with automap("discard"), the oxygen atoms labeled as 9 and 12 in the reactants and product appear mismatched. Specifically:
This behavior can be visualized in the attached molecule images.
Expected behavior
Oxygen atoms in the reactants and product should retain consistent mapping based on chemical equivalence. Specifically:
Environment details:
Attachments
Additional context
This issue could potentially impact downstream applications that rely on accurate atom mappings for reaction modeling. Could you confirm if this is expected behavior or a bug in the mapping logic?
cc @ben-ikt
The text was updated successfully, but these errors were encountered: