From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: David Lang <david@lang.hm>
Cc: mab-wifi@lists.bufferbloat.net
Subject: Re: [mab-wifi] please post starting info
Date: Sun, 12 Feb 2017 22:00:10 +0100 [thread overview]
Message-ID: <8760kfrup1.fsf@toke.dk> (raw)
In-Reply-To: <nycvar.QRO.7.75.62.1702120134000.6590@qynat-yncgbc> (David Lang's message of "Sun, 12 Feb 2017 01:34:55 -0800 (PST)")
David Lang <david@lang.hm> writes:
> Please post links to what tests have been done, what the strategy is,
> etc.
As a starting point, see these two blog posts by Björn from a while
back:
http://www.openias.org/bayesian-wifi-rate-control
and
http://www.openias.org/bayesian-wifi-materials-and-methods
And here's some prior work:
https://people.kth.se/~alepro/pdf/infocom2014.pdf or https://arxiv.org/pdf/1307.7309.pdf
And our github repository with a bit of data and a skeleton research
paper (with only a few paragraphs of text thus far):
https://github.com/bjornsing/bayesian-wifi
And here are the algorithm implementations I was talking about:
https://www.math.univ-toulouse.fr/~agarivie/Telecom/bandits/
-Toke
prev parent reply other threads:[~2017-02-12 21:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-12 9:34 David Lang
2017-02-12 21:00 ` Toke Høiland-Jørgensen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760kfrup1.fsf@toke.dk \
--to=toke@toke.dk \
--cc=david@lang.hm \
--cc=mab-wifi@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