The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]metanet.ch.
R-based access to mass-spectrometry (MS) data. While many packages exist to process MS data, many of these make it difficult to access the underlying mass-to-charge ratio (m/z), intensity, and retention time of the files themselves. This package is designed to format MS data in a tidy fashion and allows the user perform the plotting and analysis.
Version: | 1.4.3 |
Imports: | xml2, base64enc, data.table, utils, stats |
Suggests: | testthat, knitr, rmarkdown, tidyverse, ggplot2, dplyr, plotly, openxlsx, DBI, RSQLite, reticulate, BiocParallel, Spectra, arrow, microbenchmark, rvest |
Published: | 2024-10-09 |
DOI: | 10.32614/CRAN.package.RaMS |
Author: | William Kumler [aut, cre, cph], Ricardo Cunha [ctb], Ethan Bass [ctb] |
Maintainer: | William Kumler <wkumler at uw.edu> |
BugReports: | https://github.com/wkumler/RaMS/issues |
License: | MIT + file LICENSE |
URL: | https://github.com/wkumler/RaMS |
NeedsCompilation: | no |
Citation: | RaMS citation info |
Materials: | README NEWS |
In views: | ChemPhys |
CRAN checks: | RaMS results |
Reference manual: | RaMS.pdf |
Vignettes: |
Intro-to-RaMS (source, R code) Intro-to-tmzML (source, R code) Minifying-files-with-RaMS (source, R code) RaMS-and-friends (source, R code) Benchmarking (source, R code) |
Package source: | RaMS_1.4.3.tar.gz |
Windows binaries: | r-devel: RaMS_1.4.3.zip, r-release: RaMS_1.4.3.zip, r-oldrel: RaMS_1.4.3.zip |
macOS binaries: | r-release (arm64): RaMS_1.4.3.tgz, r-oldrel (arm64): RaMS_1.4.3.tgz, r-release (x86_64): RaMS_1.4.3.tgz, r-oldrel (x86_64): RaMS_1.4.3.tgz |
Old sources: | RaMS archive |
Reverse imports: | RawHummus, squallms |
Please use the canonical form https://CRAN.R-project.org/package=RaMS to link to this page.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.