Edge coupler — Gaussian beam to inverse taper

Edge coupler — Gaussian beam to inverse taper#

validated · 2026-08-28

forwardresolution 1devicereal_worldpicedge_couplergaussiantidy3d_goldenofficial_notebook

This case compares a local FDTDX result with pinned reference data generated by Tidy3D. The originating Tidy3D example is EdgeCoupler.ipynb, pinned at commit c37c785d52e9.

Open the complete executed tutorial →

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.

Edge coupler: Gaussian beam to inverse taper

This page is the compact benchmark record. The linked notebook is the primary scientific documentation and contains the actual simulation evidence.

What is exercised#

A 0.65 um 1/e-radius Gaussian beam illuminates a quadratic 190-to-500 nm silicon inverse taper. The shared Gaussian overlap normalization measures incident beam power and the output monitor measures guided fundamental-mode power at 1.50, 1.55, and 1.60 um. The 40 nm grid retains at least 4.75 cells across the smallest taper feature.

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 464 × 128 × 128 cells and the common port/source normalization machinery. The shared energy-decay cutoff stopped the run after 10,757 of 26,225 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

out

0.154969

0.2

0.154969

0.2

PASS

total

0.179794

0.2

0.179794

0.2

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_edge_coupler

Implementation and provenance: benchmarks/cases/device_edge_coupler/case.yaml, benchmarks/cases/device_edge_coupler/run.py, benchmarks/goldens/device_edge_coupler.npz.

Return to the example atlas