Open
Description
Current
We have the following issues with 1D Mode simulations:
- We need a two-dimensional mode plane to pass validation. In GUI, it seems a bit weird to create a 2D mode plane for a 1D mode simulation domain.
- There are validation errors related to using default boundary settings (PML) in zero-dimensional simulation domain (FDTD) directions. While for Python users, that is only a minor inconvenience, since they are setting a Mode simulation and concerned about mode plane boundary conditions, in the GUI, that is critical because we don't have FDTD boundary settings in the Mode workbench.
Requirement
- Support a 0-size mode plane on directions with a simulation domain size of 0 in Mode simulations.
- Avoid validation errors related to using PML in zero-dimensional simulation domain directions in Mode simulations. Potential solution: Use periodic boundary conditions automatically for 0-size dimensions, regardless of the user’s boundary condition settings, and provide a warning/info message in the solver log in Mode simulations.