Different behaviour of molecules returned by RGroupDecompose between RDKit v2022.9.5 & 2023.3 #6861
Unanswered
LindeSchoenmaker
asked this question in
Show and tell
Replies: 1 comment 2 replies
-
I can't speak to the current change in behavior, however Chem.molzip was designed to recombine the results of a decomposition. There is one caveat that the Core must come first otherwise molzip gets confused. The one other change is that when using rdFMCS, the decomposition behaves better when using res.queryMol as opposed to res.smartsString. This simplifies your example to the following (similar to what we use in the FreeWilson contribution)
|
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am using rdkit to transfer R-groups from one molecule to another.
My workflow is as follows;
I noticed that the molecules returned by RGroupDecompose (I'm using asSmiles = False), behave differently between the different versions.
In version 2022.9.5 I'm able to add two R-groups to a positively charged primary amine (C[NH2+][*:1]). For version 2023.3 the same code leads to a valence error.
I noticed that the cores returned for v2022.9.5 are all identical, whereas for v2023.3 the number of explicit Hs in the SMILES is the same as for the parent molecule.
Below I put the code to reproduce my results.
I'm currently post-processing my molecules to fix the number of hydrogens by counting the number of bonds and comparing that to the allowed valence. However, it would be preferable if the change in returned molecules (from v.2023.3 onwards) could be prevented or the molecules could be transformed 'back' to what they were like in the earlier versions.
Beta Was this translation helpful? Give feedback.
All reactions