Changes
/* Simulating the Patch Antenna on the Vehicle's Hood */
{{projectinfo|Application|Simulating The Performance Of Installed Antennas On Vehicular Platforms Using EM.Tempo|ART_GOLF_Fig_title.png|In this project, large parabolic reflectors fed by pyramidal horn antennas mounted on a complex, real-sized, automobile platform are modeled and analyzed using EM.Illumina and EM.Tempo.|*[[Building Geometrical Constructions in CubeCAD | CubeCAD]]
*[[EM.Tempo]]
*[[EM.Illumina]]CAD Model*Pyramidal HornPatch Wizard*Parabola*Object of RevolutionYee Mesh
*Field Distribution
*Radiation Pattern
*High Performance Computing
|All versions|None }}
</table>
The patch structure was simulated using [[EM.Tempo]]'s FDTD solver on a thick metal ground. The 3D far-field radiation pattern of the isolated finite-substrate patch antenna is shown in the figure below. The directivity of the patch is computed to be 7.09dB.
<table>
</table>
== Computational Environment Importing the Vehicle Model ==
For this project, we use an IGES CAD model of a Volkswagen Golf automobile. The Mirage III CAD model has an approximate length consists of 15m, 2019 different surface objects. They are originally grouped into a wingspan number of 8m, and an approximate height of 4.5m. Expressed different object sets as shown in free-space wavelengths at 850 MHz, the approximate figure below. The overall dimensions of the aircraft model car are 42.5 about 420cm λtimes;<sub>0</sub> x 22.66 200cm λtimes;<sub>0</sub> x 12.75 λ<sub>0</sub>. Thus, for the purposes of [[EM.Tempo]], we need to solve a region of about 12,279 cubic wavelengths. For problems of this size, a very large CPU memory is needed, and a high-performance, multi-core CPU is desirable to reduce the simulation time142cm.
<table><tr><td>[https[Image://awsART GOLF Fig1.amazon.com/ Amazon Web Services] allows one to acquire highpng|thumb|left|720px| The four-performance compute instances on demand, and pay on a per-use basis. To be able to log into an Amazon instance via Remote Desktop Protocol (RDP), port view of the [[EMimported CAD model of the vehicle before material assignments in CubeCAD.Cube]] license must allow terminal services. For the purpose of this project, we used a c4.4xlarge instance running Windows Server 2012. This instance has 30 GB of RAM memory, and 16 virtual CPU cores. The CPU for this instance is an Intel Xeon E5-2666 v3 (Haswell) processor.</td></tr><br clear="all"/table> =Patch on Roof=
{| class="wikitable"
|-
! scope="col"| Material
! scope="col"| ε<sub>r</sub>
! scope="col"| σ
! scope="col"| Designated Model Parts
|-
| PEC
| 1
| ∞
| Car body
|-
| Glass
| 6.5
| 0.005005S/m| Car windows
|-
| Plastic
| 2.2
| 0.0
| Head-light covers, brake-light covers, license plate mounts
|-
| Rubber
| 2.9
| 0.005005S/m| Tires
|-
| Aluminum
| 1
| 38000003.8×10<sup>6</sup> S/m| Wheel rims
|-
| Cement
| 1.9
| 0.0
| Road surface
|}
The FDTD simulation of the vehicle structure was run on [https://aws.amazon.com/ Amazon Web Services]. For the purpose of this project, we logged into an Amazon instance via Remote Desktop Protocol (RDP) and used a c4.4xlarge instance running Windows Server 2012. This instance had 30 GB of RAM memory, and 16 virtual CPU cores. The CPU for this instance was an Intel Xeon E5-2666 v3 (Haswell) processor. The thread factor setting essentially tells the FDTD engine how many CPU threads to use during [[EM.Tempo]]'s time-marching loop. For a given system, some experimentation may be needed to determine the best number of threads to use. In many cases, using half of the available hardware concurrency works well. This comes from the fact that many modern processors often have two cores per memory port. In other words, Eight thread factors were used for many problemsthis simulation, the FDTD solver cannot load and store data from CPU memory quickly enough to use all the available threads or hardware concurrency. The extra threads remain idle waiting for the data, and a performance hit is incurred due to the increased thread context switching. [[EM.Cube]] will attempt use a version of the FDTD engine optimized for use with Intel's AVX instruction set, which provides a significant performance boost. If AVX is unavailable, a less optimal version total computation time of the engine will be used alternatively285 minutes.
<table><tr><td>[[Image:Roof meshfield.png|thumb|left|400px640px|The dB-scale electric field distribution of the vehicle-antenna combination structure in the vertical ZX plane.]]</td></tr></table>
<table><tr><td>[[Image:Roof mesh settings advancedpattern.png|thumb|left|400px640px|3D far-field radiation pattern of the vehicle-antenna combination structure, with the patch antenna installed on the vehicle's roof.]]</td></tr></table>
<table><tr><td>[[Image:Roof yz cut.png|thumb|left|480px| 2D linear-scale polar radiation pattern of the roof-mounted patchantenna in the YZ plane..]]</td></tr><tr><td>[[Image:Roof zx cut.png|thumb|left|400px480px|2D linear-scale polar radiation pattern of the roof-mounted patch antenna in the ZX plane..]]</td></tr></table>
<table><tr><td>[[Image:Roof wheel matHood mount.png|thumb|left|400px480px|The location of the patch antenna on the vehicle's hood.]]</td></tr></table>
<table><tr><td>[[Image:Roof yz cutHood mount mesh detail.png|thumb|left|400px480px|The details of the Yee mesh of the vehicle structure generated by EM.Tempo around the location of the patch antenna on the hood.]]</td></tr></table>
[[Image:Hood yz cutTop_icon.png|thumb|left|400px30px]] '''[[#Introduction |Back to the Top of the Page]]'''
[[Image:Hood zx cutBack_icon.png|thumb|left|400px30px]] '''[[EM.Cube#EM.Cube Articles & Notes |Check out more Articles & Notes]]'''