From 254eaebf88922bb7840a5c74552842fe9e1e487d Mon Sep 17 00:00:00 2001
From: GitHub Actions
Last modified: 2024-12-09 09:45:30.242476
Compiled: Mon Dec 9 10:22:03 2024
Note that the use of the filter functions might be more efficient for some backends, depending on their implementation, (e.g. database-based backends could translate the filter function into a SQL @@ -832,7 +832,7 @@
The resulting object contains now the data for all 4 MS2 spectra and an union of all spectra variables from both objects.
@@ -925,9 +925,9 @@+## Merge 2 Spectra into one [Mon Dec 9 10:48:01 2024] +## Signal <= 10 in MS level(s) 2 set to 0 [Mon Dec 9 10:48:01 2024] +## Remove peaks with intensities outside [0.1, Inf] in spectra of MS level(s) 2. [Mon Dec 9 10:48:02 2024]Data manipulations## ... 20 more variables/columns. ## Lazy evaluation queue: 2 processing step(s) ## Processing: -## Merge 2 Spectra into one [Mon Dec 9 10:22:33 2024] -## Signal <= 10 in MS level(s) 2 set to 0 [Mon Dec 9 10:22:33 2024] -## Remove peaks with intensities outside [0.1, Inf] in spectra of MS level(s) 2. [Mon Dec 9 10:22:33 2024]
It is possible to add also custom functions to the processing queue
of a Spectra
object. Such a function must take a peaks
matrix as its first argument, have ...
in the function
@@ -958,9 +958,9 @@
Object sps_2
has now 3 processing steps in its lazy
evaluation queue. Calling intensity()
on this object will
now return intensities that are half of the intensities of the original
@@ -1227,9 +1227,9 @@
Before applyProcessing()
the lazy evaluation queue
contained 2 processing steps, which were then applied to the peak data
@@ -1561,7 +1561,7 @@
fl <- tempfile()
export(sps, MsBackendMzR(), file = fl)
## Writing file file89973a4b8ffd...OK
+## Writing file file899721aa5a12...OK
To evaluate which of the spectra variables were exported, we load the exported data again and identify spectra variables in the original file which could not be exported (because they are not defined variables in @@ -1582,8 +1582,8 @@
fls <- c(tempfile(), tempfile())
export(sps, MsBackendMzR(), file = fls[c(1, 2, 1, 2)])
## Writing file file89971aa24e3f...OK
-## Writing file file89973f185768...OK
+## Writing file file89971767a8d1...OK
+## Writing file file8997359073cb...OK
A more realistic use case for mzML export would be to export MS data
after processing, such as smoothing (using the smooth()
function) and centroiding (using the pickPeaks()
function)
@@ -1624,7 +1624,7 @@
With the call the full peak data was imported from the original mzML files into the object. This has obviously an impact on the object’s size, which is now much larger than before.
diff --git a/pkgdown.yml b/pkgdown.yml index c2d478f3..b83a0785 100644 --- a/pkgdown.yml +++ b/pkgdown.yml @@ -5,7 +5,7 @@ articles: MsBackend: MsBackend.html Spectra-large-scale: Spectra-large-scale.html Spectra: Spectra.html -last_built: 2024-12-09T10:20Z +last_built: 2024-12-09T10:45Z urls: reference: https://rformassspectrometry.github.io/Spectra/reference article: https://rformassspectrometry.github.io/Spectra/articles diff --git a/reference/MsBackend.html b/reference/MsBackend.html index e7610fb0..36e21f6f 100644 --- a/reference/MsBackend.html +++ b/reference/MsBackend.html @@ -442,9 +442,9 @@For cbind2()
: A data.frame
or DataFrame
with the
-spectra variables to be added to the backend. Need to be of the same
-length as the number of spectra in the backend. The number of rows and
-their order has to match the number of spectra and their order in x.
y
+and their order have to match the number of spectra and their order
+in x
.
dropNaSpectraVariables()
might still show columns containing NA
values
for core spectra variables.
-cbind2()
: allows to appends multiple spectra variables to the backend at
-once. The Spectra
and the values for the new spectra variables have to
-be in a matching order. Replacing existing spectra variables is not
-supported through this function. For a more controlled way of adding
-spectra variables, the joinSpectraData()
should be used.
cbind2()
: allows to appends multiple new spectra variables to the
+backend at once. The values for the new spectra variables have to
+be in the same order as the spectra in x
. Replacing existing spectra
+variables is not supported through this function. For a more controlled
+way of adding spectra variables, the joinSpectraData()
should be used.
centroided()
, centroided<-
: gets or sets the centroiding
information of the spectra. centroided()
returns a logical
vector of length equal to the number of spectra with TRUE
if a
diff --git a/reference/Spectra.html b/reference/Spectra.html
index c6f8fd77..a688e7cb 100644
--- a/reference/Spectra.html
+++ b/reference/Spectra.html
@@ -438,7 +438,7 @@
applyProcessing()
function.cbind2()
: Appends multiple spectra variables from a data.frame
,
-DataFrame
or matrix
to the Spectra
object at once. It does so
-blindly (e.g. do not check rownames compatibility) and is therefore at
-the risk of the user. The function also does not allow to replace existing
-spectra variables. For a more controlled way of adding spectra
-variables, the joinSpectraData()
should be used. It will return a
-Spectra
object with the appended spectra variables. cbind2()
does
-check however that the number of rows of the data.frame
or DataFrame
-matches the number of spectra in the Spectra
object.
DataFrame
or matrix
to the Spectra
object at once. The order of
+the values (rows) in y
has to match the order of spectra in x
. The
+function does not allow to replace existing spectra variables. cbind2()
+returns a Spectra
object with the appended spectra variables. For a more
+controlled way of adding spectra variables, see the joinSpectraData()
+function.
combineSpectra()
: combines sets of spectra (defined with parameter f
)
into a single spectrum per set aggregating their MS data (i.e. their
peaks data matrices with the m/z and intensity values of their
@@ -424,8 +418,8 @@