-
-
Notifications
You must be signed in to change notification settings - Fork 24
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GC-FID data: automatinc peak detector / integrator not working #402
Comments
With GC-FID, smoothing might be required first. Could you provide the displayed data set? |
Yes sure, here is a link to the same dataset. The peaks are very tiny compared to the solvent, between 13 and 27 mins. https://we.tl/t-AfNfUjLLBc |
Thanks for the file. I would recommend to run the following steps on the GC-FID chromatogram:
|
Thank you for indicating the steps, I used them and I managed to integrate peaks well. |
@AnnaClo Watch out: there are two big peaks, one at ~3.2 Minutes, the other at ~6.1 Minutes: |
Oh ok I got it! Thank you! |
This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
I have data detected simultneously on gc ms and fid. OpenChrom detects and integrates properly the ms data, but not the fid peaks. For some reason some of the peaks result integrated only halfaway - see screenshots.
The other half of the peak is not quantified, not even as a separate peak. Before peak integration, I can see that the dotted line reaches the top of the peak but doesn't climb down the other half, so I guess the problem is peak detection.
Any idea what could be the fix?
I managed to get some peaks right by forcing 'optimize the baseline (VV) in peak detection, but the problem still appears for a handful of peaks per chromatogram. This isssue is not there at all in MS data.
Here below a peak detected and integrated with the same procedure, from ms data, and from fid data respectively.
The text was updated successfully, but these errors were encountered: