Changes

User talk:Asabet

74 bytes added, 20:49, 4 June 2014
/* 1.8 Running the FDTD Simulation */
[[Image:fdtd_lec1_18_portdefinition.png|center]]
==1.8 Running the FDTD Simulation==
[[Image:fdtd_lec1_19_run.png|right]] At this time, your project is ready for FDTD simulation. Click the Run Button of the Simulate Toolbar to open up the Simultion Run Dialog. Or alternatively, use the keyboard shortcut Ctrl+R, or the menu Simulate  Run… The simplest simulation mode in EM.Cube is “Analysis”. In this mode, your physical structure is taken “As Is” and its mesh is passed to ==Running the FDTD simulation engine, alnog with the necessary information regarding the soures and observables. An FDTD “Analysis” is a wideband analysis by nature depending on your project’s specified bandwidth. At the end of an FDTD analysis, the port characteristics are calculated over the entire bandwidth of your project. However, some frequency-domain observables like field sensors or radiation patterns are calculated only at the specified frequencies.Simulation==
Before you run your first FDTD simulation in EM[[Image:fdtd_lec1_19_run.Cubepng|right]] At this time, let’s take a closer look at the your project is ready for FDTD simulation engine’s settings. Click the Settings button next to <b>Run</b> [[Image:fdtd_runb.png]] Button of the “Select Engine” dropdown list Simulate Toolbar to bring open up the FDTD Engine Settings Simultion Run Dialog box. Or alternatively, use the keyboard shortcut <b>Ctrl+R</b>, or the menu <b>Simulate &rarr; Run…<b> The “Convergence” section of simplest simulation mode in EM.Cube is “Analysis”. In this dialog offers three criteria for terminating mode, your physical structure is taken “As Is” and its mesh is passed to the FDTD time marching schemesimulation engine, alnog with the necessary information regarding the soures and observables. The first one An FDTD “Analysis” is a Power Threshold of -30dBwideband analysis by nature depending on your project’s specified bandwidth. The second one is a Maximum Number At the end of Time Steps equal to 10an FDTD analysis,000. The third option is labeled “Both”, which means that both of the above termination criteria will be considered until one port characteristics are calculated over the entire bandwidth of is metyour project. If your computer has a CUDAHowever, some frequency-enabled Nvidia GPU, you can use EM.Cube’s accelerated GPU FDTD solver. The default setting is to use domain observables like field sensors or radiation patterns are calculated only at the Multi-Core CPU solverspecified frequencies.
In the “Excitation Waveform” section of the dialog, you can set the temporal waveform type for the FDTD simulation. Three options are available: Sinusoidal, Gaussian Pulse and Modulated Gaussian Pulse, with the last one set as default type. Accept all the parameters with their default values and click OK.
Before you run your first FDTD simulation in EM.Cube, let’s take a closer look at the FDTD simulation engine’s settings. Click the Settings button next to the “Select Engine” dropdown list to bring up the FDTD Engine Settings Dialog box. The “Convergence” section of this dialog offers three criteria for terminating the FDTD time marching scheme. The first one is a <b>Power Threshold</b> of -30dB. The second one is a <b>Maximum Number of Time Steps</b> equal to 10,000. The third option is labeled “Both”, which means that both of the above termination criteria will be considered until one of is met. If your computer has a CUDA-enabled Nvidia GPU, you can use EM.Cube’s accelerated GPU FDTD solver. The default setting is to use the Multi-Core CPU solver.   In the “Excitation Waveform” section of the dialog, you can set the temporal waveform type for the FDTD simulation. Three options are available: Sinusoidal, Gaussian Pulse and Modulated Gaussian Pulse, with the last one set as default type. Accept all the parameters with their default values and click <b>OK</b>.  To run the simulation, click the <b>Run </b> button of the Simulation Run Dialog. A separate window pops up displaying messages from the simulation engine. In four separate fields, the engine reports the current time step, elapsed time, performance in MCells/second, and convergence status. Once the simulation has been completed, you can close the message window and return to the project workspace. The Navigation Tree is now populated with simulation results, most notably under Field Sensors and Far Fields nodes. 
[[Image:fdtd_lec1_20_enginesetting.png|center]]
4,612
edits