[ndnSIM] [Fwd: Replacement metric]

Alex Afanasyev alexander.afanasyev at ucla.edu
Fri Aug 30 10:08:47 PDT 2013

Hi Andriana,

The code looks right, and the whole problem seem to be because of a small problem with "connect" implementation in your tracer.  The producer application is not "aggregated" (in NS-3 terms) on the node, rather than it is installed on a Node as an application.  While it seem the same, it actually requires a slightly different way to connect the trace.  The working example is in utils/tracers/ndn-app-delay-tracer.cc:231 and in your case ndn-producer-tracer.cc on line 105 could look something like:

  Config::ConnectWithoutContext ("/NodeList/"+m_node+"/ApplicationList/*/ServerHits",
                                 MakeCallback (&ProducerTracer::ServerHits, this));

Can you try it and if it doesn't fix the problem, I'll try to dig more.


On Aug 29, 2013, at 1:55 PM, ioannoa at scss.tcd.ie wrote:

> Hello all again,
> further to my previous question I have tried to also implement a metric in
> the producer to hold the hits made each time regarding the interests, i.e.
> how many interests were satisfied by the producer if not from a content
> store of a node along the way.
> i've tried to use the tracers available and made the included files.
> Unfortunately, even though my file is created, the metric is always 0.
> Furthermore, having a print in the function updating the metric, it seems
> that it is never called! The function is set using the TracedCallback.
> Now, i know that the tracer is made for all nodes and not just specifying
> one, but i have tried this for an operation similar to the cache misses or
> cache hits at the content store and still did not work, so can't see that
> as a problem.
> I have included the files. If someone has a hint, please let me know!
> p.s. the changes in the producer files can be found using //(+) in the
> finder!
> Kind regards,
> Andriana.
> ---------------------------- Original Message ----------------------------
> Subject: Replacement metric
> From:    ioannoa at scss.tcd.ie
> Date:    Thu, August 29, 2013 11:07 am
> To:      ndnsim at lists.cs.ucla.edu
> --------------------------------------------------------------------------
> Hello all,
> I am trying to implement a replacement metric, similar to the one used for
> cache hits and cache misses in content store. My issue is though that
> replacement counts are not calculated in the content store but rather to
> each replacement policy used. Would someone advice which way would be
> proper to try to do so? I have found this post related to:
> http://www.lists.cs.ucla.edu/pipermail/ndnsim/2012-December/000007.html
> would the creation of a new policy be the way to go?
> Thanks in advance.
> Kind regards,
> Andriana.<ndn-producer-tracer.cc><ndn-producer-tracer.h><ndn-producer.cc><ndn-producer.h>_______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim

More information about the ndnSIM mailing list