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
centWave peak picking algorithm needs option to optimise following parameters together: peakpickingParameters$min_peakwidth (Range for Min peak width range in seconds) peakpickingParameters$max_peakwidth (Range for Max peak width range in seconds) peakpickingParameters$ppm (Range for tolerated ppm m/z deviation in consecutive scans in ppm) peakpickingParameters$mzdiff (Range for Minimum difference in m/z for peaks with overlapping Retention Times)
IPO for group and retcor
For grouping method denstiy allow to optimise range of bw and mzwid simultaneously retcorGroupParameters$bw (*Range for Bandwidth) retcorGroupParameters$mzwid (*Range for width of overlapping m/z slices)
The text was updated successfully, but these errors were encountered:
Thank you @lecorguille, I think there is a problem with parameters input interface now:
would be possible for grouping parameter to make that if input is a single value and not a range, to keep that parameter fixed and optimise only other one;
for retention time correction method obiwarp parameters are listed as non-optimisable, but m/z step input still has to be range.
IPO for xcmsSet
peakpickingParameters$min_peakwidth
(Range for Min peak width range in seconds)peakpickingParameters$max_peakwidth
(Range for Max peak width range in seconds)peakpickingParameters$ppm
(Range for tolerated ppm m/z deviation in consecutive scans in ppm)peakpickingParameters$mzdiff
(Range for Minimum difference in m/z for peaks with overlapping Retention Times)IPO for group and retcor
retcorGroupParameters$bw
(*Range for Bandwidth)retcorGroupParameters$mzwid
(*Range for width of overlapping m/z slices)The text was updated successfully, but these errors were encountered: