Issue 529: Consider imposing spectrum filtering based on Full-Scan settings

issues
Status:open
Assigned To:Brendan MacLean
Type:Todo
Area:Skyline
Priority:3
Milestone: 
Opened:2017-07-01 by Brendan MacLean
Changed:2017-07-01 by Brendan MacLean
Resolved:
Resolution:
Closed:
2017-07-01 Brendan MacLean
Title»Consider imposing spectrum filtering based on Full-Scan settings
Assigned To»Brendan MacLean
Type»Todo
Area»Skyline
Priority»3
This support thread proposed a use case where the researcher had collected both high res and low res spectra into the same file and wanted Skyline to extract only from high res spectra, but Skyline imposed no such filter, even though the settings were clearly not useful for IT spectra.

https://skyline.ms/announcements/home/support/thread.view?rowId=27914

Matt Chambers had this to contribute:

Skyline could certainly use a SpectrumList_Filter to filter for only certain analyzers. I just committed CLI bindings for the rest of the filter predicates; previously only index, scan event, and scan number were available. Now there's also analyzer, activation, charge state, mzPresent, mzWindow, precursorMzSet, etc.

So "high res" would presumably map to "TOF, orbi, FT" and "low res" would be "quad, IT"?