Changes

EM.Tempo offers the following types of observable:

{| class="wikitable"

|-

| '''[[Glossary of EM.Cube's Simulation Observables#Port Definition |Port Characteristics]]'''

| style="width:250px;" | Associated with a PEC Cylinder

|-

| style="width:250px;" | Stand-alone source

|}

Of EM.Tempo's frequency domain observables, the near fields, far fields and all of their associated [[parameters]] like directivity, RCS, etc., are calculated at a certain single frequency that is specified as part of the definition of the observable. To compute those frequency domain data at several frequencies, you need to define multiple observables, one for each frequency. On the other hand, port characteristics like S/Y/Z [[parameters]] and VSWR are calculated over the entire specified bandwidth of your project. Of EM.Tempo's source types, lumped sources, waveguide sources and distributed sources let you define one or more ports for your physical structure and compute its port characteristics. One of EM.Tempo's real advantages over frequency-domain solvers is its ability of generate wideband S/Z/Y parameter data in a single simulation run.

=== Examining the Near Fields in Time and Frequency Domains ===

[[Image:FDTD77.png|thumb|400px|Time-domain evolution of the electric field at a given point.]]

EM.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 instruct EM.Tempo to save a small potion of these data for visualization and plotting purposes. Using a '''Field Probe''' at a specified point, you can record the a time-domain field component over the entire FDTD loop. The time-domain results are also transformed to the frequency domain within the specified bandwidth using a discrete Fourier transform (DFT).

In EM.Tempo, you can visualize the near fields at a specific frequency in a specific plane of the computational domain. To do so, you need to define a '''Field Sensor''' observable. EM.Tempo's field sensor defines a plane across the entire computational domain parallel to one of the three principal planes. 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.

<table>