From: George Burdell <gb@teklibre.net>
To: starlink@lists.bufferbloat.net
Subject: [Starlink] Open Data
Date: Wed, 9 Jun 2021 17:35:26 +0000 [thread overview]
Message-ID: <20210609173526.GA17949@mail.taht.net> (raw)
For those new around here, bufferbloat.net project members have
always believed in open code and open data. Been a bit coy this
month... but... for your research....
All the data collected so far (flent and packet captures)
is available via rsync to these git repositories, and we consider
to be "public", just distributed via an older means called rsync.
mkdir starlink; cd starlink; rsync -av fremont.starlink.taht.net::starlink .
cd ..; mkdir starlink_cap; rsync -av fremont.starlink.taht.net::starlink_cap .
See the git logbook for pithy details.
Useful things to extract from this data are tons of flent comparison
plots and from the packet captures, interrarrival times, loss
and ecn markings. And who knows what else.
All the tests can be easily repeated from anywhere, full source code is provided.
next reply other threads:[~2021-06-09 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-09 17:35 George Burdell [this message]
2021-06-09 19:48 ` Nathan Owens
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.bufferbloat.net/postorius/lists/starlink.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210609173526.GA17949@mail.taht.net \
--to=gb@teklibre.net \
--cc=starlink@lists.bufferbloat.net \
/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