SoftwareX

v0.2.0 as a research-software artifact.

Metriplane v0.2.0 is the current DOI-archived public release and the main software artifact for the planned SoftwareX submission. v0.1.4 remains the historical DOI-archived baseline.

Current release: v0.2.0 DOI: 10.5281/zenodo.20736619 Evidence package: evidence/paper_v2_0/ Tests: 580 passed

Reviewer path

What a reviewer can inspect.

Release and citation

GitHub release, Zenodo DOI, MIT license, and citation metadata establish a stable artifact.

Reproduction

Camera-free commands validate tests, deterministic replay, Atlas run, bundle verification, and regression test.

Evidence package

Captured logs, Cell Truth Report, evidence bundle, regression YAML, and checksums are available in the repo.

Paper relevance

The paper artifact is centered on a bounded workflow.

The central claim is not that Metriplane controls industrial hardware or validates a production factory. The central claim is that a replayed workcell incident can be converted into an inspectable evidence bundle, verified locally, and reused as a generated regression test.

replayed/calibrated state
-> physical event ledger
-> INC-0001 incident
-> Cell Truth Report
-> evidence bundle
-> local verification
-> generated regression test

Evidence

Claims that matter for artifact review.

Claim Evidence How to verify Boundary
v0.2.0 is archived as a public release GitHub release and Zenodo DOI 10.5281/zenodo.20736619 Open the v0.2.0 release and Zenodo record. SoftwareX acceptance or peer review is not claimed.
The release gate passed locally evidence/paper_v2_0/test_output.txt reports 580 passed. Run PYTEST_DISABLE_PLUGIN_AUTOLOAD=1 .venv/bin/python -m pytest -q. Captured in one local release environment.
The camera-free replay is deterministic deterministic_replay.txt reports pass=true, 0.0 cm position difference, and 0 event mismatches. Run RUNS=evidence/paper_v2_0/runs ./tools/mp.sh deterministic-replay datasets/demo/session_001.jsonl. Checked-in demo session only; no live-camera claim.
The assembly-cell replay produces one incident atlas_assembly_cell_run.txt reports events=6 and incidents=1. Run metriplane atlas run with the assembly_cell domain pack. One deterministic assembly-cell domain pack and replay.
INC-0001 is explainable as a Cell Truth Report cell_truth_report.md records a 35.0 s wait for torque_driver_1. Inspect evidence/paper_v2_0/atlas_run/cell_truth_report.md. Derived from replayed planar state, not raw-video judgement.
The incident is packaged as portable evidence INC-0001.zip contains manifest, checksums, incident, timeline, report, and replay command. Inspect artifacts/INC-0001_zip_listing.txt and the bundle manifest. Local content/checksum verification; not malware scanning.

Limitations

Paper readiness includes saying what is not proven.

v0.2.0 includes Docker local replay/demo smoke evidence only. It does not add Docker benchmark, production-runtime, live-camera, replay-mode, reliability, or safety evidence, nor Isaac Sim runtime, safety certification, robot or machine control, quality-release approval, or marker-free tracking evidence.

Next step

Review the artifact like a paper reviewer.

The useful question is whether the release, evidence package, commands, and limitations make the workflow reproducible and bounded.