Foreword

synapter is free and open-source software. If you use it, please support the project by citing it in publications:

Nicholas James Bond, Pavel Vyacheslavovich Shliaha, Kathryn S. Lilley, and Laurent Gatto. Improving qualitative and quantitative performance for MS\(^E\)-based label free proteomics. J. Proteome Res., 2013, 12 (6), pp 2340–2353

Questions and bugs

For bugs, typos, suggestions or other questions, please file an issue in our tracking system (https://github.com/lgatto/synapter/issues) providing as much information as possible, a reproducible example and the output of sessionInfo().

If you don’t have a GitHub account or wish to reach a broader audience for general questions about proteomics analysis using R, you may want to use the Bioconductor support site: https://support.bioconductor.org/.

1 Introduction

This document assumes familiarity with standard synapter pipeline described in (Bond et al. 2013) and in the package synapter vignette, available online and with vignette("synapter", package = "synapter").

In this vignette we introduce a new fragment matching feature (see figures 2, 3 and 4) which improves the matching of identification and the quantitation features. After applying the usual synergise1 workflow (see ?synergise1 and ?Synapter for details) a number of multiple matches and possible false unique matches remain that can be deconvoluted by comparing common peaks in the identification fragment peaks and the quantitation spectra.

The example data synobj2 used throughout this document is available in the synapterdata package and can be directly load as follows:

library("synapterdata")
synobj2RData()

In the [next section](:synergise] we describe how synobj2 was generated. The following sections then describe the new fragment matching functionality.

2 Running synergise1

One has to run the synergise1 workflow before fragment matching can be applied. Please read the general synapter vignette for the general use of synergise1. The additional data needed for the fragment matching procedure are a final_fragment.csv file for the identification run and a Spectrum.xml file for the quantitation run.

## Please find the raw data at:
## http://proteome.sysbiol.cam.ac.uk/lgatto/synapter/data/
library("synapter")

inlist <- list(
  identpeptide = "fermentor_03_sample_01_HDMSE_01_IA_final_peptide.csv.gz",
  identfragments = "fermentor_03_sample_01_HDMSE_01_IA_final_fragment.csv.gz",
  quantpeptide = "fermentor_02_sample_01_HDMSE_01_IA_final_peptide.csv.gz",
  quantpep3d = "fermentor_02_sample_01_HDMSE_01_Pep3DAMRT.csv.gz",
  quantspectra = "fermentor_02_sample_01_HDMSE_01_Pep3D_Spectrum.xml.gz",
  fasta = "S.cerevisiae_Uniprot_reference_canonical_18_03_14.fasta")

synobj2 <- Synapter(inlist, master=FALSE)
synobj2 <- synergise1(object=synobj2,
                      outputdir=tempdir())

3 Filtering fragments

This step is optional and allows one to remove low abundance fragments in the spectra using filterFragments. Filtering fragments can remove noise in the spectra and reduce undesired fragment matches. Prior to filtering, the plotCumulativeNumberOfFragments function can be use to visualise the intensity of all fragments. Both functions have an argument what to decide what spectra/fragments to filter/plot. Choose fragments.ident for the identification fragments and spectra.quant for the quantitation fragments.

plotCumulativeNumberOfFragments(synobj2,
                                what = "fragments.ident")
Cumulative Number of Fragments

Figure 1: Cumulative Number of Fragments

plotCumulativeNumberOfFragments(synobj2,
                                what = "spectra.quant")
Cumulative Number of Fragments

Figure 2: Cumulative Number of Fragments

filterFragments(synobj2,
                what = "fragments.ident",
                minIntensity = 70)
filterFragments(synobj2,
                what = "spectra.quant",
                minIntensity = 70)

4 Fragment matching

This method, named fragmentMatching, performs the matching of the identification fragments vs the quantitation spectra and counts the number of identical peaks for each combination.

Because the peaks/fragments in the spectra of one run will never be numerically identical to these in another, a tolerance parameter has to be set using the setFragmentMatchingPpmTolerance function. Peaks/Fragments within this tolerance are treated as identical.

setFragmentMatchingPpmTolerance(synobj2, 25)
fragmentMatching(synobj2)

The plotFragmentMatching function illustrates the details of this fragment matching procedure. If it is called without any additional argument every matched pair (fragment vs spectrum) is plotted. One can use the key argument to select a special value in a column (defined by the column argument) of the MatchedEMRTs data.frame. E.g. if one wants to select the fragment matching results with a high number of common peaks, e.g. 28 common peaks:

plotFragmentMatching(synobj2,
                     key = 28,
                     column = "FragmentMatching")
Fragment matching for cases with 28 common fragments. The identification data are shown on the top (blue) and the quantitation data are on the bottom (red). Common peaks are displayed in darker colours and highlighted by full points.

Figure 3: Fragment matching for cases with 28 common fragments
The identification data are shown on the top (blue) and the quantitation data are on the bottom (red). Common peaks are displayed in darker colours and highlighted by full points.

Or, if one is interested in all results for the peptide with the sequence "TALIDGLAQR".

plotFragmentMatching(synobj2,
                     key = "TALIDGLAQR",
                     column = "peptide.seq")
Fragment matching for peptide *TALIDGLAQ*.

Figure 4: Fragment matching for peptide TALIDGLAQ

Fragment matching for peptide *TALIDGLAQ*.

Figure 5: Fragment matching for peptide TALIDGLAQ

Maybe the peptide with a special precursor ID looks interesting.

plotFragmentMatching(synobj2,
                     key = 12589,
                     column = "precursor.leID.ident")
Fragment matching precursor with *leID* identifier 12589.

Figure 6: Fragment matching precursor with leID identifier 12589

Fragment matching precursor with *leID* identifier 12589.

Figure 7: Fragment matching precursor with leID identifier 12589

5 Plot distribution of common peaks

The plotFragmentMatchingPerformance function can be used to assess the performance of the fragment matching and the result of the filtering procedure (see below) based on the number of common peaks. This function invisibly returns a list with matrices containing true positive, false positive, true negative and false negative matches for the unique and non unique matches EMRT matches, as illustrated in tables 1 and 2. Both tables could be also generated by fragmentMatchingPerformance.

m <- plotFragmentMatchingPerformance(synobj2)
Number of true/false match peptides for different peak matching thresholds and difference in number of peaks between the first and second (in terms of number of common peaks) possible matches. The former metric is used to filter out possible false positive unique matches while the second is used to filter multiple matches. Empty circles indicate zero peptides.

Figure 8: Number of true/false match peptides for different peak matching thresholds and difference in number of peaks between the first and second (in terms of number of common peaks) possible matches
The former metric is used to filter out possible false positive unique matches while the second is used to filter multiple matches. Empty circles indicate zero peptides.


Table 1: Number of true positives, false negatives, false positives, false negatives and false discovery rate for a given number of common peaks.
ncommon tp fp tn fn all fdr
0 2176 26 0 0 4034 0.0118074
1 1940 5 21 236 2765 0.0025707
2 1426 4 22 750 1899 0.0027972
3 1039 2 24 1137 1370 0.0019212
4 759 2 24 1417 1016 0.0026281
5 569 0 26 1607 780 0.0000000
6 414 0 26 1762 600 0.0000000
7 312 0 26 1864 468 0.0000000
8 245 0 26 1931 379 0.0000000
9 197 0 26 1979 316 0.0000000
10 148 0 26 2028 252 0.0000000
11 116 0 26 2060 203 0.0000000
12 94 0 26 2082 171 0.0000000
13 66 0 26 2110 132 0.0000000
14 55 0 26 2121 110 0.0000000

Table 2: Number of true positives, false negatives, false positives, false negatives and false discovery rate for a given difference in number of common peaks between the higest and second highest multiply matching EMRTs in terms of number of common peptides.
deltacommon tp fp tn fn all fdr
0 334 72 0 0 4034 0.1773399
1 334 8 64 0 889 0.0233918
2 271 4 68 63 698 0.0145455
3 226 2 70 108 566 0.0087719
4 198 1 71 136 501 0.0050251
5 176 1 71 158 453 0.0056497
6 153 1 71 181 397 0.0064935
7 129 1 71 205 337 0.0076923
8 110 1 71 224 294 0.0090090
9 96 1 71 238 261 0.0103093
10 84 1 71 250 232 0.0117647
11 70 1 71 264 201 0.0140845
12 61 1 71 273 180 0.0161290
13 50 1 71 284 150 0.0196078
14 42 1 71 292 130 0.0232558

6 Filtering unique matches

From the left panel on figure 7 and table 1 displaying counts for unique matches one can define filtering values for the unique (this section) and multiple matches (next section). In the case of uniquely matching EMRTs, one can easily reduce the number of false matches by requiring that true matches must have at least one peak/fragment in common. Clearly this will also remove some true matches. The question is whether you want to rely on matches that have no (or only a few) peaks/fragments in common?

performance(synobj2)
getEMRTtable(synobj2)
## 
##    0    1    2    3    4    5    6    7   12   14 
##  241 2865  400   64   21    6    5    1    1    1
filterUniqueMatches(synobj2, minNumber = 1)
performance(synobj2)
getEMRTtable(synobj2)
## 
##   -1    0    1    2    3    4    5    6    7   12   14 
##  625  241 2240  400   64   21    6    5    1    1    1

7 Filtering non-unique matches

The largest benefit of fragment matching is for non unique matches. If we assume that true match have a highest number of common peaks/fragments, we can distinguish correct matches among multiple possible matches that could not resolved before (c.f. section [#sec:plotperf]). To do so, we use the difference of common peaks from the highest to the second highest number in the match group. Assuming two cases with multiple matches. In the first case, we have two possible matches: a match with 7 and a match with 2 fragments in common. In the second ambiguous match, there are a matches with 2 and 1 fragments in common respectively. If we decide to accept a difference of at least 2, our first multiple match case be resolved into a unique match as the difference between the best and second matches is 5 and the best match with 7 common fragments will be upgraded to a unique match.

The right panel of figure 7 and table 2 can be used to choose a good threshold for the difference in number of common peaks.

performance(synobj2)
getEMRTtable(synobj2)
## 
##   -1    0    1    2    3    4    5    6    7   12   14 
##  625  241 2240  400   64   21    6    5    1    1    1
filterNonUniqueMatches(synobj2, minDelta = 2)
performance(synobj2)
getEMRTtable(synobj2)
## 
##   -2   -1    0    1 
##  210  625  241 2529

In this example we rescued 289 unique matches out of the non unique ones.

8 Exporting results

Like in the initial synapter workflow, it is possible to export the MatchedEMRT results using the writeMatchedEMRTs function. The table has some new columns that correspond to the fragment matching procedure, e.g. FragmentMatching, .

writeMatchedEMRTs(synobj2, file = "MatchedEMRTs.csv")

9 Session information

All software and respective versions used to produce this document are listed below.

sessionInfo()
## R version 4.1.1 Patched (2021-08-22 r80813)
## Platform: x86_64-apple-darwin17.0 (64-bit)
## Running under: macOS Mojave 10.14.6
## 
## Matrix products: default
## BLAS:   /Library/Frameworks/R.framework/Versions/4.1/Resources/lib/libRblas.0.dylib
## LAPACK: /Library/Frameworks/R.framework/Versions/4.1/Resources/lib/libRlapack.dylib
## 
## locale:
## [1] C/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
## 
## attached base packages:
## [1] stats4    stats     graphics  grDevices utils     datasets  methods  
## [8] base     
## 
## other attached packages:
##  [1] synapterdata_1.31.0 synapter_2.18.0     MSnbase_2.20.0     
##  [4] ProtGenerics_1.26.0 S4Vectors_0.32.0    mzR_2.28.0         
##  [7] Rcpp_1.0.7          Biobase_2.54.0      BiocGenerics_0.40.0
## [10] BiocStyle_2.22.0   
## 
## loaded via a namespace (and not attached):
##  [1] bitops_1.0-7           doParallel_1.0.16      RColorBrewer_1.1-2    
##  [4] GenomeInfoDb_1.30.0    tools_4.1.1            bslib_0.3.1           
##  [7] utf8_1.2.2             R6_2.5.1               affyio_1.64.0         
## [10] cleaver_1.32.0         DBI_1.1.1              colorspace_2.0-2      
## [13] tidyselect_1.1.1       compiler_4.1.1         preprocessCore_1.56.0 
## [16] bookdown_0.24          sass_0.4.0             scales_1.1.1          
## [19] readr_2.0.2            affy_1.72.0            stringr_1.4.0         
## [22] digest_0.6.28          rmarkdown_2.11         XVector_0.34.0        
## [25] pkgconfig_2.0.3        htmltools_0.5.2        highr_0.9             
## [28] fastmap_1.1.0          limma_3.50.0           rlang_0.4.12          
## [31] impute_1.68.0          jquerylib_0.1.4        generics_0.1.1        
## [34] jsonlite_1.7.2         mzID_1.32.0            BiocParallel_1.28.0   
## [37] dplyr_1.0.7            RCurl_1.98-1.5         magrittr_2.0.1        
## [40] GenomeInfoDbData_1.2.7 MALDIquant_1.20        Matrix_1.3-4          
## [43] munsell_0.5.0          fansi_0.5.0            MsCoreUtils_1.6.0     
## [46] lifecycle_1.0.1        vsn_3.62.0             stringi_1.7.5         
## [49] yaml_2.2.1             MASS_7.3-54            zlibbioc_1.40.0       
## [52] plyr_1.8.6             qvalue_2.26.0          grid_4.1.1            
## [55] parallel_4.1.1         crayon_1.4.1           lattice_0.20-45       
## [58] Biostrings_2.62.0      splines_4.1.1          multtest_2.50.0       
## [61] hms_1.1.1              magick_2.7.3           knitr_1.36            
## [64] pillar_1.6.4           reshape2_1.4.4         codetools_0.2-18      
## [67] XML_3.99-0.8           glue_1.4.2             evaluate_0.14         
## [70] pcaMethods_1.86.0      BiocManager_1.30.16    vctrs_0.3.8           
## [73] tzdb_0.1.2             foreach_1.5.1          gtable_0.3.0          
## [76] purrr_0.3.4            clue_0.3-60            assertthat_0.2.1      
## [79] ggplot2_3.3.5          xfun_0.27              ncdf4_1.17            
## [82] survival_3.2-13        tibble_3.1.5           iterators_1.0.13      
## [85] IRanges_2.28.0         cluster_2.1.2          ellipsis_0.3.2

References

Bond, Nicholas James, Pavel Vyacheslavovich Shliaha, Kathryn S. Lilley, and Laurent Gatto. 2013. “Improving Qualitative and Quantitative Performance for Ms\(^E\)-Based Label Free Proteomics.” Journal of Proteome Research 12 (6). https://doi.org/10.1021/pr300776t.