cbielow / PTXQC

A Quality Control (QC) pipeline for Proteomics (PTX) results generated by MaxQuant
Other
42 stars 25 forks source link

Contaminant recognition #127

Closed ofleitas closed 11 months ago

ofleitas commented 1 year ago

Hello I am analyzing my proteomic data with Maxquant, but I am no using the Maxquant contaminant FASTA files instead I am using the contaminant FASTA file reported by Frankenfield et al., 2022 (Ashley M. Frankenfield, Jiawei Ni, Mustafa Ahmed, and Ling Hao Journal of Proteome Research 2022 21 (9), 2104-2113,DOI: 10.1021/acs.jproteome.2c00145). The contaminant FASTA file reported by Frankenfield et al., 2022 is more updated than Maxquant contaminant FASTA file and cRAP. When the contaminant FASTA file reported by Frankenfield et al., 2022 is integrated in MaxQuant, the identified contaminants will appear in column Protein ID with the prefix ‘Cont_’ and not in the column Potential contaminant(proteinGroups.txt). Then when I run PTXQC, it is not recognized the presence of contaminants. Appear the follows message: “No contaminants found in any sample. Incorporating contaminants during search is highly recommended! “ Then I think that could be great adapt PTXQC to recognize in the MaxQuant output the contaminants reported by Frankenfield et al., 2022. Best regards

cbielow commented 1 year ago

thanks for reporting. So, just to make sure I understand correctly: you disabled Include Contaminants in MaxQuant and added a custom FASTA file in MaxQuant (along with the FASTA file for the actual species you are interested in)?

Alternative solution: you can replace the MaxQuant_1.2.3\bin\conf\contaminants.fasta with the Frankenfield FASTA (and keep Include Contaminants in MaxQuant to "on"). Then MaxQuant will use your contaminant DB and the Potential Contaminant column should be correctly populated by MaxQuant. This way, no change to PTXQC is required.

ofleitas commented 1 year ago

Dear Chris

Your solution worked well. Thank you very much for your help. Best regards

On Tue, Mar 14, 2023 at 6:01 AM Chris Bielow @.***> wrote:

thanks for reporting. So, just to make sure I understand correctly: you disabled Include Contaminants in MaxQuant and added a custom FASTA file in MaxQuant (along with the FASTA file for the actual species you are interested in)?

Alternative solution: you can replace the MaxQuant_1.2.3\bin\conf\contaminants.fasta with the Frankenfield FASTA (and keep Include Contaminants in MaxQuant to "on"). Then MaxQuant will use your contaminant DB and the Potential Contaminant column should be correctly populated by MaxQuant. This way, no change to PTXQC is required.

— Reply to this email directly, view it on GitHub https://github.com/cbielow/PTXQC/issues/127#issuecomment-1467971350, or unsubscribe https://github.com/notifications/unsubscribe-auth/AM624NEBFS5CO77GHZAAV23W4BM2LANCNFSM6AAAAAAVWP3DU4 . You are receiving this because you authored the thread.Message ID: @.***>