Skip to content

Batman V support#345

Draft
grische wants to merge 4 commits intofreifunk:mainfrom
freifunkMUC:batman-v-support
Draft

Batman V support#345
grische wants to merge 4 commits intofreifunk:mainfrom
freifunkMUC:batman-v-support

Conversation

@grische
Copy link
Copy Markdown
Contributor

@grische grische commented Apr 17, 2026

Description

Motivation and Context

How Has This Been Tested?

Locally. Using https://gw04.ext.ffmuc.net/meshviewer.json

Screenshots/links:

It is live here: https://map.ffmuc.net/

image - image

Checklist:

  • My code follows the code style of this project. (CI will test it anyway and also needs approval)
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.

grische and others added 4 commits April 17, 2026 21:57
Batman IV neighbours expose tq, Batman V neighbours expose throughput.
Each Link can now carry either pair; UI sites pick whichever metric is
present and fall back to the other when missing.

- Link interface gains optional source_tp / target_tp (kbps) alongside
  source_tq / target_tq (now also optional; typically only one pair is
  populated per link). The field names match the yanic graph.json wire
  format.
- helper.ts: showThroughput formats kbps with SI-prefixed bit/s units;
  linkMetric returns a 0..1 normalised quality (Batman IV: tq directly;
  Batman V: log scale over 1 Mbps .. 1.2 Gbps); showLinkMetric returns
  a human-readable string for one direction; showBiDiLinkMetric joins
  both directions and drops the " - " separator when one side reports
  no metric.
- linklist, infobox/link, infobox/node, labellayer: render links with
  showBiDiLinkMetric; sort comparators wrap tq/throughput through
  linkMetric to tolerate missing values.
- forcegraph: link colour gradient and force-simulation strength use
  linkMetric so Batman V links don't destabilise the d3 simulation
  with NaN.
- forcegraph/draw and map/labellayer: gate the >= 0.99 "other" link
  recolouring branch on linkMetric so Batman V "other" links are also
  recoloured once their throughput saturates the metric range.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Batman V links carry throughput instead of TQ. Use "Transmit quality"
only when neither side reports throughput; otherwise show "Throughput".
Add the new "throughput" translation key to all shipped locales.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Previously sorted by source direction only; average both directions
so the neighbour table orders rows the same way as the link list.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Accommodate wider display strings such as "120 Mbit/s" that replaced
the previous "95%" TQ percentages on Batman V links.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@grische grische marked this pull request as draft April 17, 2026 20:26
@grische
Copy link
Copy Markdown
Contributor Author

grische commented Apr 17, 2026

Marking as draft until upstream PRs are more stabilised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant