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

Produce an spectral library per project #9

Open
ypriverol opened this issue May 19, 2024 · 0 comments
Open

Produce an spectral library per project #9

ypriverol opened this issue May 19, 2024 · 0 comments
Assignees
Labels

Comments

@ypriverol
Copy link
Member

The first release of the project should be to create for each project provided in the folder of data, an spectral library file in msp.

Here, you can see some examples about msp files https://ftp.pride.ebi.ac.uk/pub/databases/pride/resources/cluster/spectrum-libraries/2015-04/

Clustering MUST happen first in independent projects splitting by charge, instrument, species. After that, a library must be created only for these two categories: instrument and species, meaning all charges for the same species and same instrument should be merged in the same library but, they are not clustered together only merged at the end. For each project, we should get at the end, for example:

PXD008467:

  • Human
    • Q Exactive
      • PXD008467-Human-QExative.msp.gz

Currently, the pipeline ends in the maracluster for each project, to generate the consensus, you can reuse the code from https://github.com/statisticalbiotechnology/representative-spectra-benchmark where we explored the different consensus algorithms from maracluster paper here

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

No branches or pull requests

2 participants