Rabbit-RobotNav: History-Aware Error Diagnosis
and Recovery Anchors for Vision-Language Navigation

MASTER'S THESIS PROJECT · WORK IN PROGRESS

Jinghai Li

Long-horizon ground-robot navigation research · 2026

Author-supplied proposed framework: RGB, depth, language and pose feed semantic-spatial memory; instruction, history and transition consistency support diagnosis, anchor selection and a planned recovery loop. Depicted components are not all validated.
Research framework. History as diagnostic evidence and a recovery anchor. The author-supplied diagram shows the intended system; trusted memory, integrated module performance, and autonomous recovery remain under validation. View full-size diagram.

Abstract

Long-horizon vision-language navigation requires knowing not only where a robot is, but whether its progress remains consistent with the instruction. Rabbit-RobotNav investigates historical semantic-spatial evidence for deviation diagnosis and recovery-anchor selection without accessing evaluation labels. The framework separates recorded observations from trusted memory and checks instruction, history, and transition consistency. Controlled MP3D cases provide preliminary diagnostic evidence; real-robot experiments expose unstable object identity and insufficient heading fusion during room mapping. Reliable mobile mapping, navigation gains, and autonomous recovery remain unverified.

Method Overview

  1. Record before trusting. Preserve time-stamped observations, poses, and source records. Repeated detections do not establish physical identity or a reliable landmark.
  2. Diagnose with sufficient evidence. Compare instruction, history, and spatial transitions. The read-only adapter explicitly reports insufficient evidence instead of treating a missing signal as normal navigation.
  3. Recover from a supported state. Investigate an earlier trustworthy state as an anchor. Real-robot anchor validation and recovery execution are still open.

From Observations to Reliable History

Archived real-robot sessions now replay into 1,149 raw states and 3,477 semantic observations. These are repeated observations, not unique objects. None has yet been admitted as a trusted state or landmark.

Three separate archived robot sessions: camera-pose traces and unverified chair projections. There are zero confirmed metric landmarks; no walls or free-space map are inferred.
Figure 1. Real-history replay, with sessions kept separate. Blue points are camera poses; object projections are unverified. This is not a room occupancy map. Source & protocol · Click to enlarge.

Read-only diagnosis. All 1,149 replayed states lack sufficient consistency evidence; no reliable recovery anchor is available. Zero supported deviation detections here means not evaluable, not successful navigation. View the diagnostic audit.

Real-Robot Room Survey

A human-controlled survey now provides an actual occupancy grid and synchronized sensor records: approximately 229 seconds, 2,747 laser scans, and 225 RGB keyframes. Collection is complete; room-map acceptance is not.

Actual room survey output: an occupancy grid with radial streaks, an estimated trajectory, and two original RGB views of chairs and desks. Room review is pending and object detection was not run.
Figure 2. Recorded occupancy grid and original camera views, 9 October 2026. The plotted trajectory and path length are estimates, not ground truth. This is not a validated semantic map. Capture protocol & source · Click to enlarge.

Map review pending. Radial streaks and inconsistent return estimates prevent a reliable geometry claim. Object detection was not run, and no metric landmark has been verified. This separate survey does not extend the 1,149-state historical replay; all robot movement was human-controlled.

Why heading evidence matters

The recorded fused heading stayed at zero despite turns in raw odometry. An isolated A/B test of the actual extended Kalman filter (EKF) enabled only odometry angular-velocity fusion. The candidate still failed: heading changed by −0.077 rad, versus −7.122 rad in the recorded input.

Two measured time-series plots compare recorded raw odometry, historical fused output, and isolated actual EKF baseline and candidate runs. The candidate heading response remains near zero rather than following the recorded turns.
Figure 3. Actual EKF runs on identical recorded odometry, changing only the angular-velocity input flag. Raw odometry is a reference, not orientation ground truth; the candidate was not deployed. A/B protocol & source · Click to enlarge.

Supported finding, not a completed fix. The driver reports angular-velocity variance of 1,000 whenever any velocity component is nonzero; the source, executable constants, and recorded messages agree. This explains strong down-weighting in the tested candidate, not the sole cause of every map artifact. Source audit.

Latest IMU check. A separate stationary recording received 500 raw inertial measurement unit (IMU) messages at approximately 20 Hz. The filtered IMU topic selected by the EKF had no publisher. Static screening is complete, but turning response and measurement reliability remain unverified; no fusion candidate has been selected. Stationary evidence & original plots.

Next: record synchronized IMU and odometry during a separately authorized, controlled turn with an independent angle reference, before selecting another fusion candidate or accepting the room map.

Experimental Evidence

Video 1. Controlled MP3D instruction-order violation. Plotted points are sparse reference waypoints; “correction triggered” is a replay decision, not an executed robot recovery.

Different evaluation scopes; no combined benchmark-improvement claim.
EvaluationObserved resultEvidence boundary
Controlled MP3D · 5 scenes / 5 episodes3/4 deviation types detected; 0/34 normal reference points alertedSmall mechanism study; a 2.44 m pose jump was missed
Paired CMA navigation A/B · 110 episodesSR tied; SPL and nDTW did not improveNo demonstrated navigation gain
WheelTec · manual-move Trial 1RSame chair: obj_0000 → obj_0034Identity persistence failed; cause remains inconclusive
Real-history read-only diagnosis · 8 Oct1,149/1,149 states: insufficient evidence; 0 reliable anchorsDiagnosis not evaluable; not a zero-error result
Manual room survey · 9 Oct2,747 scans; 225 RGB keyframes; occupancy grid capturedGeometry review pending; no verified metric landmarks
Isolated actual EKF A/B · 9 OctCandidate heading: −0.077 rad; recorded input: −7.122 radCandidate failed; no deployment or ground-truth accuracy claim
Stationary IMU input audit · 9 Oct500 raw messages at ≈20 Hz; filtered topic has no publisherTurning response and reliability unverified; no fusion candidate

SR: success rate · SPL: success weighted by path length · nDTW: normalized dynamic time warping.

Failure cases & additional replays

Human-confirmed views of the same chair before and after manual movement. The ID change remains a failure, not evidence of successful relocalization.

Same chair before manual movement in Trial 1R, with a yellow detection box.
Before movement. obj_0000
Same human-confirmed chair after manual movement in Trial 1R, assigned a new object ID.
After movement. obj_0034

These controlled videos and the depth trace do not establish a physical error cause or autonomous recovery. The 8 October live diagnostic attempt stopped at its initialization memory limit before processing any frames.

Resources

Research mind map

The research question, evidence boundaries, and next experiment, updated 9 October 2026. This is a research outline, not an experimental result.

Research mind map connecting history-aware diagnosis, earlier MP3D and real-history limits, the completed manual room capture, a failed isolated EKF candidate, and the remaining IMU and geometry validation.

BibTeX

Provisional project citation only. This master's thesis project is in progress and has not been published as a paper.

@unpublished{li2026rabbitrobotnav,
  author = {Li, Jinghai},
  title  = {Rabbit-RobotNav: History-Aware Error Diagnosis and Recovery Anchors for Vision-Language Navigation},
  year   = {2026},
  note   = {Master's thesis project, work in progress; not a published paper},
  url    = {https://lijinghai.github.io/RabbitRobotNav/}
}