-
Notifications
You must be signed in to change notification settings - Fork 6
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
How to extract just metabolic subset of genes? #34
Comments
@DeniseSl22, didn't we write a SPARQL query for this at some point in time? Or was that just on my long wish-/todo list? |
The pathway SELECT ?wpid ?catalyst ?source ?target WHERE {
?pathway a wp:Pathway ;
dc:identifier / dcterms:identifier ?wpid .
?catalysis a wp:Catalysis ;
dcterms:isPartOf ?pathway ;
wp:source / rdfs:label ?catalyst ;
wp:participants ?reaction .
?reaction a wp:Interaction .
OPTIONAL { ?reaction wp:source ?source }
OPTIONAL { ?reaction wp:target ?target }
} ORDER BY ASC(?catalysis) |
@avelar-ageing , thanks for your question! I believe that the reactions without a clear source and/or target are not relevant in this case (and require some curation on our side). There are also a bunch of interactions between two metabolites which have not been drawn with the MIM-Catalysis interaction type, but with a regular arrow. I've reworked that line in the SPARQL query (see below), so you can comment it out to see the difference in response (# is used for comments in SPARQL). Also note that this is for all pathway (WikiPathways and Reactome) and all species.
|
I am interested in downloading metabolic enzymes from pathways. For example in the omega3 senescence pathway (https://www.wikipathways.org/pathways/WP5424.html) there are various genes that are not directly linked to metabolism, including p21. I think it it should be possible to identify metabolism genes using all genes involved in conversion MIM interactions? Is there a method of just extracting these genes as opposed to all genes in the pathway using the R package?
Thanks
The text was updated successfully, but these errors were encountered: