-
Notifications
You must be signed in to change notification settings - Fork 7
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
Open Search for TMT16/TMT18-plex with Extended Precursor Mass Range (lower than -230 Da, higher than 600 Da) #340
Comments
No, it is hardcoded to make the PeptideProphet modeling more stable. Best, Fengchao |
You can change from PeptideProphet to Percolator, and then change from -230 to 350. But results will be noisier because Percolator is not controlling the error rates for open search that well. But if you just want to see the most common mass shifts, that should be fine. |
Thank you for your quick response, Fengchao and Alexey Nesvizhskii. The issue lies within the search engine, as we are running MSFragger via the command line. After this, we use post-processing programs to model the modifications. Therefore, we need to extend the range of precursor masses directly in MSFragger. Best regards, |
Fengchao, did we hardcode it in MSFragger? If so we should change. I think setting -230 in FragPipe is sufficient by default, without hardcoding |
Yes, we hardcoded it in MSFragger. I will remove it in the next release. Best, Fengchao |
Thank you for your consideration, Fengchao and Alexey Nesvizhskii. Best Regards, |
Hi Fengchao, BTW, do you know when the release with this update will be available? Thanks in adavance! Best, |
We plan to release it soon. I have replied your email. Best, Fengchao |
Hello everyone,
We are trying to perform an open search for TMT18-plex, but we have encountered an issue: the lower bound of the precursor mass window is limited to -230 Da.
Is there any way to perform an open search with a precursor mass range of -350 Da to 600 Da?
Thank you in advance for your assistance.
Best regards,
J
The text was updated successfully, but these errors were encountered: