From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.etf.bg.ac.rs (mx1.etf.rs [147.91.14.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 4EBD320016C; Thu, 31 Jan 2013 02:57:45 -0800 (PST) Received: from localhost (avs2.etf.rs [147.91.14.173]) by mx1.etf.bg.ac.rs (Postfix) with ESMTP id 266FD1200D2; Thu, 31 Jan 2013 11:57:43 +0100 (CET) X-Virus-Scanned: amavisd-new at etf.rs Received: from mx2.etf.bg.ac.rs ([147.91.14.170]) by localhost (avs2.etf.rs [147.91.14.171]) (amavisd-new, port 10026) with ESMTP id UGHe1OBTm5L7; Thu, 31 Jan 2013 11:57:41 +0100 (CET) Received: from mail-ie0-f182.google.com (mail-ie0-f182.google.com [209.85.223.182]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: igorm) by mx2.etf.bg.ac.rs (Postfix) with ESMTP id 1099160112; Thu, 31 Jan 2013 11:57:40 +0100 (CET) Received: by mail-ie0-f182.google.com with SMTP id k14so2177389iea.13 for ; Thu, 31 Jan 2013 02:57:39 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.50.214.10 with SMTP id nw10mr752516igc.15.1359629859052; Thu, 31 Jan 2013 02:57:39 -0800 (PST) Received: by 10.231.229.193 with HTTP; Thu, 31 Jan 2013 02:57:38 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 11:57:38 +0100 Message-ID: From: =?ISO-8859-2?Q?Igor_Maravi=E6?= To: Andrew McGregor Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: codel@lists.bufferbloat.net, andrew.mcgregor@alliedtelesis.co.nz, bloat@lists.bufferbloat.net Subject: Re: [Codel] Python scripts from ns-3-dev GitHub repo X-BeenThere: codel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list Reply-To: igorm@etf.rs List-Id: CoDel AQM discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 10:57:45 -0000 Thanks Andrew, I managed to start simulations. Unfortunately it wasn't as easy as expected= . You forgot to add patch that added some cmd line arguments to tcp-qfp and which you're using in python script + there were some problems with python script. Anyway, Thanks :) BR Igor 2013/1/31 Andrew McGregor : > Ok, so multirun.py runs a whole set of experiments. The various commente= d > bits of code around line 85 give ways to do ranges of options in several > different ways. The options are just passed as text to tcp_qfp.cc. It r= uns > experiment cases in parallel, one for each core in your machine. > > That will produce a huge number of files, with names that tell you which > experiment they belong to and which nodes in the topology they were > collected from. Then you can analyse them. > > burstmemoryestimators.py is a graphing routine that gives you a whole lot= of > information about what happened in each run. It opens the ptrace files l= eft > by the experiment (passed as an argument, you want a file called somethin= g > like tcp_qfp-1-11-Left.pcap if there were 10 nodes in your experiment), a= nd > calculates a bunch of statistics: packet interarrival time (blue dots), > burstiness metric (red) and queue markov memory metric (green). > > The burstiness metric runs from -1 (periodic) through 0 (Poisson process)= to > +1 (1/f noise). > > The memory metric is zero if the queue is perfectly memoryless, and non-z= ero > proportional to how much memory it has. Thus it shows the queue's > contribution to interarrival time statistics. Note that a queue is > memoryless both if it is empty OR if it is completely full, and this metr= ic > is signed (negative if the queue is draining). > > It only makes sense to run this script on a leaf link; if there is more t= han > one flow, the estimators will not track flows separately and thus will no= t > make sense. > > > On Wed, Jan 30, 2013 at 11:21 PM, Igor Maravi=C4=87 wrote: >> >> Hi Andrew, >> >> I'm trying to use useful python scripts from ns-3-dev GitHub repo, but >> unsuccessfully. >> >> Could you provide some usage cases on how they should be used? >> >> BR >> Igor >> _______________________________________________ >> Codel mailing list >> Codel@lists.bufferbloat.net >> https://lists.bufferbloat.net/listinfo/codel > >