Although originally developed for high resolution LC-MS/MS data, CluMSID can also be used to find similarities in GC-EI-MS data, i.e. data from hard ionisation mass spectrometry.
As the peak picking and spectral merging differs considerably from data dependent ESI-MS/MS, we cannot use the standard
mergeMS2spectra(). In fact, the analysis of mass spectra from hard ionisation mass spectrometry resembles the one of MS1 pseudospectra in ESI-MS. Thus, we can use the CluMSID function
extractPseudospectra() in conjunction with pseudspectra generated by the
CAMERA sometimes have difficulties in handling GC-EI-MS data, we use the
metaMS package that enables workflows specialised to the analysis of such data. We also require the
metaMSdata package from which we import the
FEMSsettings object that contains
CAMERA settings for GC-EI-MS data.
As example data, we use GC-EI-MS metabolomics data from pooled cell extracts of Pseudomonas aeruginosa measured on a Thermo Scientific ITQ linear ion trap that has been converted to netCDF using Thermo Xcalibur. A netCDF file is available in the
To generate a list of (pseudo)spectra, we first need an xsAnnotate object as generated by
CAMERA. In the case of GC-MS data, it is more convenient to use to use the
runCAMERA() than actual
metaMS::runCAMERA requires an
xcmsSet object which we generate by using
xcms::xcmsSet on our netCDF file (we can do that in one go). We used standard GC-MS settings for
runCAMERA() as they are proposed in the
xsAnnotate object, we can now extract the (pseudo)spectra using the
extractPseudospectra() function as we would do for MS1 pseudospectra from LC-ESI-MS data.
Adding annotations is not as easy as with LC-(DDA-)MS/MS data, because only the retention time and the spectrum itself describe the feature and no precursor m/z is available. Thus, feature annotations/identifications made in a different programme, in this case MetaboliteDetector, have to be compared to the spectra in the
Like with LC-(DDA-)MS/MS data, we can use
addAnnotations() to add external annotations. The table output from
writeFeaturelist() will give
NA for all precursor m/z.
To facilitate manual annotation, it helps to plot the spectra along with the relevant information for every feature/pseudospectrum. That can be done by CluMSID’s
In this example, we load the list of feature annotations from
This list of spectra in turn serves as an input for
distanceMatrix(). As we are dealing with low resolution data, we have to adjust the m/z tolerance. The default value, 10ppm, is suitable for time-of-flight mass spectrometers while linear ion traps or single quadrupoles which are commonly used in GC-EI-MS only have unit mass resolution, equivalent to a relative mass error of 0.02 to 0.001 depending on the m/z of the analyte. We chose 0.02 to be tolerant enough for low molecular weight analytes:
Starting from this distance matrix, we can use all the data exploration functions that
CluMSID offers. In this example workflow, we look at a cluster dendrogram:
It is directly visible that the resulting clusters are not as dense as with the LC-MS/MS example data. In turn, there are more between-cluster similarities. This also shows in the correlation network, resulting in a chaotic plot when used with the default minimal similarity of
By choosing a higher similarity threshold of e.g.
0.4, it is far easier to identify clusters:
Presumably, the high between-cluster similarities are due to the low resolution data and the resulting fact, that fragment with different chemical composition but same unit resolution mass cannot be distinguished.
We can also use hierarchical clustering to identify clusters of similar (pseudo-)spectra. Here, too, we have to adjust
h to account for higher between-cluster similarities:
We see that e.g. octadecanoic acid, hexadecanoic acid and dodecanoic acid form a nice cluster as well as the phosphorate containing metabolites phosphoenolpyruvic acid, glyceric acid-3-phosphate, glycerol-3-phosphate and phosphoric acid itself. It is also apparent that some features have a similarity of 1 and could therefore represent the same compound, like e.g. the features 98, 67 and 72. Those three features cluster together with AMP and UMP, suggesting that they could be related to nucleotides.
To illustrate the use of CluMSID’s accessory function with this type of data, we take another look at nucleotides: A signature fragment for nucleotides in GC-EI-MS is m/z 315 that derives from pentose-5-phosphates. We see this fragment in Figure 1, the spectrum of UMP (derivatised with 5 TMS groups). We can use findFragment to see if there are more spectra outside the cluster that freature this fragment. As we deal with unit masses, we would like to find m/z of 315 +/- 0.5 which we can do by setting
tolerance = 0.5/315:
We find four more spectra that contain a 315 fragment that could be investigated closer.
In conclusion, every annotation method is extremely limited if only low resolution data is available and so is CluMSID. Still, we see that the tool works independently of chromatography and mass spectrometry method and even has the potential to give some good hints for feature annotation in GC-EI-MS metabolomics.
sessionInfo() #> R version 3.6.3 (2020-02-29) #> Platform: x86_64-pc-linux-gnu (64-bit) #> Running under: Ubuntu 18.04.4 LTS #> #> Matrix products: default #> BLAS: /home/biocbuild/bbs-3.10-bioc/R/lib/libRblas.so #> LAPACK: /home/biocbuild/bbs-3.10-bioc/R/lib/libRlapack.so #> #> locale: #>  LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C #>  LC_TIME=en_US.UTF-8 LC_COLLATE=C #>  LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 #>  LC_PAPER=en_US.UTF-8 LC_NAME=C #>  LC_ADDRESS=C LC_TELEPHONE=C #>  LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C #> #> attached base packages: #>  stats4 parallel stats graphics grDevices utils datasets #>  methods base #> #> other attached packages: #>  metaMSdata_1.22.0 metaMS_1.22.0 CAMERA_1.42.0 #>  xcms_3.8.2 MSnbase_2.12.0 ProtGenerics_1.18.0 #>  S4Vectors_0.24.4 mzR_2.20.0 Rcpp_22.214.171.124 #>  BiocParallel_1.20.1 Biobase_2.46.0 BiocGenerics_0.32.0 #>  CluMSIDdata_1.2.0 CluMSID_1.2.1 #> #> loaded via a namespace (and not attached): #>  colorspace_1.4-1 ellipsis_0.3.0 htmlTable_1.13.3 #>  base64enc_0.1-3 rstudioapi_0.11 farver_2.0.3 #>  affyio_1.56.0 fansi_0.4.1 codetools_0.2-16 #>  splines_3.6.3 ncdf4_1.17 doParallel_1.0.15 #>  impute_1.60.0 robustbase_0.93-6 knitr_1.28 #>  Formula_1.2-3 jsonlite_1.6.1 cluster_2.1.0 #>  vsn_3.54.0 png_0.1-7 graph_1.64.0 #>  BiocManager_1.30.10 compiler_3.6.3 httr_1.4.1 #>  backports_1.1.6 assertthat_0.2.1 Matrix_1.2-18 #>  lazyeval_0.2.2 limma_3.42.2 cli_2.0.2 #>  acepack_1.4.1 htmltools_0.4.0 tools_3.6.3 #>  igraph_1.2.5 coda_0.19-3 gtable_0.3.0 #>  glue_1.4.0 affy_1.64.0 RANN_2.6.1 #>  dplyr_0.8.5 MALDIquant_1.19.3 statnet.common_4.3.0 #>  vctrs_0.2.4 multtest_2.42.0 gdata_2.18.0 #>  ape_5.3 preprocessCore_1.48.0 nlme_3.1-147 #>  iterators_1.0.12 xfun_0.13 stringr_1.4.0 #>  network_1.16.0 lifecycle_0.2.0 gtools_3.8.2 #>  XML_3.99-0.3 DEoptimR_1.0-8 zlibbioc_1.32.0 #>  MASS_7.3-51.5 scales_1.1.0 pcaMethods_1.78.0 #>  RBGL_1.62.1 MassSpecWavelet_1.52.0 RColorBrewer_1.1-2 #>  yaml_2.2.1 gridExtra_2.3 ggplot2_3.3.0 #>  rpart_4.1-15 reshape_0.8.8 latticeExtra_0.6-29 #>  stringi_1.4.6 highr_0.8 foreach_1.5.0 #>  checkmate_2.0.0 caTools_1.18.0 rlang_0.4.5 #>  pkgconfig_2.0.3 bitops_1.0-6 mzID_1.24.0 #>  evaluate_0.14 lattice_0.20-41 purrr_0.3.3 #>  htmlwidgets_1.5.1 tidyselect_1.0.0 GGally_1.5.0 #>  plyr_1.8.6 magrittr_1.5 R6_2.4.1 #>  IRanges_2.20.2 gplots_3.0.3 Hmisc_4.4-0 #>  sna_2.5 pillar_1.4.3 foreign_0.8-76 #>  survival_3.1-12 nnet_7.3-13 tibble_3.0.0 #>  crayon_1.3.4 KernSmooth_2.23-16 plotly_126.96.36.199 #>  rmarkdown_2.1 jpeg_0.1-8.1 grid_3.6.3 #>  data.table_1.12.8 digest_0.6.25 tidyr_1.0.2 #>  dbscan_1.1-5 munsell_0.5.0 viridisLite_0.3.0