Euler-like bend — broadband 90-degree transmission

Euler-like bend — broadband 90-degree transmission#

validated · 2026-08-28

forwardresolution 1devicereal_worldpicbendtidy3d_goldenofficial_notebook

This case compares a local FDTDX result with pinned reference data generated by Tidy3D. The originating Tidy3D example is EulerWaveguideBend.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.

Euler-like waveguide bend: broadband bend loss

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

What is exercised#

Tangent-continuous 90-degree silicon bend retaining the official notebook’s SOI cross-section. The benchmark exercises an x-directed mode source and a y-directed mode monitor at 1.50, 1.55, and 1.60 um on a 25 nm grid.

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 296 × 296 × 72 cells and the common port/source normalization machinery. The shared energy-decay cutoff stopped the run after 15,077 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

out

0.0077952

0.05

0.0077952

0.05

PASS

total

0.00851615

0.05

0.00851615

0.05

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_euler_bend

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

Return to the example atlas