Organize and view your data#

The Nominal data model can be shaped to fit your workflow. Start from how you test, which determines the structure. Then add how you use the data, which works with any structure. Or, skip directly to the three underlying approaches.

How you test#

I have data right now and I want to see it right now, I am not worried about organizing it yet

Quick visualization

Quick visualization

I have a static test station and need to execute tests repeatably and compare their results

Repeatable test execution

Repeatable test execution

I build and rework test rigs while the hardware is still changing. I want to see my data right away, and decide how to organize it once I know what it is.

Test station development

Test station development

We're developing a controller on a handful of dev boards. I probe some signals by hand and script the rest, rework boards as bugs turn up, and want each board's data live now and comparable later.

Controller development

Controller development

I don't have hardware yet. I'm building software, test procedures, and simulations, and I need those results to line up with real tests later.

Simulation before hardware

Simulation before hardware

How you use the data#

These work with any of the approaches, and you can combine them, such as live monitoring of a hardware control loop.

I sit on console during a test and watch live telemetry from the system in front of me. I want every channel on screen, and calculations that still work on units that record fewer channels.

Live monitoring on console

Live monitoring during a test

I don't want to read plots after every test. I want each test checked against its limits automatically, with a clear pass or fail.

Automated pass/fail checks

Automated pass/fail checks

After a test I pull channels from a time range, sometimes from several units, analyze them in Python, and put the results back next to the original data.

Post-test analysis

Post-test analysis