Library building cut-off score

support
Library building cut-off score sstoychev  2018-08-05 01:15
 

Hi,

I would like to understand better the cut-off score used during library building. For example when importing Protein Pilot data a score of 0.99 is used which I think corresponds to 99% confidence in Protein Pilot? Depending on the search space and /or number of LCMS runs searched the 99% (0.99) cut-off can include a different number of false positives i.e. a small search space/ dataset could have fewer than 1% FP while a large search space/ dataset could have higher than 1% FP. So rather than using the 0.99 cut-off would not be better to use the FDR analysis output from Protein Pilot since that is independent of search space and dataset size? Since Skyline can not read this FDR output maybe could look up the 1%FDR and match to the corresponding % confidence score from Protein pilot?

How would the same work with Max Quant data? I think the msms input file for Slyline is already 1% FDR filtered by MQ so can import all entries i.e. cut-off score can be left blank?

 
 
Brendan MacLean responded:  2018-08-05 08:46

Hi Stoyan,
We use the most appropriate probability value supplied by the search pipeline. When a q value or FDR estimate is available, we try to use that, but some search pipelines provide only posterior error probability or an expectation score. I was recently at ETH teaching the DIA/SWATH course, in which the tutorials used Comet with the TPP. The TPP is one of the pipelines which provides a posterior error probability, and participants were taught to use a tool called Mayu to estimate the PEP with a 1% protein-level FDR. Once that was estimated, then they entered it as the cut-off for Skyline. If your Protein Pilot pipeline uses a non-FDR related probability score, but you have a tool for estimating FDR, then you would just enter the appropriate cut-off for the FDR you want. (Note: if the score is one where zero is best, then you use 1-score as the cutoff. Skyline will flip the value appropriately.)

If you have a pipeline, like MaxQuant or Spectrum Mill where you can apply a cut-off before giving the results to Skyline, then you can just enter 0 in the score cut-off, which explicitly tells Skyline to ignore the cutoff. Since in all other cases, this is a very bad idea, we make you explicitly enter zero to indicate you know what you are doing and you have already pre-filtered your spectrum matches.

Hope this helps. Thanks for using Skyline in your research.

--Brendan