Inputs
Replay sessions or calibrated planar state streams representing tracked workcell assets.
Explore pages
Technical scope
A clear contract.
A bounded workcell.
Metriplane works with replayed or calibrated planar workcell state. It turns state into events, incidents, reports, bundles, verification targets, and repeatable regression checks. The software is camera-compatible for calibrated input, while the public reproduction path is camera-free and replay-based.
Architecture
The pipeline is intentionally narrow.
Input / 01
Recorded state
Assets, positions and timestamps.
Input / 02
Process rule
The requirement and its threshold.
MetriPlane
An inspectable
An inspectable
incident.
State becomes timestamped events.
Related events form a case.
Incident Report
What happened, when and why.
Evidence bundle
The case, its inputs and integrity checks.
Regression check
Detect the expected incident again.
Components
Major technical surfaces.
Process rules (domain packs)
A configuration folder describing assembly-cell assets, process steps, contracts, work orders, and the workspace.
Event timeline
Timestamped events and process deviations generated from the replayed state and process rules.
Incident model
INC-0001 captures the missing required asset, related events, timing, severity, and limitations.
Evidence bundle
Manifest, checksums, incident JSON, event timeline, report, replay command, and scoped excerpts.
Repeatable regression check
A generated YAML file checks for the expected recorded incident again.
Distribution surface
The packaged core and repository artifact are intentionally different.
Metriplane v0.4.1 distributes the core Python packages, CLI entry points, and resources for the bundled camera-free demo through PyPI. Additional repository fixtures and review assets remain outside the wheel so the frozen v0.2.0 evidence can be inspected and reproduced from an exact source checkout.
PyPI-installed core
Core Python modules, runtime dependencies, CLI entry points, and the complete package-contained missing-tool demo.
python -m pip install "metriplane==0.4.1"Source-checkout assets
Additional research datasets and process-rule configurations (domain
packs), the local dashboard, helper tools, and frozen evidence under datasets/, configs/, web/, tools/,
and evidence/.
Boundaries
Non-claims are part of the design.
The project is research software for evidence review. Its credibility comes from bounded claims, local reproduction, and explicit limits.
Observe-only
Inspect what happened. MetriPlane does not control the machine.
A bounded workcell
Planar state from tracked or tagged assets, with explicit process rules.
Replay first
A camera-free reproduction path. Integration claims require their own evidence.
Full scope and limitations
- No robot or machine control
- No safety certification
- No quality-release approval
- No people recognition
- No marker-free tracking claim
- No full 3D reconstruction claim
- No arbitrary anomaly-detection claim
- No successful-remediation claim
- No production-factory validation
- No factory-wide deployment readiness
- No complete external-validation claim
- No SoftwareX acceptance or peer-reviewed publication claim
Integration posture
Adapters exist, but runtime claims stay bounded.
The Metriplane repository includes integration surfaces for ROS 2, Omniverse, dashboards, exporters, and local operator review. The public research-evidence claim stays centered on the camera-free, local, assembly-cell v0.2.0 reproduction path unless separate runtime evidence is linked.
