-
Notifications
You must be signed in to change notification settings - Fork 57
Closed
Description
When I read in the file using the xcms R package, the msnPrecursorIntensity has a value of 0. When comparing my two mzML files, I see these differences in the precursorList:
msconvert
<selectedIonList count="1">
<selectedIon>
<cvParam cvRef="MS" accession="MS:1000744" name="selected ion m/z" value="734.569152832031" unitCvRef="MS" unitAccession="MS:1000040" unitName="m/z"/>
<cvParam cvRef="MS" accession="MS:1000041" name="charge state" value="1"/>
<cvParam cvRef="MS" accession="MS:1000042" name="peak intensity" value="1.7700104e07" unitCvRef="MS" unitAccession="MS:1000131" unitName="number of detector counts"/>
</selectedIon>
ThermoRawFileParser
<selectedIonList count="1">
<selectedIon>
<cvParam cvRef="MS" accession="MS:1000744" value="734.569152832031" name="selected ion m/z" unitAccession="MS:1000040" unitName="m/z" unitCvRef="MS" />
<cvParam cvRef="MS" accession="MS:1000041" value="1" name="charge state" />
</selectedIon>
</selectedIonList>
So it looks like the peak intensity for the selectedIon is missing from the ThermoRawFileParser.
Now, I don't do anything with MS2 scans in my work, and I'm processing my data in a very particular way, so I'm not sure how important this difference actually is, and whether any other software will care, but it is a difference I see, so I thought I should point it out.
These are both profile data conversions, btw. But I still don't see a value for the peak intensity if I generate centroided data either.
v117_snapshot
Metadata
Metadata
Assignees
Labels
No labels