mzmine / mzmine

mzmine source code repository
https://mzmine.github.io/mzmine_documentation/
MIT License
182 stars 122 forks source link

the similar issues on peak area integration #2042

Open ashin947 opened 3 weeks ago

ashin947 commented 3 weeks ago

mzmine integration issue.pdf

Hi, everyone, I do not know if anybody observing the issues on the peak integration. I run 20 data files by Thermo QE-Plus mass spec and then by MZMINE software. One feaure ,m/z=782.56878 RT=1.23 min positive mode, by MZMINE was wrongly skewed integrated, which shows lots of scan points were missing and integration area was much lower. However, all 20 files were good when integration on Thermo Xcalibur browser and data acquistion was absolutely fine= no any data scan missing. So the problems happened on MZMINE. It could be poor scan mass accuracy, however, the mass accuracy was 3 in raw mass spec data and 8 ppm was used for mzmine processing. So it is unlikely to be the reason of mass accuracy. Does anyone come across the similar issues on peak area integration?

ansgarkorf commented 3 weeks ago

Hi, difficult to help without seeing data. As a first step you can easily find out if mass accuracy is the problem by allowing wider tolerances.

ashin947 commented 3 weeks ago

mzmine integration issue_01 mzmine integration issue_02 mzmine integration issue_03 4 I have found a few pictures, hoping they can express my meaning

ansgarkorf commented 3 weeks ago

Very hard to see, but is this polarity switching data? If yes, please make sure you have enough data points per peak. We should check if the manual integration tool properly works for polarity switching.

Kirsteen426 commented 3 weeks ago

Very hard to see, but is this polarity switching data? If yes, please make sure you have enough data points per peak. We should check if the manual integration tool properly works for polarity switching.

MZMINE never make mess of the peak integration if the parameters stetting is correct? Thank you very much for the help.

ansgarkorf commented 3 weeks ago

Can you share one of the raw files where the integration is not good?

Kirsteen426 commented 3 weeks ago

Can you share one of the raw files where the integration is not good?

Thank you for the reply. For this case, raw files integration are good. If the raw files integration is bad, I would not expect MZMINE to rectify the bad integrations.

Kirsteen426 commented 3 weeks ago

Very hard to see, but is this polarity switching data? If yes, please make sure you have enough data points per peak. We should check if the manual integration tool properly works for polarity switching.

Dear all, have a look the PDF. The data acquisition is by polarity switching. The scan point is really fine for this peak, no missing no lacking etc, as can be seen from Thermo Xcalibur browser. Really want to figure out why MZMINE integration is poor. Thanks. mzmine integration issue.pdf

robinschmid commented 3 weeks ago

@Kirsteen426 thanks for filing an issue. In order to work on it and solve it, we need a raw data file and the batch processing configuration. The batch should contain all the steps needed to reproduce the issue.

I guess your issue is really with the manual reintegration pane and not so much with the automatic integration during batch processing with chromatogram builder and feature resolving?

Best Robin

ashin947 commented 3 weeks ago

I have sent the file to this address
https://github.com/ashin947/raw-data.git image

robinschmid commented 3 weeks ago

in the raw data visualizer, you have to select the polarity to show below the chromatogram plot.

image

During processing you need to set the scan filter to only use one polarity. This can be done in the mzwizard: image

Or in the chromatogram builder to build chromatograms for positive mode first and then negative mode second. image

ashin947 commented 2 weeks ago

image Thank you very much for your reply, but I'm not sure if it's really a display issue. When I double-click on "Area" in "feature list table", S1 Data file shows missing scan points (FIG A) while S2 data file is normal (this file's integration is correct). If I open TIC Visualizer (right click on "area" in the "feature list table"), however, it shows the correct integration (FIG B). Can you possibly work out the reasons? Thanks