Closed jorainer closed 2 years ago
Any opinion on that @lgatto or @sgibb ?
I am in favour for a column
argument in peaksData,Spectra
. So it is very obvious what you get (a matrix with column
columns).
I'll work on that and convert to a PR again once I'm done.
Some general info:
peaksData,Spectra
gained parameter columns
which is passed down to peaksData,MsBackend
.Spectra
support only columns "mz"
and "intensity"
, but in any arbitrary order.columns
- but I will fix these later.OK for review @sgibb and @lgatto :)
This PR:
peaksVariables,MsBackend
method to list the available peaks variables from a backend. The default is"mz"
and"intensity"
, but backends such as theMsBackendTimsTof
would also have ion mobility or other peak-related information available.peaksData,MsBackend
to include a new parametercolumns = peaksVariables()
.Open for discussion:
peaksData
implementations? So far I have only added...
and hence thecolumns
parameter would be ignored for theMsBackendMzR
,MsBackendDataFrame
et al backends.peaksData,Spectra
to include a parametercolumns = peaksData(object)
or should we support passing that parameter using...
?