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

I want to (have to) filter for two peptides per protein. #398

Closed
wolski opened this issue May 27, 2022 · 2 comments
Closed

I want to (have to) filter for two peptides per protein. #398

wolski opened this issue May 27, 2022 · 2 comments

Comments

@wolski
Copy link

wolski commented May 27, 2022

When reporting protein IDs or Quant's, journals require at least two peptides to identify a protein.

I am thinking of using the "report.tsv" and implementing as follows:

  • Compute the number of "Stripped.Sequence" per "Protein.Group" then filter "Protein.Group" where the number of Stripped.Sequence > 1.
  • Afterward, filter proteins for Q-value:
    • Lib.PG.Q.Value < 0.01
    • PG.Q.Value < 0.05

Since I used MBR, I should use Lib.PG.Q.Value instead of Global.PG.Q.Value, according to the documentation,

However, you describe more options for filtering, e.g., using PG.Q.Value in:

  • How to choose the FDR/q-value threshold?

Is the answer applicable to MBR runs? That is, can I use PG.Q.Values when MBR is enabled and Lib.PG.Q.Value instead of Global.PG.Q.Value?

@vdemichev
Copy link
Owner

I would suggest:

  • Filter report.tsv at global precursor FDR 1% and global protein FDR 1%, in addition to 1% run-specific precursor FDR.
  • Determine proteins for which there are at least two stripped sequences (in the filtered data).
    But I don't think this journal request makes sense for most analyses, so to formally comply with it can also calculate the number of stripped sequences matching the protein before the filtering.

With or without MBR, using PG.Q.Value filters at run-specific protein FDR.

Vadim

@wolski
Copy link
Author

wolski commented May 30, 2022

Thank you.

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