Flent-users discussion archives
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <notifications@github.com>
To: tohojo/flent <flent@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [Flent-users] [tohojo/flent] completion delay for an iperf script (#138)
Date: Fri, 08 Jun 2018 03:20:51 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/138/395718604@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/138@github.com>

[-- Attachment #1.1: Type: text/plain, Size: 2109 bytes --]

Matthieu Coudron <notifications@github.com> writes:

> so I managed to pass a negative length but it fails with 
> ```
> NetperfDemoRunner TCP netperf::5 finished
> Runner aggregation finished
> Data file written to ./tcp_iperf_delay-2018-06-08T154503.539961.flent.gz.
> Creating new PlotFormatter
> CACHEDIR=/home/teto/.cache/matplotlib
> Using fontManager instance from /home/teto/.cache/matplotlib/fontList.json
> backend GTK3Cairo version unknown
> Initialised matplotlib v2.2.2 on numpy v1.14.2.
> Traceback (most recent call last):
>   File "/run/user/1000/tmp.84zoa9EUe9/bin/flent", line 11, in <module>
>     load_entry_point('flent', 'console_scripts', 'flent')()
>   File "/home/teto/flent/flent/__init__.py", line 59, in run_flent
>     b.run()
>   File "/home/teto/flent/flent/batch.py", line 617, in run
>     return self.run_test(self.settings, self.settings.DATA_DIR, True)
>   File "/home/teto/flent/flent/batch.py", line 525, in run_test
>     formatter.format([res])
>   File "/home/teto/flent/flent/formatters.py", line 396, in format
>     self.init_plots(results)
>   File "/home/teto/flent/flent/formatters.py", line 381, in init_plots
>     self.plotter.init()
>   File "/home/teto/flent/flent/plotters.py", line 1814, in init
>     s_unit = self.data_config[s['data']]['units']
> KeyError: 'TCP netperf'
> ```
> on https://github.com/tohojo/flent/compare/master...teto:iperf_delay?expand=1
> Ideally I would like to run several times one tcp transfer but I
> thought running several at once would allow me to test the cdf_combine
> faster.

Ah. Using 'duplicates' changes the name (adds ::1, ::2, etc). You can
use a glob in the plot definition to grab all of them.

To run the test multiple times, you'd just repeat the Flent invocation
(or use the batch facility and the 'repetitions' keyword). That will
produce a bunch of data files that you then plot at once in a separate
plot definition.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

[-- Attachment #1.2: Type: text/html, Size: 7759 bytes --]

[-- Attachment #2: Type: text/plain, Size: 151 bytes --]

Flent-users mailing list

  parent reply	other threads:[~2018-06-08 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tohojo/flent/issues/138@github.com>
2018-06-07  8:57 ` Toke Høiland-Jørgensen
2018-06-07 10:01 ` Toke Høiland-Jørgensen
2018-06-08 10:20 ` Toke Høiland-Jørgensen [this message]
2018-06-08 10:55 ` Toke Høiland-Jørgensen
2018-06-11  9:15 ` Toke Høiland-Jørgensen
2018-06-11  9:36 ` Toke Høiland-Jørgensen
2018-06-11 12:20 ` Toke Høiland-Jørgensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://lists.flent.org/postorius/lists/flent-users.flent.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=tohojo/flent/issues/138/395718604@github.com \
    --to=notifications@github.com \
    --cc=flent@noreply.github.com \
    --cc=reply+01ead4bf6460ed0ad91390525e629cd06981206e632a278c92cf0000000117321a8392a169ce13aceaa7@reply.github.com \
    --cc=subscribed@noreply.github.com \
    --subject='Re: [Flent-users] [tohojo/flent] completion delay for an iperf script (#138)' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox