Conversation
Adds rti.rs: a grid solver that treats each transmitter-receiver link as an ellipse and accumulates per-cell evidence from links whose response deviates from their own resting level. 826 lines, 22 tests. Pure functions over coordinates and floats -- it takes observations and a config and returns an estimate, with no dependency on any other module here. The adapter that feeds it live link metrics is deliberately NOT included, because it needs both the per-link table and the room footprint, neither of which is upstream yet. This lands the estimator and its tests; the consumer follows. HONEST LIMITATION, stated because it would be easy to omit. The elliptical link-line kernel is the standard formulation, and on this deployment it did not hold: measured 2026-08-28, per-link response was INVERSELY related to link-line distance -- the opposite of what the model predicts. That measurement was taken in a single room with three co-located nodes and does not necessarily generalise to a distributed fleet, so it falsifies the model in that configuration rather than in general. The code is therefore offered as a correct and tested implementation of a published technique, not as a demonstration that the technique works in a home. Anyone adopting it should validate the kernel against their own geometry before trusting an estimate, and the normalise_response/temporal_authority helpers are useful independently of whether the ellipse model holds. Co-Authored-By: claude-flow <ruv@ruv.net>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds rti.rs: a grid solver that treats each transmitter-receiver link as an
ellipse and accumulates per-cell evidence from links whose response deviates
from their own resting level. 826 lines, 22 tests.
Pure functions over coordinates and floats -- it takes observations and a
config and returns an estimate, with no dependency on any other module here.
The adapter that feeds it live link metrics is deliberately NOT included,
because it needs both the per-link table and the room footprint, neither of
which is upstream yet. This lands the estimator and its tests; the consumer
follows.
HONEST LIMITATION, stated because it would be easy to omit. The elliptical
link-line kernel is the standard formulation, and on this deployment it did not
hold: measured 2026-08-28, per-link response was INVERSELY related to link-line
distance -- the opposite of what the model predicts. That measurement was taken
in a single room with three co-located nodes and does not necessarily
generalise to a distributed fleet, so it falsifies the model in that
configuration rather than in general.
The code is therefore offered as a correct and tested implementation of a
published technique, not as a demonstration that the technique works in a home.
Anyone adopting it should validate the kernel against their own geometry before
trusting an estimate, and the normalise_response/temporal_authority helpers are
useful independently of whether the ellipse model holds.
Rebased onto current
mainbefore opening: staged before today's seven merges, so it needed replaying to avoid reading as a revert of them. Clean rebase, no files deleted.