-
Notifications
You must be signed in to change notification settings - Fork 0
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
take out cross pathway links #50
Comments
What do you mean by no links to subpathways? Does that mean that in the Reactome representation of axon guidance we won't include Netrin-1 signaling? |
The idea is that we could only ever see one level of the hierarchy as seen in the Reactome viewer. For axon guidance, you would just see You would not see any events from these subpathways (that is the same as now). This change will mainly impact models (e.g. most signaling pathways) that have connections linking to events in other pathways (which are often super or sub pathways). |
As an example of a model that is strongly affected by this change. See TCF dependent signaling in response to WNT. In order to build up the full picture of this pathway we would really need to find a way to display the information from the many inter-linked pathways from Reactome. I think the bridge model pattern would work but again, requires client development to happen. The only real alternative that I see is to do what we did before and import the connected data into the model - but then we deal with large clouded graphs (which is why Reactome broke it apart in the first place) and massive redundancy across related models. |
This is an interim step before finishing #43
The view in Noctua will only show contents from the individual pathway. No links to super/sub pathways nor links to events in other pathways will be shown. These will all eventually be captured in the bridge model graph(s). Fairly significant work on the client will be needed to support the use of the bridge model in the UI. (Won't happen unless it is prioritized.)
The text was updated successfully, but these errors were encountered: