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
Feature Description:
A (set of) filter(s), ideally also applying when exporting summaries, that let you filter out any features with no matching structures, above/below certain quality metrics (Tanimoto score, precursor error, MS2 error, etc.)
Use Case / Problem Description
Adding basic filtering based on user-defined thresholds of the abundance of quality metrics available (CSI FinderID, Tanimoto similarity, MS1 and MS2 error, etc.) seems simple enough, and given the existence of the GUI, it seems like it should be a feature there without having to use API calls to do this level of filtering.
Benefits
Time savings for users who use the GUI and have thresholds for quality metrics to filter out bad hits, in a way that doesn't involve manually checking thousands of features.
The text was updated successfully, but these errors were encountered:
Example:
Export a project summary, but only export hits with formulas having >=25% peaks (and/or absolute threshold of at least three peaks) explained, explained intensity >=33%, and a structure associated that has >=70% Tanimoto similarity. Just to filter out garbage hits.
Feature Description:
A (set of) filter(s), ideally also applying when exporting summaries, that let you filter out any features with no matching structures, above/below certain quality metrics (Tanimoto score, precursor error, MS2 error, etc.)
Use Case / Problem Description
Adding basic filtering based on user-defined thresholds of the abundance of quality metrics available (CSI FinderID, Tanimoto similarity, MS1 and MS2 error, etc.) seems simple enough, and given the existence of the GUI, it seems like it should be a feature there without having to use API calls to do this level of filtering.
Benefits
Time savings for users who use the GUI and have thresholds for quality metrics to filter out bad hits, in a way that doesn't involve manually checking thousands of features.
The text was updated successfully, but these errors were encountered: