Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--smallest-transformation-only doesn't work for some transformations #20

Open
mahendra-awale opened this issue Nov 4, 2019 · 0 comments

Comments

@mahendra-awale
Copy link

A "--smallest-transformation-only" option doesn't produce desirable result with some transformations. It seems that there is conflict between --smallest-transformation-only option (use during indexing) with --min-heavies-per-const-frag option (use during fragmentation)

For example, if one considers this transformation [:1]C(=O)Nc1ccccc1>>[:1]C(=O)Nc1cccnc1, it is clearly reducible to [:1]c1ccccc1>>[:1]c1cccnc1.

However, if someone sets the option --min-heavies-per-const-frag == 9 (during fragmentation step), then the output is [:1]C(=O)Nc1ccccc1>>[:1]C(=O)Nc1cccnc1 and not the [:1]c1ccccc1>>[:1]c1cccnc1.

This is possibly because, a number of heavy atoms in fragment [:1]C(=O)Nc1ccccc1 (or [:1]C(=O)Nc1cccnc1) <=min-heavies-per-const-frag and hence there is no further fragmentation possible for this fragments and hence it's not reducible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant