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
Support an OR for matching values (as described in here).
Specifically, we want to support queries such as WHERE MS2PROD=(100 OR 104):TOLERANCEPPM=5. This should ideally work for all conditions, e.g. also for MS2PREC etc.
The text was updated successfully, but these errors were encountered:
The functions .translate_filter_ms2prec and .translate_filter_ms2nl use filter functions from Spectra: filterPrecursorMzand containsNeutralLoss which allow only one value (of mz or neutral loss). Assuming we have
a query like WHERE MS2PREC=(100 OR 104):TOLERANCEPPM=5 we would need to check both values (100 and 104).
At the moment .translate_filter_ms2prec returns ProcessingStep(filterPrecursorMz, ARGS = list(mz = mzr)) which is ok if mzr has length 1. Maybe to solve the problem at the origin one could modify the filterPrecursorMz so that it receives also vectors. Otherwise I was thinking to define a filter function like
and return ProcessingStep(filt_fun, ARGS = list(pmz, tolerance, ppm)). This however can have problems because due to tolerance and ppm different calls to filterPrecursorMz could return the same spectra leading to duplicates in the final spectra returned.
Support an
OR
for matching values (as described in here).Specifically, we want to support queries such as
WHERE MS2PROD=(100 OR 104):TOLERANCEPPM=5
. This should ideally work for all conditions, e.g. also forMS2PREC
etc.The text was updated successfully, but these errors were encountered: