# Cross-Validation and Accuracy

Channel: release; package: 1.8.0; source: 7d1e97331656dd74ad0f5471653ac0c5effdff70

Page: https://remilab.ai/rfx/versions/v1.8.0/guide/validation/
Source: https://github.com/bk-squared/rfx/blob/7d1e97331656dd74ad0f5471653ac0c5effdff70/docs/public/guide/validation.mdx

Validation evidence for rfx is kept on three pages, split by the question you
are asking:

- **Which configuration should I start from, and which calculator has narrower
  limits?** [Recommended Configuration](https://remilab.ai/rfx/versions/v1.8.0/validation/reference-lane/) — the
  uniform Cartesian Yee starting point, plus the per-calculator restrictions for
  waveguide, microstrip-line, lumped/wire, coaxial, graded-mesh and
  differentiable work.
- **Is this exact combination supported, and what must fail?**
  [Support Boundaries](https://remilab.ai/rfx/versions/v1.8.0/api/support-boundaries/) — the status legend, the
  S-parameter API table, and the combinations that are required to raise rather
  than return a number.
- **What has actually been measured, against what reference, with which pass
  criterion?** [Benchmarks](https://remilab.ai/rfx/versions/v1.8.0/guide/benchmarks/) — every case in
  `validation/crossval/manifest.json` with its reference, gate and reproduce
  command. [Cross-Solver Validation](https://remilab.ai/rfx/versions/v1.8.0/validation/cross-solver/) explains the
  exit codes.

A completed run, a clean preflight, and an exported artifact are none of these.