We love ms2convert! Works great.
We just got a new Orbitrap Fusion in the lab and installed - looks like it's returning the ms2 scan header mass precision into the "precursor_mz" field, which suffers from rounding errors and M+1 mis-selection. I guess Thermo changed some things around in Fusion .raw files?
Anyway, just wanted to say thanks for the great program, and see if you're aware of this new glitch for these instruments.
Scott A. Gerber, PhD
Associate Professor of Genetics & Biochemistry
Member, Norris Cotton Cancer Center,
Director, Proteomics Shared Resource, and
Investigator, Institute for Quantitative Biomedical Sciences
Geisel School of Medicine at Dartmouth, Lebanon, NH 03756
Tel. 603.653.3679 / 6185 Fax. 9223
From: Matt Chambers <matt.chambers42@gm...> - 2013-10-15 15:24:22
For the scans you say suffer from rounding errors, is the Monoisotopic M/Z scan header value
populated? If that's not the value you're seeing from pwiz then yeah there's some issue and I'll
need to see the file to test. Er, and I think we also might night need to update the version of
MSFileReader on our build nodes to properly support Fusion, so that might have an effect too.
On 10/14/2013 4:16 PM, Scott A. Gerber wrote:
> We love ms2convert! Works great.
> We just got a new Orbitrap Fusion in the lab and installed – looks like it’s returning the ms2
> scan header mass precision into the “precursor_mz” field, which suffers from rounding errors and
> M+1 mis-selection. I guess Thermo changed some things around in Fusion .raw files?
> Anyway, just wanted to say thanks for the great program, and see if you’re aware of this new
> glitch for these instruments.