Skip to content
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

Unable to read .mzML files #29

Open
StSchulze opened this issue Apr 29, 2019 · 4 comments
Open

Unable to read .mzML files #29

StSchulze opened this issue Apr 29, 2019 · 4 comments

Comments

@StSchulze
Copy link

I am using the most current pGlyco version (2019.01.01) which is supposed to support mzML files, but when I try to use an mzML file, I get the following error

[pParse] Path Invalid! datapath = C:\Users\Admin\Desktop\pGlyco2\20150708_QE3_UPLC8_DBJ_SA_Hela_39frac_Trypsin_18.mzML

[pParse] Task abort!
[pParse] pParse has encountered a problem and will exit. Retry with correct parameters.

The path is correct/the file is located at the given location (it was selected in the GUI by browsing), so I'm not sure what that error means.
The corresponding .raw file works perfectly fine.
I have converted it using ProteoWizard 3.0.19046

The full report is attached.
pGlyco_task_2019-04-29-18-11-46.log

Thanks for any help on this.

@jalew188
Copy link
Contributor

jalew188 commented May 1, 2019

@StSchulze please check https://github.com/pFindStudio/pParse_pXtract/blob/master/README.md to see how pGlyco supports mzML.

@StSchulze
Copy link
Author

@jalew188 Thanks for the link. I converted the .raw to .mzML again with msconvert, using the described settings. Unfortunately, it fails with the same error as before, so it doesn't seem to solve the problem.

I have added a screenshot of the msconvert settings in case I have missed something.
screenshot

@jalew188
Copy link
Contributor

jalew188 commented May 5, 2019

Hi, the problem is not from ProteoWizard, it seems that pParse does not find the file C:\Users\Admin\Desktop\pGlyco2\20150708_QE3_UPLC8_DBJ_SA_Hela_39frac_Trypsin_18.mzML. I will try mzML files in these days.

@StSchulze
Copy link
Author

Yeah, that's what I initially thought as well.
As mentioned above the path is correct (and the file has been selected through browsing with the GUI).
Thanks for having a look into this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants