Changes

EM.Tempo

40 bytes added, 22:26, 1 June 2015
{{Note|You can import external objects only to '''[[CubeCAD]]'''. You need to move the imported objects form [[CubeCAD]] to EM.Tempo as described above.}}
===Understanding Different FDTD Material Types===
====Perfect Conductors====
Once you define a source, you can always changes its [[parameters]] later from its property dialog, which can be accessed from its right-click contextual menu. You can also delete sources.
===Understanding Different FDTD Source Types===
====Ideal Source====
====Plane Wave Source====
In [[EM.Tempo]], 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.Tempo]] provides the following polarization options: * TMz* , TEz* , Custom Linear* , LCPz* and RCPz . The direction of incidence is defined through the &theta; and &phi; angles of the unit propagation vector in the spherical coordinate system. The values of these angles are set in degrees in the boxes labeled '''Theta''' and '''Phi'''. The default incidence angles are &theta; = 180° and &phi; = 0° representing a normally incident plane wave propagating along the -Z direction with a +X-polarized E-vector. In the TM<sub>z</sub> and TE<sub>z</sub> polarization cases, the magnetic and electric fields are parallel to the XY plane, respectively. The components of the unit propagation vector and normalized E- and H-field vectors are displayed in the source dialog. This way of defining a plane wave source is more convenient when the structure is laid out along the XY plane and Z-axis such as layered and periodic structures. In the more general case of custom linear polarization, besides the incidence angles, you have to enter the components of the unit electric '''Field Vector'''. However, two requirements must be satisfied: '''ê . ê''' = 1 and '''ê × k''' = 0 . This can be enforced using the '''Validate''' button at the bottom of the dialog. If these conditions are not met, an error message is generated. The left-hand (LCP) and right-hand (RCP) circular polarization cases are restricted to normal incidences only (&theta; = 180°).
EM.Tempo requires a finite plane wave incidence surface to calculate the excitation. When you create a plane wave source, a plane wave box is created as part of its definition. A trident symbol on the box shows the propagation vector as well as the E-field and H-field polarization vectors. The time domain plane wave excitation is 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. Initially, the radio button '''Size: Default''' is selected. 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 left corner and Corner 2 is the rear upper right corner of the box. The box has to be defined in the world coordinate system (WCS).
== Working with FDTD Simulation Data ==
 
===The 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 (E<sub>x</sub>, 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 time steps from t = 0 until the end of the time loop. However, in order to save memory space, 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 (RCS) 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.
Once you define an observable, you can always changes its [[parameters]] later from its property dialog, which can be accessed from its right-click contextual menu. You can also delete observables.
===Understanding Different FDTD Observable Types=== ====Probing Fields in Time and Frequency Domains====
[[Image:FDTD75.png|thumb|300px|FDTD Field Probe Dialog]]
{{twoimg|FDTD77.png|Time domain component plotted vs. time|FDTD78.png|Probed field plotted vs. frequency.}}
====Frequency-Domain Near Field Visualization====
[[Image:FDTD71(1).png|thumb|300px|[[FDTD Module]]'s Field Sensor dialog]]
You can plot frequency domain fields in EM.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 to lower-front-left corner of the computational domain.
====Visualizing Field Evolution in Time Domain====
In 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, 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 '''Properties...'''from the contextual menu. In the section titled '''Sensor Domain''', select the radio button labeled '''Time Domain'''. Also, in the section titled "Field Display - Multiple Plots", select one of the two radio buttons labeled '''E-Field''' or '''H-Field'''. By default, the time domain field data are saved every 100 time steps. To change this setting, right click on the '''Field Sensors''' item in the Navigation Tree and select '''Time Domain Settings...''' from the contextual menu. In the Time Domain Settings Dialog, change the value of the box labeled '''Sampling Interval (in time steps)'''.
{{twoimg|FDTD121.png|Field sensor setup for time-domain output|FDTD126.png|Time interval settings}}
====Scattering Parameters and Port Characteristics====
If your physical structure is excited by a Lumped Source or a Waveguide Source or a Distributed Source, and one or more ports have been defined, the FDTD engine calculates the scattering (S) [[parameters]], impedance (Z) [[parameters]] and admittance (Y) [[parameters]] of the selected ports. The S [[parameters]] are calculated based on the port impedances specified 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 the following definition:
[[Image:FDTD116.png|thumb|300px|[[FDTD Module]]'s Radiation Pattern dialog]]
[[Image:fdtd_out26_tn.png|thumb|300px|The 3D total radiation pattern of a dipole antenna: polar type.]]
====Far Field Calculations in FDTD====
For radiating structures or scatterers, the far field quantities are of primary interest. [[EM.Tempo]] computes 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. 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.Tempo]] uses rectangular boxes to define these closed surfaces. You can use [[EM.Tempo]]'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.
Click here to learn about [[Advanced Features of FDTD Radiation Patterns]].
====Defining The Far Field Box====
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:
[[Image:FDTD131.png|thumb|300px|EM.Tempo's RCS dialog]]
====Radar Cross Section====
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. To compute the RCS of your physical structure, you must define an RCS observable instead of a radiation pattern. Follow these steps:
28,333
edits