Issue 315: Improve support for library scores in Skyline

issues
Status:open
Assigned To:Kaipo
Type:Todo
Area:Skyline
Priority:3
Milestone: 
Opened:2014-03-09 by Brendan MacLean
Changed:2014-08-28 by Brendan MacLean
Resolved:
Resolution:
Closed:
2014-03-09 Brendan MacLean
Title»Improve support for library scores in Skyline
Assigned To»kaipot@u.washington.edu
Type»Todo
Area»Skyline
Priority»3
Milestone»2.6
It would be nice, in Skyline, to be able to get at the original score used as the BiblioSpec cut-off score, and even apply a more stringent cut-off in peptide filtering without needing to create a new library.

Currently we use a certain score to apply a cut-off during library creation. We store that score in the library, and even the type of score it was, but we never again allow Skyline users any access to that score, without them using a SQLite tool to look at the raw .blib database.

We should store the value in the Skyline document XML for every peptide that has a library match, along with its score type, and we should expose these two values as new columns in the Skyline custom reports.

Finally, we should add UI to the Peptide Settings - Library tab to allow setting a score cut-off that is more restrictive than the values in the library itself.

2014-08-28 Brendan MacLean
Milestone2.6»