From iliamo at ucla.edu Wed Oct 1 00:02:46 2014 From: iliamo at ucla.edu (Ilya Moiseenko) Date: Wed, 1 Oct 2014 00:02:46 -0700 Subject: [ndnSIM] Distributed Application in CCN domain In-Reply-To: References: <2F3CDC59-A99B-4698-A9E6-8AE9107C6EC8@ucla.edu> Message-ID: <2B19C89B-DA49-4F8B-B760-5745C501ADBE@ucla.edu> 1) Usually, multi-threaded programs have some thread model - either a thread pool, or thread creation/destruction while keeping the current number of active threads. My point is that there is a shared data structure to keep references to the threads, and you sort of know what each thread is doing. In case there are multiple thread-pools in your process, your naming model can look like this: /localhost/chatapp/workerPool/thread1 /localhost/chatapp/workerPool/thread2 /localhost/chatapp/managerPool/thread1 /localhost/chatapp/managerPool/thread2 and so on. And you can develop a forwarding strategy that will do broadcasting for example to /localhost/chatapp/workerPool (for all threads in this pool), or multicasting with retransmission, etc. 2) Yeah, it?s MPI related. Are you sure that you need ndnSIM for testing inter-process communication inside the localhost? I would use NFD. On Sep 30, 2014, at 11:47 PM, Haroon Rashid wrote: > Some more clarifications: > > 1> By CCN I mean CCN/NDN paradigm and not the CCN daemon. How come a thread would come to know the name of another thread, because threads created by a parent process are unaware of each other. > > 2> Right now my concern is only about ndnSIM. I don?t know anything about NFD. While searching, I found there is something MPI in NS-3, but I am not sure do I need this one or something else. > > 3> By distributed application I mean an application which can be divided into some threads such that each thread work parallely. End result of such a process execution should be same as that of its serial execution. > > > On Wed, Oct 1, 2014 at 5:15 AM, Ilya Moiseenko wrote: > I don?t work with CCNx daemon, but with NFD daemon each of your threads can register its own individual name like > 1) /chatapp/thread1 > 2) /chatapp/thread2 > 3) /chatapp/thread3 > > I didn?t understand question b), but you can have intra-process communication with Interest and Data packets in NFD. > > Regarding ndnSIM, in normal mode, its core works in a single thread, and it?s not that trivial to make your simulation scenario run in multiple-threads. > You can refer to general NS-3 documentation for help. > > To find some information about ?pushing? you can find the section talking about "Command Interests" in NFD developers guide. > > Ilya > > On Sep 30, 2014, at 4:32 AM, Haroon Rashid wrote: > >> Dear All, >> >> I am curious to know how a distributed application works in CCN paradigm. Consider a scenario where an application is having three threads (logical processes) running on three nodes (three processors of a single node). Now, if these three processes want to communicate with each other for a certain reason. How can I achieve the same in CCN, i.e., (a) how processes can refer to each other (NAMING CONCERN) (b) will the format of Interest and Data packets will be same as that of current packet structure in CCN/NDN. Since, these communication messages might be very short like Hello packets or status request of a node. >> >> >> >> Is there any simple distributed application with which I can start working and come out with different possibilities of communication between processes of an application? Furthermore, I would like to mention that I want do this in ndnSIM. Currently, is there any support (libraries) in ndnSIM for doing this. >> >> >> >> Another concern I am thinking is that I know that CCN is pull based approach. Can I mix a push based approach for some messages in a distributed scenario discussed above without violating CCN paradigm? >> >> >> >> Best, >> >> Haroon Rashid >> >> >> _______________________________________________ >> ndnSIM mailing list >> ndnSIM at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > > > > -- > Haroon Rashid > > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From haroonr at iiitd.ac.in Wed Oct 1 00:14:14 2014 From: haroonr at iiitd.ac.in (Haroon Rashid) Date: Wed, 1 Oct 2014 12:44:14 +0530 Subject: [ndnSIM] Distributed Application in CCN domain In-Reply-To: <2B19C89B-DA49-4F8B-B760-5745C501ADBE@ucla.edu> References: <2F3CDC59-A99B-4698-A9E6-8AE9107C6EC8@ucla.edu> <2B19C89B-DA49-4F8B-B760-5745C501ADBE@ucla.edu> Message-ID: No, I am not sure about using ndnSIM for this experiment. From last one week I am playing with ndnSIM with an intention that this experiment might be possible in ndnSIM. So, you are suggesting me to go for NFD. Can you further explain me with which of the modules of NFD should I start with for this. This might save my time a little bit. Thanking you for your considerable amount of time. On Wed, Oct 1, 2014 at 12:32 PM, Ilya Moiseenko wrote: > 1) Usually, multi-threaded programs have some thread model - either a > thread pool, or thread creation/destruction while keeping the current > number of active threads. > My point is that there is a shared data structure to keep references to > the threads, and you sort of know what each thread is doing. > > In case there are multiple thread-pools in your process, your naming model > can look like this: > /localhost/chatapp/workerPool/thread1 > /localhost/chatapp/workerPool/thread2 > > /localhost/chatapp/managerPool/thread1 > /localhost/chatapp/managerPool/thread2 > > and so on. And you can develop a forwarding strategy that will do > broadcasting for example to /localhost/chatapp/workerPool (for all threads > in this pool), or multicasting with retransmission, etc. > > 2) Yeah, it?s MPI related. Are you sure that you need ndnSIM for testing > inter-process communication inside the localhost? I would use NFD. > > > On Sep 30, 2014, at 11:47 PM, Haroon Rashid wrote: > > Some more clarifications: > > 1> By CCN I mean CCN/NDN paradigm and not the CCN daemon. How come a > thread would come to know the name of another thread, because threads > created by a parent process are unaware of each other. > > 2> Right now my concern is only about ndnSIM. I don?t know anything > about NFD. While searching, I found there is something MPI in NS-3, but I > am not sure do I need this one or something else. > > 3> By distributed application I mean an application which can be divided > into some threads such that each thread work parallely. End result of such > a process execution should be same as that of its serial execution. > > On Wed, Oct 1, 2014 at 5:15 AM, Ilya Moiseenko wrote: > >> I don?t work with CCNx daemon, but with NFD daemon each of your threads >> can register its own individual name like >> 1) /chatapp/thread1 >> 2) /chatapp/thread2 >> 3) /chatapp/thread3 >> >> I didn?t understand question b), but you can have intra-process >> communication with Interest and Data packets in NFD. >> >> Regarding ndnSIM, in normal mode, its core works in a single thread, and >> it?s not that trivial to make your simulation scenario run in >> multiple-threads. >> You can refer to general NS-3 documentation for help. >> >> To find some information about ?pushing? you can find the section >> talking about "Command Interests" in NFD developers guide. >> >> Ilya >> >> On Sep 30, 2014, at 4:32 AM, Haroon Rashid wrote: >> >> Dear All, >> >> I am curious to know how a distributed application works in CCN paradigm. >> Consider a scenario where an application is having three threads (logical >> processes) running on three nodes (three processors of a single node). >> Now, if these three processes want to communicate with each other for a >> certain reason. How can I achieve the same in CCN, i.e., (a) how processes >> can refer to each other (NAMING CONCERN) (b) will the format of Interest >> and Data packets will be same as that of current packet structure in >> CCN/NDN. Since, these communication messages might be very short like Hello >> packets or status request of a node. >> >> >> Is there any simple distributed application with which I can start >> working and come out with different possibilities of communication between >> processes of an application? Furthermore, I would like to mention that I >> want do this in ndnSIM. Currently, is there any support (libraries) in >> ndnSIM for doing this. >> >> >> Another concern I am thinking is that I know that CCN is pull based >> approach. Can I mix a push based approach for some messages in a >> distributed scenario discussed above without violating CCN paradigm? >> >> >> Best, >> Haroon Rashid >> >> >> _______________________________________________ >> ndnSIM mailing list >> ndnSIM at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim >> >> >> > > > -- > Haroon Rashid > > > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > > -- Haroon Rashid -------------- next part -------------- An HTML attachment was scrubbed... URL: From iliamo at ucla.edu Wed Oct 1 00:26:17 2014 From: iliamo at ucla.edu (Ilya Moiseenko) Date: Wed, 1 Oct 2014 00:26:17 -0700 Subject: [ndnSIM] Distributed Application in CCN domain In-Reply-To: References: <2F3CDC59-A99B-4698-A9E6-8AE9107C6EC8@ucla.edu> <2B19C89B-DA49-4F8B-B760-5745C501ADBE@ucla.edu> Message-ID: <5DA92CFC-A32A-45BF-A59B-6C21917BB662@ucla.edu> Just install NFD - it goes in one piece. http://named-data.net/doc/NFD/current/ And write your multi-threaded application with NDN-CXX library https://github.com/named-data/ndn-cxx There are some examples of simple applications in the library sources. On Oct 1, 2014, at 12:14 AM, Haroon Rashid wrote: > No, I am not sure about using ndnSIM for this experiment. From last one week I am playing with ndnSIM with an intention that this experiment might be possible in ndnSIM. So, you are suggesting me to go for NFD. Can you further explain me with which of the modules of NFD should I start with for this. This might save my time a little bit. > > Thanking you for your considerable amount of time. > > On Wed, Oct 1, 2014 at 12:32 PM, Ilya Moiseenko wrote: > 1) Usually, multi-threaded programs have some thread model - either a thread pool, or thread creation/destruction while keeping the current number of active threads. > My point is that there is a shared data structure to keep references to the threads, and you sort of know what each thread is doing. > > In case there are multiple thread-pools in your process, your naming model can look like this: > /localhost/chatapp/workerPool/thread1 > /localhost/chatapp/workerPool/thread2 > > /localhost/chatapp/managerPool/thread1 > /localhost/chatapp/managerPool/thread2 > > and so on. And you can develop a forwarding strategy that will do broadcasting for example to /localhost/chatapp/workerPool (for all threads in this pool), or multicasting with retransmission, etc. > > 2) Yeah, it?s MPI related. Are you sure that you need ndnSIM for testing inter-process communication inside the localhost? I would use NFD. > > > On Sep 30, 2014, at 11:47 PM, Haroon Rashid wrote: > >> Some more clarifications: >> >> 1> By CCN I mean CCN/NDN paradigm and not the CCN daemon. How come a thread would come to know the name of another thread, because threads created by a parent process are unaware of each other. >> >> 2> Right now my concern is only about ndnSIM. I don?t know anything about NFD. While searching, I found there is something MPI in NS-3, but I am not sure do I need this one or something else. >> >> 3> By distributed application I mean an application which can be divided into some threads such that each thread work parallely. End result of such a process execution should be same as that of its serial execution. >> >> >> On Wed, Oct 1, 2014 at 5:15 AM, Ilya Moiseenko wrote: >> I don?t work with CCNx daemon, but with NFD daemon each of your threads can register its own individual name like >> 1) /chatapp/thread1 >> 2) /chatapp/thread2 >> 3) /chatapp/thread3 >> >> I didn?t understand question b), but you can have intra-process communication with Interest and Data packets in NFD. >> >> Regarding ndnSIM, in normal mode, its core works in a single thread, and it?s not that trivial to make your simulation scenario run in multiple-threads. >> You can refer to general NS-3 documentation for help. >> >> To find some information about ?pushing? you can find the section talking about "Command Interests" in NFD developers guide. >> >> Ilya >> >> On Sep 30, 2014, at 4:32 AM, Haroon Rashid wrote: >> >>> Dear All, >>> >>> I am curious to know how a distributed application works in CCN paradigm. Consider a scenario where an application is having three threads (logical processes) running on three nodes (three processors of a single node). Now, if these three processes want to communicate with each other for a certain reason. How can I achieve the same in CCN, i.e., (a) how processes can refer to each other (NAMING CONCERN) (b) will the format of Interest and Data packets will be same as that of current packet structure in CCN/NDN. Since, these communication messages might be very short like Hello packets or status request of a node. >>> >>> >>> >>> Is there any simple distributed application with which I can start working and come out with different possibilities of communication between processes of an application? Furthermore, I would like to mention that I want do this in ndnSIM. Currently, is there any support (libraries) in ndnSIM for doing this. >>> >>> >>> >>> Another concern I am thinking is that I know that CCN is pull based approach. Can I mix a push based approach for some messages in a distributed scenario discussed above without violating CCN paradigm? >>> >>> >>> >>> Best, >>> >>> Haroon Rashid >>> >>> >>> _______________________________________________ >>> ndnSIM mailing list >>> ndnSIM at lists.cs.ucla.edu >>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim >> >> >> >> >> -- >> Haroon Rashid >> >> >> _______________________________________________ >> ndnSIM mailing list >> ndnSIM at lists.cs.ucla.edu >> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > > > > -- > Haroon Rashid > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From emerson.barea at gmail.com Thu Oct 9 07:08:29 2014 From: emerson.barea at gmail.com (Emerson Barea) Date: Thu, 9 Oct 2014 11:08:29 -0300 Subject: [ndnSIM] NDN or CCNx version in ndnSIM Message-ID: Sorry, but I'm so confused. What's the real version of NDN ou CCNx, routing protocolo (OSPF? NLSR? Other) compatible with ndnSIM? ndnSIM already has ndn::Face for IPv4, TCP or UDP? Thank you Tocha. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Thu Oct 9 07:14:23 2014 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Thu, 9 Oct 2014 14:14:23 +0000 Subject: [ndnSIM] NDN or CCNx version in ndnSIM In-Reply-To: References: Message-ID: <904280E9-1C22-4185-AE48-097A8CAA8506@memphis.edu> ndnSIM doesn't have a dynamic routing protocol yet. Lan On Oct 9, 2014, at 9:08 AM, Emerson Barea wrote: > Sorry, but I'm so confused. What's the real version of NDN ou CCNx, routing protocolo (OSPF? NLSR? Other) compatible with ndnSIM? ndnSIM already has ndn::Face for IPv4, TCP or UDP? > > Thank you > > Tocha. > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim From emerson.barea at gmail.com Thu Oct 9 07:17:06 2014 From: emerson.barea at gmail.com (Emerson Barea) Date: Thu, 9 Oct 2014 11:17:06 -0300 Subject: [ndnSIM] NDN or CCNx version in ndnSIM In-Reply-To: <904280E9-1C22-4185-AE48-097A8CAA8506@memphis.edu> References: <904280E9-1C22-4185-AE48-097A8CAA8506@memphis.edu> Message-ID: Thank you Lan. But, what's the compatible NDN ou CCNx release? Are there ndn::Face to IPv4, TCP or UDP? Tocha. 2014-10-09 11:14 GMT-03:00 Lan Wang (lanwang) : > ndnSIM doesn't have a dynamic routing protocol yet. > > Lan > On Oct 9, 2014, at 9:08 AM, Emerson Barea > wrote: > > > Sorry, but I'm so confused. What's the real version of NDN ou CCNx, > routing protocolo (OSPF? NLSR? Other) compatible with ndnSIM? ndnSIM > already has ndn::Face for IPv4, TCP or UDP? > > > > Thank you > > > > Tocha. > > _______________________________________________ > > ndnSIM mailing list > > ndnSIM at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lanwang at memphis.edu Thu Oct 9 07:46:39 2014 From: lanwang at memphis.edu (Lan Wang (lanwang)) Date: Thu, 9 Oct 2014 14:46:39 +0000 Subject: [ndnSIM] NDN or CCNx version in ndnSIM In-Reply-To: References: <904280E9-1C22-4185-AE48-097A8CAA8506@memphis.edu> Message-ID: <6AA7B434-3387-4572-B72A-DA1A6B5C47A3@memphis.edu> I don't know the answers (and I'm not sure what you mean by compatible). Alex can help. Lan On Oct 9, 2014, at 9:17 AM, Emerson Barea > wrote: Thank you Lan. But, what's the compatible NDN ou CCNx release? Are there ndn::Face to IPv4, TCP or UDP? Tocha. 2014-10-09 11:14 GMT-03:00 Lan Wang (lanwang) >: ndnSIM doesn't have a dynamic routing protocol yet. Lan On Oct 9, 2014, at 9:08 AM, Emerson Barea > wrote: > Sorry, but I'm so confused. What's the real version of NDN ou CCNx, routing protocolo (OSPF? NLSR? Other) compatible with ndnSIM? ndnSIM already has ndn::Face for IPv4, TCP or UDP? > > Thank you > > Tocha. > _______________________________________________ > ndnSIM mailing list > ndnSIM at lists.cs.ucla.edu > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim _______________________________________________ ndnSIM mailing list ndnSIM at lists.cs.ucla.edu http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Thu Oct 9 13:55:37 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Thu, 9 Oct 2014 13:55:37 -0700 Subject: [ndnSIM] NDN or CCNx version in ndnSIM In-Reply-To: References: <904280E9-1C22-4185-AE48-097A8CAA8506@memphis.edu> Message-ID: <872D5237-BF99-400B-AC68-C5F229A9BF99@ucla.edu> Hi Tocha, On Oct 9, 2014, at 7:17 AM, Emerson Barea wrote: > Thank you Lan. > > But, what's the compatible NDN ou CCNx release? We are working on making ndnSIM compatible with the latest NDN (NFD + ndn-cxx) release, but this will take some time (all help is as always welcome). Currently, packet format is (when enabled, see http://ndnsim.net/examples.html#simple-scenario-with-pcap-dump on how to do it) compatible with the old CCNx release (0.7.x). > Are there ndn::Face to IPv4, TCP or UDP? There TcpFace and UdpFace. There are very basic examples for both in the ndnSIM source code: - examples/ndn-simple-tcp.cc - examples/ndn-simple-udp --- Alex > > Tocha. > > 2014-10-09 11:14 GMT-03:00 Lan Wang (lanwang) : > ndnSIM doesn't have a dynamic routing protocol yet. > > Lan > On Oct 9, 2014, at 9:08 AM, Emerson Barea > wrote: > > > Sorry, but I'm so confused. What's the real version of NDN ou CCNx, routing protocolo (OSPF? NLSR? Other) compatible with ndnSIM? ndnSIM already has ndn::Face for IPv4, TCP or UDP? > > > > Thank you > > > > Tocha. -------------- next part -------------- An HTML attachment was scrubbed... URL: From emerson.barea at gmail.com Thu Oct 9 16:14:48 2014 From: emerson.barea at gmail.com (Emerson Barea) Date: Thu, 9 Oct 2014 20:14:48 -0300 Subject: [ndnSIM] NDN or CCNx version in ndnSIM In-Reply-To: <872D5237-BF99-400B-AC68-C5F229A9BF99@ucla.edu> References: <904280E9-1C22-4185-AE48-097A8CAA8506@memphis.edu> <872D5237-BF99-400B-AC68-C5F229A9BF99@ucla.edu> Message-ID: Great Alex. Exactly what I wanted to know. Regards. 2014-10-09 17:55 GMT-03:00 Alex Afanasyev : > Hi Tocha, > > On Oct 9, 2014, at 7:17 AM, Emerson Barea wrote: > > Thank you Lan. > > But, what's the compatible NDN ou CCNx release? > > > We are working on making ndnSIM compatible with the latest NDN (NFD + > ndn-cxx) release, but this will take some time (all help is as always > welcome). Currently, packet format is (when enabled, see > http://ndnsim.net/examples.html#simple-scenario-with-pcap-dump on how to > do it) compatible with the old CCNx release (0.7.x). > > Are there ndn::Face to IPv4, TCP or UDP? > > > There TcpFace and UdpFace. There are very basic examples for both in the > ndnSIM source code: > > - examples/ndn-simple-tcp.cc > - examples/ndn-simple-udp > > --- > Alex > > > Tocha. > > 2014-10-09 11:14 GMT-03:00 Lan Wang (lanwang) : > >> ndnSIM doesn't have a dynamic routing protocol yet. >> >> Lan >> On Oct 9, 2014, at 9:08 AM, Emerson Barea >> wrote: >> >> > Sorry, but I'm so confused. What's the real version of NDN ou CCNx, >> routing protocolo (OSPF? NLSR? Other) compatible with ndnSIM? ndnSIM >> already has ndn::Face for IPv4, TCP or UDP? >> > >> > Thank you >> > >> > Tocha. >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From alexander.afanasyev at ucla.edu Wed Oct 15 21:09:23 2014 From: alexander.afanasyev at ucla.edu (Alex Afanasyev) Date: Wed, 15 Oct 2014 21:09:23 -0700 Subject: [ndnSIM] query about interfaces of a node In-Reply-To: References: Message-ID: <1194C6F8-C4E4-4188-AC66-87302AF6B151@ucla.edu> Hi Shahneela, You're trying to modify value, which is used for indexing purposes inside the policy (i.e., policy sorts all items based on the lifetime, which results in trivial eviction when time comes). Unfortunately, you cannot directly modify time for the items in the policy container. What you need to do instead is to remove item from the container, update the value, and then reinsert the value into the container. There is basic example of this in lfu-policy.h, though it doesn't deal with const iterators. With boost::intrusive::multiset you should be able to use `typename policy_container::iterator`. You still should not directly modify the value (as it would invalidate order), but you should be able to do the conversions. -- Alex On Oct 15, 2014, at 11:55 AM, Shahneela Naz wrote: > Dear Sir, > > I want to loop over cache contents to change their lifetime with respect to passing time.. for this I am using policy_container::iterator e.g. > > for (typename policy_container::const_iterator item = policy_container::begin (); > item != policy_container::end (); item++) > > the problem is that I can read time value against an item using get_time(&(*item)).. > but when I want to set new value to the same item it requires Container::const_iterator type... > I am finding it hard to typecast between iterator and const_iterator types which is required to set a value against an item.. > > can you kindly help me in this regard.. > > regards, > > shahneela > > > > On Fri, Sep 12, 2014 at 7:07 PM, Alex Afanasyev wrote: > > On Sep 12, 2014, at 7:16 AM, Shahneela Naz wrote: > > > Dear Users, > > > > I want to make a little change in cache-with-probability class that if a node has certain number of interfaces it should add a content. For this I want to know number of interfaces to which the node is attached. > > > > but when I try to get a node as follows > > > > Ptr n = This->GetObject(); > > > > it gives error that the function is defined out of scope. it is the problem due to virtual or inline function calls... > > > > can any one kindly help me on this.. If I want to get information related to a node while using policy traits. how can I do this.. > > Hi Shaneela, > > Where exactly you're adding this? If you're inside any of the policy methods, you can do something like: > > Ptr n = item->payload ()->GetContentStore()->template GetObject(); > > Note that there is "template" keyword before GetObject. Is is necessary, since policy and all policy methods are part of the template implementation. > > --- > Alex > > > > regards, > > > > Shahneela > > _______________________________________________ > > ndnSIM mailing list > > ndnSIM at lists.cs.ucla.edu > > http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ju.wulfheide at gmail.com Tue Oct 28 12:19:17 2014 From: ju.wulfheide at gmail.com (Julian Wulfheide) Date: Tue, 28 Oct 2014 20:19:17 +0100 Subject: [ndnSIM] Cannot launch visualizer in scenario-template project Message-ID: Hi, I installed ns-3 and ndnSim as described here: http://ndnsim.net/getting-started.html#simulating-using-ndnsim I then copied the simple example (http://ndnsim.net/examples.html#simple-scenario) into the template project (scenarios/) and tried running it with ./waf --run=ndn-simple --vis The visualizer does not show up. When I switch to the main ns-3 directory and create a ndn-simple.cc and use the same command to start the simulation, the visualizer does show up. What can I do to launch the visualizer in the scenario template? Thanks! From sarantarnoi at gmail.com Tue Oct 28 22:54:36 2014 From: sarantarnoi at gmail.com (Saran Tarnoi) Date: Wed, 29 Oct 2014 14:54:36 +0900 Subject: [ndnSIM] ndnSIM-related papers Message-ID: Hello Alex, Please add the following papers to the list of ndnSIM-related papers: - *S. Tarnoi*, K. Suksomboon, and Y. Ji, "Cooperative Routing for Content-Centric Networking," * IEEE Conference on Local Computer Networks (IEEE LCN)*, Sydney, Australia, October 2013. (DOI: 10.1109/LCN.2013.6761314 ) - *S. Tarnoi*, K. Suksomboon, W. Kumwilaisak, and Y. Ji, "Performance of probabilistic caching and cache replacement policies for content-centric networks", *IEEE LCN*, Edmonton, Canada, September 2014. (DOI: 10.1109/LCN.2014.6925761 ) - *S. Tarnoi*, W. Kumwilaisak, and Y. Ji, "Optimal cooperative routing protocol based on prefix popularity for content centric networking", *IEEE LCN*, Edmonton, Canada, September 2014. (DOI:10.1109/LCN.2014.6925805 ) Thank you. -- Regards, Saran Tarnoi -------------- next part -------------- An HTML attachment was scrubbed... URL: