<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Anil,<div class=""><br class=""></div><div class="">The comment you’re looking applies to NS-3 logger, which suppose to be used only in debug mode to debug the simulation model and/or scenarios.</div><div class=""><br class=""></div><div class="">Answering to your original question. The post you mentioned refer to different scenario (ndn-tree-tracers), which actually uses tracers. ndn-grid-topo-plugin-loss scenario was aimed to demonstrate how to set up loss and does not have any tracers in there. If you want, you can add tracers yourself, e.g., add</div><div class=""><br class=""></div><div class=""><div class=""> ndn::L3AggregateTracer::InstallAll ("aggregate-trace.txt", Seconds (0.5));</div><div class=""> ndn::L3RateTracer::InstallAll ("rate-trace.txt", Seconds (0.5));</div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">before Simulator::Run();</div><div class=""><br class=""></div><div class="">This should produce two txt files. Without these or some other tracers, your simulation scenario is running, but not producing anything useful.</div><div class=""><br class=""></div><div class="">—</div><div class="">Alex</div><div class=""><br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Nov 12, 2014, at 5:00 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="">I found this note in log.h file which proved useful. <div class=""><br class=""></div><blockquote style="margin:0 0 0 40px;border:none;padding:0px" class=""><div class=""><font class=""><span class="" id="LC175" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * LOG functionality: macros which allow developers to</span></font></div><div class=""><font class=""><span class="" id="LC176" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * send information out on screen. All logging messages </span></font></div><div class=""><font class=""><span class="" id="LC177" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * are disabled by default. To enable selected logging </span></font></div><div class=""><font class=""><span class="" id="LC178" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * messages, use the ns3::LogComponentEnable</span></font></div><div class=""><font class=""><span class="" id="LC179" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * function or use the NS_LOG environment variable </span></font></div><div class=""><font class=""><span class="" id="LC180" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> *</span></font></div><div class=""><font class=""><span class="" id="LC181" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * Use the environment variable NS_LOG to define a ':'-separated list of</span></font></div><div class=""><font class=""><span class="" id="LC182" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * logging components to enable. For example (using bash syntax), </span></font></div><div class=""><font class=""><span class="" id="LC183" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * NS_LOG="OlsrAgent" would enable one component at all log levels. </span></font></div><div class=""><font class=""><span class="" id="LC184" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * NS_LOG="OlsrAgent:Ipv4L3Protocol" would enable two components, </span></font></div><div class=""><font class=""><span class="" id="LC185" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * at all log levels, etc.</span></font></div><div class=""><font class=""><span class="" id="LC186" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * NS_LOG="*" will enable all available log components at all levels.</span></font></div><div class=""><font class=""><span class="" id="LC187" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> *</span></font></div><div class=""><font class=""><span class="" id="LC188" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * To control more selectively the log levels for each component, use</span></font></div><div class=""><font class=""><span class="" id="LC189" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * this syntax: NS_LOG='Component1=func|warn:Component2=error|debug'</span></font></div><div class=""><font class=""><span class="" id="LC190" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * This example would enable the 'func', and 'warn' log</span></font></div><div class=""><font class=""><span class="" id="LC191" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * levels for 'Component1' and the 'error' and 'debug' log levels</span></font></div><div class=""><font class=""><span class="" id="LC192" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * for 'Component2'. The wildcard can be used here as well. For example</span></font></div><div class=""><font class=""><span class="" id="LC193" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * NS_LOG='*=level_all|prefix' would enable all log levels and prefix all</span></font></div><div class=""><font class=""><span class="" id="LC194" style="display:inline;font-family:Menlo,Monaco,Consolas,'Courier New',monospace;font-size:12px;line-height:16px;white-space:pre"> * prints with the component and function names.</span></font></div></blockquote><div class=""><br class=""></div><div class="">With this, we can enable log at component level. </div><div class=""><br class=""></div><div class="">/anil.</div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sun, Nov 9, 2014 at 12:30 AM, Anil Jangam <span dir="ltr" class=""><<a href="mailto:anilj.mailing@gmail.com" target="_blank" class="">anilj.mailing@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Thanks Spyros. This worked. </div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br class=""><div class="gmail_quote">On Sat, Nov 8, 2014 at 5:51 PM, Spyridon (Spyros) Mastorakis <span dir="ltr" class=""><<a href="mailto:spiros.mastorakis@gmail.com" target="_blank" class="">spiros.mastorakis@gmail.com</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="">Hello Anil,<div class=""><br class=""></div><div class="">you should enable the logging component. You can do that by typing:</div><div class=""><br class=""></div><div class="">NS_LOG=ndn.Consumer:ndn.Produce ./waf --run=ndn-grid-topo-plugin-loss</div><div class=""><br class=""></div><div class="">This worked for me and should also work for you.</div><div class=""><br class=""></div><div class="">Kind regards,</div><div class="">Spyros </div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class=""><div class=""><div class="">On Nov 8, 2014, at 2:24 PM, Anil Jangam <<a href="mailto:anilj.mailing@gmail.com" target="_blank" class="">anilj.mailing@gmail.com</a>> wrote:</div><br class=""></div></div><div class=""><div class=""><div class=""><div dir="ltr" class=""><div class="">Hi Alex,</div><div class=""><br class=""></div><div class="">I trace back to one of your replies in past. <a href="http://www.lists.cs.ucla.edu/pipermail/ndnsim/2013-January/000040.html" target="_blank" class="">http://www.lists.cs.ucla.edu/pipermail/ndnsim/2013-January/000040.html</a></div><div class=""><br class=""></div><div class="">When I run one of the example scenarios, I am not sure it is producing any output or if it actually running. The command with waf helper just produces below output. It apparently does not run the use case. </div><div class=""><br class=""></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px" class=""><div class="">./waf --run=ndn-grid-topo-plugin-loss</div><div class="">Waf: Entering directory `/home/anilj1/sandbox/ndnSIM/ns-3/build'</div><div class="">Waf: Leaving directory `/home/anilj1/sandbox/ndnSIM/ns-3//ns-3/build'</div><div class="">'build' finished successfully (1.877s)</div></blockquote><div class=""><br class=""></div><div class="">However, when I run the same command with --vis option it pops up the GUI, and I am able to see the GUI. On F3, I see some action on the GUI. However, this also does not generate any of the trace files you have mentioned in above link. </div><div class=""><br class=""></div><div class="">Can you pls point to correct steps? Does command line (non GUI) produces the logs elsewhere, which I am not aware of?</div><div class=""><br class=""></div><div class="">/anil.</div><div class=""><br class=""></div></div></div></div>
_______________________________________________<br class="">ndnSIM mailing list<br class=""><a href="mailto:ndnSIM@lists.cs.ucla.edu" target="_blank" class="">ndnSIM@lists.cs.ucla.edu</a><br class=""><a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim" target="_blank" class="">http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim</a><br class=""></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></div>
</div></div></blockquote></div><br class=""></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=""></div></div></body></html>