[ndnSIM] L3RateTracer Kilobyte values for OutInterests

[Klaus Schneider]

Hi Alexander,

thank you for looking at this.

I just did a fresh install of ndnSim in order to reproduce the behavior:

> mkdir ndnSIM2
> cd ndnSIM2
> git clone https://github.com/named-data/ndn-cxx.git ndn-cxx
> git clone https://github.com/cawka/ns-3-dev-ndnSIM.git ns-3
> git clone https://github.com/cawka/pybindgen.git pybindgen
> git clone https://github.com/named-data/ndnSIM.git ns-3/src/ndnSIM
> cd ndnSIM2/ndn-cxx
> ./waf configure
> ./waf
> sudo ./waf install
> cd ../ns-3
> ./waf configure --disable-python --enable-examples
> ./waf

Then you can just run the "ndn-tree-tracers" example and look at the 
output (which is the same as below).

> ./waf --run=ndn-tree-tracers
> cat rate-trace.txt | grep "\sOutInterests" | grep "netDeviceFace"

I hope this helps.

Klaus


On 11.04.2015 20:49, Alex Afanasyev wrote:
>
>> On Apr 6, 2015, at 6:44 AM, Klaus Schneider <klaus.schneider at uni-bamberg.de> wrote:
>>
>> Hi everyone,
>>
>> I have noticed that in the result file of the L3RateTracer outgoing interest packets ("OutInterests") sometimes have lack the value for "Kilobytes"/"KilobytesRaw". However, the value for "Packets"/"PacketsRaw" seems to always be there.
>>
>> In my example (see appendix) I used the broadcast strategy and the throughput value ("OutInterests") only exists for two of the faces.
>>
>> You can reproduce that by running the ndn-tree-tracers.cpp example (http://ndnsim.net/2.0/metric.html). In this case the Kilobytes values for OutInterests of the leaf nodes are missing.
>>
>> $ cat rate-trace.txt | grep "\sOutInterests" | grep "netDeviceFace"
>>
>>> Time    Node    FaceId  FaceDescr   Type    Packets Kilobytes   PacketRaw   KilobytesRaw
>>> 19	leaf-1	256	netDeviceFace://	OutInterests	100	0	50	0
>>> 19	leaf-2	256	netDeviceFace://	OutInterests	100	0	50	0
>>> 19	leaf-3	256	netDeviceFace://	OutInterests	100	0	50	0
>>> 19	leaf-4	256	netDeviceFace://	OutInterests	100	0	50	0
>>> 19	rtr-1	256	netDeviceFace://	OutInterests	0	0	0	0
>>> 19	rtr-1	258	netDeviceFace://	OutInterests	200	6.44531	100	3.22266
>>> 19	rtr-1	257	netDeviceFace://	OutInterests	0	0	0	0
>>> 19	rtr-2	256	netDeviceFace://	OutInterests	0	0	0	0
>>> 19	rtr-2	257	netDeviceFace://	OutInterests	0	0	0	0
>>> 19	rtr-2	258	netDeviceFace://	OutInterests	200	6.44531	100	3.22266
>>> 19	root	256	netDeviceFace://	OutInterests	0	0	0	0
>>> 19	root	257	netDeviceFace://	OutInterests	0	0	0	0
>>
>> Is this behavior expected?
>
> This doesn’t look right…  Can you give us a simple scenario that reproduces this output?
>
> —
> Alex
>
>>
>> Best regards,
>> Klaus
>>
>>
>> --
>> Klaus Schneider
>>
>> Mail: klaus.schneider at uni-bamberg.de
>> LinkedIn: https://www.linkedin.com/in/schneiderklaus
>> <rates_bc.pdf>_______________________________________________
>> ndnSIM mailing list
>> ndnSIM at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>

-- 
Klaus Schneider

Mail: klaus.schneider at uni-bamberg.de
LinkedIn: https://www.linkedin.com/in/schneiderklaus