Improve ring-break merge detection and expose RDKit MCS kwargs - #542
Merged
Conversation
lohedges
temporarily deployed
to
biosimspace-build
July 29, 2026 17:06 — with
GitHub Actions
Inactive
lohedges
temporarily deployed
to
biosimspace-build
July 29, 2026 17:06 — with
GitHub Actions
Inactive
lohedges
temporarily deployed
to
biosimspace-build
July 29, 2026 17:06 — with
GitHub Actions
Inactive
lohedges
temporarily deployed
to
biosimspace-build
July 29, 2026 17:06 — with
GitHub Actions
Inactive
lohedges
temporarily deployed
to
biosimspace-build
July 29, 2026 17:06 — with
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR fixes a small issue with the ring-break merge detection code where changes in unrelated rings triggered a ring-break warning, i.e. removing one ring and growing another.
The PR also exposes a new
mcs_kwargsoption, allowing the user to tune the options used for the underlying RDKit MCS search. This is useful for certain perturbations, where the defaultFESetup-inspired options are not ideal. I've also added a function to expose the default options such that a user can use these as a base, or compare with them. Previously this was hidden internally, so a user wouldn't actually know what was set.develinto this branch before issuing this pull request (e.g. by runninggit pull origin devel): [y]