Skip to content
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

Organise graphs based on purposeful views #37

Open
psjm3 opened this issue Apr 10, 2024 · 0 comments
Open

Organise graphs based on purposeful views #37

psjm3 opened this issue Apr 10, 2024 · 0 comments

Comments

@psjm3
Copy link
Contributor

psjm3 commented Apr 10, 2024

Currently users select which graph to generate by issuing a command line option, to make it more intuitive we could organise the options into "views", such as "Compartments-view", "Threads-view", "Heaps-view", etc. Users can first go to a view, and then interactively generate graphs based on information they want to get from the views.

Perhaps we could have a web interface where view options can be selected, and when a view is displayed, users can zoom in and out of the view or click on the nodes to drill down on that specific compartment or thread, etc.

Copied from @rwatson's suggestion on slack:

"I have been pondering visualisations a bit, and I realised that it might be that we want to think about “views” of some sort -- e.g., “compartment centric”, “thread centric”, (perhaps) heap-centric, and so on. In a compartment-centric view we’re interested in the rights accessible from (and to?) thread stacks, but not so much that we’d arrange the whole layout around it. Whereas in a thread-centric view, I think we’d try and lay out all the disjoint stack bits associated with a single thread in vertical “stacks” perhaps with a thread ID / name above, etc.
This might help us focus the ambitions of particular plots a bit more, making it easier to figure out how to arrange them, what to elide/combine/etc."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant