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

Automatically increase edge thickness based on normalized edge weights from a property #143

Open
prrao87 opened this issue Apr 30, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@prrao87
Copy link
Member

prrao87 commented Apr 30, 2024

Consider that we have pre-computed quantities that we assign as edge properties (type: float). It's a common use case to want to visualize the graph with edge thickness normalized by weights. Below is an example visualization made in PyVis (per this video).

image

In terms of UI design, I'm not 100% certain what's the best way to make the edge thickness by weight available to the user, but an idea would be to normalize the min/max edge weights in the entire graph beforehand and then assign the edge thickness via a single checkbox like "Set edge thickness by property" (or something like this). @mewim you might have better ideas on this.

@prrao87 prrao87 added the enhancement New feature or request label Apr 30, 2024
@prrao87 prrao87 changed the title Allow user to increase edge thickness based on normalized edge weights Allow user to increase edge thickness based on normalized edge weights from a property Apr 30, 2024
@prrao87 prrao87 changed the title Allow user to increase edge thickness based on normalized edge weights from a property Automatically increase edge thickness based on normalized edge weights from a property Apr 30, 2024
@mewim
Copy link
Member

mewim commented May 1, 2024

I think the way you described makes sense. We can have an option to set the edge size based on property on the UI. Unfortunately the current edge settings do not work quite well (#119). I'll look into it again and start working on this after fixing #119.

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

No branches or pull requests

2 participants