<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Saran,<div><br></div><div>Thank you very much for your time!</div><div>I made another variation of implementation based on your code. Instead of hard coding ErrorModel parameters, I decided to allow users to specify both specific error model, as well as error model parameters (like this ns3::RateErrorModel,ErrorUnit=ERROR_UNIT_PACKET,ErrorRate=0.9). </div><div><br></div><div>Can you check out code from "feature/topology-reader-error-model" branch on github and tell me what you think (I hope it works)?</div><div><br></div><div>Thanks again,</div><div>Alex</div><div><br><div><div>On Apr 14, 2013, at 9:18 PM, Saran Tarnoi <<a href="mailto:sarantarnoi@gmail.com">sarantarnoi@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Dear Alex,<div><br></div><div style="">I spent some time this morning to implement a simple link-error-rate configuration ability in Topology file.</div><div style="">As you have told me, it's quite simple.</div>
<div style="">I added several lines to AnnotatedTopologyReader.cc.</div><div style="">Would you kindly check it.</div><div style="">The usage is just adding some loss rate data in the most right column of the link section in the Topology file.</div>
<div style="">I will added more functions and let you consider binding it to the official branch of ndnSIM in the future.</div><div style=""><br></div><div style="">Thanks,</div><div style="">Saran Tarnoi</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/4/13 Saran Tarnoi <span dir="ltr"><<a href="mailto:sarantarnoi@gmail.com" target="_blank">sarantarnoi@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi Alex,</p><p dir="ltr">The simulation of different error rates on different links is my intention.</p><p dir="ltr">I think It does make sense to create a solution that fits well any of error model.<br>
Once ndnSim is used for the simulation of multimedia streaming, the different error models may result in different quality of the received data at a destination.<br>
I think It is positive to have this function, though it is not necessary for my case now. </p><p dir="ltr">Thanks,<br>
Saran</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Apr 13, 2013 2:40 AM, "Alex Afanasyev" <<a href="mailto:alexander.afanasyev@ucla.edu" target="_blank">alexander.afanasyev@ucla.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Saran,<br>
<br>
Do you need a precise control over which error rate is set on which link, or you want to just set the same error rate on all links?<br>
<br>
I think, it could be possible and relatively simple to add this function to AnnotatedTopologyReader. Are there just two parameters you mentioned or there is something else to be configured? I see that there are also other error models available in NS-3 (BinaryErrorModel, ListErrorModel, and ReceiveListErrorModel). Would it make sense to create a solution to allow any of these models? I'm not quite sure how exactly to extend the reader, so the solution is general enough...<br>
<br>
---<br>
Alex<br>
<br>
On Apr 11, 2013, at 11:12 PM, Saran Tarnoi <<a href="mailto:sarantarnoi@gmail.com" target="_blank">sarantarnoi@gmail.com</a>> wrote:<br>
<br>
> Dear Alex and All,<br>
><br>
> I see an example code in ns-3 that simulates simple packet loss by setting an attribute of RateErrorMode in Netdevice.<br>
> I guest that ndnSIM also support this.<br>
><br>
> There will be hundreds of links in my simulating networks.<br>
> I cannot do manually link configuration, so using topology file is my choice.<br>
> However, I have no idea how to set the ErrorRate and ErrorUnit of each link in the topology file that will be later read by using AnnotatedTopologyReader.<br>
><br>
> If you know the solution, please give me some ideas.<br>
> Thanks a lot in advance for your time.<br>
><br>
> --<br>
> Regards,<br>
> Saran<br>
><br>
> _______________________________________________<br>
> ndnSIM mailing list<br>
> <a href="mailto:ndnSIM@lists.cs.ucla.edu" target="_blank">ndnSIM@lists.cs.ucla.edu</a><br>
> <a href="http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim" target="_blank">http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim</a><br>
<br>
</blockquote></div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<div>Saran Tarnoi</div><div>Graduate Student</div><div>Department of Informatics</div><div>The Graduate University for Advanced Studies (Sokendai)</div>
<div>Tokyo, Japan</div><div><a href="http://sarantarnoi.blogspot.jp/2012/11/my-profile.html" target="_blank">http://sarantarnoi.blogspot.jp</a><br></div>
</div>
<span><annotated-topology-reader.cc></span>_______________________________________________<br>ndnSIM mailing list<br><a href="mailto:ndnSIM@lists.cs.ucla.edu">ndnSIM@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim<br></blockquote></div><br></div></body></html>