-
Notifications
You must be signed in to change notification settings - Fork 2
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
Extract subgraphs in visualisation #117
Labels
enhancement
New feature or request
Comments
Work on Cyclebane may solve some cases of this (not via subgraphs), as we want to support graph[TransmissionFraction] # get the branch computing the transmission fraction (with all ancestors)
graph[RawMonitor:WavelengthMonitor] # get everything in path between start and stop, including ancestors (except those of RawMonitor) |
How does this relate to visualisation? |
If you extract a subgraph, you can visualize the subgraph, instead of everything. |
This is the opposite of my suggestion. I want to visualise the large graph but simplify subgraphs to make the overall structure more readable. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some subgraphs don't need to be visualised in detail. For example, the metadata-related graph in scipp/essreflectometry#27 is relatively large to make it customisable. But, as long as it contains the default providers, there is no need to show it in its full glory in
pipeline.visualize
. We could contract it into a single node and only show that.If we support showing the contracted subgraph separately, we wouldn't even lose information but would allow the user to 'zoom out' a little. There are also other graphs that contain subgraphs that could conceptually be represented by a single node.
Supporting this would require identifying contractable graphs. This needs domain knowledge, i.e., configuration by a human. One possibility would be the tag providers and / or data types and group and contract based on those tags.
To be clear, I'm only talking about visualisation, the actual task graph would remain unchanged.
Example
Only showing providers for brevity.
Could become
I'm not sure what's the best way of indicating inputs and outputs of subgraphs. We could, e.g. duplicate all connects nodes from the main graph in the subgraph.
The text was updated successfully, but these errors were encountered: