I encountered an error while using XCMS to process a mzML file with combined ion-mobility scans. This data file was converted using "combine ion mobility scans" function in MSconvert (3.0.20133-4ec330cb1).
Does anyone have an idea on how this could be resolved? I have had no trouble running this before but could no longer make it work after MSConvert updated at some point. The only thing I could notice being changed was the "spectrumId" column in the OnDiskMSnExp object.
> raw_data@featureData@data %>% head
fileIdx spIdx smoothed seqNum acquisitionNum msLevel polarity originalPeaksCount totIonCurrent retentionTime basePeakMZ basePeakIntensity
F1.S001 1 1 NA 1 1 1 1 100188 1420588 3.417 0 0
F1.S002 1 2 NA 2 2 1 1 93503 1420733 4.562 0 0
F1.S003 1 3 NA 3 3 1 1 99532 1440382 5.706 0 0
F1.S004 1 4 NA 4 4 1 1 111433 1475069 6.851 0 0
F1.S005 1 5 NA 5 5 1 1 101443 1466774 7.995 0 0
F1.S006 1 6 NA 6 6 1 1 97472 1456877 9.140 0 0
collisionEnergy ionisationEnergy lowMZ highMZ precursorScanNum precursorMZ precursorCharge precursorIntensity mergedScan
F1.S001 NA 0 103.0579 1677.330 NA NA NA NA NA
F1.S002 NA 0 104.3075 1617.811 NA NA NA NA NA
F1.S003 NA 0 106.2480 1654.061 NA NA NA NA NA
F1.S004 NA 0 104.9191 1636.054 NA NA NA NA NA
F1.S005 NA 0 156.7585 1686.527 NA NA NA NA NA
F1.S006 NA 0 124.2497 1647.860 NA NA NA NA NA
mergedResultScanNum mergedResultStartScanNum mergedResultEndScanNum injectionTime filterString spectrumId centroided
F1.S001 NA NA NA 0 <NA> merged=1 frame=1 TRUE
F1.S002 NA NA NA 0 <NA> merged=2 frame=2 TRUE
F1.S003 NA NA NA 0 <NA> merged=3 frame=3 TRUE
F1.S004 NA NA NA 0 <NA> merged=4 frame=4 TRUE
F1.S005 NA NA NA 0 <NA> merged=5 frame=5 TRUE
F1.S006 NA NA NA 0 <NA> merged=6 frame=6 TRUE
ionMobilityDriftTime isolationWindowTargetMZ isolationWindowLowerOffset isolationWindowUpperOffset scanWindowLowerLimit
F1.S001 29.9618 NA NA NA 99.89902
F1.S002 29.9618 NA NA NA 99.89902
F1.S003 29.9618 NA NA NA 99.89902
F1.S004 29.9618 NA NA NA 99.89902
F1.S005 29.9618 NA NA NA 99.89902
F1.S006 29.9618 NA NA NA 99.89902
scanWindowUpperLimit spectrum
F1.S001 1699.315 1
F1.S002 1699.315 2
F1.S003 1699.315 3
F1.S004 1699.315 4
F1.S005 1699.315 5
F1.S006 1699.315 6
There was a related issue at mzR package a while ago that seems to rely on this column for spectra processing. [https://github.com/sneumann/mzR/issues/44] I will keep everyone posted if I figure out what is going on here.
I guess the solution to this would be to update the proteowizard version within mzR - and if I'm not wrong @sneumann tried to do that already but stumbled across some problems.
Dear contributors,
I encountered an error while using XCMS to process a mzML file with combined ion-mobility scans. This data file was converted using "combine ion mobility scans" function in MSconvert (3.0.20133-4ec330cb1).
Here are some info of my R script.
Error information:
traceback():
Session Info:
Does anyone have an idea on how this could be resolved? I have had no trouble running this before but could no longer make it work after MSConvert updated at some point. The only thing I could notice being changed was the "spectrumId" column in the OnDiskMSnExp object.
There was a related issue at mzR package a while ago that seems to rely on this column for spectra processing. [https://github.com/sneumann/mzR/issues/44] I will keep everyone posted if I figure out what is going on here.
Thanks for helping on this in advance.
Best, Lingjue