Search found 25 matches
- 27 Feb 2013 00:05
- Forum: Plugins, presets and filters
- Topic: HTTP Graph 1.0.7 released with Gephi 0.8.2 support
- Replies: 2
- Views: 4099
HTTP Graph 1.0.7 released with Gephi 0.8.2 support
Now available on the Gephi Marketplace. Now using Membrane ESB 3.5.8. Significant performance improvements. If you see any problems with it or have suggestions for features or improvements, please let me know! Video overview is a bit outdated, but still relevant: http://vimeo.com/18591468 Marketplac...
- 23 Aug 2012 22:29
- Forum: How-To and Troubleshooting
- Topic: 2 Force Atlas Layouts
- Replies: 6
- Views: 5086
Re: 2 Force Atlas Layouts
Do you have the HTTP Graph plugin loaded? Because I have defined Force Atlas parameters in the plugin, I've noticed that it shows up separately as shown in the image.
- 04 Jun 2012 17:06
- Forum: QA: Ideas, Requests and Feedback
- Topic: An approach to improving network graph readability.
- Replies: 16
- Views: 21221
Re: An approach to improving network graph readability.
How do yall thaink about this http://bit.ly/M2IUHq edge clustering paper. Like facebook or larger network graphs have like so many edges its makes the edges like useless. Could this be a layout option to use like, after you run a ForceAtlas2? There was some discussion around developing force-direct...
- 03 Jun 2012 14:38
- Forum: QA: Ideas, Requests and Feedback
- Topic: An approach to improving network graph readability.
- Replies: 16
- Views: 21221
Re: An approach to improving network graph readability.
Is this something that would have to be built into Gephi? like hand coded? If so I'm happy to spend some time on it. However, I'm terrible at syntax and coding and stuff... Is there any way I could help? - wfb Yep, it would require implementing the pseudo-code included in the paper in Java, interac...
- 28 May 2012 13:18
- Forum: QA: Ideas, Requests and Feedback
- Topic: An approach to improving network graph readability.
- Replies: 16
- Views: 21221
An approach to improving network graph readability.
Thought this academic paper might be of interest to the Gephi community.
Motif Simplification: Improving Network Visualization Readability
with Fan and Parallel Glyphs - Cody Dunne and Ben Shneiderman
http://hcil.cs.umd.edu/trs/2012-11/2012-11.pdf
Motif Simplification: Improving Network Visualization Readability
with Fan and Parallel Glyphs - Cody Dunne and Ben Shneiderman
http://hcil.cs.umd.edu/trs/2012-11/2012-11.pdf
- 04 May 2012 21:50
- Forum: Data Import / Export
- Topic: Netflow Data and Gephi
- Replies: 8
- Views: 9485
Re: Netflow Data and Gephi
I believe you can set the end time to 'null' to make it persist forever. (this works in Java) ... Hope that helps!
- 21 Mar 2012 13:23
- Forum: How-To and Troubleshooting
- Topic: 168k nodes, 4m edges, slow UI...
- Replies: 9
- Views: 12694
Re: 168k nodes, 4m edges, slow UI...
This is Force Atlas 2 running 80 threads. Unfortunately, I don't have any crazy GPUs around to play with. For what it's worth, PFA doesn't scale quite so well. If there are too many threads, Gephi will crash hard with no stack trace (presumably the native libraries).
- 20 Mar 2012 18:24
- Forum: How-To and Troubleshooting
- Topic: 168k nodes, 4m edges, slow UI...
- Replies: 9
- Views: 12694
Re: 168k nodes, 4m edges, slow UI...
In case anyone's curious what this looks like when running:


- 19 Mar 2012 22:24
- Forum: How-To and Troubleshooting
- Topic: 168k nodes, 4m edges, slow UI...
- Replies: 9
- Views: 12694
Re: 168k nodes, 4m edges, slow UI...
Very cool, thanks for that information.
pbittner, I have been wanting to see the source for PFA (especially the GPU bits).. Any chance that is available to look at?
pbittner, I have been wanting to see the source for PFA (especially the GPU bits).. Any chance that is available to look at?
- 17 Mar 2012 01:35
- Forum: How-To and Troubleshooting
- Topic: 168k nodes, 4m edges, slow UI...
- Replies: 9
- Views: 12694
Re: 168k nodes, 4m edges, slow UI...
Reducing the heap size to the least it needs to be to process the graph, and keeping the Data Lab view up instead of the Overview makes a major difference in this scenario. It looks like the updating of the graph is the biggest contributor to the UI slowness.