You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As Reactome content is available in BioPAX format and we already have the necessary modules to make graph-based queries (e.g. paths between, common targets/regulators, etc.) on data in BioPAX format (via Paxtools), we should be able to make these queries available on Reactome content as well.
We need to be careful about the fact that the queries rely on the existence of ProteinReference objects. ProteinReference objects should have UnificationXrefs to UniProt and RelationshipXrefs to HGNC symbols. Otherwise, queries may not be able to identify sources and targets.
It is worth noting that PathwayCommons resource integration pipeline makes some modifications on Reactome BioPAX so that it is in sync with the preferred format. This here is the class doing that. The modifications don't seem necessary for the queries to work, but this is something to keep in mind.
The text was updated successfully, but these errors were encountered:
As Reactome content is available in BioPAX format and we already have the necessary modules to make graph-based queries (e.g. paths between, common targets/regulators, etc.) on data in BioPAX format (via Paxtools), we should be able to make these queries available on Reactome content as well.
We need to be careful about the fact that the queries rely on the existence of ProteinReference objects. ProteinReference objects should have UnificationXrefs to UniProt and RelationshipXrefs to HGNC symbols. Otherwise, queries may not be able to identify sources and targets.
It is worth noting that PathwayCommons resource integration pipeline makes some modifications on Reactome BioPAX so that it is in sync with the preferred format. This here is the class doing that. The modifications don't seem necessary for the queries to work, but this is something to keep in mind.
The text was updated successfully, but these errors were encountered: