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
I noticed an interesting stereo-related issue when neutralizing a protonated atom, specifically when the atom continues to be a chiral center after the hydrogen is removed and the charge reduced.
mol1 is the neutral molecule and mol2 is a different protomer where the bridgehead nitrogen has a positive charge and an additional hydrogen. If we remove the hydrogen and reduce the formal charge, [N@@H+] has changed to [N@] in the resulting SMILES.
In this specific case, I know I can "fix" this by manually flipping CHI_TETRAHEDRAL_CCW to CHI_TETRAHEDRAL_CW, but I don't understand enough about how the CW/CCW accounting works for trivalent bridgehead nitrogens (for either the RDKit ChiralTag or the SMILES @/@@) to know if this is generally what should always be done.
I'm opening this as a bug report issue rather than a discussion because I think this situation may not be handled correctly internally to rdMolHash HetAtomTautomer/HetAtomProtomer and within the rdMolStandardize Uncharger:
Describe the bug
I noticed an interesting stereo-related issue when neutralizing a protonated atom, specifically when the atom continues to be a chiral center after the hydrogen is removed and the charge reduced.
To Reproduce
Taking quinine as an example molecule:
mol1
is the neutral molecule andmol2
is a different protomer where the bridgehead nitrogen has a positive charge and an additional hydrogen. If we remove the hydrogen and reduce the formal charge,[N@@H+]
has changed to[N@]
in the resulting SMILES.In this specific case, I know I can "fix" this by manually flipping
CHI_TETRAHEDRAL_CCW
toCHI_TETRAHEDRAL_CW
, but I don't understand enough about how the CW/CCW accounting works for trivalent bridgehead nitrogens (for either the RDKit ChiralTag or the SMILES@
/@@
) to know if this is generally what should always be done.I'm opening this as a bug report issue rather than a discussion because I think this situation may not be handled correctly internally to rdMolHash HetAtomTautomer/HetAtomProtomer and within the rdMolStandardize Uncharger:
Expected behavior
rdMolHash and Uncharger should give the same output for
mol1
andmol2
.Screenshots
Configuration (please complete the following information):
The text was updated successfully, but these errors were encountered: