Closed fengmingchen closed 1 year ago
For the file you showed it clearly says that what was converted was function=4 coded with MSlevel 0... You can check your experiment file in the raw folder to figure what that is supposed to be.
MSE is unpredictable in terms of msLevel. It depends on the instrument if it is coded as 1 or 2 (yes, we love Waters...). Since there is no isolation to me it is fair enough to call it msLevel 1.
Is the raw_new
multiple files? You probably need to investigate a bit more detailed what you have there.
Why is 135MB crazy?
level 1-2 was selected by Peking filter.
You probably want to select using the "subset" --> "scanEvent" filter instead. ScanEvent is what waters calls functions.
Thank you so much for such a quick reply, I am a grad student studying your course. Thank you very much for your XCMS open course. Yes, I took your opinion on Function and set up the filter below by MSconvert.
peakpicking msLevel = 1-2
scanEvent 1-2
Update: The percursor info of the ions of function=2 filtered by the Subset are all the same ion mass, which is obviously wrong. Whether the information on the parent ion of MS2 (function=2) obtained in this way is unreliable.
Aren't you confusing things? MSE is not MS2. There is no precursor ion in reality. I think the processor is just set to be in the middle between the min and max m/z measured.
Yes, Function 2 being identified as MS2 misled me, I figured out what my problem was. Thanks for your prompt reply, compliments.
Hello everyone Running my MSE data obtained by Waters Q-TOF-MS, I want to get the data of FUCTION 1 and 2 which is MS1 MS2. But the result is beyond my expectation, The obtained RAW data format onDiskMSnExp has a crazy size of 135MB.
Also my waters raw data was converted by MSconvert and level 1-2 was selected by Peking filter. So I'm wondering why this happens.