-
Notifications
You must be signed in to change notification settings - Fork 27
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
static graph visualization #82
Comments
This graph demo (found by @MartinRyan ) allows manual node repositioning (as many do, I think): https://cytoscape.org/cytoscape.js-euler/. Could be useful when automatic layout fails us. |
Cytoscape looks great, it has a dagre extension, and a navigator 'bird's eye view and pan control' extension (mini-map). It consumes JSON though there are convertors for graph objects. |
Also from @MartinRyan py2cytoscape might be useful for static vis. (Cytoscape itself might be useful for the live control GUI as well) |
This is an interesting challenge because:
The UI-Server is only concerned with the installed copy and is not necessarily able to see the working copy. It is OK to require users to register a suite for |
Well, yes and no. If you're working on the working copy then you are able to install it repeatedly pretty easily, and if the payoff is kick-ass web base viz that seems a small price to pay, And besides you currently have to do that anyway if your Also what's the alternative? We don't want to keep a GTK-based static graph GUI. An electron app might allow us to kill both birds with one stone, I guess. |
Assuming that we have done enough logical migration from |
But what if the suite is running? Also this is the situation we have at the moment, I advise people to do this: $ rose suite-run -l; cylc graph mysuite Unfortunately this causes confusion and is a barrier to usage. As a result very few people here use essential Cylc utilities such as:
I wrote this page to try and break down the barrier but sadly it has made little difference. I still regularly see users trying is running the entire suite to test changes.
No nice solution:
|
Fair point on barriers to easy use. So let's do better than that if we can. We do need a non-PyGTK static vis tool with cylc-8 though, one way or another.
Same, and even worse, running an entire beast of a suite repeatedly to test how some cylc feature works, when a 5-line 1-task test suite would do. You can lead a horse to water, but you can't make it change its spots. Or something. |
See comments from (now closed) #81 about graphs in Cylc 8:
|
We probably want to replace
cylc graph
with web technology too, not just the control GUI graph view.The text was updated successfully, but these errors were encountered: