Loading
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, the
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add NVIDIA/skills --skill amc-run-rtsp-calibration -a cursor -y
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, then runs calibration.
Calibrate a new dataset from live RTSP camera streams via the AutoMagicCalib REST API. Use when the user provides RTSP URLs or asks to calibrate live cameras; VIOS records clips, AMC ingests them, then runs calibration.
Activate this skill when the user wants to calibrate from live RTSP camera streams. Typical prompts:
rtsp://... URLsVIOS records fixed-duration clips from each stream, the AMC microservice ingests those clips into a project, then the workflow follows the same verification, calibration, polling, and results path as pre-recorded MP4 calibration.
Do not use this skill for local MP4 files already on disk; route those requests to skills/amc-run-video-calibration/SKILL.md. Do not use it for the bundled sample dataset; route that to skills/amc-run-sample-calibration/SKILL.md.
Never reuse files from the bundled sample dataset, extracted sample zip, assets/, or previous projects for RTSP calibration unless the user explicitly provides those paths for this RTSP scene. Similar camera names, stream counts, or cam_00/cam_01 ordering are not evidence that sample alignment, layout, GT, or detector settings apply.
skills/amc-setup-calibration-stack/SKILL.md if needed).VIOS_BASE_URL is configured in the AMC microservice environment before capture starts.requests installed when using the bundled script.RTSP URLs may contain usernames, passwords, hostnames, or network topology. Do not print full RTSP URLs if credentials are embedded. This skill does not handle bearer credentials; if the VIOS deployment requires authentication, stop and hand the user to a manual admin-managed workflow instead of collecting or relaying secrets in chat, scripts, or logs.
cam_00, cam_01, ... if the user does not provide names.60; prefer 120-180 or more when the scene has sparse motion.http://<HOST_IP>:8000 or http://<HOST_IP>:8000/v1./data/my_rtsp_calib/;If the user does not provide a local asset source, stop and ask whether they want to provide a path or use UI upload. Give the UI link as http://<HOST_IP>:<AUTO_MAGIC_CALIB_UI_PORT>; the default UI port is 5000.
RTSP clips are recorded by VIOS, so there is no local videos directory to anchor file discovery. Only scan a directory the user explicitly provided for this RTSP scene. If the user provides a settings file path, use that file's directory as the scan directory. If the user provides a calibration asset directory, scan only that directory. Otherwise ask this question before planning uploads or calibration:
Do you have a local calibration asset directory or settings file for these RTSP streams, or should you upload/tune settings and alignment in the AMC UI at
http://<HOST_IP>:<AUTO_MAGIC_CALIB_UI_PORT>?
| File | Candidate filenames | UI fallback |
|---|---|---|
| Calibration settings | Explicit user path, or settings.json, config.json, or calibration_config.json in the user-provided asset directory | UI Step 3: Parameters |
| Alignment JSON | Explicit user path, or alignment_data.json in the user-provided asset directory/settings directory | UI Step 4: Alignment |
| Layout PNG | Explicit user path, or layout.png in the user-provided asset directory/settings directory | UI Step 4: Alignment |
| Ground truth zip | Optional explicit user path, or GT.zip/gt.zip in the user-provided asset directory | Omit metrics |
Posting the settings file replaces UI Step 3 and may pin detector or detector_type. If it pins resnet or transformer, pass that same detector to /calibrate. If no settings file pins a detector, ask the user which detector to use; do not silently default to resnet.
sensor_id per stream if the cameras are already registered in VIOS. Leave unset for auto-registration.GT.zip) for evaluation metrics.vggt_state == "READY".The bundled script in scripts/run_rtsp_calibration.py implements this sequence end to end. Use the prose below for decisions, UI fallback, and troubleshooting.
Confirm the AMC microservice is reachable:
curl -sf http://<HOST_IP>:<MS_PORT>/v1/ready
Confirm VIOS is reachable before starting capture. Probe in this order and stop at the first working URL:
: "${REPO_ROOT:?set REPO_ROOT to the auto-magic-calib checkout. Run amc-setup-calibration-stack Step 0b first.}"
grep -q "AutoMagicCalib" "$REPO_ROOT/README.md" 2>/dev/null && grep -q "auto-magic-calib-ms" "$REPO_ROOT/compose/ms/compose.yml" 2>/dev/null || { echo "ERROR: REPO_ROOT is not an auto-magic-calib checkout: $REPO_ROOT" >&2; exit 1; }
VIOS_BASE_URL=""
# Default local VIOS port.
if curl -sf http://localhost:30888/vst/api/v1/sensor/list >/dev/null 2>&1; then
VIOS_BASE_URL="http://localhost:30888"
echo "VIOS detected at $VIOS_BASE_URL"
fi
# Running AMC microservice container environment.
if [ -z "$VIOS_BASE_URL" ]; then
VIOS_BASE_URL=$(docker exec auto-magic-calib-ms-1 printenv VIOS_BASE_URL 2>/dev/null)
fi
if [ -n "$VIOS_BASE_URL" ]; then
curl -sf "${VIOS_BASE_URL}/vst/api/v1/sensor/list" >/dev/null \
&& echo "VIOS up at $VIOS_BASE_URL" \
|| { echo "VIOS_BASE_URL=$VIOS_BASE_URL is set but not responding"; VIOS_BASE_URL=""; }
fi
[ -n "$VIOS_BASE_URL" ] || {
echo "VIOS is not reachable. Export VIOS_BASE_URL=http://<VIOS_HOST>:30888 and relaunch the AMC microservice." >&2
exit 1
}
If VIOS is not reachable, ask the user to deploy VIOS and provide the base URL. Do not start RTSP capture until ${VIOS_BASE_URL}/vst/api/v1/sensor/list returns 200.
If VIOS is reachable but the AMC microservice is missing VIOS_BASE_URL, do not edit checked-in compose files. Export the variable and relaunch the microservice with a temporary compose override:
cd "$REPO_ROOT/compose"
export VIOS_BASE_URL="http://<VIOS_HOST>:30888"
OVERRIDE_FILE="${TMPDIR:-/tmp}/amc-vios.override.yml"
cat > "$OVERRIDE_FILE" <<'YAML'
services:
auto-magic-calib-ms:
environment:
- VIOS_BASE_URL=${VIOS_BASE_URL}
YAML
docker compose -f compose.yml -f "$OVERRIDE_FILE" up -d auto-magic-calib-ms
docker exec auto-magic-calib-ms-1 printenv VIOS_BASE_URL
A host-shell export alone is not enough after the container is already running; the microservice process must be restarted with VIOS_BASE_URL in its environment.
POST /v1/create_project with form field project_name. Save the returned project_id.
POST /v1/rtsp/capture/<project_id>
Content-Type: application/json
{
"streams": [
{"rtsp_url": "rtsp://...", "camera_name": "cam_00", "sensor_id": null},
{"rtsp_url": "rtsp://...", "camera_name": "cam_01", "sensor_id": null}
],
"duration_seconds": 180,
"ssl_verify": true
}
The response can nest session fields under session:
{"code": 0, "message": "...", "session": {"session_id": "...", "status": "STARTING"}}
Save session.session_id.
Poll every 10 seconds:
GET /v1/rtsp/capture/<project_id>/<session_id>
Session lifecycle:
STARTING -> RECORDING -> COMPLETED -> INGESTING -> INGESTED
-> ERROR
RECORDING -> CANCELLED
When capture reaches COMPLETED, ingest the recorded clips into the AMC project:
POST /v1/rtsp/capture/<project_id>/<session_id>/ingest
After ingest succeeds, the project has video files attached and the rest of the workflow matches the MP4 upload path.
Need to stop early: POST /v1/rtsp/capture/<project_id>/<session_id>/stop. A partial clip can still be ingested if VIOS produced one.
Other session endpoints:
GET /v1/rtsp/sessions/<project_id> - list sessions for a project.Resolve local files using the anchor-file pattern above. Upload resolved files:
| File | Endpoint | Notes |
|---|---|---|
| Calibration settings | POST /v1/config/<project_id> | JSON body posted as-is; replaces UI Step 3 |
| Alignment JSON | POST /v1/upload_alignment/<project_id> | Multipart alignment_file |
| Layout PNG | POST /v1/upload_layout/<project_id> | Multipart layout_file |
| Ground truth zip | POST /v1/upload_gt_file/<project_id> | Optional |
| Focal lengths | POST /v1/upload_focal_length/<project_id> | Optional repeated focal_length values |
Use only files from explicit user-provided paths or a user-provided calibration asset directory. Do not extract or scan sample data to find fallback settings, alignment, layout, or GT.
If settings are missing, direct the user to UI Step 3: Parameters at http://<HOST_IP>:<AUTO_MAGIC_CALIB_UI_PORT>, then ask which detector to use (resnet or transformer) before calibration. If alignment or layout is missing, direct the user to UI Step 4: Alignment for this project. For RTSP projects, videos are already ingested; do not re-upload videos in the UI fallback.
Before continuing after UI Step 4, verify:
PROJECT_ID=<project_id>
: "${REPO_ROOT:?set REPO_ROOT to the auto-magic-calib checkout. Run amc-setup-calibration-stack Step 0b first.}"
grep -q "AutoMagicCalib" "$REPO_ROOT/README.md" 2>/dev/null && grep -q "auto-magic-calib-ms" "$REPO_ROOT/compose/ms/compose.yml" 2>/dev/null || { echo "ERROR: REPO_ROOT is not an auto-magic-calib checkout: $REPO_ROOT" >&2; exit 1; }
HOST_PROJECTS="${PROJECTS_DIR:-$(cd "$REPO_ROOT" && realpath projects)}"
ls "$HOST_PROJECTS/project_${PROJECT_ID}/manual_adjustment/"
# Expected: alignment_data.json, layout.png
If the AMC stack stores project outputs outside the default projects/ directory, set PROJECTS_DIR explicitly before running the check above. Do not read compose/.env for project paths during this workflow.
Verify:
POST /v1/verify_project/<project_id>
The project must return project_state == "READY".
Confirm the plan before calibrating. Summarize:
resnet or transformer.Start calibration:
POST /v1/calibrate/<project_id>
Content-Type: application/json
{"detector_type": "<resnet-or-transformer>"}
Poll:
GET /v1/get_project_info/<project_id>
Stop on COMPLETED or ERROR. On error, fetch GET /v1/amc/calibrate/<project_id>/log.
Fetch results:
GET /v1/result/<project_id>/evaluation_statistics
Only expect evaluation statistics when GT was uploaded.
After AMC calibration completes, read project_info.vggt_state from GET /v1/get_project_info/<project_id>.
vggt_state == "READY", ask whether to run VGGT refinement.POST /v1/vggt/calibrate/<project_id>, poll vggt_state, then fetch GET /v1/vggt_results/<project_id>/evaluation_statistics.Use the bundled script from the amc-run-rtsp-calibration skill package, not from the auto-magic-calib repo root. If the user points the agent at this skill folder directly instead of installing it, set AMC_RTSP_SKILL_DIR to the directory containing this SKILL.md, or run the command from that directory.
Common environment variables:
export BASE_URL=http://<HOST_IP>:8000
export PROJECT_NAME=rtsp_calibration_run
export RTSP_URLS='rtsp://user:pass@cam0/stream,rtsp://user:pass@cam1/stream'
export CAMERA_NAMES='cam_00,cam_01'
export DURATION_SECONDS=180
export VIOS_BASE_URL=http://<VIOS_HOST>:30888
export CALIB_ASSET_DIR=/path/to/rtsp-calibration-assets
# Or provide explicit CONFIG_FILE, ALIGNMENT_JSON, LAYOUT_PNG, and optional GT_ZIP.
export DETECTOR_TYPE=transformer # Required when settings do not set detector/detector_type.
export AMC_UI_URL=http://<HOST_IP>:5000
export RUN_VGGT=false
# Optional but recommended: REPO_ROOT points to the auto-magic-calib checkout.
# PROJECTS_DIR can be set explicitly when project outputs live elsewhere.
if [ -z "${DEEPSTREAM_REPO_ROOT:-}" ] && [ -n "${REPO_ROOT:-}" ] && [ -d "$REPO_ROOT/../../skills/amc-run-rtsp-calibration" ]; then
DEEPSTREAM_REPO_ROOT="$(cd "$REPO_ROOT/../.." && pwd)"
fi
SCRIPT_PATH=""
for candidate in \
"${AMC_RTSP_SKILL_DIR:+$AMC_RTSP_SKILL_DIR/scripts/run_rtsp_calibration.py}" \
"$PWD/scripts/run_rtsp_calibration.py" \
"${DEEPSTREAM_REPO_ROOT:+$DEEPSTREAM_REPO_ROOT/skills/amc-run-rtsp-calibration/scripts/run_rtsp_calibration.py}" \
"$PWD/skills/amc-run-rtsp-calibration/scripts/run_rtsp_calibration.py" \
"$HOME/.claude/skills/amc-run-rtsp-calibration/scripts/run_rtsp_calibration.py" \
"$HOME/.codex/skills/amc-run-rtsp-calibration/scripts/run_rtsp_calibration.py" \
"$HOME/.cursor/skills/amc-run-rtsp-calibration/scripts/run_rtsp_calibration.py"; do
if [ -f "$candidate" ]; then
SCRIPT_PATH="$candidate"
break
fi
done
[ -n "$SCRIPT_PATH" ] || {
echo "ERROR: could not find amc-run-rtsp-calibration/scripts/run_rtsp_calibration.py" >&2
echo "Set AMC_RTSP_SKILL_DIR to the amc-run-rtsp-calibration skill directory, or run this block from that directory." >&2
exit 1
}
python3 "$SCRIPT_PATH"
Alternative stream input:
export STREAMS_JSON='[
{"rtsp_url":"rtsp://cam0/stream","camera_name":"cam_00","sensor_id":null},
{"rtsp_url":"rtsp://cam1/stream","camera_name":"cam_01","sensor_id":null}
]'
Optional env vars are CALIB_ASSET_DIR, CONFIG_FILE, ALIGNMENT_JSON, LAYOUT_PNG, GT_ZIP, FOCAL_LENGTHS, DETECTOR_TYPE, AMC_UI_URL, SSL_VERIFY, RUN_VGGT, REPO_ROOT, and PROJECTS_DIR. SSL_VERIFY defaults to true; only set SSL_VERIFY=false for loopback testing. If the VIOS deployment requires bearer authentication, stop and use a manual admin-managed capture flow instead of routing credentials through this skill.
COMPLETED.verify_project returns READY.project_state == "COMPLETED".Results persist on the AMC server under:
projects/project_<project_id>/
|-- manual_adjustment/
| |-- alignment_data.json
| `-- layout.png
|-- output/
| |-- single_view_results/cam_XX/
| | |-- camInfo_hyper_XX.yaml
| | `-- trajDump_Stream_0_3d.txt
| `-- multi_view_results/BA_output/results_ba/
| |-- initial/camInfo_XX.yaml
| `-- refined/camInfo_XX.yaml
`-- calibration.log
| Issue | Fix |
|---|---|
VIOS /vst/api/v1/sensor/list returns connection refused | VIOS is not running or not reachable from this host. Ask the user to deploy VIOS or provide the reachable base URL. |
| Capture endpoint returns 503 or "VIOS not configured" | Export VIOS_BASE_URL, relaunch the microservice with the temporary compose override from Step 0, then retry capture. |
Session stuck in STARTING | VIOS accepted the request but sensors may not be online. Check ${VIOS_BASE_URL}/vst/api/v1/sensor/list and wait 20-30 seconds after sensor restarts. |
Session stuck in RECORDING past duration_seconds | Call POST /v1/rtsp/capture/<project_id>/<session_id>/stop, then ingest the partial clip if available. |
| Ingest fails with "No clip available" | The recording window may not overlap the VIOS timeline. Wait for sensors to become online, then start a new capture. |
| 400 "empty streams" | Pass at least one stream object with rtsp_url and camera_name. |
| 400 "duration too short" | Use duration_seconds >= 60. |
404 on /v1/rtsp/capture/<project_id> | Create the project first with /v1/create_project. |
verify_project is not READY after ingest | Check project info and confirm expected videos, alignment, and layout are attached. |
Calibration reaches ERROR | Fetch GET /v1/amc/calibrate/<project_id>/log; common causes are insufficient tracklets, static scenes, or incorrect alignment. |
skills/amc-setup-calibration-stack/SKILL.md - start AMC microservice and UI first.skills/amc-run-video-calibration/SKILL.md - calibrate from local pre-recorded MP4 files.skills/amc-run-sample-calibration/SKILL.md - verify the stack with the bundled sample dataset.