FragPipe icon indicating copy to clipboard operation
FragPipe copied to clipboard

TMT channel interference problem!

Open seongminlab opened this issue 1 year ago • 1 comments

Dear developers!

In our TMTPro-16plex labeling data, 126 and 134N channels without peptides, other channels labeled with HEK and HeLa peptide.

in this case, we found more than 5% of channel interference from 127 to 126!

So, how can we use isotope distribution (from Thermo, TMT kit with each Lot Number) for peptide quantification?

and can we use protein quantification without TMT-integrator on FragPipe?

Thank you

seongminlab avatar Oct 21 '22 01:10 seongminlab

FragPipe/TMT-Integrator does not have the isotope impurity correction. We used to have it but removed because it was creating some new problems.

When you have empty channels, annotate them as None in the annotation.txt file

You can use PSM.tsv to do your own quantification in any way you want

There is also quantification in protein.tsv files that is from Philosopher quant, not TMT-Integrator. And it is based on summing reporter ion intensities, more like in PD.

Best Alexey

From: Seongmin Cheon @.> Sent: Thursday, October 20, 2022 9:27 PM To: Nesvilab/FragPipe @.> Cc: Subscribed @.***> Subject: [Nesvilab/FragPipe] TMT channel interference problem! (Issue #868)

External Email - Use Caution

Dear developers!

In our TMTPro-16plex labeling data, 126 and 134N channels without peptides, other channels labeled with HEK and HeLa peptide.

in this case, we found more than 5% of channel interference from 127 to 126!

So, how can we use isotope distribution (from Thermo, TMT kit with each Lot Number) for peptide quantification?

and can we use protein quantification without TMT-integrator on FragPipe?

Thank you

— Reply to this email directly, view it on GitHubhttps://github.com/Nesvilab/FragPipe/issues/868, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIIMM644H635JUTSQYB75PDWEHWO7ANCNFSM6AAAAAARKWDJXQ. You are receiving this because you are subscribed to this thread.Message ID: @.@.>>


Electronic Mail is not secure, may not be read every day, and should not be used for urgent or sensitive issues

anesvi avatar Oct 21 '22 13:10 anesvi