<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 26, 2016, at 8:42 PM, Anil Jangam <<a href="mailto:anilj.mailing@gmail.com" class="">anilj.mailing@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><div class="">Hi Spyros,<br class=""><br class=""></div>I was curious to know if those topology diagrams were created manually or were they created by some 'R'script? I could generate some of the graphs using the provided Rscripts though. <br class=""></div></div></div></blockquote><div><br class=""></div><div>No, the topology diagrams on <a href="http://ndnsim.net" class="">ndnsim.net</a> website are created manually using aafig module (ascii art to svg converter). You can see the source code of the pages here <a href="http://ndnsim.net/2.1/_sources/metric.txt" class="">http://ndnsim.net/2.1/_sources/metric.txt</a> or in github repo. For large topologies, it is better to use graphviz dot (neato, twopi, circo, fdp, or sfdp) tool to visualize arbitrary topologies. For example, you could use AnnotatedTopology:: SaveGraphviz method (<a href="http://ndnsim.net/2.1/doxygen/classns3_1_1AnnotatedTopologyReader.html#a2078a690442885c1c3e2ae5fd9c83895" class="">http://ndnsim.net/2.1/doxygen/classns3_1_1AnnotatedTopologyReader.html#a2078a690442885c1c3e2ae5fd9c83895</a>) or create it manually.</div><div><br class=""></div><div>--</div><div>Alex</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div>/anil.<br class=""><br class=""><div class=""><div class=""><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, Mar 26, 2016 at 10:01 AM, Spyridon (Spyros) Mastorakis <span dir="ltr" class=""><<a href="mailto:mastorakis@cs.ucla.edu" target="_blank" class="">mastorakis@cs.ucla.edu</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hi Asif,<div class=""><br class=""></div><div class="">the internal face is the face that NFD uses to communicate with its managers (used for command Interests). You can think of the netDeviceFace as the network layer interfaces of a router. The ndnFace refers to the ndnSIM specific implementation of the ndn-cxx face. The appFace refers to the face of an ndnSIM application receiving Data and Interest packets. The face ids are used to distinguish among the different faces. You can take a look here as well:</div><div class=""><br class=""></div><div class=""><a href="http://ndnsim.net/2.1/metric.html" target="_blank" class="">http://ndnsim.net/2.1/metric.html</a></div><div class=""><br class=""></div><div class="">What application you were running when you obtained this trace file?</div><div class=""><br class=""></div><div class="">Thanks,</div></div></blockquote></div><br class=""></div></div></div></div>
_______________________________________________<br class="">ndnSIM mailing list<br class=""><a href="mailto:ndnSIM@lists.cs.ucla.edu" class="">ndnSIM@lists.cs.ucla.edu</a><br class="">http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim<br class=""></div></blockquote></div><br class=""></body></html>