# A short introduction to MSnbase development

Laurent Gatto1, Johannes Rainer2 and Sebastian Gibb3

1de Duve Institute, UCLouvain, Belgium
2Institute for Biomedicine, Eurac Research, Bolzano, Italy.
3Department of Anesthesiology and Intensive Care, University Medicine Greifswald, Germany.

#### 31 May 2019

#### Abstract

This vignette describes the classes implemented in package. It is intended as a starting point for developers or users who would like to learn more or further develop/extend mass spectrometry and proteomics data structures.

#### Package

MSnbase 2.10.1

# Foreword

MSnbase is under active development; current functionality is evolving and new features will be added. This software is free and open-source software. If you use it, please support the project by citing it in publications:

> Gatto L, Lilley KS. MSnbase-an R/Bioconductor package for isobaric tagged mass spectrometry data visualization, processing and quantitation. Bioinformatics. 2012 Jan 15;28(2):288-9. doi: 10.1093/bioinformatics/btr645. PMID: 22113085.

# Questions and bugs

For bugs, typos, suggestions or other questions, please file an issue in our tracking system (https://github.com/lgatto/MSnbase/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/.

NB This document is going to be updated based on current major development plans in `MSnbase`.

# 1 Introduction

This document is not a replacement for the individual manual pages, that document the slots of the MSnbase classes. It is a centralised high-level description of the package design.

MSnbase aims at being compatible with the Biobase infrastructure (Gentleman et al. 2004). Many meta data structures that are used in `eSet` and associated classes are also used here. As such, knowledge of the Biobase development and the new eSet vignette would be beneficial; the vignette can directly be accessed with `vignette("BiobaseDevelopment", package="Biobase")`.

The initial goal is to use the MSnbase infrastructure for MS2 labelled (iTRAQ (Ross et al. 2004) and TMT (Thompson et al. 2003)) and label-free (spectral counting, index and abundance) quantitation - see the documentation for the `quantify` function for details. The infrastructure is currently extended to support a wider range of technologies, including metabolomics.

# 2 Coding style

`MSnbase` follows the Bioconductor style guide. In particular

- Do not use `.` when naming symbols.
- A leading `.` can be used for hidden/local functions or variables.
- Snake case should be restricted to internal functions. For consistency, we favour camel case for public functions.
- Class names should start with a capital and each class should posses a constructor with identical name. Running the constructor without any input should produce a valid empty object.
- Use `##` to start full-line comments.
- For roxygen headers `#'` is preferred, although `##'` is tolerated.
- Use spaces between `=` in function arguments or class definition: `f(a = 1, b = 2)`.
- Always use a space after a comma: `a, b, c`.
- Always use spaces around binary operators: `a + b`.
- Lines should be kept shorter than 80 characters. For example the following code isn’t accepted

    # no wrap at 80
    someVeryLongVariableName <- someVeryLongFunctionName(withSomeEvenLongerFunctionArgumentA = 1, withSomeEvenLongerFunctionArgumentB = 2)

and should be wrapped as shown below:

    # alternative 1
    someVeryLongVariableName <-
        someVeryLongFunctionName(withSomeEvenLongerFunctionArgumentA = 1,
                                 withSomeEvenLongerFunctionArgumentB = 2)

    # alternative 2
    someVeryLongVariableName <- someVeryLongFunctionName(
        withSomeEvenLongerFunctionArgumentA = 1,
        withSomeEvenLongerFunctionArgumentB = 2)

# 3 MSnbase classes

All classes have a `.__classVersion__` slot, of class `Versioned` from the Biobase package. This slot documents the class version for any instance to be used for debugging and object update purposes. Any change in a class implementation should trigger a version change.

## 3.1 `pSet`: a virtual class for raw mass spectrometry data and meta data

This virtual class is the main container for mass spectrometry data, i.e spectra, and meta data. It is based on the `eSet` implementation for genomic data. The main difference with `eSet` is that the `assayData` slot is an environment containing any number of `Spectrum` instances (see the `Spectrum` section).

One new slot is introduced, namely `processingData`, that contains one `MSnProcess` instance (see the `MSnProcess` section). and the `experimentData` slot is now expected to contain `MIAPE` data. The `annotation` slot has not been implemented, as no prior feature annotation is known in shotgun proteomics.

    getClass("pSet")

    ## Virtual Class "pSet" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:           assayData          phenoData        featureData
    ## Class:        environment AnnotatedDataFrame AnnotatedDataFrame
    ##
    ## Name:      experimentData       protocolData     processingData
    ## Class:              MIAxE AnnotatedDataFrame         MSnProcess
    ##
    ## Name:              .cache  .__classVersion__
    ## Class:        environment           Versions
    ##
    ## Extends: "Versioned"
    ##
    ## Known Subclasses:
    ## Class "MSnExp", directly
    ## Class "OnDiskMSnExp", by class "MSnExp", distance 2, with explicit coerce

## 3.2 `MSnExp`: a class for MS experiments

`MSnExp` extends `pSet` to store MS experiments. It does not add any new slots to `pSet`. Accessors and setters are all inherited from `pSet` and new ones should be implemented for `pSet`. Methods that manipulate actual data in experiments are implemented for `MSnExp` objects.

    getClass("MSnExp")

    ## Class "MSnExp" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:           assayData          phenoData        featureData
    ## Class:        environment AnnotatedDataFrame AnnotatedDataFrame
    ##
    ## Name:      experimentData       protocolData     processingData
    ## Class:              MIAxE AnnotatedDataFrame         MSnProcess
    ##
    ## Name:              .cache  .__classVersion__
    ## Class:        environment           Versions
    ##
    ## Extends:
    ## Class "pSet", directly
    ## Class "Versioned", by class "pSet", distance 2
    ##
    ## Known Subclasses:
    ## Class "OnDiskMSnExp", directly, with explicit coerce

## 3.3 `OnDiskMSnExp`: a on-disk implementation of the `MSnExp` class

The `OnDiskMSnExp` class extends `MSnExp` and inherits all of its functionality but is aimed to use as little memory as possible based on a balance between memory demand and performance. Most of the spectrum-specific data, like retention time, polarity, total ion current are stored within the object’s `featureData` slot. The actual M/Z and intensity values from the individual spectra are, in contrast to `MSnExp` objects, not kept in memory (in the `assayData` slot), but are fetched from the original files on-demand. Because mzML files are indexed, using the mzR package to read the relevant spectrum data is fast and only moderately slower than for in-memory `MSnExp` 1 1 The benchmarking vignette compares data size and operation speed of the two implementations..

To keep track of data manipulation steps that are applied to spectrum data (such as performed by methods `removePeaks` or `clean`) a lazy execution framework was implemented. Methods that manipulate or subset a spectrum’s M/Z or intensity values can not be applied directly to a `OnDiskMSnExp` object, since the relevant data is not kept in memory. Thus, any call to a processing method that changes or subset M/Z or intensity values are added as `ProcessingStep` items to the object’s `spectraProcessingQueue`. When the spectrum data is then queried from an `OnDiskMSnExp`, the spectra are read in from the file and all these processing steps are applied on-the-fly to the spectrum data before being returned to the user.

The operations involving extracting or manipulating spectrum data are applied on a per-file basis, which enables parallel processing. Thus, all corresponding method implementations for `OnDiskMSnExp` objects have an argument `BPPARAM` and users can set a `PARALLEL_THRESH` option flag2 2 see `?MSnbaseOptions` for details. that enables to define how and when parallel processing should be performed (using the BiocParallel package).

Note that all data manipulations that are not applied to M/Z or intensity values of a spectrum (e.g. sub-setting by retention time etc) are very fast as they operate directly to the object’s `featureData` slot.

    getClass("OnDiskMSnExp")

    ## Class "OnDiskMSnExp" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:  spectraProcessingQueue                backend              assayData
    ## Class:                   list              character            environment
    ##
    ## Name:               phenoData            featureData         experimentData
    ## Class:     AnnotatedDataFrame     AnnotatedDataFrame                  MIAxE
    ##
    ## Name:            protocolData         processingData                 .cache
    ## Class:     AnnotatedDataFrame             MSnProcess            environment
    ##
    ## Name:       .__classVersion__
    ## Class:               Versions
    ##
    ## Extends:
    ## Class "MSnExp", directly
    ## Class "pSet", by class "MSnExp", distance 2
    ## Class "Versioned", by class "MSnExp", distance 3

The distinction between `MSnExp` and `OnDiskMSnExp` is often not explicitly stated as it should not matter, from a user’s perspective, which data structure they are working with, as both behave in equivalent ways. Often, they are referred to as in-memory and on-disk `MSnExp` implementations.

## 3.4 `MSnSet`: a class for quantitative proteomics data

This class stores quantitation data and meta data after running `quantify` on an `MSnExp` object or by creating an `MSnSet` instance from an external file, as described in the MSnbase-io vignette and in `?readMSnSet`, `readMzTabData`, etc. The quantitative data is in form of a n by p matrix, where n is the number of features/spectra originally in the `MSnExp` used as parameter in `quantify` and p is the number of reporter ions. If read from an external file, n corresponds to the number of features (protein groups, proteins, peptides, spectra) in the file and \(p\) is the number of columns with quantitative data (samples) in the file.

This prompted to keep a similar implementation as the `ExpressionSet` class, while adding the proteomics-specific annotation slot introduced in the `pSet` class, namely `processingData` for objects of class `MSnProcess`.

    getClass("MSnSet")

    ## Class "MSnSet" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:      experimentData     processingData               qual
    ## Class:              MIAPE         MSnProcess         data.frame
    ##
    ## Name:           assayData          phenoData        featureData
    ## Class:          AssayData AnnotatedDataFrame AnnotatedDataFrame
    ##
    ## Name:          annotation       protocolData  .__classVersion__
    ## Class:          character AnnotatedDataFrame           Versions
    ##
    ## Extends:
    ## Class "eSet", directly
    ## Class "VersionedBiobase", by class "eSet", distance 2
    ## Class "Versioned", by class "eSet", distance 3

The `MSnSet` class extends the virtual `eSet` class to provide compatibility for `ExpressionSet`-like behaviour. The experiment meta-data in `experimentData` is also of class `MIAPE` . The `annotation` slot, inherited from `eSet` is not used. As a result, it is easy to convert `ExpressionSet` data from/to `MSnSet` objects with the coersion method `as`.

    data(msnset)
    class(msnset)

    ## [1] "MSnSet"
    ## attr(,"package")
    ## [1] "MSnbase"

    class(as(msnset, "ExpressionSet"))

    ## [1] "ExpressionSet"
    ## attr(,"package")
    ## [1] "Biobase"

    data(sample.ExpressionSet)
    class(sample.ExpressionSet)

    ## [1] "ExpressionSet"
    ## attr(,"package")
    ## [1] "Biobase"

    class(as(sample.ExpressionSet, "MSnSet"))

    ## [1] "MSnSet"
    ## attr(,"package")
    ## [1] "MSnbase"

## 3.5 `MSnProcess`: a class for logging processing meta data

This class aims at recording specific manipulations applied to `MSnExp` or `MSnSet` instances. The `processing` slot is a `character` vector that describes major processing. Most other slots are of class `logical` that indicate whether the data has been centroided, smoothed, although many of the functionality is not implemented yet. Any new processing that is implemented should be documented and logged here.

It also documents the raw data file from which the data originates (`files` slot) and the MSnbase version that was in use when the `MSnProcess` instance, and hence the `MSnExp`/`MSnSet` objects, were originally created.

    getClass("MSnProcess")

    ## Class "MSnProcess" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:              files        processing            merged
    ## Class:         character         character           logical
    ##
    ## Name:            cleaned      removedPeaks          smoothed
    ## Class:           logical         character           logical
    ##
    ## Name:            trimmed        normalised    MSnbaseVersion
    ## Class:           numeric           logical         character
    ##
    ## Name:  .__classVersion__
    ## Class:          Versions
    ##
    ## Extends: "Versioned"

## 3.6 `MIAPE`: Minimum Information About a Proteomics Experiment

The Minimum Information About a Proteomics Experiment (Taylor et al. 2007, 2008) `MIAPE` class describes the experiment, including contact details, information about the mass spectrometer and control and analysis software.

    getClass("MIAPE")

    ## Class "MIAPE" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:                     title                      url
    ## Class:                character                character
    ##
    ## Name:                  abstract                pubMedIds
    ## Class:                character                character
    ##
    ## Name:                   samples            preprocessing
    ## Class:                     list                     list
    ##
    ## Name:                     other                dateStamp
    ## Class:                     list                character
    ##
    ## Name:                      name                      lab
    ## Class:                character                character
    ##
    ## Name:                   contact                    email
    ## Class:                character                character
    ##
    ## Name:           instrumentModel   instrumentManufacturer
    ## Class:                character                character
    ##
    ## Name:  instrumentCustomisations             softwareName
    ## Class:                character                character
    ##
    ## Name:           softwareVersion        switchingCriteria
    ## Class:                character                character
    ##
    ## Name:            isolationWidth            parameterFile
    ## Class:                  numeric                character
    ##
    ## Name:                 ionSource         ionSourceDetails
    ## Class:                character                character
    ##
    ## Name:                  analyser          analyserDetails
    ## Class:                character                character
    ##
    ## Name:              collisionGas        collisionPressure
    ## Class:                character                  numeric
    ##
    ## Name:           collisionEnergy             detectorType
    ## Class:                character                character
    ##
    ## Name:       detectorSensitivity        .__classVersion__
    ## Class:                character                 Versions
    ##
    ## Extends:
    ## Class "MIAxE", directly
    ## Class "Versioned", by class "MIAxE", distance 2

## 3.7 `Spectrum` et al.: classes for MS spectra

`Spectrum` is a virtual class that defines common attributes to all types of spectra. MS1 and MS2 specific attributes are defined in the `Spectrum1` and `Spectrum2` classes, that directly extend `Spectrum`.

    getClass("Spectrum")

    ## Virtual Class "Spectrum" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:            msLevel        peaksCount                rt
    ## Class:           integer           integer           numeric
    ##
    ## Name:     acquisitionNum         scanIndex               tic
    ## Class:           integer           integer           numeric
    ##
    ## Name:                 mz         intensity          fromFile
    ## Class:           numeric           numeric           integer
    ##
    ## Name:         centroided          smoothed          polarity
    ## Class:           logical           logical           integer
    ##
    ## Name:  .__classVersion__
    ## Class:          Versions
    ##
    ## Extends: "Versioned"
    ##
    ## Known Subclasses: "Spectrum2", "Spectrum1"

    getClass("Spectrum1")

    ## Class "Spectrum1" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:            msLevel        peaksCount                rt
    ## Class:           integer           integer           numeric
    ##
    ## Name:     acquisitionNum         scanIndex               tic
    ## Class:           integer           integer           numeric
    ##
    ## Name:                 mz         intensity          fromFile
    ## Class:           numeric           numeric           integer
    ##
    ## Name:         centroided          smoothed          polarity
    ## Class:           logical           logical           integer
    ##
    ## Name:  .__classVersion__
    ## Class:          Versions
    ##
    ## Extends:
    ## Class "Spectrum", directly
    ## Class "Versioned", by class "Spectrum", distance 2

    getClass("Spectrum2")

    ## Class "Spectrum2" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:              merged        precScanNum        precursorMz
    ## Class:            numeric            integer            numeric
    ##
    ## Name:  precursorIntensity    precursorCharge    collisionEnergy
    ## Class:            numeric            integer            numeric
    ##
    ## Name:             msLevel         peaksCount                 rt
    ## Class:            integer            integer            numeric
    ##
    ## Name:      acquisitionNum          scanIndex                tic
    ## Class:            integer            integer            numeric
    ##
    ## Name:                  mz          intensity           fromFile
    ## Class:            numeric            numeric            integer
    ##
    ## Name:          centroided           smoothed           polarity
    ## Class:            logical            logical            integer
    ##
    ## Name:   .__classVersion__
    ## Class:           Versions
    ##
    ## Extends:
    ## Class "Spectrum", directly
    ## Class "Versioned", by class "Spectrum", distance 2

## 3.8 `ReporterIons`: a class for isobaric tags

The iTRAQ and TMT (or any other peak of interest) are implemented `ReporterIons` instances, that essentially defines an expected MZ position for the peak and a width around this value as well a names for the reporters.

    getClass("ReporterIons")

    ## Class "ReporterIons" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:               name     reporterNames       description
    ## Class:         character         character         character
    ##
    ## Name:                 mz               col             width
    ## Class:           numeric         character           numeric
    ##
    ## Name:  .__classVersion__
    ## Class:          Versions
    ##
    ## Extends: "Versioned"

## 3.9 `Chromatogram` and `Chromatograms`: classes to handle chromatographic data

The `Chromatogram` class represents chromatographic MS data, i.e. retention time and intensity duplets for one file/sample. The `Chromatograms` class allows to arrange multiple `Chromatogram` instances in a two-dimensional grid, with columns supposed to represent different samples and rows two-dimensional areas in the plane spanned by the m/z and retention time dimensions from which the intensities are extracted (e.g. an extracted ion chromatogram for a specific ion). The `Chromatograms` class extends the base `matrix` class. `Chromatograms` objects can be extracted from an `MSnExp` or `OnDiskMSnExp` object using the `chromatogram` method.

    getClass("Chromatogram")

    ## Class "Chromatogram" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:              rtime         intensity                mz
    ## Class:           numeric           numeric           numeric
    ##
    ## Name:           filterMz       precursorMz         productMz
    ## Class:           numeric           numeric           numeric
    ##
    ## Name:           fromFile    aggregationFun           msLevel
    ## Class:           integer         character           integer
    ##
    ## Name:  .__classVersion__
    ## Class:          Versions
    ##
    ## Extends: "Versioned"

    getClass("Chromatograms")

    ## Class "Chromatograms" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:               .Data          phenoData        featureData
    ## Class:             matrix AnnotatedDataFrame AnnotatedDataFrame
    ##
    ## Extends:
    ## Class "matrix", from data part
    ## Class "array", by class "matrix", distance 2
    ## Class "structure", by class "matrix", distance 3
    ## Class "vector", by class "matrix", distance 4, with explicit coerce
    ## Class "vector_OR_factor", by class "matrix", distance 5, with explicit coerce

## 3.10 Other classes

### Lists of `MSnSet` instances

When several `MSnSet` instances are related to each other and should be stored together as different objects, they can be grouped as a list into and `MSnSetList` object. In addition to the actual `list` slot, this class also has basic logging functionality and enables iteration over the `MSnSet` instances using a dedicated `lapply` methods.

    getClass("MSnSetList")

    ## Class "MSnSetList" [package "MSnbase"]
    ##
    ## Slots:
    ##
    ## Name:                  x               log       featureData
    ## Class:              list              list         DataFrame
    ##
    ## Name:  .__classVersion__
    ## Class:          Versions
    ##
    ## Extends: "Versioned"

# 4 Miscellaneous

#### Unit tests

MSnbase implements unit tests with the testthat package.

#### Processing methods

Methods that process raw data, i.e. spectra should be implemented for `Spectrum` objects first and then `eapply`ed (or similar) to the `assayData` slot of an `MSnExp` instance in the specific method.

# 5 Session information

    sessionInfo()

    ## R version 3.6.0 (2019-04-26)
    ## Platform: x86_64-w64-mingw32/x64 (64-bit)
    ## Running under: Windows Server 2012 R2 x64 (build 9600)
    ##
    ## Matrix products: default
    ##
    ## locale:
    ## [1] LC_COLLATE=C
    ## [2] LC_CTYPE=English_United States.1252
    ## [3] LC_MONETARY=English_United States.1252
    ## [4] LC_NUMERIC=C
    ## [5] LC_TIME=English_United States.1252
    ##
    ## attached base packages:
    ##  [1] grid      stats4    parallel  stats     graphics  grDevices utils
    ##  [8] datasets  methods   base
    ##
    ## other attached packages:
    ##  [1] microbenchmark_1.4-6 pryr_0.1.4           magrittr_1.5
    ##  [4] gplots_3.0.1.1       msdata_0.24.0        pRoloc_1.24.0
    ##  [7] BiocParallel_1.18.0  MLInterfaces_1.64.0  cluster_2.0.9
    ## [10] annotate_1.62.0      XML_3.98-1.19        AnnotationDbi_1.46.0
    ## [13] IRanges_2.18.1       pRolocdata_1.22.0    Rdisop_1.44.0
    ## [16] zoo_1.8-6            MSnbase_2.10.1       ProtGenerics_1.16.0
    ## [19] S4Vectors_0.22.0     mzR_2.18.0           Rcpp_1.0.1
    ## [22] Biobase_2.44.0       BiocGenerics_0.30.0  ggplot2_3.1.1
    ## [25] BiocStyle_2.12.0
    ##
    ## loaded via a namespace (and not attached):
    ##   [1] snow_0.4-3            plyr_1.8.4            igraph_1.2.4.1
    ##   [4] lazyeval_0.2.2        splines_3.6.0         ggvis_0.4.4
    ##   [7] crosstalk_1.0.0       TH.data_1.0-10        digest_0.6.19
    ##  [10] foreach_1.4.4         htmltools_0.3.6       viridis_0.5.1
    ##  [13] gdata_2.18.0          memoise_1.1.0         doParallel_1.0.14
    ##  [16] mixtools_1.1.0        sfsmisc_1.1-4         limma_3.40.2
    ##  [19] recipes_0.1.5         gower_0.2.1           rda_1.0.2-2.1
    ##  [22] sandwich_2.5-1        lpSolve_5.6.13.1      prettyunits_1.0.2
    ##  [25] colorspace_1.4-1      blob_1.1.1            xfun_0.7
    ##  [28] dplyr_0.8.1           crayon_1.3.4          RCurl_1.95-4.12
    ##  [31] hexbin_1.27.3         genefilter_1.66.0     impute_1.58.0
    ##  [34] survival_2.44-1.1     iterators_1.0.10      glue_1.3.1
    ##  [37] gtable_0.3.0          ipred_0.9-9           zlibbioc_1.30.0
    ##  [40] kernlab_0.9-27        prabclus_2.2-7.1      DEoptimR_1.0-8
    ##  [43] scales_1.0.0          vsn_3.52.0            mvtnorm_1.0-10
    ##  [46] DBI_1.0.0             viridisLite_0.3.0     xtable_1.8-4
    ##  [49] progress_1.2.2        bit_1.1-14            proxy_0.4-23
    ##  [52] mclust_5.4.3          preprocessCore_1.46.0 lava_1.6.5
    ##  [55] prodlim_2018.04.18    sampling_2.8          htmlwidgets_1.3
    ##  [58] httr_1.4.0            threejs_0.3.1         FNN_1.1.3
    ##  [61] RColorBrewer_1.1-2    fpc_2.2-1             modeltools_0.2-22
    ##  [64] pkgconfig_2.0.2       flexmix_2.3-15        nnet_7.3-12
    ##  [67] caret_6.0-84          labeling_0.3          reshape2_1.4.3
    ##  [70] tidyselect_0.2.5      rlang_0.3.4           later_0.8.0
    ##  [73] munsell_0.5.0         mlbench_2.1-1         tools_3.6.0
    ##  [76] LaplacesDemon_16.1.1  generics_0.0.2        RSQLite_2.1.1
    ##  [79] pls_2.7-1             evaluate_0.14         stringr_1.4.0
    ##  [82] mzID_1.22.0           yaml_2.2.0            ModelMetrics_1.2.2
    ##  [85] knitr_1.23            bit64_0.9-7           robustbase_0.93-5
    ##  [88] caTools_1.17.1.2      randomForest_4.6-14   purrr_0.3.2
    ##  [91] dendextend_1.12.0     ncdf4_1.16.1          nlme_3.1-140
    ##  [94] mime_0.6              biomaRt_2.40.0        compiler_3.6.0
    ##  [97] e1071_1.7-1           affyio_1.54.0         tibble_2.1.2
    ## [100] stringi_1.4.3         highr_0.8             lattice_0.20-38
    ## [103] Matrix_1.2-17         gbm_2.1.5             pillar_1.4.1
    ## [106] BiocManager_1.30.4    MALDIquant_1.19.3     data.table_1.12.2
    ## [109] bitops_1.0-6          httpuv_1.5.1          R6_2.4.0
    ## [112] pcaMethods_1.76.0     affy_1.62.0           hwriter_1.3.2
    ## [115] bookdown_0.11         promises_1.0.1        KernSmooth_2.23-15
    ## [118] gridExtra_2.3         codetools_0.2-16      MASS_7.3-51.4
    ## [121] gtools_3.8.1          assertthat_0.2.1      withr_2.1.2
    ## [124] multcomp_1.4-10       diptest_0.75-7        hms_0.4.2
    ## [127] rpart_4.1-15          timeDate_3043.102     coda_0.19-2
    ## [130] class_7.3-15          rmarkdown_1.13        segmented_0.5-4.0
    ## [133] lubridate_1.7.4       shiny_1.3.2           base64enc_0.1-3

# References

Gentleman, Robert C., Vincent J. Carey, Douglas M. Bates, Ben Bolstad, Marcel Dettling, Sandrine Dudoit, Byron Ellis, et al. 2004. “Bioconductor: Open Software Development for Computational Biology and Bioinformatics.” Genome Biol 5 (10):–80. https://doi.org/10.1186/gb-2004-5-10-r80.

Ross, Philip L., Yulin N. Huang, Jason N. Marchese, Brian Williamson, Kenneth Parker, Stephen Hattan, Nikita Khainovski, et al. 2004. “Multiplexed Protein Quantitation in Saccharomyces Cerevisiae Using Amine-Reactive Isobaric Tagging Reagents.” Mol Cell Proteomics 3 (12). Applied Biosystems, Framingham, MA 01701, USA.:1154–69. https://doi.org/10.1074/mcp.M400129-MCP200.

Taylor, Chris F., Norman W. Paton, Kathryn S. Lilley, Pierre-Alain Binz, Randall K. Julian, Andrew R. Jones, Weimin Zhu, et al. 2007. “The Minimum Information About a Proteomics Experiment (Miape).” Nat Biotechnol 25 (8). The HUPO Proteomics Standards Initiative, Wellcome Trust Genome Campus, Hinxton, Cambridgeshire CB10 1SD, UK. chris.taylor@ebi.ac.uk:887–93. https://doi.org/10.1038/nbt1329.

Taylor, Chris F, Pierre-Alain Binz, Ruedi Aebersold, Michel Affolter, Robert Barkovich, Eric W Deutsch, David M Horn, et al. 2008. “Guidelines for Reporting the Use of Mass Spectrometry in Proteomics.” Nat. Biotechnol. 26 (8):860–1. https://doi.org/10.1038/nbt0808-860.

Thompson, Andrew, Jürgen Schäfer, Karsten Kuhn, Stefan Kienle, Josef Schwarz, Günter Schmidt, Thomas Neumann, R Johnstone, A Karim A Mohammed, and Christian Hamon. 2003. “Tandem Mass Tags: A Novel Quantification Strategy for Comparative Analysis of Complex Protein Mixtures by MS/MS.” Anal. Chem. 75 (8):1895–1904.