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

Phosphosite information #10

Closed
Spacebio opened this issue Mar 20, 2017 · 3 comments
Closed

Phosphosite information #10

Spacebio opened this issue Mar 20, 2017 · 3 comments
Labels

Comments

@Spacebio
Copy link

Hi,

I have a question about your tool, how did you store and use the phosphosite information?

Thanks!
Corinne

@jdrudolph
Copy link
Owner

could you be more specific about which information you mean?

@Spacebio
Copy link
Author

I meant, how did you link the phosphosite data to the PPI network to map it? Where can I find this script? and is it possible to to use symbols ot entities rather than entrez ID?

Thank you,
C.

@jdrudolph
Copy link
Owner

jdrudolph commented Mar 21, 2017

You have to make some compromise between the network and the data. I chose to map the data from uniprot to the entrez gene ids used for the network. If I were to map it the other way round, my network would be cluttered with duplicated entries stemming from the (one gene id) => (many uniprot ids) mapping.

I don't know for sure how it'll work out but if the identifiers are consistent between the network and the data you should be able to run the functionality score and network reconstruction from the command line. In order for the full pipeline to work you will need to provide a custom idmapping file instead of db/uniprot/HUMAN_9606_idmapping.dat.gz which will allow the curated site information from phosphosite plus to be mapped to your custom identifiers.

If you want to map your own data from uniprot to entrez you could use the code in util/mapping.py

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