From: "Martin Hundebøll" <martin@hundeboll.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Alfred batadv-vis json conformance
Date: Thu, 03 Oct 2013 08:09:08 +0200 [thread overview]
Message-ID: <524D0A04.4090702@hundeboll.net> (raw)
In-Reply-To: <20131002160106.GA1939@neomailbox.net>
On 2013-10-02 18:01, Antonio Quartulli wrote:
> On Wed, Oct 02, 2013 at 03:05:48PM +0200, Simon Wunderlich wrote:
>>> > >I'm also wondering if label and gateway could have more meaningful
>>> > >names? TQ and host? Also, is TT the best?
>> >
>> >Hm, that is a good question. We also have the batman v with new metrics
>> >coming up, I'm not sure how to handle these (maybe Antonio has some
>> >idea?). It is not the TQ-value in the label after all, but some kind of
>> >ETX-converted value (255/TQ if i remember correctly).
> I think the ETX stuff comes from OLSR (but I don't know the details).
>
> I agree with Simon that we should find a generic name (e.g. metric ?) but I am
> not sure we can represent this value in a "algorithm-generic" fashion (and maybe
> we don't want to).
May I suggest that the cjson output includes an entry to tell the
version of the batman-algorithm?
Users might want to do different map overlays (or whatever) depending on
the available metric(s).
--
Kind Regards
Martin Hundebøll
Frederiks Allé 99, 1.th
8000 Aarhus C
Denmark
+45 61 65 54 61
martin@hundeboll.net
next prev parent reply other threads:[~2013-10-03 6:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-01 20:26 [B.A.T.M.A.N.] Alfred batadv-vis json conformance Andrew Lunn
2013-10-02 13:05 ` Simon Wunderlich
2013-10-02 13:36 ` Andrew Lunn
2013-10-06 8:35 ` Nicolás Echániz
2013-10-07 9:00 ` Andrew Lunn
2013-10-02 16:01 ` Antonio Quartulli
2013-10-03 6:09 ` Martin Hundebøll [this message]
2013-10-03 8:11 ` Andrew Lunn
2013-10-03 8:22 ` Antonio Quartulli
2013-10-03 8:53 ` Andrew Lunn
2013-10-03 9:00 ` Antonio Quartulli
2013-10-03 9:05 ` Andrew Lunn
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=524D0A04.4090702@hundeboll.net \
--to=martin@hundeboll.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.