FerrisOxide

Rust-centered signal validation

Evidence for signals that need to be trusted.

FerrisOxide turns CSV waveform data into auditable pass/fail evidence: measurements, criteria, reports, plots, and portable rule-package artifacts for engineering review.

Explore the docs Understand the project

Built for engineering review, not hand-wavy plots.

FerrisOxide is deliberately documentation-heavy because signal validation needs repeatable criteria, preserved raw data, and evidence a reviewer can inspect later.

1 same CSV and config produce repeatable reports
7+ criteria families for waveform evidence
4 evidence surfaces: text, JSON, SVG, rule packages
0 certification or live hardware claims

What it does today.

The implemented MVP focuses on local files, auditable criteria, and software-only validation fixtures.

Waveform reconstruction

Load local CSV data, map time and signal channels, preserve raw samples, and track metadata such as units, sample timing, lineage, and tolerance.

Criteria and measurements

Evaluate voltage ranges, state transitions, response latency, pulse width, stable-state duration, transient events, and rise/fall time.

Reviewable evidence

Produce text and JSON reports, SVG plots, annotated evidence overlays, portable rule packages, manifests, checksums, and qualification-style software evidence reports.

From captured signal to reviewable artifact.

The desktop workflow is a software evidence path. It does not claim live DAQ, hardware control, certification, or production controller readiness.

01 CSV waveform data
02 Channel mapping
03 Measurements and criteria
04 Reports and plots
05 Rule package evidence

A practical example: heated actuator response.

The repository includes a software-only heated actuator scenario. A command signal goes high, feedback must respond within a fixed window, a stable high interval must hold, transient lows are bounded, and the supply rail must stay inside limits.

FerrisOxide makes those assumptions explicit in configuration and then reports the measured value, required value, timestamp, sample index, channel, and reason for each pass or fail.

Read the example path Open the source repo
test-verification-config.toml software evidence 
command goes high at 1.000 s
feedback responds within 50 ms
feedback remains stable for 500 ms
transient low must stay below 1 ms
supply rail stays inside 4.75 V..5.25 V

Know the boundaries before you build on it.

FerrisOxide is a validated MVP slice. It is not a finished commercial product, certified test system, live DAQ integration, GUI, or production controller runtime.

In scope

  • Local CSV input and TOML configuration.
  • Local text, JSON, SVG, and rule-package evidence.
  • Software-only validation fixtures and parity tests.
  • Rust libraries, CLI workflow, and no_std-compatible foundations.

Out of scope

  • Live DAQ vendor SDKs or hardware control.
  • Hardware-in-the-loop execution or production RTOS runtime.
  • Full GUI, cloud service, accounts, or multi-user workflow.
  • Certified aerospace validation or safety certification claims.