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

Output Venn diagram visualization for a set of selections #7

Open
Lambeaux opened this issue Jul 7, 2020 · 1 comment
Open

Output Venn diagram visualization for a set of selections #7

Lambeaux opened this issue Jul 7, 2020 · 1 comment
Labels
capabilities/analysis Concerns the graph data model, output libraries, and command line workflow type/feature New feature or request that's satisfying some kind of functional requirement

Comments

@Lambeaux
Copy link
Contributor

Lambeaux commented Jul 7, 2020

Issue summary & value proposition

Visually represent the relationship between multiple selections so users know they are getting the data they expect.

Problem

Visualization is challenging because it's not always clear how to detect the difference between:

  • Bad data
  • User error
  • An actual bug

When writing selections for filtering dependencies, seeing the relationship between multiple selections can be really useful so that follow-on analysis can be performed with more confidence.

Proposed solution

Provide another draw function that operates on selections or labeled selections:

;; Takes variadic args of filters and labels them using a stringified version of the filters
(draw-venn [:node "ddf/.*"] [:node ".*/.*catalog.*"] [:node ".*/.*spatial.*"])
;; Takes variadic args of alternating labels and filters
(draw-venn-labeled "ddf-nodes" [:node "ddf/.*"] "ddf-catalog" [:node ".*/.*catalog.*"] "everything-else" [:node ".*"])

Could also provide a counterpart that operates on features by aggregating the bundles into the appropriate buckets to assess how independent a set of features truly are:

(draw-venn-feature "feature-A" "feature-B" "feature-C")
@Lambeaux Lambeaux added the type/feature New feature or request that's satisfying some kind of functional requirement label Jul 7, 2020
@Lambeaux
Copy link
Contributor Author

Lambeaux commented Jul 7, 2020

Helps us answer the hard data questions:

When someone doesn't get something, could the tail case just be that their graph doesn't have the requisite edges? Or the edges just aren't coming up in a search?

Hard to answer a question of omission without additional tools to peek into other aspects of the data.

@Lambeaux Lambeaux added the capabilities/analysis Concerns the graph data model, output libraries, and command line workflow label Dec 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
capabilities/analysis Concerns the graph data model, output libraries, and command line workflow type/feature New feature or request that's satisfying some kind of functional requirement
Projects
None yet
Development

No branches or pull requests

1 participant