October 24, 2017 at 11:38 am #1058
I suspect that the need for tags explorer to display the network is one of the reasons why browsers struggle with high tweet numbers.
If the network calculation was decoupled from the display it might be possible to produce adjacency matrices for larger networks without causing browsers to crash, which could then be opened in software designed to handle them (e.g. gephi). bOctober 24, 2017 at 9:17 pm #1061
I’m keen to keep a web based solution and I think it’s achievable. The current solution has a number of inefficiencies in particular the visualisation library is a very old version and a lot of processing could be saved. Hoping to have a complete rebuild ready by the end of the year…October 24, 2017 at 9:18 pm #1062
… I should add that as well as a better visualisation tool I’m keen to implement data export options for tools like gephi and nodexlNovember 20, 2017 at 12:06 pm #1090
Maybe it’s a D3.JS issue ? another similar project that have similar issue is http://flocker.outliers.es and with this harvesting tool the issue is the same (both Tags & Flocker use D3.js) I was wondering if OGMA from the guys at Linkurious could be a better engine to render big visualizations ?
see : https://linkurio.us/blog/ogma-js-library-large-scale-graph-visualization/June 19, 2019 at 2:45 pm #1345
May I ask if the mentioned Gephi/NodeXL export ist still planned? I would highly appreciate to be able to export the results to make them available for a range of tools.June 19, 2019 at 7:42 pm #1346
Planned but don’t hold your breath … in the meantime you might want to check the list of tools published here https://blogs.lse.ac.uk/impactofsocialsciences/2019/06/18/using-twitter-as-a-data-source-an-overview-of-social-media-research-tools-2019/June 20, 2019 at 9:20 am #1347
You must be logged in to reply to this topic.