The simulation region object defines the region that is included in the simulation. Only one simulation region is supported in a simulation.
Note: Objects which lie outside the simulation region.
Any simulation objects contained or partly contained within the simulation region are included in the simulation, while any objects which fall completely outside of the simulation region are not included in the simulation. Those physical structures (and portions thereof) lying within the simulation region are included in the simulation (i.e. the simulation is performed on that portion of the physical structure lying within the simulation region). Physical monitors and sources are treated in a similar fashion, such that any portion of a monitor or source lying within a simulation region will be used. The user is warned when at least one source or monitor falls completely outside the simulation region.
General tab
The simulation region contains several settings:
- DIMENSION: This drop down menu gives the choice of a 2D simulation plane or a 3D simulation.
- X, Y, Z MIN/MAX BOUNDARY
- OPEN: The boundary is defined by the structure shape. When selected, it extends the boundary to the surface of the outer structure.
- CLOSED: The boundary is defined by the simulation region geometry. If all boundaries are closed, the simulation region is a square in 2D, and a cube in 3D.
- SHELL: This boundary is for PML.
- X,Y,Z MIN/MAX SHELL THICKNESS (UM): The PML thickness. It can vary from simulation to simulation, users may consider using the thickness equivalent to the half of mid-wavelength to start with, if there is a wavelength range.
Material tab
BACKGROUND MATERIAL: Choose the background material for the simulation region. This option is not available when one boundary is open.
Geometry tab
- X, Y, Z: The center position of the simulation region
- X MIN, X MAX: X min, X max position
- Y MIN, Y MAX: Y min, Y max position
- Z MIN, Z MAX: Z min, Z max position
- X SPAN, Y SPAN, Z SPAN: X, Y, Z span of the simulation region
Note:The availability is based on the SOLVER TYPE |