The Repast Networks encapsulate JUNG graph objects, so in a sense they are JUNG networks. The Repast Network interface is implemented by an abstract class – JungNetwork, which in turn is extended by two default classes in Repast - the
DirectedJungNetwork and UndirectedJungNetwork. These two classes create a JUNG graph instance internally DirectedOrderedSparseMultigraph and UndirectedOrderedSparseMultigraph, respectively. The Repast Network and JungNetwork classes provide a number of Network
access methods for adding edges and vertices, etc. You can also access the JUNG graph object directly via JungNetwork.getGraph() and then access any of the JUNG API through the graph object.
The reason why Repast network support is stated as supplied by JUNG is simply because it uses JUNG to supply all of the internal network functionality of the Repast Network classes. Users are free to use any other network/graph implementation
in their own custom network classes as long as it implements the Repast Network interface.
From: Juan Moreno Oto [mailto:[hidden email]]
Sent: Saturday, June 17, 2017 11:08 AM To:[hidden email] Subject: [Repast-interest] Repast Networks vs. Jung graphs/networks
In Repast simphony we have networks as one of the available types of projections.
On the other hand, the Repast documentation says that “The default support for networks is supplied by the excellent library JUNG”
¿Does it mean that a Repast Network is the same than a Jung graph/network?
If the answer in no. When is it better to use the one or the other?