graph-tool August 2015

graph-tool@skewed.de

9 participants
22 discussions

graph-tool graphml and networkx
by tcb 17 Aug '15

17 Aug '15

Hi, I am trying to read the graphml output of graph-tool's graphml using networkx. https://github.com/networkx/networkx/issues/843 Unfortunately this does not work with any of the vector_* type property maps which graph-tool uses. Have you encountered this issue before? It seems the right thing to do might be to extend your graphml to hold the vector_* attributes as detailed: http://graphml.graphdrawing.org/primer/graphml-primer.html#EXT Is there some reason why it was done the way it is? How do you manage read/writing graphml data to other tools? In the meantime, it might be possible to hack some read support for graph-tool's xml into networkx. To this end, could you please advise how to parse the 'key1' data (should be two floats) <node id="n1"> <data key="key0">6</data> <data key="key1">0x1.5c71d0cb8d943p+3, 0x1.70db7f4083655p+3</data> </node> thanks - -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com… Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.

4 12

Please help with my licensing headache!
by monkeynut 04 Aug '15

04 Aug '15

I have been working on a toolkit for network security analysis. I intended to license it with a BSD license, but I ideally want the freedom to change the license in future versions as I see fit. So far all the dependencies have been BSD, MIT, or Boost license so I have not really had any concerns. However, for performance reasons I need to switch out of using networkx and graph-tool seems extremely attractive (great quality, API, openmp use etc.). I originally chose Networkx over graph-tool purely for the liberal license and not having to spend much effort on license considerations. The toolkit itself has (currently) 11 major components which can be theoretically self-standing but are particularly useful together (do they count as one, can they have seperate licenses?). Two of these components require the use of a graph library. I have now spent weeks reading the FSF, GPLv3, BSD, Boost etc. license pages and guides and all sorts of stuff. Plenty of (people claiming to be) lawyers who all disagree about what to do and where I stand (most of it involving disagreements about derivative works). I would love to just get back to design and development, something I'm actually good at! The obvious solution would be just to GPL everything but given the amount of pain the draconian and anti-liberal GPLv3 has given me, I don't want to inflict that on anyone else in the future if possible. Additionally, there are a number of people I would like to work with who would be unable due to contractual contraints to risk using my project if it were GPL. Has anybody had a similar situation and how have you resolved it? Can anybody help? Tiago, if you could give me any advice about your intentions behind choosing GPLv3 over e.g. LGPL and how my project relates to that (is this something we should discuss off-line)? Thanks in advance for any help. -- View this message in context: http://main-discussion-list-for-the-graph-tool-project.982480.n3.nabble.com… Sent from the Main discussion list for the graph-tool project mailing list archive at Nabble.com.

2 6

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

graph-tool August 2015