On Thu, Oct 19, 2017 at 9:11 AM Leonardo Maccari <[email protected]> wrote:
> > Hi Federico > > https://github.com/netCommonsEU/netjson-robustness-analyser >> > > Great thanks! > > > glad you like it. > > > The second thing is just a small set of modifications to netjsongraph.js >> to show the new network. >> Source code is here https://github.com/netCommonsEU/netjsongraph.js in >> the robustness_graph branch. >> > > I checked the commits, have you only changed the examples or also the > source code of the library? > > > Just the examples. The modifications I made are only to the CSS and to the > way the d3 function is called from the HTML. > Nice, I guess we can include the most significant examples in the main netjsongraph.js repository, I'd suggest to choose one or two, what do you think? Have time to send a PR? > > >> >> One example is here (sorry for the bad certs, I have to fix it) : >> - original ninux network: https://opendata.netcommons.eu/examples/ >> - bloc-cut tree: >> https://opendata.netcommons.eu/examples/condensed-ninux.html >> >> in the second graph blue balls are blocks (cliques of nodes that resist >> to one node failure) and >> the other ones are cutpoints (if they break, network is partitioned), >> size and color changes with >> the size of the fracture they produce. >> > > At first sight it seems that the bigger circles are more important, but > after reading the description I understand that those circles are just > group of nodes, not particularly critical in the network. > Would make the orange nodes bigger instead of the blue block nodes make > sense? > > > Blue circles are important because they tell you visually how big is the > part of the network that remains disconnected if you remove one cutpoint, > without clicking on the cutpoint (which shows the number of potentially > disconnected nodes). So they are not nodes, but their size is important to > understand what is happening. maybe we can change the color, or the alpha, > or we may change the shape of the cutpoint (from circles to diamonds). > I suppose for the latter thing we need to change the library though. > Ok we can play with the alpha. Note that when I use json.dumps() whatever property of the node ends in the > "properties" section of the node, which means it is displayed. I hide them > with CSS, but maybe there is a better way of putting them somewhere else in > the node data. > We should look into add a way to do what you are doing now without using properties but other custom attributes that are in the node. > embedding the python into the topology module. This is all work in >> progress, so any feedback is >> largely welcome. >> > > Great news! > > Could you add a few more lines in the README of > netjson-robustness-analyser > <https://github.com/netCommonsEU/netjson-robustness-analyser> to explain > how to use it? > > > done. do you think it is a good idea to add it the topology module, so > when one visualizes the topology he can actually choose between several > views? I can start digging into it if you think it makes sense. > Yes, I think it would be a nice feature, we could start thinking about a generic way to create different elaborations and visualisations. To accomplish this we should think about either using functions or classes that take something in input (NetJSON NetworkGraph?), perform some work on it and return NetJSON NetworkGraph output. Once we have this defined, we can create a django setting that lists the available elaborations/visualisations (let's find a good name for this) and we can have a menu item in the visualiser that when clicked shows the available elaborations/visualisations, if the user clicks on one of this is taken to that view. Is your python module published in pypi yet? I don't see any setup.py file so I guess it's not published yet. Federico -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
