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

support .apl files #11

Open
colin-combe opened this issue Jul 25, 2018 · 5 comments
Open

support .apl files #11

colin-combe opened this issue Jul 25, 2018 · 5 comments
Labels
enhancement New feature or request

Comments

@colin-combe
Copy link

related Rappsilber-Laboratory/XiSearch#22

@colin-combe
Copy link
Author

motivated by fact xiSearch reads .apl, but converting files before search might be better

@lutzfischer
Copy link
Member

we have various implementation for converting apl to mgf - problem is the how unknown-charge states are handled. potentially breaking the index.

maxquant writes spectra with unknown charge state o .peka.apl - but twice - ones as doubly charged and ones as triply charged. and I am not sure if the order is consistent (especially if you use the allspectra.apl files)
Xi just ignores the the triply charged entries of the .peak.apl and consideres the doubly charged as unknown chargestates.

If you want to support apl - then i need to ensure that the index is correct for the spectrum when returned from xi

@colin-combe
Copy link
Author

we have various implementation for converting apl to mgf - problem is the how unknown-charge states are handled. potentially breaking the index.

I don't think I follow - i'm thinking if everything's converted to .mgf before its fed to xiSearch then the indexes should be correct when it comes out the other end?

If you want to support apl

I don't really want to support another non-standard format, I'd prefer we recommended converting .apl files sooner rather than later if that's a workable solution.

@lutzfischer
Copy link
Member

we have various implementation for converting apl to mgf - problem is the how unknown-charge states are handled. potentially breaking the index.

I don't think I follow - i'm thinking if everything's converted to .mgf before its fed to xiSearch then the indexes should be correct when it comes out the other end?

Yes if converted before search then everything should be fine. But there is the alternative approach to convert the files after search - maybe because you did not convert it and the search did take a month, then researching becomes an effort. This still works fairly straight forward - as long as no peak spectra (unknown charge state - actually a lot more is comparatively vague about these) where searched.
Convert each file on its own and rename in the xi-result everything from .apl to .mgf.

I don't really want to support another non-standard format, I'd prefer we recommended converting .apl files sooner rather than later if that's a workable solution.

I agree that it would be better if we could ignore apl. It's a dependency on a format that is only internally used by maxquant and could therefore change or disappear in any future version of maxquant.

Also it comes per default with a lot less information then we get usually from mgf-files.

But it seems there are still cases where apl-files give still better results then our mgf-pipeline...

@colin-combe
Copy link
Author

Also there's no support for .apl in pyteomics (which the parser uses) or any other open source lib I've found. I can't even really find documentation for the format. Another downside of proprietary formats.

@colin-combe colin-combe added the enhancement New feature or request label Jan 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants