3 ms·

Looks great! Today after work I plan to try out version with PMI and https://github.com/graphistry/pygraphistry https://github.com/graphistry/pygraphistry .

by kozikow 10y ago

stared 10y ago
I don't know this one... when not D3 I was using Gephi or igraph (see http://kateto.net/network-visualization http://kateto.net/network-visualization, it has also Python bindings).
- kozikow 10y ago
  Does any of those libraries would support: - Mouse over to highlight neighbours - Zoom in and out - Browser based - Ideally "hide this cluster" functionality I wanted to add some of those features using d3, but the weekend ran out. Also "mouse over" would require me to move the vis from canvas to svg.
  - stared 10y ago
    For interactive I use D3.js, on SVG. And I can add all functionalities I like. :) In particular, I am thinking about creating a general-purpose co-occurrence graph (after some success of TagOverflow), see e.g. http://p.migdal.pl/delab-matury/koincydencje/ http://p.migdal.pl/delab-matury/koincydencje/. If you like it, you can motivate me to making it a library :). But: there should be exports from igraph to D3.js, and from Gephi to http://sigmajs.org/ http://sigmajs.org/ (<- this is interactive, and higher level that D3.js; I haven't used it, though; with mouseover and zoom).
    - kozikow 10y ago
      d3 tends to be very low level and there are a few successful libraries built on top of it. Co-occurrence graph library certainly would be popular. In my visualisation I've spent the most time fiddling with JavaScript and currently it's the bottle neck of quality of the visualisation. My another problem was that due the graph size it took ~1 minute to stabilize[1] on my browser and it was very wobbly and janky. I had to pre-load nodes positions and disable animation to make it usable for viewers. The fully automated analsysis of big graphs would require some server side component pre-computing the graph. 1. It was stabilizing quicker with smaller collision (newly introduced in d3 v4 force layout) parameter, but nodes were more likely to overlap.
      - stared 10y ago
        For larger graphs than ~100 it's better to precompute it. If you want to make all vis, then I will still use precomputed as a seed.

Looks great! Today after work I plan to try out version with PMI and https://github.com/graphistry/pygraphistry https://github.com/graphistry/pygraphistry .

by kozikow 10y ago

Looks great! Today after work I plan to try out version with PMI and https://github.com/graphistry/pygraphistry https://github.com/graphistry/pygraphistry .

stared 10y ago

I don't know this one... when not D3 I was using Gephi or igraph (see http://kateto.net/network-visualization http://kateto.net/network-visualization, it has also Python bindings).

kozikow 10y ago
Does any of those libraries would support: - Mouse over to highlight neighbours - Zoom in and out - Browser based - Ideally "hide this cluster" functionality I wanted to add some of those features using d3, but the weekend ran out. Also "mouse over" would require me to move the vis from canvas to svg.
- stared 10y ago
  For interactive I use D3.js, on SVG. And I can add all functionalities I like. :) In particular, I am thinking about creating a general-purpose co-occurrence graph (after some success of TagOverflow), see e.g. http://p.migdal.pl/delab-matury/koincydencje/ http://p.migdal.pl/delab-matury/koincydencje/. If you like it, you can motivate me to making it a library :). But: there should be exports from igraph to D3.js, and from Gephi to http://sigmajs.org/ http://sigmajs.org/ (<- this is interactive, and higher level that D3.js; I haven't used it, though; with mouseover and zoom).
  - kozikow 10y ago
    d3 tends to be very low level and there are a few successful libraries built on top of it. Co-occurrence graph library certainly would be popular. In my visualisation I've spent the most time fiddling with JavaScript and currently it's the bottle neck of quality of the visualisation. My another problem was that due the graph size it took ~1 minute to stabilize[1] on my browser and it was very wobbly and janky. I had to pre-load nodes positions and disable animation to make it usable for viewers. The fully automated analsysis of big graphs would require some server side component pre-computing the graph. 1. It was stabilizing quicker with smaller collision (newly introduced in d3 v4 force layout) parameter, but nodes were more likely to overlap.
    - stared 10y ago
      For larger graphs than ~100 it's better to precompute it. If you want to make all vis, then I will still use precomputed as a seed.