Waveguide crossing — O-band through and crosstalk spectra#
validated · 2026-08-28
This case compares a local FDTDX result with pinned reference data generated by Tidy3D. The originating Tidy3D example is WaveguideCrossing.ipynb, pinned at commit c37c785d52e9.
Parameters → exact geometry → voxelized material → local FDTDX run → simulated field → quantitative analysis. Every code cell and retained output is visible, and the .ipynb source is downloadable.
This page is the compact benchmark record. The linked notebook is the primary scientific documentation and contains the actual simulation evidence.
What is exercised#
Compact reconstruction of the official convex-cosine O-band crossing. One 3-D broadband run measures fundamental-mode through power and orthogonal crosstalk at 1.26, 1.31, and 1.36 um on a 25 nm grid. Touching silicon tapers are boolean-unioned before rasterization so their relative geometry is preserved without per-polygon grid snapping.
This case runs at its declared full benchmark resolution (resolution factor 1.0).
Reconstruction choices#
The official device dimensions, material stack, excitations, and measured observable are retained where they determine the physics. The local scene uses 376 × 376 × 64 cells and the common port/source normalization machinery. The shared energy-decay cutoff stopped the run after 13,982 of 31,470 allowed steps. Geometry is rasterized as connected material before placement when touching polygons would otherwise introduce grid-snapping seams.
The field panel above is explicitly a schematic of the device and propagation path. The curves and scalar values in the result panel are executed benchmark outputs: solid circles are FDTDX; dashed crosses are the frozen Tidy3D reference.
Recorded result#
Metric |
Observed / error |
Reference / limit |
Error |
Effective budget |
Result |
|---|---|---|---|---|---|
|
0.0387861 |
0.1 |
0.0387861 |
0.1 |
PASS |
|
0.00106898 |
0.01 |
0.00106898 |
0.01 |
PASS |
|
0.0403683 |
0.08 |
0.0403683 |
0.08 |
PASS |
The table is rendered from progress.json; it is not a hand-written success claim. For metrics that report an error directly, the “observed” column repeats that error and the reference column is the acceptance threshold.
Reproduce#
uv run fdtdx-bench run --case device_waveguide_crossing
Implementation and provenance: benchmarks/cases/device_waveguide_crossing/case.yaml, benchmarks/cases/device_waveguide_crossing/run.py, benchmarks/goldens/device_waveguide_crossing.npz.