Issue 214: Ambiguous peptide spectrum matches are removed during library building without any notification

issues
Status:closed
Assigned To:Guest
Type:Todo
Area:Skyline
Priority:3
Milestone:3.1
Opened:2013-01-12 by Brendan MacLean
Changed:2016-09-05 by Brendan MacLean
Resolved:2015-10-12 by Kaipo
Resolution:Fixed
Closed:2016-09-05 by Brendan MacLean
2013-01-12 Brendan MacLean
Title»Ambiguous peptide spectrum matches are removed during library building without any notification
Assigned To»Brendan MacLean
Type»Todo
Area»Skyline
Priority»4
Milestone»2.1
Over the years people have been confused and sought support when ambiguous peptide spectrum matches get removed during spectral library building. It usually starts with a request for why certain peptides are missing in the library.

It would be a big improvement, if Skyline could notify the user that ambiguous peptides were removed and give them information on how many and which ones. I just typed up the following report for one such case:

DNKDGTITVR++ -> EKTGYRVVSGNEQGR+++ (scan 6440)
LNELVEYVSTNR++ -> LLLLLPPAIRGPGLGVAGVAGAAG+++ (scan 5150)
DFSALESQLQDTQELLQEENR++ -> MLDGSRKDKALPNSGDETLMRRTSTIGKKSVQTI+++ (scan 9036)
VQLNFLKLLSATAR++ -> LDLFYKCVCFLPVKLIFVAM+++ (scan 7175)
YIYFHKAPSPEKAEEESERLLR+++ -> SCGSCGGSKGGCGSCGGSKGGC++ (scan 8847)

It would be nice if something like this were automatically accessible any time PSMs were removed due to ambiguity.

2014-01-08 Brendan MacLean
Assigned ToBrendan MacLean»kaipot@u.washington.edu
Milestone2.1»2.6

2014-08-28 Brendan MacLean
Priority4»3
Milestone2.6»3.1

2015-10-12 Kaipo
resolve as Fixed
Statusopen»resolved
Assigned Tokaipot@u.washington.edu»Brendan MacLean

2016-09-05 Brendan MacLean
close
Statusresolved»closed
Assigned ToBrendan MacLean»Guest