Nanobeam cavity — resonant wavelength and Q

Nanobeam cavity — resonant wavelength and Q#

validated · 2026-08-28

forwardresolution 1devicereal_worldcavityresonancequality_factortidy3d_goldenofficial_notebook

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

Nanobeam cavity: resonant wavelength and quality factor

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

What is exercised#

The official cubic lattice/radius taper is retained with four constant mirror cells per side and eight tapered cells total. A broadband Ey dipole excites the cavity, a time-domain point monitor records its 3 ps ringdown, and the same local pole extractor analyzes Tidy3D and FDTDX signals.

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 180 × 86 × 160 cells and the common port/source normalization machinery. 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

wavelength_um

1.56871

1.58801

0.0193015

0.02294

PASS

Q

3.513e+04

2.998e+04

5145.42

1.149e+04

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_nanobeam_cavity

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

Return to the example atlas