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

Open Search for TMT16/TMT18-plex with Extended Precursor Mass Range (lower than -230 Da, higher than 600 Da) #340

Open
jmrodriguezc opened this issue Dec 16, 2024 · 8 comments
Assignees

Comments

@jmrodriguezc
Copy link

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

@fcyu fcyu self-assigned this Dec 16, 2024
@fcyu
Copy link
Member

fcyu commented Dec 16, 2024

No, it is hardcoded to make the PeptideProphet modeling more stable.

Best,

Fengchao

@anesvi
Copy link
Collaborator

anesvi commented Dec 16, 2024

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.

@jmrodriguezc
Copy link
Author

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,
J

@anesvi
Copy link
Collaborator

anesvi commented Dec 16, 2024

Fengchao, did we hardcode it in MSFragger? If so we should change. I think setting -230 in FragPipe is sufficient by default, without hardcoding

@fcyu
Copy link
Member

fcyu commented Dec 16, 2024

Yes, we hardcoded it in MSFragger. I will remove it in the next release.

Best,

Fengchao

@jmrodriguezc
Copy link
Author

Thank you for your consideration, Fengchao and Alexey Nesvizhskii.

Best Regards,
J

@jmrodriguezc
Copy link
Author

Hi Fengchao,

BTW, do you know when the release with this update will be available?

Thanks in adavance!

Best,
J

@fcyu
Copy link
Member

fcyu commented Dec 17, 2024

We plan to release it soon. I have replied your email.

Best,

Fengchao

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

3 participants