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
First, thank you for a fantastic tool! Just tried it, works great.
I wonder, would it be possible to add options for applying various kinds of filters based on q-values?
Of course, the user can do the filtering before uploading the report, but it would be cool if all was automatic. With DIA-NN applying filters based on global precursor & protein q-values as well as run-specific PTM q-value & potentially site confidence score will usually be beneficial.
One simple way to implement it is by just adding a single textbox where the user can enter filters in a text format, one line per filter, e.g. Global.Q.Value < 0.01. And this is very easily parsed: find '<' or '>' in the string, everything to the left is the column name, everything to the right is the value.
Best,
Vadim
The text was updated successfully, but these errors were encountered:
Thanks a lot, Vadim! 😊 I completely agree that it could be quite a useful feature. Thank you for the suggestion! We'll add it in the next release of the tool.
First, thank you for a fantastic tool! Just tried it, works great.
I wonder, would it be possible to add options for applying various kinds of filters based on q-values?
Of course, the user can do the filtering before uploading the report, but it would be cool if all was automatic. With DIA-NN applying filters based on global precursor & protein q-values as well as run-specific PTM q-value & potentially site confidence score will usually be beneficial.
One simple way to implement it is by just adding a single textbox where the user can enter filters in a text format, one line per filter, e.g. Global.Q.Value < 0.01. And this is very easily parsed: find '<' or '>' in the string, everything to the left is the column name, everything to the right is the value.
Best,
Vadim
The text was updated successfully, but these errors were encountered: