Changes

EM.Tempo

30,876 bytes removed, 14:07, 7 August 2019
[[Image:Splash-fdtd.jpg|right|720px]]<strong><font color="#961717" size="4">Fast Multicore & GPU-Accelerated FDTD Solvers for Simulating the Most Complex Electromagnetic Modeling Problems</font></strong><table><tr><td>[[image:Cube-icon.png | link=Getting_Started_with_EM.Cube]] [[image:cad-ico.png | link=Building_Geometrical_Constructions_in_CubeCAD]] [[image:prop-ico.png | link=An EM.Terrano]] [[image:static-ico.png | link=EM.Ferma]] [[image:planar-ico.png | link=EM.Picasso]] [[image:metal-ico.png | link=EM.Libera]] [[image:po-ico.png | link=EM.Illumina]]</td><tr></table>[[Image:Tutorial_icon.png|30px]] '''[[EM.Cube#EM.Tempo_Documentation | EM.Tempo Primer Tutorial Gateway]]''' [[Image:Back_icon.png|30px]] '''[[EM.Cube | Back to EM.Cube Main Page]]'''==Product Overview==
=== EM.Tempo in a Nutshell ===
EM.Tempo is a powerful time-domain electromagnetic simulator for full-wave modeling of 3D radiation, scattering and propagation problems. It features a highly efficient Finite Difference Time Domain (FDTD) simulation engine that has been optimized for speed and memory usage. EM.Tempo brings to your desktop the ultimate in computational power. Its FDTD solver has been parallelized to take full advantage of multi-core processor architectures. With a large variety of geometrical, material and excitation features including open-boundary and periodic structures, you can use EM.Tempo as a general purpose 3D field simulator for most of your electromagnetic modeling needs. EM.Tempo's new advanced simulation capabilities are your the key to a thorough understanding of wave the interaction in of electromagnetic waves with complex media such as anisotropic composites, metamaterials or biological environmentsor with passive and active devices and nonlinear circuits.
=== Pros and Cons EM.Tempo has undergone several evolutionary development cycles since its inception in 2004. The original simulation engine utilized an FDTD formulation based on the uniaxial perfectly matched layer (UPML) boundary termination. Subsequently, a more advanced boundary termination based on the convolutional perfectly matched layer (CPML) was implemented with a far superior performance for all oblique wave incidences in different types of media. EM.Tempo now has the ability to model laterally infinite layered structures using CPML walls that touch material media. A novel formulation of periodic boundary conditions was implemented based on the constant transverse wavenumber method (or direct spectral FDTD Simulation ===). In 2013 we introduced an Open-MP optimized multi-core version of the FDTD engine as well as a hardware-accelerated solver that runs on CUDA-enabled graphical processing unit (GPU) platforms. Both of these fast solvers are now a standard part of the EM.Tempo Pro package.
A time domain simulation like FDTD offers several advantages over a frequency domain simulation[[Image:Info_icon. In certain applications, the time domain signature or behavior png|30px]] Click here for an overview of a system, e.g. the transient response '''[[Basic Principles of a circuit or an antenna, is sought. In other applications, you may need to determine the wideband frequency response of a system. In such cases, using a frequency domain technique, you have to run the simulation engine many times to adequately sample the specified frequency range. In contrast, using the FDTD method requires a single-run simulation. The temporal field data are transformed into the Fourier domain to obtain the wideband frequency response of the simulated system. Among other advantages of the Finite Difference Time Domain Method | Basic FDTD method are its versatility in handling complex material compositions as well as its superb numerical stability. It is worth noting that unlike frequency domain methods like the finite element method (FEM) or method of moments (MoM), the FDTD technique does not involve numerical solution of large ill-conditioned matrix equations that are often very sensitive to the mesh qualityTheory]]'''.
Like every numerical technique, the FDTD method has disadvantages, too<table><tr><td>[[Image:ART GOLF Fig title. Adding the fourth dimension, time, to the computations increases the size of the numerical problem significantly. Unfortunately, this translates to both larger memory usage and longer computation times. Note that the png|thumb|left|400px| The 3D far-field data are generated in both the 3D space and time. EM.Tempo uses a staircase "Yee" mesh to discretize the physical structure. This works perfectly fine for rectangular objects that are oriented along the three principal axes. In the case radiation pattern of highly curved structures or slanted surfaces and lines, however, this may compromise the geometrical fidelity of your structure. EM.Tempo provides a default adaptive FDTD mesher that can capture the fine details of geometric contours, slanted thin layers, surfaces, etc. to arbitrary precision. However, with smaller mesh cells, the stability criterion leads to smaller time steps; hence, longer computation times. Another disadvantage of the FDTD technique compared to naturally openvehicle-boundary methods like MoM is its finite-extent computational domain. This means that to model open boundary problems like radiation or scattering, absorbing boundary conditions are needed to dissipate the incident waves at the walls of the computational domain and prevent them from reflecting back into the domain. The accuracy of the FDTD simulation results depends on the quality of these absorbers and their distance from the actual physical mounted antenna structure. simulated by EM.Tempo provides high quality perfectly match layer (PML) terminations at the boundaries which can be placed fairly close your physical structure.]]</td></tr></table>
=== An Overview of EM.Tempo as the FDTD Modeling Module of EM.Cube ===
EM.Tempo is a general-purpose EM simulator than can solve most types of electromagnetic modeling problems involving arbitrary geometries and complex material variations in both time and frequency domains. It has also been integrated within the [[Image:FDTD93.png|thumb|300px|A metal ellipsoid object..EM.Cube]][[Image:FDTD94simulation environment as its full-wave "FDTD Module".png|thumb|300px|EM...and its Yee mesh.]]In Tempo shares the Finite Difference Time Domain (FDTD) methodvisual interface, a discretized form of Maxwell’s equations is solved numerically and simultaneously in both the 3D space and time. During this processparametric CAD modeler, data visualization tools, the electric and magnetic fields are computed everywhere in the computational domain many more utilities and features collectively known as a function [[Building Geometrical Constructions in CubeCAD | CubeCAD]] with all of time starting at t = 0. From knowledge of the primary fields in space and time, one can compute other secondary quantities including frequency domain characteristics like scattering [[parametersEM.Cube]], input impedance, far field radiation patterns, radar cross section, etc's other computational modules.
[[Image:Info_icon.png|30px]] Click here to learn more about the '''[[Differential Form of Maxwell's EquationsGetting_Started_with_EM.Cube | EM.Cube Modeling Environment]]'''.
Since FDTD is a finite domain numerical technique, the computational domain === The Advantages & Limitations of the problem must be truncatedEM. At the boundaries of the computational domain, proper boundary conditions must be enforced. In a shielded structure, all objects are enclosed within a perfect electric (or magnetic) conductor box. In an open boundary problem like an antenna, some kind of absorbing boundary conditions such as a perfectly matched layer (PML) must be used to emulate the free space. The absorbing boundaries should act such that the field propagates through them without any back reflection. The Tempo's FDTD simulation time depends directly on the size of the computational domain and on how close you can place the PML walls to the enclosed objects. Simulator ===
Click here A time domain simulation like FDTD offers several advantages over frequency domain simulations. In certain applications, the time domain signature or behavior of a system, e.g. the transient response of a circuit or an antenna, is sought. In other applications, you may need to learn more about EMdetermine the wideband frequency response of a system.Tempo's [[Perfectly Matched Layer Termination]]In such cases, using a frequency domain technique, you have to run the simulation engine many times to adequately sample the specified frequency range. In contrast, using the FDTD method requires a single-run simulation. The temporal field data are transformed into the Fourier domain to obtain the wideband frequency response of the simulated system. Among other advantages of the FDTD method are its versatility in handling complex material compositions as well as its superb numerical stability. It is worth noting that unlike most frequency domain methods, the FDTD technique does not involve numerical solution of large ill-conditioned matrix equations that are often very sensitive to the mesh quality.
The Like every numerical technique, the FDTD computational domain must be discretized using an appropriate meshing schememethod has disadvantages, too. Adding the fourth dimension, time, to the computations increases the size of the numerical problem significantly. Unfortunately, this translates to both larger memory usage and longer computation times. Note that the field data are generated in both the 3D space and time. EM.Tempo uses a non-uniform, variable, staircase (pixelated) "Yee " mesh with a mesh density that you can customizeto discretize the physical structure. A fixed-cell mesh generator is also available, where you can set constant cell dimensions This works perfectly fine for rectangular objects that are oriented along the three principal axes for the entire computational domain. The variable mesh density is specified in terms In the case of the effective wavelength inside material media. As a resulthighly curved structures or slanted surfaces and lines, however, this may compromise the mesh resolution and average mesh cell size differ in regions that are filled with different types geometrical fidelity of materialyour structure. [[EM.Cube]]'s non-uniform Tempo provides a default adaptive FDTD mesher generates more cells in the areas that are occupied by dielectric materialscan capture the fine details of geometric contours, fewer slanted thin layers, surfaces, etc. to arbitrary precision. However, with smaller mesh cells in , the free space regions and no cells inside (impenetrable) PEC regionsstability criterion leads to smaller time steps; hence, longer computation times. [[Another disadvantage of the FDTD Module]]'s default "adaptive" mesh generator also refines technique compared to naturally open-boundary methods like the mesh around curved segments method of lines, surface moments (MoM) is its finite-extent computational domain. This means that to model open boundary problems like radiation or solids scattering, absorbing boundary conditions are needed to produce a far more accurate representation dissipate the incident waves at the walls of your geometrythe computational domain and prevent them from reflecting back into the domain. The example accuracy of the FDTD simulation results depends on the right illustrates a metal ellipsoid quality of these absorbers and a 3D view their distance from the actual physical structure. EM.Tempo provides high quality perfectly matched layer (PML) terminations at the boundaries, which can be placed fairly close to your physical structure to reduce the total size of its Yee meshthe computational domain.
The FDTD method provides a wideband simulation of your physical structure. In order to produce sufficient spectral information, an appropriate wideband temporal waveform is needed to excite the physical structure. The choice of the waveform, its bandwidth and time delay all affect the convergence behavior of the FDTD time marching loop. By default, EM.Tempo uses a modulated Gaussian waveform with optimal <table><tr><td>[[parameters]]Image:Airplane Mesh. Another issue of concern is the numerical stability of the time marching scheme. You might expect to get better and more accurate results if you keep increasing the FDTD png|thumb|left|480px|The Yee mesh resolution. However, in order to satisfy the Courant-Friedrichs-Levy (CFL) stability condition, the time step must be inversely proportional to the maximum grid cell size . A high resolution mesh requires a smaller time step. To let the fields in the computational domain fully evolve over time, a smaller time step will require a larger number of time steps to convergean imported aircraft CAD model. [[EM.Cube]] automatically chooses a time step that satisfies the CFL condition.</td></tr></table>
For more detailed information, see [[Waveform, Bandwidth, Stability]]== EM.Tempo Features at a Glance ==
==Building the = Physical StructureDefinition ===
[[Image:FDTD1.png|thumb|200px|[[FDTD Module]]'s Navigation Tree.]]<ul>In [[EM.Cube]]'s [[FDTD Module]] <li> PEC, a physical structure consists PMC and dielectric materials and thin wires</li> <li> Uniaxial and fully anisotropic materials with four complete constitutive tensors</li> <li> Dispersive materials of sets of objects that are grouped together Debye, Drude and identified by their material Lorentz types. All the objects belonging to the same material group share the same color with arbitrary number of poles</li> <li> Generalized uniaxial and same material properties. Materials are divided into seven categories that are listed under the '''Physical Structure''' node at the top doubly negative refractive index metamaterials with arbitrary numbers of the navigation treeboth electric and magnetic poles</li> <li> Two types of gyrotropic materials:ferrites and magnetoplasmas</li> <li> PEC, PMC and convolutional perfectly match layer (CPML) boundary conditions</li> <li> Doubly periodic structures</li></ul>
* [[#Perfect Conductors|Perfect Electric Conductor (PEC) Objects]]* [[#Perfect Conductors|Perfect Magnetic Conductor (PMC) Planes]]* [[#Dielectric Materials|Dielectric Materials]]* [[#Anisotropic Materials|Anisotropic Materials]]* [[#Dispersive Materials|Dispersive Materials]]* Inhomogeneous Materials* Thin Wires=== Sources, Ports & Devices ===
Under each material node<ul> <li> Lumped voltage sources with internal resistance placed on a PEC line or thin wire object with an arbitrary orientation</li> <li> Distributed sources with uniform, you can create new material groups of sinusoidal and edge-singular profiles</li> <li> Microstrip, coplanar Waveguide (CPW) and coaxial ports</li> <li> Waveguide sources with the same typedominant TE<sub>10</category but sub> modal profile</li> <li> Multi-port and coupled port definitions</li> <li> Two types of filamentary current sources: Hertzian short dipole radiators with different properties (color, texturearbitrary orientation and long wire current sources aligned along one of the principal axes with a uniform, triangular or electric sinusoidal current distribution profile</li> <li> Plane wave excitation with linear and magnetic constitutive circular polarizations</li> <li> Multi-ray excitation capability (ray data imported from [[parametersEM.Terrano]]). These material groups are used to organize the CAD objects you draw in the project workspace or import from external model files. When you create a new geometrical object such as a Box or a Sphere, it is inserted under the currently active material type. There is only one material group that is active at any time. It is recommended that you first create material groups)</li> <li> Gaussian beam excitation</li> <li> Huygens sources</li> <li> Source arrays with weight distribution &amp; phase progression</li> <li> Periodic sources with user defined beam scan angles</li> <li> Standard excitation waveforms (Gaussian pulse, modulated Gaussian and then draw new objects as part of the active material group. Howeversinusoidal) for optimal frequency&nbsp;domain computations&nbsp;</li> <li> Arbitrary user-defined temporal excitation waveforms using mathematical expressions and Python functions</li> <li> Passive lumped devices: R, if you start a new EM.Tempo project from scratchL, and start drawing a new object without having previously defined any material groupsC, a new default PEC group is created series RL and added to parallel RC and nonlinear diode device</li> <li> Active lumped one-port and two-port devices placed on PEC lines aligned along one of the navigation tree to hold your new CAD object.principal axes with arbitrary Netlist definitions</li> <li> Active distributed one-port and two-port devices placed under microstrip lines with arbitrary Netlist definitions</li></ul>
===Defining Material TypesMesh Generation ===
To define a new material group<ul> <li> Fast generation of Yee grid mesh of solids, follow these steps:surfaces and curves</li> <li> Geometry-aware and material-aware adaptive mesh generator with gradual grid transitions</li> <li> Fixed-cell uniform mesh generator with three unequal cell dimensions</li> <li> Mesh view with three principal grid profilers</li> <li> Manual control of mesh parameters and fixed grid points</li></ul>
* Right click on the name of the desired material in the navigation tree and select '''Insert New Material...''' from the contextual menu. A material dialog opens up.* Specify a '''Label''' and '''Color''' (and optional Texture) for the material group being created.* Either accept the default values of the available material [[parameters]] or enter new values.* Click the '''OK''' button of the dialog to accept the changes and close it.=== 3D FDTD Simulation ===
Once <ul> <li> Wideband full-wave simulation of 3D structures</li> <li> Transient analysis with arbitrary user defined excitation waveforms</li> <li> Multi-frequency computation of frequency domain quantities in a new material node has been created single FDTD simulation run</li> <li> OpenMP-parallelized multi-core and multi-thread FDTD simulation engine</li> <li> GPU-accelerated FDTD simulation engine based on NVIDIA CUDA platforms</li> <li> Total-field-scattered-field analysis of plane wave and Gaussian beam excitation</li> <li> Full-wave analysis of periodic structures with arbitrary plane wave incidence angles using the navigation tree, it becomes the "Active" Direct Spectral FDTD method</li> <li> Infinite material group half-space Green&#39;s functions for calculation of the project workspace, which is always listed far fields in bold letters. Then you can start drawing new objects under that node. Any material can be made active by right clicking presence of a lossy ground</li> <li> Accelerated computation of S-parameters of resonant structures based on its name in the Navigation Tree and selecting the Prony'''Activate''' item s method of the contextual menu.exponential interpolation</li> <li> Parametric sweeps of variable object properties or source parameters including frequency and angular sweeps</li> <li> Multi-variable and multi-goal optimization of structures</li> <li> Automated generation of compact reduced order surrogate models from full-wave simulation data</li></ul>
===Moving Objects among Material GroupsData Generation &amp; Visualization ===
[[Image:FDTD21<ul> <li> Near-field intensity (1colorgrid).png|thumb|325px|Moving objects from one FDTD material group to another.]], contour and surface plots (vectorial - amplitude &amp; phase)</li>You can move one or more selected objects at a time among different material groups. The objects can be selected either <li> Near-field probes for monitoring field components in the project workspace, or their names can be selected from the navigation tree. Right click on the highlighted selection both time &amp; frequency domains</li> <li> Far-field radiation patterns: 3D pattern visualization and select '''Move To 2D polar and Cartesian graphs</li> FDTD <li>''' from the contextual menu. This opens up another sub Far-menu with a list field characteristics such as directivity, beam width, axial ratio, side lobe levels and null parameters, etc.</li> <li> Radiation pattern of arbitrary array configurations of all the available material groups already defined FDTD structure or periodic unit cell</li> <li> Bistatic and monostatic radar cross section</li> <li> Huygens surface data generation for use in your other [[EM.Tempo project. Select the desired material nodeCube]] modules</li> <li> Periodic reflection/transmission coefficients and k-&beta; diagrams</li> <li> Port characteristics: S/Y/Z parameters, VSWR and all the selected objects will move Smith chart</li> <li> Time and frequency domain port voltages, currents and powers</li> <li> Touchstone-style S-parameter text files for direct export to that material group[[RF. In the case Spice A/D]]</li> <li> Interanl node voltages and currents of a multiple selection from the navigation tree using the keyboard's '''Shift Key''' or '''Ctrl Key'''Netlist-based one-port and two-port networks</li> <li> Computation of electric, make sure that you continue to hold the keyboard's '''Shift Key''' magnetic and total energy densities, dissipated power density (Ohmic loss), specific absorption rate (SAR) density and complex Poynting vector on field sensor planes</li> <li> Animation of temporal evolution of fields</li> <li> Custom output parameters defined as mathematical expressions or '''Ctrl Key''' down while selecting the destination material group's name from the contextual menu.Python functions of standard outputs</li></ul>
In a similar way, you can move one or more objects from an FDTD material group to one of [[EM.Cube]]'s other modules. In this case, == Building the sub-[[menus]] of the '''Move To >''' item of the contextual menu will indicate all the [[EM.Cube]] modules that have valid groups for transfer of the selected objects. You can also move one or more objects from [[EM.Cube]]'s other modules to a material group Physical Structure in EM.Tempo. ==
{{Note|You can import external objects only to '''[[CubeCAD]]'''. You need to move the imported objects form [[CubeCAD]] to === Material Variety in EM.Tempo as described above.}}===
===Perfect Conductors===Your physical structure in EM.Tempo offers two types can be made up of perfect conductorsseveral geometric objects with different material compositions. In other words, the geometric objects you draw or import from external files are grouped together based on a common material composition. EM.Tempo's material types are divided into seven categories:
{| class="wikitable"|-! scope="col"| Icon! scope="col"| Material Type! scope="col"| Applications! scope="col"| Geometric Object Types Allowed|-| style="width:30px;" | [[File:pec_group_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types# '''Perfect Electric Conductor (PEC) Objects:''' The tangential electric field on the surface of this type of perfect conductor is zero. The electric and magnetic fields are assumed to vanish inside the volume of a PEC object. A PEC material is characterized by an infinite electric conductivity |Perfect Electric Conductor (&sigmaPEC)]]| style="width:300px; " | Modeling perfect metals| style= &infin"width:250px;). You can draw solid" | Solid, surface and curve objects|-| style="width:30px;" | [[Curve ObjectsFile:thin_group_icon.png]]|curve objectsstyle="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Thin Wire |Thin Wire]] as part | style="width:300px;" | Modeling wire radiators| style="width:250px;" | Lines parallel to one of a PEC groupthe three principal axes|-| style="width:30px;" | [[File:pmc_group_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types# '''Perfect Magnetic Conductor (PMC) Planes|Perfect Magnetic Conductor (PMC)]]| style="width:''' The tangential magnetic field on the surface of this type of 300px;" | Modeling perfect conductor is zero. The electric and magnetic fields are assumed sheets | style="width:250px;" | Rectangle strips parallel to vanish inside the volume one of a PMC objectthe three principal planes|-| style="width:30px;" | [[File:diel_group_icon. A PMC png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Dielectric Material |Dielectric Material]]| style="width:300px;" | Modeling any homogeneous material is characterized by an infinite magnetic conductivity (&sigma| style="width:250px;<sub>m</sub> " | Solid objects|-| style= &infin"width:30px;)" | [[File:aniso_group_icon. EMpng]]| style="width:150px;" | [[Glossary_of_EM.Tempo currently allows only PMC plates (rectangle strips Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Anisotropic Material |Anisotropic Material]]| style="width:300px;" | Modeling unaxial or generalized anisotriopic materials| style="width:250px;" | Solid objects) parallel to one |-| style="width:30px;" | [[File:disp_group_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Dispersive Material |Dispersive Material]]| style="width:300px;" | Modeling Debye, Drude and Lorentz materials and generalized metamaterials | style="width:250px;" | Solid objects|-| style="width:30px;" | [[File:voxel_group_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Gyrotropic_Material |Gyrotropic Material]]| style="width:300px;" | Modeling ferrites and magnetoplasmas| style="width:250px;" | Solid objects|-| style="width:30px;" | [[File:Virt_group_icon.png]]| style="width:150px;" | [[Glossary of the three principal axesEM.Cube's Materials, Sources, Devices & Other Physical Object Types#Virtual_Object_Group | Virtual Object]]| style="width:300px;" | Used for representing non-physical items | style="width:250px;" | All types of objects|}
PEC and PMC materials do not have any constitutive material properties that you can modify except for their color or textureClick on each category to learn more details about it in the [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types]].
===Dielectric MaterialsOrganizing the Physical Structure by Material Groups ===[[Image:FDTD5.png|thumb|450px|[[EM.Cube]]'s material list]]In [[EM.Tempo]], a dielectric material represents a general isotropic, homogeneous material with both electric and magnetic properties. The constitutive [[parameters]] of a dielectric material include permittivity (&epsilon;), permeability (&mu;), electric conductivity (&sigma;) and magnetic conductivity (&sigma;<sub>m</sub>):
:<math> \mathbf{D} = \epsilon \mathbf{E}EM.Tempo groups your geometric objects in the project workspace based on their material type. All the objects belonging to the same material group share the same color and same material properties. Under each material node in the navigation tree, \quad \quad \mathbf{J} = \sigma \mathbf{E} </math>you can create new material groups of the same type but with different properties such as color, texture, or electric and magnetic constitutive parameters.
:<math> \mathbf{B} = \epsilon \mathbf{H}Once a new material node has been created on the navigation tree, \quad \quad \mathbf{M} = \sigma_m \mathbf{H} </math>it becomes the "Active" material group of the project workspace, which is always listed in bold letters. When you draw a new geometric object such as a box or a sphere, its name is added under the currently active material type. There is only one material group that is active at any time. Any material can be made active by right clicking on its name in the navigation tree and selecting the '''Activate''' item of the contextual menu. It is recommended that you first create material groups, and then draw new objects under the active material group. However, if you start a new EM.Tempo project from scratch, and start drawing a new object without having previously defined any material groups, a new default PEC group is created and added to the navigation tree to hold your new object.
where '''E''' and '''H''' are the electric and magnetic fields, respectively, '''D''' is the electric flux density, also known as the electric displacement vector, '''B''' is the magnetic flux density, also known as the magnetic induction vector, and '''J '''and '''M '''are the electric and magnetic current densities, respectively{{Note|You can import external objects only to CubeCAD. For example, an imperfect metal You can be represented by a dielectric material that has a large, finite, electric conductivitythen move the imported objects form CubeCAD to EM. PEC and PMC, therefore, are the limiting cases of an isotropic dielectric material when &sigma; &rarr; &infin; or &sigma;<sub>m</sub> &rarr; &infin;, respectivelyTempo.}}
You may also choose from [[EMImage:Info_icon.Cubepng|30px]]'s list of preloaded material types. Click here to access the button labeled '''Material''' to open [[Glossary of EM.Cube]]'s Material List dialog. Select the desired material from the list or type the first letter of a material to find it. For exampleMaterials, typing Sources, Devices & Other Physical Object Types]]'''V''' selects '''Vacuum '''in the list. Once you close the dialog by clicking '''OK''', the selected material properties fill the parameter fields automatically.
=== Anisotropic Materials ===<table><tr><td> [[Image:Tempo NavTree.png|thumb|left|400px|EM.Tempo's navigation tree.]]</td></tr></table>
[[=== Material Hierarchy in EM.Tempo]] allows you to define a general anisotropic material, whose constitutive [[parameters]], i.e. permittivity ('''&epsilon;'''), permeability ('''&mu;'''), electrical conductivity ('''&sigma;''') and magnetic conductivity ('''&sigma;<sub>m</sub>'''), are all tensorial in nature. Each constitutive parameter in this case is represented by a 3×3 matrix:===
[[File:FDTD16EM.png|500pxTempo]]allows overlapping objects although it is generally recommended that object overlaps be avoided in favor of clearly defined geometries and object boundaries. If two or more objects of the same material type and group overlap, they are merged using the Boolean union operation during the mesh generation process. If two overlapping objects belong to two different material categories, then the material properties of the FDTD cells in the overlap region will follow the [[EM.Tempo]]'s material hierarchy rule. In that case, the overlap area cells will always be regarded as having the material type of the higher priority. According to this rule, the material types are ordered from the highest priority to the lowest in the following manner:
A "'''# PEC# PMC# Dispersive# Gyrotropic# General Anisotropic# Uniaxial'''" material is a special case of an anisotropic material whose constitutive [[parameters]] are all diagonal matrices. Specifying an anisotropic material as <u>'''Uniaxial'''</u> in the [[FDTD Module]] has a very important computational implication. There are six field update equations for uniaxial materials at each time steps: three for the electric field and three for the magnetic field. In this respect, a uniaxial material is similar to an isotropic dielectric material. On the other hand, a fully anisotropic material with non-zero off-diagonal constitutive matrix elements requires twelve update equations at each time step: three equations for the three components of each of the four vector fields '''E''', '''D''', '''H''' and '''B'''. As a result, the time loop for fully anisotropic materials takes much longer time than uniaxial materials.Anisotropic# Dielectric
===Dispersive Materials===If planned carefully, taking advantage of [[EM.Tempo]]'s material hierarchy rule would make the construction of complex objects easier. For example, a dielectric coated metallic cylinder can be modeled by two concentric cylinders: an inner PEC of smaller radius and an outer dielectric of larger radius as shown in the illustration below. The portion of the dielectric cylinder that overlaps the inner PEC cylinder is ignored by the FDTD engine because the PEC cylinder takes precedence over the dielectric in the material hierarchy. Alternatively, you can model the same structure by an inner solid PEC cylinder enclosed by an outer hollow pipe-shaped dielectric cylinder.
<table><tr><td> [[FileImage:FDTD7FDTD_MAN2.png|thumb|250pxleft|Debye Add Pole Dialog]][[#Perfect Conductors|PEC]], [[#Perfect Conductors|PMC]], [[#Dielectric Materials360px|The geometric construction of a dielectric]] and [[#Anisotropic Materials|anisotropic]] materials are non-dispersive. In other words, their constitutive [[parameters]] do not vary coated metallic cylinder with frequencya conformal foil. Most of the materials used in the design of RF and microwave circuits, antennas and systems fall into this frequency-independent category. However, there are other types of materials whose constitutive [[parameters]] exhibit frequency-dependent behaviors. [[EM.Cube]]'s [[FDTD Module]] currently offers four types of dispersive material:</td></tr></table>
# Debye === Moving Objects Among Different Material# Drude Material (Unmagnetized Plasma)# Lorentz Material# Left-handed Metamaterial Groups or EM.Cube Modules ===
The FDTD simulation engine uses the Auxiliary Differential Equation (ADE) method You can move any geometric object or a selection of objects from one material group to model dispersive materialsanother. You can also transfer objects among [[EM.Cube]] allows 's different modules. For example, you often need to define an arbitrary number of poles for each of the above dispersive material typesmove imported CAD models from CubeCAD to [[EM. Keep Tempo]]. To transfer objects, first select them in mind that all the objects belonging to project workspace or select their names in the same dispersive navigation tree. Then right-click on them and select <b>Move To &rarr; Module Name &rarr; Object Group</b> from the contextual menu. For example, if you want to move a selected object to a material group called "Dielectric_1" in [[EM.Tempo]], then you have to select the same dispersion propertiesmenu item '''Move To &rarr; [[EM.Tempo]] &rarr; Dielectric_1''' as shown in the figure below. Note that you can transfer several objects altogether using the keyboards's {{key|Ctrl}} or {{key|Shift}} keys to make multiple selections.
The complex permittivity of a Debye material with N poles is given by<table><tr><td>[[Image:Tempo_L11_Fig2.png|thumb|left|720px|Moving an imported object from CubeCAD to EM.Tempo.]]</td></tr></table>
:<math> \varepsilon (\omega) = \varepsilon_\infty + \sum_{p=1}^N \dfrac{\Delta \varepsilon_p}{1 + j\omega \tau_p}, \quad \Delta \varepsilon_p = \varepsilon_{sp} - \varepsilon_\infty </math><!--[[Image:FDTD18(2).png]]--> where <math>\varepsilon_{\infty}</math> is the value of the permittivity at infinite frequency, <math>\tau_p</math> is the relaxation time corresponding to the p''th'' pole having the unit of seconds, and <math>\varepsilon_{sp}</math> is the value of the static permittivity (at DC) corresponding to the p''th'' pole. <math>\Delta \varepsilon_p = \varepsilon_{sp} - \varepsilon_{\infty}</math> represents the change in permittivity due to the p''th'' pole. Unmagnetized plasmas are typically modeled as Drude materials. The complex permittivity of a Drude material with N poles is given by: :<math> \varepsilon(\omega) = \varepsilon_{\infty} - \sum_{p=1}^N \dfrac{{\omega_p}^2}{\omega^2 - j\omega \nu_p} </math><!--[[Image:FDTD19(1).png]]--> where <math>\omega_p</math> and <math>\nu_p</math> are the angular plasma frequency and angular collision frequency corresponding to the p''th'' pole, respectively, and both are expressed in rad/s. For an unmagnetized plasma, <math>\varepsilon_{\infty} = 1</math>. The complex permittivity of a Lorentz material with N poles is given by: :<math> \varepsilon(\omega) = \varepsilon_{\infty} - \sum_{p=1}^N \dfrac{\Delta \varepsilon_p {\omega_p}^2}{\omega^2 - 2j\omega \delta_p - {\omega_p}^2}, \quad \Delta \varepsilon_p = \varepsilon_{sp} - \varepsilon_{\infty} </math><!--[[Image:FDTD20.png]]--> where <math>\omega _p</math> and <math>\delta_p</math> are the angular resonant frequency and angular damping frequency corresponding to the p''th'' pole, respectively, and both are expressed in rad/s. Similar to a Debye material, <math>\Delta \varepsilon_p = \varepsilon_{sp} - \varepsilon_{\infty}</math> represents the change in permittivity due to the p''th'' pole. {| border="0"|-| valign="top"|[[Image:FDTD2.png|thumb|250px|EM.Tempo's PEC Dialog]]| valign="top"|[[Image:FDTD3.png|thumb|250px|EM.Tempo's PMC Dialog]]| valign="top"|[[Image:FDTD4.png|thumb|250px|Dielectric Material dialog]]| valign="top"|[[Image:FDTD6.png|thumb|250px|[[FDTD Module]]'s Anisotropic Material dialog]]| valign="top"|[[Image:FDTD8.png|thumb|250px|Debye Material Dialog]]|-|} ===Geometrical Rules & Material Hierarchy=== [[Image:fdtd14_tn.png|thumb|400px|Geometric construction of a dielectric-coated metallic cylinder.]]The following rules apply to the definition of materials and objects in [[EM.Tempo]]: * Under the [[#Perfect Conductors|PEC]] category, you can define all types of solid, and surface and [[Curve Objects|curve objects]].* Under the [[#Perfect Conductors|PMC]] category, you can define only define rectangle strip objects parallel to the principal planes. * Under the [[#Dielectric Materials|Dielectric]], [[#Anisotropic Materials|Anisotropic]] and [[#Dispersive Materials|Dispersive]] material categories, you can define only [[Solid Objects|solid objects]].* Under the Inhomogeneous Material category, you can only import a Cartesian ".CAR" data file.* Under the Thin Wire category, you can only define line objects parallel to the principal axes.  [[EM.Tempo]] allows overlapping objects, although it is generally recommended that object overlaps be avoided in favor of clearly defined geometries and object boundaries. If two or more objects of the same material type and group overlap, they are merged using the Boolean union operation during the mesh generation process. If two overlapping objects belong to two different material categories, then the material properties of the FDTD cells in the overlap region will follow the EM.Tempo's material hierarchy rule. In that case, the overlap area cells will always be regarded as having the material type of the higher priority. According to this rule, the material types are ordered from the highest priority to the lowest in the following manner: # [[#Perfect Conductors|PEC]]# [[#Perfect Conductors|PMC]]# [[#Dispersive Materials|Dispersive]]# General [[#Anisotropic Materials|Anisotropic]]# Uniaxial [[#Anisotropic Materials|Anisotropic]]# [[#Dielectric Materials|Dielectric]] If planned carefully, taking advantage of EM.Tempo's material hierarchy rule would make the construction of complex objects easier. For example, a dielectric coated metallic cylinder can be modeled by two concentric cylinders: an inner PEC of smaller radius and an outer dielectric of larger radius as shown in the illustration below. The portion of the dielectric cylinder that overlaps the inner PEC cylinder is ignored by the FDTD engine because the PEC cylinder takes precedence over the dielectric in the material hierarchy. Alternatively, you can model the same structure by an inner solid PEC cylinder enclosed by an outer hollow pipe-shaped dielectric cylinder.   == Setting the Computational Domain & Boundary Conditions==
===The FDTD Solution Domain===
[[Image:FDTD22(1).png|thumb|300px|The computational domain box enclosing a metallic sphere.]]
The FDTD method requires a finite-extent solution domain. This is rather straightforward for shielded structures, where a typical PEC enclosure box defines the computational domain. For open-boundary structures like antennas and scatterers, the computational domain must be truncated using appropriate termination boundary conditions. The objective of termination boundary conditions is to eliminate the reflections from the walls of the domain box back to the computational domain.
In [[EM.Tempo]], you can define two types of domain box. A "'''Default'''" -type domain is a box that is placed at a specified offset distance from the largest extents of your physical structure (global bounding box). The offset is specified in free-space wavelengths. A "'''Custom'''" -type domain, on the other hand, is defined as a fixed-size and fixed-location box in the World Coordinate System (WCS). In this case, you have to specify the coordinates of the lower left front corner (Corner 1) and upper right back corner (Corner 2) of the domain box.
When you start a new project in [[EM.Tempo]], a default-type domain is automatically created with a default offset value set equal to a quarter free-space wavelength (0.25&lambda;<sub>0</sub>). As soon as you draw your first object, a blue domain box shows up in the project workspace and encloses your object. As you add more objects and increase the overall size of your structure, the domain box grows accordingly to encompass your entire physical structure. When you delete objects from the project workspace, the domain box also shrinks accordingly. ===Changing the Domain Settings===
[[Image:FDTD14.png|thumb|300px|[[FDTD Module]]'s Domain Settings dialog.]]
To set the solution domain of your FDTD project, follow these steps:
* Click the '''Domain''' [[Image:domain_icon.png]] button of the '''Simulate ''' Toolbar or select the menu item '''Menu > Simulate > &rarr; Computational Domain > &rarr; Domain Settings...''' or right click on the '''FDTD Domain''' item of the Navigation Tree and select '''Domain Settings...''' from the contextual menu, or use the keyboard shortcut '''Ctrl+A'''. The Domain Settings Dialog opens up, showing the current domain type selection.
* Select one of the two options for '''Domain Type'''<nowiki>: </nowiki>'''Default''' or '''Custom'''.
* If you select the "Default" domain type, the domain box is defined in terms of the offsets along the X, Y and Z directions from the largest extents of your physical structure. Select one of the two options for '''Offset Units: Grid''' and '''Wavelength'''. In the section titled '''"Domain Size"''', enter the amount of domain extension beyond the largest extents of the structure along the ±X, ±Y and ±Z directions. Note that in the case of a default-type domain box, the offset values based on your current project settings (frequency and units).
By default, the domain box is shown as a wireframe box with blue lines. You can change the color of the domain box or hide it.
===[[Image:Info_icon.png|30px]] Click here to learn more about '''[[Glossary_of_EM.Cube%27s_Simulation-Related_Operations#Domain_Settings | Domain Boundary Conditions===Settings]]'''.
<table><tr><td> [[Image:FDTD13FDTD14.png|thumb|300pxleft|[[FDTD Module]]480px|EM.Tempo's Boundary Conditions domain settings dialog.]]</td></tr></table>
EM.Tempo supports four types of domain boundary conditions:===Settings the Domain Boundary Conditions===
* [[EM.Tempo]] supports four types of domain boundary conditions: PEC* , PMC* , Convolutional Perfectly Matched Layers (CPML)* and Periodic Boundary Conditions (PBC) . By default, all the six sides of the computational domain box are set to CPML, representing a completely open-boundary structure. Different boundary conditions can be assigned to each of the six walls of the domain box. The periodic boundary conditions are special ones that are assigned through [[EM.Tempo]]'s Periodicity Dialog and will be discussed later under modeling of periodic structures. The current release of [[EM.Cube]] allows periodic boundary conditions only on the side walls of the computational domain, and not on the top or bottom walls.
To define the boundary conditions of the solution domain, follow these steps:
* Select the menu item '''Menu > Simulate > &rarr; Computational Domain > &rarr; Boundary Conditions''' or right click on the '''Boundary Conditions''' item in the '''Computational Domain''' section of the Navigation Tree and select '''Boundary Conditions...''' from the contextual menu. The Boundary Conditions Dialog opens.
* You need to assign the type of boundary condition on each of the six domain boundaries: ±X, ±Y and ±Z. For each face, choose one of the three options available: '''PEC''', '''PMC '''or '''PML'''.
The PEC and PMC boundary conditions are the most straightforward to set up and use. Assigning the PEC boundary to one of the bounding walls of the solution domain simply forces the tangential component of the electric field to vanish at all points along that wall. Similarly, assigning the PMC boundary to one of the bounding walls of the solution domain forces the tangential component of the magnetic field to vanish at all points along that wall. For planar structures with a conductor-backed substrate, you can use the PEC boundary condition to designate the bottom of the substrate (the -Z Domain Wall) as a PEC ground. For shielded waveguide structures, you can designate all the lateral walls as PEC. Similarly to model shielded cavity resonators, you designate all the six walls as PEC.
In many electromagnetic modeling problems you need a boundary condition that simply absorbs all the incoming radiation. For problems of this nature, an absorbing boundary condition (ABC) is often chosen that effectively minimizes wave reflections at the boundary<table><tr><td> [[Image:FDTD13. png|thumb|left|480px|EM.Tempo uses Convolutional Perfectly Matched Layers (CPML) for absorbing 's boundary conditionsdialog. The boundary CPML cells in the project workspace are transparent to the user. But, in effect, multiple rows of CPML cells are placed on the exterior side of each face of the visible domain box.]]</td></tr></table>
Click here to learn more about the theory of [[Perfectly Matched Layer Termination]].=== Advanced CPML Setup ===
Click here to learn more about In open-boundary electromagnetic modeling problems, you need a boundary condition that simply absorbs all the incoming radiation. For problems of this nature, an absorbing boundary condition (ABC) is often chosen that effectively minimizes wave reflections at the boundary. [[Advanced CPML SetupEM.Tempo]]uses Convolutional Perfectly Matched Layers (CPML) for absorbing boundary conditions. Usually two or more ABC layers must be placed at the boundaries of the physical structure to maximize wave absorption. The boundary CPML cells in the project workspace are not visible to the user. But, in effect, multiple rows of CPML cells are placed on the exterior side of each face of the visible domain box.
You can also use EM.Tempo to model planar structures set the number of infinite extentsCPML layers as well as their order. To model a laterally infinite dielectric substrateThis is done through the CPML Settings Dialog, you must assign a PML boundary condition to which can be accessed by right clicking on the '''CPML''' item in the four lateral sides '''Computational Domain''' section of the domain box navigation tree and set selecting '''CPML Settings...''' from the lateral domain offset values along the ±X and ±Y directions all equal to zerocontextual menu. If By default, eight CPML layers of the planar structure ends in an infinite dielectric half-space from third order are placed outside the bottom, FDTD problem domain. It is recommended that you must assign always try a PML boundary condition four-layer CPML first to assess the bottom side computational efficiency. The number of the domain box and set the CPML layers may be increased if a very low reflection is required (<-Z offset equal to zero40dB).
{{Note|[[EM.Tempo]]'s default quarter wavelength offset for the domain box and its 8-layer CPML walls are very conservative choices and can be relaxed in many cases. An offset equal to eight free-space grid cells beyond the largest bounding box usually gives a more compact, but still valid, domain box.}}
== Generating [[Image:Info_icon.png|30px]] Click here to learn more about the FDTD Mesh ==theory of '''[[Basic_Principles_of_The_Finite_Difference_Time_Domain_Method#CPML_vs._PML | Perfectly Matched Layer Termination]]'''.
== The <table><tr><td> [[Image:FDTD Mesh Types ==MAN10.png|thumb|left|360px|The boundary CPML cells placed outside the visible domain box.]] </td><td> [[Image:FDTD15.png|thumb|left|400px|CPML Settings dialog.]] </td></tr></table>
[[EM.Tempo]]'s FDTD mesh is a rectangular Yee mesh that extends === Using CPML to the entire computational domain. It is primarily constructed from three mesh grid profiles along the XY, YZ and ZX principal planes. These projections together create a 3D rectangular (voxel) mesh space. You have the option to choose one Model Structures of the three FDTD mesh types:Infinite Extents ===
* Adaptive Mesh* Regular Mesh* FixedYou can use EM.Tempo to model planar structures of infinite extents. A planar substrate usually consists of one or more dielectric layers, possibly with a PEC ground plane at its bottom. To model a laterally infinite dielectric substrate, you must assign a PML boundary condition to the four lateral sides of the domain box and set the lateral domain offset values along the ±X and ±Y directions all equal to zero. If the planar structure ends in an infinite dielectric half-Cell Meshspace from the bottom, you must assign a PML boundary condition to the bottom side of the domain box and set the -Z offset equal to zero. This leaves only the +Z offset with a nonzero value.
The default choice is the adaptive mesh, which is When a quite sophisticated mesh. The resolution of the adaptive FDTD mesh is driven by the '''Mesh Density''', expressed in cells per effective wavelength. Since FDTD domain boundary wall is designated as CPML and its has a time-zero domain method and the excitation waveform may have offset, meaning it touches a wideband spectral contentmaterial block, the effective wavelength is calculated based on CPML cells outside the highest frequency of domain wall are reflected back inside the project: f<sub>max</sub> = f<sub>0</sub> + &Delta;f/2, where f<sub>0</sub> is your project's center frequency and &Delta;f (or BW) is its specified bandwidthcomputational domain. In other words, the effective wavelength in number of CPML layers will be twice the free space is &lambda;<sub>0,eff</sub> = c / f<sub>max</sub>, c being the speed of light one specified in the free spaceCPML Settings dialog. The adaptive FDTD mesh, however, produces different grid cell sizes in This will effectively extend the free space regions material block infinitely beyond the boundary wall and inside dielectric regions. The effective wavelength will create an open boundary effect in a dielectric material with relative permittivity e<sub>r</sub> and permeability µ<sub>r</sub> is given by &lambda;<sub>d,eff</sub> = &lambda;<sub>0,eff</sub> / &radic;&epsilon;<sub>r</sub>&mu;<sub>r</sub>the specified direction. Therefore, It goes without saying that only "substrate" objects are supposed to touch the average ratio of the cell size boundary walls in such a dielectric region to the cell size in the free space is 1/&radic;(&epsilon;<sub>r</sub>&mu;<sub>r</sub>)scenario. The adaptive FDTD mesh generator also takes note Because of the geometrical features of rolled-back CPML cells inside the objects domain, it discretizes. This is more visible in the case of curved solids, curves surfaces and curved wires or obliquely oriented planes and lines which need very important to be approximated using a staircase profile. The mesh resolution varies with the slope of the geometrical shapes and tries to capture the curved segments in the best way. Another important feature of the adaptive FDTD mesher is generation of gradual grid transitions between lowmake sure that other finite-density sized parts and high-density mesh regions. For example, this often happens around objects stay clear from the interface between domain walls as well as from the free space and high permittivity dielectric objects. Gradual mesh transitions provide better accuracy especially in the case of highly resonant structuresinvisible "interior" CPML cells.
According to the Courant-Friedrichs-Levy (CFL) stability criterion, the FDTD time step is determined by the smallest cell size in your FDTD mesh. Occasionally, [[FDTD Module]]'s adaptive mesh generator may create extremely tiny grid cells that would result in extremely small time steps. This would then translate into a very long computation time. [[EM.Cube]] offers the "Regular" FDTD mesh generator, which is a simplified version of the adaptive mesh generator. In a regular FDTD mesh, the grid cell sizes stay rather the same in objects of the same material composition. {{Note|The mesh resolution increases in materials current release of higher permittivity and/or permeability based on the effective wavelength in exactly the same way as the adaptive mesh. Finally, [[EM.Cube]]'s FDTD Modules offers a "Uniform" FDTD mesh generator. The uniform mesh consists Tempo does not support full-anisotropic or dispersive or gyrotropic layers of three uniform grids along the XY, YZ and ZX principal planeslaterally infinite extents. In other words, your anisotropic or dispersive or gyrotropic material objects must not touch the grid cell sizes &Delta;x, &Delta;y and &Delta;z are fixed throughout the entire computational CPML domainboundaries. In this case, the uniform mesh generator has to fit your physical structure to the fixed mesh, rather than adapting the mesh to your physical structure. }}
{{Note<table><tr><td> [[Image:FDTD MAN8.png|When choosing thumb|left|360px|The domain box of a mesh type for your patch antenna with a finite-sized substrate and ground.]] </td><td> [[Image:FDTD simulationMAN9.png|thumb|left|360px|The domain box of a laterally infinite patch antenna with zero ±X, keep in mind that adaptive ±Y and regular mesh types are frequency-dependent and their density varies Z domain offsets. Note that the bottom PEC plate can be replaced with a PEC boundary condition at the highest frequency of your specified bandwidth, while the uniform mesh type is always fixed and independent of your project's frequency settings-Z domain wall.}}]] </td></tr></table>
===Viewing the FDTD Mesh=EM.Tempo's Excitation Sources ==
Because a full 3D FDTD mesh is difficult to visualize everywhere === Source Variety in the computational domain, only the discretized objects are displayed in [[EM.Cube]]'s "'''Mesh View'''" mode. In particular, only the outer boundary cells on the surface of [[Solid Objects|solid objects]] are shown. However, you can view the mesh grid planes across the domain. You can even step these planes back and forth inside the domain and view different mesh profiles of your physical structure.Tempo ===
To generate Before you can run an FDTD mesh and view it the project workspacesimulation, follow these stepsyou have to define a source to excite your project’s physical structure. EM.Tempo offers a variety of excitation mechanisms for your physical structure depending on your particular type of modeling problem or application:
* First, click the '''Mesh Settings''' {| class="wikitable"|-! scope="col"| Icon! scope="col"| Source Type! scope="col"| Applications! scope="col"| Host Object! scope="col"| Spatial Domain! scope="col"| Restrictions / Additional Requirements|-| style="width:30px;" | [[ImageFile:mesh_settingslumped_src_icon.png]] button of the '''Simulate Toolbar''' or select '''Menu > Simulate > Discretization > Mesh Settings| style="width:150px;" | [[Glossary_of_EM...'''Cube%27s_Materials, or right click on the '''Yee Mesh''' item of the Navigation Tree and select '''Mesh Settings...''' from the contextual menu_Sources, _Devices_%26_Other_Physical_Object_Types#Lumped Source |Lumped Source]]| style="width:250px;" | General-purpose point voltage source| style="width:200px;" | PEC or use the keyboard shortcut '''Ctrl+G'''. The Mesh Settings Dialog opens up, where you can set the values of the various mesh thin wire line parallel to a principal axis| style="width:200px;" | A single point| style="width:200px;" | None|-| style="width:30px;" | [[parametersFile:distrb_src_icon.png]] including the '''Mesh Density'''.* After specifying the desired mesh density, you can examine the mesh grid plane| style="width:150px;" | [[Glossary_of_EM. The XYCube%27s_Materials, YZ_Sources, and ZX mesh grid planes can be displayed through '''Menu > Simulate > Discretization > Grid Planes > XY Plane'''_Devices_%26_Other_Physical_Object_Types#Distributed Source |Distributed Source]]| style="width:250px;" | General-purpose distributed planar source with a uniform, '''YZ Plane''' edge-singular or '''ZX Plane''' or by right clicking on one of the three '''XY Plane'''sinusoidal impressed field profile| style="width:200px;" | Virtual rectangle strip parallel to a principal plane| style="width:200px;" | A rectangular area| style="width:200px;" | None|-| style="width:30px;" | [[File:mstrip_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials, '''YZ Plane''' or '''ZX Plane''' items _Sources,_Devices_%26_Other_Physical_Object_Types#Microstrip Port |Microstrip Port Source]]| style="width:250px;" | Used for S-parameter computations in the '''Discretization''' section of the Navigation Tree and selecting '''Show''' from the contextual menu. The mesh grid planes give you microstrip-type structures| style="width:200px;" | PEC rectangle strip parallel to a good idea of what principal plane| style="width:200px;" | A vertical rectangular area underneath the mesh will look like once it is generated and its resolution along different planes. To remove host strip| style="width:200px;" | Requires a mesh grid PEC ground plane from strip underneath the project workspacehost strip|-| style="width:30px;" | [[File:cpw_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials, select '''Menu > Simulate > Discretization > Grid Planes >''' one more time and remove the check mark _Sources,_Devices_%26_Other_Physical_Object_Types#Coplanar Waveguide (CPW) Port |Coplanar Waveguide (CPW) Port Source]]| style="width:250px;" | Used for S-parameter computations in front of CPW-type structures| style="width:200px;" | PEC rectangle strip parallel to a principal plane| style="width:200px;" | Two parallel horizontal rectangular areas attached to the name of opposite lateral edges the currently displayed mesh grid plane, or right click host center strip| style="width:200px;" | Requires two parallel PEC ground strips on the name two sides of the currently displayed mesh grid plane host center strip|-| style="width:30px;" | [[File:coax_icon.png]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Coaxial Port |Coaxial Port Source]]| style="width:250px;" | Used for S-parameter computations in coaxial-type structures| style="width:200px;" | PEC Cylinder oriented along a principal axis| style="width:200px;" | A circular ring area enveloping the Navigation Tree and select '''Hide''' from the contextual menuhost inner conductor cylinder| style="width:200px;" | Requires a concentric hollow outer conductor cylinder|-| style="width:30px;" | [[File:wg_src_icon.png]]* To display the FDTD mesh| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials, click _Sources,_Devices_%26_Other_Physical_Object_Types#Waveguide Port |Waveguide Port Source]]| style="width:250px;" | Used for S-parameter computations in waveguide structures| style="width:200px;" | Hollow PEC box oriented along a principal axis| style="width:200px;" | A rectangular area at the '''Show Mesh''' cross section of the host hollow box| style="width:200px;" | The host box object can have one capped end at most. |-| style="width:30px;" | [[ImageFile:mesh_toolhertz_src_icon.png]] button | style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Filamentary_Current_Source |Filamentary Current Source]]| style="width:250px;" | General-purpose wire current source of the '''Simulate''' '''Toolbar '''two types: Hertzian short dipole radiator and long wire current source with a uniform, triangular or select '''Menu > Simulate > Discretization > Show Mesh''' or use sinusoidal current distribution profile| style="width:200px;" | None (stand-alone source)| style="width:200px;" | A line| style="width:200px;" | Hertzian short dipole radiators can have an arbitrary orientation, but long wire current sources must be aligned along one of the keyboard shortcut '''Ctrl+M'''principal axes|-| style="width:30px;" | [[File:plane_wave_icon. This takes png]]| style="width:150px;" | [[EMGlossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Plane Wave |Plane Wave Source]] into its | style="Mesh Viewwidth:250px;" mode, and the Yee mesh | Used for modeling electromagnetic scattering & computation of reflection/transmission characteristics of periodic surfaces | style="width:200px;" | None (stand-alone source)| style="width:200px;" | Surface of a cube enclosing the whole physical structure is displayed in the project workspace| style="width:200px;" | None|-| style="width:30px;" | [[File:gauss_icon. While the mesh view is enabledpng]]| style="width:150px;" | [[Glossary_of_EM.Cube%27s_Materials, _Sources,_Devices_%26_Other_Physical_Object_Types#Gaussian Beam |Gaussian Beam Source]]| style="width:250px;" | Used for modeling focused beams | style="width:200px;" | None (stand-alone source)| style="width:200px;" | Surface of a cube enclosing the '''Show Mesh''' physical structure| style="width:200px;" | None|-| style="width:30px;" | [[ImageFile:mesh_toolhuyg_src_icon.png]] button remains depressed| style="width:150px;" | [[Glossary of EM. To get back to Cube's Materials, Sources, Devices & Other Physical Object Types#Huygens Source |Huygens Source]]| style="width:250px;" | Used for modeling equivalent sources imported from other [[EM.Cube]]'s modules | style="Normal Viewwidth:200px;" mode, click this button one more time, or deselect '''Menu > Simulate > Discretization > Show Mesh''' to remove its check mark or simply hit the '''Esc Key''' | None (stand-alone source)| style="width:200px;" | Surface of the keyboard.a cube | style="width:200px;" | Imported from a Huygens surface data file|}
In [[EM.Cube]]'s "Mesh View" mode, you can rotate or pan the view of the project workspace, but you cannot edit the objects. '''"Show Mesh"''' generates a new mesh and displays it if there is none in the memory, or it simply displays an existing mesh in the memory. This is a useful feature because generating an FDTD mesh may take a long time depending Click on the complexity of structure each category to learn more details about each source type and the total size of the computational domain. If you change the structure or alter the mesh settings, a new mesh is always generated. You can ignore any mesh in the memory and force [[EM.Cube]] how to generate a fresh FDTD mesh from the ground up by selecting '''Menu > Simulate >Discretization > Regenerate Mesh''' or by right clicking on the '''Yee Mesh''' item of the Navigation Tree and selecting '''Regenerate''' from the contextual menudefine one.
{{twoimg|FDTD34[[Image:Info_icon.png|A human head model and a cellular phone handset on its side.|FDTD33.png|The regular FDTD mesh of 30px]] More information about all the human head model and source types can be found in the cellular phone handset'''[[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types]]'''.}}
===Mesh Profiling & Grid Coordinate System===In the most general sense, one can consider two fundamental types of excitation sources for an FDTD simulation: a lumped source and a distributed source. A lumped sources is localized at a single mesh point in the computational domain, while a distributed source is spread over several mesh cells. Among the source types of the above list, the microstrip port, CPW port, coaxial port, waveguide port, plane wave and Gaussian beam sources are indeed special cases of a distributed source for specific applications.
A volumetric FDTD mesh lumped source is overwhelming for visualization in the 3D space. For this reason, [[EM.Cube]]'s mesh view only shows the outline most commonly used way of the (staircased) meshed objects, skipping the outline of all the individual brick cells exciting a structure in the entire computational domainEM. The mesh grid planes provide Tempo. A lumped source is a 2D profile voltage source with a series internal resistor that must be placed on a PEC or thin wire line object that is parallel to one of the mesh cells along the three principal coordinate planesaxes. Since A lumped source is displayed as a small red arrow on the Yee cells host line. Lumped sources are congruent along typically used to define ports and compute the coordinate axesport characteristics like S/Y/Z parameters. Using simple lumped sources, the three mesh grid planes together provide you can simulate a complete picture variety of the entire FDTD mesh. To display a mesh grid planestransmission line structures including filters, select '''Menu > Simulate > Discretization > Grid Planes >''' and pick one of the three options: '''XY Plane''', '''YZ Plane''' couplers or '''ZX Plane'''antenna feeds. You This approach may also right click on one become less accurate at higher frequencies when the details of the '''XY Plane'''feed structure become important and can no longer be modeled with highly localized lumped ports. In such cases, '''YZ Plane''' or '''ZX Plane''' items in it is recommended to use “Distributed Sources”, which utilize accurate modal field distributions at the '''Discretization''' section ports for calculation of the Navigation Tree incident and select '''Show''' from reflected waves. Waveguide source is used to excite the contextual menudominant TE<sub>10</sub> mode of a hollow rectangular waveguide. Other special types of distributed sources are microstrip port, CPW port and coaxial ports that can be used effectively to excite their respective transmission line structures.
While a mesh grid plane is visible, When you can move it back and forth between the two boundary planes at the two opposite sides create an array of the computational domain. You an object type that can do this in host one of the following four ways:above source types, you can also associate a source array with that array object.
* Using the keyboard's '''Page Up (PgUp) Key''' and '''Page Down (PgDn) key'''[[Image:Info_icon.* By selecting png|30px]] Click here to learn more about '''Menu > Simulate > Discretization > Grid Planes > Increment Grid''' or ''' Decrement Grid'''.* By right clicking on one of the '''XY Plane''', '''YZ Plane''' or '''ZX Plane''' items in the '''Discretization''' section of the Navigation Tree and selecting '''Increment Grid''' or ''' Decrement Grid''' from the contextual menu.* Using the [[Keyboard ShortcutsPreparing_Physical_Structures_for_Electromagnetic_Simulation#Modeling_Finite-Sized_Source_Arrays |keyboard shortcutsModeling Finite-Sized Source Arrays]] '''">"''' or '''"<"'''.
As you “step through” A plane wave source is a popular excitation method that is used for calculation of the radar cross section of targets or profile reflection and transmission characteristics of periodic surfaces. A Gaussian beam source is another source type that is highly localized as opposed to the mesh griduniform plane wave. For both plane wave and Gaussian beam sources, [EM.Tempo requires a finite incidence surface to calculate the excitation. When you can see how create either of these sources, a plane wave box or a Gaussian beam box is created as part of their definition. A trident symbol on the structure box shows the propagation vector as well as the E-field and H-field polarization vectors. The time domain plane wave or Gaussian beam excitation is discretized along internal planes calculated on the surface of this box and injected into the computational domain.The plane wave box is displayed in the project workspace as a purple wireframe box enclosing the structure, while the Gaussian beam box appears as a green wireframe box. Both boxes have an initial default size with an offset of 0.2&lambda;<sub>0</sub> from the largest bounding box enclosing your entire physical structure. In both source dialogs, the radio button '''Size: Default''' is selected by default. The radio button '''Size: Custom''' allows you to set the excitation box manually. The values for the coordinates of '''Corner 1''' and '''Corner 2''' can now be changed. Corner 1 is the front lower left corner and Corner 2 is the rear upper right corner of the box. The corner coordinates are defined in the world coordinate system (WCS). <table><tr><td> [[Image:FDTD MAN11.png|thumb|360px|A plane wave box enclosing a PEC cylinder at oblique incidence: &theta; = 105&deg; and &phi; = 315&deg;.]] </td><td> [[Image:FDTD MAN12.png|thumb|360px|A Gaussian beam box enclosing a PEC cylinder at oblique incidence: &theta; = 105&deg; and &phi; = 315&deg;. The concentric circles represent the beam's focus point and radius.]] </td></tr></table>
Once the project structure is meshed in [[EM.Cube]]'s [[FDTD Module]], === Simulating a second coordinate system becomes available to you. The mesh grid coordinate system allows you to specify any location Multiport Structure in the computational domain in terms of node indices on the mesh grid. [[EM.Cube]] displays the total number of mesh grid lines of an FDTD simulation domain (N<sub>x</sub> × N<sub>y</sub> × N<sub>z</sub>) along the three principal axes on the '''Status Bar'''. Therefore, the number of cells in each direction is one less than the number of grid lines, i.e. (N<sub>x</sub>-1)× (N<sub>y</sub>-1) × (N<sub>z</sub>-1). The minimum X, Y, and Z coordinates of the FDTD domain in the world coordinate system (Xmin, Ymin, Zmin), which represent the lower left front corner of the domain box, become the origin of the mesh grid coordinate system (0,0,0), The maximum domain coordinates, which represent the upper right back corner of the domain box, are therefore (N<sub>x</sub>-1, N<sub>y</sub>-1, N<sub>z</sub>-1).Tempo ===
[[EM.Cube]] allows you Ports are used to navigate through the mesh grid order and evaluate the grid points individuallyindex sources for circuit parameter calculations like S/Y/Z parameters. Every time you display one of the three mesh grid planes, the "'''Grid Coordinate System (GCS)'''" is automatically activatedIn EM. On the Status Bar, you will see [[Image:statusgrid.png]] instead of the default [[Image:statusworld.png]]. This means that the current coordinates reported on Status Bar are now expressed in grid coordinate system. The current grid point is displayed by a small white circle on the current mesh grid plane, and it always starts from (I= 0, J=0, K=0). Using the keyboard's '''Arrow Keys'''Tempo, you can move the white circle through the mesh grid plane and read the current node's (I, J, K) indices on the status bar. You can switch back to the "'''World Coordinate System (WCS)'''" or change to the "'''Domain Coordinate System'''" by double-clicking the status bar box that shows the current coordinate system and cycling through the three options. The domain coordinate system is one that establishes its origin define ports at the lower left front corner location of the computational domain and measure distances in project unit just like the WCS.following types of sources:
{{isoimg*[[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Lumped Source |FDTD35(1)Lumped sources]]*[[Glossary of EM.pngCube's Materials, Sources, Devices & Other Physical Object Types#Distributed Source |The grid cursor on the XY grid plane and its grid coordinates (IDistributed sources]]*[[Glossary of EM.Cube's Materials, JSources, KDevices & Other Physical Object Types#Microstrip Port |Microstrip port sources]]*[[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Coplanar Waveguide (CPW) displayed on the status barPort |CPW port sources]]*[[Glossary of EM.}}Cube's Materials, Sources, Devices & Other Physical Object Types#Coaxial Port |Coaxial port sources]]*[[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Waveguide Port |Waveguide port sources]]
===Meshing Arbitrary Geometries===Every time you create a new source with one of the above types, the program asks if you want to initiate a new port and associate it with the newly created source. If the physical structure of your project workspace has N sources, then N default ports are defined, with one port assigned to each source according to their order in the navigation tree. You can define any number of ports equal to or less than the total number of sources in your project.
Straight linesIf your physical structure has two or more sources, boxes and rectangular plates whose edges are aligned with but you have not defined any ports, all the three principal axes are sources will excite the simplest objects structure simultaneously during the simulation. However, when you assign N ports to mesh the sources, then you have a multiport structure that is characterized by an N×N scattering matrix, an N×N impedance matrix, and an N×N admittance matrix. To calculate these matrices, EM.Tempo uses a binary excitation scheme in conjunction with the [[FDTD Module]]principle of linear superposition. Such objects preserve their shapes exactly after discretizationIn this binary scheme, the structure is analyzed a total of N times. All Each time one of the objects with curved edges N port-assigned sources is excited, and curved surfaces or objects with straight edges and flat faces that all the other port-assigned sources are not parallel to turned off. In other words, the principal axes or principal planes need to be discretized using FDTD solver runs a staircase profile"port sweep" internally.When the ''j''th port is excited, all the S<sub>ij</sub> parameters are calculated together based on the following definition:
In the cases of oblique lines and slanted faces :<math> S_{ij} = \sqrt{\frac{Re(like lateral faces of a pyramidZ_i), a uniform staircase profile is used by all of [[FDTD Module]]'s three mesh generators. in other words, the cell sizes or grid line spacing remain the same across the edge or face, since the slope is constant. In the case of curved edges and curved faces or surfaces }{Re(like a sphereZ_j), the uniform and regular mesh generators use a uniform staircase profile. However, the adaptive mesh generator uses a variable staircase profile, where the cell sizes of grid line spacing vary with the curvature (derivative) of the edge or face. As a result, a higher mesh resolution is achieved at "more curvy" areas to better capture the geometrical details.}} \cdot \frac{V_j - Z_j^*I_j}{V_i+Z_i I_i} </math>
{{twoimg|FDTD31(1)where V<sub>i</sub> is the voltage across Port i, I<sub>i</sub> is the current flowing into Port i and Z<sub>i</sub> is the characteristic impedance of Port i.png|A pyramidal object with a slanted plate|FDTD32(2)The sweep loop then moves to the next port until all ports have been excited.png|An adaptive FDTD mesh}}
{{twoimg|FDTD26In summary, to analyze an N-port structure, EM.png||FDTD25Tempo runs N separate FDTD time marching loops.png|}}The S/Z/Y parameters are frequency-domain quantities. The port voltages and currents are Fourier-transformed to the frequency domain over the frequency range [fc-bw/2, fc+bw/2], where fc is the center frequency and bw is the bandwidth of your project. You can reduce the frequency range of the Fourier transform by settings new values for '''Start''' and '''End''' frequencies in the "Port Definition" dialog as long as these are within the range [fc-bw/2, fc+bw/2]. By default, 200 frequency samples are taken over the specified frequency range. This number can be modified from the FDTD simulation engine settings dialog.
{{twoimgNote|FDTD27In order to obtain correct results, the port impedance must equal the characteristic impedance of the transmission line on which the port is established.png||FDTD28This is not automatically taken care of by EM.Tempo.png|}}The geometry of a sphere and its regular and adaptive FDTD meshes (top and perspective views).
=== FDTD Mesh Settings ===[[Image:Info_icon.png|30px]] Click here to learn more about the '''[[Glossary_of_EM.Cube%27s_Simulation_Observables_%26_Graph_Types#Port_Definition_Observable | Port Definition Observable]]'''.
[[Image:FDTD80Info_icon.png|thumb|400px|[[FDTD Module30px]]Click here to learn more about 's Mesh Settings dialog''[[Preparing_Physical_Structures_for_Electromagnetic_Simulation#Modeling_Coupled_Sources_.26_Ports | Modeling Coupled Sources & Ports]]'''.
<table><tr><td> [[EMImage:FDTD MAN15.png|thumb|left|640px|A two-port CWP transmission line segment.Cube]]'s </td></tr><tr><td> [[Image:FDTD ModuleMAN16.png|FDTD module]] discretizes objects using what is often referred to as the “staircase approximation”thumb|left|480px|EM. In this mesh generation scheme, the structure is recreated using a large number of cubic cells carefully assembled in a way that approximates the shape of the original structureTempo's port definition dialog. By default, a carefully calculated, "]] <u/td>'''Adaptive'''</utr></table>" mesh of your physical structure is generated in order to satisfy the following criteria:
* Optimize the number of mesh cells in each dimension. The product of the number of cells in each dimension determines the total mesh size. The larger the mesh size, the longer the simulation time, especially with the CPU version of the FDTD engine. Also, a very large mesh size requires more RAM, which may exceed your GPU memory capacity. Set the '''Minimum Mesh Density''' to a moderately low value to keep the mesh size manageable, but be careful not to set it too low (see the next item below).* Ensure simulation accuracy by requiring an acceptable minimum number of cells per wavelength through each object and in the empty (free) space between them and the computational domain boundaries. An effective wavelength is defined for each material at the highest frequency of the project's specified spectrum. We recommend a '''Minimum Mesh Density '''of at least 15-20 cells/ wavelength. But for some resonant structures, 25 or even 30 cells per wavelength may be required to achieve acceptable accuracy. As you reduce the mesh density, the simulation accuracy decreases.* Accurately represent and approximate the boundaries of edges or surfaces that are not grid-aligned by closely adhering to their geometric contours. This is controlled by the '''Minimum Grid Spacing Over Geometric Contours''', which can be specified either as a fraction of the free space grid spacing or as an absolute length value in project units.* Maximize the minimum grid spacing in any dimension inside the computational domain and thus maximize the simulation time step. The time step size is dictated by the CFL stability criterion and is driven by the smallest grid spacing in each dimension. The smaller the time step, the larger the number of time steps required for convergence. This is controlled using the '''Absolute Minimum Grid Spacing''', which can be specified either as a fraction of the free space grid spacing or as an absolute value. It is critical to accurately represent and precisely maintain the object edge/surface boundaries in certain structures like resonant antennas and filters, as the phase of the reflected fields/waves is affected by the object boundary positions. When object boundaries are very close to each other, the mesh needs to represent them by two separate, but very closely spaced, grid lines. To control the minimum allowed grid spacing, use the '''Absolute Minimum Grid Spacing '''settings,* Maintain a smooth grid with no abrupt jumps from low-density to high-density regions. This feature is enabled with the '''Create Gradual Grid Transitions '''check box (always checked by default).=== Excitation Waveform & Frequency Domain Computations ===
Occasionally, you may prefer a more regular When an FDTD mesh with almost equal grid line spacing everywheresimulation starts, but still with a frequency-dependent cell size. In that case, you can select your project's source starts pumping energy into the "<ucomputational domain at t >0. Maxwell'''Regular'''</u>" option of the '''Mesh Type '''dropdown list s equations are solved in all cells at every time step until the FDTD Mesh Settings dialog. The regular FDTD mesh enforces only two solution converges, or the maximum number of the above [[parameters]]: '''Minimum Mesh Density''' and '''Absolute Minimum Grid Spacing'''time steps is reached. Or you may opt for an absolutely "<uA physical source has a zero value at t = 0, but it rises from zero at t >'''Uniform'''</u>" mesh type, for which you need 0 according to specify the '''Cell Size '''along the X, Y, Z directions in project unitsa specified waveform.EM.Tempo currently offers four types of temporal waveform:
===Global vs. Local Control Of FDTD Mesh===# Sinusoidal# Gaussian Pulse# Modulated Gaussian Pulse# Arbitrary User-Defined Function
{{mainpage|[[Advanced Meshing in A sinusoidal waveform is single-tone and periodic. Its spectrum is concentrated around a single frequency, which is equal to your project's center frequency. A Gaussian pulse decays exponentially as t &rarr; &infin;, but it has a lowpass frequency spectrum which is concentrated around f = 0. A modulated Gaussian pulse decays exponentially as t &rarr; &infin;, and it has a bandpass frequency spectrum concentrated around your project's center frequency. For most practical problems, a modulated Gaussian pulse waveform with EM.Tempo]]}} 's default parameters provides an adequate performance.
When [[EM.Cube]] generates an FDTD mesh, a large number The accuracy of geometrical considerations are taken into account. These include the bounding box of each object and its corners, FDTD simulation results depends on the ends right choice of temporal waveform. EM.Tempo's default waveform choice is a line, modulated Gaussian pulse. At the apex end of a cone or pyramidan FDTD simulation, or the locations of lumped sources, time domain field probes and sensors, vertices of plane wave data are transformed into the frequency domain at your specified frequency or far field boxes, bandwidth to name a few examples. These points are “locked” as fixed grid nodes in produce the FDTD meshdesired observables.
You can control the global mesh more selectively using the Advanced FDTD Mesh Settings Dialog{{Note|All of EM. To open this dialog, click the Tempo'''Advanced '''button at the bottom of the FDTD Mesh Settings dialog. For example, s excitation sources have a default modulated Gaussian pulse waveform unless you can control the quality of the gradual grid transitions by setting the value of '''Max Adjacent Cell Size Ratio'''change them. }}
In certain cases, you may wish to exert some level of local mesh control[[Image:Info_icon. For example, you may want png|30px]] Click here to increase the mesh density at a very particular area of your structure. Or you may want to increase or decrease the mesh resolution inside certain types of materials independent of their permittivity and permeabilitylearn more about EM. Tempo's '''[[EM.CubeBasic_Principles_of_The_Finite_Difference_Time_Domain_Method#The_Relationship_Between_Excitation_Waveform_and_Frequency-Domain_Characteristics | Standard & Custom Waveforms and Discrete Fourier Transforms]] provides two additional mechanisms for local control of the FDTD mesh: locking mesh of object groups and user defined fixed grid points'''.
=== Defining Custom Waveforms in EM.Tempo ===
==In some time-domain applications, you may want to simulate the propagation of a certain kind of waveform in a circuit or structure. In addition to the default waveforms, EM.Tempo allows you to define custom waveforms by either time or frequency specifications for each individual source in your project. If you open up the property dialog of any source type in EM.Tempo, you will see an {{key|Excitation Sources==Waveform...}} button located in the "Source Properties" section of the dialog. Clicking this button opens up EM.Tempo's Excitation Waveform dialog. From this dialog, you can override EM.Tempo's default waveform and customize your own temporal waveform. The Excitation Waveform dialog offers three different options for defining the waveform:
Before you can run an FDTD simulation, you have to define a source to excite your project’s physical structure. A physical source has a zero value at t = 0, but it rises from zero at t > 0 according to a specified waveform. [[EM.Tempo]] currently offers four types of temporal waveform:* Automatically Generate Optimal Waveform* Use Custom Frequency Domain Specifications* Use Custom Time Domain Specifications
# Sinusoidal# The first option, which is also the default option, constructs an optimal modulated Gaussian Pulse# Modulated Gaussian Pulse# Arbitrary User-Defined Functionpulse waveform based on your project's specified center frequency and bandwidth. This optimal waveform guarantees the most accurate frequency domain computations for your simulation. The second option gives you a choice of the three standard waveforms and lets you define their waveform parameters in terms of frequency domain characteristics like center frequency and bandwidth and spectral contents. The third option lets you define a completely arbitrary temporal waveform for your source.
A sinusoidal Select the third option of waveform is single-tone definition and periodicthen choose the '''Custom''' option from the '''Waveform Type''' dropdown list. Its spectrum is concentrated around Enter a single frequency, which is equal to mathematical expression for your projectcustom waveform a function of the time variable "T" or "t" in the box labeled '''Expression'''s center frequency. A sinusoidal source does not have a finite energy You can use arithmetic operations, standard and it does not decay library functions as t &rarr; &infin;. A Gaussian pulse decays exponentially well as t &rarr; &infin;, but it has a lowpass frequency spectrum which is concentrated around f = 0user-defined Python functions. A modulated Gaussian pulse decays exponentially as t &rarr; &infin;, and it does have a bandpass frequency spectrum concentrated around your project's center frequency. For most practical problems, a modulated Gaussian pulse waveform provides an adequate performance. That is why this type of waveform is chosen by [[EMImage:Info_icon.Cubepng|30px]] as your projectClick here to learn more about '''[[Using Python to Create Functions, Models & Scripts#Creating Custom Python Functions | Creating Custom Python Functions]]'''s default waveform.
When an <table><tr><td> [[Image:FDTD simulation starts, your project's source starts pumping energy into the FDTD computational domain at t > 0MAN13. Maxwellpng|thumb|left|720px|EM.Tempo's equations are solved in all cells at every time step until excitation waveform dialog showing the solution converges, or the maximum number of time steps is reached. If you use a Gaussian pulse or a default standard modulated Gaussian pulse temporal waveform to drive your FDTD source, after a certain number of time steps, the total energy of the computational domain drops to very negligible levels. At the point, you can consider your solution to have converged. If you drive your FDTD source by a sinusoidal waveform, the total energy of the computational domain will oscillate indefinitely, and you have to force the time loop to terminate after a certain number of time steps assuming a steady state have been reached.]]</td></tr></table>
[[EM.Cube]]'s [[FDTD Module]] provides When you define a number of sources or excitation schemes that have different applications. These source types will be described custom waveform in the following sections. An [[#Ideal SourcesExcitation Waveform dialog, make sure to click the {{key|Ideal Source]] is Accept}} button of the simplest way of exciting a structure in [[EMdialog to make your changes effective.Cube]]'s [[FDTD Module]]. It consists of an ideal voltage source connected between two consecutive nodes A graph of your FDTD mesh. A [[#Lumped Sources|Lumped Source]] custom waveform is an ideal voltage source plotted in series with a resistor. You have to place a lumped source on a line object that is parallel to one the right panel of the three principal axes, and you can assign a port to it to calculate the circuit characteristics of dialog for your structurereview. A [[#Waveguide Sources|Waveguide Source]] It is placed across a rectangular waveguide. In other words, it requires a hollow box object important to keep in mind that is aligned along one typical time scales in the FDTD simulation of RF structures are on the three principal axes and has one order of nanosecond or two open endssmaller. A waveguide source can excite a certain TE<sub>mn</sub> or TM<sub>mn</sub> modal profile Using the variable "fc" in the expression of the host rectangular waveguideyour waveform definition usually takes care of this required scaling. A [[#Distributed Sources|Distributed Source]] is defined on a finiteOtherwise, you need to use scaling factors like 1e-sized plane parallel to one of 9 explicitly in your expression. For example, in the three principal planes and with figure below, we have defined a prescribed field distribution profile on that plane. A [[#Plane Waves|Plane Wave Source]] is used to study modulated Bessel waveform in the scattering characteristics form of your structure and compute its radar cross section "sp.j0(RCSt/2e-9)*sin(2*pi*fc*t)", where sp. A [[#Focused Gaussian Beams|Gaussian Beam Source]] is similar to a plane wave source but with a focused energy profile in j0(x) denotes the transverse direction and a beamzeroth-diverging profile in order Bessel function of the longitudinal directionfirst kind burrowed from Python's special functions module.
===Ideal Sources===[[Image:Info_icon.png|30px]] Click here to learn more about '''[[Glossary of EM.Cube's Python Functions#Standard Python Functions | Python's Standard & Advanced Mathematical Functions]]'''.
[[Image:FDTD42.png{{Note|thumb|250px|[[If you define a custom excitation waveform for your source, none of the standard frequency domain output data and parameters will be computed at the end of your FDTD Module]]'s Ideal Source dialog]]simulation.}}
An ideal source acts as <table><tr><td> [[Image:FDTD MAN14.png|thumb|left|720px|EM.Tempo's excitation waveform dialog showing a voltage source with a zero internal resistance that can be placed between any two adjacent mesh grid nodes anywhere in custom modulated Bessel temporal waveform defined using the computational domainPython function sp. To create a new ideal source, follow these steps:j0(x).]]</td></tr></table>
* Right click on the '''Ideal Sources''' item in the '''Sources''' section of the Navigation Tree and select '''Insert New Source...''' to open the Ideal Source Dialog.* You can change the default name of the source as well as its color. The ideal source is displayed as a small orange arrow in the Project Workspace.* By default, [[== EM.Cube]] creates a +Z-directed ideal source located at the origin of coordinates (0, 0, 0). You can change the location of the source by setting new values for the X, Y and Z coordinates. When you use the spin buttons to increment or decrement the source coordinates, you can see the source moving in the project workspace. You can also change the Tempo'''Direction''' of the source from a dropdown list in the Source Location section of the dialog that contains ±X, ±Y and ±Z options.* In the '''Source Properties''' section, you can specify the '''Source Amplitude''' in Volts and the '''Phase''' in Degrees.s Active & Passive Devices ==
===Defining Lumped SourcesDevices ===
In [[Image:FDTD43EM.png|thumb|200px|[[FDTD Module]]’s Lumped Source dialogTempo]], you can define eigth types of lumped devices:
A # '''Lumped Source [[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Resistor | Resistor]]'' is the most commonly used way ' # '''[[Glossary of exciting a structure in EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Inductor | Inductor]]'''# '''[[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Capacitor | Capacitor]]''' # '''[[Glossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Series_RL_Device | Series RL Device]]''' # '''[[FDTD ModuleGlossary of EM.Cube's Materials, Sources, Devices & Other Physical Object Types#Parallel_RC_Device | Parallel RC Device]]''' # '''[[Glossary of EM. A lumped source acts as a voltage source in series with an internal resistance that is placed between two adjacent mesh grid nodes on a line objectCube's Materials, Sources, Devices & Other Physical Object Types#Diode | Nonlinear Diode]]''' # '''[[Glossary of EM. The line object must be parallel to one Cube's Materials, Sources, Devices & Other Physical Object Types#Active_Lumped_One-Port_Device | Active Lumped One-Port Device]]''' # '''[[Glossary of the three principal axesEM.Cube's Materials, Sources, Devices & Other Physical Object Types#Active_Lumped_Two-Port_Device | Active Lumped Two-Port Device]]'''
{{Note|In order Lumped devices are connected between two adjacent FDTD mesh nodes. Although lumped devices are not sources and the passive types do not excite a structure, their properties are similar to lumped sources. That is why they are listed under the '''Sources''' section of the navigation tree. A lumped device has to create be associated with a PEC line object that is parallel to one of the three principal axes. Similar to lumped sourcesources, you must lumped devices have at least one line object in an '''Offset''' parameter that is equal to the project workspacedistance between their location on the host line and its start point.}}
To create a new A lumped source, follow these stepsdevice is characterized by a v-i equation of the form:
* Right click on the '''Lumped Sources''' item in the '''Sources''' section of the Navigation Tree and select '''Insert New Source...''' to open the Lumped Source Dialog.* In the '''Source Location''' section of the dialog, you will find a list of all eligible line objects (:<math>i.e. lines that are parallel to one of the principal axes(t) = L \{ v(t). Select the desired line object. The box labeled '''Direction''' shows the direction of the source with respect to the host line object. You have the option to select either the positive or negative direction for the source.* In the box labeled '''Offset''', enter the distance of the source from the start point of the line. A lumped source by default is placed at the center of the host line. In other words, the default offset value is equal to half the length of the host line object.* In the '''Source Properties''' section, you can specify the source '''Amplitude''' in Volts, '''Phase''' in Degrees and internal '''Resistance''' in Ohms.\} </math>
===Waveguide Sources===where V(t) is the voltage across the device, i(t) is the current flowing through it and ''L'' is an operator function, which may involve differential or integral operators. Lumped devices are incorporated into the FDTD grid across two adjacent nodes in a similar manner to lumped sources. At the location of a lumped device, the FDTD solver enforces the device's governing equation by relating the device voltage and current to the electric and magnetic field components and updating the fields accordingly at every time step. [[Image:Info_icon.png|30px]] Click here for a general discussion of '''[[Preparing_Physical_Structures_for_Electromagnetic_Simulation#A_Review_of_Linear_.26_Nonlinear_Passive_.26_Active_Devices | Linear & Nonlinear Passive & Active Devices]]'''.
Waveguide structures have many applications at microwave and millimeter wave frequencies{{Note|Small values of inductance may result in the divergence of the FDTD numerical scheme. For exampleTo avoid this problem, a rectangular waveguide is used you need to feed increase the mesh resolution and adopt a pyramidal horn antenna. A waveguide structure is usually excited using some type of strategically located probe mechanismhigher mesh density. This can be modeled using a lumped source placed on a wire structure made up , of line objects. Alternatively, use can use [[EM.Cube]]'s '''Waveguide Sources'''course, may lead to a special type of source that excites a prescribed modal field distribution in a rectangular waveguide structure. The scattering [[parameters]] are calculated from knowledge of incident and reflected fields at designated waveguide ports. Waveguide sources typically provide more accurate results for scattering [[parameters]] compared to lumped ports as they represent the actual dominant propagating modes at the transmission line portsmuch longer computation time.}}
<table><tr><td> [[Image:FDTD MAN17.png|thumb|left|480px|EM.CubeTempo's lumped device dialog for nonlinear diode.]] provides special waveguide sources that can excite either the TE<sub/td>mn</subtr> or TM<subtr>mn</subtd> modes of a rectangular waveguide which is oriented along one of the three principal axes[[Image:FDTD MAN17A. In other words, the plane of the waveguide source must be parallel to one of the principal (XY, YZ or ZX) coordinate planespng|thumb|left|480px|EM.Tempo's lumped device dialog for active lumped two-port device.]] </td></tr></table>
[[Image:FDTD44.png|thumb|200px|[[FDTD Module]]'s Waveguide Source dialog.]]=== Defining Active Distributed Multiport Networks ===
{{Note|In order to create a waveguide source, you must have at least one "Hollow" Box object with no caps or only one end cap in your projectEM.}}Tempo also provides two types of active distributed multiport network devices:
To create a new waveguide source# '''[[Glossary_of_EM.Cube%27s_Materials, follow these steps:_Sources,_Devices_%26_Other_Physical_Object_Types#Active_Distributed_One-Port_Device | Active Distributed One-Port Device/Circuit]]''' # '''[[Glossary_of_EM.Cube%27s_Materials,_Sources,_Devices_%26_Other_Physical_Object_Types#Active_Distributed_Two-Port_Device | Active Distributed Two-Port Device/Circuit]]'''
* Right click on Unlike the '''Waveguide Sources''' item in the '''Sources''' section of the Navigation Tree active lumped devices, these devices are rather distributed and select '''Insert New Source...''' their behavior is similar to open the Waveguide Source Dialoga microstrip port source.* In the '''Source Location''' section of the dialogother words, you will find a list of all the eligible box objects. These are all the hollow boxes in the project workspace whose longitudinal axis is parallel to active distributed one of the principal axes and have at least one unchecked '''Cap Ends''' box in their property dialog. Select the desired box -port device requires a rectangle strip object. The box labeled '''Direction''' shows the direction of the source with respect to the as a host box object. You have , while the option to select either the positive or negative direction active distributed two-port device requires two rectangle strip objects for the sourceits definition.* In the box labeled '''Offset''', enter the distance You can choose one of the source plane from the base edges of the box strip object. A waveguide source by default is placed at for establishing the center of the host boxcircuit port. In other words, the default offset value is equal to half the length case of the host box object.* The default waveguide more to be excited is TE<sub>10</sub>. You can select '''TE''' or '''TM''' mode types with arbitrary "m" and "n" modal indices.* In the '''Source Properties''' sectiona two-port device, you can specify the source '''Amplitude''' in Volts, need two parallel and the '''Phase''' in Degreesend-to-end aligned strip objects.
=== Distributed Sources ===The circuit behavior of these devices is defined by a Netlist file. Their property dialog provides a text editor for simply writing the Netlist description of the device. You can also import an existing external Netlist file with a ".CIR" or ".TXT" file extension using the button labeled {{key|Load Netlist}}..
{{Note|[[Image:FDTD45RF.png|thumb|300px|[[FDTD Module]]'s Distributed Source dialogSpice A/D]]can generate a Netlist file corresponding to an existing circuit project, which can then be saved to a text file with a ".TXT" file extension. }}
Waveguide sources are a special case of distributed sources in <table><tr><td> [[Image:ActiveOnePort.png|thumb|left|480px|EM.Cube]]Tempo's [[FDTD Module]]. A Distributed Source is defined in a rectangular plane of finite extents, parallel to active one of the three principal coordinate planes-port device/circuit dialog. An impressed electric field component is assumed across the specified rectangular area, which pumps energy into the computational domain. The current version of [[EM.Cube]] provides three spatial field profiles for a distributed source:</td></tr></table>
# Uniform<table># Sinusoidal<tr># Edge<td> [[Image:ActiveTwoPort.png|thumb|left|720px|EM.Tempo's active two-Singularport device/circuit dialog.]] </td></tr></table>
The sinusoidal type has the functional form cos(py/w), and the edge-singular type has the functional form 1/v(1-(2y/w)^2), where y is the coordinate along the direction of field variation measured from the center of the rectangular area and w is its total width.=== A Note on Using Active Devices ===
[[Image:fdtd_src7_tnWhen your physical structure contains an active device, EM.png|thumb|250px|A distributed source placed between two horizontal rectangular stripsTempo performs an EM-circuit co-simulation that involves both the full-wave FDTD EM solver and the SPICE circuit solver. In a global self-consistent co-simulation, at each time step of the FDTD time marching loop, the electric and magnetic fields at the location of the device ports are used to compute the port voltages and currents. These quantities are then used in the SPCIE circuit solver to update all the voltages and currents at the internal nodes of the active device. The updated port voltages and currents are finally used to update the electric and magnetic fields in the physical mesh cells and the time marching loop proceeds to the next time step.]]
To create EM.Tempo can handle several active one-ports and two-ports simultaneously. In that case, all the devices are automatically compiled into a new distributed sourcesingle Netlist that serves as the input of the SPICE solver. The individual internal nodes of each device need to be renamed for the global Netlist. Besides the main circuit, follow these steps:the Netlist of each device may contain several "subcircuits". Note that the subcircuit nodes are not re-indexed for the global Netlist as is expected.
* Right click on the '''Distributed Sources''' item in the '''Sources''' section of the Navigation Tree and select '''Insert New Source...''' to open the Distributed Source Dialog.* In the '''Excitation Plane''' section of the dialog, first {{Note|If you have want to select the orientation of the use a B-type nonlinear dependent source plane. The dropdown list labeled '''Direction''' gives three options: '''X, Y''' and '''Z''', which create planes parallel to the YZ, ZX and XY principal planes, respectively. Depending on in the choice Netlist definition of the plane orientation, another dropdown list labeled '''Field Dir''' gives four options for the direction of the source field component. For example, the default plane orientation is X (parallel to the YZan active one-Plane) and the available field directions are +Y, port or two-Yport, +Z and -Z. Next, you have to enter the coordinates of two opposite corners of the source plane: the lower left and upper right corners. You can type it must be contained in values for the X, Y, Z coordinates or you can use the spin buttons to slide the default source planes a subcircuit definition rather than in the Project Workspace.* In the '''Source Properties''' section, you can select the '''Profile''' from three options: '''Uniform''', '''Sinusoidal''' and '''Edge-Singular'''. You can also specify the source '''Amplitude''' in Volts, and '''Phase''' in Degrees and the source's internal '''Resistance '''in Ohms main circuit.}}
===Defining Ports===The figure below shows the geometry of a two-port amplifier device with microstrip input and output transmission lines. The Netlist of the two-port device is given below:
[[Image:FDTD48.png|thumb|200px|The Port Definition dialog]]----
Ports are used to order and index sources for circuit parameter calculations like S/Y/Z [[parameters]]. That is why they are defined in the '''Observables''' section of Navigation Tree. In [[EM.Cube]]'s [[FDTD Module]], you can define ports at the location of '''Lumped Sources''', '''Waveguide Sources''' and '''Distributed Sources'''. In other words, ideal sources or other types of sources cannot be used to define ports or calculate port characteristics.C1 1 0 1p
Ports are defined in the '''Observables''' section of the Navigation Tree. Right click on the '''Port Definition''' item of the Navigation Tree and select '''Insert New Port Definition...''' from the contextual menu. The Port Definition Dialog opens up, showing the default port assignments. If you have N sources in your physical structure, then N default ports are defined, with one port assigned to each source according to their order on the Navigation Tree.R1 1 0 50
[[Image:FDTD49.png|thumb|250px|Reassigning sources to ports and defining coupled ports.]]E1 2 0 1 0 20
You can define any number of ports equal to or less than the total number of sources in your project. The Port List of the dialog shows a list of all the ports in ascending order, with their associated sources and the port's characteristic impedance, which is 50O by default. You can delete any port by selecting it from the Port List and clicking the '''Delete '''button of the dialog. Keep in mind that after deleting a port, you will have a source in your project without any port assignment. Make sure that is what you intend. When you delete one or more ports in your project, their associated sources become free and "available" for either defining new ports or reassignment to the other ports. To define a new port, click the '''Add '''button of the Port Definition dialog to open the "Add Port" dialog. On the left side of this dialog, you will see a table containing all the available sources. Select one or more ports and use the right arrow ('''--->''') button to move them to the table on the right side, labeled "Associated". These ports are now associated with the new port being defined. You can move sources from the "Associated" table back to the "Available" table on the left using the left arrow ('''<---''') button of the dialog. You can associate more than one source with the same port. In that case, you will have coupled sources, collectively representing a coupled port.RS 2 3 10
{{Note|In order to obtain correct results, the port impedance must equal the characteristic impedance of the transmission line on which the port is established. This is not done automatically in [[EM.Cube]].}}R2 3 0 50
You can change the characteristic impedance of a port by selecting it from the Port List and clicking the '''Edit '''button of the dialog. This opens up the Edit Port dialog, where you can enter a new value in the box labeled '''Impedance'''.C2 3 0 1p
===Modeling Microstrip Line Ports===----
Using simple lumped sourcesIn this case, you can simulate a variety linear voltage-controlled voltage source (E1) with a voltage gain of transmission line structures in [[EM20 has been used.Cube]]’s [[FDTD Module]] including filters, couplers or antenna feeds The input and you can calculate their scattering [[parameters]]. This approach may become less accurate at very high frequencies when the details of the feed structures become important output nodes are 1 and can no longer be modeled with highly localized lumped ports. In such cases3, it is recommended to use “Distributed Sources”, which utilize accurate modal field distributions at the ports for calculation of the incident and reflected waves. This and next two sections explain how you can use simple lumped sources to model some popular transmission line feedsrespectively.
Microstrip ports can be modeled with lumped sources placed underneath <table><tr><td> [[Image:Amp circ.png|thumb|left|420px|The schematic of the microstrip line stretching to the ground plane through the substrateamplifier circuit in RF. To build a microstrip port with a lumped source, follow these steps:Spice A/D.]] </td></tr></table>
* First, draw the PEC microstrip The same Netlist can be written using the '''Rectangle Strip Tool''' and end it at the desired port location.* Then, draw the substrate box and make sure that its extends at least &lambda;<sub>g</sub>/8 beyond than the microstrip line (&lambda;<sub>g</sub> is the guide wavelength).* If the microstrip's ground plane is the bottom of your simulation structure, set a PEC boundary for the bottom face of the computational domain. Otherwise, you do need to draw a PEC rectangle strip to represent a finite ground.* Connect the center of the microstrip’s end to the ground plane with a PEC line using the '''Line Tool'''.* Place a lumped source with 1V amplitude and zero phase on the line pointing towards the line.* In the '''Port Definition''' Dialog, set the number of ports equal to one. Associate the lumped B-type nonlinear dependent source with Port 1. Set the value of '''Port Impedance''' properly equal to the characteristic impedance of the microstrip feed line.as follows:
{{Note|If you want to model a microstrip structure with a laterally infinite substrate and a laterally infinite ground plane, make sure to set the domain offsets in the ±X, ±Y and -Z directions equal to zero.}}---
{{isoimg|FDTD50.png|A microstrip line port on a substrate terminated from the bottom by a PEC boundary plane.}}C1 1 0 1p
===Modeling Coplanar Waveguide Ports===X1 1 0 2 0 amp_dev
Using lumped sources, you can define coplanar waveguide (CPW) ports either with or without a bottom ground plane. In order to build a CPW port with a lumped source, follow these steps:subckt amp_dev 1 2 3 4
* First, draw the PEC center strip of the CPW with its two PEC coplanar ground planes, all using the '''Rectangle Strip Tool''', and end them at the desired port location.* Then, draw the substrate box and make sure that it is at least &lambda;<sub>g</sub>/8 longer than the CPW line.* Connect the two end corners of the center strip to the two side ground planes with two PEC line objects using the '''Line Tool'''.* Place a lumped source with 1V amplitude and zero phase on each line pointing towards the center strip.* In the '''Port Definition''' Dialog, set the number of ports equal to one. Associate both of the lumped sources with Port R1 1. Set the value of the '''Port Impedance''' properly equal to the characteristic impedance of the CPW feed line.2 50
[[EM.Cube]] sets the internal resistance of each of the two coupled lumped sources equal to twice the specified port B1 3 4 v = 20*v(or line1,2) impedance since the CPW port is a parallel connection of the two individual lumped sources. If you want to model a CPW with laterally infinite substrate and ground planes, make sure to set the domain offsets in the ±X and ±Y directions equal to zero. In the -Z direction, you need a nonzero offset to push the bottom CPML boundary down away outside the dielectric layer of finite thickness. Alternatively, you can terminate the bottom boundary by PEC and set its domain offset equal to zero to represent a CPW with a bottom PEC ground.
{{isoimg|FDTD51.png|A coplanar waveguide (CPW) port on a dielectric substrate.}}ends
===Modeling Coaxial Line Ports===RS 2 3 10
Coaxial line is often used to feed various RF and microwave structures. In order to excite the dominant TEM mode of a coaxial line, it has to be fed symmetrically between its inner and outer conductors. Using lumped sources, you can define symmetrical coaxial line ports. To do so, follow these steps:R2 3 0 50
* First, use the '''Cylinder Tool''' to draw a solid PEC inner conductor and end it at the desired port location.* Next, using the '''Cylinder Tool''' again, draw a hollow PEC outer conductor with the '''Cap Ends''' option unchecked, and end it at the desired port location.* Then, draw the dielectric core of the coaxial cable using the '''Cylinder Tool''' under an active dielectric material group and make sure it is at least &lambda;<sub>g</sub>/8 longer than the inner and outer conductors. Note that you only need to draw a solid dielectric cylinder rather than a hollow, pipe-like one. According to [[FDTD Module]]'s material hierarchy, the PEC core takes precedence over its enclosing dielectric cylinder.* Using the '''Line Tool''', connect the ends of the inner and outer conductors with four PEC line objects along the principal coordinate axes pointing from the inner conductor towards the outer conductor.* Place a lumped source with 1V amplitude and zero phase on each line.* In the '''Port Definition''' Dialog, set the number of ports equal to one. Associate all the four lumped sources with Port 1. Set the value of the '''Port Impedance''' properly equal to the characteristic impedance of the coaxial feed line.C2 3 0 1p
{{Note|[[EM.Cube]] will set the internal impedance of each of the four coupled lumped sources equal to four times the specified port (or line) impedance since the coaxial port is a parallel connection of the four individual lumped sources.}}----
{{isoimgNote|FDTD52.png|A coaxial line port You can use active one-ports to define custom voltage or current sources for your entire physical structure rather than using four symmetric lumped sourcesone of the physical excitation source types of the navigation tree.}}
===Lumped Loads===<table><tr><td> [[Image:Amp ex.png|thumb|left|550px|The geometry of a microstrip-based amplifier with an active two-port device.]] </td></tr></table>
In [[== EM.Cube]]Tempo's [[FDTD Module]] you can define simple lumped elements such as resistors, inductors, capacitors as well as nonlinear diodes. Although lumped loads are not sources and do not excite a structure, their properties are similar to lumped sources. Lumped Loads are incorporated into the FDTD grid across two adjacent nodes in a similar manner to lumped sources. Likewise, lumped loads are defined on Line objects. In order to create a lumped load, you must have at least one line object in your project.Observables & Simulation Data Types==
To create a new lumped load, follow these steps:=== Understanding the FDTD Observable Types ===
* Right click on the '''Lumped Loads''' item in the '''Sources''' section of the Navigation Tree and select '''Insert New Source..EM.Tempo''' to open s FDTD simulation engine calculates all the Lumped Load Dialog.* You can change the name of the lumped load as well as its color using the '''Color''' button of the dialog six electric and selecting the desired color from the color palette.* In the Lumped Element Location section of the dialogmagnetic field components (E<sub>x</sub>, you will find a list of E<sub>y</sub>, E<sub>z</sub>, H<sub>x</sub>, H<sub>y</sub> and H<sub>z</sub>) at every mesh grid node at all eligible line objects (i.e. lines that are parallel to one of time steps from t = 0 until the principal axes). Select the desired line object. The box labeled '''Direction''' shows the direction end of the lumped load with respect to the host line objecttime marching loop. Note that for a passive lumped loadHowever, the direction does not make any difference. But it matters for the case of a diode.* In the box labeled '''Offset'''in order to save memory usage, enter the distance of engine discards the lumped element temporal field data from each time step to the start point of the linenext. A lumped load by default is placed at the center of the host line. In other wordsStorage, the default offset value is equal to half the length manipulation and visualization of the host line object3D data can become overwhelming for complex structures and larger computational domains.* In the Lumped Element Properties SectionFurthermore, you can set the type calculation of the load. In the dropdown list you have four options: '''Resistor''', '''Inductor''', '''Capacitor''' and '''Diode'''. The resistance is expressed in Ohms some field characteristics such as radiation patterns or radar cross section (ORCS)can be sizable, inductance in Nanotime-Henry (nH) and capacitance in Picoconsuming, post-Farad (pF)processing tasks. In the case That is why EM.Tempo asks you to define project observables to instruct what types of a diode, output data you have to specify the '''Saturation Current''' want in femto-Ampere (fA), the ambient '''Temperature''' in Degree Kelvin and also the diode's '''Ideality Factor''', which is usually a number between 1 and 2each simulation process.
{{Note|Small values of inductance may result in the divergence of the FDTD numerical schemeEM. To avoid this problem, you need to increase Tempo offers the mesh resolution and adopt a higher mesh density. This, following types of course, may lead to a much longer computation time.}}output simulation data:
{| borderclass="0wikitable"
|-
| valign! scope="topcol"|Icon[[File:FDTD53.png|thumb! scope="col"|left|250px|]]Simulation Data Type| valign! scope="topcol"|Associated Observable Type[[File:FDTD54.png! scope="col"|thumb|left|250pxApplications! scope="col"|]]Restrictions
|-
| valignstyle="topwidth:30px;"|[[File:FDTD55fieldprobe_icon.png|thumb|left|250px|]]| valignstyle="topwidth:150px;"|Temporal Waveforms| style="width:150px;" | [[File:FDTD56Glossary of EM.pngCube's Simulation Observables & Graph Types#Temporal_Field_Probe_Observable |thumbTemporal Field Probe]]|leftstyle="width:300px;" |Computing electric and magnetic field components at a fixed location in the time domain| style="width:250px;" |]]None
|-
| style="width:30px;" | [[File:fieldprobe_icon.png]]
| style="width:150px;" | Point Fields
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Temporal_Field_Probe_Observable |Temporal Field Probe]]
| style="width:300px;" | Computing the amplitude and phase of electric and magnetic field components at a fixed location in the frequency domain
| style="width:250px;" | None
|-
| style="width:30px;" | [[File:fieldsensor_icon.png]]
| style="width:150px;" | Near-Field Distribution Maps
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Near-Field_Sensor_Observable |Near-Field Sensor]]
| style="width:300px;" | Computing the amplitude and phase of electric and magnetic field components on a planar cross section of the computational domain in the frequency domain
| style="width:250px;" | None
|-
| style="width:30px;" | [[File:fieldsensor_icon.png]]
| style="width:150px;" | Time-Domain Near-Field Animation
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Near-Field_Sensor_Observable |Near-Field Sensor]]
| style="width:300px;" | Computing either total electric or total magnetic field distribution on a planar cross section of the computational domain in the time domain
| style="width:250px;" | The field maps are generated at certain specified time intervals
|-
| style="width:30px;" | [[File:farfield_icon.png]]
| style="width:150px;" | Far-Field Radiation Patterns
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Far-Field_Radiation_Pattern_Observable |Far-Field Radiation Pattern]]
| style="width:300px;" | Computing the 3D radiation pattern in spherical coordinates
| style="width:250px;" | Requires one of these source types: lumped, distributed, microstrip, CPW, coaxial or waveguide port
|-
| style="width:30px;" | [[File:farfield_icon.png]]
| style="width:150px;" | Far-Field Radiation Characteristics
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Far-Field_Radiation_Pattern_Observable |Far-Field Radiation Pattern]]
| style="width:300px;" | Computing additional radiation characteristics such as directivity, axial ratio, side lobe levels, etc.
| style="width:250px;" | Requires one of these source types: lumped, distributed, microstrip, CPW, coaxial or waveguide port
|-
| style="width:30px;" | [[File:farfield_icon.png]]
| style="width:150px;" | Far-Field Scattering Patterns
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Far-Field_Radiation_Pattern_Observable |Far-Field Radiation Pattern]]
| style="width:300px;" | Computing the 3D scattering pattern in spherical coordinates
| style="width:250px;" | Requires a plane wave or Gaussian beam source
|-
| style="width:30px;" | [[File:rcs_icon.png]]
| style="width:150px;" | Radar Cross Section
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Radar_Cross_Section_(RCS)_Observable | RCS]]
| style="width:300px;" | Computing the bistatic and monostatic RCS of a target
| style="width:250px;" | Requires a plane wave source
|-
| style="width:30px;" | [[File:rcs_icon.png]]
| style="width:150px;" | Polarimetric Scattering Matrix Data
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Radar_Cross_Section_(RCS)_Observable | RCS]]
| style="width:300px;" | Computing the scattering matrix of a target for various plane wave source incident angles
| style="width:250px;" | Requires a plane wave source
|-
| style="width:30px;" | [[File:port_icon.png]]
| style="width:150px;" | Port Characteristics
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Port_Definition_Observable |Port Definition]]
| style="width:300px;" | Computing the S/Y/Z parameters and voltage standing wave ratio (VSWR)
| style="width:250px;" | Requires one of these source types: lumped, distributed, microstrip, CPW, coaxial or waveguide port
|-
| style="width:30px;" | [[File:port_icon.png]]
| style="width:150px;" | Port Voltages, Currents & Powers
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Port_Definition_Observable |Port Definition]]
| style="width:300px;" | Computing the port voltages, port currents and total port powers in both time and frequency domains
| style="width:250px;" | Requires one of these source types: lumped, distributed, microstrip, CPW, coaxial or waveguide port
|-
| style="width:30px;" | [[File:period_icon.png]]
| style="width:150px;" | Periodic Reflection & Transmission Coefficients
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Periodic Characteristics |Periodic Characteristics]] (No observable definition required)
| style="width:300px;" | Computing the reflection and transmission coefficients of a periodic surface
| style="width:250px;" | Requires a plane wave source and periodic boundary conditions
|-
| style="width:30px;" | [[File:energy_icon.png]]
| style="width:150px;" | Electric and Magnetic Energy
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Energy-Power_Observable | Energy-Power]]
| style="width:300px;" | Computing the electric, magnetic and total energy inside the entire computational domain in the time domain
| style="width:250px;" | None
|-
| style="width:30px;" | [[File:energy_icon.png]]
| style="width:150px;" | Dissipated Power
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Energy-Power_Observable | Energy-Power]]
| style="width:300px;" | Computing the total dissipated power inside the entire computational domain in the time domain
| style="width:250px;" | None
|-
| style="width:30px;" | [[File:energy_icon.png]]
| style="width:150px;" | Electric and Magnetic Energy Density
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Energy-Power_Observable | Energy-Power]]
| style="width:300px;" | Computing the electric, magnetic and total energy density on a field sensor plane in the frequency domain
| style="width:250px;" | Requires at least one field sensor observable
|-
| style="width:30px;" | [[File:energy_icon.png]]
| style="width:150px;" | Dissipated Power (Ohmic Loss) Density and Specific Absorption Rate (SAR) Density
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Energy-Power_Observable | Energy-Power]]
| style="width:300px;" | Computing the dissipated power density and SAR density on a field sensor plane in the frequency domain
| style="width:250px;" | Requires at least one field sensor observable
|-
| style="width:30px;" | [[File:energy_icon.png]]
| style="width:150px;" | Poynting Vector
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Energy-Power_Observable | Energy-Power]]
| style="width:300px;" | Computing the complex Poynting vector on a field sensor plane in the frequency domain
| style="width:250px;" | Requires at least one field sensor observable
|-
| style="width:30px;" | [[File:huyg_surf_icon.png]]
| style="width:150px;" | Equivalent Electric and Magnetic Surface Currents
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#Huygens_Surface_Observable |Huygens Surface]]
| style="width:300px;" | Collecting tangential field data on a box to be used later as a Huygens source in other [[EM.Cube]] modules
| style="width:250px;" | None
|-
| style="width:30px;" | [[File:CartData_icon.png]]
| style="width:150px;" | Generic 3D Cartesian Spatial Data
| style="width:150px;" | [[Glossary of EM.Cube's Simulation Observables & Graph Types#3D_Cartesian_Data_Observable | 3D Cartesian Data]]
| style="width:300px;" | Visualizing the contents of generic 3D Cartesian spatial data files overlaid on the project workspace
| style="width:250px;" | Requires import of an existing ".CAR" data file
|}
===Sources Click on each category to learn more details about it in the [[Glossary of EM.Cube's Simulation Observables & Loads For Antenna Arrays===Graph Types]].
If your project contains an array of line objects, you can also define an array of Of EM.Tempo'''Lumped Sources''' to be placed on those lines. If you insert a new lumped sources frequency domain observables, the near fields, far fields and all line array objectsof their associated parameters like directivity, if anyRCS, will be listed in the Lumped Source dialog etc., are calculated at a certain single frequency that is specified as eligible objects for lumped source placement. A lumped source will be placed on each element part of the array. All definition of the lumped sources will have identical direction and offsetobservable. HoweverTo compute those frequency domain data at several frequencies, you can prescribe certain amplitude andneed to define multiple observables, one for each frequency. On the other hand, port characteristics like S/Y/or phase distribution among Z parameters and VSWR are calculated over the array elementsentire specified bandwidth of your project. Of EM. The available '''Weight Distributions''' include '''Uniform''Tempo's source types, '''Binomial'''lumped sources, '''Chebyshev''' waveguide sources and '''Data File'''. In the last case, distributed sources let you need to set a value define one or more ports for maximum side lobe level (your physical structure and compute its port characteristics. One of EM.Tempo'''SLL''') s real advantages over frequency-domain solvers is its ability of generate wideband S/Z/Y parameter data in dB. You can also define a '''Phase Progression''' in degrees along each of the three principal axessingle simulation run.
{{isoimg|FDTD59.png|Defining lumped sources with a Chebyshev weight distribution on an array of line objects.}}=== Examining the Near Fields in Time and Frequency Domains ===
Just like lumped sourcesEM.Tempo's FDTD time marching loop computes all the six electric and magnetic field components at every Yee cell of your structure's mesh at every time step. This amounts to a formidable amount of data that is computationally very inefficient to store. Instead, you can place instruct EM.Tempo to save a small potion of these data for visualization and plotting purposes. Using a '''Lumped LoadsField Probe''' on array of line objects. These loads can be resistorsat a specified point, capacitors, inductors or nonlinear diodes. If you insert can record the a new lumped load, all line array objects, if any, will be listed in time-domain field component over the Lumped Load dialog as eligible objects for lumped load placemententire FDTD loop. A lumped load will be placed on each element of The time-domain results are also transformed to the arrayfrequency domain within the specified bandwidth using a discrete Fourier transform (DFT). All <table><tr><td> [[Image:FDTD77.png|thumb|left|480px|Time-domain evolution of the lumped load will have identical type, direction, offset and parameter valueselectric field at a given point.]]</td></tr></table>
If the project workspace contains an array of hollow box objects to model a rectangular waveguide arrayIn EM.Tempo, you can also define an array of '''Waveguide Sources''' to be placed across those waveguides. If you insert visualize the near fields at a new waveguide source, all hollow box array objects, if any, will be listed as eligible objects for waveguide source placement. A waveguide source will be placed on each element specific frequency in a specific plane of the array. All the waveguide sources will have identical direction and offsetcomputational domain. However, you can prescribe certain amplitude and/or phase distributions. The available '''Weight Functions''' include '''Uniform''', '''Binomial''', '''Chebyshev''' and '''Data File'''. In the last caseTo do so, you need to set define a value for maximum side lobe level ('''SLLField Sensor''') in dBobservable. You can also define EM.Tempo's field sensor defines a '''Phase Progression''' in degrees along each plane across the entire computational domain parallel to one of the three principal axesplanes. The magnitude and phase of all the six components of the electric and magnetic fields on the mesh grid points on the sensor plane are computed and displayed.
===Plane Waves===<table><tr><td> [[Image:FDTD_FS2.png|thumb|left|420px|EM.Tempo's Field Sensor dialog.]] </td></tr><tr><td> [[Image:FDTD_FS1_new.png|thumb|left|480px|Three field sensor planes defined around a PEC ellipsoid illuminated by a plane wave source.]] </td></tr></table><table><tr><td> [[Image:FDTD_FS3_new.png|thumb|left|360px|Electric field distribution above the PEC plate.]] </td><td> [[Image:FDTD_FS4_new.png|thumb|left|360px|Magnetic field distribution above the PEC plate.]] </td></tr></table>
[[Image:FDTD46.png|thumb|300px|[[=== Computing Far-Field Characteristics in FDTD Module]]'s Plane Wave dialog]]===
In [[EMFar fields are the asymptotic form the fields when r &rarr; &infin; or k<sub>0</sub>r >> 1.Cube]]'s [[FDTD Module]]Under these assumptions, you can excite a structure with an arbitrary incident plane wave and compute its scattering pattern or bi-static radar cross section. A plane wave excitation is defined by its propagation vector indicating the direction of incidence and its polarization. [[EM.Cube]]'s [[FDTD Module]] provides the following polarization optionsfields propagate outward as transverse electromagnetic (TEM) waves:
* TMz* TEz* Custom Linear* LCPz* RCPz<math> \mathbf{H^{ff}(r)} = \frac{1}{\eta_0} \mathbf{ \hat{k} \times E^{ff}(r)} </math>
The direction Far fields are typically computed in the spherical coordinate system as functions of incidence is defined through the elevation and azimuth observation angles &theta; and &phi; angles . Only far-zone electric fields are normally considered. When your physical structure is excited using a lumped source, a waveguide source, a distributed source, a short dipole source, or an array of such sources, the unit propagation vector in far fields represent the spherical coordinate system. The values radiation pattern of these angles are set in degrees your source(s) in the boxes labeled far zone. In that case, you need to define a '''Theta''' and '''PhiRadiation Pattern - Far Field Observable'''for your project. The default incidence angles are &theta; = 180° and &phi; = 0° representing When your physical structure is illuminated by a normally incident plane wave propagating along the -Z direction with source or a +X-polarized E-vector. You select the polarization from the five radio buttons in the "Polarization" section of the dialog. In the TM<sub>z</sub> and TE<sub>z</sub> polarization casesGaussian beam source, the magnetic and electric far fields are parallel to represent the XY plane, respectivelyscattered fields. The components of In the unit propagation vector and normalized E- and H-field vectors are displayed in the dialog. This way case of defining a plane wave source is more convenient when , you can compute the radar cross section (RCS) of your target structure is laid out along the XY plane and Z-axis such as layered and periodic structures. In the more general that case of custom linear polarization, besides the incidence angles, you have need to enter the components of the unit electric define an '''RCS - Far Field VectorObservable'''for your project. However In the FDTD method, two requirements must be satisfied: '''ê the far fields are calculated using a near-field-to-far-field transformation of the field quantities on a given closed surface. ê''' = 1 and '''ê × k''' = 0 EM. This Tempo uses rectangular boxes to define these closed surfaces. You can be enforced using the use EM.Tempo'''Validate''' button at s default radiation box or define your own custom box. Normally, the bottom of radiation box must enclose the dialogentire FDTD structure. If these conditions are not metIn this case, an error message is generatedthe calculated radiation pattern corresponds to the entire radiating structure. The left-hand (LCP) and right-hand (RCP) circular polarization cases are restricted to normal incidences Alternatively, you can define a custom radiation box that may contain only (&theta; = 180°)parts of a structure, which results in a partial radiation pattern.
Since the FDTD technique requires a finite simulation domain, it also needs a finite plane wave incidence surface to calculate the excitation<table><tr><td> [[Image:FDTD_FF1. When you create a plane wave source, a plane wave box is created as part of its definitionpng|thumb|left|720px|EM. The time domain plane wave excitation is calculated on the surface of this box and injected into the computational domainTempo's Radiation Pattern dialog. The plane wave box is displayed in the project workspace as a purple wireframe box enclosing the structure]] </td></tr><tr><td> [[Image:FDTD_FF3.png|thumb|left|600px|EM.Tempo's Radar Cross Section dialog.]] </td></tr></table>
To create a new plane wave sourceThe default radiation box is placed at an offset of 0.1&lambda;<sub>0</sub> from the largest bounding box of your physical structure. You can change the offset value from the "Far Field Acceleration" dialog, follow these steps:which can be accessed by clicking the {{key|Acceleration...}} button of EM.Tempo's Radiation Pattern dialog. Calculation of far-field characteristics at high angular resolutions can be a very time consuming computational task. You can accelerate this process by setting a lower '''Max. Far Field Sampling Rate''' from the same dialog. The default sampling rate is 30 samples per wavelength. A low sampling rate will under-sample the mesh grid points on the radiation box.
* Right click on the '''Plane Waves''' item in the '''Sources''' section of the Navigation Tree and select '''Insert New Source...''' The Plane wave Dialog opens up.<table><tr>* Initially, the radio button '''Size<td> [[Image: Default''' is selectedFDTD_FF2. With this option, the boundaries of the excitation box always have a distance of three cells from the bounding box of the geometry and cannot be changed. The radio button '''Size: Custom''' allows you to set the excitation box manually. The values for the coordinates of '''Corner 1''' and '''Corner 2''' can now be changed. Corner 1 is the front lower png|thumb|left corner and Corner 2 is the rear upper right corner of the box|480px|EM. The box has to be defined in grid coordinate system (GCS).* In the Field Definition section of the dialog, you can enter the '''Amplitude''Tempo' of the incident electric s far field in V/m and its '''Phase''' in degreesacceleration dialog. The default field Amplitude is 1 V]] </m with a zero Phase.td>* The direction of the Plane Wave is determined by the incident '''Theta''' and '''Phi''' angles in degrees. You can also set the '''Polarization''' of the plane wave and choose from the five options described earlier.</tr></table>
A plane wave box placed around === Radiation Pattern Above a PEC sphere object. The trident at the corner of the box shows the propagation vector as well as the EHalf-field and H-field polarization vectors.Space Medium ===
===Focused Gaussian Beams===In EM.Tempo, you can use CPML boundary conditions with zero offsets to model a structure with infinite lateral extents. The calculation of the far fields using the near-field-to-far-field transformation requires the dyadic Green's function of the background structure. By default, the FDTD engine uses the free space dyadic Green's function for the far field calculation. In general, the EM.Tempo provides the dyadic Green's functions for four scenarios:
[[Image:FDTD47.png|thumb|250px|[[FDTD Module]]'s Gaussian Beam dialog]]# Free space background# Free space background terminated in an infinite PEC ground plane at the bottom# Free space background terminated in an infinite PMC ground plane at the bottom# Free space background terminated in an infinite dielectric half-space medium
<table><tr><td> [[Image:FDTD133.png|thumb|left|480px|EM.CubeTempo's far field background medium dialog.]] gives you an option to illuminate objects with a focused beam instead of a uniform plane wave. The focused beam is a Gaussian beam, which is a solution of the paraxial approximation to the Helmholtz equation. The fundamental Gaussian beam is rotationally-symmetric about its propagation axis, and its transverse field distribution follows a Gaussian function profile. The critical parameter is the beam radius w<sub>0</subtd>; it is the point where the field drops by 1/e from its value at the center. The beam opens up into a cone along the propagation direction, with a cone angle of tan &theta; = &lambda;<sub>0</subtr>/(&pi;.&omega;<sub>0</subtable>) (&lambda;<sub>0</sub> is the free-space wavelength).
In other words, EM.Tempo lets you calculate the far field radiation pattern of a structure in the presence of any of the above four background structure types. You can set these choices in EM.Tempo's "Far Field Background Medium" dialog. To access this dialog, open the Radiation Pattern dialog and click the button labeled {{notekey|The beam radius has Background...}}. From this dialog, you can also set the Z-coordinate of the top of the terminating half-space medium. If you set the -Z boundary condition of your computational domain to be at least &lambda;<sub>0</sub>/&pi;; otherwisePEC or PMC types, strong fields appear outside the excitation box}}cases of infinite PEC or PMC ground planes from the above list are automatically selected, respectively, and the Z-coordinates of the ground plane and the bottom face of the computational domain will be identical.
The Gaussian beam box fourth case applies when your computational domain ends from the bottom in a dielectric layer with a CPML -Z boundary along with a -Z domain offset equal to zero. If you set the lateral domain offset values along the ±X and ±Y directions equal to zero, too, , then your structure is displayed , in effect, terminated at an infinite half-space dielectric medium. In that case, you have to specify the project workspace permittivity &epsilon;<sub>r</sub> and electric conductivity &sigma; of the terminating medium in the Background Medium dialog. You may additionally want to set the Z-coordinate of the top of that dielectric layer as a green wireframe box enclosing the structureposition of the interface between the free space and the lower dielectric half-space. To define Note that the current version of EM.Tempo does not calculate the far-field Green's function of a new Gaussian Beam sourceconductor-backed, follow these steps:dielectric substrate with a finite layer thickness. To use the background medium feature of EM.Tempo, your structure can have either an infinite PEC/PMC ground or a dielectric half-space termination.
* Right click on the '''Gaussian Beam''' item in the '''Sources''' section of the Navigation Tree and select '''Insert New Source...''' This opens up the Gaussian Beam Dialog.<table>* Similar to the plane wave, a default Excitation Box three cells away from the bounding box of the geometry is suggested, i.e. the radio button '''Size<tr><td> [[Image: Default''' is selected by defaultfdtd_out36_tn. The radio button '''Size: Custom''' allows you to set the excitation box manually by modifying the coordinates of '''Corner 1''' (front lower png|thumb|left) and '''Corner 2''' (back upper right) |360px|Radiation pattern of the box in the grid coordinate system (GCS)a vertical dipole above PEC ground.* In the Field Definition section of the dialog, you can enter the Amplitude of incident electric field in V]] </mtd><td> [[Image:fdtd_out37_tn. The default field '''Amplitude''' is 1 V/m. Note that you do not specify the phase png|thumb|left|360px|Radiation pattern of a Gaussian beam because the beam focus already contains the phase informationvertical dipole above PMC ground.* The direction of the Gaussian Beam is determined by the incident '''Theta''' and '''Phi''' angles in degrees. You can also set the '''Polarization''' of the Gaussian Beam and choose from the three options: '''TM]] <sub/td>z</subtr>''', '''TE<subtr>z</subtd>''' and '''User Defined'''[[Image:fdtd_out38_tn.* Unlike plane waves, png|thumb|left|360px|Radiation pattern of a Gaussian beam is a localized fieldhorizontal dipole above PEC ground. Therefore, you need to specify the '''Beam Properties''']] </td><td> [[Image:fdtd_out39_tn. This includes the coordinates png|thumb|left|360px|Radiation pattern of the beam's '''Focus''', which is the beam's waist center in the world coordinate system as well as the beam's '''Radius''' in project unitsa horizontal dipole above PMC ground.]] </td></tr></table>
A Gaussian beam box placed around a horizontal PEC plate. The trident at the corner of the box shows the propagation vector as well as the E-field === Generating and HWorking with Multi-field polarization vectors. The titled transparent green circle shows the footprint of Gaussian beam at its focal (waist) point.Frequency Simulation Data ===
==Running One of the primary advantages of the FDTD Simulations==method is its ability to run wideband EM simulations. The frequency domain data are computed by transforming the time-domain data to the Fourier domain. This is done automatically when EM.Tempo computes the port characteristics such as S/Z/Y parameters. The following frequency-domain observables are defined at a single frequency:
===Strategy For An Accurate & Efficient FDTD Simulation===* Near-Field Sensor* Far-field Radiation Pattern* RCS* Huygens Surface
The FDTD method is one default computation frequency of the most versatile numerical techniques for solving electromagnetic modeling problemsabove observables is the project's center frequency (fc). Choosing You can change the right settings observable frequency from the observable's property dialog and optimal values for certain numerical [[parameters]] will have a significant impact on both accuracy and computational efficiency enter any frequency in Hz. The reason these types of an FDTD simulation. Below data are computed at a number single frequency is their typically very large size. However, you can define as many instances of steps these observables and set different frequency values for each one. In the case of radiation pattern and RCS, there are two dialogs that you should typically follow by order when planning your FDTD simulation:can be accessed from the navigation tree. Right-click on the "Fer-Field Radiation Patterns" or "Radar Cross Sections" items of the navigation tree and select '''Insert Multi-Frequency Radiation Pattern...''' or '''Insert Multi-Frequency RCS...''' from the contextual menu.
* Identify material types and proper domain boundary conditions.<table>* Identify the source type and excitation mechanism.<tr>* Define the project observables<td> [[Image:RadPattern multi.* Mesh the physical structure and examine the quality of the generated mesh and it geometric fidelitypng|thumb|left|360px|EM.* Determine the proper temporal waveformTempo's Multi-frequency Radiation Pattern dialog.]] </td>* Select the simulation mode and run the FDTD engine<td> [[Image:RCS multi.png|thumb|left|360px|EM.Tempo's Multi-frequency Radar Cross Section dialog.]] </td></tr></table>
For certain problemsUsing the multi-frequency dialogs, more than one combination or choice you can set the value of settings Start Frequency, Stop Frequency and [[parameters]] may still give acceptable resultsStep Frequency in Hz. In most cases, [[EM.Cube]] tries to make these choices convenient for you by suggesting default settings or default parameter You can also set the values. For example, [[EM.Cube]] by default generated am "adaptive" type mesh with a default density of 20 cells per effective wavelengthTheta Angle Increment and Phi Angle Increment in degrees. The default computational domain features CPML walls placed a quarter free-space wavelength away from the large bounding box values of the entire physical structureboth quantities are 5&deg;. A modulated Gaussian waveform with certain optimal [[parameters]] is used to drive In the project's excitation source by default. You can change most case of these settings arbitrarily. For exampleRCS, you can set up your own computational domain with different types have choose one of boundary conditions, customize the FDTD mesh by modifying a large number of mesh settings and use other types of excitation waveformstwo options: '''Bistatic RCS''' or '''Monostatic RCS'''.
{{Note|Keep in mind that you are always responsible for To facilitate the choice process of excitation source and all the project defining multi-frequency observablesin EM. In other wordsTempo, [[EM.Cube]] does not automatically provide a default excitation source or does not suggest default observables.}}you can also use the following Python functions at the command line:
===FDTD Observable Types===----
In [[EM.Cube]], project observables are the simulation data that are generated by the simulation engine at the end of each simulation run. [[EM.Cube]]'s FDTD simulation engine calculates all the six electric and magnetic field components emag_field_sensor_multi_freq(E<sub>x</sub>f1, E<sub>y</sub>f2, E<sub>z</sub>df, H<sub>x</sub>dir_coordinate, H<sub>y</sub> and H<sub>z</sub>) at every mesh grid node at all time steps from t = 0 until the end of the time loop. Howeverx0, in order to save memory spacey0, the engine has to destroy the temporal field data from each time step to the next and reuse the memory. Storage, manipulation and visualization of 3D data can become overwhelming for complex structures and larger computational domains. Furthermore, calculation of some field characteristics such as radiation patterns or radar cross section (RCSz0) can be sizable, time-consuming, post-processing tasks. That is why [[EM.Cube]] asks you to define project observables to instruct why types of simulation data you seek in each simulation effort.
[[EM.Cube]]'s FDTD Modules currently offers the following types of observable:emag_farfield_multi_freq(f1,f2,df,theta_incr,phi_incr)
* Field Probes* Field Sensors* Domain Energy* Far Field - Radiation Patterns* Far Field - RCS* Huygens Surface Data* Port Characteristics emag_rcs_bistatic_multi_freq(S/Y/Z [[Parameters]] and VSWRf1,f2,df,theta_incr,phi_incr)* Reflection and Transmission Coefficients
Field probes monitor the field components at a certain point in the computational domain. They record the time-domain field data during the entire time loop and compute their frequency spectrum using a discrete Fourier transform. Field sensors are primarily intended for observation of near field maps on a certain cross section of the computational domain. The field sensor planes are parallel to one of the three principal XYemag_rcs_monostatic_multi_freq(f1, YZ or ZX planes. When you run a frequency sweep or parametric sweepf2, multiple maps are generated for each sample of your sweep variabledf, and you can animate these maps. You can also animate the evolution of the near fields in the time domain over the course of the simulated time loop. [[EM.Cube]] can also keep track of the electrictheta_incr, magnetic and total energy of the computational domain as functions of the time step.phi_incr)
Using asymptotic near-to-far-field transformationsemag_huygens_surface_multi_freq(f1, [[EM.Cube]] calculates the far fields of your physical structure in the standard spherical coordinate system. The radiation patterns are indeed the spherical electric field components E<sub>&theta;</sub> and E<sub>&phi;</sub> expressed as functions of the observation angles &theta; and &phi; over a unit sphere. The far field data are calculated in the frequency domain at a specified frequencyf2, which is equal to your project's center frequency by default. When your excitation source is a plane wave or a Gaussian beamdf, the far field data actually represent the scattering behavior of your "target". In the case of a plane wave sourcex1, the FDTD simulation engine can also compute the radar cross section of you target. If your structure is periodicy1, then the reflection and transmission coefficients of the periodic surface are also calculated over the entire bandwidth of your project.z1,x2,y2,z2)
You can define ports for lumped sources, waveguide sources and distributed sources. In that case, the FDTD simulation engine calculates the scattering (S) [[parameters]] of your multiport network over the entire bandwidth specified in your project. From the scattering matrix, [[EM.Cube]] determines the impedance and admittance matrices of your network over the operational bandwidth. You can plot the S/Y/Z [[parameters]] in EM.Grid. If your project has more than one port, the FDTD time loop will be run as many times as the number of ports, N. In each time loop run j (j = 1, 2, ..., N), the source(s) associated with the jth port is (are) excited with a unit amplitude and all the other sources are turned off. In this run, all the S<sub>ij</sub> parameters (i = 1, 2, ..., N) are calculated. At the end of the Nth run, the entire S matrix is completed.----
=== In the above Python functions, f1 and f2 are the start and stop frequencies, respectively, and df is the frequency increment, all expressed in Hz. Note that the above commands simply create and insert the specified observables in the navigation tree. They do not run perform a simulation. The FDTD Simulation Engine Settings ===created observables have the same "base name" with ordered numeric indices. For example, far-field radiation patterns are names as Multi_FF_1, Multi_FF_2, ...
[[Image:FDTD58EM.Tempo also provides some additional Python functions for the far-field radiation patterns and RCS observables.png|thumb|300px|[[FDTD Module]]'s Engine Settings dialog]]
An FDTD simulation involves a number of numerical [[parameters]] that can be accessed and modified from the FDTD Engine Settings Dialog. To open this dialog, select '''Menu > Simulate > Simulation Engine Settings... '''or open the '''Run Dialog''', and click the '''Settings''' button next to the engine dropdown list.----
In the " '''Convergence''' " section of the dialog, you can set the '''Termination Criterion''' for the FDTD time loop. The time loop must stop after a certain point in time. If you use a decaying waveform like a Gaussian pulse or a Modulated Gaussian pulse, after certain number of time steps, the total energy of the computational domain drops to very negligible values, and continuing the time loop thereafter would not generate any new information about your physical structure. By contrast, a sinusoidal waveform will keep pumping energy into the computational domain forever, and you have to force the simulation engine to exit the time loop. [[EM.Cube]]'s [[FDTD Module]] provides two mechanism to terminated the time loop. In the first approach, an energy-like quantity defined as U<sub>n</sub> = &Sigma; [ &epsilon;<sub>0</sub>|'''E<sub>i,n</sub>'''|<sup>2</sup> + &mu;<sub>0</sub>|'''H<sub>i,n</sub>'''|<sup>2</sup> ].&Delta;V<sub>i</sub> is calculated and recorded at a large random set of points in the computational domain. Here i is the space index and n is the time index. The quantity U<sub>n</sub> has a zero value at t = 0 emag_farfield_consolidate(i.e. n = 0)x1, and its value starts to build up over time. With a Gaussian or Modulated Gaussian pulse waveformx2, U<sub>n</sub> reach a maximum value U<sub>max</sub> at some time step and starts to decline thereafter. The ratio 10.log( U<sub>n</sub>/ U<sub>max</sub>) expressed in dB is used as the convergence criterion. When its value drops below certain '''Power Threshold'''dx, the time loop is exited. The default value of Power Threshold is -30dB, meaning that the FDTD engine will exit the time loop if the quantity U<sub>n</sub> drops to 1/1000 of its maximum value ever. The second termination criterion is simply reaching a '''Maximum Number of Time Steps''' , whose default value set to 10,000. A third option, which is [[EM.Cube]]'s default setting (labeled "'''Both'''"base_name), terminates the simulation as soon as either of the first two criteria is met first.
{{Note|Keep in mind that for highly resonant structuresemag_rcs_consolidate(x1, you may have to increase the maximum number of time steps to very large values above 20x2,000.}}dx,base_name)
The "'''Acceleration'''" section of the FDTD Simulation Engine Settings dialog give three options for the FDTD kernel:emag_farfield_explode(base_name)
# Serial CPU Solver# Multi-Core CPU Solver# GPU Solveremag_rcs_explode(base_name)
The serial CPU solver is [[EM.Cube]]'s basic FDTD kernel that run the time marching loop on a single central processing unit emag_farfield_average(CPU) of your computer. The default option is the multi-core CPU solver. This is a highly parallelized version of the FDTD kernel based on the Open-MP framework. It takes full advantage of a multi-coren, multi-CPU architecture, if your computer does have one. The GPU solver is a hardware-accelerated FDTD kernel optimized for CUDA-enabled graphical processing unit (GPUbase_name) cards. If your computer has a fast NVIDIA GPU card with enough onboard RAM, the GPU kernel can speed up your FDTD simulations up to 50 times or more over the single CPU solver.
For structures excited with a plane wave source, there are two standard FDTD formulations: '''Scattered Field '''emag_rcs_average(SF) formulation and '''Total Field - Scattered Field''' (TF-SF) formulation. [[EM.Cube]]'s [[FDTD Module|FDTD module]] offers both formulations. The TF-SF solver is the default choice and is typically much faster than the SF solver for most problems. In two casesn, when the structure has periodic boundary conditions or infinite CPML boundary conditions (zero domain offsetsbase_name), only the SF solver is available. The other sections of the FDTD Simulation Engine Settings dialog will be described next in the context of [[Waveforms and Discrete Fourier Transforms]].
===Running A Wideband FDTD Simulation===----
Once you build your physical structure The two "consolidate" Python functions take the results of multi-frequency simulation observables and merge them into a single data file. The base name in the project workspace case of far-field radiation patterns is "Multi_FF" as pointed out earlier. The name of the resulting consolidated data file is the same as the base name with a "_All" suffix and define an excitation sourcea ".DAT" file extension. In the case of far-field radiation patterns, you are ready to run an FDTD simulationit is "Multi_FF_All.DAT". The simulation engine will run even if you have not defined any observablestwo "explode" Python functions take a consolidated data file names as "base_name_All. Obviously, no simulation DAT" and break it up into several single-frequency ".RAD" or ".RCS" data will be generated files. Finally, the two "average" Python functions take several radiation pattern or RCS files with a common base name in that casethe current project folder, compute their average and save the results to a new data file named "base_name_ave" with a ". [[EMRAD" or ".RCS" file extensions, respectively.Cube]]'s [[FDTD Module]] currently offers several different simulation modes as follows:
# Analysis# Frequency Sweep# Parametric Sweep# Angular Sweep# R/T Macromodel# Dispersion Sweep# Huygens Sweep# [[Optimization]]# HDMR== Generating the FDTD Mesh in EM.Tempo ==
[[Image:FDTD57.png|thumb|250px|Figure 1: [[=== EM.Cube]]Tempo's FDTD Simulation dialog.]]Mesh Types ===
Analysis EM.Tempo generates a brick volume mesh for FDTD simulation. The FDTD mesh is a rectangular Yee mesh that extends to the simplest and most straightforward simulation mode of the [[FDTD Module]]entire computational domain. It runs is primarily constructed from three mesh grid profiles in the FDTD time marching loop onceXY, YZ and ZX principal planes. At the end These projections together create a 3D mesh space consisting of the simulation, the time-domain field data are transformed into the frequency domain using a discrete Fourier transform large number of cubic volume cells (DFTvoxels). As carefully assembled in a result, you can generate wideband frequency data from a single time-domain simulation run. The other simulation modes will be explained later in this manualway that approximates the shape of the original structure.
To open the Simulation Run DialogIn EM.Tempo, click you can choose one of the '''Run''' [[Imagethree FDTD mesh types:run_icon.png]] button of the '''Simulate Toolbar''' or select '''Menu > Simulate > Run...''' from the menu bar or use the keyboard shortcut '''Ctrl+R'''.
To start the FDTD simulation, click the '''Run''' button at the bottom of this dialog. Once the simulation starts, the "'''Output Window'''" pops up and reports messages during the different stages of the FDTD simulation. During the FDTD time marching loop, after every 10th time step, the output window updates the values of the time step, elapsed time, the engine performance in Mega* Adaptive Mesh* Regular Mesh* Fixed-cells per seconds, and the value of the convergence ratio U<sub>n</sub>/U<sub>max</sub> in dB. An [[EM.Cube]] FDTD simulation is terminated when the ratio U<sub>n</sub>/U<sub>max</sub> falls below the specified power threshold or when the maximum number of time steps is reached. You can, however, terminate the FDTD engine earlier by clicking the '''Abort Simulation''' button.Cell Mesh
{{isoimg|FDTD66EM.png|[[Tempo's default mesh generator produces an adaptive brick mesh of your physical structure, whose mesh resolution varies with the frequency. As the operating frequency of your project increases, the default '''Adaptive''' FDTD Module]]mesh generator creates a larger number of smaller voxels for a given physical structure. The adaptive mesh is optimized in such a way as to capture all the geometric details, curvatures and thin slanted plates or sheets, which often pose a challenge to staircase meshing. It usually provides a reasonably accurate discretization of most complex structures. Occasionally, you may opt for a more regularized FDTD mesh with almost equal grid line spacings everywhere, but still with a frequency-dependent cell size. In that case, you can use EM.Tempo's output window '''Regular''' FDTD mesh generator, which is indeed a simplified version of its adaptive mesh generator. The regular FDTD mesh enforces only two criteria: minimum mesh density and absolute minimum grid spacing. The grid cell sizes in this mesh are almost uniform in objects of the same material composition or in free-space regions.}}
===Waveforms EM.Tempo also offers a uniform, frequency-independent, '''Fixed-Cell''' FDTD mesh generator. The fixed-cell mesh consists of three uniform grids in the XY, YZ and ZX principal planes. However, the uniform mesh cell dimensions along the three direction, i.e. & Discrete Fourier Transforms===Delta;x, &Delta;y and &Delta;z do not have to be equal. The fixed-cell mesh generator tries to fit your physical structure to the mesh grid rather than adapting the mesh to your physical structure.
{{mainpageNote|When choosing a mesh type for your FDTD simulation, keep in mind that adaptive and regular mesh types are frequency-dependent and their density varies with the highest frequency of your specified bandwidth, while the uniform mesh type is always fixed and independent of your project's frequency settings.}} [[Waveforms and Discrete Fourier TransformsImage:Info_icon.png|30px]]}}Click here to learn more about '''[[Preparing_Physical_Structures_for_Electromagnetic_Simulation#Working_with_EM.Cube.27s_Mesh_Generators | Working with Mesh Generator]]'''.
The accuracy of the FDTD simulation results depends on [[Image:Info_icon.png|30px]] Click here to learn more about the right choice properties of temporal waveform. '''[[EMGlossary_of_EM.Cube%27s_Simulation-Related_Operations#Adaptive_Yee_Mesh | EM.Tempo's Adaptive Brick Mesh Generator]]'s default waveform choice is a modulated Gaussian pulse. At the end of an FDTD simulation, the time domain field data are transformed into the frequency domain at your specified frequency or bandwidth to produce the desired observables''.
In addition [[Image:Info_icon.png|30px]] Click here to learn more about the default waveforms, properties of '''[[EMGlossary_of_EM.Cube%27s_Simulation-Related_Operations#Fixed-Cell_Brick_Mesh |EM.CUBETempo's Fixed-Cell Brick Mesh Generator]] allows the ability to define custom waveforms by either time or frequency specifications on a per source basis'''.
Of <table><tr><td> [[FDTD ModuleImage:Tempo L11 Fig5.png|thumb|left|550px|A human head model and a cellular phone handset on its side.]]'s observables, the near fields, far fields and all of their associated </td></tr><tr><td> [[parameters]] like directivity, RCS, etcImage:Tempo L11 Fig7., are calculated at a certain frequency that is specified as part png|thumb|left|550px|The FDTD mesh of the definition of human head model and the observablecellular phone handset. On the other hand, port characteristics like S]] </Ytd></Z tr><tr><td> [[parameters]], VSWR and periodic characteristics like reflection and transmission coefficients, are calculated over Image:Tempo L11 Fig8.png|thumb|left|550px|Another view of the entire specified bandwidth FDTD mesh of your projectthe human head model and the cellular phone handset.]] </td></tr></table>
===Probing Fields in Time and Frequency DomainsDiscretizing the Physical Structure Using the Adaptive Yee Mesh ===
[[Image:FDTD75EM.png|thumb|300px|FDTD Field Probe Dialog]]By computing the time domain fields at Tempo's default mesh generator creates an adaptive brick volume mesh that uses a certain locationvariable staircase profile, you can examine where the transient response of a system at that location. This is also very useful for monitoring grid line spacings vary with the convergence curvature (derivative) of FDTD time marching loopthe object edges or faces. [[EM.Cube]]'s field probes allow you As a result, a higher mesh resolution is produced at "curved" areas to save better capture the temporal values geometrical details. The resolution of a field component at a specified point in the computational domain during adaptive FDTD mesh is driven by the entire time marching loop'''Mesh Density''', expressed in cells per effective wavelength. You can plot the Since FDTD is a time -domain field components as method and the excitation waveform may have a function of wideband spectral content, the time step index. You can also plot effective wavelength is calculated based on the spectral contents highest frequency of those field components, i.e. their Fourier transform, over the project: f<sub>max</sub> = f<sub>0</sub> + &Delta;f/2, where f<sub>0</sub> (or fc) is your project's specified center frequency and &Delta;f (or bw) is its specified bandwidth. To define In other words, the effective wavelength in the free space is &lambda;<sub>0,eff</sub> = c / f<sub>max</sub>, c being the speed of light in the free space. The effective wavelength in a new field probedielectric material with relative permittivity &epsilon;<sub>r</sub> and permeability &mu;<sub>r</sub> is given by &lambda;<sub>d, follow these steps:eff</sub> = &lambda;<sub>0,eff</sub> / &radic;&epsilon;<sub>r</sub>&mu;<sub>r</sub>.
* Right click on the '''Field Probe''' item The adaptive FDTD mesh, by default, produces different grid cell sizes in the '''Observables''' section of the Navigation Tree free space regions than inside dielectric regions. The effective wavelength in a dielectric material with relative permittivity e<sub>r</sub> and select '''Insert New Observablepermeability µ<sub>r</sub> is given by &lambda;<sub>d,eff</sub> = &lambda;<sub>0,eff</sub> / &radic;&epsilon;<sub>r</sub>&mu;<sub>r</sub>...'''* You can change Therefore, the default name average ratio of the probe as well as its color. The field probe is displayed as cell size in a small green arrow dielectric region to the cell size in the Project Workspacefree space is 1/&radic;(&epsilon;<sub>r</sub>&mu;<sub>r</sub>).* By default [[EM.Cube]] creates a field probe located at The adaptive FDTD mesh generator also takes note of the origin geometrical features of coordinates (0,0,0)the objects it discretizes. You can move This is more visible in the probe to any location by changing its Xcase of curved solids, Y curves surfaces and Z coordinatescurved wires or obliquely oriented planes and lines which need to be approximated using a staircase profile.* In The mesh resolution varies with the Probe Location section slope of the dialog, you can also set geometrical shapes and tries to capture the '''Direction''' curved segments in the best way. Another important feature of the probe from a dropdown list that contains ±Xadaptive FDTD mesher is generation of gradual grid transitions between low-density and high-density mesh regions. For example, ±Y this often happens around the interface between the free space and ±Z optionshigh permittivity dielectric objects. The default direction is +ZGradual mesh transitions provide better accuracy especially in the case of highly resonant structures.
[[ImageA carefully calculated, "<u>'''Adaptive'''</u>" mesh of your physical structure is generated in order to satisfy the following criteria:FDTD76.png|thumb|300px|An X-directed probe placed above a PEC plate illuminated by a normally incident plane wave.]]
At * Optimize the end number of mesh cells in each dimension. The product of an FDTD simulation, the electric and magnetic field components along number of cells in all the specified probe direction are saved at three dimension determines the probe's locationtotal mesh size. Both The larger the time domain fields from t = 0 to mesh size, the longer the last simulation time step and their frequency domain spectrum are recorded, especially with the CPU version of the FDTD engine. You can plot these data in EM.GridAlso, a very large mesh size requires more RAM, which can be accessed from [[EMmay exceed your GPU memory capacity.Cube]]'s Data Manager. To open data manager, click Set the '''Data ManagerMinimum Mesh Density''' [[Image:data_manager_iconto a moderately low value to keep the mesh size manageable, but be careful not to set it too low (see the next item below).png]] button * Ensure simulation accuracy by requiring an acceptable minimum number of cells per wavelength through each object and in the empty (free) space between them and the computational domain boundaries. An effective wavelength is defined for each material at the highest frequency of the project's specified spectrum. We recommend a ''Simulate Toolbar'Minimum Mesh Density '''of at least 15-20 cells/ wavelength. But for some resonant structures, 25 or select '''Simulate > Data Manager''' from even 30 cells per wavelength may be required to achieve acceptable accuracy. As you reduce the menu barmesh density, the simulation accuracy decreases.* Accurately represent and approximate the boundaries of edges or right click on surfaces that are not grid-aligned by closely adhering to their geometric contours. This is controlled by the '''Data ManagerMinimum Grid Spacing Over Geometric Contours''' item , which can be specified either as a fraction of the Navigation Tree free space grid spacing or as an absolute length value in project units.* Maximize the minimum grid spacing in any dimension inside the computational domain and select Open Data Manager.thus maximize the simulation time step.The time step size is dictated by the CFL stability criterion and is driven by the smallest grid spacing in each dimension. from The smaller the contextual menutime step, or use the keyboard shortcut larger the number of time steps required for convergence. This is controlled using the '''Ctrl+DAbsolute Minimum Grid Spacing'''. In the Data manager Dialog, you see which can be specified either as a list fraction of all the data files available for plottingfree space grid spacing or as an absolute value. These include It is critical to accurately represent and precisely maintain the time-domain object edge/surface boundaries in certain structures like resonant antennas and frequency-domain probe data files with '''.DAT''' and '''.CPX''' file extensionsfilters, respectivelyas the phase of the reflected fields/waves is affected by the object boundary positions. Select any data file When object boundaries are very close to each other, the mesh needs to represent them by clicking and highlighting its row in two separate, but very closely spaced, grid lines. To control the table and then click minimum allowed grid spacing, use the '''PlotAbsolute Minimum Grid Spacing ''' button settings,* Maintain a smooth grid with no abrupt jumps from low-density to plot the graph. The timehigh-domain field probe density regions. This feature is plotted on a Cartesian graph showing enabled with the selected field component as a function of time step. The frequency-domain probe contains two Cartesian graphs: amplitude and phase of the selected field component over the project's frequency range''Create Gradual Grid Transitions '''check box (always checked by default).
{{twoimg|FDTD77When [[EM.png|Time domain component plotted vsCube]] generates an FDTD mesh, a large number of geometrical considerations are taken into account. time|FDTD78.png|Probed These include the bounding box of each object and its corners, the ends of a line, the apex of a cone or pyramid, or the locations of lumped sources, field plotted vsprobes and sensors, vertices of plane wave or far field boxes, to name a few examples. These points are “locked” as fixed grid nodes in the FDTD mesh. [[EM.Cube]] determines these points internally to generate a mesh that best approximates the original structure. As you saw earlier, you can use the FDTD mesh settings to control the shape and resolution of the mesh, for example, around the curved portions of your structure, or on slanted lines or faces, etc. frequencyThese settings are global and apply to all the objects making up your physical structure.}}
===FrequencyYou can control the global mesh more selectively using the Advanced FDTD Mesh Settings Dialog. To open this dialog, click the '''Advanced '''button at the bottom of the FDTD Mesh Settings dialog. For example, you can control the quality of the gradual grid transitions by setting the value of '''Max Adjacent Cell Size Ratio'''. The default value of this parameter is 1.3, which maintains a smooth grid line spacing scheme with no more than 1:1.3 ratio for adjacent cells. By default, grid lines are enforced at all source and observable locations. You have the option to disable this feature and round up source locations to their closest grid lines. You may also uncheck the box labeled "Adapt mesh resolution to material properties". In that case, the same effective wavelength will be used to determine the mesh resolution inside all materials as well as the free-Domain Near Field Visualization===space regions.
<table><tr><td> [[Image:FDTD71(1)FDTD80.png|thumb|300pxleft|[[FDTD Module]]720px|EM.Tempo's Field Sensor mesh settings dialog.]]</td></tr></table>
In [[EM.Cube]] you can visualize The figures below compare the near fields at a specific frequency in a specific plane three types of the computational domain. At the end of an FDTD simulation, all the time domain electric and magnetic field values are available at all mesh nodesfor a dielectric ellipsoid with &epsilon;<sub>r</sub> = 4. These temporal quantities are transformed into Note that the frequency domain using discrete Fourier transforms to calculate cell size inside the electric and magnetic fields on a specified sensor planedielectric region is half the cell size in the air region. To define a new Field Sensor, follow these steps:
<table>
<tr>
<td>
[[Image:FDTD MAN21.png|thumb|left|360px|The geometry of a dielectric ellipsoid with &epsilon;<sub>r</sub> = 4.]]
</td>
<td>
[[Image:FDTD MAN22.png|thumb|left|360px|The adaptive mesh of the dielectric ellipsoid.]]
</td>
</tr>
</table>
* Right click on <table><tr><td> [[Image:FDTD MAN18.png|thumb|left|360px|The top view of the '''Field Sensors''' item in the '''Observables''' section adaptive FDTD mesh of the Navigation Tree and select '''Insert New Observabledielectric ellipsoid...''']]* The '''Label''' box allows you to change the sensor’s name.</td>* Set the '''Direction''' <td> [[Image:FDTD MAN19.png|thumb|left|360px|The top view of the field sensor. This is specified by the normal vector regular FDTD mesh of the sensor plane. The available options are '''X''', '''Y''' and '''Z''', dielectric ellipsoid with the last being the default optionsame mesh density.]]</td></tr><tr><td> * By default [[EMImage:FDTD MAN20A.Cube]] creates a field sensor plane passing through the origin png|thumb|left|360px|The top view of coordinates (0,0,0) and coinciding with the XY plane. Note that the sensor plane extends across the entire computational domain. You can change the location fixed-cell FDTD mesh of the sensor plane to any point by typing in new values for dielectric ellipsoid using the X, Y and Z coordinates. Keep in mind that you can move a sensor plane only along larger cell size inside the specified direction of the sensor. Therefore, only one coordinate can effectively be changed. As you increment or decrement this coordinate, you can observe the sensor plane moving along that direction in the project workspaceair region.]]* </td><td> [[Image:FDTD MAN20.png|thumb|left|360px|The frequency at which top view of the field is evaluated has to be specified in fixed-cell FDTD mesh of the box labeled '''Near Field Frequency''' in dielectric ellipsoid using the project's frequency unit. By default, this is equal to smaller cell size inside the project's center frequencydielectric region.]]</td></tr></table>
After closing The figures below compare the Field Sensor Dialog, the a new field sensor item immediately appears under the '''Observables''' section in the Navigation Tree low resolution and can be right clicked for additional editing. Once an high resolution adaptive FDTD simulation is finished, a total meshes of 14 plots are added to every Field Sensor node in the Navigation Tree. These include the magnitude and phase of all three components of E and H fields and the total electric and magnetic field values at the specified frequency. Click on any of these items and a color-coded intensity plot of it is visualized in the project workspacePEC parabolic reflector. A legend box appears in the upper right corner of the field plot, which can be dragged around using the left mouse button. The values of the magnitude plots are normalized between 0 and 1. The legend box contains the minimum field value corresponding to 0 of the color map, maximum field value corresponding to 1 of the color map, and the unit of the field quantity, which is V/m for E-field and A/m for H-field. The values of phase plots are always shown in Radians between -p and p. To display the fields properly, the This structure is cut through the field sensor plane, involves both a curved surface and only part of it is shown. If the structure still blocks your view, you can simply hide or freeze it. You can change the view of the field plot with the available view operations such as rotating, panning, zooming, etca very thin surface.
{{twoimg|FDTD72<table><tr><td> [[Image:FDTD MAN23.png|Field Sensor (E-field) thumb|FDTD74left|450px|The geometry of a PEC parabolic reflector.png|Field Sensor (H-field)}}]]</td></tr></table>
<table><tr><td> [[Image:FDTD73FDTD MAN24.png|thumb|300pxleft|Cartesian graph 360px|The low-resolution adaptive mesh of total magnetic field vsthe PEC parabolic reflector. Y]]</td><td> [[Image:FDTD MAN27.png|thumb|left|360px|The high-index along resolution adaptive mesh of the crosshair in PEC parabolic reflector.]]</td></tr><tr><td> [[Image:FDTD MAN26.png|thumb|left|360px|The top (XY) view of the low-resolution adaptive mesh of the PEC parabolic reflector.]]</td><td> [[Image:FDTD MAN25.png|thumb|left|360px|The right (YZ) view of the low-resolution adaptive mesh of the field senor planePEC parabolic reflector.]]</td></tr></table>
You can plot frequency domain fields in EM.=== Adding Fixed Grid on 2D Cartesian graphs. Using field probes, you can plot any frequency domain field component as a function of frequency over the specified bandwidth at any point within the computational domain. Using field sensors, you can plot the total frequency domain fields as a function of position (spatial coordinates) across the computational domain. Every field sensor has a crosshair made up of two perpendicular lines parallel to the boundaries of the sensor plane. When you define a field sensor for the first time, the crosshair passes through the origin of coordinates. You can change the location of the crosshair on the sensor plane using the other two coordinate boxes besides the one that moves the location of the sensor plane. At the end of an FDTD simulation, in addition to the 3D near field maps, [[EM.Cube]] also generates 2D Cartesian graphs of the total electric and magnetic fields along the two perpendicular crosshair lines. A total of four Cartesian data files are generated, two for total E-field and two for total H-field along the two lines. You can plot these data in EM.Grid, which can be accessed from [[EM.Cube]]'s Data Manager. To open data manager, click the '''Data Manager''' [[Image:data_manager_icon.png]] button of the '''Simulate Toolbar''', or select '''Simulate > Data Manager''' from the menu bar, or right click on the '''Data Manager''' item of the Navigation Tree and select Open Data Manager... from the contextual menu, or use the keyboard shortcut '''Ctrl+D'''. In the Data Manager dialog, you see a list of all the data files available for plotting including the frequency-domain sensor data files with a '''.DAT''' file extension. Select any data file by clicking and highlighting its row in the table and then click the '''Plot''' button to plot the graph. Frequency domain field sensor graphs show the total field as a function of cell index along one of the principal axes. If the FDTD mesh is uniform in that direction, the position is found by multiplying the cell index by the cell dimension and offsetting with respect Points to lower-front-left corner of the computational domain.Adaptive Yee Mesh ===
===Visualizing Field Evolution Adding fixed grid points to an FDTD mesh increases its resolution locally. Each fixed grid point adds three grid lines along the three principal axes passing through that point. You can add as many fixed grid points as you desire and create dense meshes at certain regions. Fixed grid points appear as grey points in Time Domain===the project workspace. To insert a new fixed grid point, follow these steps:
In * Open the course of the FDTD time marching process, a tremendous amount of data are generated that include all the six E/H field components at every Yee cell and at every time step. The temporal field values at a sensor plane are of particular interest. Such plots show the evolution of the fields as a function of time starting from time t = 0, when all the fields are zero everywhere in the computational domain. [[EM.Cube]] can record snapshots of the field sensor data as the time loop marches forward. When you define a field sensor for the first time, Fixed Grid Points Dialog by default it displays the frequency domain near field data. In order to record and save the time domain data, you have to open the field sensor's property dialog by right clicking on the field sensor's name in the Navigation Tree and selecting '''PropertiesMenu > Simulate > Discretization > Fixed Grid Points...'''from or by right-clicking on the contextual menu. In the section titled '''Sensor DomainFDTD''', select the radio button labeled '''Time DomainMesh'''. Also, in the section titled "Field Display - Multiple Plots", select one item of the two radio buttons labeled navigation tree and selecting '''E-Field''' or '''H-FieldFixed Grid Points Settings...'''* Click the {{key|Add/Edit}} button to open the "Add Fixed Grid Point" dialog. By default, * Enter the time domain field data are saved every 100 time steps. To change this setting(X, right click on Y, Z) coordinates of the '''Field Sensors''' item new fixed point in the Navigation Tree coordinate boxes and click the {{key|OK}} button.* To modify the coordinates of an existing fixed grid point, select '''Time Domain Settings...''' it from the contextual menutable and click the {{key|Add/Edit}} button. In * You can also remove a fix grid point from the Time Domain Settings Dialog, change FDTD mesh using the value of the box labeled '''Sampling Interval (in time steps)'''{{key|Delete}} button.
<table>
<tr>
<td> [[Image:FDTD36.png|thumb|left|480px|A user-defined fixed grid point in an FDTD mesh.]] </td>
</tr>
<tr>
<td> [[Image:FDTD38.png|thumb|left|480px|Adding a new fixed grid point in EM.Tempo's fixed grid points settings dialog.]] </td>
</tr>
<tr>
<td> [[Image:FDTD39.png|thumb|left|480px|The "Add Fixed Grid Point" dialog.]] </td>
</tr>
</table>
Time domain [[animation]] is available only for FDTD simulations of "Analysis" type. It cannot be used in conjunction with sweep simulations. Once According to the Courant-Friedrichs-Levy (CFL) stability criterion, the FDTD Analysis time step is finished, you can click any of determined by the field plots and visualize it smallest cell size in the main window or you can animate them by right clicking on the field sensoryour FDTD mesh. Occasionally, EM.Tempo's name adaptive mesh generator may create extremely tiny grid cells that would result in the Navigation Tree and selecting '''extremely small time steps. This would then translate into a very long computation time. [[AnimationEM.Cube]]''' from offers the contextual menu"Regular" FDTD mesh generator, which is a simplified version of the adaptive mesh generator. You can change In a regular FDTD mesh, the [[animation]] settings from grid cell sizes stay rather the '''[[Animation]] Controls Dialog'''same in objects of the same material composition. Note that The mesh resolution increases in materials of higher permittivity and/or permeability based on the [[animation]] loop repeats itself indefinitely until you close effective wavelength in exactly the [[Animation]] Controls dialog or hit same way as the keyboard’s '''Esc Key'''adaptive mesh.
{{twoimg|FDTD121.png|Field sensor setup for time-domain output|FDTD126.png|Time interval settings}}=== Profiling the Brick Mesh ===
===Scattering Parameters A volumetric brick mesh is overwhelming for visualization in the 3D space. For this reason, [[EM.Cube]]'s mesh view shows only the outline of the cells on exterior surface of the (staircased) meshed objects. The mesh grid planes provide a 2D profile of the mesh cells along the principal coordinate planes. To display a mesh grid plane, select '''Menu > Simulate > Discretization > Grid Planes >''' and Port Characteristics===pick one of the three options: '''XY Plane''', '''YZ Plane''' or '''ZX Plane'''. You may also right click on one of the '''XY Plane''', '''YZ Plane''' or '''ZX Plane''' items in the '''Discretization''' section of the navigation tree and select '''Show''' from the contextual menu.
If your physical structure While a mesh grid plane is excited by a Lumped Source or a Waveguide Source or a Distributed Sourcevisible, you can move it back and one or more ports have been defined, forth between the FDTD engine calculates two boundary planes at the scattering (S) [[parameters]], impedance (Z) [[parameters]] and admittance (Y) [[parameters]] two opposite sides of the selected portscomputational domain. The S [[parameters]] are calculated based on the port impedances specified You can do this in the project's "Port Definition". If more than one port has been defined in the project, the FDTD engine runs an internal port sweep. Each port is excited separately with all the other ports turned off. When the ''j''th port is excited, all the S<sub>ij</sub> [[parameters]] are calculated together based on of the following definitionfour ways:
:<math> S_* Using the keyboard's Page Up {ij{key|PgUp}} = \sqrtkey and Page Down {\frac{Re(Z_i)key|PgDn}} key.* By selecting '''Menu > Simulate > Discretization > Grid Planes > Increment Grid''' or ''' Decrement Grid'''.* By right clicking on one of the '''XY Plane''', '''YZ Plane''' or '''ZX Plane''' items in the '''Discretization''' section of the navigation tree and selecting '''Increment Grid''' or ''' Decrement Grid''' from the contextual menu.* Using the keyboard shortcut {Re(Z_j){key|>}} \cdot \fracor {V_j - Z_j^*I_j}{V_i+Z_i I_i} key|</math><!--[[Image:FDTD82(1)}}.png]]-->
where V<sub>i</sub> is As you “step through” or profile the voltage across Port imesh grid, I<sub>i</sub> is you can see how the current flowing into Port i and Z<sub>i</sub> structure is the characteristic impedance discretized along internal planes of Port i. The sweep loop then moves to the next port until all ports have been excited. After the FDTD simulation is finished, the S [[parameters]] are written into output ASCII data files. Since these data are complex, they are stored as '''.CPX''' files. Every file begins with a header starting with "#". Besides the scattering [[parameters]], the admittance (Y) and impedance (Z) [[parameters]] are also calculated and saved in complex data files with '''.CPX''' file extensionscomputational domain. The following relationships are used:
:<mathtable><tr><td>\mathbf{ [Z] = [\sqrt{Z_0}Image:Tempo L1 Fig11.png|thumb|left|360px|The XY mesh grid plane.] \cdot ([U]+</td><td> [S]) \cdot ([UImage:Tempo L1 Fig12.png|thumb|left|360px|The YZ mesh grid plane.]-[S])^{-1} \cdot [\sqrt{Z_0}] }</mathtd></tr></table>
:<math> \mathbf{ [Y] = [Z]^{-1} } </math><!--[[Image:FDTD83.png]]-->== The FDTD Grid Coordinate System (GCS) ===
where <math>\mathbf{When your physical structure is discretized using the brick mesh generator, a second coordinate system becomes available to you. The mesh grid coordinate system allows you to specify any location in the computational domain in terms of node indices on the mesh grid. [U[EM.Cube]}] displays the total number of mesh grid lines of the simulation domain (N<sub>x</mathsub> is the identity matrix of order × N, and <mathsub>\mathbf{\sqrt{Z_0}}y</mathsub> × N<sub>z</sub> is a diagonal matrix whose diagonal elements are the square roots of port characteristic impedances. The voltage standing wave ratio (VSWR) of along the structure at three principal axes on the first port is also computed and saved to a real data '''.DATStatus Bar''' file. The following definition Therefore, the number of cells in each direction is used:one less than the number of grid lines, i.e. (N<sub>x</sub>-1)× (N<sub>y</sub>-1) × (N<sub>z</sub>-1). The lower left front corner of the domain box (Xmin, Ymin, Zmin) becomes the origin of the mesh grid coordinate system (I = 0, J = 0, K = 0). The upper right back corner of the domain box (Xmax, Ymax, Zmax) therefore becomes (I = N<sub>x</sub>-1, J = N<sub>y</sub>-1, K = N<sub>z</sub>-1).
[[EM.Cube]] allows you to navigate through the mesh grid and evaluate the grid points individually. Every time you display one of the three mesh grid planes, the "'''Grid Coordinate System (GCS)'''" is automatically activated. On the Status Bar, you will see [[Image:<math> \text{VSWR} = \frac{|V_{max}|}{|V_{min}|} = \frac{1+|S_{11}|}{1-|S_{11}|} </math><!--statusgrid.png]] instead of the default [[Image:FDTD84statusworld.png]]. This means that the current coordinates reported on Status Bar are now expressed in grid coordinate system. The current grid point is displayed by a small white circle on the current mesh grid plane, and it always starts from (I = 0, J = 0, K = 0). Using the keyboard's '''Arrow Keys''', you can move the white circle through the mesh grid plane and read the current node's (I, J, K) indices on the status bar. You can switch back to the "'''World Coordinate System (WCS)'''" or change to the "'''Domain Coordinate System'''" by double-->clicking the status bar box that shows the current coordinate system and cycling through the three options. The domain coordinate system is one that establishes its origin at the lower left front corner of the computational domain and measure distances in project unit just like the WCS.
You can plot the port characteristics from the Navigation Tree. Right click on the '''Port Definition''' item in the '''Observables''' section of the Navigation Tree and select one of the items: '''Plot S [[Parameters]]''', '''Plot Y [[Parameters]]''', '''Plot Z [[Parameters]]''', or '''Plot VSWR'''. In the first three cases, another sub-menu gives a list of individual port [[parameters]]. Keep in mind that in multi-port structures, each individual port parameter has its own graph. You can also see a list of all the port characteristics data files in [[EM.Cube]]'s data manager. To open data manager, click the '''Data Manager''' <table><tr><td> [[Image:data_manager_iconFDTD35(1).png]] button of the '''Simulate Toolbar''' or select '''Simulate > Data Manager''' from the menu bar or right click |thumb|left|480px|The grid cursor on the '''Data Manager''' item of the Navigation Tree XY grid plane and select Open Data Manager... from the contextual menu or use the keyboard shortcut '''Ctrl+D'''. Select any data file by clicking and highlighting its row in the table and then click the '''Plot''' button to plot the graph in '''EM.Grid'''. By defaultgrid coordinates (I, the S [[parameters]] are plotted as dual magnitude-phase graphsJ, while K) displayed on the Y and Z [[parametersstatus bar.]] are plotted as dual real-imaginary part graphs. The VSWR data are plotted on a Cartesian graph. You change the format of complex data plots. In general complex data can be plotted in three forms:</td></tr></table>
# Magnitude and Phase# Real and Imaginary Parts# Smith Chart== Running FDTD Simulations in EM.Tempo ==
In particular, it may be useful to plot the S<sub>ii</sub> [[parameters]] on a Smith chart=== EM. To change the format of a data plot, select it and click the Tempo'''Edit '''button of Data Manager and select one of the available graph type options.<br />s Simulation Modes ===
{{twoimg|FDTD114Once you build your physical structure in the project workspace and define an excitation source, you are ready to run an FDTD simulation. The simulation engine will run even if you have not defined any observables. Obviously, no simulation data will be generated in that case.png|[[EM.CubeTempo]]'s data manager showing a list of complex data files available for plotting in EM.Grid.|FDTD115.png|Plot of S<sub>21</sub> of a filter in EM.Grid.}}currently offers several different simulation modes as follows:
===Far Field Calculations in FDTD=== {{mainpage|[[Farfield Calculations in EM.Tempo]]}} For radiating structures or scatterers, the far field quantities are of primary interest. [[EM.Cube]]'s [[FDTD Module]] can calculate the far field radiation patterns of an antenna or the radar cross section (RCS) of a target. In general, by far fields we mean the electric fields evaluated in the far zone of a physical structure, which satisfies the following condition: In the FDTD method, the far fields are calculated using a near-field-to-far-field transformation of the field quantities on a given closed surface. [[EM.Cube]] uses rectangular boxes to define these closed surfaces. You can use [[EM.Cube]]'s default radiation box or define your own. Normally, the radiation box should enclose the entire FDTD structure. In this case, the calculated radiation pattern corresponds to the entire radiating structure. The radiation box may also contain only parts of a structure, which results in partial radiation patterns. ===Defining The Far Field Box=== [[Image:FDTD116.png|thumb|250px|[[FDTD Module]]'s Radiation Pattern dialog]] For any far field calculations in [[EM.Cube]], first you have to define a far field observable in the Navigation Tree. In [[FDTD Module]], defining a far field observable also initiates a far field box in the computational domain. This box is used to perform the near-to-far-field transformation at the end of an FDTD simulation. To insert a new far field box, follow these steps: * Right click on the '''Far Fields''' item in the '''Observables''' section of the Navigation Tree and select '''Insert New Radiation Pattern...''' to open the Radiation Pattern Dialog.* Use the '''Label''' box to change the name of the far field or change the color of the far field box using the '''Color''' button.* The frequency of radiation pattern calculation can be specified in the box labeled '''Far Field Frequency'''. By default, this is equal to the center frequency of the project. However, you can calculate the far field data at any other frequency within the project's frequency range.* The resolution of far field calculations is specified by '''Angle Increment''' expressed in degrees. By default, the &theta; and &phi; angles are incremented by 5 degrees.* Define the desired box for far field calculations in the '''Radiation Box''' section of the dialog. As in the case of plane waves and Gaussian beams, there are two options available, a default radiation box (radio button '''Size: Default''') or a user defined radiation box (radio buttons '''Size: Custom'''). If you check '''Size: Default''', no radiation box corner coordinates need to be specified. The radiation box will always be 0.1 free space wavelength away from the bounding box of the entire structure. Select '''Size: Custom''' to set the far field box manually. The values for the coordinates of '''Corner 1''' and '''Corner 2''' can now be changed. '''Corner 1''' is the lower-front-left corner and '''Corner 2''' is the upper-rear-right corner of the radiation box. The dimensions are specified in the world coordinate system (WCS).* At the end of an FDTD simulation, besides calculating the radiation data over the entire (spherical) 3D space, a number of 2D pattern graphs are also generated. These are indeed pattern cuts at certain planes, which include the three principal XY, YZ and ZX planes plus one additional constant f-cut. This latter cut is at &phi; = 45° by default. You can assign another phi angle in degrees in the box labeled '''Non-Principal Phi Plane'''. Also, the 2D radiation pattern graphs are normalized by default. You can instruct [[EM.Cube]] to plot the 2D pattern graphs un-normalized (as calculated) by removing the check mark from the box labeled '''Normalize 2D Patterns'''. After closing the Far Field Dialog, a far field entry immediately appears with its given name under the '''Far Fields''' item of the '''Observables''' section in the Navigation Tree. A far field box shows up as a light blue wireframe box in the project workspace. You can right click on the far field item's name in the navigation tree and select '''Properties...''' to open up the radiation pattern dialog for further editing. Bear in mind that a full 3D radiation pattern calculation with a high angular resolution might be very time-consuming. ===Visualizing 3D Radiation Patterns=== Once an FDTD simulation is finished, three far field items are added to the Far Field section of the Navigation Tree. These are the far-zone E-field component along &phi; direction, the far-zone E-field component along &phi; direction and the total far-zone E-field defined as: :<math>|\mathbf{E_{ff,tot}}| = \sqrt{| E_{\theta}|^2 + |E_{\phi}|^2 }</math><!--[[Image:FDTD129.png]]--> The 3D plots can be viewed in the project workspace by clicking on each item. The view of the 3D far field plot can be changed with the available view operations such as rotate, pan and zoom. A legend box appears in the upper right corner of the 3D radiation pattern plot, which can be dragged around with the left mouse button. The (maximum) '''Directivity''' of the radiating structure is displayed at the bottom of the legend box and is calculated using the definition: :<math> D_0 = \frac{4\pi [S(\theta,\phi)]_{max}}{P_{rad}} = \frac{ 4\pi \big| \mathbf{E^{ff}}(\theta,\phi) \big|^2 |_{max} } { \int\limits_0^{2\pi} \int\limits_0^{\pi} \big| \mathbf{E^{ff}}(\theta,\phi) \big|^2 \sin\theta \,d\theta \,d\phi } </math><!--[[Image:FDTD113.png]]--> You can change the type of the 3D radiation pattern plot through the '''Radiation Pattern Dialog'''. In the '''3D Display Type''' section of this dialog you can choose from three options: '''3D Polar''', which is the default choice, '''Spherical Map''' and '''Cone'''. In the case of cone type, you can also set the size of the cones that are used for a vectorial visualization of the far field data. If the structure blocks the view of the radiation pattern, you can simply hide or freeze the entire physical structure or parts of it. Note that 3D radiation patterns are always positioned at the origin (0,0,0) of the spherical world coordinate system even though the radiation center of the structure may not be located at that point. Sometimes, it might be a good idea to hide the physical structure when you are viewing the 3D radiation patterns to avoid any confusion. In a 3D radiation pattern visualization, the fields are always normalized to the maximum of the total far field. For this reason, sometimes the cross-polarization component might get lost compared to the co-polarization component and you have to zoom in to make it visible. You can also change the properties of the 3D radiation pattern plot by selecting the '''Properties...''' item in the right click menu of the plot's name in the Navigation Tree or by double-clicking the legend box. This opens up the '''Output Plot Settings Dialog'''. In general, there are two scale options: Linear (which is the default option) and dB. In the case of a linear plot, the plot range varies between 0 and 1. In the case of a dB plot, the range is fixed from -50 to 0dB. You can change the '''Color Map''' option as well the foreground and background colors of the legend box. {{twoimg|fdtd_out26_tn.png|The 3D total radiation pattern of a dipole antenna: polar type.|fdtd_out28_tn.png|The 3D total radiation pattern of a dipole antenna: cone type. }} ===2D Radiation Graphs=== At the end of an FDTD simulation, the radiation pattern data E<sub>&theta;</sub>, E<sub>&phi;</sub> and E<sub>tot</sub> in the three principal XY, YZ and ZX planes plus one additional user defined phi plane cut are available for plotting on 2D graphs in '''EM.Grid'''. There are a total of eight 2D pattern graphs in the data manager: 4 polar graphs and 4 Cartesian graphs of the same pattern data. To open data manager, click the '''Data Manager''' [[Image:data_manager_icon.png]] button of the '''Simulate Toolbar''' or select '''Simulate > Data Manager''' from the menu bar or right click on the '''Data Manager''' item of the Navigation Tree and select '''Open Data Manager...''' from the contextual menu or use the keyboard shortcut '''Ctrl+D'''. In the Data manager Dialog, you will see a list of all the data files available for plotting. These include the four polar pattern data files with a '''.ANG''' file extension and the four Cartesian pattern data file with a '''.DAT''' file extension. Select any data file by highlighting its row in the table and then click the '''Plot''' button to plot the graph. At the end of an FDTD sweep simulation, other radiation characteristics are also computed as a function of the sweep variable (frequency, angle, or any other user defined variable). These include the '''Directivity (D0)''', '''Total Radiated Power (PRAD)''' and '''Directive Gain (DG)''' as a function of the &theta; and &phi; angles. Another radiation characteristic of interest especially in circularly polarized scenarios is the Axial Ratio. In [[EM.Cube]], the axial ratio is always defined in the LCP<sub>z</sub> or RCP<sub>z</sub> sense based on the X- and Y-components of the electric field. In order to calculate the directive gain or axial ratio, you have to check the boxes labeled '''Axial Ratio (AR)''' or '''Directive Gain (DG)''' in the "Additional Radiation Characteristics" section of the '''Radiation Pattern Dialog'''. Four 2D Cartesian graphs of the axial ratio as functions of the theta angle are generated in the three principal XY, YZ and ZX planes as well as the additional user defined phi plane cut. At the end of an FDTD sweep simulation, the directive gain and axial ratio can also be plotted as functions of the sweep variable. In that case, either quantity needs to be computed at a fixed pair of &theta; and &phi; angles. These angles are specified in degrees as '''User Defined Azimuth & Elevation''' in the "Output Settings" section of the '''Radiation Pattern Dialog'''. The default values of the user defined azimuth and elevation are both zero corresponding to the zenith. {| borderclass="0wikitable"
|-
! scope="col"| valignSimulation Mode! scope="topcol"|Usage[[File:FDTD119.png|thumb|left|250px! scope="col"|[[EM.Cube]]'s Data Manager dialog showing a list Number of 2D polar and Cartesian radiation pattern graphs.]]Engine Runs| valign! scope="topcol"|Frequency [[File:FDTD118.png|thumb|left|250px|A 2D Cartesian radiation pattern in the ZX plane cut.]]| valign! scope="topcol"|[[File:FDTD117.png|thumb|left|250px|A 2D Cartesian radiation pattern in the ZY plane cut.]]Restrictions
|-
| style="width:120px;" | [[#Running a Wideband FDTD Analysis | Wideband Analysis]]
| style="width:270px;" | Simulates the physical structure "As Is"
| style="width:100px;" | Single run
| style="width:200px;" | Generates data for many frequency samples
| style="width:150px;" | None
|-
| style="width:120px;" | [[Parametric_Modeling_%26_Simulation_Modes_in_EM.Cube#Running_Parametric_Sweep_Simulations_in_EM.Cube | Parametric Sweep]]
| style="width:270px;" | Varies the value(s) of one or more project variables
| style="width:100px;" | Multiple runs
| style="width:200px;" | Runs at the center frequency fc
| style="width:150px;" | None
|-
| style="width:120px;" | [[Parametric_Modeling_%26_Simulation_Modes_in_EM.Cube#Performing_Optimization_in_EM.Cube | Optimization]]
| style="width:270px;" | Optimizes the value(s) of one or more project variables to achieve a design goal
| style="width:100px;" | Multiple runs
| style="width:200px;" | Runs at the center frequency fc
| style="width:150px;" | None
|-
| style="width:120px;" | [[Parametric_Modeling_%26_Simulation_Modes_in_EM.Cube#Generating_Surrogate_Models | HDMR Sweep]]
| style="width:270px;" | Varies the value(s) of one or more project variables to generate a compact model
| style="width:100px;" | Multiple runs
| style="width:200px;" | Runs at the center frequency fc
| style="width:150px;" | None
|-
| style="width:120px;" | [[#Running a Dispersion Sweep in EM.Tempo | Dispersion Sweep]]
| style="width:270px;" | Varies the value of wavenumber in a periodic structure
| style="width:100px;" | Multiple runs
| style="width:200px;" | Runs at multiple frequency points corresponding to constant wavenumber values
| style="width:150px;" | Only for periodic structures excited by a plane wave source
|}
===Radiation Pattern Above A Half-Space MediumRunning a Wideband FDTD Analysis ===
{{mainpage|[[Radiation Pattern Above A Half Space Medium]]}}The FDTD method is one of the most versatile numerical techniques for solving electromagnetic modeling problems. Choosing the right settings and optimal values for certain numerical parameters will have a significant impact on both accuracy and computational efficiency of an FDTD simulation. Below are a number of steps that you should typically follow by order when planning your FDTD simulation:
As mentioned earlier when discussing boundary conditions * Identify material types and computational proper domain, you can use CPML boundary conditions with zero offsets to model a structure with infinite lateral extents. At * Identify the end of source type and excitation mechanism.* Define the FDTD simulation, project observables.* Mesh the far fields are calculated using physical structure and examine the near-field-to-far-field transformation. This calculation requires the dyadic Green's function quality of the background structuregenerated mesh and it geometric fidelity.* Determine the proper temporal waveform. By default, * Select the simulation mode and run the FDTD engine uses the free space dyadic Green's function for the far field calculation. In general, the [[FDTD Module]] features dyadic Green's functions for four scenarios:
# Free space background# Free space background terminated in an infinite PEC ground plane at Wideband analysis is [[EM.Tempo]]'s simplest and most straightforward simulation mode. It runs the bottom# Free space background terminated in an infinite PMC ground plane at FDTD time marching loop once. At the bottom# Free space background terminated in an infinite dielectric halfend of the simulation, the time-space mediumdomain field data are transformed into the frequency domain using a discrete Fourier transform (DFT). As a result, you can generate wideband frequency data from a single time-domain simulation run. The other simulation modes will be explained later in this manual.
===Radar Cross Section===To open the Simulation Run Dialog, click the '''Run''' [[Image:run_icon.png]] button of the '''Simulate Toolbar''' or select the menu item '''Simulate &rarr; Run...''' from the menu bar or use the keyboard shortcut {{key|Ctrl+R}}. To start the FDTD simulation, click the {{key|Run}} button at the bottom of this dialog. Once the simulation starts, the "Output Message Window" pops up and reports messages during the different stages of the FDTD simulation. During the FDTD time marching loop, after every 10th time step, the output window updates the values of the time step, elapsed time, the engine performance in Mega-cells per seconds, and the value of the convergence ratio U<sub>n</sub>/U<sub>max</sub> in dB. An [[EM.Tempo]] simulation is terminated when the ratio U<sub>n</sub>/U<sub>max</sub> falls below the specified power threshold or when the maximum number of time steps is reached. You can, however, terminate the FDTD engine earlier by clicking the '''Abort Simulation''' button.
<table><tr><td> [[Image:FDTD131Tempo L1 Fig13.png|thumb|300pxleft|[[FDTD Module480px|EM.Tempo's simulation run dialog.]]</td></tr><tr><td> [[Image:Tempo L1 Fig15.png|thumb|left|550px|EM.Tempo's RCS dialogoutput message window.]]</td></tr></table>
When the physical structure is illuminated by a plane wave source, the calculated far field data indeed represent the scattered fields. In that case, the incident and scattered fields can be separated. [[EM.Cube]] can calculate the radar cross section (RCS) of a target defined as:=== The FDTD Simulation Engine Settings ===
:<mathAn FDTD simulation involves a number of numerical parameters that can be accessed and modified from the FDTD Engine Settings Dialog. To open this dialog, select '''Menu >\sigma_{\theta} = 4\pi r^2 \dfrac{ \big| \mathbf{E}_{\theta}^{scat} \big| ^2} {\big| \mathbf{E}^{inc} \big|^2}Simulate > Simulation Engine Settings... '''or open the '''Run Dialog''', \quad \sigma_and click the {\phi} = 4\pi r^2 \dfrac{ \bigkey| \mathbf{ESettings}_{\phi}^{scat} \big| ^2} {\big| \mathbf{E}^{inc} \big|^2}, \quad \sigma = \sigma_{\theta} + \sigma_{\phi} = 4\pi r^2 \dfrac{ \big| \mathbf{E}_{tot}^{scat} \big| ^2} {\big| \mathbf{E}^{inc} \big|^2}</math><!--[[Image:FDTD130button next to the engine dropdown list.png]]-->
To compute In the RCS " '''Convergence''' " section of the dialog, you can set the '''Termination Criterion''' for the FDTD time loop. The time loop must stop after a certain point in time. If you use a decaying waveform like a Gaussian pulse or a Modulated Gaussian pulse, after certain number of time steps, the total energy of the computational domain drops to very negligible values, and continuing the time loop thereafter would not generate any new information about your physical structure. By contrast, a sinusoidal waveform will keep pumping energy into the computational domain forever, and you must define have to force the simulation engine to exit the time loop. [[EM.Tempo]] provides two mechanism to terminated the time loop. In the first approach, an RCS observable instead energy-like quantity defined as U<sub>n</sub> = &Sigma; [ &epsilon;<sub>0</sub>|'''E<sub>i,n</sub>'''|<sup>2</sup> + &mu;<sub>0</sub>|'''H<sub>i,n</sub>'''|<sup>2</sup> ].&Delta;V<sub>i</sub> is calculated and recorded at a large random set of points in the computational domain. Here i is the space index and n is the time index. The quantity U<sub>n</sub> has a radiation patternzero value at t = 0 (i.e. n = 0), and its value starts to build up over time. With a Gaussian or Modulated Gaussian pulse waveform, U<sub>n</sub> reach a maximum value U<sub>max</sub> at some time step and starts to decline thereafter. The ratio 10.log( U<sub>n</sub>/ U<sub>max</sub>) expressed in dB is used as the convergence criterion. When its value drops below certain '''Power Threshold''', the time loop is exited. The default value of Power Threshold is -30dB, meaning that the FDTD engine will exit the time loop if the quantity U<sub>n</sub> drops to 1/1000 of its maximum value ever. The second termination criterion is simply reaching a '''Maximum Number of Time Steps''' , whose default value set to 10,000. A third option, which is [[EM.Tempo]]'s default setting (labeled "'''Both'''"), terminates the simulation as soon as either of the first two criteria is met first. Follow these steps:
* Right click on the '''Far Fields''' item {{Note|Keep in the '''Observables''' section of the Navigation Tree and select '''Insert New RCS...''' to open the Radar Cross Section Dialog.* Use the '''Label''' box to change the name of the far field or change the color of the far field box using the '''Color''' button.* The frequency of RCS calculation can be specified in the box labeled '''Far Field Frequency'''. By default, this is equal to the center frequency of the project. However, you can calculate the far field data at any other frequency within the project's frequency range.* The resolution of RCS calculation is specified by '''Angle Increment''' expressed in degrees. By default, the &theta; and &phi; angles are incremented by 5 degrees.* Define the desired box mind that for far field calculations in the '''Scattering Box''' section of the dialog. As in the case of radiation patternhighly resonant structures, there are two options available, a default radiation box (radio button '''Size: Default''') or a user defined radiation box (radio buttons '''Size: Custom'''). If you check '''Size: Default''', no radiation box corner coordinates need may have to be specified. The radiation box will always be 0.1 free space wavelength away from increase the bounding box maximum number of the entire physical structure. Select '''Size: Custom''' time steps to set the far field box manually. The very large values for the coordinates of '''Corner 1''' and '''Corner 2''' can now be changed. '''Corner 1''' is the lower-front-left corner and '''Corner 2''' is the upper-rear-right corner of the radiation box. The dimensions are entered in world coordinate system (WCS).* At the end of an FDTD simulationabove 20, besides calculating the RCS data over the entire (spherical) 3D space, a number of 2D RCS graphs are also generated. These are indeed RCS cuts at certain planes, which include the three principal XY, YZ and ZX planes plus one additional constant &phi;-cut. This latter cut is at &phi; = 45° by default. You can assign another &phi; angle in degrees in the box labeled '''Non-Principal Phi Plane'''000.}}
The "'''Acceleration'''" section of the FDTD Simulation Engine Settings dialog give three options for the FDTD kernel:
[[Image:FDTD132.png|thumb|300px|An example of the 3D radar cross section of a PEC plate.]]# Serial CPU Solver# Multi-Core CPU Solver# GPU Solver
At the end of an The serial CPU solver is [[EM.Tempo]]'s basic FDTD simulation, in kernel that run the far field section of the Navigation Tree, you will have the &theta; and &phi; components of RCS as well as the total radar cross section: &sigma;<sub>&theta;</sub>, &sigma;<sub>&phi;</sub>, and &sigma;<sub>tot</sub>. You can view time marching loop on a 3D visualization of these quantities by clicking on their entries in the Navigation Tree. The RCS values single central processing unit (&sigma;CPU) are expressed in m<sup>2</sup>of your computer. The 3D plots are normalized to the maximum RCS value, which default option is displayed in the legend boxmulti-core CPU solver. The 2D RCS graphs can be plotted in '''EM.Grid '''exactly in This is a highly parallelized version of the same way that you plot 2D radiation pattern graphsFDTD kernel based on the Open-MP framework. A total It takes full advantage of eight 2D RCS graphs are available: 4 polar and 4 Cartesian graphs for the XYa multi-core, YZmulti-CPU architecture, ZX and user defined plane cutsif your computer does have one. at the end of The GPU solver is a sweep simulation, [[EM.Cube]] calculates some other quantities including the backscatter RCS (BRCS), forwardhardware-scatter RCS accelerated FDTD kernel optimized for CUDA-enabled graphical processing unit (FRCS) and the maximum RCS (MRCS) as functions of the sweep variable (frequency, angle, or any user defined variableGPU)cards. In this caseIf your computer has a fast NVIDIA GPU card with enough onboard RAM, the RCS needs to be computed at a fixed pair of &phi; and &theta; angles. These angles are specified in degrees as '''User Defined Azimuth & Elevation''' in the "Output Settings" section of the '''Radar Cross Section Dialog'''. The default values of the user defined azimuth and elevation are both zero corresponding GPU kernel can speed up your FDTD simulations up to 50 times or more over the zenithsingle CPU solver.
{{Note|Unlike For structures excited with a plane wave source, there are two standard FDTD formulations: '''Scattered Field '''(SF) formulation and '''Total Field - Scattered Field''' (TF-SF) formulation. [[EM.CubeTempo]]'s Planar, MoM3D and Physical Optics Modules, the [[FDTD Module]] currently does not support 3D monooffers both formulations. The TF-static RCS calculation due to SF solver is the enormous amount of computational work neededdefault choice and is typically much faster than the SF solver for most problems. Only In two cases, when the bi-static RCS structure has periodic boundary conditions or infinite CPML boundary conditions (zero domain offsets), only the SF solver is calculated for a given plane wave sourceavailable.}}
===Angular Sweeps===<table>If your FDTD project has a plane wave excitation, then you can also run an angular sweep<tr><td> [[Image:FDTD58. In this sweep, the values of the incidence angles &theta; and &phi; are varied at each sweep runpng|thumb|left|720px|EM. To run an angular sweep, open the FDTD Tempo'''Run Dialog''' and from the '''Simulation Mode '''dropdown list select the '''Angular Sweep''' option. Click the '''Settings''' button next to this dropdown list to open up the Angle Settings Dialog. In an angular sweep, only one of the two angles, &theta; and &phi;, can be varied at a time. Choose the radio button corresponding to the angle that you want to sweep. Then, set the values of the '''Start Angle''' and '''End Angle''' as well as the '''Number of Samples'''. Under normal circumstances, you would sweep &theta; from 180°to 90° backward and sweep &phi; from zero to 360° forwards simulation engine settings dialog.]]</td></tr><br /table>
{{isoimg|FDTD128==Modeling 3D Periodic Structures in EM.png|[[FDTD Module]]'s Angle Settings dialog.}}Tempo==
===Defining Custom Output Parameters===[[EM.Tempo]] allows you to simulate doubly periodic structures with periodicities along the X and Y directions. In the FDTD method, this is accomplished by applying periodic boundary conditions (PBC) at the side walls of the computational domain.
{{mainpageNote|Custom Output[[EM.Tempo]] can only handle regular, non-skewed periodic lattices with no secondary offsets.}} [[Image:Info_icon.png|30px]] Click here to learn more about the theory of '''[[Basic_Principles_of_The_Finite_Difference_Time_Domain_Method#Time_Domain_Simulation_of_Periodic_Structures | Time Domain Simulation of Periodic Structures]]'''.
At the end of an FDTD simulation, ===Defining a number of computed quantities are designated as "Standard Output" [[parameters]] and can be used for various post-processing data operations. For example, you can define design objectives based on them, which you need for [[optimization]]. The table below gives a list of all the currently available standard output [[parameters]] Periodic Structure in [[EM.Cube]]'s [[FDTD Module]]:Tempo===
{| class="wikitable"!scope="col"| Standard Output Name / Syntax!scope="col"| Description|-| SijM| Magnitude of (iBy default,j)-th Scattering Parameter|-| SijP| Phase of (i,j)-th Scattering Parameter (in radians)|-| SijR| Real Part of (i,j)-th Scattering Parameter|-| SijI| Imaginary Part of (i,j)-th Scattering Parameter|-| ZijM| Magnitude of (i,j)-th Impedance Parameter|-| ZijP| Phase of (i,j)-th Impedance Parameter (in radians)|-| ZijR| Real Part of (i,j)-th Impedance Parameter|-| ZijI| Imaginary Part of (i,j)-th Impedance Parameter|-| YijM| Magnitude of (i,j)-th Admittance Parameter|-| YijP| Phase of (i,j)-th Admittance Parameter (in radians)|-| YijR| Real Part of (i,j)-th Admittance Parameter|-| YijI| Imaginary Part of (i,j)-th Admittance Parameter|-| VSWR| Voltage Standing Wave Ratio|-| D0| Directivity|-| PRAD| Total Radiated Power|-| THM| Main Beam Theta|-| PHM| Main Beam Phi|-| DGU| Directive Gain along User Defined Direction|-| ARU| Axial Ratio along User Defined Direction|-| FBR| Front-to-Back Ratio|-| HPBWXY| Half Power Beam Width in XY Plane|-| HPBWYZ| Half Power Beam Width in YZ Plane|-| HPBWZX| Half Power Beam Width in ZX Plane|-| HPBWU| Half Power Beam Width in User Defined Plane|-| SLLXY| Maximum Side Lobe Level in XY Plane|-| SLLYZ| Maximum Side Lobe Level in YZ Plane|-| SLLZX| Maximum Side Lobe Level in ZX Plane|-| SLLU| Maximum Side Lobe Level in User Defined Plane|-| FNBXY| First Null Beam Width in XY Plane|-| FNBYZ| First Null Beam Width in YZ Plane|-| FNBZX| First Null Beam Width in ZX Plane|-| FNBU| First Null Beam Width in User Defined Plane|-| FNLXY| First Null Level in XY Plane|-| FNLYZ| First Null Level in YZ Plane|-| FNLZX| First Null Level in ZX Plane|-| FNLU| First Null Level in User Defined Plane|-| BRCS| Back-Scatter RCS|-| FRCS| Forward-Scatter RCS along User Defined Incident Direction|-| MRCS| Maximum Bi-static RCS|-| RCM| Magnitude of Reflection Coefficient|-| RCI| Phase of Reflection Coefficient (in radians)|-| RCR| Real Part of Reflection Coefficient|-| RCI| Imaginary Part of Reflection Coefficient|-| TCM| Magnitude of Transmission Coefficient|-| TCP| Phase of Transmission Coefficient (in radians)|-| TCR| Real Part of Transmission Coefficient|-| TCI| Imaginary Part of Transmission Coefficient|} All the radiation- and scattering-related standard outputs are available only if you have defined a radiation pattern far field observable or an RCS far field observable, respectively. The standard output [[parameters]] DGU and ARU are the directive gain and axial ratio calculated at the certain user defined direction with spherical observation angles (&theta;, &phi;). These angles are specified in degrees as '''User Defined Azimuth & Elevation''' in the "Output Settings" section of the '''Radiation Pattern Dialog'''. The standard output [[parameters]] HPBWU, SLLU, FNBU and FNLU are determined at a user defined f-plane cut. This azimuth angle is specified in degrees as '''Non-Principal Phi Plane''' in the "Output Settings" section of the '''Radiation Pattern Dialog''', and its default value is 45°. The standard output [[parameters]] BRCS and MRCS are the total back-scatter RCS and the maximum total RCS of your planar physical structure when it is excited by an incident plane wave source at the specified &theta;<sub>s</sub> and &phi;<sub>s</sub> source angles. FRCS, on the other hand, is the total forward-scatter RCS measured at the predetermined &theta;<sub>o</sub> and &phi;<sub>o</sub> observation angles. These angles are specified in degrees as '''User Defined Azimuth & Elevation''' in the "Output Settings" section of the '''Radar Cross Section Dialog'''. The default values of the user defined azimuth and elevation are both zero corresponding to the zenith. ===3D Near & Far Field Animation=== [[Image:FDTD123.png|thumb|250px|[[Animation]] of total E-field plots and far field radiation patterns at the end of an FDTD sweep simulation]] At the end of a sweep simulation (a frequency sweep, angular sweep, parametric sweep, etc.), if you have defined a field sensor or a far field observable (either radiation pattern or RCS) in your project, a number of near field plots or far field plots are generated for all samples of the sweep variable. Each field sensor normally has 14 field maps for the amplitude and phase of all the three components of E- and H-fields plus the magnitude of the total fields. Each far field observable has three spherical plots corresponding to the &theta; and &phi; components of the far field and the total far field. Generating all these 14 near-field intensity plots or 3 far-field spherical plots at each sweep sample would result in a very large number of graphs on the Navigation Tree. Instead, during a sweep simulation, [[EM.Cube]] generates either a total E-field or a total H-field plot at each sweep run for the field sensors. By default, the total E-field plots are saved. You can change this setting from the field sensor's property dialog. Right click on the field sensor's name in the Navigation Tree and select '''Properties...'''from the contextual menu. In the section titled "Field Display - Multiple Plots", select one of the two radio buttons labeled '''E-Field''' or '''H-Field'''. As for far field observables, only the total field plot is generated at each sweep sample. Once the sweep simulation is finished, you can click any of the near-field or far-field plots and visualize it in the main window. You can also animate these field plots. [[Animation]] in [[EM.Cube]] consists of sequential display of the plots in the main window at a preset speed. To animate the field sensor plots, right click on the field sensor's name in the Navigation Tree and select '''[[Animation]]''' from the contextual menu. The field plots start to animate beginning with the first sample, going through all the plots one by one until the last one and repeating the loop all over again. While the [[animation]] proceeds in the main window, a dialog titled '''[[Animation]] Controls Dialog''' pops up at the lower right corner of the screen. You can drag this dialog anywhere in the project workspace from its title bar. The controls dialog shows the title of each graph as it is reviewed. You can set the speed of [[animation]] by typing in a value for '''Rate''', which is indeed the frame duration expressed in multiples of 100 milliseconds. The default frame duration is 300 msec. You can pause the [[animation]] and resume at any time. You can rewind to the first sample or skip to the last sample. You can also step through the samples one at a time using the increment (forward) or decrement (backward) buttons. To stop [[animation]] at any time, use the keyboard's '''Esc Key''' or click the '''Close (X)''' button of the [[animation]] controls dialog. {{twoimg|FDTD120.png|Selecting the field type for plotting at the end of an FDTD sweep simulation.|FDTD122.png|[[EM.Cube]]'s [[Animation]] Controls dialog.}} ==Modeling 3D Periodic Structures Using FDTD== EM.Tempo allows you to simulate doubly periodic structures with periodicities along the X and Y directions. Many interesting structures such as frequency selective surfaces (FSS), electromagnetic band-gap (EBG) structures and metamaterial structures can be modeled using periodic geometries. In the case of an infinitely extended periodic structure, it is sufficient to analyze only a unit cell. In the FDTD method, this is accomplished by applying periodic boundary conditions (PBC) at the side walls of the computational domain.  Click here to learn more about [[Time Domain Simulation of Periodic Structures]]. ===Setting Up A Periodic Unit Cell=== Using [[EM.Cube]]'s [[FDTD Module]], you can simulate complex 3D periodic structures. A periodic structure is one that repeats itself infinitely along one, two or three directions. In this release of [[EM.Cube]]'s [[FDTD Module]], the periodicity is limited to the X-Y plane. In other words, the periodic structure repeats itself along the X- and Y-axes, but not along the Z-axis. By default, your physical structure is not periodic, and you have to instruct [[EM.CubeTempo]] to turn it into a periodic structure through [[FDTD Module]]'s using its Periodicity Dialog. By designating a structure as periodic, you enforce periodic boundary conditions (PBC) on the side walls of its computational domain. Your structure in the project workspace then turns into a periodic unit cell. The periodic side walls are displayed with dashed blues lines. [[Image:FDTD134.png|250px|thumb|[[FDTD Module]]'s Periodicity Settings dialog]]
To define a periodic structure, follow these steps:
* Periodic boundary conditions (PBC) are established on the ±X and ±Y faces of the domain box. You still have to designate the boundary conditions on the ±Z faces of the computational domain. These are CPML by default. But you can change them to PEC or PMC.
===Exciting A Periodic Structure As An Infinite Phased Array===<table><tr><td> [[Image:FDTD134.png|thumb|360px|EM.Tempo's periodicity settings dialog.]]</td></tr></table>
In [[===Exciting Periodic Structures as Radiators in EM.Cube]]'s [[FDTD Module]], a periodic structure can be excited using various source types. Exciting the unit cell structure using a lumped source, a waveguide source, an ideal source or a distributed source, you can model an infinite periodic antenna array. For most practical antenna types, you will excite your periodic structure with a lumped source or waveguide source. In this case, you can define a port for the lumped source or waveguide source and calculate the S<sub>11</sub> parameter or input impedance of the periodic antenna array. You can also compute the near-field and far-field data.Tempo===
In [[EM.CubeTempo]]'s , a periodic FDTD simulator uses periodic boundary conditions (PBC) to model an infinite periodic arraystructure can be excited using various source types. All the periodic replicas of Exciting the unit cell structure are excited. In this case, you can impose using a phase progression across the infinite array to steer its beam. You can do this from the property dialog of the lumped source or , a waveguide source. At the bottom of the '''Lumped Source Dialog''' , or '''Waveguide Source Dialog''', there is a section titled '''Periodic Beam Scan Angles'''. This section is grayed out when the project structure is not periodic. You can enter desired beam scan angle values for both '''Theta''' and '''Phi''' in degrees. At the end of the periodic FDTD simulationdistributed source, the radiation pattern of the unit cell is calculated and stored in a radiation data file with a '''.RAD''' file extension. The 3D radiation patterns that you normally visualize in [[EM.Cube]], in this case, correspond to the single unit cell, not the can model an infinite periodic antenna array. Therefore, they do not show the beam scanning even if you have entered nonzero values for the &theta; and/or &phi; scan angles. For this purposemost practical antenna types, you have to define excite your periodic structure with a finite-sized array factorlumped source or waveguide source. You do In this in the "Impose Array Factor" section of the '''Radiation Pattern Dialog'''. In the case of a periodic structure, when you can define a new far field item in port for the Navigation Tree, the values of element spacing along the X lumped source or waveguide source and Y directions are automatically set equal to calculate the values S<sub>11</sub> parameter or input impedance of the periodic lattice spacing along those directionsantenna array. Set the number of elements along the X and Y directions to any desired values. [[EM.Cube]] will then You can also compute the radiation pattern of the specified finitenear-sized periodic array, field and the beam scanning will appear in the radiation pattern plots, if anyfar-field data.
{{Note|For large &theta; scan angles[[EM.Tempo]]'s periodic FDTD simulator uses periodic boundary conditions (PBC) to model an infinite periodic array. All the periodic replicas of the unit cell structure are excited. In this case, you can impose a phase progression across the infinite array to steer its beam. You can do this from the property dialog of the lumped source or waveguide source. At the bottom of the '''Lumped Source Dialog''' or '''Waveguide Source Dialog''', there is a section titled '''Periodic Beam Scan Angles'''. This section is grayed out when the project structure is not periodic FDTD time matching loop may take far more time steps . You can enter desired beam scan angle values for both '''Theta''' and '''Phi''' in degrees. To visualize the radiation pattern of the beam-steered array, you have to convergedefine a finite-sized array factor. You do this in the "Impose Array Factor" section of the '''Radiation Pattern Dialog'''.}}
{{twoimgNote|FDTD137.png|Setting periodic For large &theta; scan angles in , the lumped source dialog|FDTD138.png| Setting the array factor in radiation pattern dialogperiodic FDTD time marching loop may take far more time steps to converge.}}
{{twoimg|FDTD135<table><tr><td> [[Image:Period1.png|Radiation pattern of a 8×8 finite-sized periodic dipole array with scan angles with phi and theta equal to 0 degrees.thumb|FDTD136.png350px| Radiation pattern of a 8×8 finite-sized Setting periodic dipole array with scan angles theta equal to 45 degrees, and phi equal to 0 degreesin EM.Tempo's Lumped Source dialog.}}]] </td></tr></tr></table>
===Analyzing Antenna Arrays===<table><tr><tr><td> [[Image:Period2.png|thumb|720px|Setting the array factor in EM.Tempo's Radiation Pattern dialog.]] </td></tr></table>
Real antenna arrays have finite extents, that is, finite numbers of elements along the X and Y directions. Earlier, you saw how to excite an array of line objects using an array of lumped sources or an array of rectangular waveguides (hollow boxes) using an array of waveguide sources. Setting up array structures of this kind using <table><tr><td> [[EMImage:Period3.Cube]]'s '''Array Tool '''and exciting the individual elements using individual lumped or waveguide sources results in png|thumb|360px|Radiation pattern of an accurate full-wave analysis of your antenna array. This type of simulation takes into account all the inter-element coupling effects as well as the finite edge and corner effects of the 8×8 finite-sized periodic wire dipole array. At the end of the FDTD simulation of your antenna array, you can plot the radiation patterns with 0&deg; phi and other far field characteristics of the array just like any other FDTD structuretheta scan angles. However, depending on the total size ]] </td><td> [[Image:Period4.png|thumb|360px|Radiation pattern of your array, a fullbeam-wave simulation like this may easily lead to a very large computational problem. As the number of elements grow very large, the array starts to look like an infinite periodic structure. In that case, it is possible to consider and analyze a periodic unit cell of the array structure and use an "Array Factor" representing the steered 8×8 finite-extent topology of the sized periodic wire dipole array grid to calculate the radiation pattern of your antenna array. This approach works well for most large arrays. However, it ignores the finite edge with 45&deg; phi and corner effects, which may be important for certain array architecturestheta scan angles. In that case we recommend that you use [[EM.Cube]]'s [[Planar Module]]. Also, note that using an array factor for far field calculations, you cannot assign non-uniform amplitude or phase distributions to the array elements. For this purpose, you have to define an array object.</td></tr></table>
[[Image:FDTD146(1).png|thumb|250px|Defining additional radiation characteristics ===Exciting Periodic Structures Using Plane Waves in [[FDTD Module]]'s Radiation Pattern dialogEM.]]Tempo===
In the previous section, you saw how Using a plane wave source to excite a periodic unit cell using a lumped source or a waveguide sourcestructure in [[EM. You Tempo]], you can specify model frequency selective surfaces, electromagnetic band-gap (EBG) structures, metamaterials, etc. Exciting periodic structures with plane wave sources requires careful attention. [[EM.Tempo]]'s FDTD simulation engine uses the beam scan angles in the source dialogsdirect spectral domain FDTD or constant transverse wavenumber method for analyzing periodic structures. The finite array factor is defined in In this technique, instead of a plane wave box, one defines a plane wave surface parallel to the radiation pattern dialogX-Y plane. At the end of the periodic FDTD simulationof a periodic structure with plane wave excitation, you can visualize the 3D radiation patterns in the project workspace reflection and plot the 2D Cartesian and polar pattern graphs in EM.Grid. [[EM.Cube]] also calculates the '''Directive Gain (DG)''' as a function transmission coefficients of the &theta; structure are calculated and &phi; anglessaved into ASCII data files. This is defined as:
<mathtable><tr><td>D(\theta,\phi) = \dfrac{4\pi [S(\theta,\phi)[Image:Period11.png|thumb|380px|Geometry of a periodic printed strip FSS in EM.Tempo.]}{P_{rad}} = ] </td>\dfrac{4\pi \big<td> [[Image:Period12.png| \mathbf{E}^{ff}(\theta,\phi) \bigthumb|^2} {\int\limits_0^{2\pi} \int\limits_0^{\pi} \big340px| \mathbf{E}^{ff}(\theta,\phi) \big|^2 \sin\theta \, d\theta \, d\phi}Define a custom periodic plane wave box in EM.Tempo.]] </td></tr></mathtable>
The directivity D<sub>0</sub> is the maximum value of the directive gain. [[EM.Cube]] generates four Cartesian graphs of directive gain in the three principal XY, YZ, ZX planes as well as in the user defined f-plane cut. The radiation patterns of antenna arrays usually have a main beam and several side lobes. Some [[parameters]] of interest in such structures include the '''Half Power Beam Width (HPBW)''', '''Maximum Side Lobe Level (SLL)''' and '''First Null [[Parameters]]''' (i.e. first null level and first null beam width). You can have [[EM.Cube]] calculate all such [[parameters]] if you check the relevant boxes in the "Additional Radiation Characteristics" section of the '''Radiation Pattern Dialog'''. These quantities are saved into ASCII data files of similar names with '''.DAT''' file extensions. You can plot graphs of such data files at the end of a sweep simulation in''' '''EM.Grid. You can also plot the directive gain as a function of the sweep variable at the end of an FDTD sweep simulation. In that case, the directive gain is computed at a fixed pair of &theta; and &phi; angles. These angles are specified in degrees as '''User Defined Azimuth & Elevation''' in the "Output Settings" section of the Radiation Pattern dialog. The default values of the user defined azimuth and elevation are both zero corresponding to the zenith. The results are saved to an ASCII data file called "DGU.DAT". Note that DGU is also one of [[EM.Cube]]'s standard output [[parameters]] and can be used to define custom output or design objectives. ===Exciting A Periodic Surface With A Plane Wave=== Using a plane wave source to excite a periodic structure in [[EM.Cube]]'s [[FDTD ModuleTempo]], you can model frequency selective surfaces, electromagnetic band-gap (EBG) structures, metamaterials, etc. Exciting periodic structures with plane wave sources requires careful attention. [[EM.CubeTempo]]'s FDTD simulation engine uses the direct spectral domain FDTD or constant transverse wavenumber method for analyzing periodic structures. In this technique, instead of a plane wave box, one defines a plane wave surface parallel to the X-Y plane. If the plane wave source illuminates the periodic unit cell from the top (90&deg; < &theta; < 180&deg;), the excitation surface is placed above the structure's bounding box. If the plane wave source illuminates the periodic unit cell from the bottom up (0&deg; < &theta; < 90&deg;), the excitation surface is placed below the structure's bounding box. In either case, the plane wave must intercept the excitation surface before hitting the unit cell's physical structure. It is highly recommended that you accept [[EM.CubeTempo]]'s default settings for the plane wave box of periodic structures. Nevertheless, you can change the location of the excitation surface if you wish. To do so, you have to open the '''Plane Wave Dialog'''. In the Excitation Box section of the dialog, select the '''Size: Custom''' option. Only the '''Z Coordinate''' of '''Corner 1''' is available for editing. The rest of the coordinates are enforced by the periodic domain. You can enter the incidence angles '''Theta''' and '''Phi''' in degrees. For periodic structures, only the '''TM<sub>z</sub>''' and '''TE<sub>z</sub>''' polarization options are available.
One of the pitfalls of the direct spectral FDTD method is the possibility of horizontal resonances, which may lead to indefinite oscillation or even divergence of field values during the time marching loop. This happens in the case of oblique plane wave incidence when &theta; > 0&deg;. [[EM.Cube]]'s FDTD engine automatically detects such cases and avoids those resonances by shifting the modulation frequency of the modulated Gaussian pulse waveform away from the resonant frequency. However, in some cases, the size of oscillations may still remain large after a large number of time steps. Occasionally, a late-time diverging behavior may appear. To avoid situations like these, it is highly recommended that you place a time-domain field probe above your structure and monitor the temporal field behavior during the time marching loop as shown in the figure below.
 
{{twoimg|FDTD140(1).png|Setting a custom plane wave source plane|FDTD139.png|Plane Wave visualization in the scene.}}
 
===Reflection & Transmission Characteristics===
 
At the end of the FDTD simulation of a periodic structure with plane wave excitation, the reflection and transmission coefficients of the structure are calculated and saved into two complex data files with '''.CPX''' file extensions. These coefficients behave like the S<sub>11</sub> and S<sub>21</sub> [[parameters]] of a two-port network. You can think of the upper half-space as Port 1 and the lower half-space as Port 2 of this network. The reflection and transmission (R/T) coefficients can be plotted on 2D graphs in '''EM.Grid '''similar to the scattering [[parameters]]. You can plot them from the Navigation Tree. To do so, right click on the '''Periodic Characteristics''' item in the '''Observables''' section of the Navigation Tree and select '''Plot Reflection Coefficients''' or '''Plot Transmission Coefficients'''. The complex data files are also listed in [[EM.Cube]]'s data manager. To open data manager, click the '''Data Manager''' [[Image:data_manager_icon.png]] button of the '''Simulate Toolbar''' or select '''Simulate > Data Manager''' from the menu bar or right click on the '''Data Manager''' item of the Navigation Tree and select Open Data Manager... from the contextual menu or use the keyboard shortcut '''Ctrl+D'''. Select any data file by selecting its row in the table and then click the '''Plot''' button to plot the graph in EM.Grid.
{{Note|It is very important to keep in mind that only in the case of normal incidence does [[EM.Cube]] compute the reflection and transmission coefficients over the entire specified bandwidth of the project. At oblique incidences when &theta; > 0, the computed R/T coefficients after the discrete Fourier transformation are valid only at the center frequency of the project for the given value of the incident &theta;<sub>0</sub> angle. In other words, the computed R/T coefficients at all the other frequencies away from the center frequency correspond to different values of the incident &theta; angle. As a result, [[EM.Cube]] only saves the reflection and transmission coefficients at the center frequency into the output data files "reflection_coefficient.CPX" and "transmission_coefficient.CPX".}}
{| border="0"|-| valign="top"|[[File:FDTD141.png|400px|thumb|Magnitude and Phase of reflection coefficient from a periodic surface plotted vs. frequency.]]| valign="bottom"|[[File:FDTD142.png|400px|thumb|Magnitude and Phase of transmission coefficient from Running a periodic surface plotted vsDispersion Sweep in EM. frequency.]]|-|} Tempo ===Periodic FDTD Simulation Types===  [[File:FDTD143.png|thumb|200px|[ R/T Macromodel Settings Dialog.]]
Besides analyzing a periodic structure in a single-run simulation, [[EM.Cube]]'s [[FDTD Module]] offers a number of sweep simulations for periodic structures. These include '''Frequency Sweep''', '''Angular Sweep''', '''R/T Macromodel Sweep '''and The '''Dispersion Sweep'''. These options are available from option of the '''Simulation Mode''' dropdown drop-down list performs a sweep of constant k<sub>l</sub> wavenumber values. This is a specialized sweep for the constant transverse wavenumber method that [[FDTD ModuleEM.Tempo]]'s '''Run Dialog'''uses to model periodic structures illuminated by a plane wave source. Of theseThe real advantage of a dispersion sweep is that through a one-dimensional sweep of k<sub>li</sub>, you can find the reflection and transmission coefficients for all combinations of frequency sweep f<sub>j</sub> and angular sweep are similar to incident angle &theta;<sub>j</sub> such that (2&pi;/c) . f<sub>j</sub>. sin &theta;<sub>j</sub> = k<sub>li</sub>. This provides a complete picture of the non-dispersion behavior of your periodic case as discussed earlierstructure. Keep in mind The sweep data can be graphed as a wavenumber-frequency intensity plot (also known as beta-k diagram) that in this release projects the eigenvalues of the periodic structure. The horizontal axis represents the constant transverse wavenumber k<sub>l</sub> (or beta). The vertical axis represents frequency. Sometimes, the free space wave number k<sub>0</sub> = (2&pi;/c).f is used as the vertical axis, hence, the term beta-k diagram. However, [[EM.Cube]]'s [[FDTD Module]], for oblique plane wave incidences, you need to run a plots frequency sweep vs. wavenumber. Both the horizontal and vertical axes start from 0 and extend to get wideband reflectionf<sub>max</transmission coefficient data. Similarlysub> and k<sub>l, max</sub>, respectively, where f<sub>max</sub> = f<sub>0</sub> + &Delta;f/2, and &Delta;f is the specified bandwidth of the project. For this sweep option you need have to run an angular sweep to plot R/T coefficients vsspecify the number of wavenumber samples. Note that the dispersion sweep is run for a fixed given value of the plane wave incident angle&phi; as specified in [[EM.Tempo]]'s Plane Wave Dialog.
<table><tr><td>[[FileImage:FDTD144KBT Settings.png|thumb|200px360px|[[FDTD ModuleEM.Tempo]]'s Dispersion Sweep Settings dialog.]]</td></tr></table>
The '''<table><tr><td>[[Image:KBT R/T Macromodel Sweep''' option of the Simulation Mode dropdown list is only available for periodic structures. It is used to generate a lookup table model for the png|thumb|360px|A typical reflection and transmission coefficients coefficient dispersion diagram of a periodic surface for both TM and TE polarizationsstructure. The results are written into a file named "PW_UserDefinedMacroData.mat". Through the Macromodel Settings dialog you can set the start and end value and number of samples for both the Theta (&theta;) and Phi (&phi;) angles of the incident plane wave. The R]]</T macormodels can be used by td><td>[[EMImage:KBT T.Cube]]'s [[Propagation Module]] to calculate the reflection and png|thumb|360px|A typical transmission coefficients coefficient dispersion diagram of incident rays at the facets of obstructing blocks with "non-standard" a periodic surfacesstructure.]]</td></tr></table>
The '''Dispersion Sweep '''option of the Simulation Mode dropdown list performs a sweep of constant k<sub>l<br /sub> wavenumber values. This is a specialized sweep for the constant transverse wavenumber method that [[EM.Cube]]'s [[FDTD Module]] uses to model periodic structures illuminated by a plane wave source. The real advantage of a dispersion sweep is that through a one-dimensional sweep of k<sub>li</sub>, you can find the reflection and transmission coefficients for all combinations of frequency f<sub>j</sub> and incident angle &theta;<sub>j</sub> such that (2&pi;/c) . f<sub>j</sub>. sin &theta;<sub>j</sub> = k<sub>li</sub>. This provides a complete picture of the dispersion behavior of your periodic structure. The sweep data can be graphed as a wavenumber-frequency intensity plot (also known as beta-k diagram) that projects the eigenvalues of the periodic structure. The horizontal axis represents the constant transverse wavenumber k<sub>l</sub> (or beta). The vertical axis represents frequency. Sometimes, the free space wave number k<sub>0</sub> = (2&pi;/c).f is used as the vertical axis, hence, the term beta-k diagram. However, [[EM.Cube]] plots frequency vs. wavenumber. Both the horizontal and vertical axes start from 0 and extend to f<sub>max</sub> and k<sub>l,max</sub>, respectively, where f<sub>max</sub> = f<sub>0</sub> + &Delta;f/2, and &Delta;f is the specified bandwidth of the project. For this sweep option you have to specify the number of wavenumber samples. Note that the dispersion sweep is run for a fixed given value of the plane wave incident angle &phi; as specified in [[FDTD Module]]'s Plane Wave Dialog.
{{isoimg|FDTD148.png|A typical dispersion diagram of a periodic structure}}<hr>
[[Image:Top_icon.png|30px]] '''[[EM.Tempo#Product_Overview | Back to the Top of the Page]]'''
{{FDTD Details}}[[Image:Tutorial_icon.png|30px]] '''[[EM.Cube#EM.Tempo_Documentation | EM.Tempo Tutorial Gateway]]'''
<p>&nbsp;</p>[[Image:Back_icon.png|30px]] '''[[EM.Cube | Back to EM.Cube Main Page]]'''
4,622
edits