-
Notifications
You must be signed in to change notification settings - Fork 80
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
precusor charge for each features #726
Comments
The information of the precursor charge is extracted from the mzML files. If the mzML file(s) provide this information it can be extracted with the If with features you mean the LC-MS features that get defined through the xcms preprocessing (i.e. as a result from the correspondence analysis with the |
Hi jorainer Very well explained. Thanks. I know that the precusor charge can be obtained only when the MS/MS spectra is available. My question is, is it possible to obtain a precusor charge when there is no MS/MS spectra available? we can set in the orbitrap instrument to filter out certain ions depending on the number of precusor charges, which means the precusor charge can be obtained without MS/MS spectra? Best wishes, |
that's a good question - I guess it depends whether the Thermo software stores that information also in the raw data files and whether this is then also available in the mzML file. Maybe have a look at all columns that are available in your ( Also, if you can't find any information, maybe re-evaluate the conversion from raw to mzML files - maybe some of this information got lost during that conversion? but I'm not familiar with Thermo data, so I can't be of any help there. |
Hi, All
I would like to request about the method used in xcms for precusor charge detection for each features. I can open the @featureData@data[["precursorCharge"]] in XCMSnExp object. There are many 0 or NA. My question is how to get more precursorCharge and got the precursorCharge for each feature?
Thanks very much
Hees
The text was updated successfully, but these errors were encountered: