NLSYS filters ordered signals, compiles verified nonlinear dynamics and produces bounded control recommendations—without a hand-designed filter or a supplied governing model.
Ordered numeric signalsHeld-out free-runExplicit support boundariesSDRE + NMPC control stack
01 · MEASURERaw signal
→
02 · FILTERClean dynamics
→
03 · MODELExecutable dynamics
Free-run · Passport · support
→
04 · CONTROLBounded action
Workflow illustration — not measured performance data.
One engine, three jobs
Start where the value is obvious
Each product is independently usable. The same ordered data can then move from cleaning to modelling and from modelling to control without changing the underlying evidence discipline.
FILTER
Recover the signal without designing a filter
Self-tuning filtration in instant, bounded-latency and offline modes, with gap recovery, prediction, health and System Passports.
Turn measured dynamics into bounded recommendations
Use full-model SDRE under a real-time cadence and NMPC where a slower optimisation loop is acceptable. Execution remains with the operator or supervisory system.
The tables below give recorded outcomes and their stated protocol boundaries. Review the full rows, applicable cases and limitations before comparing results across methods.
Choose the relevant product, inspect its input requirements and try the available example. Use public evidence when it helps your evaluation; a benchmark visit is not required before using the workspace.
01Open a public proof
Read the full protocol, baseline and limitations.
02Run the built-in example
Use the example already available in the current account interface.
03Use your own data
Upload a file or connect an ordered stream.
04Take the artifact
Download the cleaned output, Passport or executable model.
05Repeat or automate
Move to a subscription, shared workflow, API or Controller only when the job repeats.
Entry points
Use the shortest route for the data already in front of you
No account
Battery file check
Free
Screen a cycler CSV or TSV locally in the browser. The file is not uploaded.
Every successful run should leave something another engineer can inspect
NLSYS outputs are designed for hand-off: cleaned files, event evidence, System Passports, executable nonlinear models, validation reports, support boundaries, manifests and checksums.