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

Comet v2024.01.0 yields empty results when using 'peptide_mass_tolerance' #60

Closed
cbielow opened this issue Jul 2, 2024 · 3 comments
Closed

Comments

@cbielow
Copy link

cbielow commented Jul 2, 2024

The reason is basically rooted in #59.
When using peptide_mass_tolerance = 10 in the param.txt then Comet will use

10 to -10 as mass tolerance boundaries (which yields an empty result), instead of -10 to 10.

Quickfix: specify

peptide_mass_tolerance = -10

which will negate the bug (not the go-to solution though).

The fix is easy, and probably part of #59.

Regression tests are highly valuable here, since they would have caught this early on.

@jke000
Copy link
Collaborator

jke000 commented Jul 2, 2024

Thanks for reporting all of these issues. I just committed a fix to restore backwards support for the retired peptide_mass_tolerance parameter. It got broken with commit c238fec which addressed proper application of the _upper and _lower parameter settings. Backwards support of this retired parameter was not part of my set of tests that I run before release but I just added this to my test suite. And regression testing will hopefully make it into the code someday. I'm going to close this issue with this comment and commit but reply if I missed anything.

@jke000 jke000 closed this as completed Jul 2, 2024
@cbielow
Copy link
Author

cbielow commented Jul 3, 2024

thanks for fixing this so quickly.
This will go into the next Comet release, I assume?
In the meantime I will implement the negation hack into OpenMS if it detects Comet v2024.01.0, so users will not notice.

@jke000
Copy link
Collaborator

jke000 commented Jul 3, 2024

Yes, this fix will be in the next release.

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

2 participants