Skip to content

[T-090] Spike: headless TurtleBot 4 + Nav2 warehouse in Docker — measure RTF, startup, CPU; record findings #58

Closed

Description

@CodewithJha

Task T-090 · Milestone M2 — Scenario + kinematic2d · Size S · Priority P0 · Epic #2

Implements FR-SIM-003

Branch spike/t-090-spike-headless-turtlebot-4-nav2 — one task = one branch = one PR (doc 32 §6)

Summary

Time-boxed (≤ 3 days) feasibility spike retiring risk R-01: run nav2_minimal_tb4_sim warehouse headless in an Ubuntu 24.04 + Jazzy + Harmonic container on the owner's laptop, send one NavigateToPose, measure real-time factor, cold-start time, CPU/RAM, with and without GPU (LIBGL_ALWAYS_SOFTWARE=1), and 1 vs 2 parallel instances.

Context / motivation

Scheduled early (parallel to M2, doc 22 §2) because the Gazebo path is the largest technical risk; results set max_parallel_per_host and timeouts.

Scope

In scope

  • Throw-away Dockerfile under spikes/T-090/ (not production).
  • Findings: docs/evidence/T-090-gazebo-spike.md with measured numbers, versions, commands, problems and recommendation (go / adjust / fallback).

Out of scope

  • Production image (T-095) and any RoboProbe code.

Implementation guidance

  • Time box: 3 working days; stop and write findings even if incomplete — the deliverable is knowledge, not code.
  • Container: ros:jazzy-ros-base-noble + ros-jazzy-navigation2 ros-jazzy-nav2-bringup ros-jazzy-nav2-minimal-tb4-sim ros-jazzy-ros-gz ros-jazzy-rmw-cyclonedds-cpp (verify package names against the Jazzy apt index; record exact versions with dpkg -l | grep ros-jazzy in the evidence).
  • Launch: ros2 launch nav2_bringup tb4_simulation_launch.py headless:=True use_rviz:=False with the warehouse world (verify launch/arg names for the installed version); send a goal via ros2 action send_goal /navigate_to_pose nav2_msgs/action/NavigateToPose ... or a 20-line nav2_simple_commander script in spikes/T-090/.
  • Measure: cold start to Nav2 ACTIVE (s), wall time of one delivery, RTF (gz topic -e -t /stats), CPU% and RSS (docker stats --no-stream sampled every 2 s by a script), with and without LIBGL_ALWAYS_SOFTWARE=1, and 1 vs 2 concurrent containers with distinct ROS_DOMAIN_ID/GZ_PARTITION.
  • Also verify: enable_stamped_cmd_vel default, depth camera availability on the TB4 sim model, /clock usage, and whether headless rendering works in Docker on the laptop GPU.
  • Evidence sections: Environment · Versions · Procedure · Results table · Problems & workarounds · Recommendation (max_parallel_per_host, startup_timeout_s, go/no-go) · Follow-up issues.
  • Standards: respect the layering contracts (doc 16 §2) and conventions in doc 34; no hard-coded tunables — thresholds/defaults come from typed settings (doc 27); no magic numbers (ruff PLR2004); public APIs typed (mypy strict) and documented.

Configuration keys

From the configuration reference (doc 27). Keys marked (new) must be added to the typed settings models and appear in the generated reference (T-003c).

  • backends.gazebo_nav2.max_parallel_per_host
  • backends.gazebo_nav2.startup_timeout_s
  • backends.gazebo_nav2.software_rendering
  • backends.gazebo_nav2.headless_rendering

Acceptance criteria

  • Evidence doc with RTF, startup, CPU/RAM numbers and a clear recommendation.
  • Doc 23 risk R-01 updated with the outcome.
  • Recommended values for backends.gazebo_nav2.max_parallel_per_host and startup_timeout_s stated with data.
  • Follow-up issues filed for any blocker found.
  • Tests listed below added and green in CI; coverage of new code meets the gate in doc 18 §3.
  • Docs, config reference and CHANGELOG Unreleased updated where behaviour, keys or interfaces changed.
  • Definition of Done (doc 32 §3) satisfied.

Tests required

  • N/A (spike) — reproducible commands recorded.

Dependencies

Blocked by: #26 (T-005a)

Blocks: #190 (T-091)

Parallelization notes

Files / paths owned by this task — avoid editing other paths; shared files (pyproject.toml entry points, cli/main.py, api/routers/__init__.py, router.tsx, docker/compose.yaml, ci.yml) are append-only:

  • spikes/T-090/**
  • docs/evidence/T-090-gazebo-spike.md

Runs in parallel with M2–M4; touches no product code.

Definition of Done

Per doc 32 §3 and AGENTS.md §5: lint, format, mypy strict and import-linter green; tests added and passing; docs updated; PR template completed with Closes #<this issue>; Conventional Commit messages referencing T-090 (doc 16 §6); commits authored only by the repository owner identity (AGENTS.md §4); CI green; reviewer checklist (doc 32 §5.1) satisfied.

References

Design docs: doc 10 §1 · doc 10 §2 · doc 10 §8 · doc 23 · doc 22 §2

Requirements: FR-SIM-003 (traceability: doc 28)

External:

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:rosROS 2 nodes and packagesarea:simulatorSimulator backends (kinematic2d, Gazebo adapter)milestone:M2M2 — Scenario + kinematic2dpriority:P0Critical path / blocks otherssize:S<= 1 daytaskChild task of a milestone epictype:researchTime-boxed spike / investigation

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions