-
Notifications
You must be signed in to change notification settings - Fork 27
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
ZenoTOF EAD spectra in Spectra objects #349
Comments
and these values are not yet reported as spectra variables? if not, we might need to add support for that rather in mzR - which then also depends on proteowizard. do you know by chance if proteowizard can read/handle this mzML file and what the MS OBO for these variables is? |
Thank you! The mzML file I am referencing has been generated through Proteowizards mzConvert (enabled through ProteoWizard/pwiz#3087). For EAD you have to set a collision energy and electron beam energy. In the file it looks like this: EAD name: Example:
For normal CID in TOFs you should have: CID name: Example:
|
Thanks! but that looks like we need to add support for these terms in mzR. I'll look into that - and once mzR can extract this info it's automatically reported in Spectra |
I made a PR in mzR that extracts also the MS_electron_beam_energy from mzML files: sneumann/mzR#303 - with this you get also a spectra variable (if you read the data into a Until it gets included into official mzR you could install my fork with BiocManager::install("jorainer/mzR", ref = "devel") |
Thank you, that solves it! |
Note: the PR was merged into mzR (the current developmental version). Closing the issue - feel free to re-open if needed. |
Hello and thank you for maintaining this!
I am working with ZenoTOF data containing CID and EAD spectra. MS2 scans in such files can contain two different fragmentation energies, which are stored in the mzML files for EAD and CID, respectively. It would be great to be able to access those energies and fragmentation types in Spectra objects. An example file can be downloaded from here. Thank you!
The text was updated successfully, but these errors were encountered: