|

Robotics Journey

A roadmap into robotics simulation and sim-to-real, in order: every study session and the deliverable that closes each stage. The red line marks today and shows where the plan expects progress to be. This is a plan, not a course: it comes with no learning materials of its own. I find the materials for every topic myself, in open and paid courses, and I share whatever I can on my social media along the way.

Field
Simulation engineers build the virtual worlds robots are developed and tested in: physics models, simulated sensors, and the tooling that runs them at scale. Sim-to-real is the part that checks those worlds against reality and says how far to trust them. Sensor virtualization makes simulated data reach other software as if it came from a real device.
Goal
Learn to model how robotic systems behave, check simulations against real recorded data, and build software tools to test them. The focus is simulation engineering and sim-to-real, not all of robotics, and everything runs without physical hardware.
Pace
About 20 hours a week for six months: 24 weeks of study and 2 weeks of reserve, roughly 520 hours. If time runs short, the scope shrinks; the plan does not grow. Every date on this page is an estimate.

Roadmap

Dates are estimates at 20 hours a week (currently ending around May 18, 2027) and may be adjusted as the work progresses. A stage ends when its deliverable meets its criteria, not on a date.

  1. Today · Wed, Nov 18, 2026
  2. Stage 1

    Simulation Foundations

    Every robot simulator, however large, is a loop: take the state, apply the physics for one small timestep, repeat. This stage builds that loop by hand for a two-wheeled robot, so later tools are not black boxes. C++ and Python are refreshed selectively, not learned from zero.

    Math
    Vectors, the dot product, 2×2 and 3×3 matrices, radians, rotations, local and world coordinate frames, composing transforms.
    Physics
    Position, velocity, acceleration; differential-drive kinematics.
    Numerical methods
    Euler and Runge–Kutta 4 integration, timestep, numerical error and stability.
    Code
    C++20 with CMake and tests for the model; Python with NumPy and Matplotlib for analysis.

    Not in this stage: Manipulator dynamics, contact solvers, optimal control theory, a full linear algebra course, 3D quaternions (they come in Stage 2).

  3. Est. Wed, Nov 18, 2026

    Stage 1 · Day 1 · C++

    CMake project and compiler warnings

    Set up a C++20 project that builds with one CMake command and treats compiler warnings as signals, not noise.

  4. Est. Thu, Nov 19, 2026

    Stage 1 · Day 2 · C++

    C++ structs, values and RAII

    Refresh value types, references, and RAII: the parts of C++ a simulator leans on every day.

  5. Est. Fri, Nov 20, 2026

    Stage 1 · Day 3 · Math

    Vec2 operations and numerical checks

    Vectors and the dot product in code, with tests that check results within a numerical tolerance.

  6. Est. Mon, Nov 23, 2026

    Stage 1 · Day 4 · Math

    Pose2, radians and rotation matrices

    A 2D pose as position plus heading: radians, 2×2 rotation matrices, and moving between local and world frames.

  7. Est. Tue, Nov 24, 2026

    Stage 1 · Day 5 · Physics

    Differential drive: forward motion

    Kinematics of a two-wheeled robot: how equal wheel speeds turn into straight-line motion.

  8. Est. Wed, Nov 25, 2026

    Stage 1 · Day 6 · Physics

    Wheel-speed kinematics and turns

    Different wheel speeds give an angular velocity; the robot follows an arc around a turning centre.

  9. Est. Thu, Nov 26, 2026

    Stage 1 · Day 7 · Math

    Euler integration and timestep

    Step the motion forward in time with Euler integration and see how the timestep size creates error.

  10. Est. Fri, Nov 27, 2026

    Stage 1 · Day 8 · Math

    RK4 comparison on curved paths

    Runge–Kutta 4 against Euler on curved paths: accuracy, cost, and stability for the same timestep.

  11. Est. Mon, Nov 30, 2026

    Stage 1 · Day 9 · Python

    CSV output and Python plots

    The C++ simulator writes CSV; NumPy and Matplotlib turn it into trajectory and error plots.

  12. Est. Tue, Dec 1, 2026

    Stage 1 · Day 10 · Validation

    Reproducible run, tests and stage review

    Same parameters, same result: tests, a clean rebuild, and a review against the stage criteria.

  13. Est. by Dec 1, 2026

    Stage 1 · Deliverable

    2D differential-drive simulator

    Wheel speeds, wheel radius, wheelbase, timestep, and duration in; a CSV of time, x, y, heading and plots out. The model is C++, the analysis Python.

    • To do: Clean build with one CMake command
    • To do: Drives straight with equal wheel speeds and turns with different ones
    • To do: Coordinate transforms pass simple checks
    • To do: Repeated runs with the same parameters give the same result
    • To do: Plots and an explanation of how the timestep affects the error
  14. Stage 2

    Robotics Simulation

    The everyday toolset of robotics simulation: describe a robot as a model with frames, joints, mass, and contacts, put it in a physics engine, drive it through ROS 2, and give it simulated sensors. The result is a digital robot prototype whose behavior can be recorded, changed, and explained.

    Math
    3D rotations and rigid transforms (SO(3), SE(3)), quaternions, frame trees, forward kinematics, the pinhole camera model.
    Physics
    Mass and inertia, friction, restitution, contact stability, generalized coordinates.
    Sensors
    Simulated camera, IMU, and LiDAR, with configurable noise.
    Tools
    ROS 2 (topics, QoS, tf2, rosbag2), Gazebo and SDF, MuJoCo and MJCF, URDF/Xacro, one small CAD-to-simulation exercise, Rerun and Foxglove for visual debugging.

    Not in this stage: A separate CAD course, deep SLAM and navigation, reinforcement learning.

  15. Est. Wed, Dec 2, 2026

    Stage 2 · Day 11 · Math

    SO(3), SE(3) and Rodrigues formula

    Rotations and rigid-body transforms in 3D: the groups SO(3) and SE(3), and the axis–angle Rodrigues formula.

  16. Est. Thu, Dec 3, 2026

    Stage 2 · Day 12 · Math

    Quaternion rotations and frame inverses

    Quaternions as a compact, stable way to store rotations; composing and inverting frame transforms.

  17. Est. Fri, Dec 4, 2026

    Stage 2 · Day 13 · Math

    TF tree and forward kinematics

    A robot as a tree of coordinate frames; forward kinematics chains transforms from the base to each part.

  18. Est. Mon, Dec 7, 2026

    Stage 2 · Day 14 · Tools

    3D frame visualization in Rerun

    Draw frames and trajectories in Rerun so 3D mistakes become visible instead of hiding in numbers.

  19. Est. Tue, Dec 8, 2026

    Stage 2 · Day 15 · ROS 2

    ROS 2 topics, QoS and tf2 diagnostics

    How ROS 2 nodes talk: topics, quality-of-service settings, and diagnosing the tf2 frame tree.

  20. Est. Wed, Dec 9, 2026

    Stage 2 · Day 16 · Modeling

    URDF/Xacro robot model and joint frames

    Describe a robot in URDF/Xacro: links, joints, and the frames between them.

  21. Est. Thu, Dec 10, 2026

    Stage 2 · Day 17 · CAD

    Build123d CAD-as-code: one robot part

    Model one robot part as code with Build123d, so geometry is versioned and reproducible.

  22. Est. Fri, Dec 11, 2026

    Stage 2 · Day 18 · Physics

    Trimesh mass, volume and inertia check

    Compute volume, mass, and the inertia tensor from a mesh with Trimesh, and check them against the model.

  23. Est. Mon, Dec 14, 2026

    Stage 2 · Day 19 · Modeling

    Collision geometry and model validation

    Simplified collision shapes versus visual meshes, and checks that the model loads and behaves sensibly.

  24. Est. Tue, Dec 15, 2026

    Stage 2 · Day 20 · CAD

    CAD-to-URDF reproducible pipeline

    One script from CAD part to URDF, so the simulated robot can be rebuilt from source.

  25. Est. Wed, Dec 16, 2026

    Stage 2 · Day 21 · Gazebo

    Gazebo SDF world and contact parameters

    Build a Gazebo world in SDF and look at the contact parameters that decide how bodies touch.

  26. Est. Thu, Dec 17, 2026

    Stage 2 · Day 22 · Physics

    Gazebo friction and restitution experiment

    Change friction and bounciness (restitution) and measure how the motion changes.

  27. Est. Fri, Dec 18, 2026

    Stage 2 · Day 23 · ROS 2

    ros_gz_bridge and cmd_vel control

    Connect ROS 2 to Gazebo with ros_gz_bridge and drive the robot with velocity commands.

  28. Est. Mon, Dec 21, 2026

    Stage 2 · Day 24 · ROS 2

    ros2_control architecture: guided exploration

    A guided look at ros2_control: how controllers, hardware interfaces, and the simulator fit together.

  29. Est. Tue, Dec 22, 2026

    Stage 2 · Day 25 · Physics

    Contact stability and repeatable baseline

    Find contact settings that do not jitter or explode, and save them as a repeatable baseline.

  30. Est. Wed, Dec 23, 2026

    Stage 2 · Day 26 · ROS 2

    ROS 2–Gazebo bridge

    Carry sensor and control topics both ways between ROS 2 and Gazebo, and check what arrives.

  31. Est. Thu, Dec 24, 2026

    Stage 2 · Day 27 · ROS 2

    Simulation clock and reset

    Simulated time versus wall-clock time, and resetting a scenario to a known starting state.

  32. Est. Fri, Dec 25, 2026

    Stage 2 · Day 28 · Data

    rosbag2 record and playback

    Record topics with rosbag2 and play them back: the basis of every later experiment.

  33. Est. Mon, Dec 28, 2026

    Stage 2 · Day 29 · Validation

    Timestamp and frame consistency

    Check that every message has a sensible timestamp and frame, before trusting any data.

  34. Est. Tue, Dec 29, 2026

    Stage 2 · Day 30 · Validation

    Reproducible dataset run

    Record the same scenario twice and confirm the two runs give the same data.

  35. Est. Wed, Dec 30, 2026

    Stage 2 · Day 31 · Sensors

    Virtual camera setup

    Add a simulated camera to the robot and publish its images.

  36. Est. Thu, Dec 31, 2026

    Stage 2 · Day 32 · Sensors

    Camera intrinsics and image topics

    The pinhole camera model: focal length, principal point, and how they appear in ROS image topics.

  37. Est. Fri, Jan 1, 2027

    Stage 2 · Day 33 · Math

    Camera frame transformations

    Project 3D points into the image and move them between the camera, robot, and world frames.

  38. Est. Mon, Jan 4, 2027

    Stage 2 · Day 34 · Data

    Image recording and visualization

    Record camera streams and inspect them frame by frame.

  39. Est. Tue, Jan 5, 2027

    Stage 2 · Day 35 · Tools

    Foxglove sensor stream debugging

    Use Foxglove to inspect live and recorded sensor streams side by side.

  40. Est. Wed, Jan 6, 2027

    Stage 2 · Day 36 · Sensors

    IMU orientation and acceleration

    A simulated IMU: what orientation, angular velocity, and linear acceleration really measure, gravity included.

  41. Est. Thu, Jan 7, 2027

    Stage 2 · Day 37 · Sensors

    LiDAR scan geometry

    How a LiDAR scan is built from rays: angles, ranges, and the geometry of a scan line.

  42. Est. Fri, Jan 8, 2027

    Stage 2 · Day 38 · Sensors

    GPU LiDAR and raycasting concepts

    How GPU raycasting simulates LiDAR, and what it simplifies compared with a real sensor.

  43. Est. Mon, Jan 11, 2027

    Stage 2 · Day 39 · Sensors

    Noise configuration and data checks

    Add sensor noise in the simulator and check the output statistics match the configuration.

  44. Est. Tue, Jan 12, 2027

    Stage 2 · Day 40 · Sensors

    Multisensor scenario

    Run camera, IMU, and LiDAR together in one recorded scenario.

  45. Est. Wed, Jan 13, 2027

    Stage 2 · Day 41 · MuJoCo

    MuJoCo MJCF and generalized coordinates

    Describe a model in MuJoCo’s MJCF and see how it represents motion with generalized coordinates.

  46. Est. Thu, Jan 14, 2027

    Stage 2 · Day 42 · MuJoCo

    Basic actuators and motion

    Drive joints with MuJoCo actuators and watch the resulting motion.

  47. Est. Fri, Jan 15, 2027

    Stage 2 · Day 43 · Physics

    MuJoCo contact solref/solimp experiment

    Tune MuJoCo’s soft-contact parameters (solref, solimp) and measure their effect.

  48. Est. Mon, Jan 18, 2027

    Stage 2 · Day 44 · Validation

    Compare equivalent scenarios with Gazebo

    Run the same scenario in MuJoCo and Gazebo and explain where and why they differ.

  49. Est. Tue, Jan 19, 2027

    Stage 2 · Day 45 · Review

    Stage 2 demonstration

    Demonstrate the digital robot prototype against the stage criteria.

  50. Est. by Jan 19, 2027

    Stage 2 · Deliverable

    Digital robot prototype

    A simulated robot with control, a camera, an IMU, and a LiDAR, used as a test fixture for physics and sensors rather than a hardware design.

    • To do: Controlled robot with a camera, an IMU, and a LiDAR
    • To do: TF tree, URDF/Xacro, mass and inertia, and contact parameters checked
    • To do: A reproducible experiment, run and recorded
    • To do: Change physical parameters and explain how the system behaves
  51. Stage 3

    Sim-to-Real Engineering

    A simulation is only useful if you know how far to trust it. Sim-to-real is the work of measuring the reality gap: compare the model with real recorded data, estimate its parameters, model sensor noise and delays, and state where the simulation holds and where it does not. Public datasets stand in for hardware; this is not presented as testing on a physical robot.

    Math
    System identification with least squares and optimization, frame and time alignment, one narrow extended Kalman filter (EKF) and one ICP point-cloud experiment.
    Statistics
    Error distributions, train and held-out validation splits, absolute trajectory error (ATE), uncertainty, robustness across random seeds.
    Sensors
    Camera intrinsics and extrinsics, IMU white noise and bias random walk, Allan variance, dropout, outliers, latency, jitter.
    Methods
    Calibration, sensitivity analysis, domain randomization, controlled experiment matrices.

    Not in this stage: A full state-estimation or SLAM course.

  52. Est. Wed, Jan 20, 2027

    Stage 3 · Day 46 · Data

    Choose a public robot/sensor dataset

    Pick a public dataset of real robot or sensor recordings to stand in for hardware.

  53. Est. Thu, Jan 21, 2027

    Stage 3 · Day 47 · Data

    Inspect dataset units and metadata

    Read the dataset carefully: units, frames, timestamps, and sensor setup.

  54. Est. Fri, Jan 22, 2027

    Stage 3 · Day 48 · Statistics

    ATE and sensor fidelity metrics

    Absolute trajectory error (ATE) and sensor metrics: how “close to reality” becomes a number.

  55. Est. Mon, Jan 25, 2027

    Stage 3 · Day 49 · Validation

    Build a simulated baseline for comparison

    Recreate the dataset’s scenario in simulation as the baseline to compare against.

  56. Est. Tue, Jan 26, 2027

    Stage 3 · Day 50 · Validation

    Document mismatches and assumptions

    Write down every known difference between the simulation and the recording.

  57. Est. Wed, Jan 27, 2027

    Stage 3 · Day 51 · Math

    Parameter estimation concept

    System identification: estimating model parameters from recorded data with least squares.

  58. Est. Thu, Jan 28, 2027

    Stage 3 · Day 52 · Math

    Fit wheel radius from recorded motion

    Estimate the effective wheel radius from recorded motion with an optimizer.

  59. Est. Fri, Jan 29, 2027

    Stage 3 · Day 53 · Math

    Fit wheelbase or turning parameter

    Estimate the wheelbase, the parameter that decides how sharply the robot turns.

  60. Est. Mon, Feb 1, 2027

    Stage 3 · Day 54 · Statistics

    Train/validation split by runs

    Fit on some recordings and check on others, so the model is not just memorizing.

  61. Est. Tue, Feb 2, 2027

    Stage 3 · Day 55 · Validation

    Parameter fit report

    Report the fitted parameters, their error, and how much to trust them.

  62. Est. Wed, Feb 3, 2027

    Stage 3 · Day 56 · Physics

    Friction and slip sensitivity

    How much results change when friction and wheel slip change.

  63. Est. Thu, Feb 4, 2027

    Stage 3 · Day 57 · Physics

    Mass/inertia sensitivity

    How much results change when mass and inertia are off.

  64. Est. Fri, Feb 5, 2027

    Stage 3 · Day 58 · Tools

    Parameter sweep runner

    A small runner that tries many parameter combinations and collects the results.

  65. Est. Mon, Feb 8, 2027

    Stage 3 · Day 59 · Statistics

    Compare error distributions

    Compare whole error distributions, not single numbers.

  66. Est. Tue, Feb 9, 2027

    Stage 3 · Day 60 · Math

    Identify unobservable parameters

    Find parameters the data cannot pin down, and stop pretending to know them.

  67. Est. Wed, Feb 10, 2027

    Stage 3 · Day 61 · Calibration

    Camera intrinsic calibration concepts

    How intrinsic camera calibration works, and what a calibrated model gets right.

  68. Est. Thu, Feb 11, 2027

    Stage 3 · Day 62 · Calibration

    Extrinsics and coordinate frames

    Extrinsics: where each sensor sits relative to the robot, and how errors there spread.

  69. Est. Fri, Feb 12, 2027

    Stage 3 · Day 63 · Sensors

    IMU white noise, random walk and Allan variance

    IMU error models: white noise, bias random walk, and reading them from an Allan variance plot.

  70. Est. Mon, Feb 15, 2027

    Stage 3 · Day 64 · Calibration

    Timestamp offsets

    Estimate and correct time offsets between sensors.

  71. Est. Tue, Feb 16, 2027

    Stage 3 · Day 65 · Calibration

    Calibration report and limitations

    Report calibration results and what they cannot guarantee.

  72. Est. Wed, Feb 17, 2027

    Stage 3 · Day 66 · Sensors

    Gaussian noise and bias

    Model sensor noise as Gaussian noise plus bias, and check the model against data.

  73. Est. Thu, Feb 18, 2027

    Stage 3 · Day 67 · Sensors

    Allan deviation on recorded IMU data

    Compute the Allan deviation on real IMU recordings and compare with the simulated IMU.

  74. Est. Fri, Feb 19, 2027

    Stage 3 · Day 68 · Sensors

    Sensor dropout and outliers

    Simulate missing samples and outliers, the failures real sensors actually have.

  75. Est. Mon, Feb 22, 2027

    Stage 3 · Day 69 · Sensors

    Latency and jitter

    Model sensor latency and timing jitter, and measure their effect.

  76. Est. Tue, Feb 23, 2027

    Stage 3 · Day 70 · Validation

    Noise model validation against recorded data

    Check the noise models against recorded data, not just against intuition.

  77. Est. Wed, Feb 24, 2027

    Stage 3 · Day 71 · Statistics

    Select plausible parameter ranges

    Choose realistic parameter ranges for domain randomization from the data.

  78. Est. Thu, Feb 25, 2027

    Stage 3 · Day 72 · Physics

    Randomize friction and mass

    Domain randomization: vary friction and mass across runs.

  79. Est. Fri, Feb 26, 2027

    Stage 3 · Day 73 · Sensors

    Randomize lighting and camera noise

    Vary lighting and camera noise across runs.

  80. Est. Mon, Mar 1, 2027

    Stage 3 · Day 74 · Validation

    Run a controlled experiment matrix

    Run a planned matrix of experiments, changing one factor at a time.

  81. Est. Tue, Mar 2, 2027

    Stage 3 · Day 75 · Statistics

    Quantify robustness across seeds

    Repeat runs with different random seeds and measure the spread.

  82. Est. Wed, Mar 3, 2027

    Stage 3 · Day 76 · Validation

    Separate baseline and validation scenes

    Keep tuning scenes and test scenes apart.

  83. Est. Thu, Mar 4, 2027

    Stage 3 · Day 77 · Infrastructure

    Create deterministic scenario definitions

    Define scenarios in files so every run is exactly repeatable.

  84. Est. Fri, Mar 5, 2027

    Stage 3 · Day 78 · Statistics

    ATE trajectory evaluation and tolerances

    Evaluate trajectories with ATE and set the tolerances that count as a pass.

  85. Est. Mon, Mar 8, 2027

    Stage 3 · Day 79 · Validation

    Investigate the worst-case mismatch

    Dig into the run where simulation and reality disagree most.

  86. Est. Tue, Mar 9, 2027

    Stage 3 · Day 80 · Validation

    Write an evidence-based validity claim

    State where the simulation is valid, with the evidence for each claim.

  87. Est. Wed, Mar 10, 2027

    Stage 3 · Day 81 · Validation

    Compare trajectories on held-out data

    Compare simulated and recorded trajectories on data never used for tuning.

  88. Est. Thu, Mar 11, 2027

    Stage 3 · Day 82 · Math

    Align coordinate frames and time

    Align frames and timestamps before comparing anything.

  89. Est. Fri, Mar 12, 2027

    Stage 3 · Day 83 · Math

    EKF with robot_localization: limited experiment

    One narrow experiment with an extended Kalman filter (robot_localization), not a full estimation course.

  90. Est. Mon, Mar 15, 2027

    Stage 3 · Day 84 · Math

    Open3D ICP: limited point cloud experiment

    One narrow point-cloud alignment experiment with ICP in Open3D.

  91. Est. Tue, Mar 16, 2027

    Stage 3 · Day 85 · Python

    Error breakdown visualization

    Plots that show where the error comes from.

  92. Est. Wed, Mar 17, 2027

    Stage 3 · Day 86 · Validation

    Rebuild the experiment from scratch

    Rebuild the whole experiment from a clean checkout to prove it is reproducible.

  93. Est. Thu, Mar 18, 2027

    Stage 3 · Day 87 · Math

    Tune against training recordings

    Tune the model on the training recordings only.

  94. Est. Fri, Mar 19, 2027

    Stage 3 · Day 88 · Validation

    Evaluate on an unseen recording

    Evaluate the tuned model on a recording it has never seen.

  95. Est. Mon, Mar 22, 2027

    Stage 3 · Day 89 · Statistics

    Reproducibility and uncertainty report

    Report how reproducible the results are and how uncertain.

  96. Est. Tue, Mar 23, 2027

    Stage 3 · Day 90 · Review

    Stage 3 review and limitations

    Review the stage and write down its limits honestly.

  97. Est. by Mar 23, 2027

    Stage 3 · Deliverable

    Held-out sim-to-real evaluation

    The simulation is tuned on some real recordings and judged on others it has never seen. A dataset comparison does not replace a test on a physical robot.

    • To do: Model compared with real recorded data, with timestamps and frames aligned
    • To do: Parameters adjusted and the improvement measured (ATE or a sensor metric)
    • To do: Effect of noise and latency estimated
    • To do: Documented where the simulation is valid, where it is not, and what shows it
  98. Stage 4

    Simulation Infrastructure & Validation

    Simulation at scale is software engineering: run scenarios headless and in batches, replay recordings, compare against a baseline, and catch regressions in CI. Sensor virtualization makes simulated data look like a real device to other programs. The stage produces two tools: a Simulation Reliability Toolkit and a Virtual Sensor Bridge.

    Infrastructure
    Headless and batch runs, scenario configuration, seeds, run metadata, recording and replay, CI with GitHub Actions, profiling.
    Virtualization
    A simulated Gazebo camera delivered through ROS 2 or as a Linux V4L2 device, with frame rate, format, timestamps, latency, and dropped frames measured.
    Validation
    Baseline metrics and thresholds, regression tests, noisy and failure scenarios, machine-readable reports.

    Not in this stage: Other sensor types in the bridge unless a scenario needs them. Everything runs without physical hardware.

  99. Est. Wed, Mar 24, 2027

    Stage 4 · Day 91 · Infrastructure

    Gazebo headless execution

    Run Gazebo without a screen, as a test machine or CI would.

  100. Est. Thu, Mar 25, 2027

    Stage 4 · Day 92 · Infrastructure

    Command-line scenario configuration

    Choose scenarios and parameters from the command line.

  101. Est. Fri, Mar 26, 2027

    Stage 4 · Day 93 · Infrastructure

    Batch runner with seeds

    Run many scenarios in a batch, each with a recorded random seed.

  102. Est. Mon, Mar 29, 2027

    Stage 4 · Day 94 · Infrastructure

    Run isolation and output folders

    Keep every run isolated, with its own output folder.

  103. Est. Tue, Mar 30, 2027

    Stage 4 · Day 95 · Infrastructure

    Baseline batch execution

    Run the full batch once to produce the reference baseline.

  104. Est. Wed, Mar 31, 2027

    Stage 4 · Day 96 · Infrastructure

    Standardize run metadata

    Record what produced each result: version, parameters, seed, and time.

  105. Est. Thu, Apr 1, 2027

    Stage 4 · Day 97 · Data

    rosbag2 replay harness

    Replay recordings automatically into the system under test.

  106. Est. Fri, Apr 2, 2027

    Stage 4 · Day 98 · Validation

    Compare recorded and simulated messages

    Compare recorded and simulated messages field by field.

  107. Est. Mon, Apr 5, 2027

    Stage 4 · Day 99 · Validation

    Detect missing or late messages

    Detect missing or late messages automatically.

  108. Est. Tue, Apr 6, 2027

    Stage 4 · Day 100 · Validation

    Replay reproducibility report

    Report how repeatable replays are.

  109. Est. Wed, Apr 7, 2027

    Stage 4 · Day 101 · Virtualization

    Select a camera interface and consumer

    Choose how the virtual camera is delivered and which program consumes it.

  110. Est. Thu, Apr 8, 2027

    Stage 4 · Day 102 · Virtualization

    Gazebo camera ROS image stream

    Publish the Gazebo camera as a ROS 2 image stream.

  111. Est. Fri, Apr 9, 2027

    Stage 4 · Day 103 · Virtualization

    Bridge images to a consumer via ROS 2

    Deliver those images to a consumer program through ROS 2.

  112. Est. Mon, Apr 12, 2027

    Stage 4 · Day 104 · Virtualization

    Validate encoding and frame rate

    Check the image encoding and the frame rate the consumer actually gets.

  113. Est. Tue, Apr 13, 2027

    Stage 4 · Day 105 · Virtualization

    Virtual Sensor Bridge: measurable camera demo

    A camera demo with measured numbers, not just a picture on screen.

  114. Est. Wed, Apr 14, 2027

    Stage 4 · Day 106 · Virtualization

    Choose a Linux V4L2 option if the environment supports it

    Decide whether Linux V4L2 can present the virtual camera as a normal webcam here.

  115. Est. Thu, Apr 15, 2027

    Stage 4 · Day 107 · Virtualization

    Implement or configure a V4L2 loopback bridge

    Set up v4l2loopback so any program can read the simulated camera as a webcam.

  116. Est. Fri, Apr 16, 2027

    Stage 4 · Day 108 · Virtualization

    Bridge latency, dropped frames and timestamp fidelity

    Measure the bridge: latency, dropped frames, and whether timestamps survive.

  117. Est. Mon, Apr 19, 2027

    Stage 4 · Day 109 · Virtualization

    Fallback ROS 2 consumer compatibility

    Keep a pure ROS 2 path working for where V4L2 is not available.

  118. Est. Tue, Apr 20, 2027

    Stage 4 · Day 110 · Virtualization

    Bridge interface and troubleshooting docs

    Document the bridge interface and how to troubleshoot it.

  119. Est. by Apr 20, 2027

    Stage 4 · Deliverable

    Virtual Sensor Bridge

    A simulated camera presented to other programs through a standard interface, as if it were a real device.

    • To do: A virtual camera stream from Gazebo reaches a consumer through ROS 2 or Linux V4L2
    • To do: Frame rate, format, timestamps, latency, and dropped frames measured
  120. Est. Wed, Apr 21, 2027

    Stage 4 · Day 111 · Validation

    Define baseline metrics and thresholds

    Decide which metrics matter and what change counts as a regression.

  121. Est. Thu, Apr 22, 2027

    Stage 4 · Day 112 · Validation

    Scenario regression test harness

    Turn scenarios into automated regression tests.

  122. Est. Fri, Apr 23, 2027

    Stage 4 · Day 113 · Validation

    Test noisy and failure scenarios

    Test noisy and failing scenarios too, not just the happy path.

  123. Est. Mon, Apr 26, 2027

    Stage 4 · Day 114 · Infrastructure

    Produce a machine-readable report

    Produce a report that other tools and CI can read.

  124. Est. Tue, Apr 27, 2027

    Stage 4 · Day 115 · Infrastructure

    CI integration

    Run the tests in GitHub Actions on every change.

  125. Est. Wed, Apr 28, 2027

    Stage 4 · Day 116 · Infrastructure

    Unify runner, replay and bridge

    Join the runner, replay, and bridge into one tool.

  126. Est. Thu, Apr 29, 2027

    Stage 4 · Day 117 · Infrastructure

    Config schema and validation

    A configuration schema that rejects bad input early.

  127. Est. Fri, Apr 30, 2027

    Stage 4 · Day 118 · Infrastructure

    Profiling CPU and memory

    Profile CPU and memory and fix the worst hotspots.

  128. Est. Mon, May 3, 2027

    Stage 4 · Day 119 · Infrastructure

    Documentation and one-command demo

    Documentation and a demo that runs with one command.

  129. Est. Tue, May 4, 2027

    Stage 4 · Day 120 · Validation

    End-to-end acceptance test

    One test that exercises the whole toolkit end to end.

  130. Est. by May 4, 2027

    Stage 4 · Deliverable

    Simulation Reliability Toolkit

    A tool that runs simulation scenarios, collects results, compares them with a baseline, and flags regressions.

    • To do: An experiment reproduces with one command
    • To do: Results are compared with a baseline using stated criteria, and a report is produced
    • To do: Regressions are detected automatically
  131. Reserve

    Buffer & Final Review

    Two weeks kept free on purpose. They absorb whatever ran late, then close the plan: a clean install on a fresh machine, a recorded demo, a published technical README, and a final audit of every deliverable against this roadmap.

  132. Est. Wed, May 5, 2027

    Reserve · Day 121 · Review

    Revisit the weakest prerequisite

    Go back to the topic that held things up the most.

  133. Est. Thu, May 6, 2027

    Reserve · Day 122 · Review

    Fix flaky Gazebo or ROS configuration

    Fix configuration that fails only sometimes.

  134. Est. Fri, May 7, 2027

    Reserve · Day 123 · Review

    Re-run a failed sensor experiment

    Re-run a sensor experiment that did not work the first time.

  135. Est. Mon, May 10, 2027

    Reserve · Day 124 · Review

    Strengthen tests and diagnostics

    Add the tests and diagnostics that were missing.

  136. Est. Tue, May 11, 2027

    Reserve · Day 125 · Review

    Verify the reproducible demo

    Check the demo still reproduces from scratch.

  137. Est. Wed, May 12, 2027

    Reserve · Day 126 · Review

    Improve the held-out dataset evaluation

    Improve the evaluation on held-out data.

  138. Est. Thu, May 13, 2027

    Reserve · Day 127 · Review

    Resolve remaining bridge issues

    Close the remaining Virtual Sensor Bridge issues.

  139. Est. Fri, May 14, 2027

    Reserve · Day 128 · Review

    Independent clean install test

    Install everything on a clean machine, following only the README.

  140. Est. Mon, May 17, 2027

    Reserve · Day 129 · Review

    Record a demo and publish the technical README

    Record a demo and publish the technical README.

  141. Est. Tue, May 18, 2027

    Reserve · Day 130 · Review

    Final audit against the roadmap

    Check every deliverable against this roadmap.