Opened 6 years ago

Closed 6 years ago

#820 closed defect (fixed)

Rows with different scan numbers but same peak ids treated the same

Reported by: dbrentw Owned by: dbrentw
Priority: normal Milestone: GRITS - 1.2
Component: MS annotation management Version: GRITS 1.1.x
Severity: critical Keywords:
Cc:

Description

Occasionally, the MS instrument will perform multiple MS/MS events on the same peak in the MS1. Thus you will have multiple scans for the same peak (same precursor m/z). In GRITS, scan number seems to be irrelevant because any changes made to a particular scan are propigated to all scans with the same peak id and parent scan number.

Also, if you click a row for a particular scan to fill the Selection view and the click another row w/ different scan number but same peak id and parent scan number, the Selection window is not updated.

Change History (4)

comment:1 Changed 6 years ago by dbrentw

Owner: set to dbrentw
Status: new → accepted

comment:2 Changed 6 years ago by dbrentw

Resolution: → fixed
Status: accepted → review

Resolved in SVN revision 2067

comment:3 Changed 6 years ago by Rene Ranzinger

Milestone: GRITS - 1.2 SR1 → GRITS - 1.2

comment:4 Changed 6 years ago by Rene Ranzinger

Status: review → closed
Note: See TracTickets for help on using tickets.