-
Notifications
You must be signed in to change notification settings - Fork 12
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
Request features: flagging (or solving?) saturated features #2
Comments
Hi @lfnothias, thanks for the report! |
Hi @iprotsyuk This saturation level will depend on the instrument and the methods. Here is an example of strong chromatographic/mass spec saturation. Regarding MS saturation in detail, here is the corresponding ions. And here is a typical non-saturated feature we see. Thanks and let me know if I can give more info. |
@lfnothias, it looks like the identification of oversaturated peaks in m/z space will require the processing of profile-mode data which isn't acceptable by Optimus at the moment. From this of view, it's easier to implement the spotting of such features based on their distorted chromatographic profile. In the example you shared, the chromatographic plato lasts for about 10-20 seconds. Is it usual for oversaturated peaks or they can be shorter, down to several seconds? |
Hi @iprotsyuk, LF |
Hi,
Saturation of the detector in mass spectrometry is quite common in metabolomic. Obviously, these saturated MS1 or MS2 features cannot be compared properly between samples. Decreasing the sample concentration allows to avoid saturation of most abundant features, but will lead into a loss of sensitivity regarding the smaller intensity features, that deserves to be investigated as much as the most abundant ones.
So it would be great to tackle this matter, and I can see two options:
13C isotopologue (m/z +1) as a proxy to estimate the intensity of saturated monoisotopic ion across various samples.
I know that Optimus contains an OpenMS option that pool detected isotopologues for a MS1 feature. But I think it takes into account only the m/z +1 (and/or +2), only if, the isotopologue ratio match a "natural" profil for metabolite. So that doesnt solve the problem here.
I take the chance to express how fantastic Optimus workflow is ! Thanks guys for sharing it with the community.
Louis-Félix
The text was updated successfully, but these errors were encountered: