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: Comment <comment@noreply.github.com>,
	flent-users <flent-users@flent.org>
Subject: Re: [Flent-users] [tohojo/flent] Aborting plotting due to error (#187)
Date: Tue, 15 Oct 2019 07:07:58 -0700	[thread overview]
Message-ID: <tohojo/flent/issues/187/542230661@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/187@github.com>


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

acdcjavier <notifications@github.com> writes:

>> acdcjavier <notifications@github.com> writes:
>> > acdcjavier ***@***.***> writes: > > Could you please try the git version of Flent and see if the same bug is present there? You should be able to just clone the repository and use the `run-flent` script in place of the system-installed version. Ok, but do I need to remove flent system-installed version? > Not for testing; you can just run the ./run-flent script and it'll ignore the system-installed version... Thanks but got this error Sorry, Flent requires v3.5 or later of Python. But I have phyton 3.7...
>> Ah yes, that is a bug. I just pushed a fix for this, so please do a 'git pull' and then try again :)
>
> Working now using RRUL testing, it creates the .png file 
> But when I opened the flent.gz file using GUI interface, it freeze Ubuntu and must force reboot.
>
> Also, when I perform a "Ping" test, got this error:
>
> ./run-flent ping -p all_scaled -l 10 -H netperf.bufferbloat.net -t text-to-be-included-in-plot -o prueba.png
>
> Started Flent 1.9.9-git-edfc0e0 using Python 3.7.5rc1.
> Starting ping test. Expected run time: 10 seconds.
> Data file written to ./ping-2019-10-15T105435.560049.text-to-be-included-in-plot.flent.gz
> Initialised matplotlib v3.0.2 on numpy v1.16.2.
> ERROR: Error loading plotter: Unable to find plot configuration
> 'all_scaled'

This means exactly what it says - there's not 'all_scaled' plot for the
'ping' test. So try with '-p ping' instead :)


-- 
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/187#issuecomment-542230661

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

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

_______________________________________________
Flent-users mailing list
Flent-users@flent.org
http://flent.org/mailman/listinfo/flent-users_flent.org

  parent reply	other threads:[~2019-10-15 14:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <tohojo/flent/issues/187@github.com>
2019-10-10 19:43 ` Toke Høiland-Jørgensen
2019-10-15 11:39 ` Toke Høiland-Jørgensen
2019-10-15 12:18 ` Toke Høiland-Jørgensen
2019-10-15 13:00 ` Toke Høiland-Jørgensen
2019-10-15 14:07 ` Toke Høiland-Jørgensen [this message]
2021-01-13 16:04 ` [Flent-users] " 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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/187/542230661@github.com \
    --to=notifications@github.com \
    --cc=comment@noreply.github.com \
    --cc=flent-users@flent.org \
    --cc=flent@noreply.github.com \
    --cc=reply+AHVNJP3ZRFOWPD4EPPGXXON3WMCT5EVBNHHB4FM33Y@reply.github.com \
    --subject='Re: [Flent-users] [tohojo/flent] Aborting plotting due to error (#187)' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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