SoftwareX manuscript · Minor revision

The research.
The exact artifact.

Metriplane v0.2.0 is the DOI-archived public release and primary software artifact for a manuscript submitted to SoftwareX. The related manuscript is publicly available as a non-peer-reviewed SSRN preprint (DOI: 10.2139/ssrn.7166858). The current v0.4.1 PyPI release improves packaging and delivery but does not replace or modify this frozen evidence boundary. This website does not claim SoftwareX acceptance or peer-reviewed publication.

Release relationship

Use the current package for installation and the frozen tag for manuscript evidence.

v0.4.1: package delivery

The current release adds the package-contained camera-free demo, plain-language adoption path, stricter validation, and broader release gates. It does not create new SoftwareX measurements or evidence.

Open installation and packaging details

v0.2.0: manuscript artifact

The DOI, evidence package, expected outputs, and reproduction commands remain tied to the exact v0.2.0 tag and its recorded evidence commits.

Open exact research release

Reviewer path

What a reviewer can inspect and reproduce.

Release and citation

GitHub release v0.2.0, its tag commit, the Zenodo DOI, the SSRN preprint DOI, MIT license, and citation metadata identify the artifact and manuscript.

Core reproduction

The camera-free, replay-based, observe-only path uses the exact tag and writes fresh output only under /tmp.

Archived evidence

Captured logs, the Incident Report (formal artifact name: Cell Truth Report), bundle, regression YAML, and checksums in evidence/paper_v2_0/ are author-run evidence for inspection.

Manuscript relevance

The manuscript artifact centers on a bounded workflow.

The claim is not that Metriplane controls industrial hardware or validates a production factory. It is that a replayed workcell incident can become an inspectable evidence bundle, be verified locally, and be preserved as a repeatable regression check.

replayed/calibrated state
-> event timeline
-> INC-0001 incident
-> Incident Report (Cell Truth Report artifact)
-> evidence bundle
-> local verification
-> repeatable regression check

Validation paths

Core reproduction and the maintainer gate are separate.

Core reproduction

The exact v0.2.0 workflow uses temporary paths, requires no Playwright, Chromium, Docker, ROS 2, or camera, and does not overwrite evidence/paper_v2_0/. The public independent core workflow passed.

Run the core workflow

Optional full maintainer gate

The optional gate requires additional browser and system dependencies. 580 passed is archived author-run release evidence. The public independent macOS gate recorded 575 passed, 3 skipped, 2 failed, so the public full suite is not a complete pass.

See gate commands

Evidence

Claims that matter for manuscript review.

Claim Evidence How to verify Boundary
v0.2.0 is archived as a public research release GitHub release and Zenodo DOI 10.5281/zenodo.20736619 Open the exact v0.2.0 release and Zenodo record. v0.4.1 is the current installable software release; SoftwareX acceptance or peer review is not claimed.
The archived author-run maintainer gate recorded 580 passed Archived author-run evidence/paper_v2_0/test_output.txt reports 580 passed. Inspect the archived file; do not use evidence/paper_v2_0/ as a fresh rerun destination. The public independent macOS gate recorded 575 passed, 3 skipped, 2 failed; the public full suite is not a complete pass.
The camera-free replay is deterministic deterministic_replay.txt reports pass=true, 0.0 cm position difference, and 0 event mismatches. Run with RUNS=/tmp/metriplane-softwarex-runs and the checked-in demo session. Checked-in demo session only; no live-camera claim.
The assembly-cell replay produces one incident atlas_assembly_cell_run.txt reports 6 physical events, 1 process deviation, and 1 incident. Run metriplane atlas run with the assembly_cell domain pack and --out /tmp/metriplane-softwarex-atlas. One deterministic assembly-cell domain pack and replay.
INC-0001 has a readable Incident Report cell_truth_report.md records a 35.0 s wait for torque_driver_1. Inspect archived 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

Manuscript readiness includes saying what is not proven.

The artifact is observe-only research software for a bounded, planar/tagged-asset workcell. It does not claim robot or machine control, safety certification, quality approval, successful remediation, arbitrary anomaly detection, marker-free tracking, full 3D reconstruction, production-factory validation, or complete external validation.

Next step

Inspect the exact manuscript artifact.

Follow the reviewer guide through the frozen release, archived evidence and fresh reproduction path.