Demo Scripts & Simulations

ROBIN now uses two canonical demo scripts:

  • demo/profiles/welding_profile.py

  • demo/profiles/spray_coating_profile.py

Each script validates both operational modes with real AI-backed deviation checks and produces alert entities when simulation data deviates beyond tolerance.

Canonical Demos

Script

What it validates

python demo/profiles/welding_profile.py --mode both --duration 120 --interval 2

Welding profile, parameter-driven + geometry-driven in one run, telemetry updates, dashboard refresh, and real alert generation from POST /check-deviation.

python demo/profiles/spray_coating_profile.py --mode both --duration 120 --interval 2

Spray coating profile, same dual-mode validation with domain-specific vocabulary and units.

Dual-Mode Validation Logic

Parameter-driven

  1. Operator sets initial process parameters.

  2. AI predicts expected geometry.

  3. Telemetry is streamed.

  4. Alert processor compares measured geometry to AI-predicted geometry.

  5. Deviation alerts are generated when tolerance is exceeded.

Geometry-driven

  1. Operator sets target geometry.

  2. AI suggests process parameters for that target.

  3. Telemetry is streamed.

  4. Alert processor compares measured geometry against the expected geometry from AI-suggested parameters.

  5. In geometry-driven mode, deviation checks use fixed AI-guided/setpoint parameters for the run (not per-sample live measured parameters).

  6. Reason: this keeps the deviation metric anchored to the planned operating point and avoids conflating geometric quality with control-loop jitter.

  7. Deviation alerts are generated when tolerance is exceeded.

Press Start to Begin

When you run a demo script (without --no-prompt), it will create the process and configure AI expectations, then pause and wait for you to press Start from the dashboard UI. The terminal will print:

Waiting for Start from the dashboard UI for process "<id>"...
  Open http://localhost:5174, select process "<id>", and press Start.

In the dashboard:

  1. Select the process from the top-bar dropdown.

  2. Click Start in the Robot Control panel.

The simulation detects the start signal and begins streaming telemetry. The dashboard progress bar tracks the actual simulation elapsed time (not just measurement count).

Tip

Pass --no-prompt to skip the Start-button wait and stream data immediately. This is useful for CI, scripted verification, or when you want the demo to start unattended.

What to watch in the dashboard:

  • Progress bar advances with actual simulation progress (elapsed / total).

  • Measurement KPIs update in real time.

  • Telemetry chart continues streaming.

  • 3D Visualization shows the UR5 robot performing a welding sweep driven by simulation progress.

  • Deviation Monitor toggles between OK/Deviation/ALERT with mode-aware source.

  • Alerts panel receives warning/critical entries during injected deviation windows.

Rebuild + Verification Checklist

Use this exact sequence when you need to ensure recent code changes are live and the dashboard is plotting real Mintaka-stored data.

  1. Rebuild and recreate backend, dashboard, and visualization containers:

docker compose build alert-processor robin-dashboard robin-viser
docker compose up -d --force-recreate alert-processor robin-dashboard robin-viser
docker compose ps alert-processor robin-dashboard robin-viser

  1. Start a non-interactive dual-mode welding demo:

BASE="verify-$(date +%s)"
python demo/profiles/welding_profile.py \
    --process-id "$BASE" \
    --mode both \
    --duration 60 \
    --interval 1 \
    --no-prompt

  1. In the dashboard (http://localhost:5174), select ${BASE}-parameter then ${BASE}-geometry from the top bar process selector and confirm in Live Ops -> Telemetry:

  • source chip shows Mintaka stored data

  • poll chip shows Poll 1s (Active Run) or Poll 2s (Demo Mode)

  • chart points keep advancing at that cadence

  1. API verification (source must be Mintaka):

curl -s "http://localhost:8001/process/${BASE}-parameter/measurements?last=5" | jq '.debug_info.source, .measurements'

Expected first output line:

"mintaka"

  1. Optional raw Mintaka cross-check:

curl -s "http://localhost:9090/temporal/entities/urn:ngsi-ld:Process:${BASE}-parameter?attrs=measuredHeight,measuredWidth,measuredSpeed,measuredCurrent,measuredVoltage&timeproperty=observedAt&timerel=between&timeAt=1970-01-01T00:00:00Z&endTimeAt=2035-01-01T00:00:00Z&options=temporalValues&lastN=5" | jq

Mode-specific runs

You can run one mode at a time:

python demo/profiles/welding_profile.py --mode parameter_driven
python demo/profiles/welding_profile.py --mode geometry_driven

python demo/profiles/spray_coating_profile.py --mode parameter_driven
python demo/profiles/spray_coating_profile.py --mode geometry_driven

Supporting Utilities (Non-canonical)

The following scripts are still available for troubleshooting or specific integration tasks, but they are not the primary demos:

  • demo/validate-setup.sh - service health checks

  • demo/cleanup-demo.sh - remove demo entities

  • demo/simulation-demo-rosbag.sh - ROS 2 bag replay path

  • demo/interactive-demo.sh - interactive walkthrough

Cleanup

./demo/cleanup-demo.sh weld-
./demo/cleanup-demo.sh coating-

For a full reset (Orion + Mintaka temporal history), see Reset Demo Data for Fresh Replay.