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

pLink (and pParse) not working on Astral data #104

Open
amaralbc opened this issue Mar 25, 2024 · 3 comments
Open

pLink (and pParse) not working on Astral data #104

amaralbc opened this issue Mar 25, 2024 · 3 comments

Comments

@amaralbc
Copy link

Hello,

I'm trying to run some Thermo Astral data on pLink, but I'm getting an error when searching using the .raw files. I have MS File Reader installed and I'm able to process orbitrap data (from an Eclipse and from a QExactive) with no problems at all.
The error I'm getting is this:

pLink_CrashLog_AstralData

It happens in the beginning when extracting the data. If I click OK, it tries to resume and says the engine is ready to search. However, it gets stuck in the start search line and it doesn't go through:

[pLink] Start searching C:\Users\Lab\Desktop\Processing\pLink\AstralTestingPhoX.raw, Labeling None

It stays there for days and nothing happens.
The same data file does work if I first convert it to MGF using ProteoWizard, but that means I lose intensity info.
Is there any workaround?

Thanks!

@amaralbc
Copy link
Author

Just a quick add if that helps: I've tried to run pParse directly from cmd on the raw file, according to the instructions here: http://pfind.org/software/pParse/index.html

It generates the .ms1 and .ms2 files, however the .xtract file has a size of 0kb before throwing the same error as before with the "unhandled exception". This is the info I have on the terminal:

C:\Program Files\pLink\2.3.11\bin>pParse.exe -D C:\Users\Lab\Desktop\Processing\pLink\AstralTestingPhoX.raw

      *********************************************
     /       pParse2.0 (x64) from pFind Studio     \
    /        Email  :  pfind@ict.ac.cn              \
    \        Website:  http://pfind.ict.ac.cn       /
      *********************************************

[pParse] Calling pXtract to export MS1 and MS2 files...
[pXtract] The software will expire in 01/01/2100
[pXtract] Begin to extract C:\Users\Lab\Desktop\Processing\pLink\AstralTestingPhoX.raw
[pXtract] pXtract tries to use MSFileReader
[pXtract] : 100.00%
[pXtract] Output Files Completed!
[pXtract] == == == Time elapsed: 1002.03s. == == ==
[pParse] MS1list completes.
[pParse] Processing C:\Users\Lab\Desktop\Processing\pLink\AstralTestingPhoX.MS1
[pParse] Start spliting MS2...
[pParse] File 0: C:\Users\Lab\Desktop\Processing\pLink\AstralTestingPhoX_ID_0.ms2 complete!
[pParse] File 1: C:\Users\Lab\Desktop\Processing\pLink\AstralTestingPhoX_ID_1.ms2 complete!
[pParse] Loading MS1 and MS2 files...
[pParse] Loading MS1 Spectra Number: 6603

At this point the error pops up like before. If I click OK in the error pop-up, pParse just quits and cmd go back to waiting commands.

@NorthblueM
Copy link
Contributor

Sorry for the delay in updating the spectra extraction plug-in, pXtract, and the precursor correction plug-in, pParse, within the current version of pLink to support Astral data. The format of Astral's data differs slightly from that of Orbitrap's. Rest assured, we are actively addressing this issue and plan to release a new version once internal testing is completed.

Indeed, MSconvert can be used to extract mgf before feeding it to pLink search for the time being, although the mgf extracted by MSConvert might lack mass correction and mixed spectra features compared to what pParse offers. I'm curious, are you looking for the intensity information of the precursor ions, or something else?

@amaralbc amaralbc closed this as completed Apr 8, 2024
@amaralbc
Copy link
Author

amaralbc commented Apr 8, 2024

That's great to know, looking forward to the new release!

For this dataset I was only curious about identification numbers, but we have a few projects to evaluate precursor intensity for the near future, so the raw file support would be appreciated. The MGF route is not the best when using MSconvert, I'm seeing a 20% drop in identifications when looking at the same data in mgf versus raw file formats (acquired on an Eclipse). Most likely due to the mass corrections you mentioned, maybe some wrong monoisotopic peak peaking as well.

@amaralbc amaralbc reopened this Apr 8, 2024
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