Cross-Validation and Accuracy
This page gives the short public version of rfx validation status.
Recommended default lane
Section titled “Recommended default lane”The most mature public path is the uniform Cartesian Yee RF/FDTD lane:
- cavity and waveguide-style RF problems
- patch-style resonance workflows
- probes and Harminv resonance extraction
- selected port and S-parameter workflows
- benchmarked far-field workflows
Use this lane when you want the safest starting point.
Under active validation
Section titled “Under active validation”The following features are useful, but should be treated as experimental or under active validation:
- non-uniform mesh workflows
- distributed execution
- Floquet/Bloch periodic workflows
- SBP-SAT subgridding
- coaxial and advanced port workflows
- inverse-design extensions
These features may have examples and tests, but their support boundaries are narrower than the default lane.
Recommended public examples
Section titled “Recommended public examples”| Example | Role |
|---|---|
examples/crossval/05_patch_antenna.py | current patch cross-check and practical antenna reference |
examples/crossval/11_waveguide_port_wr90.py | rectangular waveguide-port reference workflow |
examples/nonuniform_patch_demo.py | quick non-uniform thin-substrate demo; experimental lane |
examples/inverse_design/multilayer_ar_coating.py | inverse-design demo with a conservative public scope |
Practical takeaway
Section titled “Practical takeaway”Lead public messaging with the recommended uniform Yee RF lane. Mention experimental lanes only when the user specifically needs them, and keep those descriptions scoped to current examples and limitations.