You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At present filterPrecursorMz expects a range of m/z values and keeps all spectra with a precursor m/z within that range. I'm wondering if it would not also be nice to have the possibility to filter spectra matching any of provided precursor m/z (see also on rformassspectrometry/SpectraQL#1). So, what I would suggest is the following:
new filterPrecursorMzRange method (that symlinks at present to the filterPrecursorMz function) which accepts a numeric(2) with lower and upper m/z range.
new filterPrecursorMzValue method that has parameters mz, ppm and tolerance and keeps all spectra that match any of the mz (given ppm and tolerance).
This is somewhat similar to the filterMzRange and filterMzValue methods we have already implemented. Any thoughts on that @sgibb and @lgatto ?
The text was updated successfully, but these errors were encountered:
At present
filterPrecursorMz
expects a range of m/z values and keeps all spectra with a precursor m/z within that range. I'm wondering if it would not also be nice to have the possibility to filter spectra matching any of provided precursor m/z (see also on rformassspectrometry/SpectraQL#1). So, what I would suggest is the following:filterPrecursorMzRange
method (that symlinks at present to thefilterPrecursorMz
function) which accepts anumeric(2)
with lower and upper m/z range.filterPrecursorMzValue
method that has parametersmz
,ppm
andtolerance
and keeps all spectra that match any of themz
(givenppm
andtolerance
).This is somewhat similar to the
filterMzRange
andfilterMzValue
methods we have already implemented. Any thoughts on that @sgibb and @lgatto ?The text was updated successfully, but these errors were encountered: