Protocol and waveform checks
RFix scenarios cover radar, GNSS, private-radio, generic modulation, channel effects, and analysis flows with regression tests around generation behavior.
Validation proof
RF data generation should be inspectable, repeatable, and exportable.
RFix validation is built around the artifacts engineers actually need: generated recordings, metadata, scenario graphs, decoder checks, and clear runtime limits.
Engineering proof
Where confidence comes from.
Decoder-backed validation
Integration coverage can compare generated outputs against external RF tools such as GNSS-SDR, DSD-FME, BTLE tooling, tetra-kit, and GNU Radio where applicable.
Export integrity
Generated outputs are packaged as IQ recordings, SigMF metadata, and portable RFix projects so samples remain interpretable outside the UI.
Repeatability and audit
Scenarios keep graph state, parameters, and metadata together so lab teams can replay a case and RFML teams can inspect dataset provenance.
Known limits
Clear boundaries for evaluation.
- Desktop runtime is the primary path for large datasets and offline/private work, while the browser runtime is recommended for demos with smaller recording sizes.
- Field testing remains the final authority for operational deployment decisions.