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] feature: positional data/plots and handling disconnects. (#199)
Date: Tue, 03 Mar 2020 11:25:28 -0800 [thread overview]
Message-ID: <tohojo/flent/issues/199/594124179@github.com> (raw)
In-Reply-To: <tohojo/flent/issues/199@github.com>
[-- Attachment #1.1: Type: text/plain, Size: 1538 bytes --]
Jumziey <notifications@github.com> writes:
> I would like to get some good data on how tcp uploads/downloads works
> from a boat in certain areas while moving around with different
> solutions.
>
> I did a naive test with flent running the tcp_download tcp_1up_noping
>tests but had a problem with the test just completely shutting down if
>i lost connection due to getting into a blind spot. Is this a
>configuration issue or is there some extra coding required to fix this?
Well, TCP will tend to do that - depending on what you mean by "lost
connection". What would you like to have happen instead?
> Would be great if there was some native support for presenting gps
> data as well on a seachart ala openseamap or similar.
It should already be possible to embed a starting location in the
metadata (just add it as a test parameter and it'll be saved). But I
assume you mean you want periodic location data collected while the test
is running, right?
> I could certainly look into implementing these features, but would
> like some feedback on my thoughts before just forking and trying it on
> my own.
The location data collection should be straight-forward enough, given a
suitable source of location data; no idea what it would take to
integrate a map service into the GUI, though... But happy to take
patches if you do give it a shot :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/tohojo/flent/issues/199#issuecomment-594124179
[-- Attachment #1.2: Type: text/html, Size: 3070 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:[~2020-03-03 19:26 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tohojo/flent/issues/199@github.com>]
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/199/594124179@github.com \
--to=notifications@github.com \
--cc=flent@noreply.github.com \
--cc=reply+AHVNJPYXXPT7PLVPPKACDPF4NKICREVBNHHCEQPGPM@reply.github.com \
--cc=subscribed@noreply.github.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox