Professional Documents
Culture Documents
Contents - 1
Customize Toolbar Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
Customize Toolbar Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-20
Customizing the Tools Menu: External Tools . . . . . . . . . . . . . . . . . . . . . 1-20
Working with the Shortcut Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Shortcut Menu in the Toolbars Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-22
Shortcut Menu in the 3D Modeler Window . . . . . . . . . . . . . . . . . . . . . . . . . 1-23
Shortcut Menus in the Project Manager Window . . . . . . . . . . . . . . . . . . . . 1-24
Keyboard Shortcuts for HFSS General Purposes . . . . . . . . . . . . . . . . . . 1-24
Custom Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25
Working with the Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Exiting the Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Working with the Project Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-27
Working with the Project Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-28
Setting the Project Tree to Expand Automatically . . . . . . . . . . . . . . . . 1-28
Viewing HFSS Design Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Viewing the Design List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-29
Viewing Material Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Working with the Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-30
Opening the Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-31
Showing and Hiding the Properties Window . . . . . . . . . . . . . . . . . . . . . . . . 1-32
Setting the Properties Window to Open Automatically . . . . . . . . . . . . . . . . 1-32
Modifying Object Attributes Using the Properties Window . . . . . . . . . . . . 1-32
Modifying Object Command Properties Using the Properties Window . . . 1-33
Working with the Progress Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-33
Stopping or Aborting Simulation Progress . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Viewing Distributed Analysis Subtasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Working with the Message Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-34
Setting the Message Manager to Open Automatically . . . . . . . . . . . . . . . . . 1-35
Showing new messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Showing errors and warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-35
Working with the 3D Modeler Window . . . . . . . . . . . . . . . . . . . . . . . . . 1-36
Working with the History Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-37
Expand or Collapse Groupings in the History Tree . . . . . . . . . . . . . . . . . . . 1-38
History tree Grouping by Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-38
Select Objects in the History Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
Shortcut Menus in the History Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-39
View Item Properties in the History Tree . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
View and Edit Commands on History Tree Objects . . . . . . . . . . . . . . . . . . 1-41
Controlling the View of Objects in the History Tree . . . . . . . . . . . . . . . . . . 1-42
Upgrade Version in History Tree Shortcut Menu . . . . . . . . . . . . . . . . . . . . 1-42
Keyboard Shortcuts for the 3D Modeler Window . . . . . . . . . . . . . . . . . . 1-42
Using the Password Manager to Control Access to Resources . . . . . . . . . 1-44
Contents - 2
Running HFSS from a command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-45
Running from a Windows Remote Terminal . . . . . . . . . . . . . . . . . . . . . . . 1-51
Windows HPC Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-52
Getting Started Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-53
Getting Started Guide: A Waveguide Tee Junction . . . . . . . . . . . . . . . . . 1-53
Getting Started Guide: Optimizing A Waveguide Tee Junction . . . . . . . 1-54
Getting Started Guide: A Dielectric Resonator Antenna . . . . . . . . . . . . . 1-55
Getting Started Guide: A 20 GHz Waveguide Combiner . . . . . . . . . . . . 1-55
Getting Started Guide: Floquet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-55
Getting Started Guide: RCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
Getting Started Guide: Coax Tee . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-56
Getting Started Guide: A Coax Connector . . . . . . . . . . . . . . . . . . . . . . . 1-57
Getting Started Guide: A Bandpass Filter . . . . . . . . . . . . . . . . . . . . . . . . 1-57
Getting Started Guide: A UHF Probe . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Getting Started Guide: A Patch Antenna . . . . . . . . . . . . . . . . . . . . . . . . . 1-58
Getting Started Guide:Silicon Spiral Inductor . . . . . . . . . . . . . . . . . . . . . 1-59
Application Specific Modeling Guide: Antennas . . . . . . . . . . . . . . . . . . 1-60
Application Specific Modeling Guide: Spiral Inductors on Silicon
Substrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-60
HFSS-IE Getting Started Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-62
HFSS Transient Getting Started Guides . . . . . . . . . . . . . . . . . . . . . . . . . . 1-64
Example Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-66
Other Examples with Brief Descriptions in the Online Help . . . . . . . . . . 1-67
Tee and OptimTee Waveguide Projects . . . . . . . . . . . . . . . . . . . . . . . . . . 1-68
Dielectric Resonator Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-70
Waveguide Combiner Example Project . . . . . . . . . . . . . . . . . . . . . . . . . . 1-71
cavity.hfss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-72
Optiguide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-74
Package Example Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-76
Antennas on Mast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-77
Parametric Sweep of a Coax Bend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-78
Coaxial Resonator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-79
Connector - Terminal Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-81
Corporate Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-83
Helical Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-84
Package Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-86
Small Array of Planar Flared Dipole Antennas . . . . . . . . . . . . . . . . . . . . 1-88
Pyramidal Horn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-89
Ring Hybrid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91
Tune a Coax Fed Patch Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-94
Contents - 3
Unit Cell of a Phased Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-96
Via Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-98
Copyright and Trademark Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-100
2. Getting Help
Conventions Used in the Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Searching in Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Using WebUpdate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Obtaining Information About the Software and Version . . . . . . . . . . . . . . 2-6
Emailing a Help Page Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
3. Working with HFSS Projects
HFSS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Creating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Opening Example Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Opening Recent Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
Opening Legacy HFSS Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Legacy HFSS Project Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Closing Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
Saving Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Saving a New Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10
Saving the Active Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Saving a Copy of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Renaming a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11
Saving Project Data Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Save Before Solve Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12
Recovering Project Data in an Auto-Save File . . . . . . . . . . . . . . . . . . . . . . 3-13
Deleting Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14
Undoing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15
Redoing Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16
Updating Design Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
Managing Projects and Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Copy and Paste a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Rename a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Delete a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-18
Validating Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19
Modeler Validation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20
Exporting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Exporting 2D Geometry Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Contents - 4
Exporting 3D Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
Exporting Graphics Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24
Exporting Data Table Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25
Importing Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Importing 2D Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26
Importing GDSII Format Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-27
Tech File Colors with RGB Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29
Importing 3D Model Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51
Importing DXF and DWG Format Files . . . . . . . . . . . . . . . . . . . . . . . . . 3-53
Importing Solution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55
Importing Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-56
Importing HFSS Plot Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Importing Plot Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57
Inserting a Documentation File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60
Previewing the Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61
Changing the Page Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-62
Saving Project Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-63
Setting Options in HFSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
Setting General Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
General Options: Project Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-64
General Options: Default Units Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
General Options: Analysis Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-65
General Options: RSM Service Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
General Options: WebUpdate Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . 3-67
General Options: Miscellaneous Options Tab . . . . . . . . . . . . . . . . . . . . . . . 3-67
Setting HFSS Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-68
HFSS Options: General Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-69
HFSS Options: Solver Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-70
Setting Solver Settings Using VB Scripts . . . . . . . . . . . . . . . . . . . . . . . 3-71
Setting HFSS-IE Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
HFSS-IE Options: General Options Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-72
HFSS-IE Options: Solver Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-73
Setting Fields Reporter Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-74
Setting Report2D Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Report 2D Options: Curve Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75
Report2D Options: Axis Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Report2D Options: Grid Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Report2D Options: Header Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-76
Report2D Options: Note Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Report2D Options: Legend Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Contents - 5
Report2D Options: Marker tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-77
Report2D Options: Marker Table Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Report2D Options: General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-78
Report2D Options: Table Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Setting Modeler Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-79
Modeler Options: Operation Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Modeler Options: Display Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-80
Modeler Options: Drawing Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-82
Report Setup Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-83
Working with Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Adding a Project Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-85
Intrinsic Variables in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-87
Deleting Project Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
Adding a Design Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-88
Add Array of Values for a Design Variable . . . . . . . . . . . . . . . . . . . . . . 3-91
Editing a Design Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-92
Deleting Design Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-93
Adding Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-94
Modifying Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Defining Mathematical Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-95
Defining an Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-96
Using Valid Operators for Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Using Intrinsic Functions in Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-97
Using Piecewise Linear Functions in Expressions . . . . . . . . . . . . . . . . . . . . 3-99
Using Dataset Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Assigning Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Choosing a Variable to Optimize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-100
Including a Variable in a Sensitivity Analysis . . . . . . . . . . . . . . . . . . . . . 3-101
Choosing a Variable to Tune . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-102
Including a Variable in a Statistical Analysis . . . . . . . . . . . . . . . . . . . . . 3-102
Exporting Variables for Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 3-103
4. Setting up an HFSS Design
Inserting an HFSS Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Selecting the Solution Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
5. HFSS Transient
Adding a Solution Setup for Transient Solutions . . . . . . . . . . . . . . . . . . . 5-3
Transient Network Analysis Input Signal Tab: a Time Profile . . . . . . . . . 5-5
Duration Tab for Transient Solution Setup . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Saved Fields Tab for Transient Solution Setup . . . . . . . . . . . . . . . . . . . . . 5-8
Contents - 6
Active or Passive Excitations in HFSS Transient . . . . . . . . . . . . . . . . . . . 5-9
Transient Solution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
Selecting the Report Type in HFSS Transient . . . . . . . . . . . . . . . . . . . . . . 5-13
Procedure for Viewing Transient Radiated Fields . . . . . . . . . . . . . . . . . . . 5-14
6. HFSS-IE
Inserting an HFSS-IE Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
Assigning HFSS-IE Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Assigning Excitations in HFSS-IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Adding a Solution Setup to an HFSS-IE Design . . . . . . . . . . . . . . . . . . . . 6-6
7. Drawing a Model
Setting Units of Measurement for the Model . . . . . . . . . . . . . . . . . . . . . . 7-3
Drawing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Drawing a Straight Line Segment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Drawing a Three-Point Arc Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Drawing a Center-Point Arc Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Drawing a Spline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Drawing a Polyline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9
Assigning a Cross Section and Dimensions to a Polyline . . . . . . . . . . . . 7-11
Inserting Line Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13
Drawing an Equation-Based Curve . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14
Drawing a Circle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Drawing an Ellipse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15
Drawing a Rectangle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Drawing a Regular Polygon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17
Drawing an Equation-Based Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18
Drawing a Sphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-19
Drawing a Cylinder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-20
Drawing a Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-21
Drawing a Regular Polyhedron . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Drawing a Cone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-22
Drawing a Torus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-23
Drawing a Helix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24
Drawing a Segmented Helix with Polygon Cross-Section Using a User
Defined Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-25
Drawing a Segmented Helix with Rectangular Cross-Section Using a
User Defined Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-26
Drawing a Spiral . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27
Drawing a Spiral using User Defined Primitives . . . . . . . . . . . . . . . . . . . 7-29
Contents - 7
Drawing a Bondwire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30
Drawing a Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Drawing a Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31
Creating Segmented Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Segmented Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32
Drawing Non-Model Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33
Selecting Non-Model Drawing Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Changing an Object to Non Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Drawing a Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34
Model Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36
Analysis Options Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37
Analyzing the Surface Mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Model Analysis dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-38
Objects Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39
Object Misalignment Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-40
Surface Mesh (Single/Pairs) Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-41
Last Simulation Mesh Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-42
Design Settings for HFSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-43
Design Settings for HFSS-IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45
Setting the Temperature of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46
Heal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47
Healing Non-Manifold Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-48
Setting the Healing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-51
Stitch Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-52
Align Selected Faces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Remove Selected Faces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Remove Selected Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-53
Creating a User Defined Primitive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-55
User Customization through User Defined Primitives (UDPs) . . . . . . . . 7-57
Modifying Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-59
Assigning Color to Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Setting the Default Color of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Setting the Default Color of Object Outlines . . . . . . . . . . . . . . . . . . . . . . . . 7-60
Assigning Transparency to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61
Setting the Default Transparency of Objects . . . . . . . . . . . . . . . . . . . . . . . . 7-61
Copying and Pasting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-61
Import a Model from the Clipboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Copy Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-62
Deleting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
Deleting Start Points and Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-63
Delete Last Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Contents - 8
Cutting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Moving Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Rotating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-64
Changing the Orientation of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Mirroring Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-65
Offsetting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Duplicating Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67
Duplicating Objects Along a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Duplicating Objects Around an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-68
Duplicating and Mirroring Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
Scaling Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-69
Sweeping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Sweeping Around an Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-70
Sweeping Along a Vector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-71
Sweeping Along a Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-72
Sweeping Faces Along Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Thicken Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Wrap Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-73
Covering Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-74
Covering Faces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
Uncovering Faces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
Detaching Faces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
Detaching Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-75
Creating a Cross-Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
Connecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
Moving Faces or Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-76
Moving Faces Along the Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-77
Moving Faces Along a Vector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-78
Moving Edges Along Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
Uniting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-79
Subtracting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-80
Creating Objects from Intersections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-81
Creating an Object from a Face . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-82
Creating an Object from an Edge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-83
Splitting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-83
Separating Bodies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85
Converting Polyline Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-85
Rounding the Edge of Objects (Fillet Command) . . . . . . . . . . . . . . . . . . 7-86
Flattening the Edge of Objects (Chamfer Command) . . . . . . . . . . . . . . . 7-87
Imprinting an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87
Imprint Projection commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-89
Contents - 9
Purge History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-90
Generate History to Reproduce Portions of Model . . . . . . . . . . . . . . . . . 7-90
Selecting Items in the 3D Modeler Window . . . . . . . . . . . . . . . . . . . . . . . 7-93
Selecting Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-93
Selecting Several Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-94
Selecting Objects by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-95
Select By Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-95
Selecting All Objects in a History Tree Group . . . . . . . . . . . . . . . . . . . . . . 7-97
Setting the Default Color and Transparency of Selected Objects . . . . . . . . 7-98
Setting the Default Color of Highlighted Objects . . . . . . . . . . . . . . . . . . . . 7-98
Creating an Object List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-99
Reassigning Objects to Another Object List . . . . . . . . . . . . . . . . . . . . . . . . 7-99
Using or Viewing List Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100
Selecting Faces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-100
Selecting All Faces of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-101
Selecting Faces by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102
Selecting Faces by Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-102
Face Selection Toolbar Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-103
Creating a Face List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-103
Selecting Edges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-104
Selecting All Edges of an Object or Face . . . . . . . . . . . . . . . . . . . . . . . . . . 7-105
Selecting Vertices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-106
Selecting Multi (a Mode for Selecting Objects, Faces, Vertices or
Edges) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107
Controlling the Selection in Multi Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107
Clearing a Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-108
Selecting the Face, Edge, Vertex, or Object Behind . . . . . . . . . . . . . . . . 7-108
Selecting Objects by Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-109
Assigning Coordinates to New Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111
Setting the Reference Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111
Defining Cartesian Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-111
Defining Cylindrical Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-112
Defining Spherical Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-113
Using Absolute Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-114
Using Relative Coordinates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-114
Choosing the Movement Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-116
Moving the Cursor In Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-116
Moving the Cursor Out of Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-117
Moving the Cursor in 3D Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-117
Moving the Cursor Along the X-Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-118
Moving the Cursor Along the Y-Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-119
Moving the Cursor Along the Z-Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-119
Contents - 10
Choosing Snap Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-120
Snap Setting Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-121
Measure Modes for Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-122
Measuring Position and Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-123
Setting Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-126
Setting the Working Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . 7-127
Creating a Relative Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127
Creating an Offset Relative CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127
Creating a Rotated Relative CS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-128
Creating an Offset and Rotated Relative CS . . . . . . . . . . . . . . . . . . . . . . . . 7-128
Creating a Face Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-129
Automatically Creating Face Coordinate Systems . . . . . . . . . . . . . . . . . . . . 7-130
Modifying Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-130
Expressing Cartesian, Cylindrical, or Spherical Coordinates . . . . . . . . . 7-131
Deleting Coordinate Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-132
Setting the Drawing Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-133
8. Assigning Boundaries
Zoom to Selected Boundary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Setting Default Boundary/Excitation Base Names . . . . . . . . . . . . . . . . . 8-3
Assigning Perfect E Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Assigning Perfect H Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Assigning Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Assigning Radiation Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Assigning PML Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Creating PMLs Automatically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Creating PML Boundaries Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-13
Guidelines for Assigning PML Boundaries . . . . . . . . . . . . . . . . . . . . . . . 8-15
Modifying PML Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15
Assigning Finite Conductivity Boundaries . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Assigning Finite Conductivity Boundaries in HFSS-IE . . . . . . . . . . . . . . 8-19
Assigning Symmetry Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-21
Assigning Master Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Assigning Slave Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
Assigning Lumped RLC Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-26
Vector Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27
Assigning Screening Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . 8-28
Get Impedance from External Design . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29
Assigning Layered Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . . . 8-31
Assigning Aperture Boundaries in HFSS-IE . . . . . . . . . . . . . . . . . . . . . . . 8-33
Contents - 11
Assigning Infinite Ground Plane Boundaries in HFSS-IE . . . . . . . . . . . . 8-34
Assigning Layered Impedance Boundaries in HFSS-IE . . . . . . . . . . . . . . 8-35
Designating Infinite Ground Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37
Modifying Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38
Deleting Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39
Reassigning Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-40
Reprioritizing Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41
Global Material Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42
Duplicating Boundaries and Excitations with Geometry . . . . . . . . . . . . . 8-43
Showing and Hiding Boundaries and Excitations . . . . . . . . . . . . . . . . . . . 8-44
Showing and Hiding Boundaries and Excitations in the Active View
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44
Showing and Hiding Boundaries and Excitations in Every View
Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45
Reviewing Boundaries and Excitations in the Solver View . . . . . . . . . . . 8-46
Setting Default Values for Boundaries and Excitations . . . . . . . . . . . . . . 8-47
9. Assigning Excitations
Zoom to Selected Excitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Assigning Wave Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Assigning Wave Ports for Modal Solutions . . . . . . . . . . . . . . . . . . . . . . . 9-5
Assigning Wave Ports for Terminal Solutions . . . . . . . . . . . . . . . . . . . . 9-8
Set Renormalizing Impedance for Terminals . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Auto Assign for Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Manually Assigning Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12
Manually Assigning a Wave Port for Terminal Solutions . . . . . . . . . . . . 9-13
Assigning Lumped Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17
Assigning Lumped Ports for Modal Solutions . . . . . . . . . . . . . . . . . . . . . 9-18
Manually Assigning Lumped Ports for Terminal Solutions . . . . . . . . . . 9-19
Assigning Floquet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Floquet Ports: Lattice Coordinate System . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Floquet Port: Modes Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Defining an Integration Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
Guidelines for Defining Integration Lines . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Duplicating Integration Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Modifying Integration Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Setting up Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Assigning Incident Waves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-32
Incident Plane Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-33
Incident Hertzian-Dipole Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-34
Contents - 12
Incident Cylindrical Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-35
Incident Gaussian Beam Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-36
Incident Linear Antenna Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-38
Far Field Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-39
Setup Link for Far Field or Near Field Wave . . . . . . . . . . . . . . . . . . . . . . . 9-41
External Data File for Far Field Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-42
Translation of Source Relative to Design . . . . . . . . . . . . . . . . . . . . . . . . . . 9-43
Near Field Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-45
HFSS-IE Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-47
Assigning Voltage Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
Modifying Voltage Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-48
Assigning Current Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Modifying Current Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-50
Assigning Magnetic Bias Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-51
Setup Link Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-53
Modifying Excitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-54
Deleting Excitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-55
Reassigning Excitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-56
Duplicating Excitations with Geometry . . . . . . . . . . . . . . . . . . . . . . . . . . 9-57
Showing and Hiding Excitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-58
Setting the Impedance Multiplier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59
Renormalizing S-Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-60
De-embedding S-Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-62
10. Assigning Materials
Solving Inside or on the Surface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Assigning DC Thickness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Searching for Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Searching by Material Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Searching by Material Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Adding New Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Assigning Material Property Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9
Defining Anisotropic Relative Permeability Tensors . . . . . . . . . . . . . . . . 10-10
Defining Anisotropic Relative Permittivity Tensors . . . . . . . . . . . . . . . . . 10-11
Defining Anisotropic Conductivity Tensors . . . . . . . . . . . . . . . . . . . . . . . 10-11
Defining Anisotropic Dielectric Loss Tangent Tensors . . . . . . . . . . . . . . . 10-12
Defining Magnetic Loss Tangent Tensors . . . . . . . . . . . . . . . . . . . . . . . . . 10-13
Defining Variable Material Properties . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Defining Frequency-Dependent Material Properties . . . . . . . . . . . . . . . 10-14
Assigning Frequency Dependent Material: Piecewise Linear Input . . . . . 10-17
Contents - 13
Assigning Frequency Dependent Material: Debye Model Input . . . . . . . . 10-18
Assigning Frequency Dependent Material: Multipole Debye Model
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
Assigning Frequency Dependent Material: Djordjevic-Sarkar Model
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-22
Assigning Frequency Dependent Material: Enter Frequency Dependent
Data Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Specifying Thermal Modifiers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-25
Defining Material Properties as Expressions . . . . . . . . . . . . . . . . . . . . . 10-26
Defining Functional Material Properties . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Assigning Materials from the Object Properties Window . . . . . . . . . . . . 10-27
Viewing and Modifying Material Attributes . . . . . . . . . . . . . . . . . . . . . . 10-28
Validating Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-30
Copying Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-31
Removing Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-32
Exporting Materials to a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33
Sorting Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34
Filtering Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35
Working with Material Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Working with Ansoft’s System Material Library . . . . . . . . . . . . . . . . . 10-36
Working with User Material Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Editing Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
Configuring Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-36
11. Modifying the Model View
View Options: 3D UI Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3
Rotating the View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Panning the View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5
Zooming In and Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Zooming In or Out on a Rectangular Area . . . . . . . . . . . . . . . . . . . . . . 11-6
Fitting Objects in the View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Fitting All Objects in a View Window . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Fitting a Selection in a View Window . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Hiding Objects from View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Showing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Active View Visibility Dialogue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Rendering Objects as Wireframes or Solids . . . . . . . . . . . . . . . . . . . . . . 11-13
Setting the Default View Rendering Mode . . . . . . . . . . . . . . . . . . . . . . 11-13
Setting the Curved Surface Visualization . . . . . . . . . . . . . . . . . . . . . . . . 11-14
Using Clip Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-16
Contents - 14
Modifying the View Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Applying a Default View Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . 11-20
Applying a New View Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Removing an Orientation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21
Modifying the Lighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22
Setting the Projection View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23
Setting the Background Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-24
Modifying the Coordinate System Axes View . . . . . . . . . . . . . . . . . . . . 11-25
Showing or Hiding the Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
Show the Axes for Selected Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
Enlarging or Shrinking the Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
Showing or Hiding the Triad Axes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-25
Choosing Grid Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26
Setting the Grid Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26
Setting the Grid Style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-26
Setting the Grid Density and Spacing . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Setting the Grid’s Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
Setting the Grid Plane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-27
12. Defining Mesh Operations
Assigning Length-Based Mesh Refinement on Object Faces . . . . . . . . . 12-3
Assigning Length-Based Mesh Refinement Inside Objects . . . . . . . . . . 12-4
Assigning Skin Depth-Based Mesh Refinement on Object Faces . . . . . . 12-5
Modifying Surface Approximation Settings . . . . . . . . . . . . . . . . . . . . . . 12-7
Specifying the Model Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9
Reverting to the Initial Mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-11
Applying Mesh Operations without Solving . . . . . . . . . . . . . . . . . . . . . . 12-12
Specifying Initial Mesh Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-13
Deleting All Previously Assigned Mesh Refinements . . . . . . . . . . . . . . 12-15
Viewing List of Mesh Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16
Reassigning a Mesh Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17
Viewing Mesh Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-18
13. Specifying Solution Settings
Adding a Solution Setup to an HFSS Design . . . . . . . . . . . . . . . . . . . . . 13-2
Add Dependent Solve Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Renaming a Solution Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Copying a Solution Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6
Setting the Solution Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Contents - 15
Solving for Ports Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
Setting the Minimum Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9
Setting the Number of Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10
Setting Adaptive Analysis Parameters for HFSS . . . . . . . . . . . . . . . . . . 13-11
Setting the Maximum Number of Passes . . . . . . . . . . . . . . . . . . . . . . . . 13-11
Setting the Maximum Delta S Per Pass . . . . . . . . . . . . . . . . . . . . . . . . . 13-12
Setting the Maximum Delta Energy Per Pass . . . . . . . . . . . . . . . . . . . . 13-12
Setting the Maximum Delta Frequency Per Pass . . . . . . . . . . . . . . . . . . 13-13
Specifying Convergence on Real Frequency Only . . . . . . . . . . . . . . . . . . 13-13
Specifying Expressions for Adaptive Convergence . . . . . . . . . . . . . . . . 13-13
Specifying a Source for the Initial Mesh . . . . . . . . . . . . . . . . . . . . . . . . 13-16
Clearing Linked Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Setting Lambda Refinement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-19
Setting Lambda Refinement for HFSS-IE . . . . . . . . . . . . . . . . . . . . . . . 13-20
Setting the Percent Maximum Refinement Per Pass . . . . . . . . . . . . . . . 13-20
Setting the Maximum Refinement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Setting the Minimum Number of Passes . . . . . . . . . . . . . . . . . . . . . . . . 13-21
Setting the Minimum Number of Converged Passes . . . . . . . . . . . . . . . 13-21
Setting Matrix Convergence Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-22
Setting the Order of Basis Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-23
Enable Iterative Solver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Enable Use of Solver Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-24
Balancing Resources for Solver Domains . . . . . . . . . . . . . . . . . . . . . . . 13-25
Use Radiation Boundary on Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Port Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26
Enable Thermal Feedback from ANSYS Mechanical . . . . . . . . . . . . . . 13-27
Produce Derivatives for Selected Variables . . . . . . . . . . . . . . . . . . . . . . 13-29
Adding a Frequency Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31
Selecting the Sweep Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32
Options for Discrete Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
Options for Fast Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
Options for Interpolating Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-33
Setup Interpolating Sweep Advanced Options . . . . . . . . . . . . . . . . . . . . . . 13-34
Setting the Error Tolerance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35
Setting the Maximum Number of Solutions . . . . . . . . . . . . . . . . . . . . . . . 13-35
Interpolation Basis Convergence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36
Specifying the Frequency Points to Solve . . . . . . . . . . . . . . . . . . . . . . . 13-37
Specifying Frequency Points with a Linear Step Size . . . . . . . . . . . . . . . . 13-37
Specifying a Linear Count of Frequency Points . . . . . . . . . . . . . . . . . . . . 13-38
Specifying a Logarithmic Spaced Frequency Sweep . . . . . . . . . . . . . . . . . 13-39
Specifying Single Frequency Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40
Contents - 16
Change the Value of an Existing Frequency Point . . . . . . . . . . . . . . . . . . 13-40
Deleting Frequency Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-41
Inserting Frequency Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-41
Choosing Frequencies for Full-Wave SPICE . . . . . . . . . . . . . . . . . . . . . . . 13-42
Guidelines for Calculating Frequencies for Full-Wave SPICE . . . . . 13-43
Requirements for Full-Wave SPICE . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44
Disabling or Enabling a Frequency Sweep . . . . . . . . . . . . . . . . . . . . . . . 13-45
Disabling and Enabling an Analysis Setup . . . . . . . . . . . . . . . . . . . . . . . 13-46
Specifying the Number of Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-47
Specifying the Desired RAM Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-48
Specifying the Hard Memory Limit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-49
14. Running Simulations
Solving a Single Setup or Sweep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Running More Than One Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Monitoring Queued Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6
Remote Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-7
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-10
Distributed Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Configuring Distributed Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-12
Editing Distributed Machine Configurations . . . . . . . . . . . . . . . . . . . . . 14-13
Selecting an Optimal Configuration for Distributed Analysis . . . . . . . . 14-17
Monitoring the Solution Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18
High Performance Computing (HPC) Integration . . . . . . . . . . . . . . . . . . 14-20
Scheduler Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20
What a Scheduler Does . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-21
Installation of Ansoft Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22
Firewall Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Installation Directory Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Ansoft Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23
Integration with Microsoft Windows® HPC Scheduler . . . . . . . . . . . . 14-24
Windows® HPC Job Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25
Windows® HPC Task Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26
Windows® HPC Job Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28
Selecting Computation Resource Units (Job Unit Type) . . . . . . . . . . . . . . 14-29
How to Select the Windows® HPC Job Unit Type . . . . . . . . . . . . . . . . . . 14-30
Windows® HPC Job Credentials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-30
Submitting and Monitoring Ansoft HPC Jobs . . . . . . . . . . . . . . . . . . . . 14-31
Submitting and Monitoring Jobs Using the Ansoft Submit HPC Job
Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-32
The Ansoft Submit HPC Job Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-35
Contents - 17
Specifying the Number of Compute Resource Units for HPC Jobs . . . . . 14-37
Integration with Platform’s Load Sharing Facility (LSF) . . . . . . . . . . . 14-38
Installation of Ansoft Tools on LSF Cluster . . . . . . . . . . . . . . . . . . . . . . . 14-39
Integration of Ansoft Products with LSF . . . . . . . . . . . . . . . . . . . . . . . . . . 14-41
LSF Job Submission Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-41
LSF Command Used to Launch Remote Engine Processes . . . . . . . . . . . . 14-42
Submitting Ansoft LSF Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-42
Current Working Directory with LSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-42
Quoting Ansoft Command or Arguments for LSF . . . . . . . . . . . . . . . . . . . 14-43
bsub Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-43
Monitoring Ansoft LSF Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-43
Terminating Ansoft LSF Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-44
Example LSF bsub Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-44
Known Issues for LSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-48
Troubleshooting for LSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-49
Workarounds for LSF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-50
Integration with PBS (Portable Batch System) Professional from
Altair Engineering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-50
qsub Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-52
Monitoring Ansoft PBS Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-53
Example PBS qsub Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-53
Integration with Sun Grid Engine (SGE) . . . . . . . . . . . . . . . . . . . . . . . . 14-55
Monitoring Ansoft SGE Batch Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-58
Ansoft Desktop -monitor Command Line Option for SGE . . . . . . . . . . . . 14-58
Example SGE qsub Command Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-59
Issue with qrsh (SGE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-61
Issue with MainWin Core Services for SGE . . . . . . . . . . . . . . . . . . . . . . . 14-61
Command Line Enhancements for Ansoft Desktop Products . . . . . . . . 14-63
Integrating Ansoft Tools with Third Party Schedulers . . . . . . . . . . . . . 14-65
Build Information for Scheduler Proxy Library . . . . . . . . . . . . . . . . . . . . . 14-65
Implementation Details for Custom Scheduler Integration . . . . . . . . . . . . 14-66
IsProductLaunchedInYourEnvironment . . . . . . . . . . . . . . . . . . . . . . . . . . 14-66
GetTempDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-67
GetMachineListAvailableForDistribution . . . . . . . . . . . . . . . . . . . . . . . . . 14-67
LaunchProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-68
GetUseRsmForEngineLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-69
GetThisJobID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-70
GetSchedulerDisplayName . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-70
Testing Your Scheduler Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-71
Testing IsProductLaunchedInYourEnvironment . . . . . . . . . . . . . . . . . . . . 14-72
Testing GetSchedulerDisplayName and GetThisJobID . . . . . . . . . . . . . . . 14-72
Testing GetTempDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-72
Testing GetMachineListAvailableForDistribution . . . . . . . . . . . . . . . . . . 14-72
Contents - 18
Testing LaunchProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-73
Testing GetUseRsmForEngineLaunch . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-73
Troubleshooting Custom Scheduler Integration . . . . . . . . . . . . . . . . . . 14-73
None of the Proxy Functions are Called . . . . . . . . . . . . . . . . . . . . . . . . . . 14-74
Troubleshooting IsProductLaunchedInYourEnvironment Function . . . . . 14-74
Troubleshooting GetSchedulerDisplayName . . . . . . . . . . . . . . . . . . . . . . . 14-74
Troubleshooting GetThisJobID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-75
Troubleshooting GetTempDirectory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-75
Troubleshooting GetMachineListAvailableForDistribution . . . . . . . . . . . 14-75
Troubleshooting LaunchProcess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-75
Troubleshooting GetUseRsmForEngineLaunch . . . . . . . . . . . . . . . . . . . . 14-76
Changing a Solution Priority for System Resources . . . . . . . . . . . . . . . . 14-77
Aborting an Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-78
Re-solving after Modifying a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-79
Re-Solving after ANSYS Thermal Link Feedback . . . . . . . . . . . . . . . . . 14-80
15. Optimetrics
Parametric Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Setting Up a Parametric Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Adding a Variable Sweep Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-4
Specifying Variable Values for a Sweep Definition . . . . . . . . . . . . . . . . . 15-6
Synchronizing Variable Sweep Definitions . . . . . . . . . . . . . . . . . . . . . . . . 15-6
Modifying a Variable Sweep Definition Manually . . . . . . . . . . . . . . . . 15-7
Overriding a Variable's Current Value in a Parametric Setup . . . . . . . . 15-8
Specifying a Solution Setup for a Parametric Setup . . . . . . . . . . . . . . . 15-8
Specifying the Solution Quantity to Evaluate for Parametric Analysis . . . 15-9
Setup Calculations for Optimetrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-9
Specifying a Solution Quantity's Calculation Range . . . . . . . . . . . . . . . . . 15-11
Viewing Results for Parametric Solution Quantities . . . . . . . . . . . . . . . 15-11
Using Distributed Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-12
Adding a Parametric Sweep from a File . . . . . . . . . . . . . . . . . . . . . . . . 15-13
Optimization Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Choosing an Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Quasi Newton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-15
Pattern Search . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-18
Sequential Non-linear Programming (SNLP) . . . . . . . . . . . . . . . . . . . . . . 15-20
Sequential Mixed Integer NonLinear Programming . . . . . . . . . . . . . . . . . 15-21
Genetic Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-22
Optimization Variables and the Design Space . . . . . . . . . . . . . . . . . . . . 15-23
Setting Up an Optimization Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-24
Optimization Setup for the Quasi Newton Optimizer . . . . . . . . . . . . . . 15-25
Optimization Setup for the Pattern Search Optimizer . . . . . . . . . . . . . . 15-26
Contents - 19
Optimization Setup for the SNLP Optimizer . . . . . . . . . . . . . . . . . . . . . 15-27
Optimization Setup for the SMINLP Optimizer . . . . . . . . . . . . . . . . . . 15-28
Optimization Setup for the Genetic Algorithm Optimizer . . . . . . . . . . . 15-29
Setting the Maximum Iterations for an Optimization Analysis . . . . . . . 15-30
Cost Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-31
Acceptable Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-32
Cost Function Noise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-32
Adding a Cost Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-32
Adding/Editing a Cost Function Calculation . . . . . . . . . . . . . . . . . . . 15-34
Specifying a Solution Quantity for a Cost Function Goal . . . . . . . . . 15-35
Setting the Calculation Range of a Cost Function Goal . . . . . . . . . . . 15-35
Setting a Goal Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-36
Specifying a Single Goal Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-36
Specifying an Expression as a Goal Value . . . . . . . . . . . . . . . . . . . . . 15-37
Specifying a Variable-Dependent Goal Value . . . . . . . . . . . . . . . . . . 15-37
Goal Weight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-37
Modifying the Starting Variable Value for Optimization . . . . . . . . . . . 15-39
Setting the Min. and Max. Variable Values for Optimization . . . . . . . . 15-39
Overriding the Min. and Max. Variable Values for a Single
Optimization Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
Changing the Min. and Max. Variable Values for Every Optimization
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
Step Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-40
Setting the Min. and Max. Step Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-42
Setting the Min and Max Focus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-42
Equalizing the influence of different optimization variables. . . . . . . . . . . 15-43
To set the Min and Max Focus values: . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-43
Solving a Parametric Setup Before an Optimization . . . . . . . . . . . . . . . 15-43
Solving a Parametric Setup During an Optimization . . . . . . . . . . . . . . . 15-44
Automatically Updating a Variable's Value After Optimization . . . . . . 15-44
Changing the Cost Function Norm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-44
Explanation of L1, L2 and Max norms in Optimization . . . . . . . . . . . . . . 15-45
Example of a More Complex Cost Function . . . . . . . . . . . . . . . . . . . . . . . 15-47
Advanced Genetic Algorithm Optimizer Options . . . . . . . . . . . . . . . . . 15-48
Sensitivity Analysis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-51
Selecting a Master Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-51
Setting Up a Sensitivity Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-52
Setting the Maximum Iterations Per Variable . . . . . . . . . . . . . . . . . . . . 15-53
Setting Up an Output Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-53
Specifying a Solution Quantity for an Output Parameter . . . . . . . . . . . . . 15-54
Setting the Calculation Range of an Output Parameter . . . . . . . . . . . . . . . 15-55
Modifying the Starting Variable Value for Sensitivity Analysis . . . . . . 15-55
Contents - 20
Setting the Min. and Max. Variable Values . . . . . . . . . . . . . . . . . . . . . . 15-56
Overriding the Min. and Max. Variable Values for a Single Sensitivity
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-56
Changing the Min. and Max. Variable Values for Every Sensitivity
Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-57
Setting the Initial Displacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-57
Solving a Parametric Setup Before a Sensitivity Analysis . . . . . . . . . . 15-57
Solving a Parametric Setup During a Sensitivity Analysis . . . . . . . . . . 15-58
Statistical Analysis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-59
Setting Up a Statistical Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-60
Setting the Maximum Iterations for a Statistical Analysis . . . . . . . . . . 15-60
Specifying the Solution Quantity to Evaluate for Statistical Analysis . 15-61
Setting the Solution Quantity's Calculation Range . . . . . . . . . . . . . . . . 15-62
Setting the Distribution Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-62
Overriding the Distribution Criteria for a Single Statistical Setup . . . . . . 15-63
Changing the Distribution Criteria for Every Statistical Setup . . . . . . . . . 15-64
Statistical Cutoff Probability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-65
Edit Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-66
Modifying the Starting Variable Value for Statistical Analysis . . . . . . 15-67
Solving a Parametric Setup During a Statistical Analysis . . . . . . . . . . . 15-68
Tuning Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-69
Tuning a Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-70
Applying a Tuned State to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-72
Saving a Tuned State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-72
Reverting to a Saved Tuned State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-73
Resetting Variable Values after Tuning . . . . . . . . . . . . . . . . . . . . . . . . . 15-73
Saving Field Solutions for Optimetrics Analyses . . . . . . . . . . . . . . . . . . 15-74
Saving Field Solutions for a Parametric Setup . . . . . . . . . . . . . . . . . . . 15-74
Saving Field Solutions for an Optimization Setup . . . . . . . . . . . . . . . . . 15-74
Saving Field Solutions for a Sensitivity Setup . . . . . . . . . . . . . . . . . . . . 15-75
Saving Field Solutions for a Tuning Analysis . . . . . . . . . . . . . . . . . . . . 15-75
Saving Field Solutions for a Statistical Setup . . . . . . . . . . . . . . . . . . . . 15-76
Copying Meshes in Optimetrics Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . 15-77
Adding an Expression in the Output Variables Window . . . . . . . . . . . . . 15-78
Excluding a Variable from an Optimetrics Analysis . . . . . . . . . . . . . . . . 15-79
Modifying the Value of a Fixed Variable . . . . . . . . . . . . . . . . . . . . . . . . 15-80
Linear Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-81
Setting a Linear Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-81
Modifying a Linear Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-82
Deleting a Linear Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-82
Contents - 21
Running an Optimetrics Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-84
Viewing Analysis Results for Optimetrics Solutions . . . . . . . . . . . . . . . 15-85
Viewing Solution Data for an Optimetrics Design Variation . . . . . . . . 15-85
Viewing an Optimetrics Solution's Profile Data . . . . . . . . . . . . . . . . . . 15-86
Viewing Results for Parametric Solution Quantities . . . . . . . . . . . . . . . 15-86
Plotting Solution Quantity Results vs. a Swept Variable . . . . . . . . . . . . . . 15-87
Viewing Cost Results for an Optimization Analysis . . . . . . . . . . . . . . . 15-87
Plotting Cost Results for an Optimization Analysis . . . . . . . . . . . . . . . . . . 15-88
Viewing Output Parameter Results for a Sensitivity Analysis . . . . . . . 15-88
Plotting Output Parameter Results for a Sensitivity Analysis . . . . . . . . . . 15-88
Viewing Distribution Results for a Statistical Analysis . . . . . . . . . . . . . 15-89
Plotting Distribution Results for a Statistical Analysis . . . . . . . . . . . . . . . 15-90
Link to Design Xplorer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-91
16. Post Processing and Generating Reports
Viewing Solution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Viewing Convergence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
Viewing the Number of Completed Passes . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Viewing the Max Magnitude of Delta S Between Passes . . . . . . . . . . . . . 16-3
Viewing the Output Variable Convergence . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Viewing the Delta Magnitude Energy . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-4
Viewing the Magnitude Margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Viewing the Phase Margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Viewing the Max Delta (Mag S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-5
Viewing the Max Delta (Phase S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Viewing the Maximum Delta Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . 16-6
Plotting Convergence Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Viewing a Solution Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-7
Viewing Matrix Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-9
Selecting the Matrix Display Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-10
Exporting Matrix Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-11
Renaming Matrix Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Reordering Matrix Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Exporting Equivalent Circuit Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-14
Exporting W-element Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-17
Viewing Mesh Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-17
Viewing Eigenmode Solution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-18
Deleting Solution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
Deleting Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-19
Export Transfer File for ANSYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-21
Exporting the Model Geometry to ANSYS Workbench . . . . . . . . . . . . . . 16-24
Creating the Thermal Link Coupling File . . . . . . . . . . . . . . . . . . . . . . . . . 16-24
Contents - 22
Scaling a Source's Magnitude and Phase . . . . . . . . . . . . . . . . . . . . . . . . . 16-27
Guidelines for Scaling a Source's Magnitude and Phase . . . . . . . . . . . . 16-29
Ports and Edit Sources Behavior for Transient Network . . . . . . . . . . . 16-30
Creating Animations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31
Creating Phase Animations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-31
Creating Frequency Animations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-32
Creating Geometry Animations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-33
Controlling the Animation’s Display . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-34
Exporting Animations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-35
Creating Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-37
Creating a Quick Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-38
Creating a New Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-39
Context Section for Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-41
Using Families Tab for Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-42
Modifying Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-44
Modifying the Background Properties of a Report . . . . . . . . . . . . . . . . 16-46
Modifying the Legend in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-48
Creating Custom Report Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-49
Selecting the Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-50
Selecting the Display Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-51
Creating 2D Rectangular Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-52
Creating 2D Rectangular Stacked Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-54
Creating 3D Rectangular Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-56
Creating Rectangular Contour Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-57
Creating 2D Polar Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-58
Reviewing 2D Polar Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-60
Creating 3D Polar Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-60
Creating Smith Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-61
Creating Smith Contour Charts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-62
Creating Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-64
Creating Radiation Patterns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-66
Delta Markers in 2D Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-67
Plotting in the Time Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-67
TDR Windowing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-72
Working with Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-77
Editing Trace Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-78
Editing the Display Properties of Traces . . . . . . . . . . . . . . . . . . . . . . . . . . 16-79
Adding Data Markers to Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-81
Discarding Report Values Below a Specified Threshold . . . . . . . . . . . . . . 16-82
Add Trace Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-83
Removing Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-84
Copy and Paste of Report and Trace Definitions . . . . . . . . . . . . . . . . . . . . 16-84
Contents - 23
Copy and Paste of Report and Trace Data . . . . . . . . . . . . . . . . . . . . . . . . . 16-85
Sweeping a Variable in a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-86
Sweeping Values Across a Distance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-86
Sweeping Values Across a Sphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-87
Selecting a Function for a Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-88
Selecting Solution Quantities to Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-92
Selecting a Field Quantity to Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-94
Selecting a Far-Field Quantity to Plot . . . . . . . . . . . . . . . . . . . . . . . . . . 16-95
Plotting Vertical Cross-Sections of Far Fields . . . . . . . . . . . . . . . . . . . . 16-100
Plotting Horizontal Cross-Sections of Far Fields . . . . . . . . . . . . . . . . . 16-100
Selecting a Near-Field Quantity to Plot . . . . . . . . . . . . . . . . . . . . . . . . . 16-101
Selecting an Emission Test Quantity to Plot . . . . . . . . . . . . . . . . . . . . . 16-102
Plotting Imported Solution Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-103
Setting a Range Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-103
Eye Measurement Range Function Parameters . . . . . . . . . . . . . . . . . . . . . 16-104
Perform FFT on a Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-105
FFT Window Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-106
Apply FFT to Report Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-108
Perform TDR on Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-109
Specifying Output Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-110
Adding a New Output Variable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-110
Building an Expression Using Existing Quantities . . . . . . . . . . . . . . . . . . 16-111
Deleting Output Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-112
Derivative Tuning for Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-113
Port Field Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-115
Plotting Field Overlays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-117
Overlaying 3D Polar Plots on Models . . . . . . . . . . . . . . . . . . . . . . . . . . 16-119
Plotting Derived Field Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-120
Creating Scalar Field Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-121
Modifying SAR Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-121
Creating Vector Field Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-122
Modifying Field Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-122
Setting Field Plot Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-123
Modifying Field Plot Colors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-125
Setting the Color Key Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-126
Moving the Color Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-127
Modifying the Field Plot Scale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-127
Modifying Vector Field Plot Arrows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-129
Setting the Mesh Visibility on Field Plots . . . . . . . . . . . . . . . . . . . . . . . . . 16-130
Modifying Scalar Field Plot Isovalues . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-130
Mapping Scalar Field Plot Transparency to Field Values . . . . . . . . . . . . . 16-131
Modifying Markers on Point Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-131
Contents - 24
Modifying Line Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-132
Setting a Plot's Visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-133
Saving a Field Overlay Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-133
Opening a Field Overlay Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-134
Deleting a Field Overlay Plot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-134
Setting Field Plot Defaults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-134
Using the Fields Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-136
Opening the Fields Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-136
Context Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-138
The Calculator Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-138
Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-139
Enlarging the Register Display Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-139
Units of Measure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-140
Stack Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-140
Input Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-141
Quantity Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-141
Geometry Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-144
Constant Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-145
Number Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-146
Function Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-146
Geom Settings Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-147
Read Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-148
Output Vars [Input for Eigenmode problems] . . . . . . . . . . . . . . . . . . . . . . 16-148
General Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-148
Steps for Calculating the Complex Vector Electric Field . . . . . . . . . . . 16-151
Scalar Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-152
Vec? Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-152
1/x (Inverse) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-153
Pow Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-153
(Square Root) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-153
Trig . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-154
d/d? (Partial Derivative) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-154
(Integral) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-154
Min Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-155
Max Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-156
∇ (Gradient) Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-156
Ln Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-157
Log Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-157
Vector Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-157
Scal? Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-158
Matl Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-158
Mag Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-159
Dot Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-159
Contents - 25
Cross Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-160
Divg Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-160
Curl Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-160
Tangent Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-161
Normal Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-161
Unit Vec Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-162
Output Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-163
Value Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-163
Eval Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-163
Write Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-164
Export Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-165
Calculating Derived Field Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-167
Named Expression Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-168
Exiting the Fields Calculator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-170
Radiated Fields Post Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-171
Setting up a Near-Field Sphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-172
Setting up a Near-Field Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-173
Computing Maximum Near-Field Parameters . . . . . . . . . . . . . . . . . . . . 16-175
Setting up a Far-Field Infinite Sphere . . . . . . . . . . . . . . . . . . . . . . . . . . 16-176
Defining Antenna Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-177
Defining a Regular Antenna Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-178
Defining a Custom Antenna Array . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-179
Computing Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-179
Exporting Antenna Parameters and Maximum Field Data . . . . . . . . . . . . 16-181
Plotting the Mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-183
Setting Mesh Plot Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-183
17. Technical Notes
The Finite Element Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
Representation of a Field Quantity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-2
Rectilinear Elements and Curvilinear Elements . . . . . . . . . . . . . . . . . . 17-2
Basis Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-3
Size of Mesh Vs. Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-4
The HFSS Solution Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
The Mesh Generation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-5
Seeding the Mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Guidelines for Seeding the Mesh . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-6
Length-Based Mesh Refinement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Skin Depth-Based Mesh Refinement . . . . . . . . . . . . . . . . . . . . . . . . . 17-7
Surface Approximation Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-8
Guidelines for Modifying Surface Approximation Settings . . . . . . . . 17-9
Meshing Region Vs. Problem Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-9
Contents - 26
Model Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-10
Port Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
Excitation Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-11
Wave Equation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Mesh Refinement on Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-12
Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-13
Degenerate Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Multiple Ports on the Same Face . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Port Accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-14
Calculating Characteristic Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-15
Calculating the PI Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Calculating the PV Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Calculating the VI Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-16
Impedance Multipliers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Calculating Terminal Characteristic Impedance Matrix . . . . . . . . . . . 17-17
Complex Propagation Constant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-17
Calculating the Effective Wavelength (Lambda) . . . . . . . . . . . . . . . . 17-18
Calculating the Relative Permittivity (Epsilon) . . . . . . . . . . . . . . . . . 17-18
The Adaptive Analysis Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-18
Maximum Delta S . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Maximum Delta E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-19
Percent of Tetrahedra Refined Per Pass . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Magnitude Margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Phase Margin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Maximum Delta Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-20
Max Delta (Mag S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Max Delta (Phase S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Matrix Solvers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Direct Matrix Solver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-21
Iterative Matrix Solver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Guidelines for Using the Iterative Solver . . . . . . . . . . . . . . . . . . . . . . . . . . 17-22
Multiprocessing and the Iterative Solver . . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
Iterative Matrix Solver Technical Details . . . . . . . . . . . . . . . . . . . . . . . . . 17-23
Single Frequency Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-25
Frequency Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
Fast Frequency Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-26
Discrete Frequency Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-27
Interpolating Frequency Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-28
Solution Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-29
Eigenmode Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-30
Calculating the Resonant Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . 17-30
Calculating the Quality Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31
Field Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31
Contents - 27
Field Overlay Plots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-31
Field Quantities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-32
Specifying the Phase Angle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-33
Peak Versus RMS Phasors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-33
Calculating the SAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-34
Transient Solution Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-36
Discontinuous Galerkin Finite Element Method . . . . . . . . . . . . . . . . . . 17-36
Local Time Stepping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-37
Materials in Time Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-39
Excitations in Time Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-39
Analysis Setup in Time Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-44
References for Time Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-45
Domain Decomposition Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-47
Basic DDM Theory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-47
Computational Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-48
Computational Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-49
Integral Equation Method Used in HFSS-IE . . . . . . . . . . . . . . . . . . . . . . 17-50
S-Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-52
Post Processed S-Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-52
Renormalized S-Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-53
De-embedded S-Matrices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54
Alternative Matrix Characterizations . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54
Calculating the Z-Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-54
Calculating the Y-Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
Passivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-55
Radiated Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-56
Spherical Cross-Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-57
Maximum Near-Field Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-59
Maximum Far-Field Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-60
Array Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-61
Theory of the Array Factor Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-61
Regular Uniform Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-62
Scan Specification for Regular Uniform Arrays . . . . . . . . . . . . . . . . . 17-63
Custom Arrays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-63
Power Normalizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-65
Antenna Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-66
Polarization of the Electric Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-67
Spherical Polar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Ludwig-3 Polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Circular Polarization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Axial Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-68
Polarization Ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-69
Contents - 28
Max U . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-70
Peak Directivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-71
Peak Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-71
Peak Realized Gain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-72
Radiated Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-72
Accepted Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-73
Incident Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-74
Radiation Efficiency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-74
Decay Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-75
Calculating Finite Thickness Impedance . . . . . . . . . . . . . . . . . . . . . . . . . 17-76
Modes to Terminals Conversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-77
Calculating the W-Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-79
Terminal-Based Models for Circuit Analysis . . . . . . . . . . . . . . . . . . . . 17-80
Terminal Characteristic Impedance Matrix . . . . . . . . . . . . . . . . . . . . . . 17-81
Geometric Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-83
Bondwires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-83
Healing and Meshing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-84
Detecting and Addressing Model Problems to Improve Meshing . . . . . 17-86
One: Healing during geometry import . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-86
Two: Healing after geometry import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-87
Three: Removing Object Intersections . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-90
Four: Removing Small Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-91
Five: Aligning Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-92
Six: Troubleshooting if meshing still fails . . . . . . . . . . . . . . . . . . . . . . . . . 17-93
Handling Complicated Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-94
Interface Options for Complicated Models . . . . . . . . . . . . . . . . . . . . . . . . 17-94
Geometry Imperfections and Complicated Models . . . . . . . . . . . . . . . . . . 17-95
Object Overlap Settings for Complicated Models . . . . . . . . . . . . . . . . . . . 17-95
Post Processing for Complicated Models . . . . . . . . . . . . . . . . . . . . . . . . . . 17-95
Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-96
Perfect E Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-96
Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-96
Units of Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-97
Radiation Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-98
PML Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-99
Material Tensors Applied at PML Boundaries . . . . . . . . . . . . . . . . . . . . . 17-100
Tensor Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-101
Boundaries at PML Surfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-102
Finite Conductivity Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-102
Symmetry Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-103
Perfect E Vs. Perfect H Symmetry Boundaries . . . . . . . . . . . . . . . . . . . . . 17-103
Symmetry and Port Impedance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-104
Contents - 29
Symmetry and Multiple Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-104
Master and Slave Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-104
Calculating the E-Field on the Slave Boundary . . . . . . . . . . . . . . . . . . . . . 17-106
Screening Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-106
Lumped RLC Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-107
Layered Impedance Boundaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-107
Impedance Calculation for Layered Impedance Boundary . . . . . . . . . . . . 17-108
Surface Roughness Calculation for Impedance Boundary . . . . . . . . . . . . . 17-108
Infinite Ground Planes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-109
Frequency-Dependent Boundaries and Excitations . . . . . . . . . . . . . . . . 17-109
Implicit Boundary Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-110
General Approach for Scattered and Total Field Decomposition . . . . . . 17-111
Scattered and total field formulation pros and cons . . . . . . . . . . . . . . . . 17-111
Where the Solvers Apply Scattered or Total Field Formulations . . . . . 17-112
Summary for Total and Scattered Fields . . . . . . . . . . . . . . . . . . . . . . . . 17-114
Excitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-115
Wave Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-115
Mode Polarity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-116
Mode Alignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-116
Analytic Port Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-117
Lumped Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-118
Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-118
Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-120
Computing Differential Pairs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-120
Floquet Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-122
Formula Summary for HFSS Floquet Modes . . . . . . . . . . . . . . . . . . . . . . 17-122
Incident Waves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-126
Plane Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-126
Evanescent Plane Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-127
Electric Spherical Wave (Electric Hertzian Dipole) . . . . . . . . . . . . . . . . . 17-128
Magnetic Spherical Wave (Magnetic Hertzian Dipole) . . . . . . . . . . . . . . . 17-128
Cylindrical Wave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-129
Gaussian Beam . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-129
Linear Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-130
Voltage Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-131
Current Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-131
Magnetic Bias Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-132
Uniform Applied Bias Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-132
Non-uniform Applied Bias Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-133
Deembedding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-133
Materials Technical Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-140
Relative Permeability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-140
Contents - 30
Relative Permittivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-141
Bulk Conductivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-141
Dielectric Loss Tangent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-142
Magnetic Loss Tangent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-142
Ferrite Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-142
Magnetic Saturation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-142
Lande G Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-143
Delta H . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-143
Anisotropic Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-143
Anisotropic Relative Permeability Tensors . . . . . . . . . . . . . . . . . . . . . . . . 17-144
Anisotropic Relative Permittivity Tensors . . . . . . . . . . . . . . . . . . . . . . . . . 17-145
Anisotropic Conductivity Tensors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-145
Anisotropic Dielectric Loss Tangent Tensors . . . . . . . . . . . . . . . . . . . . . . 17-146
Anisotropic Magnetic Loss Tangent Tensors . . . . . . . . . . . . . . . . . . . . . . . 17-147
Anisotropic Materials and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-148
Frequency-Dependent Material Properties . . . . . . . . . . . . . . . . . . . . . . 17-148
Debye Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-149
18. Scripting
Recording a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Stopping Script Recording . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Running a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Pausing and Resuming a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Stopping a Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-3
19. ANSYS Workbench Integration Overview
Integrating Ansoft Products with ANSYS Workbench13.0 . . . . . . . . . . 19-1
Integration with ANSYS 13.0 During Ansoft Product Installation . . . . 19-2
Integration with ANSYS 13.0 after Ansoft Product Installation . . . . . . 19-3
Workbench Data Integration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Adding New Ansoft Analysis Systems . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Importing Ansoft Projects into ANSYS Workbench . . . . . . . . . . . . . . . 19-8
Editing Ansoft Models in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Analyzing Ansoft Models in Workbench . . . . . . . . . . . . . . . . . . . . . . . 19-10
Performing Parameter Studies in Workbench . . . . . . . . . . . . . . . . . . . . 19-11
Scripting in Workbench . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Ansoft - ANSYS Multiphysics Coupling . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Multiphysics Coupling on Workbench with ANSYS Thermal . . . . . . . 19-13
Multiphysics Coupling on Workbench with ANSYS Structural . . . . . . 19-14
Multiphysics Coupling between Ansoft Field Systems on Workbench 19-15
20. Glossaries
Contents - 31
Contents - 32
1
Getting Started with HFSS
HFSS is an interactive software package for calculating the electromagnetic behavior of a structure.
The software includes post-processing commands for analyzing this behavior in detail.
Using HFSS, you can compute:
• Basic electromagnetic field quantities and, for open boundary problems, radiated near and far
fields.
• Characteristic port impedances and propagation constants.
• Generalized S-parameters and S-parameters renormalized to specific port impedances.
• The eigenmodes, or resonances, of a structure.
You are expected to draw the structure, specify material characteristics for each object, and identify
ports and special surface characteristics. HFSS then generates the necessary field solutions and
associated port characteristics and S-parameters.
Note If you are using the Eigenmode Solution solver, you do not need to specify sources for
the problem. HFSS calculates the resonances for the model based on the geometry,
materials, and boundaries.
As you set up the problem, HFSS allows you to specify whether to solve the problem at one spe-
cific frequency or at several frequencies within a range.
System Requirements
HFSS supports the following operating systems:
• Windows
• Linux
For details regarding which revisions of each of these operating systems are supported; as well as,
memory and disk requirements and known issues at the time of shipping, consult the read me file
shipped with this release of the software by clicking the link below:
.
On all systems when you run HFSS for the first time (that is, with no project directory specified in
the registry), or if the project directory or the temp directory does not exist, HFSS displays a dialog
that asks you to set the project and temp directories. For the temp directory, there is a comment ask-
ing you to ensure that adequate disk space is available.
HFSS 13 requires at least FLEXlm for Ansoft v10.8.5 license server.
Note If you attempt to run HFSS and get a message reporting a corrupted license file, please
contact Ansoft.
Note HFSS displays a warning message if the license file expires within 15 days.
Note All operating systems must have 32-bit OpenGL libraries installed regardless of whether
the OS is 32-bit or 64-bit.
Windows
Supported Platforms
• Windows XP Professional (32-bit and 64-bit)
• Windows Server 2003 (32-bit and 64-bit)
• Windows Vista Service Pack 1 (32-bit and 64-bit)
32-Bit System Requirements
Minimum System Requirements
Processor: All fully compatible 686 (or later) instruction set processors, 500 MHz
Hard Drive Space (for HFSS software): 200 MB
RAM: 512 MB
Recommended Minimum Configuration
Processor: All fully compatible 786 (or later) instruction set processors, 1 GHz
Hard Drive Space (for HFSS software and temporary files): 500 MB
RAM: 2 GB
Increasing RAM on 32-Bit PC
1-2 Getting Started with HFSS
HFSS Online Help
Users with the appropriate Windows OS can take advantage of potentially all the installed
RAM up to a limit of 3 GB on 32-bit PCs. Doing so also requires setting up the appropriate OS
boot.ini switch (/3GB) to tell the OS that 3 GB is to be used for application space and only one
GB for the OS kernel and related overhead.
Note If you are using the NVIDIA Quadro2 MXR/EX video card on Windows 2000 or
Windows XP, you should also download Version 40.41 or greater video driver, available
for download at http://www.nvidia.com.
Warning Windows Vista (32-bit and 64-bit) is supported in limited capacity for this release.
Ansoft will attempt to assist with any problems or questions you may have but
cannot guarantee full compatibility with Windows Vista.
If you are running the Windows Vista 32-bit Operating System, you can take advantage of poten-
tially all the installed RAM up to a limit of 3GB on 32-bit machines. On Windows Vista, the /3gb
switch has been replaced with an option called increaseuserva. You must edit its value using the
bcdedit utility.
If you type bcdedit from a Windows command prompt, you will see the current values for the Boot
Manager and Boot Loader. If you do not have increaseuserva set, then you will not see this line in
the boot loader output.
To set increaseuserva to 3GB:
1. Open a Command Prompt window.
2. Type bcdedit /set increaseuserva 3072 in the Command Prompt window and press
Enter.
To delete the increaseuserva setting, which will revert the OS back to 2GB:
1. Open a Command Prompt window.
2. Type bcdedit /deletevalue increaseuserva in the Command Prompt window and press
Enter.
Note You must edit this value as an administrator. If you have User Access Control enabled,
then you must start the command prompt in elevated mode. To do this, find the
Command Prompt in the Windows Start menu, right-click on it, and choose Run as
Administrator.
Linux
If you attempt to open an HFSS v9 project in Linux, you receive an error message that the project
must first be converted to HFSS v11. This must be done using the -BatchSave command on a non-
Linux system running HFSS v11. See the discussion here.
Supported Platforms
• Red Hat Enterprise Linux v4 and v5
• SUSE Linux Enterprise Server v10 and v11.
32-bit System Requirements
Minimum System Requirements:
Processor: All fully compatible 686 (or later) instruction set processors, 500 MHz Hard Drive
Space (for HFSS software): 200 MB
RAM: 512 MB
Recommended Minimum Configuration (for Optimal Performance):
Processor: All fully compatible 786 (or later) instruction set processors, 2 GHz Hard Drive Space
(for HFSS software and temporary files): 700 MB
RAM: 4 GB
64-bit System Requirements
Minimum System Requirements:
Supported processors: AMD Athlon 64, AMD Opteron, Intel Xeon with Intel EM64T support, Intel
Pentium 4 with Intel EM64T support Hard Drive Space (for HFSS software): 200 MB
RAM: 2 MB
Recommended Minimum Configuration (for Optimal Performance):
Supported processors: AMD Athlon 64, AMD Opteron, Intel Xeon with Intel EM64T support, Intel
Pentium 4 with Intel EM64T support Video card: 128-bit SVGA or PCI Express video card Hard
Drive Space (for HFSS software and temporary files): 700 MB
RAM: 8 GB
Setting Up a Printer on Linux
To print from Ansoft software on Linux, you must first configure a printer. To do this, launch the
MainWin control panel.
1. Run mwcontrol & in the installation subdirectory.
Note On Solaris you setup a new print queue by running "lpadmin" (as root). On Red Hat
Linux, you can run 'System Settings/Printing' to launch printconf-gui (as root).
6. Click Next.
The Print Command dialog appears.
7. Change the Print Command only if instructed to do so by your user administrator.
8. Click Next.
The Choose PPD File dialog appears.
9. Select your printer manufacturer and model from the list or use the Choose File button to
browse to a PPD file provided by your printer manufacturer. Click Next.
The Printer Name dialog appears.
10. Enter a Name to identify the printer. Click Next.
11. Choose whether this printer should be the default and click Next.
12. Choose whether you would like to print a test page and click Next.
13. In the Finish Adding New Printer dialog, verify the printer setup information. If the informa-
tion is incorrect, use the Back button to return to the appropriate dialog and correct the entry. If
the information is correct, click Finish to complete the setup of your printer.
With a print queue setup, and the printer added, you should then see the printer when running the
software.
• With the Online Help Index tab selected, search the help index.
• With the Online Help Search tab selected, search the full help text.
• With Online Help Favorites tab selected, create a custom list of favorite topics.
• With the Online Help Search tab selected, search the full help text.
• With Online Help Favorites tab selected, create a custom list of favorite topics.
Antennas in HFSS
Click graphics for descriptions of the following HFSS and HFSS-IE antenna examples:
RF/Microwave in HFSS
Click graphics for descriptions of the following HFSS RF/Microwave examples:
Also see: Application Specific Modeling Guide: Spiral Inductors on Silicon Substrate
Project
Manager
Property window
Message Manager
Status bar
Progress window
Related Topics
Getting Help
Keyboard Shortcuts for HFSS General Purposes
Keyboard shortcuts for the 3D Modeler Window.
Showing and Hiding Windows
The View menu contains commands that let you show and hide the windows that comprise the
desktop. You can show or hide the Status Bar, the Message Manager, the Project Manager, the
docked Properties window, and the Progress window.
The shortcut menu in the toolbar area also lets you show and hide each desktop window.
You can also close the windows by clicking the "x" in the window title bar.
Related Topics
HFSS Desktop
Moving and Resizing Desktop Windows
Moving and Resizing Desktop Windows
You can customize the appearance of the desktop by moving and resizing the Status Bar, the Mes-
sage Manager, the Project Manager, the docked Properties window, and the Progress window.
To move one of these windows:
1. Click and hold on the title bar.
2. Drag the cursor towards the region where you want to place the window.
A rectangle shape follows the cursor. As you drag the rectangle to different parts of the desk-
top, the changes in dimension show when you have reached a location where you can place the
window. This can be at the top, left, bottom, and side of the modeler window. You can place a
window next to another, as well as above or below another.
If you drag the window to the center of the 3D Modeler window, you can place it there as a
floating window.
3. Release the mouse button to place the window.
You can also resize the windows in two ways.
• To size a desktop window, place the cursor over an edge of the window. Over the inner-edges,
for sizing a window within the desktop, the cursor changes to a double bar with arrows point-
ing each direction. Over the outer-edges, for sizing the desktop, the cursor changes to a line
with arrows pointing each direction. Press and drag to size the window.
• To expand a window to fill the horizontal or vertical space it shares with another window, click
the triangle in the window title bar. When you expand a window, the triangle appears as
inverted and any other windows in the same horizontal or vertical space are compressed to
only the title bar. If a window does not share a horizontal or vertical space with another, the tri-
Related Topics
Desktop
Showing and Hiding Windows
Working with the Menu Bar
The menu bar enables you to perform all HFSS tasks, such as managing project files, customizing
the desktop, drawing objects, and setting and modifying all project parameters.
To open a help topic about an HFSS menu command, press Shift+F1, and then click the command
or toolbar icon.
HFSS contains the following menus, which appear at the top of the desktop:
File menu Use the File menu commands to manage HFSS project files and printing
options.
Edit menu Use the Edit menu commands to modify the objects in the active model and
undo and redo actions.
View menu Use the View menu commands to display or hide desktop components and
model objects, modify 3D Modeler window visual settings, and modify the
model view.
Project menu Use the Project menu commands to add an HFSS or HFSS-IE design to the
active project, view, define datasets, and define project variables.
Draw menu Use the Draw menu commands to draw one-, two-, or three-dimensional
objects, and sweep one- and two-dimensional objects.
Modeler menu Use the Modeler menu commands to import, export, and copy Ansoft 2D
Modeler files and 3D Modeler files; assign materials to objects; manage the
3D Modeler window’s grid settings; define a list of objects or faces of objects;
control surface settings; perform boolean operations on objects; and set the
units for the active design.
HFSS menu Use the HFSS menu to setup and manage all the parameters for the active
project. Most of these project properties also appear in the project tree.
Tools menu Use the Tools menu to modify the active project’s material library, arrange the
material libraries, run and record scripts, update project definitions from
libraries, customize the desktop’s toolbars, and modify many of the software’s
default settings.
Window menu Use the Window menu commands to rearrange the 3D Modeler windows and
toolbar icons.
Help menu Use the Help menu commands to access the online help system and view the
current HFSS version information.
Related Topics
Getting Help
Keyboard Shortcuts for General Purposes
Keyboard shortcuts for the 3D Modeler Window.
Related Topics
Customize Toolbar Options
Customize Toolbar Commands
Related Topics
Working with Toolbars
Customize Toolbar Commands
3. To add a custome Tools menu entry, click the Add button in the Customize User Tools Menu
dialog.
This enables the following fields:
Menu Text field -- this displays [new tool] as text you will replace with the text you want to
appear in the User Tools menu.
Command field -- this will display the external executable. An ellipsis button [...] lets you
navigate to the file location.
Arguments field -- this field accepts command arguments from the > button menu selections
for File Path, File Directory, File Name, File Extension, Project Directory, or Temp Directory.
Initial Directory -- this field specifies the initial directory for the command to operate. The
ellipsis button {...] displays a dialog that lets you navigate folders in your desktop, or across
the network.
4. Click OK to add the External Tools menu to HFSS or Cancel to close the dialog without
changes.
You can also add scripts to the Tools menu. Assuming you have a script to generate custom reports
called report.vbs, use the cscript.exe program to execute your script.
This example shows the cscript.exe program added to the Tools menu as Run My Script. The
command line argument to the csscript.exe program is report.vbs. You can also name the directory
in which it will be run.
Related Topics
Scripting
Note All of the commands on the shortcut menus are also available on the menu bar.
A check box will appear next to a command if the item is visible. For example, if a check box
appears next to the Project Manager command, then the Project Manager window is currently
visible on the desktop.
Click Customize to open the Customize dialog box, which enables you to modify the toolbar set-
tings on the desktop.
Shortcut Menu in the 3D Modeler Window
Use the shortcut menu in the 3D Modeler window to select, magnify, and move options (zoom,
rotate, etc.), change the view, perform boolean operations, assign materials, boundaries, excita-
tions, or mesh operations to objects, and work with field overlays.
To access the shortcut menu in the 3D Modeler window:
• CTRL + V: Paste
• CTRL + X: Cut
• CTRL + Y: Redo
• CTRL + Z: Undo
• CTRL + 0: Cascade windows
• CTRL + 1: Tile windows horizontally
• CTRL + 2: Tile windows vertically
To customize the shortcut assignments, use Tools>Keyboard Shortcuts.
Related Topics
Keyboard Shortcuts for the 3D Modeler Window
Custom Keyboard Shortcuts
Custom Keyboard Shortcuts
Click Tools>Keyboard Shortcuts to display a dialog that lets you view existing assignments, cre-
ate new shortcuts, save and load assignment files.
Selecting a Command category lists the available commands for that category. If the command has
an assigned shortcut, it is displayed on the Shortcuts for the selected command field. You can use
the Remove button to disable the shortcut for the selected command. If the selected command does
not have an assigned shortcut, the Shortcuts for selected command field and the Remove button are
greyed out.
To create a new shortcut key:
1. Select the Category and Command.
2. If you want disable a current assignment for the selected command, click Remove.
3. To assign a keyboard shortcut, place the cursor in the Press new shortcut key field.
The field displays the keystrokes you make. When you have made keystrokes, the dialog
enables the Assign button. If you combine keystrokes these are displayed with a “+” between
them. For example, Ctrl + p or Alt +o.
4. The Use new shortcut in field displays Global by default, which means that the shortcut will
apply to all applicable contexts, including HFSS and HFSS-IE. If a limited context exists, the
menu will offer a selection.
5. When you have made the assignments you want to make, You can save the assignments to a
named file.
Clicking the Save... button displays a browser window that lets you navigate the file structure
and assign a name, using an aks suffix for Ansoft Keyboard Shortcut file.
Buttons on the browser window let you designate the file location as Use Path, Personallib,
Syslib, UserLib, or Project folder.
If you have an existing aks file, you can use the Load... button to display a browser window to
locate the desired file.
6. You can OK the current settings, or Reset to Default.
Related Topics
Keyboard Shortcuts for HFSS General Purposes
Keyboard Shortcuts for the 3D Modeler Window
The Project Manager window displays details about all open HFSS projects. Each project ulti-
mately includes a geometric model, its boundary conditions and material assignments, and field
solution and post-processing information.
-27
To show or hide the Project Manager window, do one of the following:
• Click View> Project Manager.
A check box appears next to this command if the Project Manager window is visible.
• Right-click in the toolbars area on the desktop, and then click Project Manager on the short-
cut menu.
A check box appears next to this command if the Project Manager window is visible.
Related Topics
Working with the Project Tree
Shortcut Menus in the Project Manager Window
Working with the Project Tree
The project tree is located in the Project Manager window and contains details about all open
HFSS projects, as shown below:
The top node listed in the project tree is the project name. It is named Projectn by default, where n
is the order in which the project was added to the current session of HFSS. Expand the project icon
to view all the project’s HFSS design information and material definitions.
Related Topics
Viewing HFSS Design Details
Setting the Project Tree to Expand Automatically
You can set the project tree to automatically expand when an item is added to a project.
1. Click Tools > Options>General Options.
The Options dialog box appears.
2. Under the Project Options tab, select Expand Project Tree on Insert.
-28
Viewing HFSS Design Details
Once you insert an HFSS design into a project, it is listed as the second node in the project tree. It is
named HFSSModeln by default, where n is the order in which the design was added to the project.
Expand the design icon in the project tree to view all of the specific data about the model, including
its boundary conditions and material assignments, and field solution and post-processing informa-
tion.
The HFSSModeln node contains the following project details:
Boundaries Displays the boundary conditions assigned to an HFSS design, which
specify the field behavior at the edges of the problem region and object
interfaces.
Excitations Displays the excitations assigned to an HFSS design, which are used to
specify the sources of electromagnetic fields and charges, currents, or
voltages on objects or surfaces in the design.
Mesh Operations Displays the mesh operations specified for objects or object faces. Mesh
operations are optional mesh refinement settings that are specified before a
mesh is generated.
Analysis Displays the solution setups for an HFSS design. A solution setup specifies
how HFSS will compute the solution.
Optimetrics Displays any Optimetrics setups added to an HFSS design.
Results Displays any post-processing reports generated.
Port Field Display Displays all port fields in the active model.
Field Overlays Displays field overlay plots, which are representations of basic or derived
field quantities on surfaces or objects.
Plot folders are listed under Field Overlays. These folders store the
project’s plots and can be customized. See Setting Field Plot Defaults for
information on how to customize the plot folders.
Radiation Displays far- and near-field setups added to an HFSS design.
-29
Model Displays the objects that comprise the model and their properties.
Boundaries Displays the boundary conditions assigned to an HFSS design, which
specify the field behavior at the edges of the problem region and object
interfaces.
Excitations Displays the excitations assigned to an HFSS design, which are used to
specify the sources of electromagnetic fields and charges, currents, or
voltages on objects or surfaces in the design.
Mesh Operations Displays the mesh operations specified for objects or object faces. Mesh
operations are optional mesh refinement settings that are specified before a
mesh is generated.
Analysis Setup Displays the solution setups for an HFSS design. A solution setup specifies
how HFSS will compute the solution.
-30
Related Topics
Opening the Properties Window
Showing and Hiding the Properties Window
Setting the Properties Window to Open Automatically
Modifying Object Attributes using the Properties Window
Modifying Object Command Properties Using the Properties Window
Opening the Properties Window
1. Select the object whose properties you want to view.
2. Click Edit>Properties.
The Properties window for that object appears.
3. When you are finishing making changes, click OK.
Rather than opening a separate window, you can also view an object's properties if you have the
Properties window displayed within the desktop.
Related Topics
Showing and Hiding the Properties Window
Setting the Properties Window to Open Automatically
Modifying Object Attributes using the Properties Window
Modifying Object Command Properties Using the Properties Window
-31
Showing and Hiding the Properties Window
To show or hide the Properties window on the desktop, do one of the following:
• Click View> Property Window.
A check box appears next to this command if the Properties window is visible.
• Right-click in the toolbars area at the top of the desktop, and then click Properties on the
shortcut menu.
A check box appears next to this command if the Properties window is visible.
Related Topics
Setting the Properties Window to Open Automatically
Setting the Properties Window to Open Automatically
To set the Properties window to open after an object is drawn, enabling you to modify the object’s
properties, do the following:
1. Click Tools >Options>Modeler Options.
The Modeler Options window appears.
2. Click the Drawing tab.
3. Select Edit property of new primitives.
Hereafter, after you draw an object in point mode, the Properties window will open. However,
if you draw an object in Dialog mode, this setting is ignored.
Related Topics
Showing and Hiding the Properties Window
Modifying Object Attributes Using the Properties Window
1. Select the object for which you want to edit its attributes by clicking it in the view window or
clicking its name in the history tree.
2. Under the Attribute tab in the Properties window, edit the object attribute.
Depending on the attribute type, you can edit it by doing one of the following:
• Select the check box to apply the attribute; clear the check box to disable the attribute.
• Click in the field and edit the numeric values or text, and then press ENTER.
• Click the button and then edit the current settings in the window or dialog box that
appears.
• Click the attribute, and then select a new setting from the menu that appears.
Related Topics
Modifying Objects
Modifying Object Command Properties Using the Properties Window
-32
Modifying Object Command Properties Using the Properties Window
The Command tab in the Properties window displays information about an action selected in the
history tree that was performed either to create an object, such as the Draw>Box) command, or to
modify an object, such as the Edit>Duplicate>Mirror command.
Not all command properties can be modified. In general, the command properties that you can typ-
ically modify are the numeric values, such as position values (base position, normal position, start
position, etc.), size values (height, radius, etc.), and various other coordinate values. You can also
modify many of the unit settings for a command property.
1. In the history tree, select the command for which you want to edit its properties.
Hint Press and hold CTRL to select multiple commands. If you select multiple commands,
only the common, or shared, properties will be displayed under the Command tab.
2. Under the Command tab in the Properties window, edit the command’s properties.
Depending on the property type, you can edit it by doing one of the following:
• Select the check box to apply the property; clear the check box to disable the property.
• Click in the field and edit the numeric values or text, and then press ENTER.
• Click the button and then edit the current settings in the window or dialog box that
appears.
• Click the attribute, and then select a new setting from the menu that appears.
Related Topics
Modifying Objects
Modifying Object Attributes using the Properties Window
Working with the Progress Window
The Progress window monitors a simulation while it is running.
In the image below, the Progress window is displaying the progress of a discrete frequency sweep,
which is nearing completion:
-33
A check box appears next to this command if the Progress window is visible.
• Right-click the history tree, and then click Progress on the shortcut menu.
A check box appears next to this command if the Progress window is visible.
Related Topics
Stopping or Aborting Simulation Progress
Viewing Distributed Analysis Subtasks
Stopping or Aborting Simulation Progress
To abort progress, right-click in the Progress window, and select Abort.
To stop the simulation cleanly between time steps, right-click in the Progress window, and select
Clean Stop.
Related Topics
Aborting an Analysis
Viewing Distributed Analysis Subtasks
While a distributed analysis is running, you can access parent and child progress bars. By
default, only the main progress bar is displayed, while the child progress bars (or subtasks)
remain hidden. You can toggle between showing and hiding the child progress bars.
To show the child progress bars:
• Right-click the progress window, and select Show Subtask Progress Bars.
To hide the child progress bars:
• Right-click the progress window, and select Hide Subtask Progress Bars.
Working with the Message Manager
The Message Manager displays messages associated with a project’s development, such as error
messages about the design’s setup or informational messages about the progress of an analysis.
Error messages contains timestamps with a precision of seconds.
To display or hide the Message Manager:
• Click View> Message Manager.
A check box appears next to this command if the Message Manager is visible.
If you right click in the Message Manager window, you see a popup menu that lets you:
• Clear the messages for the current model.
• Copy the messages to the clipboard. This can be helpful for sending the messages to applica-
tion engineers.
• Details. This brings up a information dialog with the project and design for specific message.
• After you run a validation check, you can right-click on an intersection error message in the
Message window, and select Go to reference from the shortcut menu. This selects the intere-
-34
secting objects.
Related Topics
Showing new messages
Showing errors and warnings
Setting the Message Manager to Open Automatically
Setting the Message Manager to Open Automatically
You can set the Message Manager to open automatically to show new messages and errors and
warnings.
Related Topics
Showing new messages
Showing errors and warnings
Showing new messages
You can set the Message Manager to automatically be brought up when a new message
appears.
1. Click Tools>Options>General Options.
The General Options dialog box appears.
2. Click the Project Options tab.
3. Under Additional Options, select Show Message Window on new messages.
4. Click OK.
Showing errors and warnings
You can set the Message Manager to automatically expand when an item is added to a project.
1. Click Tools>Options>General Options.
The General Options dialog box appears.
2. Click the Project Options tab.
3. Under Additional Options, select Expand Message Window Tree on errors and warn-
-35
ings.
Click OK.
Working with the 3D Modeler Window
The 3D Modeler window is the area where you create the model geometry. It appears to the right of
the Project Manager window after you insert an HFSS design to a project.
The 3D Modeler window consists of the model view area, or grid, and the history tree, as shown
below:
History tree
Related Topics
Modifying the Model View
Keyboard shortcuts for the 3D Modeler Window.
-36
Working with the History Tree
The history tree in the 3D Modeler window lists all the active model’s structure and grid details.
You can perform the following tasks with the history tree.
• Expand or Collapse Groupings in the History Tree
• Group Items by Material in the History Tree
• Select Objects in the History Tree
• Use Shortcut Menus in the History Tree
• View Properties for History Tree Objects
• View and Edit Commands on History Tree Objects
• Control the View of Objects in the History Tree
• Select All Objects in a History Tree Group
• Upgrade Version
The history tree contains the following model details:
Invalid Lists all invalid objects
Objects Displays all the model’s objects and a history of the commands carried out
on each object. By default HFSS groups objects by material. you can
change this by selecting the Objects icon in the history tree and right-click
to display the shortcut menu with the Group Objects By Material
checkbox.
Sheets Displays all the sheets in the model 3D design area. By default, HFSS
groups sheet objects by boundary assignment. You can change this by
selecting the Sheet icon in the history tree and right-click to display the
shortcut menu with the Group Sheets by Assignment checkbox.
Lines Displays all line objects included in the active model.
See Drawing a Straight Line for information on how to draw a line object.
Points Displays all point objects included in the active model.
See Drawing a Point for information on how to draw a point object.
-37
Coordinate Systems Displays all the coordinate systems for the active model.
See Setting Coordinate Systems for more information on this model detail.
Planes Displays the planes for all the coordinate systems. When you create a
coordinate system, default planes are created on its xy, yz, and xz planes.
Lists Displays the object or face lists for the active model. By default, a list
called "AllObjects" appears.
Creating an object list is a convenient way to identify a group of objects for
a field plot or calculation.
Creating a face list is a convenient way to identify a specific set of surfaces
for a field plot or calculation.
See Creating an Object List
Note While objects created in HFSS can always be classed in the history tree as either a solid,
sheet, or wire some imported objects may have mixture of these. HFSS places such
objects in an Unclassified folder in the history tree.
Related Topics
Purge History
Generate History
Selecting Several Objects
Creating an Object List
Expand or Collapse Groupings in the History Tree
You can expand or collapse object groupings in the history tree by left clicking the + or - respec-
tively. In addition, right-clicking on any group icon opens a pull-down to expand all groupings or
collapse all groupings.
Related Topics
Grouping Items by Material in the History Tree
Selecting Objects in the History Tree
History tree Grouping by Material
In addition, right-clicking on Objects lets you specify whether or not the Objects are sorted by
material (the default is to sort by material.) When the objects are sorted by material, 2D and 3D
objects are listed separately in the history tree.
Related Topics
Select Objects in the History Tree
-38
Select Objects in the History Tree
Selecting objects in the History tree also selects them in the View window. This can be useful for
complex objects, when it may be easier to find the objects of interest by name or material, if the
object of interest is inside or behind others.
You can use CTLR-click to make multiple selections. You can select a range of objects by a click
on the first, and then SHIFT-Click to select all in the range. You can also use click and drag the
mouse to make rubber band selections. Only visible objects are selected. That is, if the hierarchy is
closed under the selection, any operand parts are ignored and do not interfere with cut and paste
operations.
You can also right click on any History tree object or grouping and right click to display a shortcut
menu with a Select All command. This lets you select at one time all solids, sheets, lines, non-
model objects, or all unclassified objects.
Related Topics
Group Items by Material in the History Tree
Shortcut Menus in the History Tree
If you select particular objects in the history tree, right-click displays a shortcut menu lists the com-
mands that you can apply to the selected command, object, or objects. The shortcut menus for
model objects are most extensive.
-39
In other cases, you can only view properties, or expand or collapse hierarchy.
Related Topics
View Properties for History Tree Objects
View and Edit Commands on History Tree Objects
View Item Properties in the History Tree
To view the properties of an item in the history tree:
• Click the item’s name in the history tree.
The item’s properties appears in the docked Properties window.
• Double-click on an item in the history tree to display a Properties window.
• Click the item’s name in the history tree, and double right click to display a shortcut menu.
Then select Properties to display the Properties window.
Related Topics
Purge History
Generate History
Selecting Several Objects
Selecting All from a History Tree Grouping
-40
View and Edit Commands on History Tree Objects
The history tree also lists the history of all commands carried out a model’s objects, for example,
“CreateBox” or “Subtract.” This history is displayed in the order in which it occurred. Here is a his-
tory tree from the waveguide combiner example.
Selecting a command in the history highlights the object in the Modeler window and shows that
object’s properties (if available) in the docked Properties dialog. You can look at the fields in the
Properties dialog to see any editable fields for that command, such as coordinate system, line type,
coordinates, or units.
For some commands, such as Edit>Arrange>Move, or boolean operations, selecting them in the
history tree enables the X (delete) icon on the toolbar and the Edit>Delete menu. In these cases,
you can delete those commands from the history tree as a way of undoing those operations. As an
alternative to deletion, you can check Suppress command in the Properties window for that com-
mand. This undoes the effect of a command on an object without removing it from the History tree.
Related Topics
Select Objects in the History Tree
Purge History command
Generate History command
Modifying Objects
-41
Controlling the View of Objects in the History Tree
To control the view and visibility of an object such as a box or PML, right click on an object in the
history tree display the short-cut menu and select View. The short cut menu contains the following
commands:
• Fit in Active View
• Hide in Active View
• Show in Active View
• Fit in All Views
• Hide in All Views
• Show in All Views
Related Topics
Purge History
Generate History
Selecting Several Objects
Upgrade Version in History Tree Shortcut Menu
By right-clicking on an operation icon in the history tree in the Modeler window, you can see the
Upgrade Version command.
The Modeler by default opens the legacy project in previous (what ever that the project was saved
with) ACIS version so that you don't see side effects of slight topology changes between ACIS ver-
sions. If you want you can use Upgrade Version to move the operation to use latest ACIS code.
Typically this applies when a needed fix is available with new ACIS version.
Related Topics
Working with the History Tree
Keyboard Shortcuts for the 3D Modeler Window
By default, the following keyboard shortcuts apply to the 3D Modeler Window
• B: Select face/object behind current selection
• F: Select faces mode
• O: Select objects mode
-42
• E: Select edges mode
• V: Select vertices mode
• M: Multi select mode
• CTRL + A: Select all visible objects
• CTRL + SHIFT + A: Deselect all objects
• CTRL + D: Fit view
• CTRL + E: Zoom in, screen center
• CTRL + F: Zoom out, screen center
• SHIFT + LMB: Zoom in / out
• Alt + LMB: Rotate model
• Alt + SHIFT + LMB: Zoom in / out
• Alt + 2xLMB: Sets model projection to standard isometric projections (cursor must be in cor-
ner of model screen N/NE/E/SE/S etc)
• F6: Render model wire frame
• F7: Render model smooth shaded
-43
Using the Password Manager to Control Access to
-44
Running HFSS from a command line
-45
Running HFSS from a command line
-46
Running HFSS from a command line
Note • The -batchoptions filename value must be enclosed in double quotes if it contains
whitespace
• The $begin 'Config' and $end 'Config' lines are required
• The -batchoptions filename value must be enclosed in double quotes if it contains whitespace
• The $begin 'Config' and $end 'Config' lines are required
-47
Running HFSS from a command line
registry with values specified on the command line or in a file. The values specified using the
-batchoptions command line option only apply to the batch job, and do not affect the parameter
values in the registry. For example, you could specify the following command to ensure that this
analysis uses 2 processors for distributed processing and 2 processors for non-distributed process-
ing. If the -batchoptions value is not specified, then the number of processors for distributed pro-
cessing or for non-distributed processing could be affected by an interactive HFSS job running on
the same host as the same user.
hfss -ng -BatchSolve -Distributed
-machinelist num=2 _
-batchoptions _
"'HFSS/Preferences/NumberOfProcessorsDistributed'=2 _
'HFSS/Preferences/NumberOfProcessors'=2
'HFSS/Preferences/UseHPCForMP'=1
'HFSS/Preferences/HPCLicenseType'=pool"
OptimTee.hfss
-Monitor
You can monitor progress and messages on standard output, during non-graphical analy-
sis. Progress, warning and info messages are logged to the standard output stream. Error
and fatal messages are logged to the standard error stream. Schedulers intercept these
streams and provide commands for display of this output - see individual scheduler docu-
mentation for specifics.
Examples:
C:\HFSS\hfss.exe -distributed _
-machinelist list="192.168.1.1,192.168.1.2" _
-batchsolve design_transient:Optimetrics
"C:\distrib_project.adsn"
"c:/Program Files/Ansoft/HFSS13.0/hfss.exe" _
-Iconic -Queue _
-LogFile "H:\HFSS\_HFSSQueue\fence-v2__Array with Fence4.log" _
-BatchSolve "Array with Fence4:Nominal" "H:\HFSS\fence-v2.hfss"
-RunScript <script file name>
Run the specified script. You can use the -ScriptArgs option to add one or more argu-
ments to this command and can use the -Iconic option.
-RunScriptAndExit <script file name>
-48
Running HFSS from a command line
Run the specified script and exit. You can use the -ScriptArgs option to add one or more
arguments to this command. You can also use the -Iconic option, the -Logfile option, and
the -WaitForLicense option.
<none>
If you do not specify a run command with hfss on the command line, you can still specify
the -Help and -Iconic option.
<project file>
Open the specified project on start up. If -BatchSolve is also set, the project will be
solved.
Note The <project file> must be the last command line entry.
Options
The following options can be associated with one or more of the run commands.
-Distribute
Distribute a batch solve to multiple machines. This option must be combined with the -
BatchSolve run command and must be specified before it in the command line. See Dis-
tributed Analysis for more information on distributed analysis.
Example:
C:\HFSS\hfss.exe -distribute -batchsolve _
HFSSDesign1:Optimetrics:ParametricSetup1 "C:\Project1.hfss"
-Help
Open a window that displays the different command-line options. This is only used when
none of the four run commands are used.
-Iconic
Run HFSS with the window iconified (minimized). This can be used with all or none of
the run commands.
-LogFile <log file name>
Specify a log file (use in conjunction with -BatchSave or -BatchSolve or -RunScriptAn-
dExit run commands). If no log file is specified, it will be written to the directory in which
the script or HFSS project is located, with the name <project_name>.log.
-ng
Run HFSS in non-graphical mode (use along with -BatchSave or -BatchSolve run com-
mands).
-WaitForLicense
Wait for unavailable licenses (use along with -BatchSolve or -RunScriptAndExit).
-ScriptArgs <scriptArguments>
Add arguments to the specified script in conjunction with -RunScript and -RunScrip-
tAndExit.
-49
Running HFSS from a command line
ScriptArgs looks at the single argument after it and uses those as script arguments. You
can pass multiple arguments to scriptargs by surrounding the script arguments in double
quotes.
For instance:
hfss -scriptargs "HFSSDesign1 Setup1" -RunScriptAndExit
c:\temp\test.vbs
Here, HFSSDesign1 is taken into HFSS as the first argument, and Setup1 is the second
argument. Without the quotes, HFSSDesign1 is taken as the first argument, and Setup1
will not be understood by HFSS.
hfss -scriptargs HFSSDesign1 Setup1 -RunScriptAndExit
c:\temp\test.vbs
Example:
c:\hfss\hfss.exe -runscriptandexit "c:\project1.vbs"
-scriptargs "Setup1"
Example:
C:\hfss\hfss.exe -RunScriptAndExit C:\scripts\test.vbs _
-scriptsargs "arg1 arg2 arg3"
Related Topics
Running a Script.
Windows® HPC Task Properties
Command Line Enhancements for Ansoft Desktop Products
-50
Running from a Windows Remote Terminal
-51
Windows HPC Commands
-52
Getting Started Guides
A list of example projects included with the HFSS installation is located here.
A brief Application Specific Modeling Guide: Antennas.
An Application Specific Guide: Spiral Inductors on Silicon Substrate:
Guides for HFSS-IE are here.
Guides for HFSS Transient are here.
Getting Started Guide: A Waveguide Tee Junction
Open the PDF:
.
This Getting Started guide is written for HFSS beginners as well as experienced users who are
using HFSS version 12 for the first time. This guide will lead you step-by-step through creating,
solving, and analyzing the results of a T-shaped waveguide with an inductive septum. This type of
-53
Getting Started Guides
structure is used to split an incoming microwave signal into two outgoing signals. The waveguide’s
transmission and reflection of the signal will depend on the position of the septum.
By following the steps in this guide, you will learn how to perform the following tasks in HFSS:
• Draw a geometric model.
• Modify a model’s design parameters.
• Assign variables to a model’s design parameters.
• Specify solution settings for a design.
• Validate a design’s setup.
• Run an HFSS simulation.
• Create a 2D x-y plot of S-parameter results.
• Create a field overlay plot of results.
• Create a phase animation of results.
Getting Started Guide: Optimizing A Waveguide Tee Junction
Open the PDF:
.
This Getting Started guide is written for Optimetrics beginners as well as experienced users who
are using Optimetrics version 3 for the first time. You must have completed Getting Started with
HFSS: A Waveguide T-Junction before you begin this guide.
You will use Ansoft’s Optimetrics software to find an optimal position for the septum. Prior to per-
forming the optimization, you will set up and solve a parametric analysis.
By following the steps in this guide, you will learn how to perform the following tasks in HFSS
using Optimetrics:
• Create a basic parametric setup.
• Solve a parametric analysis.
• Create a 2D x-y plot of S-parameter results.
• Create a 2D x-y plot of power distribution results.
• Create a geometry animation.
• Specify a variable to be optimized.
• Create an optimization setup, which includes defining a cost function and setting the range of
variable values for an optimization.
• Solve an optimization analysis.
• During an optimization analysis, view a plot of cost values versus solved iterations.
• Run an HFSS simulation using the optimal variable value.
• Update an existing field overlay plot with new results.
Related Topics
Optimetrics
-54
Getting Started Guides
-55
Getting Started Guides
This Getting Started guide is written for HFSS beginners as well as experienced users who are
using version 12 for the first time. This manual guides you through the setup, solution, and analysis
of two different models using Floquet ports.
By following the steps in this guide, you will learn how to setup Floquet ports in HFSS.
Getting Started Guide: RCS
Open the PDF:
.
This Getting Started guide is written for HFSS beginners as well as experienced users who are
using version 12 for the first time. This manual guides you through the setup, solution, and analysis
a simple radar cross section (RCS) problem. By following the steps in this guide, you will learn
how to perform the following tasks in HFSS:
• Draw the geometric models.
• Create the Perfectly Matched Layer (PML) Boundaries
• Add the Excitation
• Setup Mesh Operations
• Specify solution setting for the design.
• Validate the design setups.
• Run HFSS simulations.
• Create the geometry setups for monostatic and bistatic infinite spheres.
• Create plots for these geometries for a Normalized Bistatic RCS and Monostatic RCS.
By following the steps in this guide, you will learn how to setup RCS problems.
Getting Started Guide: Coax Tee
Open the PDF:
.
This Getting Started guide assumes some familiarity with HFSS. It guides you through the steps of
creating and simulating a coax tee. The simulation solves for the fields in an arbitrary volume.
Coax Dielectric
• Coax Center Pin
• Outer Boundary
-56
Getting Started Guides
• Coax Shield
-57
Getting Started Guides
This Getting Started guide assumes some familiarity with HFSS. It guides you through the process
of creating a bandpass filter. It includes the use of duplicate around axis commands.
-58
Getting Started Guides
This Getting Started guide assumes some familiarity with HFSS. It includes the use of Perfect E
and Radiation boundaries and a Radiation Pattern plot.
Related Topics
Example Projects
Getting Help
Getting Started Guide:Silicon Spiral Inductor
Open the PDF:
.
This Getting Started guide assumes some familiarity with HFSS. It includes the use of Perfect E
and Radiation boundaries and Output Variables in generating plots.
-59
Getting Started Guides
Related Topics
Example Projects
Application Specific Modeling Guide: Spiral Inductors on Silicon Substrate
Application Specific Modeling Guide: Antennas
Open the PDF:
.
This Application Specific Modeling Guide is written for HFSS beginners as well as experienced
users who are using version 13 for the first time. This brief manual provides guidelines for model-
ing antennas in HFSS.
Related Topics
Antennas in HFSS
Application Specific Modeling Guide: Spiral Inductors on Silicon
Substrate
Open the PDF:
.
This Application Specific Modeling Guide is written for HFSS beginners as well as experienced
users who are using version 13 for the first time. This brief manual provides guidelines for model-
ing spiral inductors in HFSS.
Related Topics
Getting Started Guide: A Silicon Spiral Inductor
Drawing a Spiral Using User Defined Primitives
-60
Getting Started Guides
Drawing a Spiral
Setting the Reference Point
-61
HFSS-IE Getting Started Guides
-62
HFSS-IE Getting Started Guides
-63
HFSS Transient Getting Started Guides
-64
HFSS Transient Getting Started Guides
-65
Example Projects
Example Projects
Your HFSS installation includes an example directory containing a projects folder including the
following projects:
Getting Started Guide Projects: (See associated Getting Started Guides)
Related Topics
Other Examples with Brief Descriptions in the Online Help
Opening Example Projects
-66
Example Projects
For further examples, see Getting Started Guides and look at the Ansoft Website
Related Topics
Example Projects
Getting Started Guides
-67
Example Projects
The animated Mag_E1 plot of the E-field when the septum is located 0.2 inches closer to Port 2.
The second version of the wave guide t-junction demonstrates the use of the Optimetrics.
• parametric analysis
-68
Example Projects
-69
Example Projects
-70
Example Projects
-71
Example Projects
• wave ports
• integration lines in wave ports.
• solution data
• plot creation and analysis
• a phase animation.
cavity.hfss
The cavity model is in the Examples/Projects directory.
-72
Example Projects
-73
Example Projects
Optiguide
This optiguide project is a modal solution project located in the Examples/Projects folder.
-74
Example Projects
-75
Example Projects
-76
Example Projects
Antennas on Mast
Description - Three dipole antennas mounted on an aluminum mast, simulated in HFSS-IE. The
mast is mounted on an infinite ground plane.
Model - The mast is 3.1 m high. The dipoles are modeled using 2D objects with a PerfE boundary.
The excitations are lumped ports and the mounting structures are modeled by the polystyrene rods.
Note under Boundaries in the Project tree, InfGndPlane1.
-77
Example Projects
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
Model - The walls of the coax use the default outer PerfE boundary. The inner conductor is copper.
The ports are assigned to the faces of the coax so port2 will automatically move with the coax body
as the angle is changed.
-78
Example Projects
Setup - Adapt at 5 GHz and do an interpolating sweep from 0.1 to 5 GHz. The defined Parametric
sweep in bend angle sweeps from 50 - 90o every 10o.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
To view the S Parameter frequency plots for all five bend_angle variations, double-click on XY
Plot 1 under Results in the Project tree.
To see the shade plots of the electric field, double-click on Mag_E1 under Field Overlays>E Field.
To view all variations right-click on Mag_E1 and select Animate. In the Select Animation win-
dow select New, and then select bend_angle for the swept variable in the setup pane. Then click
OK.
Coaxial Resonator
Description - A coaxial resonator model showing how to use the Eigenmode solver. The eigen
solver computes the resonant frequency and Q of the model. This example was taken from Micro-
wave Circuit Modelling Using Electromagnetic Field Simulation (D. Swanson Jr., W. Hoefer).
Model - A coaxial cavity. Walls are defined to have σ = 6.17 x 107 mho/m.
Setup - There are no defined sources in an eigen solution so you need only select the number of
modes to compute and the convergence criteria. For this model, only the first mode is computed.
For maximum accuracy, we need to use curvilinear elements. To verify that this has been set for the
-79
Example Projects
model, go to HFSS>Mesh Operations> Initial Mesh Settings, and make sure “Apply Curvilinear
Elements” is checked.
Note Selecting an object in the History tree will also display its properties.
-80
Example Projects
To view the shade plot, right-click on E Field under Field Overlays in the Project tree, and select
Update Plots.
* Data computed using a mode matching program are given in the reference. The results presented
are f0 = 1.87 GHz and Q = 5592.
Connector - Terminal Example
Description - a simplified model of a four pin section of a connector. This is a driven terminal
design.
Model - the connector is configured with lumped ports on each end of the two inner pins. The two
outer pins are each grounded at both ends. The boards are FR4 and the connector body is modfied
epoxy. A radiation boundary is applied to the surrounding airbox.
-81
Example Projects
Setup - Driven Terminal Solution with adapt at 5 GHz. An interpolating sweep is also included that
has an upper frequency of 5 GHz and uses DC extrapolation at the low end.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
-82
Example Projects
Corporate Feed
Description - A microstrip 8 way corporate feed. The model was originally created in Ansoft
Designer. Export to HFSS was used to create this project. It is a Driven Terminal design.
Model - The traces are defined as 2D objects with a finite conductivity boundary of copper. The
sources are all lumped ports with a 50 Ohm impedance. There is a surrounding air box with a radi-
ation boundary on the top and sides.
Setup - Adapt at 7.5 Ghz and use Mixed Order for the Order of Basis function.
Note To view a port or boundary, select the desired item in the Project Tree. It is highlighted in
the Model window and the properties will be displayed. Selecting an object in the
History tree will also display its properties.
-83
Example Projects
To view the shade plot of the E field, shown below, double click on MagE1 in the Project
tree under Field Overlays>E Field. To see a phase animation of this field plot, right click
on MagE1, and select Animation, Then click OK in the dialog.
Helical Antenna
Description - a coax fed helical antenna with a dielectric support on a finite ground plane. The
antenna is designed to run at 3.5 GHz. A smaller virtual object is defined as the integration surface
for radiated field calculations. This is surrounded by an air box with a radiation boundary.*
-84
Example Projects
Model - the support is made of Teflon and the ground has as thickness of 0.5 in. The coax port is
internal and is capped by a conducting object. You can create a helix similar to this by using
Draw>User Defined Primitive>SysLib>Segmented Helix.
Setup - adapt at 3.5 GHz and use mixed order for Order of Basis function. Since this model has
open air regions and the tightly spaced helix it is a good choice for mixed order.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
*For a further discussion on using integration surfaces and for more on creating sample
antenna designs, see the antenna design kit at www.ansoft.com/hfssantennadesignkit.
Post Processing
After solving, you can view solution data by right-clicking on Setup1 and selecting Profile to dis-
play the Solution dialog. You also view the Solution tabs for Convergence, Matrix Data, and
Mesh Statistics.
To view 3D plot of the antenna gain, look in the Project Tree under Results and double click on 3D
Polar Plot 1. To overlay the 3D plot on the model, click HFSS>Fields>Plot Fields>Radiation
Field to display the Overlay radiation field dialog. Check Visible for 3D Polar Plot 1, and set the
transparency and scale as desired.
To view a 2D plot of the total gain, in the Project tree, double-click on Results - Radiation Pattern 1.
To view a 2D plot of the circular polarization pattern for this antenna in the φ = 0o cut, in the Proj-
ect tree, double click Results - Radiation Pattern 2.
-85
Example Projects
You can add markers to the Radiation Pattern plots by right-clicking on the plot window and choos-
ing Marker>Add Marker.
Package Section
Description - a model of a section of a complex package. The model was created using Ansoft
Links from an ANF file and is a driven terminal design.
Model - the model is two traces of a larger package. At one end are the bond wires that are excited
by lumped ports. The opposite ends terminate in ports at the solder balls. The substrate is FR4 and
a radiation boundary has been applied to the surface of the surrounding airbox.
Setup - driven terminal setup with an adapt frequency of 2.5 GHz. An interpolating sweep is also
included that has an upper frequency of 2.5 GHz and uses DC Extrapolation at the lower end.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
-86
Example Projects
To view the S parameter plot show below, double click on XY plot1 in the Project Tree under
Results.
To view the shade plot of jsurf, the surface current density, on one of the package planes, right click
on Jsurf under Field Overlays in the Project Tree and select update.
-87
Example Projects
Model - The elements use a teflon substrate with 1.6 mm thickness. The excitations are lumped
ports. A radiation boundary is defined on an air box that is not show here.The post processing vari-
able is called phase_shift.
Setup - Adapt at 1.9 GHz.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
-88
Example Projects
The easiest way to adjust the phase_shift variable is to click on the design name, HFSSDesign2, in
the Project tree. You will see the design variable displayed in the Properties window. You can
change the value of phase_shift in this window. The plot shown here is for a setting of 30o.
Pyramidal Horn
Description - A pyramidal horn designed to operate at 10 GHz. The feed is an x-band wave-
guide.This project uses PMLs for its radiation boundary.
-89
Example Projects
Model - The horn has 0.02" wall thickness and is defined as PEC. The port is internal to the solu-
tion region and is capped by a PEC object (cap). PMLs are included in the model and are defined
on the faces of air_box. Their visibility, by default, has been turned off.
Setup - Adapt at 10 GHz.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
-90
Example Projects
Field to display the Overlay radiation field dialog. Check Visible for 3D Polar Plot 1, and set the
transparency and scale as desired.
To view a 2D plot of the dB gain total, look in the Project Tree under Results, and double click on
Radiation Pattern 1
A shade plot showing the fields on the Y-Z plane has also been created and can be viewed by right-
clicking on E Field under Field Overlays and selecting Update.
Ring Hybrid
Description - a ring hybrid that can be used as a splitter. Power input to the Sum port splits equally
between Ports 2 and 3 in phase while power input to Difference Port splits with 180o phase shift. It
-91
Example Projects
can be used as a power combiner with power input to Ports 2 and 3. In that case, the sum of the two
inputs will be seen at Sum port and the difference at Difference port.
Model - This is a hybrid designed to operate at 10 GHz using stripline transmission lines. The sub-
strate is 40 mil Duriod 5880. The ports are defined on four of the faces of the substrate. Default
outer boundary boundary (PerfE) is defined on the remaining faces. The trace is a 2D object with a
PerfE boundary.
Setup - Adapt at 10 GHz with interpolating frequency sweep from 8 to 12 GHz. Also, the model
includes an output variable called Diff_port_phase that computes the difference in phase between
ports 2 and 3 when the Difference port is excited.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed. Selecting an
object in the History tree also displays its properties.
-92
Example Projects
To view the shade plot as shown, change excitations so that ports 2 and 3 are excited by equal
amplitude and phase, using HFSS>Fields>Edit Sources.
To view a phase animation of the resulting shade plot, right click on MagE1 and choose Animation
from the menu.
-93
Example Projects
Model - The patch, shoulder, and ground plate are united into a single PEC object. The air filled
coax has an internal port that is capped by the PEC ground plate. The variable feed_pos controls the
value of X for the coax location in millimeters. The surrounding air box with radiation boundary is
not shown.
Setup - Adapt at 1.8 GHz., and do an interpolating sweep from 1.5 to 2 GHz. The derivative of the
S parameter data w.r.t. feed_pos about the default value of 10.8 mm is computed. This feature is
enabled in the Derivatives tab of the Setup1 window.
Post processing for tuning a Coax Fed Patch Antenna
After solving, you can view solution data by right-clicking on Setup1 and selecting Profile to dis-
play the Solution dialog. You also view the Solution tabs for Convergence, Matrix Data, and
Mesh Statistics.
-94
Example Projects
To view the derivatives you can create a new plot by right clicking on Results and choosing Create
Modal Solution Data Report>Rectangular Plot. In the New Report Setup window, select
feed_pos in the derivative box and select the desired quantities to plot.
To tune the design, double-click on XY Plot 2 under Results to open the plot shown. In a separate
project, the response for feed_pos = 10.5 and 11 mm was computed and the results from each was
imported into this plot. By right clicking on Results and choosing Tune Reports you can open the
Report Tuning dialog shown. As you adjust the slider, the plot is recomputed using the derivatives.
Adjust the Offset to -0.3 and +0.2 to compare to the imported feed_pos = 10.5 and 11mm results.
Related Topics
Derivative Tuning for Reports
-95
Example Projects
Model - the antenna is fed by a coax line with a wave port. The upper
face of the unit cell is terminated in a Floquet port. The sides are two
pairs of Master and Slave boundaries. The substrate εr = 6 and is 1.27 mm
thick. The conducting traces are 2D objects with PerE boundaries.
Setup - Adapt at 4.5 GHz with an interpolating sweep from 2 to 5 GHz.
Note To view a port or boundary, select the desired item in the Project Tree.
It is then highlighted in the Model window and the properties will be
displayed in the Properties window.
Post Processing
After solving, you can view solution data by right-clicking on Setup1 and selecting Profile to dis-
play the Solution dialog. You also view the Solution tabs for Convergence, Matrix Data, and
Mesh Statistics.
-96
Example Projects
To view a plot of active S parameter seen at the feed, look in the Project tree and double-click on
XY Plot1. To view the modes present on the Floquet port click on the desired mode under Port
Field Display>Floquet Port 1 in the Project tree, and a vector plot of the mode will be displayed.
This design was analyzed in “Analysis of Periodic Structures via a Time-Domain Finite-Element
Formulation with a Floquet ABC,” L.E.R. Peterson et al., IEEE Trans, AP, March 2006, pp 933-
944. You will see the plot computed here agrees nicely with Fig. 9b in the reference.
-97
Example Projects
Via Model
Description - a model of a differential via pair. It has a pair of microstrip
lines that transition through the vias to a pair of striplines on a lower
layer. This model was created using the Via Wizard.*
Model - the two microstrip lines are each assigned a terminal in the coupled microstrip port. Like-
wise for the two striplines at the opposite end. The conductors are copper and a radiation boundary
is applied to the air box.
Setup - adapt at 4.38 GHz with an interpolating sweep that has an upper frequency of 4.38 GHz
and uses DC extrapolation at the lower end. Mixed Order is set for Order of Basis Function.
Note To view a port or boundary, select the desired item in the Project Tree. It is then
highlighted in the Model window and the properties will be displayed in the Properties
window. Selecting an object in the History tree will also display its properties.
-98
Example Projects
To view the S parameter plot shown below, double click on XY plot1 in the Project Tree under
Results.
-99
Copyright and Trademark Notices
-100
Copyright and Trademark Notices
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTOR(S) ``AS IS'' AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBU-
TOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCURE-
MENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-101
2
Getting Help
Getting Help2-1
The pdf of online help provides a format and function better suited for printing than the chm. You
can print ranges of pages encompassing topics and subtopics as needed.
Open the PDF:
.
Getting Help2-2
Conventions Used in the Online Help
"Click Draw> Line " means that you can click the Draw Line toolbar button to execute
the Line command.
Getting Help2-3
Searching in Help
Searching in Help
The online help system provides four ways to search for information and navigate quickly:
• A hierarchical table of contents - you can expand or collapse the hierarchy by clicking, and you
can jump to selected entries by double-clicking.
• A searchable index - you can search for indexed terms by typing the text field, and jump to
topic locations by double-clicking on them.
• A full text search - you can type text, and search the entire online help. Items are listed accord-
ing to rank in discussing the search text.
• A favorites list - you can select topics that you use frequently to create a favorites list.
Getting Help2-4
Using WebUpdate
Using WebUpdate
To use WebUpdate:
1. Select Help>Launch WebUpdate.
This displays the WebUpdate dialogue, which lists the applications available for update.
2. Select the application of interest and click Next.
This displays the application and whether it is currently up to date and whether an update is
available
3. If an update is available, enable the application checkbox to select it.
a. You can choose to enable the checkboxes to install the update automatically and to save
the update to disk.
If you choose to update, the Next button is enabled.
b. Click Next to continue the update.
c. The Webupdate shows the progress of the update.
4. Click Close when done
Getting Help2-5
Obtaining Information About the Software and Version
Getting Help2-6
Emailing a Help Page Title
6. The recipient copies the section title from the email and pastes it into the search field.
7. The recipient clicks the List Topics button.
This displays the topic. The recipient can click the topic to go directly to the help page.
Getting Help2-7
3
Working with HFSS Projects
An HFSS or HFSS-IE project is a folder that includes one or more HFSS models, or designs.
Each design ultimately includes a geometric model, its boundary conditions and material assign-
ments, and field solution and post-processing information.
A new project called Projectn is automatically created when the software is launched. A design
named Designn is automatically created for a new project. You can also open a new project by
clicking File>New. In general, use the File menu commands to manage projects. If you move or
change the names of files without using these commands, the software may not be able to find
information necessary to solve the model.
HFSS Files
When you create an HFSS project, it is given an .hfss file extension and stored in the directory you
specify. Any files related to that project are also stored in that directory.
Some common HFSS file and folder types are listed below:
.hfss HFSS project.
design_name.hfssresults HFSS folder containing results data for a design. It resides in the
project.hfssresults folder.
project_name.hfssresults HFSS folder containing results data for a project.
project_name.asol The .asol file contains the database of all solved variations and
where the resulting data is stored in the design.hfssresults folder.
This file is stored in the project_name.hfssresults folder.
.pjt HFSS version 8.5 and earlier project.
.anfp Ansoft PCB neutral file
Creating Projects
• Click File> New .
A new project is listed in the project tree. It is named Projectn by default, where n is the order
in which the project was added to the current project folder. A default design named Designn is
added under the project.
Project definitions, such boundary and material assignments, are stored under the project name
in the project tree.
You specify the name of the project when you save it using the File>Save or File>Save As com-
mands.
Projects
Open a previously saved project using the File>Open command.
1. Click File> Open .
2. Use the file browser to find the HFSS or HFSS-IE .hfss project file.
By default, files that can be opened or translated by HFSS or HFSS-IE are displayed.
3. Select the file you want to open.
4. Click OK.
The project information appears in the project tree.
If you open another project without editing the automatically-created project, HFSS or HFSS-
IE removes the automatically-created project.
You can also open a saved project by:
• Dragging an HFSS or HFSS-IE project file icon to the HFSS or HFSS-IE icon.
• Dragging an HFSS or HFSS-IE project file icon to the HFSS or HFSS-IE desktop.
• Double-clicking on an HFSS or HFSS-IE project file icon.
Related Topics
Opening Legacy HFSS Projects
Opening Example Projects
Closing Projects
To close the current HFSS or HFSS-IE project, select HFSS or HFSS-IE>Close. This closes the
project without exiting HFSS or HFSS-IE. If there you have a simulation running, you see a mes-
sage saying that if you continue, HFSS or HFSS-IE will abort before closing. If you OK, HFSS
or HFSS-IE aborts the simulation and closes the project.
Saving Projects
Use the File>Save As command to do the following:
• Save a new project.
• Save the active project with a different name or in a different location.
• Save the active project in another file format for use in another program.
Use the File>Save command to save the active project.
HFSShas a "Save before solving" setting located in the Tools>Options> HFSS or HFSS-IE
Options menu. By default this is on. However, for efficiency reasons, the project is only saved if it
has been modified since its last save.
A prompt appears when you attempt to save a previously-versioned file. If you agree to the prompt,
the file is upgraded to the HFSSversion in which you are running the software. In this case the file
may no longer be compatible with previous versions. If you do not agree to the prompt, the file is
not saved, so the file retains the previous compatibility.
If you have a simulation running, you see a warning that if you continue, HFSSwill abort the sim-
ulation. If you OK the warning, HFSS or HFSS-IE aborts the simulation and saves the project.
Related Topics
Saving a New Project
Saving the Active Project
Saving a Copy of a Project
Deleting Projects
Saving a New Project
1. Click File> Save As.
2. Use the file browser to find the directory where you want to save the file.
3. Type the name of the file in the File name box.
4. Use the correct file extension for the file type.
5. If the window has a Switch to saved option, do one of the following:
• Leave the option selected to display the new file name, and then close the current file.
• Cancel the Switch to saved selection to save the file under the new name without chang-
ing which file is displayed.
6. Click OK.
HFSS saves the project to the location you specified.
Warning Be sure to save geometric models periodically. Saving frequently helps prevent the
loss of your work if a problem occurs.
Although HFSS has an "auto-save" feature, it may not automatically save
frequently enough for your needs.
Related Topics
Saving the Active Project
Saving a Copy of a Project
Saving the Active Project
• Click File> Save .
HFSS saves the project over the existing one.
Warning Be sure to save geometric models periodically. Saving frequently helps prevent the
loss of your work if a problem occurs.
Although HFSS has an "auto-save" feature, it may not automatically save
frequently enough for your needs.
Related Topics
Saving a New Project
Saving a Copy of a Project
Saving a Copy of a Project
To save an existing, active project with a new name, a different file extension, or to a new location:
1. Click File >Save As.
2. Use the file browser to find the directory where you want to save the file.
3. Type the name of the file in the File name box.
4. Select the desired file extension for the file type.
5. If the window has a Switch to saved field, do one of the following:
• Leave the field selected to display the new file name, and then close the current file.
• Cancel the Switch to saved selection to save the file under the new name without chang-
ing which file is displayed.
6. Click OK.
HFSS saves the project with the new name or file extension to the location you specified.
Related Topics
Saving a New Project
Saving the Active Project
Renaming a Project
To rename an existing, active project:
1. Select the project in the Project tree.
2. Right-click to display the short-cut menu.
3. Select Rename.
This activates the text field for the project name.
Note Auto-save always increments forward; therefore, even when you undo a command,
HFSS or HFSS-IE counts it as an edit.
Warning When you close or rename a project, HFSS or HFSS-IE deletes the auto-save file.
HFSS or HFSS-IE assumes that you have saved any desired changes at this point.
Related Topics
Recovering Project Data in an Auto-Save File
Save Before Solve Option
The Tools> HFSS or HFSS-IE Options command displays a dialog with a checkbox for an auto-
matic Save Before Solve option. The main purpose is to force a full save before running the solve.
In the case where you start a solve while another solve is running, and the Save Before Solve option
is set, HFSS or HFSS-IE asks if you want solve without saving first. This lets you do multiple
solves, and if you have not edited the project in between solves, crash recovery will work. In any
case, you can start a new solve while running another without having to abort the running solve.
Recovering Project Data in an Auto-Save File
Following a sudden workstation crash or other unexpected problem, you can recover the project
data in its auto-save file.
Warning When you recover a project’s auto-save file you cannot recover any solutions data;
recovering an auto-save file means you will lose any solutions data that existed in
the original project file.
Warning If you choose to recover the auto-save file, you cannot recover the original project
file that has been overwritten; recovering data in an auto-save file is not reversible.
Related Topics
Saving Project Data Automatically
Deleting Projects
To delete a project:
1. Select the project in the project tree.
2. Click either Edit>Delete, or right click to display the short-cut menu and select Delete.
A dialog displays the message: "The project selected and all its files will be deleted from the
permanent storage medium. Click OK to proceed."
3. Click OK to delete the files or Cancel to retain them.
Undoing Commands
Use the Undo command on the Edit menu to cancel, or undo, the last action you performed on the
active project or design. This is useful for undoing unintended commands related to project man-
agement, model creation, and post-processing.
1. In the Project Manager window, do one of the following:
• To undo the last action you performed on the active project, such as inserting a design or
adding project variables, click the project icon.
• To undo the last action you performed on the active design, such as drawing an object or
deleting a field overlay plot, click the design icon.
Note You cannot undo an analysis that you’ve performed on a model, that is, the
HFSS>Analyze command.
Note When you save a project, HFSS always clears the entire undo/redo history for the project
and its designs.
Related Topics
Redoing Commands
Redoing Commands
Use the Redo command on the Edit menu to reapply, or redo, the last action that was canceled, or
undone. You can redo a canceled action related to project management, model creation, and post-
processing.
1. In the Project Manager window, do one of the following:
• To redo the last action you canceled on the active project, such as inserting a design or
adding project variables, click the project icon.
• To redo the last action you canceled on the active design, such as drawing an object or
deleting a field overlay plot, click the design icon.
2. Click Edit>Redo, or click the Redo button on the toolbars.
Your last canceled action is now reapplied.
Note When you save a project, HFSS always clears the entire undo/redo history for the project
and its designs.
Related Topics
Undoing Commands
Validating Projects
Before you run an analysis on a model, it is very important that you first perform a validation check
on the project. When you perform a validation check on a project, HFSS runs a check on all the
setup details of the active project to verify that all the necessary steps have been completed and
their parameters are reasonable.
To perform a validation check on the active project:
1. Click HFSS>Validation Check .
HFSS checks the project setup, and then the Validation Check window appears.
2. View the results of the validation check in the Validation Check window.
4. If the validation check indicates that a step in your project is incomplete or incorrect, carefully
review the setup details for that particular step and revise them as necessary.
5. Click HFSS>Validation Check to run a validation check after you have revised any setup
details for an incomplete or incorrect project step.
6. Click Close.
Related Topics
Modeler Validation Settings
Modeler Validation Settings
You can adjust the degree to which the software checks a model for faults that could jeopardize
mesh accuracy. There are three levels of model validation that a user can specify for a given design:
Warning Only, Basic, and Strict. Note that this setting affects only the "3D Model" stage of a
design validation.
• The Warning Only entity check setting allows all models to pass 3D Model validation regard-
less of any faults that are found (acis_entity check errors). These faults are posted in the mes-
sage window as warnings.
• The Basic entity check setting allows most models to pass 3D Model validation. This excuses
non-manifold errors and most acis_entity_check errors. Some faults are flagged as model
errors (basic entity check errors), thereby prohibiting a design from proceeding to the meshing
stage of an analysis. You must either correct such errors before attempting to analyze the
design under the Basic setting, or you must change the Model Validation level to Warning
Only.
• The Strict entity check setting enforces a tighter tolerance for model faults than the "Warning
Only" and "Basic" settings. All model faults that are found during 3D Model validation are
posted to the message window. These errors must be corrected before attempting to analyze
the design under the Strict setting, or you must change the Model Validation level to Basic or
Warning Only.
To set the Model Validation level:
1. Select Modeler->Validation Settings.
This displays the Validation Settings dialog that lets you set the validation as basic, strict, or
warning only.
2. Choose the desired level of validation from the Entity Check Level drop down menu.
You can also click the Save as Default button to make the current selection the default. You
can select the Restore Default button.
3. Click OK to accept the selection and close the dialog.
Related Topics
Model Analysis
Analyze Objects
Interobject Misalignment
Analyze Surface Mesh
Heal
Healing State On: Validation Check
Show Analysis dialog
Align Faces
Remove Faces
Remove Edges
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Exporting Files
You can export the following types of files from HFSS or HFSS-IE:
• Ansoft 2D modeler files
• 3D model files
• Graphics files
• Data tables
Related Topics
Exporting Matrix Data
Exporting Equivalent Circuit Data
Exporting 2D Geometry Files
When you export a file in a 2D geometry format (the Ansoft 2D Modeler (.sm2) format or the
AutoCAD DXF (.dxf) format), the geometry located within the xy plane is exported.
Note If you want to export a plane that does not coincide with the global xy plane, you must
create a relative coordinate system to redefine the location of the origin.
See Creating a Relative Coordinate System for more information.
5. Click Save.
The file is exported to the specified location as a 3D model file
Extension Contents
.step, .stp Industry standard AP203 STEP files. An additional license is required.
6. If you selected .sm3, the Select Version dialog box appears. Do the following:
• Click an ACIS version in which to export the model from the ACIS SM3 Version pull-
down list, and then click OK.
7. Click Save. Unless you selected GDSII, the file is exported to the specified location as a 3D
model file. If you selected GDSII, the GDSII Export dialog appears.
• If the model has been defined with layers, those layers are listed by layer number in the
table, with columns for Layer Name, Layer Number, Elevation in units. There is a check-
box to specify whether to include the layer in the exported file.
• If you have defined a layer map file for the model, the Layermap button opens a browser
for you to open that file before export. The *.layermap file is a text file that maps the
GDSII layer numbers to layer names in the stackup. The *.layermap file can have the
same format as the .tech file used in GDSII import, but it only needs the layer name and
number in the file. In a *.layermap file, other information is ignored.
• In the Polygon Vertices area, check a radio button to select either No Limit to the num-
ber of vertices or Limit the number of vertices to a specified value.
• For Arc tolerance, specify a value or accept the default.
8. Click the OK button in the GDSII Export dialog to complete the export. The file is exported to
the specified location.
Related Topics
Exporting 2D Model Files
Exporting Graphics Files
Importing 3D Model Files
Importing GDSII Format Files
Export Results to Thermal Link for ANSYS Mechanical
Exporting Graphics Files
You can export the following graphics formats:
Extension Contents
Extension Contents
.txt Post processor format file
.csv Comma-delimited data file
.tab Tab-separated file
.dat Ansoft plot data file
5. Click Save. The file is exported to the specified location as a data table file.
Related Topics
Exporting Matrix Data
Exporting Equivalent Circuit Data
Importing Files
You can import the following types of files to HFSS or HFSS-IE:
• 2D model files
• 3D model files
• Solution data files
• Data table files
• HFSS or HFSS-IE Plot Data
• Plot Data
The import dialog contains a check box for the Heal command which is enabled by default.
Related Topics
Exporting Files
Importing 2D Model Files
You can read 2D model files directly into the active Modeler window:
Note If you import a file into an active Modeler window that contains an existing model, the
file is added to the existing model; it will not replace it.
Extension Contents
.gds GDSII is a standard file format for 2D graphical design layout data.
Note When importing .sm2 files, they will import into the current XY or XZ plane depending
upon how they were originally created. If you want to import them in a specific
orientation other than the current XY or XZ plane, you must first create a relative
coordinate system with the planes in the desired orientation.
See Creating a Relative Coordinate System for more information.
Related Topics
Importing 3D Model Files
Importing GDSII Format Files
Importing GDSII Format Files
See the introductory topic Importing 2D Model Files for the initial steps in the process of importing
2D data.
The process for importing GDSII format files into the HFSS or HFSS-IE uses a single dialog box:
3. Click the Open button in the Layer mapping panel to locate and open an existing layer map-
ping file.
4. Click OK.
The file is imported into the active Modeler window.
You can use the Save button to save a layer mapping file with the current settings.
Tech File Colors with RGB Values
Color string choices with corresponding RBG values
snow RBG = { 255, 250, 250},
ghost white RBG = { 248, 248, 255},
GhostWhite RBG = { 248, 248, 255},
white smoke RBG = { 245, 245, 245},
WhiteSmoke RBG = { 245, 245, 245},
gainsboro RBG = { 220, 220, 220},
floral white RBG = { 255, 250, 240},
FloralWhite RBG = { 255, 250, 240},
old lace RBG = { 253, 245, 230},
OldLace RBG = { 253, 245, 230},
linen RBG = { 250, 240, 230},
antique white RBG = { 250, 235, 215},
AntiqueWhite RBG = { 250, 235, 215},
Note If you import a file into an active 3D Modeler window that contains an existing model,
the file will be added to the existing model; it will not replace it.
Note While objects created in HFSS or HFSS-IE can always be classed in the history tree as
either a solid, sheet, or wire some imported objects may have mixture of these. HFSS or
HFSS-IE places such objects in an Unclassified folder in the history tree.
Extension Contents
.dxf, .dwg AutoCAD Drawing Interchange Format files from version 2.5 through 2009.
.tech The .tech file is an ASCII file that contains layer names, units, color,
elevation, thickness, and material information in a tab delimited format. See
Importing DXF and DWG Format Files.
.iges, .igs Industry standard Initial Graphics Exchange Specification (IGES) files
versions up to 5.3.1
.prt*, .asm* Pro/E model files. For ProE models, the import dialog lets enable Import Free
Surfaces, which will include such surfaces as well as parts.
.Pro/E 16 to Wildfire 4.0
.step, .stp Industry standard AP203 STEP files and AP214 (geometry only).1
Extension Contents
Related Topics
Importing 2D Model Files
Importing DXF and DWG Format Files.
Exporting 3D Model Files
Technical Notes: Handling Complicated Models
Importing DXF and DWG Format Files
You can import AutoCAD versions 2.5 through 2009. The entities are imported as 2 dimensional
(not 3D). The types of entities imported are:
• 2D Polyline, Polyline, and Line
• Arc
• Circle
• Ellipse
• Solid
• Block
To import a .dxf or .dwg model file (which may use an associated .tech file):
1. Click Modeler>Import.
The Import File dialog box appears.
2. Select AutoCAD Files (*.dxf;*.dwg) from the Files of type pull-down list.
3. Use the file browser to find the file you want to import.
4. Select the .dxf/.dwg model file you want to import.
5. Click Open.
Initially, the DWG/DXF Import dialog opens with the Layer Selection tab is displayed:
The Input Layer Name field shows the name of the layer in the DXF/DWG file (not editable)
6. Use the Include check boxes to specify which layers to import from the selected file.
7. You can use the Open button for a browser window to locate a tech file. The tech file is a plain
text file that includes units, layer names, color, elevation, and thickness information.
units um
//Layer_Name Color Elevation Thickness
BOTTOMLAYER purple 0 200
MIDLAYER green 500 200
TOPLAYER blue 1000 200
9. Use the Override pulldown to select the layout units for the imported file (default is mm).
10. Use the Objects check boxes to fine-tune the import:
• Auto-detect closure causes polylines to be checked to see whether or not they are closed.
If a polyline is closed, the modeler creates a polygon in the design.
• Self-stitch causes multiple straight line segments to be joined to form polylines. If the
resulting polyline is closed, a polygon is created in the modeler.
• De-feature tolerance removes certain small features in the imported geometry to reduce
complexity. The features that are removed include: multiple points placed within the spec-
ified distance; thin or narrow regions (“thins” and “spikes”); and extraneous points along
straight line segments.
• Round coordinates to Decimal place rounds all imported data to the specified number of
decimal points.
• Convert closed wide lines to polygons imports wide polylines as polygons. You have
more flexibility to change the shape of such an object when it is imported as a polygon.
• Import as 2D sheet bodies causes imported objects to be organized in terms of 2D sheets.
11. For Import method, select Script or Acis.
12. When you have completed selections on all tabs, click OK on any tab.
The file is imported into the active Layout window.
Importing Solution Data
1. Click HFSS or HFSS-IE>Results>Import Solutions.
The Imported Data dialog box appears.
a. In the All Columns list, click the heading you want to change. The heading appears in the
Column Name box.
b. Type a new name in the Column Name box, and then click Set Column Name.
The heading is changed to the new name in every place it appears in the Imported Data
dialog box.
9. In the Independent Data Columns list, the first heading in the data table file is listed by
default. In the Dependent Data Columns list, the second and subsequent headings in the data
table file are listed by default. Optionally, click a heading name and then click an arrow button
to move it from one column to another.
10. If the data in the Dependent Data Columns list contains matrix data, select Matrix Data. If it
contains field data, select Field Data.
11. Click Import.
You return to the Imported Data dialog box.
12. Click the data you want to import in the Current Imports list, and then click OK.
The solution data is now available for post processing.
Related Topics
Adding Datasets
2. Use the Look In feature, or the icons to navigate to the file location.
3. Specify the file name in the file name field, or select the file from those listed in the current
directory.
4. The file format field contains a drop-down menu listing the formats you can import. These
include comma delimited files (.csv) tab delimited files (.tab) or Ansoft Plot Data files (*.dat).
5. Click Open to import the file into the currently open Report.
The imported traces appear in the Project tree under the current report.
Related Topics
Importing HFSS Plot Data
Printing
The printing commands enable you to send an image of the active window to the printer.
To print the project:
1. Click File>Print .
A dialog box similar to the following one appears:
2. You can change the printer (if other printer names are listed on the drop down), set the print
range, number of copies, or use the check box to Print to file.
3. Do one of the following:
• Click OK to print the project.
• Click Cancel to dismiss the window without printing.
• Click Setup to define printer settings.
You can also access the printer properties by clicking Printer in the Page Setup dialog box.
Related Topics
Getting Help
Note Notes are used to document aspects of designs only. For project level documentation,
you can insert a documentation file into a project with the Project>Insert Documentation
Files command.
to enable the path text field and the ... button for finding and selecting the desired directory.
4. To reset the library directories to the default, click Reset Library Directory.
5. Select or clear the Expand Project Tree on Insert check box.
6. For When creating a new project, select a radio button to either Insert a design of type
HFSS or Don’t insert a design.
7. You can choose to specify a warning to be given when available disk space is less than a given
amount in M bytes.
General Options: Default Units Tab
These options are set on the Default Units tab of the General Options dialog box.
Select the desired units from each of the following pull-down lists:
• Length
• Angle
• Time
• Temperature
• Torque
• Magnetic Induction
• Frequency
• Power
• Voltage
• Current
• Speed
• Weight
• Resistance
• Inductance
• Capacitance
• Force
• Angular Speed
• Magnetic field strength
• Pressure
General Options: Analysis Options Tab
These options are set on the Analysis Options tab of the General Options dialog box. All but the
last, the Queue all simulations checkbox, are grouped as Design Analysis Options for Design
Type.
1. The type of design is HFSS or HFSS-IE.
2. If you would like to select the machine to which to send the analysis immediately before ana-
Note If the Queue all simulations option is selected, this setting is ignored, and the default
analysis machine is used.
3. Under Analysis Machine Options, select whether the default analysis machine should be the
local machine (Local), a remote machine (Remote), or whether analysis should be distributed
across multiple machines (Distributed).
a. If you selected Remote, enter the default analysis machine information either as an IP
address, a DNS name, or a UNC name. See Remote Analysis.
b. If you selected Distributed, you can select an distributed machine configuration list, or
add new list, or edit, remove, or clone an existing machine list. See Configuring Distrib-
uted Analysis. When you have made a selection, the lower field shows the enab led
machines in the configuration.
Regardless of the machine(s) on which the analysis is actually run, the number of processors
and Desired RAM Limit settings, and the default process priority settings are now read from
the machine from which you launch the analysis. See HFSS Options: Solver Tab.
For more information, see distributed analysis.
Once configured, you can also control these selections via toolbar icons for:
4. Select or clear the Queue all simulations check box. This allows subsequent projects to wait
in a queue till the currently running project solves completely.
Related Topics
HFSS Options: Solver Tab or HFSS-IE Options:Solver Tab for setting the maximum Number of
Processors, the desired RAM and Maximum RAM, and the process priority.
• Select or clear Dynamically update reports and field overlays during edits.
If selected, report plots and overlays update dynamically.
• Dynamically update postprocessing data for new solutions.
Updating numerous reports may a significant amount of time. Updating reports during the
analysis process can impact the overall time to solution. You may want to vary the times when
your reports get updated relative to the impact on overall solve time.
Five options exist for updating reports during solutions:
• Automatically - the default. It means update most things immediately.
For "AdaptivePass" plot context, plots are updated at the end of each solution pass. For
"LastAdaptive" or "Transient" the plot is updated at the end of the transient or adaptive
solution.
This option balances report and field plot updating with solution time. For example,
reports may be updated after each adaptive pass but field plots will not be updated until
the solution is complete.
• Immediately - update reports and plots as soon as data comes from the solver.
This option will have the greatest impact on the overall solution time but will have the
most rapid updating of reports and field plots. Caution should be used in selecting this
option. Some types of reports and field plots may take a long time to update, especially as
the mesh size increases.
• Never - only manual intervention updates reports.
This option will prevent updates from impacting the solution time.
• On Completion - as with Never, but a single update is done when the solve completes.
Note: Reports that are updated on completion are done after the solve has been completed.
The time for that update is not included in the solve profile.
• After Each Variation - when performing an Optimetric or parametric analysis, all reports
are updated after analysis of each variation has been completed.
The Animation setting lets you set a limit to Stop computing animation frames when available
memory is less than a value in megabytes. The default is 100.
The ANSYS Workbench Application Path lets you specify a path to an installation, if you have
one. This path can be used by the HFSS Optimetrics feature for connecting to the Design Xplorer.
Setting HFSS Options
To set HFSS options:
1. Click Tools>Options> HFSS Options.
The HFSS Options window appears, displaying three available tabs:
• General Options
• Solver
• Report Updating During Analysis
2. Click each tab, and make the desired selections.
3. Click OK.
HPC licensing is based on counting the total number of cores in a simulation. For example,
when solving a distributed solution across 10 nodes, with multiprocessing enabling 2 cores per
node, the total number of cores is 2x10, or twenty cores.
The HPC License Type determines the type and number of licenses that will be checked out for
a given number of cores. For the HPC type, one license will be checked out for each core in
use. So a simulation with twenty cores would require twenty HPC licenses. For the HPC Pack
type, a single pack enables eight cores, and each additional pack enables four times as many
cores. So a simulation with twenty cores would require two “HPC Pack” licenses, enabling up
to 8x4, or 32, cores.
If you are solving an HFSS Transient problem, the solver will not checkout hfss_solve (regular
solve license). We will only checkout a hfss_transient_solve license. For HFSS-IE problems
an hfssie_solve license is required. For HFSS problems with radiation boundaries and Use IE
Formulation checked, a hfssie_solve license is required in addition to the hfss_solve.
5. For multiprocessing, check Enable multiprocessing using HPC licenses.
This option causes HPC licenses to be used to enable multiprocessing even when solving prob-
lems that do not include domains. In this context, the HPC licenses take the place of the MP
license.
For HFSS Transient problems, we will always use HPC licenses for multiprocessing (even if
you have NOT chosen "Enable multiprocessing using HPC" option).
6. Select one of the following from the Default Process Priority pull-down list:
• Critical (highest) Priority (Not recommended)
• Above Normal Priority (not recommended)
• Normal Priority
• Below Normal Priority
• Idle (lowest) Priority
You can set these values using VB Scripts.
Related Topics
Configuring Distributed Analysis
Setting Solver Settings Using VB Scripts
Setting Solver Settings Using VB Scripts
Being able to set the number of processors, desired RAM limit, and maximum RAM limit
using VB scripts allows you to solve a project by running a VB script, without having to toggle
the computer hardware usage settings.
The following macros allow you to set these options:
oDesign.SetDesiredRamMBLimit <integer num in MB>
oDesign.SetMaximumRamMBLimit <integer num in MB>
oDesign.SetNumberOfProcessors <num>
limit = oDesign.GetDesiredRamMBLimit()
limit = oDesign.GetMaximumRamMBLimit()
num = oDesign.GetNumberOfProcessors()
a given number of cores. For the HPC type, one license will be checked out for each core in
use. So a simulation with twenty cores would require twenty HPC licenses. For the HPC Pack
type, a single pack enables eight cores, and each additional pack enables four times as many
cores. So a simulation with twenty cores would require two “HPC Pack” licenses, enabling up
to 8x4, or 32, cores. For HFSS-IE problems an hfssie_solve license is required.
4. For multiprocessing, check Enable multiprocessing using HPC licenses.
This option causes HPC licenses to be used to enable multiprocessing. In this context, the HPC
licenses take the place of the MP license.
5. Select one of the following from the Default Process Priority pull-down list:
• Critical (highest) Priority
• Above Normal Priority
• Normal Priority
• Below Normal Priority
• Idle (lowest) Priority
Related Topics
Configuring Distributed Analysis
HFSS-IE Options: General Options tab
Setting Fields Reporter Options
To set the Fields Reporter options:
1. Click Tools>Options>Fields Reporter Options.
The Fields Reporter Options dialog opens with the Phase Animation tab selected.
2. Specify whether to Group Field Overlays by Type (default, yes).
3. Set the default Phase Animation settings for Scalar Plots and Vector Plots.
Each of these accepts values for From and To in degrees, and the number of steps.
4. Click the Mesh Plot tab to set when dragging the clip plane, to update the plot dynamically
Never, Always or When the number of mesh elements is less that a value (default 5000).
5. Click the Streamline tab to set the two Streamline drawing stopping criteria and the Stream-
line marker spacing.
The Streamline drawing stopping criteria are:
Fields magnitude on a streamline data point is <percentage> of maximum field value of entire
model.
Streamline length is higher than <value> times of diagonal length of model bounding box.
The streamline marker spacing the Number of markers per bounding box diagonal.
6. Click OK to accept the settings and close the dialog.
Related Topics
Creating Phase Animations
3-74 Working with HFSS Projects
HFSS Online Help
9. Sym Color -- set the color for the symbol by double clicking to display the Set color dialog.
Select a default or custom color and click OK.
Report2D Options: Axis Tab
These options are set on the Axis tab of the Report2D Options dialog box.
1. Axis Name -- this describes the axis to which the following options refer.
2. Color -- set the color by double clicking to display the Set color dialog. Select a default or cus-
tom color and click OK.
3. Auto Scale -- use the check box to toggle whether to auto scale the axis.
4. Min Scale -- if Auto Scale it not selected, edit the real value to set the minimum value of the
axis.
5. Max Scale -- if Auto Scale is not selected, edit the real value to set the maximum value of the
axis.
6. Auto Units -- use the check box compute the correct units for the axis.
7. Units -- click on the cell to select from a menu of available units if you have not checked Auto
Units.
8. Font color -- set the font color of the axis by double clicking to display the Set color dialog.
Select a default or custom color and click OK.
9. Edit Font -- click the cell to display the Edit Text Font dialog. The dialog lets you select from a
list of available fonts, styles, sizes, effects, colors, and script. The dialog also contains a pre-
view field. OK the selections to apply the font edits and to close the dialog.
Report2D Options: Grid Tab
These options are set on the Grid tab of the Report2D Options dialog box.
1. Grid Name -- lists the name or letter of the grid. Not editable.
2. Line Style -- select the options from the drop down menu. The options are Solid, Dot, Dash,
and Dot dash.
3. Line Color -- set the color by double clicking to display the Set color dialog. Select a default or
custom color and click OK.
Report2D Options: Header Tab
These options are set on the Header tab of the Report2D Options dialog box. For the Title and
subtitle, you can independently specify the following:
1. Color -- set the color by double clicking to display the Set color dialog. Select a default or cus-
tom color and click OK.
2. Font -- click the cell to display the Edit Text Font dialog. The dialog lets you select from a list
of available fonts, styles, sizes, effects, colors, and script. The dialog also contains a preview
field. OK the selections to apply the font edits and to close the dialog.
preview field. OK the selections to apply the font edits and to close the dialog.
3. X Marker -- use the following options to set the X Marker properties.
a. Show Intersection -- checkbox to show the intersection.
b. XMarker Color -- set the color by double clicking to display the Set color dialog. Select a
default or custom color and click OK.
c. XMarker Font -- click the cell to display the Edit Text Font dialog. The dialog lets you
select from a list of available fonts, styles, sizes, effects, colors, and script. The dialog also
contains a preview field. OK the selections to apply the font edits and to close the dialog.
d. Box Background Color -- set the color by double clicking to display the Set color dialog.
Select a default or custom color and click OK.
e. Line Color -- set the color by double clicking to display the Set color dialog. Select a
default or custom color and click OK.
f. Line Style -- select the options from the drop down menu. The options are Solid, Dot,
Dash, and Dot dash.
g. Line Width -- set the line width by editing the real value in the text field.
Related Topics
Modifying Markers on Point Plots
Report2D Options: Marker Table Tab
These options are set on the Marker Table tab of the Report2D Options dialog box.
1. Precision -- set the precision for marker placement by editing the real value field.
2. Text Color -- set the color by double clicking to display the Set color dialog. Select a default or
custom color and click OK.
3. Text Font -- click the cell to display the Edit Text Font dialog. The dialog lets you select from
a list of available fonts, styles, sizes, effects, colors, and script. The dialog also contains a pre-
view field. OK the selections to apply the font edits and to close the dialog.
4. Background Color -- set the color by double clicking to display the Set color dialog. Select a
default or custom color and click OK.
5. Border Line Color -- set the color by double clicking to display the Set color dialog. Select a
default or custom color and click OK.
6. Border Line Width -- set the line width by editing the real value in the text field.
7. Grid Color -- set the color by double clicking to display the Set color dialog. Select a default or
custom color and click OK.
8. Grid Line Width -- set the line width by editing the real value in the text field.
Report2D Options: General Tab
These options are set on the General tab of the Report2D Options dialog box.
1. Background Color -- set the color by double clicking to display the Set color dialog. Select a
• Select a color for the selected object or action, and click OK.
2. To specify the default for the View>Render setting for new projects, select WireFrame or
SmoothShade from the Default view render pull-down list.
When dealing with complicated geometries, choose WireFrame rendering. This is faster than
shaded rendering.
3. To set the Default transparency, move the slider, or enter a numerical value.
4. Select or clear the Show orientation of selected objects check box.
5. Select or clear the Highlight selection dynamically check box.
6. Select or clear Highlight UV Isolines.
For models with curved faces, you may prefer to clear this selection to simplify the wire-frame
display, so the rendering will be faster.
7. Under Default tree layout, select or clear the Group objects by material check box.
8. Under History operations visualization, select or clear the Visualize history of objects
check box.
The option lets you view an outline of each part that comprises an object when the given part is
selected in the model history tree. This can help you visualize an object that has been merged
with another object. A change to the option takes effect only when you restart HFSS.
Clearing this selection removes visualization of objects that are part of the model history. For
large models, this is faster and uses less memory.
The following figure shows an example history tree with an object selected and the outline
view of that object in the Main window.
able’s name when you create it, or HFSS will automatically append the project variable’s name
with the symbol after you define the variable.
1. Clicke Project>Project Variables.
• Alternatively, right-click the project name in the project tree, and then click Project Vari-
ables on the shortcut menu.
The Properties dialog box appears.
2. Under the Project Variables tab, click Add.
The Add Property dialog box appears.
3. In the Name text box, type the name of the variable.
Project variable names must start with the symbol $ followed by a letter. Variable names may
include alphanumeric characters and underscores ( _ ). The names of intrinsic functions and
the pre-defined constant pi (π) cannot be used as variable names.
You can sort the project variables by clicking on the Name column header. By default, vari-
ables are sorted in original order. Clicking once sorts them in ascending order, noted by a trian-
gle pointing up. Clicking against sorts in descending order, noted by a triangle pointing down.
Clicking a third time sorts in original order, with no triangle.
4. In the Unit Type text box you can use the drop down menu to select from the list of available
unit types. “None” is the default.
When you select a Unit Type, the choices in drop down menu for the Units text box adapt to
that unit type. For example, selecting Length as the Unit Type causes the Unit menu to show a
range of metric and english units for length. Similarly, if you select the Unit Type as Resis-
tance, the Units drop down lists a range of standard Ohm units.
5. In the Value text box, type the quantity that the variable represents. If you did not specify the
Unit Type and Unit, you can also optionally, include the units of measurement.
Warning If you include the variable’s units in its definition (in the Value text box), do not
include the variable’s units when you enter the variable name for a parameter value.
changed.
The Local Variables Properties dialog box appears. From the Properties dialog you can Add,
Add Array, Edit.. or Remove variables. This section describes Add. Use the links for descrip-
tions of Add Array, .Edit and Remove,
Any existing Design variables are listed in the Properties dialog with the name followed by
cells for Value, Unit, Evaluated Value, Type, Description, and Read-only and Hidden check
boxes. A Show Hidden checkbox on the lower right of the Properties dialog controls the
appearance of any Hidden variables .
Initially, you leave the radio button with Value selected until you have defined a variable. The
other radio buttons let you enable defined variables for Optimization, Tuning, Sensitivity or
Statistics. Selecting one of these radio buttons add a new column to the Variable definition row
for which you can check or uncheck Include for regular variables for that kind of Optimetrics
simulation. For further discussion, see Optimetrics.
2. Click Add.
The Add Property dialog box appears.
3. In the Name text box, type the name of the variable.
Variable names must start with a letter, and may include alphanumeric characters and under-
scores ( _ ). The names of intrinsic functions and the pre-defined constant pi (π) cannot be
used as variable names.
You can sort the project variables by clicking on the Name column header. By default, vari-
ables are sorted in original order. Clicking once sorts them in ascending order, noted by a trian-
gle pointing up. Clicking against sorts in descending order, noted by a triangle pointing down.
Clicking a third time sorts in original order, with no triangle.
4. In the Unit Type text box you can use the drop down menu to select from the list of available
unit types. “None” is the default.
When you select a Unit Type, the choices in drop down menu for the Units text box adapt to
that unit type. For example, selecting Length as the Unit Type causes the Unit menu to show a
range of metric and english units for length. Similarly, if you select the Unit Type as Resis-
tance, the Units drop down lists a range of standard Ohm units.
5. In the Value text box, type the quantity that the variable represents. Optionally, include the
units of measurement.
Note If you include the variable’s units in its definition (in the Value text box), do not include
the variable’s units when you enter the variable name for a parameter value.
Note Complex numbers are not allowed for variables to be used in an Optimetrics sweep, or
for optimization, statistical, sensitivity or tuning setups.
6. Click OK.
You return to the Properties dialog box. The new variable and its value are listed in the table.
If the value is an expression, the evaluated value is shown. Updating the expression also
changes the evaluated value display. Any dependent variables also have evaluated values
changed.
Any existing Design variables are listed in the Properties dialog with the name followed by
cells for Value, Unit, Evaluated Value, Type, Description, and Read-only and Hidden check
boxes. A Show Hidden checkbox on the lower right of the Properties dialog controls the
appearance of any Hidden variables.
Initially, you leave the radio button with Value selected until you have defined a variable. The
other radio buttons let you enable regular variables for Optimization, Tuning, Sensitivity or
Statistics. Array variables cannot be enabled for Optimetrics use.
2. Click the Add Array.... button.
The Add Array dialog displays.
3. Specify a variable Name in the text field.
4. Select a Unit Type and Units from the drop down menus.
5. To specify the array with Edit in Grid Selected, you can begin by clicking the Append Rows...
button to display the Number of Rows dialog. (For Edit in plain text field, see below.)
Any existing Design variables are listed in the Properties dialog with the name followed by
cells for Value, Unit, Evaluated Value, Type, Description, and Read-only and Hidden check
boxes. A Show Hidden checkbox on the lower right of the Properties dialog controls the
appearance of any Hidden variables.
Initially, you leave the radio button with Value selected until you have defined a variable. The
other radio buttons let you enable defined variables for Optimization, Tuning, Sensitivity or
Statistics. Selecting one of these radio buttons add a new column to the Variable definition row
for which you can check or uncheck Include a regular variable for that kind of Optimetrics
simulation. Array variables cannot be Enabled for Optimetrics. For further discussion, see
Optimetrics.
2. Select a variable to highlight it.
3. Click the Edit button.
For regular variables, the Add Property dialog for that variable opens, and for array variables,
the Edit Array variable dialog for that variable opens.
4. Complete the edits and OK the dialog to apply them.
Related Topics
Design Variables
Exporting Variables for Documentation
Modifying Datasets
Using Piecewise Linear Functions in Expressions
Using Dataset Expressions
Modifying Datasets
1. For Project level datasets, click Project>Datasets. For Design level datasets, click HFSS or
HFSS-IE>Design Datasets.
The Datasets dialog box appears.
2. Click the dataset name you want to modify, and then click Edit.
The Edit Dataset dialog box appears.
3. Optionally, type a name other than the default for the dataset in the Name text box.
4. Type new values for the data points as desired.
The plot is adjusted to reflect the revised data points.
5. When you are finished entering the data point coordinates, click OK.
Related Topics
Adding Datasets
Adding a Design Variable
Modifying Datasets
Using Piecewise Linear Functions in Expressions
Using Dataset Expressions
Defining Mathematical Functions
A mathematical function is an expression that references another defined variable. A function’s
definition can include both expressions and variables.
The following mathematical functions may be used to define expressions:
Basic /, +, -, *, mod (modulus), ** (exponentiation), - (Unary minus), ==
Functions (equals), ! (not), != (not equals), > (greater than), < (less than), >= (greater
than equals), <= (less than equals), && (logical and), || (logical or)
Intrinsic if, sqn, abs, exp, pow, ln (natural log), log (log to the base 10), lg (log to
functions the base 2), sqrt, floor, ceil, round, rand (returns a random number
between 0 and 1), deg, rad
Trigonometric sin, cos, tan, asin, acos, atan, sinh, cosh, tanh
expressions
The predefined variables X, Y, Z, Phi, Theta, R, and Rho must be entered as such. X, Y, and Z are
the rectangular (cartesian) coordinates. Phi, Theta, and Rho are the spherical coordinates. R is the
cylindrical radius, and Rho is the spherical radius.
If you do not specify units, all trigonometric expressions expect their arguments to be in radians,
and the inverse trigonometric functions’ return values are in radians. If you want to use degrees,
you must supply the unit name deg. When the argument to a trigonometric expression is a variable,
the units are assumed to be radians. These function names are reserved and may not be used as vari-
able names.
As far as expression evaluation is concerned: units are conversion factors (that is, from the given
unit to SI). Note also that the evaluated value of an expression) is always interpreted as in SI units.
Related Topics
Setting Coordinate Systems
Expressing Cartesian, Cylindrical or Spherical Coordinates
Defining an Expression
Expressions are mathematical descriptions that typically contain intrinsic functions, such as sin(x),
and arithmetic operators, such as +, -, *, and /, well as defined variables. For example, you could
define: x_size = 1mm, y_size = x_size + sin(x_size). Defining one variable in terms of another
makes a dependent variable. Dependent variables, though useful in many situations, cannot be the
subject of optimization, sensitivity analysis, tuning, or statistical analysis.
The Constants tab of the Project Variables dialog lists the available pre-defined constants.These
may not be reassigned a new value.
Numerical values may be entered in Ansoft’s shorthand for scientific notation. For example, 5x107
could be entered as 5e7.
Related Topics
Defining Mathematical Functions
Using Valid Operators for Expressions
Using Intrinsic Functions for Expressions
Note If you do not specify units, all trigonometric functions interpret their arguments as
radians. Likewise, inverse trigonometric functions’ return values are in given in radians.
When the argument to a trigonometric expression is a variable, the units are assumed to
be radians. If you want values interpreted in degrees, supply the argument with the unit
name deg.
Related Topics
Defining an Expression
Using Piecewise Linear Functions in Expressions
The following piecewise linear intrinsic functions are accepted in expressions:
pwl (dataset_expression, variable)
pwl_periodic (dataset_expression, variable)
The pwl function interpolates along the x-axis and returns a corresponding y value. The
pwl_periodic function also interpolates along the x-axis but periodically.
Related Topics
Adding Datasets
Adding a Design Variable
Modifying Datasets
Using Dataset Expressions
Note You can assign a variable to nearly any design parameter assigned a numeric value in
HFSS. See the HFSS online help about the specific parameter you want to vary to
determine if can be assigned a variable.
Related Topics
Working with Variables
Choosing a Variable to Optimize
Before a variable can be optimized, you must specify that you intend for it to be used during an
optimization analysis in the Properties dialog box.
1. If the variable is a design variable, do the following: Click HFSS or HFSS-IE>Design Prop-
erties.
If the variable is a project variable, do the following: Clicke Project>Project Variables.
The Properties dialog box appears.
2. Click the tab that lists the variable you want to optimize.
Note Complex numbers are not allowed for variables to be used in an Optimetrics sweep, or
for optimization, statistical, sensitivity or tuning setups.
6. Optionally, override the default minimum and maximum values that Optimetrics will use for
the variable in every optimization analysis. During optimization, the optimizer will not con-
sider variable values that lie outside of this range.
Related Topics
Setting up an Optimization Analysis
Including a Variable in a Sensitivity Analysis
Before a variable can be included in a sensitivity analysis, you must specify that you intend for it to
be used during a sensitivity analysis in the Properties dialog box.
1. If the variable is a design variable, do the following: Click HFSS or HFSS-IE>Design Prop-
erties.
If the variable is a project variable, do the following: Click Project>Project Variables.
The Properties dialog box appears.
2. Click the tab that lists the variable you want to include in the sensitivity analysis.
3. Click the row containing the variable you want to include in the sensitivity analysis.
Note Complex numbers are not allowed for variables to be used in an Optimetrics sweep, or
for optimization, statistical, sensitivity or tuning setups.
6. Optionally, override the default minimum and maximum values that Optimetrics will use for
the variable in every sensitivity analysis. During sensitivity analysis, Optimetrics will not con-
sider variable values that lie outside of this range.
7. Optionally, override the default initial displacement value that Optimetrics will use for the
variable in every sensitivity analysis. During sensitivity analysis, Optimetrics will not consider
a variable value for the first design variation that is greater than this step size away from the
starting variable value.
Related Topics
Setting up a Sensitivity Analysis
Choosing a Variable to Tune
Before a variable can be tuned, you must specify that you intend for it to be tuned in the Properties
dialog box.
1. If the variable is a design variable, do the following: Click HFSS or HFSS-IE>Design Prop-
erties.
If the variable is a project variable, do the following: Click Project>Project Variables.
The Properties dialog box appears.
2. Click the tab that lists the variable you want to tune.
3. Click the row containing the variable you want to tune.
Note Complex numbers are not allowed for variables to be used in an Optimetrics sweep, or
for optimization, statistical, sensitivity or tuning setups.
6. Click OK.
The selected variable will now be available for tuning in the Tune dialog box.
Related Topics
Tuning a Variable
Example Projects: Tune a Coax Fed Patch Antenna
Including a Variable in a Statistical Analysis
Before a variable can be included in a statistical analysis, you must specify that you intend for it to
be used during a statistical analysis in the Properties dialog box.
1. If the variable is a design variable, do the following: Click HFSS or HFSS-IE>Design Prop-
erties.
If the variable is a project variable, do the following: Click Project>Project Variables.
The Properties dialog box appears.
2. Click the tab that lists the variable you want to include in the statistical analysis.
3. Click the row containing the variable you want to include in the statistical analysis.
Note Complex numbers are not allowed for variables to be used in an Optimetrics sweep, or
for optimization, statistical, sensitivity or tuning setups.
6. Optionally, override the distribution criteria that Optimetrics will use for the variable in every
statistical analysis.
Related Topics
Setting up a Statistical Analysis
Exporting Variables for Documentation
By right-clicking in the Project Variables dialog, you can copy a a list of variables and their values
to the clipboad. You can then paste these variables elsewhere.
The pasted variables appear in a tab separated column format. Fields that do not contain values are
left blank.:
Name Value Unit "Evaluated Value "Description Read-only Hidden
$width 14.8570192 mm 14.8570192mm false false
$length 7.824547736 mm 7.824547736mm false false
$height 0.45*$width 6.68565864mm false false
Related Topics
Assigning Variables
To set up an HFSS design, follow this general procedure. Note that after you insert a design, you do
not need to perform the steps sequentially, but they must be completed before a solution can be gen-
erated.
1. Insert an HFSS or HFSS-IE design into a project.
2. Select the solution type.
3. Set the model’s units of measurement.
4. Draw the model geometry and assign material characteristics to objects.
5. Assign boundaries, which specify the field behavior at the edges of the problem region and
object interfaces.
6. For Driven solution-type designs, assign excitations - sources of electromagnetic fields and
charges, currents, or voltages on objects or surfaces.
7. Specify how HFSS or HFSS-IE will compute the solution.
8. (Optional) Set up any Optimetrics you want to run.
9. Run the simulation.
10. View solution results, post-process results, view reports, and create field overlays.
Note After a period of ildleness of 10 minutes, HFSS gives up its license. A renewal of
activity automatically requests a license. Such idle notifications do not occur during
solves.
Note Click the plus sign to the left of the design icon in the project tree to expand the project
tree and view specific data about the model, such as its boundary assignments.
Related Topics
Setting up an HFSS or HFSS-IE Design
Setting the Project Tree to Expand Automatically
Related Topics
Technical Notes: Solution Types
Technical Notes: Transient Solution Theory
HFSS Transient includes two solution types within HFSS. It employs a time-domain (“transient”)
solver. Typical applications include, but are not limited to:
• Simulations with pulsed excitations, such as ultra-wideband antennas, lightning strikes, elec-
tro-static discharge;
• field visualization employing short-duration excitations;
• time-domain reflectometry.
The interface of HFSS Transient is much like the Terminal Driven solution type in the frequency
domain. The geometry creation and the mesh are almost identical. Boundary conditions and defini-
tions of ports or incident waves are almost the same, except for some restrictions in cases where
certain frequency-domain options do not apply in the time domain. Therefore, you can often
change an existing Terminal Driven design into a Transient design and vice versa. (Note: before
doing so, you must remove the setups and solutions.) Notable differences for transient solution
types are:
• Materials cannot have arbitrary frequency dependence in a time-domain analysis. For lossy
dielectrics, a Debye model is applied to ensure that the loss remain physical across the spec-
trum. For lossy metals, a Padé approximation is used for the same reason.
• When lossy materials touch a port, the port solver will launch an excitation that fits the lossless
case. This is inherent to most time-domain solvers. The 3D part of the simulation will take
losses into account correctly.
• The Analysis Setup for the transient solver is different from that of the frequency domain. Two
types of analysis setup are offered:
a. Transient Network Analysis solution types - excitations are identical on all active ports
and are simulated one at a time to facilitate the data collection. Saved fields can be visual-
ized, and voltages and currents can be monitored. Your choice in setting the Transient
solution type affects the options for the setup. If you select Transient Network Analysis
the setup includes a tab for the Excitation for the simulation.
b. Transient solution types - Different ports can have different excitations. All Active exci-
tations are launched in one simulation. No S-parameters or TDR results may be available,
but saved fields can be visualized, and voltages and currents can be monitored.
• Fields will only be saved on pre-selected surfaces, because saving all 3D fields for all times
would take more disk space and I/O time than generally desired.
Related Topics
HFSS Transient Getting Started Guides
Adding a Solution Setup for Transient Solutions
Active and Passive Excitation in HFSS Transient
Transient Solution Theory
Selecting the Report Type in HFSS Transient
Procedure for Viewing Transient Radiated Fields
You specify the function to use for the Profile by selecting from the drop down menu.
The wave plots are updated if you select a different function or edit the parameters. The following
table lists the available functions and the parameters that apply to the upper plot. The energy spec-
trum plot parameters are always Frequency and Max Frequency.
Related Topics
Transient Network Analysis Solution Input Signal Tab: A Time Profile
Active and Passive Excitation in HFSS Transient
If lists exist, you can also choose whether to Start saving fields, the save interval, and specify the
Maximum Number of Samples.
Transient solutions support plotting rE, a real vector versus time, in reporter. Patterns and 3D plots
will also be supported.
Related Topics
Adding a Solution Setup for Transient Solutions
Transient Network Analysis Solution Input Signal Tab: A Time Profile
Transient Solution Theory
Options Tab for Transient Solution Setup
For excitations in HFSS Transient solutions (and not HFSS Transient Network solutions), if you
select Active, you can specify additional parameters for the excitation.
The general Transient solution type has more time profiles. In this case, the time profiles are
defined as part of the excitations, because excitations can have individual profiles in a general anal-
ysis. The profile includes two plots. The upper plot shows the excitation of interest given the cur-
rently specified parameters. The lower plot shows the energy spectrum of the upper plot. The lower
plot parameters include the Min and Max frequencies. The following table describes the parameters
for the upper plots.
2. Then selecting from the Show dropdown menu, you can select Input, Output, TDRz or Field
Residual to display.
3. You can select which time step to display from the dropdown, or check Show All.
4. To export the transient data, click Export. This opens File browser winder that lets you specify
a File name, location, and data format.
With Transient selected, the Quantities include Input and Output related to the terminals in your
design, as well as TDRz and Residual.
For Transient Network Solution type designs, if you select Spectral, the Category and Quantity lists
offer different selections:, including Terminal S Parameters, VSWR, and Port Zo.
Related Topics
Creating Reports
3. Under HFSS>Radiation, you can Insert Far Field Setup> Infinite Sphere. This menu is
enabled for designs with radiation boundaries, even if no setups are saving radiated fields. The
setup dialog resembles the one for frequency domain, but without the Radiation Surface tab.
Use this dialog to set up the Theta and Phi sampling and, if needed, the local coordinate sys-
tem. You can create multiple Infinite Sphere setups in a single design.
4. Once you have created a far field setup AND at least one setup has "Save radiated fields"
selected, the Results menu will include Create Far Fields Report, with all submenus as in
Frequency domain.
For Rectangular Plot, Rectangular Stacked Plot, and Data Table, the default is "Time" as the
primary sweep, with Theta and Phi in Families set to single values corresponding to the first
sample point.
For all other plots, the primary and secondary sweeps will be Theta and/or Phi, as in Frequency
domain, and the Time is set to a single value - the start time.
5. In the Report dialog, the Solution selection includes only setups with "Save radiated fields"
checked. The Geometry selection will include all far field Infinite Sphere setups. The Catego-
ries include rE, Variables, Output Variables, and Design. The rE quantities are as for fre-
No matter what type of plot is generated, you can access the Time sweep and change the sam-
pling, as with Field reports in Transient.
For 3D patterns, you can overlay the pattern on the geometry, and to animate versus time, as is
done in frequency domain.
Once plots have been created, the reporter caches the base radiation field calculation. This
means that subsequent plots will be generated more quickly. If you change the radiation setup,
or invalidate solutions, the cache is cleared and the next plot takes longer.
For Transient Network Analysis, the radiated fields are based on the setup in Edit Sources. If
you change the source excitations that forces recomputation of the radiated fields.
Output variables are supported, as for frequency domain.
Related Topics
HFSS Transient Getting Started Guides
Creating Reports
Plotting Field Overlays
HFSS-IE is a fullwave Integral Equation solver that calculates the “currents” on the surfaces of the
objects in the model – both finite conducting and lossy dielectric objects are allowed. HFSS-IE is
designed for large open problems. Application areas include:
• Radar cross Section (RCS)
• Antenna placement (for example, antenna on a vehicle)
• Stand alone antennas
• Coupling. EMI/EMC
HFSS-IE features:
• Works from within the standard HFSS desktop, sharing the GUI and the same 3D modeler and
reporting features.
• Naturally open – no air volume or ABC needed
• Support for infinite ground plane
• Supports ground planes apertures
• Supports lumped gap and incident wave excitations.
• Supports discrete and/or interpolating frequency sweeps
• Near and far field calculations
• For larger models, HFSS-IE uses automated advanced matrix based compression techniques.
• Data link from HFSS available, which means that you divide appropriate models based on
each solver’s advantages.
How HFSS-IE is different than HFSS
HFSS uses the finite element method (FEM) to solve for the electromagnetic fields in the solution
region. It meshes over the entire solution volume and solves for the electric field throughout that
volume.
HFSS-IE 6-1
HFSS Online Help
HFSS-IE uses an integral equation (sometimes called method of moments = MoM) and solves for
the currents on surfaces of objects. It creates a triangular surface mesh on all objects - it solves for
the currents or equivalent currents on conducting and dielectric objects. The IE technique is by
default an "open model" technique so no ABCs are needed. It can handle closed spaces, but that is
typically not where it will be used. In addition HFSS-IE includes a true infinite ground plane.
Related Topics
HFSS-IE Options
Inserting an HFSS or HFSS-IE Design
Setting up an HFSS or HFSS-IE Design
Assigning Excitations
Assigning HFSS-IE Boundaries
Adding a Solution Setup to an HFSS-IE Design
HFSS-IE Getting Started Guides
Technical Notes: Integral Equation Method Used in HFSS-IE
6-2 HFSS-IE
HFSS Online Help
Note Click the plus sign to the left of the design icon in the project tree to expand the project
tree and view specific data about the model, such as its boundary assignments.
Related Topics
Setting up an HFSS or HFSS-IE Design
Setting the Project Tree to Expand Automatically
HFSS-IE 6-3
HFSS Online Help
6-4 HFSS-IE
HFSS Online Help
HFSS-IE 6-5
HFSS Online Help
6-6 HFSS-IE
HFSS Online Help
HFSS-IE 6-7
HFSS Online Help
6-8 HFSS-IE
7
Drawing a Model
After you insert a design into the current project, you can draw a model of the electromagnetic
structure. The general strategy is to build the model as a collection of 3D objects. You can assign
any single material to each 3D object.
You can create 3D objects by using the modeler’s Draw commands or you can draw 1D and 2D
objects, and then manipulate them to create 3D objects. Objects are drawn in the 3D Modeler win-
dow. You can also import objects from other systems.
To open a new 3D Modeler window, do one of the following:
• Insert a new design into the current project.
• Double-click an HFSS design in the project tree.
If a 3D Modeler window for an existing design is not open, do one of the following:
• Click HFSS>3D Model Editor.
• Right-click the design name in the project tree, and then click 3D Model Editor on the short-
cut menu.
The model you draw is saved with the current project when you click File>Save.
Note If you access your machine via Remote Desktop, if HFSS is running and one or more
modeler windows are open, those modeler windows automatically close. The message
manager window displays a message indicating that HFSS closed the modeler windows.
When working with multiple projects, or when a project has multiple designs, you may have multi-
ple Modeler windows available. To switch to the modeler window associated with a specific
design:
1. In the Project Manager window, select the Design of interest.
2. Click HFSS3D Model Editor to focus the modeling window on the selected design.
If the menu command is unavailable, then the selected design is already in the modeler window.
Related Topics
Setting the Units of Measurement for the Model
Drawing Objects
Model Analysis
Design Settings
Setting the Temperature of Objects
Creating a User Define Primitive
Modifying Objects
Selecting Objects
Choosing the Movement Mode
Choosing the Snap Settings
Measure Modes for Objects
Setting Coordinate Systems
Drawing Objects
You can draw one-, two-, or three-dimensional objects using the Draw commands. You can alter
objects individually or together to create the geometry of your structure. In the Tools>Modeler
Options, Drawing tab, you can set a default to either draw objects directly with the mouse or by
invoking a Properties dialog in which you can enter the values for the object dimensions. The Dia-
log mode drawing feature works with the equation based curve, equation based surface, and all two
and three dimensional objects. You can toggle to Point mode via the F3 function key and to Dialog
mode via the F4 function key. When you use the Dialog mode for drawing objects the Edit property
of new primitives setting is ignored.
One-dimensional (1D) objects in the modeler include straight line, arc line, and spline segments, or
a combination of these - called polylines. One-dimensional objects are open objects; their boundar-
ies do not enclose a region, unless you connect their endpoints. They have length, but no surface or
volume. Generally they are used as temporary objects from which to create 2D objects.
Two-dimensional (2D) objects in the modeler include objects such as equation based surfaces, rect-
angles, ellipses, circles, and regular polygons. Two-dimensional objects are closed sheet objects;
their boundaries enclose a region. You can create 2D sheet objects by covering the enclosed region.
In many applications (FSS, antennas) it is essential to calculate net power flow through a surface.
You can also edit the properties of a polyline from the history tree to assign it a Cross Section property as
line or rectangular. If you then assign it either a height or a width, the polyline becomes a sheet object.
By default, the history tree organizes sheet objects according to their boundary assignments. To
change this, select the Sheets icon, and right-click to display the Group Sheets by Assignment
checkbox. Within the calculator sheet objects are listed under surface.
Three-dimensional (3D) objects in the modeler include objects such as boxes, cylinders, regular
polyhedra, cones, spheres, torii, and helices. These objects have boundaries that enclose a region
with volume.
You can create 3D objects by manipulating 2D objects along a plane or by using the appropriate
Draw commands. You can also edit the properties of a polyline from the history tree to assign it a Cross
Section property as circle rectangular. If you then assign it an appropriate diameter or both height or a width,
the polyline becomes a 3D object.
By default, the history tree groups 3D objects by material. To change this, select the Objects icon,
and right click to display the Group Objects by Material checkbox.
While you draw objects you can also:
• Select Movement Mode as 3D, In Plane, Out of Plane, Along X, Y or Z axis.
• Select Grid Plane as XY, YZ, or XZ.
• Set Snap Mode
• Set Reference Point for the movement mode
• Adjust the View
After you draw an object in the 3D Modeler window, you can modify the object’s properties, such
as its position, dimensions, or color, in the Properties dialog box. Most model object properties can
be assigned as Design variables when can then be manipulated during the solve to test their effect
on the solution. For non-model objects, you can both Post Processing variables (default and Design
variables,.
Note If you access your machine via Remote Desktop, if HFSS is running and one or more
modeler windows are open, those modeler windows automatically close. The message
manager window displays a message indicating that HFSS closed the modeler windows.
Related Topics
Assigning a Cross Section and Dimension to a Polyline
Modifying Objects
Drawing a Region
Setting the Temperature of Objects
Drawing a Straight Line Segment
To create an object with one or more straight line segments, use the Draw>Line command.
1. Click Draw>Line .
2. Select the first point of the line in one of the following ways:
• Click the point.
• You can accept the point or change it by editing its coordinates in the X, Y, and Z boxes in
the status bar.
To delete the last point that was entered, click Undo Previous Segment on the shortcut menu.
After using the undo feature, you can also use Redo Previous Segment on the shortcut menu.
3. Select the endpoint of the line by clicking the point or typing the coordinates in the text boxes
in the status bar.
The endpoint serves as the start point for a subsequent line segment.
To delete all points and start over, press ESC or click Escape Draw Mode on the shortcut
menu.
4. Complete the line in one of the following ways:
• Double-click the endpoint.
• Click Done on the context (right-click) menu.
• Press Enter.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, in which you can modify the object’s attributes by editing the Properties.
Those listed under the Command tab describe the commands used to create the object. These
commands also appear in the History tree. The Properties listed as line attributes include
Name, Orientation, whether a Model object, whether to Display Wireframe, Color, Transpar-
ency, and whether to Show Direction as arrows. The Show Direction property is most helpful
to unambiguously show the line start orientation when plotting fields along a line.
Note While drawing a polyline, you can switch between straight line, arc line, or spline
segments using the Set Edge Type commands on the shortcut menu.
Related Topics
Setting the Reference Point
Deleting Polyline Segments
Converting Polyline Segments
Drawing a Three-Point Arc
Drawing a Center-Point Arc Line
Drawing a Spline
Drawing a Polyline
Drawing a Three-Point Arc Line
In the modeler, a three-point arc line segment is an arced line defined by three points on its curve.
Use the Draw>Arc>3 Point command to create a polyline object with one or more arc line seg-
ments.
to unambiguously show the line start orientation when plotting fields along a line.
6. Click OK.
Based on the three points you specified, the modeler calculates the center point and radius of
the arc and draws an arced line through the three points.
Note While drawing a polyline, you can switch between arc line, straight line, or spline
segments using the Set Edge Type commands on the shortcut menu.
Related Topics
Setting the Reference Point
Drawing a Straight Line
Drawing a Spline
Drawing a Center-Point Arc Line
Drawing a Polyline
Deleting Polyline Segments
Converting Polyline Segments
Drawing a Center-Point Arc Line
In the modeler, a center-point arc line segment is an arced line defined by a center point, start point
and angle. Use the Draw>Arc>Center Point command to create a polyline object with one or
more center-point arc line segments.
1. Click Draw>Arc>Center Point .
2. Select the center point of the arc in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Select the start point, or radius, of the arc by clicking the point or typing the coordinates in the
text boxes in the status bar.
To delete the last point that was entered, click Undo Previous Segment on the shortcut menu.
After using the undo feature, you can also use Redo Previous Segment on the shortcut menu.
To delete all points and start over, press ESC or click Escape Draw Mode on the shortcut
menu.
4. Sweep the angle, or endpoint, of the arc by clicking the point or typing the coordinates in the
text boxes in the status bar.
5. If the endpoint is the last point of the polyline object, double-click the point to complete the
polyline or click Done on the shortcut menu.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s attributes.
6. Click OK.
Note While drawing a polyline, you can switch between arc line, straight line, or spline
segments using the Set Edge Type commands on the shortcut menu.
Related Topics
Setting the Reference Point
Drawing a Straight Line
Drawing a Spline
Drawing a Polyline
Deleting Polyline Segments
Converting Polyline Segments
Drawing a Three-Point Arc
Drawing a Spline
A spline is a curved line defined by three points. The modeler uses a natural spline type: a piece
wise cubic spline with an end condition that has a derivative of zero. Use the Draw>Spline com-
mand to create a polyline object with one or more spline segments.
1. Click Draw>Spline .
2. Select the spline’s start point in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar, and then press Enter.
To delete the last point entered, click Undo Previous Segment on the shortcut menu.After
using the undo feature, you can also use Redo Previous Segment on the shortcut menu.
To delete all selected points and start over, press ESC or click Escape Draw Mode on the
shortcut menu.
3. Select the midpoint of the spline by clicking the point or typing the coordinates in the text
boxes in the status bar.
4. Select the endpoint of the spline by clicking the point or typing the coordinates in the text
boxes in the status bar.
The endpoint serves as the start point for a subsequent spline segment.
5. Complete the spline in one of the following ways:
• Double-click the endpoint.
• Click Done on the shortcut menu.
• Press Enter.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, in which you can modify the object’s attributes by editing the Properties.
Those listed under the Command tab describe the commands used to create the object. These
commands also appear in the History tree. The Properties listed as line attributes include
Name, Orientation, whether a Model object, whether to Display Wireframe, Color, Transpar-
ency, and whether to Show Direction as arrows. The Show Direction property is most helpful
to unambiguously show the line start orientation when plotting fields along a line.
6. Click OK.
Note While drawing a polyline, you can switch between spline, straight line, or arc line
segments using the Set Edge Type commands on the shortcut menu.
Related Topics
Setting the Reference Point
Drawing a Polyline
Drawing a Center-Point Arc Line
Deleting Polyline Segments
Converting Polyline Segments
Drawing a Polyline
A polyline is a single object that includes any combination of straight line, arc line, or spline seg-
ments. The endpoint of one segment is the start point for the next segment. Use the shortcut menu’s
Set Edge Type commands to switch between straight line, arc line, or spline segments while draw-
ing a polyline.
In the Polyline section of Operation tab of the Modeler Options, select or clear the Automati-
cally cover closed polylines check box.
If checked, closed polylines become sheet objects, and are listed as such in the History tree. If
unchecked, closed polylines are listed under lines in the History tree.
1. Click Draw>Line .
2. Right-click in the 3D Modeler window to access the shortcut menu, and then point to Set
Edge Type.
3. Click Straight, Spline, 3 Point Arc, or Center Point Arc depending on which type of poly-
line segment you want to draw.
4. If you clicked Straight, follow the procedure for drawing a straight line.
If you clicked Spline, follow the procedure for drawing a spline.
If you clicked 3 Point Arc, follow the procedure for drawing a three-point arc line.
If you clicked Center Point Arc, follow the procedure for drawing a center-point arc line.
5. Repeat steps 2 and 3 for each segment of the polyline object. The endpoint of the previous seg-
ment serves as the start point for the next segment.
The shortcut menu lets you do the following for each segment:
Undo Previous Segment or Redo Previous Segment.
6. Complete the polyline in one of the following ways:
• Double-click the endpoint of the final segment.
• Click Done on the shortcut menu.
Note To connect the polyline’s start and endpoints, click Close Polyline on the shortcut menu.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, in which you can modify the object’s attributes by editing the Properties.
Those listed under the Command tab describe the commands used to create the object. These
commands also appear in the History tree. The Properties listed as line attributes include
Name, Orientation, whether a Model object, whether to Display Wireframe, Color, Transpar-
ency, and whether to Show Direction as arrows. The Show Direction property is most helpful
to unambiguously show the line start orientation when plotting fields along a line. Notice that
by going to the History tree selecting Create Polyline for that object, you can assign a cross
section and dimensions to a polyline.
7. Click OK.
If you select a polyline in the History tree, you can use the Measure mode to see the total length.
Related Topics
Setting the Reference Point
Assigning a Cross Section and Dimension to a Polyline
Drawing a Straight Line
Drawing a Three-Point Arc
Drawing a Center-Point Arc Line
Drawing an Equation-Based Curve
Drawing a Spline
Deleting Polyline Segments
Converting Polyline Segments
Generate History
Setting Modeler Options: Operations Tab
Assigning a Cross Section and Dimensions to a Polyline
By viewing the History tree property of a polyline, you can assign either a line, circle or rectangle
cross section to a polyline. This assignment enables editable dimension properties of width for a
line, diameter for a circle, and height and width for a rectangle. To assign a cross section to a poly-
line:
1. In the History tree of the Modeler window, right-click on the polyline that you want to give a
cross section.
This selects the polyline, displays the polyline properties in the docked properties (if you have
if displays) and displays a shortcut menu where you can choose Properties... to display the
undocked Properties window for the polyline.
2. In a Properties window (either docked or undocked) for the selected polyline click on None on
the Type line under Cross Section to display the choices for Line, Circle, Rectangle.
• Selecting Circle causes the Cross Section area of the polyline properties to display an
editable field for diameter.
• Selecting Rectangle causes the Cross Section area of the polyline properties to display
editable fields for Orientation, Width and Height.
4. If you select Line or Rectangle, you can edit the Orientation as Auto, X, Y, or Z. This provides
the direction in which the dimension extends.
5. Specify the dimensions and select the units for the Cross section.
Type a value in the dimension field(s) and select units from the drop down menu.
The dimensions must be reasonable relative to the specified shape and orientation of the poly-
line. If the polyline cannot be extended into current Orientation for the given dimension(s), you
will receive a warning. If you receive a warning, check the Orientation, dimension and units.
When the modeler can extend the dimensions legally, it displays the modified object, and lists
it in the History tree as either a Sheet object (Line or one dimensional Rectangle) or as a Solid
object (Circle or two dimensional Rectangle).
6. You can modify the new polyline either by editing the properties, or by using the History tree
to select one of the line objects that make up the polyline, and right clicking to display the
popup menu showing commands to Insert, Delete, or display editable segment Properties.
A segment that you select in the Project tree is indicated in the Modeler window by a line in
the dimensioned object. If you insert a new segment, it adopts the dimensions you specified for
the polyline object.
Related Topics
Setting the Reference Point
Drawing a Polyline
Drawing an Equation-Based Curve
Deleting Polyline Segments
Inserting Line Segments
Note To connect the polyline’s start and endpoints, click Close Polyline on the shortcut menu.
The Properties dialog box appears, in which you can modify the object’s attributes by editing
the Properties. Those listed under the Command tab describe the commands used to create the
object. These commands also appear in the History tree. The Properties listed as line attributes
include Name, Orientation, whether a Model object, whether to Display Wireframe, Color,
Transparency, and whether to Show Direction as arrows. The Show Direction property is most
helpful to unambiguously show the line start orientation when plotting fields along a line.
7. Click OK.
Related Topics
Drawing a Center-Point Arc Line
Deleting Polyline Segments
Converting Polyline Segments
• Any unitless value input in equation based curve is taken as model units. For example, for
Y(_t) = 1, the y value is taken as 1 model units (say mm). If a value has units, then it is
converted to model units and used. For example, if we specify Y(_t) = 1cm, then y value
will be correctly taken as 10mm.
• While parsing expressions, equation based curves convert each variable separately to
model units and assume that the resulting expression is in model units.
• Equation based curves depend on the variable value library to correctly evaluate the units
of expression.
3. Select a start value from the Start_t pull-down list.
4. Select an end value from the End_t pull-down list.
5. Select the number of points in the curve from the Points pull-down list.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, in which you can modify the object’s attributes by editing the Properties.
Those listed under the Command tab describe the commands used to create the object. These
commands also appear in the History tree. The Properties listed as line attributes include
Name, Orientation, whether a Model object, whether to Display Wireframe, Color, Transpar-
ency, and whether to Show Direction as arrows. The Show Direction property is most helpful
to unambiguously show the line start orientation when plotting fields along a line.
6. Click OK on the Properties dialog box.
Related Topics
Setting the Reference Point
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Related Topics
Setting the Reference Point
Surface Approximation
Creating Segmented Geometry
Covering Lines
Drawing an Ellipse
Draw an ellipse by specifying a center point, base radius, and secondary radius.
1. Click Draw>Ellipse .
2. Select the center point of the ellipse in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Specify the base radius of the ellipse. If the current drawing plane is xy, then x is the base
radius direction. If the drawing plane is yz, then y is the base radius direction. If the drawing
plane is xz, then z is the base radius direction. Select the point in one of the following ways:
• Click the point. HFSS constrains mouse movement to the base radius direction.
• Type the coordinates of a point relative to the center point in the dX, dY, or dZ box,
where d is the distance from the previously selected point.
4. Specify the secondary radius of the ellipse. Select the point in one of the following ways:
• Click the point. HFSS constrains mouse movement to a point on the plane orthogonal to
the base radius direction.
• Type the coordinates of a point relative to the center point in the dX, dY, or dZ box.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
The Ratio value represents the aspect ratio of the secondary radius to the base radius.
5. Click OK.
If the Automatically cover closed polyline option is selected in the Modeler Options win-
dow, the ellipse will be covered, resulting in a 2D sheet object. Otherwise it will be a closed 1D
polyline object.
If the base radius is larger than the secondary radius, the ellipse’s longer axis will lie along the
default base radius direction. If the secondary radius is larger than the base radius, the ellipse’s lon-
ger axis will lie perpendicular to the default base radius direction. To create an ellipse with an arbi-
trary orientation, rotate or move the ellipse after drawing it.
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Related Topics
Setting the Reference Point
1. Click Draw>Rectangle .
2. Select the first diagonal corner in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
To delete the selected point and start over, press ESC or click Escape Draw Mode on the
shortcut menu.
3. Select the second corner of the rectangle in one of the following ways:
• Click the point.
• Type the coordinates of the point relative to the first diagonal corner in the dX, dY, and
dZ boxes, where d is the distance from the previously selected point.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
4. Click OK.
If the Automatically cover closed polyline option is selected in the Modeler Options win-
dow, the rectangle will be covered, resulting in a 2D sheet object. Otherwise it will be a closed
1D polyline object.
Related Topics
Setting the Reference Point
Covering Lines
Drawing a Regular Polygon
A regular polygon is a 2D object with three or more equal sides. Regular polygons are useful for
drawing faceted 2D objects.
1. Click Draw>Regular Polygon .
2. Select the center point of the polygon in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Specify the polygon’s radius, the distance from the center point to one of the polygon’s verti-
ces, in one of the following ways:
• Click the point.
• Type the coordinates of the point relative to the center point in the dX, dY, and dZ boxes,
Note The radius is measured from the center point to a corner of the polygon, or the
intersection of two edges. It is not measured from the center point to the midpoint of an
edge.
If the Automatically cover closed polyline option is selected in the Modeler Options win-
dow, the polygon will be covered, resulting in a 2D sheet object. Otherwise it will be a closed
1D polyline object.
Related Topics
Setting the Reference Point
Covering Lines
Drawing an Equation-Based Surface
Any surface that can be described by an equation in three dimensions can be drawn.
1. Click Draw>Equation Based Surface .
The Equation Based Surface dialog box opens.
2. Type equations for X(_u, _v), Y(_u, _v), and Z(_u, _v).
• Any unitless value input in equation based curve is taken as model units. For example, for
Y(_t) = 1, the y value is taken as 1 model units (say mm). If a value has units, then it is
converted to model units and used. For example, if we specify Y(_t) = 1cm, then y value
will be correctly taken as 10mm.
• While parsing expressions, equation based curves convert each variable separately to
model units and assume that the resulting expression is in model units.
• Equation based curves depend on the variable value library to correctly evaluate the units
of expression.
3. Select start values from the Start_u and Start_v pull-down lists.
Select end values from the End_u and End_v pull-down lists.If the Modeler option for editing
properties of new primitives is checked, the Properties dialog box appears, enabling you to
modify the object’s attributes.
4. Click OK on the Properties dialog box.
Related Topics
Setting the Reference Point
Assigning a Cross Section and Dimension to a Polyline
Drawing an Equation Based Curve
Drawing a Sphere
Draw a sphere, a 3D circle, by selecting a center point and a radius. Spheres are drawn as true sur-
faces in the modeler.
1. Click Draw>Sphere .
2. Select the center point of the sphere in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Specify the radius by selecting a point on the sphere’s circumference in one of the following
ways:
• Click the point.
• Type the coordinates of the point relative to the center point in the dX, dY, and dZ boxes,
where d is the distance from the previously selected point.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
4. Click OK.
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values.
For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Drawing a Cylinder
Draw a cylinder by selecting a center point, radius, and height. Cylinders are drawn as true surfaces
in the modeler.
1. Click Draw>Cylinder .
2. Select the center point of the cylinder’s base circle in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Specify the radius by selecting a point on the base circle’s circumference in one of the follow-
ing ways:
• Click the point.
• Type the coordinates of the point relative to the center point in the dX, dY, and dZ boxes,
where d is the distance from the previously selected point.
4. Specify the cylinder’s height by selecting a point on the axis perpendicular to the base circle’s
plane. Select the point by clicking the point or typing the coordinates in the dX, dY, and dZ
boxes.
Note If you create a cylinder with a height of zero, HFSS draws a circular sheet object.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
5. Click OK.
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Related Topics
Setting the Reference Point
Assigning a Cross Section and Dimension to a Polyline
Modifying Surface Approximation Settings
Creating Segmented Geometry
Drawing a Box
Draw a box by selecting two diagonally opposite corners of the base rectangle, then specifying the
height.
1. Click Draw>Box .
2. Select the first diagonal corner of the base rectangle in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
To delete the selected point and start over, press ESC or click Escape Draw Mode on the
shortcut menu.
3. Select the second corner of the base rectangle in one of the following ways:
• Click the point.
• Type the coordinates of the point relative to the first diagonal corner in the dX, dY, and
dZ boxes, where d is the distance from the previously selected point.
4. Specify the height of the box by selecting a point on the axis perpendicular to the base rectan-
gle. Select the point by clicking the point or typing the coordinates in the dX, dY, and dZ
boxes.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
5. Click OK.
Related Topics
Setting the Reference Point
Drawing a Model 7-21
HFSS Online Help
Note The radius is measured from the center point to a corner of the polygon, or the
intersection of two edges. It is not measured from the center point to the midpoint of an
edge.
If the Automatically cover closed polyline option is selected in the Modeler Options dialog
box, the polygon will be covered, resulting in a 2D sheet object. Otherwise it will be a closed
1D polyline object.
Related Topics
Setting the Reference Point
Covering Lines
Drawing a Cone
Draw a cone by selecting the center point and radius of the cone’s base circle, then specifying the
radius of the cone’s top circle and the cone’s height. Cones are drawn as true surfaces in the mod-
eler.
1. Click Draw>Cone .
2. Select the center point of the cone’s base circle in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Specify the radius of the cone’s base circle by selecting a point on the base circle’s circumfer-
ence. Select the point in one of the following ways:
• Click the point.
• Type the coordinates of the point relative to the center point in the dX, dY, and dZ boxes,
where d is the distance from the previously selected point.
4. Specify the radius of the cone’s top circle by selecting a point on its circumference. Select the
point by clicking it or typing its coordinates in the dX, dY, and dZ boxes.
To create an apex, select the same center point as the cone’s base circle.
5. Specify the height of the cone by selecting a point on the axis perpendicular to the base circle’s
plane. Select the point by clicking the point or typing the coordinates in the dX, dY, and dZ
boxes.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
6. Click OK.
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Related Topics
Setting the Reference Point
Drawing a Torus
Draw a torus by selecting its center point, major radius, and minor radius. The modeler then sweeps
a circle around a circular path. Toruses are drawn as true surfaces in the modeler.
1. Click Draw>Torus .
2. Select the center point of the torus in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Specify the major radius by selecting a point in one of the following ways:
• Click the point.
• Type the coordinates of the point relative to the center point in the dX, dY, and dZ boxes,
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Drawing a Helix
A helix is a 3D spiral object created by sweeping a 1D or 2D object along a vector. Sweeping a 1D
object results in a hollow 3D object. Sweeping a 2D sheet object results in a 3D solid object.
1. Select the 1D or 2D object you want to sweep to form a helix.
2. Click Draw>Helix .
3. Draw the vector you want to sweep the object along. The two points that describe the vector
affect axis direction only and not the helix length. The helix length is determined when you
enter the pitch and number of turns in the Pitch and Turns text boxes. The initial radius of the
helix is determined by the axis position relative to the object being swept.
a. Select the start point by clicking the point or typing its coordinates in the X, Y, and Z text
boxes.
b. Select the endpoint by clicking the point or typing its coordinates relative to the start point
in the dX, dY, and dZ boxes.
The Helix dialog box appears.
4. For Turn Direction, select Right hand if the turn direction is clockwise and Left hand if the
turn direction is counter-clockwise.
5. In the Pitch text box, type the distance between each turn in the helix, and click a unit in the
pull-down list.
6. In the Turns text box, type the number of complete revolutions the object will make along the
vector.
7. In the Radius Change per Turn text box, type a number for the increase in the radius and
select the units from the pull-down list.
8. After you set these values, the selected object is swept along the vector to form a helix. The
original object you swept is deleted.
If the Modeler option for editing properties of new primitives is checked, the Properties dia-
log box appears, enabling you to modify the object’s properties.
9. Click OK.
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Related Topics
Setting the Reference Point
Drawing a Segmented Helix with Polygon Cross-Section using a User-Defined Primitive
Drawing a Segmented Helix with Rectangular Cross-Section using a User Defined Primitive.
Drawing a Segmented Helix with Polygon Cross-Section Using a User
Defined Primitive
Ansoft provides you with a DLL to define the parameters of a segmented helix with a polygon
cross-section.
1. Click Draw>User Defined Primitive>SysLib>SegmentedHelix>PolygonHelix.
The Create User Defined Part dialog box appears. The Parameters tab permits you to edit
the parameters. An Info tab contains information about the user defined primitive, its purpose,
the company/author who created it, the date created and the version number.
2. Specify the values for the following parameters:
PolygonSegments Number of segments in the polygon cross-section. Enter
zero (0) for true circle
PolygonRadius Radius of the polygon cross-section.
StartHelixRadius The radius of a segmented helix is defined from the helix
center of rotation to the center of the helix cross-section at
segment transitions. The first and last segments of the
helix are half segments. See this figure.
Related Topics
Setting the Reference Point
Creating a User Defined Primitive
Drawing a Segmented Helix with Polygon Cross-Section using a User-Defined Primitive
Drawing a Spiral
A spiral is a 2D or 3D spiral object created by sweeping an object around a vector. Sweeping a 1D
object results in a 2D sheet object. Sweeping a 2D sheet object results in a 3D solid object.
1. Select the 1D or 2D object you want to sweep to form a spiral.
2. Click Draw>Spiral .
3. Draw the vector you want to sweep the object around:
a. Select the start point by clicking the point or typing its coordinates in the X, Y, and Z text
boxes.
b. Select the endpoint by clicking the point or typing its coordinates relative to the start point
in the dX, dY, and dZ boxes.
The Spiral dialog box appears.
4. Select Right hand if the turn direction is clockwise and Left hand if the turn direction is
Drawing a Model 7-27
HFSS Online Help
counter-clockwise.
5. In the Radius Change text box, type the difference in radius between each turn of the spiral.
The radius of the first turn is measured from the center point of the 1D or 2D object you are
sweeping to the vector you drew.
6. Click a unit for the radius in the pull-down list.
7. In the Turns text box, type the number of complete revolutions the object will make around
the vector.
The selected object is swept around the vector to form a spiral. The original object you swept is
deleted. If the Modeler option for editing properties of new primitives is checked, the Proper-
ties dialog box appears, enabling you to modify the object’s properties.
8. Click OK.
This 3D spiral was created from a 2D circle drawn at z = 0. The turn direction was right hand,
the radius change was set at 2, and the number of turns was set at 2.
Note The 3D Geometry Modeler permits drawing of true-curved objects. However, the
solution will be obtained with a tetrahedral mesh which conforms to the true surface only
within the limits identified by certain mesh settings. The modeler has default settings for
this conformance which is a reasonable trade-off between solution speed and solution
quality for most objects, but may not be ideal for all such objects. High-aspect ratio
curves structures, such as helices with narrow and curved cross-sections, may benefit
from user control of the faceting values. For details about these commands see:
Technical Notes, "Surface Approximations" and related sections, Rectilinear Elements
and Curvilinear Elements, "Modifying Surface Approximations," and "Guidelines for
Modifying Surface Approximations"
Related Topics
Setting the Reference Point
Drawing a Spiral Using User Defined Primitives
Drawing a Spiral using User Defined Primitives
Ansoft provides you with a DLL to define the parameters of a rectangular spiral.
1. Click Draw>User Defined Primitive>SysLib>Examples>RectangularSpiral.
The Create User Defined Part dialog box appears. The Parameters tab permits you to see
edit the parameters. An Info tab contains information about the user defined primitive, its pur-
pose, the company/author who created it, the date created and the version number.
2. Specify the values for the following parameters:
Xpos X location of the starting point.
Ypos Y location of the starting point.
TurnSep The separation distance between turns.
Turns The number of complete revolutions the object will make around the vector
Width The width of the spiral.
Height The height of the spiral. If you specify the height as zero, the modeler draws a
sheet object.
3. Click OK.
This creates the primitive and displays the Properties dialog for the new object.
Hint To see newly created DLLs, click Draw>User Defined Primitive>Update Menu.
To see the primitives that you have created, click Draw>User Defined
Primitive>UserLib.
Related Topics
Setting the Reference Point
Creating a User Defined Primitive
Drawing a Spiral
Drawing a Bondwire
A bondwire is a thin metal wire that connects a metal signal trace with a chip. Please see the topic
Bondwires in the Technical Notes before drawing a bondwire.
1. Click Draw>Bondwire .
2. Select the bond pad point in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
3. Select the lead point by clicking the point or typing the coordinates in the text boxes in the sta-
tus bar.
The Bondwires dialog box appears.
4. In the Type list, click the JEDEC modeling standard shape you want the bondwire to have:
JEDEC 4-point, JEDEC 5-point, or Low.
The Type selection changes the dialogue bondwire graphic, and shows options for that type.
5. Enter the number of facets in the bondwire in the No. of Facets text box.
The minimum value is 3. The value describes the number of faces that make up the circumfer-
ence of the bondwire.
6. In the diameter field, specify a diameter value and select the units from the pull-down menu.
7. Enter the height between the bond pad and the top of the loop in the h1 text box. Include the
height’s unit of length.
8. The value in the h2 text box is the height between the bond pad and the lead point. It was cal-
culated by HFSS based on the lead point you selected. If you modify the value of h2, the lead
point will be modified.
Optionally, type a new value in the h2 text box. Include the height’s unit of length.
9. If you selected JEDEC 5-point or Low do the following:
a. Type the angle between the horizontal plane and the wire at the bond pad point in the
alpha text box.
b. Type the angle between the horizontal plane and the wire at the lead point in the beta text
box.
10. Click OK.
Related Topics
Setting the Reference Point
Technical Notes: Bondwires
7-30 Drawing a Model
HFSS Online Help
Drawing a Point
Drawing a point object within the problem region enables you to plot fields or perform field com-
putations at that point. Points are always considered non-model objects by the modeler.
1. Click Draw>Point .
2. Select the point in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
The point is listed under Points in the history tree.
Related Topics
Setting the Reference Point
Modifying Markers on Point Plots
Drawing Non-Model Objects
Drawing a Plane
A plane object is a cutplane through the problem region. You can plot fields or perform field com-
putations on its surface. Planes are always considered non-model objects by the modeler.
1. Click Draw>Plane .
2. Select the origin in one of the following ways:
• Click the point.
• Type the point’s coordinates in the text boxes in the status bar.
To delete the selected point and start over, press ESC.
3. Select a normal point in one of the following ways:
• Click the point.
• Type the coordinates of the point relative to the origin in the dX, dY, and dZ boxes, where
d is the distance from the previously selected point.
The plane is created. Its center point is located at the origin you specified and oriented perpen-
dicular to the normal point you specified. The plane is listed under Planes in the history tree.
Note You only need to draw a plane that does not lie on a pre-defined xy, yz, and xz plane.
Default planes are created on the xy, yz, and xz planes of the global coordinate system as
well as any new coordinate system you create.
Related Topics
Drawing Non-Model Objects
Segmented Objects
To create segmented circles, ellipses, and cylinders use the Number of Segments parameter on the
Command Tab of the Properties dialog as shown below. To convert an object from true surface to
segmented, do the following:
1. Select the circle, ellipse, or cylinder in the modeler window or in the history tree.
2. In the command tab of the properties window (shown docked below), change the Number of
Values of 1 and 2 are not valid values for the circle, ellipse, or cylinder command and will
cause an error.
Related Topics
Modifying Surface Approximation Settings
Creating Segmented Geometry
Drawing Non-Model Objects
If you want to create an object that does not affect the geometric model, define the object as non
model. This ensures that the object is used for analysis only; it will not affect the solution process.
After drawing the object, assuming it lies in the problem region, you can plot field quantities on it.
You can assign output variables (default) and design variable as property values for non-model
objects.
Following are examples of using non-model objects to analyze a solution:
• Draw a polyline along which to plot fields or perform field computations. Note that when you
create a value versus distance plot, by default, the line will be divided into 100 equally spaced
points. You can modify the number of points into which the line is divided in the Edit Sweeps
dialog box.For more information, see Specifying Variable Values for a Sweep Definition.
Drawing a Model 7-33
HFSS Online Help
Model Analysis
For some models it may be beneficial to remove unnecessary small entities and to fix object mis-
alignments to avoid potential mesh issues. HFSS includes Model Analysis functions to help you
evaluate models you have imported or created. Select Modeler> Model Analysis to see the menu
options. Depending on the design and the current selection, some features may not be enabled. The
menu includes the following commands.
• Analyze Objects
• Analyze InterObject Misalignment
• Analyze Surface Mesh
• Show Analysis dialog
Note Before running model analysis, you must remove all command history for the selected
object by using the Purge History command. If you need to save the object history, save
a separate copy.
1. After import, you typically perform validation check. This lets you focus on objects and object
pairs that have errors and or warnings. The objects that fail should be analyzed by using the
Modeler>Model Analysis>Analyze Objects menu item.
2. Select the objects and invoke Modeler>Model Analysis>Analyze Objects.
This displays the Analysis Options dialog to allow you to specify settings for entity check
level, and small feature detection.
When you OK this dialog, the initial analysis executes and the Model Analysis dialog is dis-
played.
3. Choose the objects that have "Invalid Entities Found" and Perform>Heal Objects.
In most cases, the objects will be healed and the errors fixed.
4. If errors still persist, choose the edges and faces and click on Delete.
This will replace the selected face/edge object by a tolerant edge/vertex respectively. In some
cases the replacement of the face/edge by tolerant edge/vertex will fail.
When models pass the initial validity checks, mesh generation could still fail. The following errors
can be present in models: (See Error Detection.)
1. Non-manifold topology. These are non-manifold edges and vertices that are present in the
model.
2. Object pair intersection. This detects whether pairs of objects intersect.
3. Small feature detection – small edge length, small face area and sliver face detection.
4. Mis-aligned entities detection – detects pairs of faces from objects that can be aligned to
remove object intersections. This improves the probability of mesh success.
5. Mesh failure error display. This is available for single object, object pairs and last simulation
run (all objects in a model). Errors reported by the meshing module are reported to the user.
Errors of type 3 and 4 should be resolved before you invoke the meshing for the model.
By default, the Heal command is automatically applied to imported objects.
Related Topics
Set Material Override
Analysis Options Dialog
Healing
Technical Notes: Removing Object Intersections
Healing Non-manifold Objects
Healing Options
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Analysis Options Dialog
To perform analysis on an object according to specified features and tolerance values:
1. Select the object you want to analyze and click Modeler> Model Analysis>Analyze Objects.
This displays the Analysis Options dialog, with the Analysis Options tab selected. Selecting
Modeler>Model Analysis>Heal also displays this dialog. If, during Modeler>Import... you
select Heal Imported Objects and Manual on the file browser dialog, you also see this dia-
log.
2. If desired, check the Perform Entity Check Errors checkbox.
This enables the Check Level menu. The setting can be Basic, Strict, or Comprehensive. See
Modeler Validation Settings for more explanation.
3. If desired, click the check boxes to enable and set the Detect Feature settings:
• Detect Holes, and specify the Maximum Radius.
• Detect Chamfers, and specify the Maximum Width.
• Detect Blends, and specify the Maximum Radius.
4. If desired set the Detect Small Entities features and tolerance values.
• Small Edges, length less than
• Small Faces, area less than
• Sliver Faces, which enables:
Object Bounding Box Scale Factor
Sliver Edge Width
5. Click the Properties tab to see a listing of the geometric properties of the selected object.
6. Clicking OK on this dialog displays the Model Analysis dialog which contains the results of
the analysis.
Related Topics
Heal
Analysis Options Dialog
Model Analysis dialog.
Analyzing the Surface Mesh
To set the options to analyze the surface mesh:
1. Select an object of interest.
This enables the Analyze Surface Mesh command in the menu.
2. Click Modeler>Model Analysis>Analyze Surface Mesh.
The Surface Mesh Analysis Options dialog box appears. This dialog box allows you to set
parameters to remove.
• You can also open the Surface Mesh Analysis Options dialog box from the Model Anal-
ysis dialog box via the Perform pull-down menu on the Objects tab.
3. Select or clear the Perform Object Pairs Analysis check box. Selecting this option evaluates
the mesh for all combinations of the selected objects.
4. Select or clear the Ignore Objects Separated by greater than check box, and enter a value in
the text box. Selecting this option means that object pairs are disregarded from analysis if their
separation is greater than the specified value.
5. Click OK to perform the analysis with the selected options.
The Model Analysis dialog box appears, displaying the results of the analysis.
Related Topics
Heal
Model Analysis dialog.
Model Analysis dialog
This dialog contains results for all model analysis, including diagnostic information relating to
mesh issues. To view the analysis options:
1. Click Modeler> Model Analysis>Show Analysis Dialog.
A submenu appears.
2. Select one of the following from the submenu:
• Objects
• Objects Misalignment
• Surface Mesh
• Last Simulation Mesh
The Model Analysis dialog box appears. (This dialog box also appears automatically after
clicking OK in the Analysis Options dialog box.)
3. Select the Auto zoom to selection check box to automatically zoom to the item selected on the
Objects tab.
4. Make the desired changes on each tab in the Model Analysis dialog box.
• Objects tab
• Objects Misalignment tab
• Surface Mesh (Single/Pairs) tab
• Last Simulation Mesh tab
Click Close to close the Model Analysis dialog box.Related Topics
Heal
Analysis Options
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Objects Tab
All results relating to model analysis of specific objects are presented under the Objects tab.
1. The results table contains the following information.
• Name - column listing the objects in the current design.
• Last Analysis status - column giving the analysis status of the listed objects. Objects can
have the following status:
• Good - the object contains no invalid geometry entities given the tolerance values
specified in the Analysis Options dialog.
• Null Body - the object is non-existent.
• Analysis not performed - the object was not selected for analysis.
• Invalid entity errors - these are api_check_entity() errors and non-manifold errors
which Ansoft recommends that you fix before meshing.
• Small entity errors - small faces, sliver faces and small edges that are optionally
detected based on the tolerance limits specified in the Analysis Options dialog.
2. Select any object name in the table which contains errors to display a set of radio buttons in the
panel and a list of corresponding faces, edges and vertices.
Note Auto Zoom to Selection -- if this option is checked, the modeler automatically zooms to
the item selected in the Model Analysis dialog box.
3. Select the face, edge or vertex entity from the list to view the error description in the Descrip-
tion field.
4. Select the Delete button if you want to remove a selected face or edge entity.
5. Select the Perform button to list the commands that you can execute on the selected objects in
the Results table.
• Heal Objects - repairs invalid geometry entities for the selected objects within the speci-
fied tolerance settings. The Healing Analysis dialog will appear.
• Analyze Objects - evaluates the object status. Selecting this displays the Analysis Options
Drawing a Model 7-39
HFSS Online Help
dialog.
• Analyze Surface Mesh - invokes a mesh for each selected object and reports analysis
results under the Surface Mesh (Single/Pairs) tab. Selecting this option displays a dialog
with radio buttons to select.
• Perform Object Pairs Analysis - evaluates mesh for all combinations of the selected
objects.
• Ignore objects separated by greater than a specified value - object pairs are disre-
garded from analysis if their separation is greater than the specified value.
• Click OK to perform the analysis with the selected options.
• Analyze Interobject Misalignment - determines any misalignments between two
selected objects in the results table. The results are reported under the Objects Misalign-
ment tab.
• Display Healing Log -- checking this causes the Model Analysis dialog to display a healing
log which includes information about operations performed on an object during the healing
process.
Related Topics
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
2. You can select individual or multiple rows and perform Align Faces. In some cases, face align-
ment will fail if the topology of the body changes by a large factor after alignment.
3. Identify individual bodies and body pairs that fail to mesh.
4. Perform Mesh analysis on individual objects and object pairs.
5. Review the reports and fix the errors.
Related Topics
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Technical Notes: Removing Object Intersections
Healing Non-manifold Objects
Healing Options
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Set Material Override for HFSS
Set Material Override for HFSS-IE
Select by intersection error message.
Surface Mesh (Single/Pairs) Tab
The panel displays the results of a surface mesh analysis.
1. You can display results for:
• Individual Objects
• Object Pairs
Note Auto Zoom to Selection -- if this option is checked, the modeler automatically zooms to
the object or object pair selected.
• Auto Zoom to Selection -- checking this causes the modeler to automatically zoom to objects
or faces corresponding to the error.
Related Topics
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Related Topics
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Note Users must be careful: this setting changes the "ground rules" of the modeler, and may
have unexpected results.
Related Topics
Drawing a Model 7-43
HFSS Online Help
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Materials
Setting the Temperature of Objects
Note Users must be careful: these settings change the "ground rules" of the modeler, and may
have unexpected results.
Related Topics
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Materials
Setting the Temperature of Objects
Heal
The Heal command provides a way to correct geometric violations and to remove specific kinds of
small features. When models are imported, two types of errors can occur – geometry errors and
topology errors. Geometry errors are errors in definition of the underlying geometry while topology
errors are errors in how the underlying components like faces, edges and vertices are connected.
Ansoft recommends that these be fixed before you invoke mesh generation.
Imported objects which have only one operation on the history tree, can be healed. (Use the Purge
History command to remove unwanted history operations before using Heal.)
Note If you need to save the object history, save a separate copy for that purpose before you
heal the object.
While working on analyzing complex bodies, it is sometimes useful to examine faces, edges and
vertices. In particular it is useful to find the connected faces for a face or edge or vertex, connected
edges for a face/edge/vertex and connected vertices for a face/edge/vertex. The additional selection
modes are available under Edit->Select and via the toolbar icons.
Related Topics
Align Faces
Remove Faces
Remove Edges
Technical Notes: Removing Object Intersections
Healing Non-manifold Objects
Healing Options
Specifying the Model Resolution
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Healing Non-Manifold Objects
Non-manifold objects, in simple terms, are non-physical objects or objects that cannot be manufac-
tured. For example, objects that intersect themselves (like the symbol for infinity in 2d) are clearly
non-manifold. In addition objects that touch themselves may be non-manifold such as when a 2D
object touches itself at a vertex, or a 3D object touches itself at a point or edge. These cases are
shown in the figure below.
Another type of non-manifold object has mixed dimensionality. For example, a pair of 2D objects
connected by a 1D line segment, or a pair of 3D objects connected by a 2D sheet object. These
cases are illustrated below.
The criteria for manufacturability is a simple manifestation of a complex mathematical concept that
must be adhered to in the solid modeling system. When creating geometry, either directly, or
through boolean operations, you should always consider whether or not the resulting operation will
result in an object that could not be manufactured. If this is the case, then the object will cause an
error in the modeler or in the meshing system.
To heal non-manifold objects:
1. Identify an edge that is non-manifold.
2. Select the connected faces.
You can use the Face selection toolbar icons.
3. Create a face coordinate system on the planar face.
4. Create a small box to cover the non-manifold edge.
5. Either do a union or a subtraction to remove the faces that contain the non-manifold edge.
The non-manifold edge is now removed. You may also remove or add a small portion of the
model.
Related Topics
Healing
Stitch Sheets
Technical Notes: Removing Object Intersections
Healing Non-manifold Objects
Specifying the Model Resolution
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Stitch Sheets
Use the Modeler>Model Healing>Stitch Sheets command to stitch selected sheets.
1. Select two or more sheet objects.
This enables the Stitch Sheets command on the Modeler>Model Healing submenu.
2. Click Modeler>Model Healing>Stitch Sheets
This displays a Stitch dialog with a Maximum Stitch Tolerance field. The default value (auto)
comes from the Healing dialog Options tab with Manual Healing selected. You may edit the
value in the Stitch dialog or in the Healing Options.
3. Click OK.
This closes the dialog and attempts to perform stitching on the selected sheets. If the sheets are
separated beyond the stitch tolerance, stitching is not performed and a warning is issued.
Related Topics
Healing
Related Topics
Align Faces
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Set Material Override
Remove Selected Edges
Use this Modeler>Model Healing>Remove Edges command to remove the selected edges. You
can also use the toolbar icon when you have made an appropriate edge selection
Related Topics
Technical Notes: Healing and Meshing
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Technical Notes: Error Types
Technical Notes: Error Detection
Analyze Objects
Analyze Interobject Misalignment
Analyze Surface Mesh
Healing
Note The header files include information on the methods that are available for use in your
source code. They must be included when you compile the DLL.
UDPDir/
myUDP.dsw
myUDP.dsp
Headers/
UserDefinedPrimitiveDLLInclude.h
UserDefinedPrimitiveStructures.h
Sources/
myUDP.cpp
7. Open myUDP.dsw using Microsoft Visual C++ Developer Studio, and edit the source code to
create your desired primitive. You may also add additional headers and source files as appro-
priate.
The UDP dll contains a data structure called UDPPrimitiveTypeInfo. This contains informa-
tion about the udp, its purpose, company/author who created it, date created and the version
number. When you select a primitive from your library, you see the Create Primitive dialog
with a Parameters tab for setting the parameters, and an Info tab with the information from
this data structure.
8. Build myUDP.dll using the Win32 Release configuration.
9. Copy the resulting file myUDP.dll to the hfss13/userlib/UserDefinedPrimi-
tives directory or the hfss13/personallib/UserDefinedPrimitives directory.
10. To view your primitives, click Draw>User Defined Primitive>Update Menu and then click
Draw>User Defined Primitive>UserLib.
Note On UNIX, you may use the same example directory structure, source, and header files to
build and compile a shared library using C++. The resulting shared library will have a
.so extension for Solaris and a .sl extension for HP-UX, and needs to be placed in the
same hfss13/userlib/UserDefinedPrimitives directory.
As with the Windows DLL, the compiled library will work only on the operating system
on which it was built.
Related Topics
Drawing a Spiral Using User Defined Primitives
Drawing a Segmented Helix with Polygon Cross-Section Using a User-Defined Primitive
Drawing a Segmented Helix with Rectangular Cross Section Using a User Defined Primitive
Modifying Objects
You can quickly modify the position, dimensions, and other characteristics of objects created in the
3D Modeler window.
What do you want to do?
• Assign color to an object.
• Assign transparency to an object.
• Assigning a Cross Section and Dimension to a Polyline
• Copy and paste objects.
• Delete objects.
• Delete Last Operation
• Cutting Objects
• Move objects.
• Rotate objects.
• Change the Orientation of an object
• Mirror objects about a plane.
• Offset an object (move every face of an object).
• Duplicate objects.
• Scale the size of objects.
• Sweep objects.
• Cover lines.
• Cover faces.
• Uncover faces.
• Detach faces.
• Detach edges.
• Create a new object by taking a cross-section of a 3D object.
• Connect objects.
• Move faces or edges.
• Unite objects.
• Subtract objects.
• Create objects from intersections.
• Create an object from a face.
• Create an object from an edge.
• Split objects.
• Separate objects.
If the Properties window not visible on the desktop, click View>Properties Window
or use Edit>Properties.
4. Select a color from the Color palette, and then click OK.
The outlines of any objects you draw after this point will be assigned the default color you
selected.
Assigning Transparency to an Object
1. Select the object to which you want to assign a transparency.
Note If the Properties window not visible on the desktop, click View>Properties Window or
use Edit>Properties.
2. Click Edit>Copy .
The objects are copied to the Clipboard, a temporary storage area. The selected items are not
deleted.
To cut an item to the clipboard and deleting the original, use the scissors icon on the toolbar.
3. Select the design into which you want to paste the objects. It can be the same design from
which you copied the items.
4. Click in the 3D Modeler window.
5. Select the working coordinate system. Objects are pasted relative to the current working coor-
dinate system.
6. Click Edit>Paste .
The objects appear in the new window.
Items on the Clipboard can be pasted repeatedly. The items currently stored on the Clipboard are
replaced by the next items that are cut or copied.
Related Topics
Duplicating Boundaries and Excitations with Geometry
Import a Model from the Clipboard
You can import a model to the Clipboard in order to use a geometry from a different design. To use
a geometry with datalink, the geometry ID must be preserved.
To import a model from the Clipboard, the model for the current design must be empty.
The geometry model is imported from the Clipboard with the ID preserved.
1. Select the objects you want to copy. For selecting all objects, you can use Edit>Select All or
Ctrl-A.
2. Click Edit>Copy .
The objects are copied to the Clipboard, a temporary storage area. The selected items are not
deleted.
3. Select the design into which you want to paste the objects. It can be the same design from
which you copied the items.
4. Click in the 3D Modeler window.
5. Select the working coordinate system. Objects are imported relative to the current working
coordinate system.
6. Click Modeler>Import From Clipboard.
The geometry model is pasted from the Clipboard with the ID preserved.
Related Topics
Setup Link Dialog
Selecting Items in the 3D Modeler Window
Copy Image
You can import images of the 3D Modeler window or of Reports into any other application. The
image has to be copied to the clipboard, so that it can be imported into the other application.
To copy an image of the 3D Modeler window and paste into another application:
1. Make the 3D Modeler window active.
This enables the Edit>Copy Image command in the menu bar.
2. Click Edit>Copy Image, or right click on the 3D Modeler window to display the shortcut
menu and select Copy Image.
Related Topics
Copy and Paste of Report and Trace Data
Copy and Paste of Report and Trace Definitions
Deleting Objects
1. Select the objects to delete.
2. Click Edit>Delete .
• Alternatively, press Delete.
The objects are deleted.
Note To maintain valid boundaries, excitations, or other parameters that were associated with
the deleted object, reassign them to other objects.
Related Topics
Deleting Polyline Segments
Deleting Start points and End points
Deleting Start Points and Endpoints
If you select a polyline in the history tree, the Delete Start Point and Delete End Point com-
mands may be enabled. These permit you to delete portions of the line.
1. In the history tree, locate the polyline that contains the segment you want to delete. Expand this
part of the history tree.
2. In the history tree, select the polyline you want to edit.
The segment is highlighted.
3. On the Edit menu or the shortcut menu, click either Delete Start Point to remove the leading
segments or Delete End Point to remove the following segments.
The designated segment is removed, and the line changes.
Cutting Objects
1. Select the objects to cut.
2. Click Edit>Cut.
The objects are copied to the Clipboard and deleted from the design.
Moving Objects
1. Select the objects to move.
2. Click Edit>Arrange>Move .
3. Select an arbitrary anchor point in one of the following ways:
• Click the point.
• Enter the point’s coordinates in the X,Y, and Z boxes.
4. Select a target point in one of the following ways:
• Click the point.
• Type the coordinates of a point relative to the anchor point in the dX, dY, and dZ boxes,
where d is the distance from the previously selected point.
All selected objects move the distance determined by the offset between the anchor point and
the target point.
Rotating Objects
Rotate objects about the x-, y-, or z-axis using the Edit>Arrange>Rotate command.
To rotate objects about an axis:
1. Select the objects to rotate.
2. Click Edit>Arrange>Rotate .
The Rotate dialog box appears.
3. Select the axis about which to rotate the objects: X, Y, or Z.
4. Type the angle to rotate the objects in the Angle box.
7-64 Drawing a Model
HFSS Online Help
A positive angle causes the object to be rotated in the counter-clockwise direction. A negative
angle causes the object to be rotated in the clockwise direction.
5. Click OK.
The selected objects are rotated about the axis.
To rotate and copy objects, use the Edit>Duplicate>Around Axis command.
Changing the Orientation of an Object
Each object has an Orientation property that specifies the coordinate system it uses is Global, or a
user defined orientation relative to the Global coordinate.
This property is useful in dealing with anisotropic materials. The properties of anisotropic materials
are specified relative to the objects orientation. Changing the orientation of an object provides a
way for objects made of the same material to be orientated differently.
To change an object’s orientation.
1. Define the coordinate systems you want to have available.
2. Open the properties window for the object.
3. Click on the Orientation property, and select from the Drop down list. If no Orientations other
than Global have been defined, none appear on the list.
4. Click OK to close the dialog and apply the changes.
Related Topics
Assigning Material Property Types
Setting Coordinate Systems
Creating a Relative Coordinate System
Mirroring Objects
Mirror an object about a plane using the Edit>Arrange>Mirror command. The plane is selected
by defining a point on the plane and a normal point. This command allows you to move an object
and change its orientation.
Note The distance between the point on the mirror plane and the point along the normal does
not matter — only the vector direction matters.
2. Click Edit>Arrange>Mirror .
3. Select a point on the plane around which you want to mirror the object.
You can do this by clicking a point, or typing coordinates in the X, Y, and Z boxes in the status
bar.
If you select a point on the object, the mirroring is relative to that point on the object. In the
following example, the first point clicked after selecting Edit>Arrange>Mirror was on the
right-rear bottom corner of the selected object. So the axis of rotation as you move the cursor is
that corner. As you move the cursor, it drags a diamond-shape on a vector extending from the
initial point. The distance along the vector does not matter. Moving the mouse rotates an out-
line of the object to new orientations. Clicking the mouse moves the object to location indi-
cated by the outline..
In this second example, the initial point is at a distance from the original object, designated by
the triad from which the handle for rotation extends to the dragging cursor.
Offsetting Objects
Move every face of a 3D object in a direction normal to its surface using the Edit>Arrange>Offset
command. The faces are moved a specified distance normal to their original planes. This command
enables you to move every face of a solid object without having to individually select and move
each face. Use the Surfaces>Move Faces>Along Normal command if you want to move just one
or more faces of an object.
To offset every face of an object:
1. Select the object you want to offset.
2. Click Edit>Arrange>Offset.
The Offset dialog box appears.
3. Type the distance you want to move the object faces from their origins, and then select a unit
from the pull-down list.
4. Click OK.
The selected object’s faces are moved the distance you specified.
Duplicating Objects
You can duplicate objects within a design using the Edit>Duplicate commands. Duplicates are
dependent upon the parameters of their parent object at the time they were created, that is, they
share the parent object’s history at the time of creation. The command hierarchy in the history tree
will show the duplication command, illustrating which commands affect all duplicates (those per-
formed before the duplication) and which commands would not affect the duplicates (those per-
formed after the duplication). For example, if you modify the radius of a parent object’s hole, the
change is applied to the holes of the object’s duplicates because they share the radius specification
history, but if you move the faces of the parent object, its duplicates are not affected because this
operation took place after the duplicates were created.
Operations performed on duplicates are independent. For example, if you duplicate a cylinder
twice, creating a row of three, and then split the second cylinder, the first and third cylinders are not
affected by the split.
When creating duplicates, the parent object is duplicated along a line or around an axis the number
of times you specify. You can also create a single duplicate that mirrors the parent object about a
plane.
Choose from the following commands:
Edit>Duplicate>Along Duplicates the parent object along a straight line. The child object
Line can be designated as attached to the parent object, but if so, no ports
or boundary conditions are duplicated.
Edit>Duplicate>Around Duplicates the parent object around an axis. The child object can be
Axis designated as attached to the parent object, but if so, no ports or
boundary conditions are duplicated.
Edit>Duplicate>Mirror Duplicates a mirror image of the parent object about a plane.
To copy objects to another design, use the Edit>Copy and Edit>Paste commands.
Note There is currently no method for dissolving the parent/duplicate relationship once a
duplicate has been created.
5. Type the total number of objects, including the original, in the Total Number box.
6. By option check the Attach to Original Object checkbox. If this is checked, no ports or
boundary conditions are duplicated for the child.
7. Click OK.
The object is duplicated around the axis at the angle you specified.
Duplicating and Mirroring Objects
To duplicate and mirror an object about a plane, use the Edit>Duplicate>Mirror command. The
plane is selected by defining a point on the plane and a normal point. This command allows you to
duplicate an object and specify the duplicate’s position.
This command is similar to Edit>Arrange>Mirror, except that this command duplicates an
object, rather than moves it.
1. Select the object you want to mirror.
Click Edit>Duplicate>Mirror .
2. Select a point on the plane on which you want to mirror the object.
A line drawn from this point to the mirror plane will be perpendicular to the plane. The dis-
tance between the point on mirror plane and point along the normal does not matter; only the
vector direction matters
3. Select a normal point on the plane in one of the following ways:
• Click the point.
• Type the coordinates of a point relative to the first point in the dX, dY, and dZ boxes,
where d is the distance from the previously selected point.
A duplicate of the object appears on the plane you specified, oriented according to the normal
point you specified.
Related Topics
Mirroring Objects
Scaling Objects
Scale an object’s dimensions in one or more directions using the Edit>Scale command.
The scale of an object is determined by the distance of each of its vertices from the origin of the
model coordinate system. When an object is scaled, the distance of each vertex from the origin is
multiplied by the scaling factor, causing the object to be resized and/or moved.
For example, if you specify a scaling factor of 2 in the X direction, each vertex in the model will be
moved so that the distance to its origin is doubled. Note that a vertex located at the origin will not
move. You can alter an object’s proportions by scaling it in one direction.
To scale an object’s dimensions in one or more directions:
1. If necessary, set a different working coordinate system to achieve the desired scaling.
2. Select the object to scale.
Click Edit>Scale. The Scale dialog box appears.
Sweeping Objects
You can sweep a 2D object around an axis, along a vector, or along a path to create a 3D solid
object. Objects that can be swept include circles, arcs, rectangles, trapezoids, polylines, or any 2D
object created in the 3D Modeler window. The 2D object need not be orthogonal to the sweep path.
You can also thicken sheets to make a 3D object.
You can also sweep open 1D objects, such as polylines. This results in open 2D sheet objects.
You can also sweep one or more faces of a 3D object to create a new object. See Sweep Faces
Along Normal.
Related Topics
Assigning a Cross Section and Dimension to a Polyline
Sweeping Around an Axis
Sweeping Along a Vector
Sweep Along a Path
Sweep Faces Along Normal
Thicken Sheet
Sweeping Around an Axis
Sweep a 1D or 2D object around the x-, y-, or z-axis using the Draw>Sweep>Around Axis com-
mand. Sweeping circles around an axis is a convenient way to create an open coil loop.
Before using this command, keep the following guidelines in mind:
• The object and the axis you are sweeping around must lie in the same plane. For example, if
you are sweeping an object around the z-axis, the object must lie in a plane that includes the z-
axis, such as xz or yz.
• The normal of the object’s plane faces must be perpendicular to the axis around which you are
sweeping.
• The object may not cross the axis around which it is being swept.
To sweep an object around an axis:
1. Select the object you want to sweep.
2. Click Draw>Sweep>Around Axis.
The Sweep Around Axis dialog box appears.
3. Select the axis you want to sweep the object around: X, Y, or Z.
4. Type the angle to sweep the object through in the Angle of sweep box.
The value must be between -360 and 360 degrees.
5. Type the draft angle.
This is the angle to which the object’s profile, or shape, is expanded or contracted as it is
swept.
6. Select one of the following draft types from the pull-down list. The draft type instructs the
modeler how to fill in gaps created by expanding or contracting a profile with a draft angle.
Extended The edges of the new profile are extended with straight tangent lines
until they intersect. The facetting of the faces will be displayed.
Round The edges of the new profile are rounded.
Natural The edges of the new profile are extended along their natural curves
until they intersect. For example, if the original object had sharp
edges, the new profile will have sharp edges.
7. Type the number of segments in the Number of segments text box.Click OK.
Note The default number of segments is zero, which creates a true path. A positive value
results in a segmented sweep, while a negative value results in an error.
If the sweep angle is 360 degrees, the number of segments is equal to the value specified.
If the sweep angle is less than 360 degrees, half segments appear at the ends.
Projects and scripts from previous software versions are treated as if the number of
segments were zero.
The object is swept around the axis. The new object has the properties of the original object.
The Properties dialog box appears, enabling you to modify the object’s properties.
8. Click OK.
Sweeping Along a Vector
Sweep a 1D or 2D object along a vector using the Draw>Sweep>Along Vector command.
1. Select the object you want to sweep.
Click Draw>Sweep>Along Vector.Draw the vector you want to sweep the object along:
a. Select the start point by clicking the point or typing its coordinates in the X, Y, and Z
boxes.
b. Select the endpoint in one of the following ways:
• Click the point.
• Type the coordinates of a point relative to the start point in the dX, dY, and dZ boxes,
where d is the distance from the previously selected point.
The Sweep Along Vector dialog box appears.
2. Type the draft angle.
Related Topics
Moving Faces Along the Normal
Thicken Sheet
To thicken one or more sheet objects to make 3D objects:
1. Select the sheet or sheets.
2. Click Modeler>Surface>Thicken Sheet.
The Thicken Sheet dialog appears.
3. Specify the thickness by typing in the field.
4. Specify the units by selecting from the drop down menu.
5. If you want to thicken both sides, use the checkbox.
6. Click OK.
The dialog closes and the sheets are changed into 3D objects of the desired thickness.
Wrap Command
You can use Modeler>Surface>Wrap command to wrap a sheet object around a suitable 3D
object (rectangular or segmented.) The sheet object must be in contact with the 3D object. It should
have smaller dimensions than the 3D object. If the sheet object does not overlap the corners of the
3D object, the wrap is straightforward, as shown in the figure. A sheet object that overlaps corners
may not wrap in straightforward fashion, depending on both the angle(s) involved, and the sheet
object. While it is possible, it is not recommended.
Note If you want the modeler to automatically cover all closed polyline objects you draw,
including circles, ellipses, rectangles, and regular polygons, select the Automatically
cover closed polylines option in the Modeler Options dialog box. A closed polyline
object can also be created by using boolean unite operations on two or more polylines.
Covering Faces
To cover object faces, the faces must be united into a 3D sheet object. To cover the face of a 2D or
3D object, use the Modeler>Surface>Cover Faces command.
Covering the face of an open 2D sheet object that had previously been uncovered results in a 3D
solid object. For example, for a box, when you select and uncover a face, the solid box becomes a
sheet with five faces. When you then select that sheet body box and use the Cover Faces com-
mand, the box becomes a solid again with six faces.
To cover the faces of objects:
1. Select the faces of the objects you want to cover.
2. Click Modeler>Surface>Cover Faces.
The object faces are now covered.
Uncovering Faces
Uncover a surface of a 3D object using the Modeler>Surface>Uncover Faces command. Uncov-
ering the surface of a 3D solid object results in an open 2D sheet object.
To uncover the face of a 3D object:
1. Switch to face selection mode: Click Edit>Select>Faces.
2. Select a face of the object you want to uncover.
Click Modeler>Surface>Uncover Faces. The selected face is uncovered, leaving an open
face on the object.
Note You can uncover one face of a 3D object at a time. If you select multiple faces, only the
first face will be uncovered.
Detaching Faces
The Modeler>Surface>Detach Faces command enables you to remove the face of a 3D object,
resulting in two separate objects.
To detach the face of an object:
1. Switch to face selection mode: Click Edit>Select>Faces.
2. Select the face of the object you want to detach. You can select multiple faces to detach.
Click Modeler>Surface>Detach Faces. The selected face is now detached, resulting in two
2D sheet objects.
Detaching Edges
The Modeler>Edge>Detach Edges command enables you to remove an edge of a wire object,
resulting in two separate wire objects.
To detach an edge of an object:
1. Switch to edge selection mode: Click Edit>Select>Edges.
2. Select the edge of the object you want to detach. You can select multiple edges to detach.
Note Only edges from wire bodies can be used in a detach edge operation.
Creating a Cross-Section
You can take a cross-section of a 3D object to create a new 2D object. This is done using the Mod-
eler>Surface>Section command.
Use this command to create cross-sections of 3D objects on the xy, yz, or xz plane. The cross-sec-
tions are created as 2D closed polyline objects.
To create a cross-section of an object:
1. Make sure the working coordinate system you want to use for the cross-sectioning plane is set.
2. Select the object from which you want to create a cross-section.
3. Click Modeler>Surface>Section. Select the section plane you will use to divide the object:
XY, YZ, or ZX.
4. Click OK.
A closed polyline object is created from the object that was sliced by the selected axis. The
original, sectioned object is unmodified.
Related Topics
Setting the Working Coordinate System
Connecting Objects
Use the Modeler>Surface>Connect command to perform the following operations:
• Connect two or more 1D polyline objects. HFSS will modify the first polyline you select to be
a 2D sheet object that connects to the second and any subsequently selected polylines. The sec-
ond and subsequent polylines selected are deleted.
• Connect two or more 2D sheet objects. HFSS will modify the first 2D object you select to be a
3D solid object that connects to the second and any subsequently selected objects. The second
and subsequent objects selected are deleted.
To connect objects:
1. Select the objects you want to connect.
2. Click Modeler>Surface>Connect.
A new object is created that connects the objects you selected. The first object you selected
was modified to create the new object and all subsequently selected objects were deleted.
Moving Faces or Edges
You can move the faces of a 3D object in a normal direction using the Modeler>Surface>Move
Faces commands. Moving object faces enables you to resize, reshape, or relocate an object.
Related Topics
Moving Faces Along the Normal
Moving Faces Along a Vector
Offsetting Objects
Moving Edges Along the Normal
Moving Faces Along the Normal
To move a 3D object’s face a specified distance in a direction normal to its original plane, use the
Modeler>Surface>Move Faces>Along Normal command. The faces that adjoin the original face
are extended or shortened along their own planes to meet the new face. Note that the adjoining
faces will not be sheared or bent.
This command is useful for extruding faces, resizing holes, and removing rounded corners, as
shown below.
To move an object face in a normal direction:
1. Click Select Faces on the shortcut menu.
1. Select the face of the object you want to move.
If you have created a suitable face list, right-click on the list and click Select Assignment from
the shortcut menu, you can operate on faces on the list.
2. Click Modeler>Surface>Move Faces>Along Normal.
The Move Faces Along Normal dialog box appears.
3. Type the distance you want to move the object face from its origin.
4. Click OK.
The face will be moved the distance you specified.
To move every face of an object normal to its surface, use the Edit>Arrange>Offset command.
Related Topics
Moving Faces Along a Vector
Offsetting Objects
Moving Edges Along the Normal
Relocating Holes
To move every face of an object normal to its surface, use the Edit>Arrange>Offset command.
Related Topics
Moving Faces Along the Normal
Offsetting Objects
Moving Edges Along the Normal
Moving Edges Along Normal
To move a 2D object’s edge a specified distance in a direction normal to its original plane, use the
Modeler>Edge>Move Edge command. The edge is extended or shortened along its own plane.
Note that the adjoining faces will not be sheared or bent. The edge can be on a rectangle, an ellipse,
a circle, a regular polygon, or an equation based surface.
This command is useful for extending or shrinking faces and resizing holes.
To move an object edge in a normal direction:
1. Click Select Edge on the shortcut menu.
2. Select the edge of the object you want to move.
3. Click Modeler>Edge>Move Edge.
The Move Faces Along Normal dialog box appears.
4. Type the distance you want to move the object face from its origin.
5. Click OK.
The edge of the object is moved based on the value you specified.
Related Topics
Select Edges.
Moving Faces Along the Normal
Moving Faces Along a Vector
Offsetting Objects
Uniting Objects
To join two or more objects into one object, use the Modeler>Boolean>Unite command. The new
object has the name, color, boundary, and material assignment of the first object selected. The
objects are united at the point of intersection.
1. Select the objects you want to join.
2. Click Modeler>Boolean>Unite. .
The objects are united.
Note By default, the objects being joined to the first object selected are not preserved for later
use. If you want to keep a copy of the objects being joined to the first object selected, do
one of the following:
• Copy the objects, and then paste them back into the design after uniting them.
• Select Clone before unite in the Modeler Options dialog box. This option instructs
the modeler to always keep a copy of the original objects being joined.
Subtracting Objects
1. Select the object from which you want to subtract other objects.
2. Hold down the Ctrl key and select the objects you want to subtract.
3. Click Modeler>Boolean>Subtract .
The Subtract dialog box appears.
Objects listed in the Tool Parts list will be subtracted from the object or objects listed in the
Blank Parts list.
4. Optionally, select an object name in either list and use the left and right arrow buttons to move
the object name to the opposite list.
• Alternatively, type the name of object you want to subtract in the empty text box below
the Tool Parts list, and then type the name of the object from which you want to subtract
it in the empty text box below the Blank Parts list.
5. Optionally, select Clone tool objects before subtract. This instructs HFSS to always keep a
copy of the original objects being subtracted.
6. Click OK.
The new object (or objects) retains the name, color, and material of the first object selected.
Note By default, the objects being subtracted from the first object selected are not preserved
for later use. If you want to keep a copy of the objects being subtracted from the first
object selected, do one of the following:
• Copy the objects, and then paste them back into the design after subtracting them.
• Select Clone before subtract in the Modeler Options dialog box. This option
instructs HFSS to always keep a copy of the original objects being subtracted.
Warning If the objects you selected do not overlap, the result is a null object and both objects
vanish.
2. Click Modeler>Boolean>Intersect .
The original objects vanish, leaving only the new object that was formed from their intersec-
tion.
Note By default, the original intersecting objects are not preserved for later use. If you want to
keep a copy of the objects that intersect the first object selected, do one of the following:
• Copy the objects, and then paste them back into the design after creating the new
object from the intersection.
• Select Clone before intersect in the Modeler Options dialog box. This option
instructs the modeler to always keep a copy of the original objects that intersect the
first object selected.
sheet object.
Hint This command is useful for assigning a boundary to the intersection of two faces. To do
this, first select the faces, and then create an object from them using the procedure
above. Next, make sure the Clone before intersect option is clear in the Modeler
Options window, and then use the Modeler>Boolean>Intersect command to modify
the object so that it includes only the intersection of the two faces. Then assign the
boundary to the new object.
Related Topics
Assigning a Cross Section and Dimension to a Polyline
Creating an Object from an Edge
Creating an Object from an Edge
The Modeler>Edge>Create Object From Edge command copies a selected edge, resulting in a
new 2D sheet object.
To create a new object from an edge:
1. Right-click in the modeler window, and select Select Edges on the shortcut menu.
2. Select the object edge you want to copy. If you select multiple edges, each becomes a new
object.
3. Click Modeler>Edge>Create Object From Edge.
The edge is copied. The resulting object appears in the history tree as a line object.
Related Topics
Assigning a Cross Section and Dimension to a Polyline
Creating an Object from a Face
Splitting Objects
To an object or objects that lie on the xy, yz, or xz plane, use the Modeler>Boolean>Split com-
mand.
1. Select the object you want to split. You can select more than one.
2. Click Modeler>Boolean>Split .
The Split dialog box appears.
3. Select XY, YZ, or XZ as the Split plane.
4. Select one of the following Keep fragments options to specify which object fragments you
want to keep (those on the positive side of the selected plane, those on the negative side of the
plane, or all pieces on both sides of the plane):
• Positive side
• Negative side
• Both
Note In previous versions of the modeler, the split operation only affected the selected
objects that crossed the selected split plane. Other objects were ignored during
the operation. In complex geometries, you may want to select everything and
perform a split. In some cases, operations are still performed on selected objects
that do not cross the split plane (i.e., both parts are retained, yielding the original
object and an invalid object). Also, depending on the options specified, some
objects not crossing the split may be deleted.
The Split objects crossing split plane option allows you to identify selected
objects that do not cross the split plane and ignore them for the operation. For a
multiple selection, only those objects that cross the split plane are split; others
are kept intact. By design, splits in existing designs from previous versions are
not changed.
6. Click OK.
The objects are divided as specified.
Separating Bodies
To separate an object with multiple lumps into individual bodies:
1. Select the object you want to separate.
2. Click Modeler>Boolean>Separate Bodies.
The object is separated.
This figure shows two separate bodies, each with one lump,
that were created from one object.
Note Converting an arc line or spline segment to a straight line segment results in two straight
line segments; one segment is created between the start point and midpoint and one
segment is created between the midpoint and endpoint.
5. By default, curved surfaces are treated as smooth (True) surfaces. If segmented surfaces are
desired, enter a number of 2 or greater in the Number of Segments parameter.
6. Click OK to dismiss the properties panel and implement the changes.
If the changes are not what was expected, undo the change using the Edit>Undo command or
press CTRL-Z.
Related Topics
Assigning a Cross Section and Dimension to a Polyline
Creating Segmented Geometry
Surface Approximation
Rounding the Edge of Objects (Fillet Command)
The fillet command rounds the object at the original edges and vertices. This means that the edges
and vertices are going to be replaced by new rounded surfaces, so that the original faces of the
object reconnect in a smooth manner. Vertices are only going to be replaced by new rounded sur-
faces if all the edges connecting to the original vertex are selected; otherwise, the vertex is pre-
served but moved (if necessary). The edges are replaced by quarter-cylindrical surfaces, of which
the radius can be customized (see the Fillet Radius property). Vertices are replaced by more com-
plicated new faces. You can control the setback distance.
The fillet command is disabled if an edge is not selected.
To switch to edge selection mode:
• Right-click the desktop, and select Select Edges from the shortcut menu.
To round the edge of an object:
1. Select the edge you want to change.
This highlights the edge and enables the Fillet command.
2. Click 3D Model>Fillet or click the fillet icon .
The Fillet Properties dialog is displayed.
3. Enter a value for the Fillet Radius in the text field and select units from the drop down menu.
The default is millimeters.
4. Enter a value for the setback distance.
The setback distance controls the shape of the vertex. It is the distance of the cross curve from
the vertex at the end of the edge. If it is less than the fillet radius it has no effect. You will get
an error if it is greater then the length of the edge.
5. Click OK to apply the change to the edge.
The dialog closes and the object is rounded by the radius value relative to the edge you
selected.
Flattening the Edge of Objects (Chamfer Command)
The chamfer command flattens the edges and vertices of the object. This means that the edges and
vertices are going to be replaced by new flat surfaces, so that the original faces of the object recon-
nect through the newly introduced flat surfaces. Vertices are only going to be replaced by new flat
surfaces if all the edges connecting to the original vertex are selected; otherwise, the vertex is pre-
served but moved (if necessary). You can control the chamfer value.
The chamfer command is disabled if an edge is not selected.
To switch to edge selection mode:
• Right-click the desktop, and select Select Edges from the shortcut menu.
To flatten an object's edge.
1. Select the edge you want to change.
The edge is highlighted, and the Chamfer command is enabled.
2. Click Modeler>Chamfer or click the Chamfer the selected edges icon on the Modeler
Blending toolbar.
The Chamfer Properties dialog box appears.
3. Type a value in the Chamfer value text box, and select the units from the pull-down list.
4. Click OK to apply the change to the edge.
The Chamfer Properties dialog box closes, and the object is flattened by the radius value relative
to the edge you selected.
Imprinting an Object
The Boolean>Imprint command lets you imprint the geometry of one object upon another. For
example, you could draw a polyhedron intersecting a cylinder, and then imprint the intersecting
lines on the cylinder.
You can select the faces of the imprinted surface separately and assign properties as needed.
3. Click OK.
This closes the dialog and performs the boolean imprinting.
After you perform the imprinting, the History tree retains the Imprint Object command and the cre-
ate command for the imprinted object
If you select the Imprint command in the History tree, you can suppress the command via the Prop-
erties window. If you select the Create <object> icon for the object, you can edit the properties of
that object. The changes applied to the object carry over to the imprinting.
Related Topics
View and Edit Commands on History Tree Objects
Imprint Projection Commands
Imprint Projection commands
The Boolean>Imprint Projection commands lets you project the form of one object to another
surface. The receiving surface can be curved or faceted.
If the surface is curved, the dimensions of the projection will be affected.You can select the faces of
the imprinted object separately, and edit properties as needed.
If projected shape extends beyond the face of the receiving object, the shape wraps.
1. Select the intersecting objects.
2. Click Modeler>Boolean>Imprint Projection>Along Normal or Modeler>Bool-
ean>Imprint Projection>Along Direction...
If you select Along Normal, the projection occurs along the normal. If you select Along Direc-
Drawing a Model 7-89
HFSS Online Help
tion, you need to specify two points that describe the direction. Once you have defined a line
by clicking two points, you see a dialog for specifying the distance for the projection.
3. Specify a distance and select units from the drop down menu and click OK.
This closes the dialog and performs the boolean imprinting.
After you perform the imprinting, the History tree shows the Imprint Object command and the cre-
ate command for the imprinted object
If you select the Imprint Projection command in the History tree, you can suppress the command
via the Properties window. If you select the Create <object> icon for the object, you can edit the
properties of that object. The changes applied to the object carry over to the imprinting.
Related Topics
View and Edit Commands on History Tree Objects
Imprinting an Object
Purge History
Each object is a sequence of modeler-based operations. The history for each object is shown under
its name in the model tree. You can use the Purge History command to remove the history of oper-
ations while not affecting the geometry itself. This is useful when you wish to perform healing
operations on the object. If there is an object for which you want to keep the history, you should
make a copy of the object for that purpose before purging.
To purge the history:
1. Select the object.
2. Select Modeler>Purge History.The history for the model is purged, and the context for the
Undo and Redo commands is updated.
Related Topics
Working with the History Tree
Generate History
Generate History to Reproduce Portions of Model
If a polyline object (line, spline, or arc), circle, or ellipse is imported or history was previously
purged, you can click on the polyline object and select Generate History to reproduce the individ-
ual line segments used to create the polyline in the model history tree.
Select Edges.
Select Vertices.
Select Multi (a mode for selecting objects, faces, edges or vertices)
Select By Area
Selecting Objects and Surfaces that Lie Inside Other Objects
Clearing a Selection
Selecting Several Objects
1. If you are selecting objects in the Modeler window make sure that the modeler is in object
selection mode by pressing the shortcut key O. You can always select objects in the History
tree.
2. Select several objects in one of the following ways:
• Hold down Ctrl, and click the objects in the view window that you want to select.
• Hold down Ctrl, and click the object names in the history tree that you want to select.
• In the History tree, select a range of objects by first clicking one object to select it, and
then Shift-click to extend the selection of visible items.
• In the History tree, under Lists, select AllObjects. This is an automatically created list that
lets you selects all object.
• Click Edit>Select All to select all objects that were drawn in the active view window,
including objects that are not currently visible.
• Press CTRL+A or click Edit>Select All Visible to select all objects that are visible in the
active view window.
Selected objects become the color that is specified for selected objects under the Display tab of
the Modeler Options dialog box. Use Tools>Options>Modeler Options to display the dialog
and set the default color. By default, the selected objects are opaque and all other objects
become relatively transparent.The settings for the relative opacity and transparency of selected
and non-selected objects appear in the 3D UI Options dialog box. Use View>Options to dis-
play the 3D UI Options dialog.
To deselect all objects, do one of the following:
• Click Edit>Deselect All.
Press Ctrl+Shift+A.
Related Topics
Selecting Objects by Name
Selecting All Faces of an Object
Creating an Object List
Selecting the Face or Object Behind
Select Edges.
Select Vertices.
trol which objects to include or exclude from area selection based on material, object names, or
object types. To do this:
1. Click Edit>Select By Area Filter to display this dialog:
2. Check Material filters to enable the Include and Exclude radio buttons. Use the text field to
specify filters by name, or use the ellipsis [...] button to display the Materials manager for
selections.
3. Check Object name filters to enable the Exclude and Include check boxes, and text fields in
which you can specify object names.
4. Check Object type filters to enable the check boxes for including Solids, Sheets, and/or lines.
5. Check Hide unfiltered objects to make unfiltered objects transparent after selection.
6. If you click Save As Default, the settings persist for the project until you change the settings
and Save as Default again.
7. Click OK to close the dialog.
Now when you left-click and drag around an area, those objects which meet the filter criteria are
highlighted in the Modeler window, and those objects are shown as selected in the History tree.
Related Topics
Selecting Items in the 3D Modeler Window
Selecting Several Objects
The object is reassigned to the selected list, replacing previous list members. The Objects
Property in for the List shows the objects contained in the list.
The object list will be treated as one volume when you are plotting and performing fields calcula-
tions. It will be listed in the Geometry window of the Fields Calculator, when you select Volume.
Related Topics
Creating an Object List
Using or Viewing List Objects
Using or Viewing List Objects
To view the objects included in an Object list:
1. In the model tree, expand the Lists tree.
2. Right-click the list you want to select, and click Select Assignment.
The objects that are included in that list are highlighted in the modeler, and the properties
appear in the desktop.
To view the properties of the object list (including a list of the objects included):
1. In the model history tree, expand the Lists tree.
2. Under Lists, right-click the list object you want to view, and click Properties.
The Properties window appears for that object list. The objects included are listed in the
Objects row.
3. Click OK or Cancel to close the Properties window.
To use an object from a list in another operation:
1. In the model tree, expand the Lists tree.
2. Right-click the list you want to select, and click Select Assignment.
The objects that are included in that list are highlighted in the modeler, and the properties
appear in the desktop.
3. Select any other objects you want to use in the operation.
4. Complete the operation.
For example, you could select an object list and another object, and then specify one of the boolean
commands (such as unite or subtract).
Selecting Faces
If the modeler is in face selection mode, click an object face in the view window to select it. To
select multiple faces, hold the CTRL key as you click the faces. You also have the option to create
face lists, which define a list of object faces, or you can make face selections from a Face ID list in
the By Face dialog.
Switch to face selection mode using one of the following methods:
• Press the shortcut key F.
• Right-click in the view window, and then click Select Faces.
• Click Edit>Select>Faces.
• Select Face from the pull-down list to the right of the select objects icon in the 3D
Modeler Selection toolbar.
You can also select faces in the Select Multi mode.
When the mouse hovers over a face in the view window, that face is highlighted, which indicates
that it will be selected when you click. Selected faces become the color specified under the Display
tab of the Modeler Options dialog box. All other objects and faces become relatively transparent.
You can also use the By Face dialog to select from a list of faces associated with an object:
1. To use the dialog, no objects should be selected to start.
2. Click Edit>Select>By Face or in the toolbar, select Face or Multi from the drop-down
menu to the right of the icon, and click the icon.
This displays the By Face dialog. This contains a list of the available objects.
3. Select an object in the Object Name list.
The Face ID list is then populated with the faces in that object.
4. Selecting a face ID from the list highlights the face in the 3D window. Use Ctrl-click to select
additional faces, or shift-click to select a range of faces.
Related Topics
Selecting All Faces of an Object
Selecting the Face or Object Behind
Selecting Faces by Name
Selecting Faces by Plane
Creating a Face List
Face Selection Toolbar Icons
Select Edges.
Select Vertices.
Select Multi (a mode for selecting objects, faces, edges or vertices)
Selecting All Faces of an Object
1. Optionally, select the object (or objects, faces, edges or vertices) with the faces you want to
select.
2. Switch to face selection mode by pressing the shortcut key F.
3. If an object is not selected, click a face on the object of interest.
4. Click Edit>Select>All Object Faces.
• Alternatively, right-click in the view window, and then click All Object Faces on the
shortcut menu.
• As another alternative, select use the face selection toolbar icons.
All the faces of the object are selected. If you selected multiple objects, all faces of those
You can also add the Mode selection menus from the Commands tab by selecting 3D Modeler
Selection from the Category list, and dragging the icons to the toolbar.
3. When Multi is selected as the mode, you can enable or disable Object, Face, Edge, or Vertex
selection by clicking the associated icon.
Related Topics
Selecting All Faces of an Object
Selecting the Face or Object Behind
Selecting Faces by Name
Selecting Faces by Plane
Creating a Face List
Select Edges
Select Vertices
Selecting the Face or Object Behind
Clearing a Selection
Measure Modes
Clearing a Selection
To clear an object, face, edge, or vertex selection, do one of the following:
• Click the view window at a point where an object does not exist.
• To clear an object selection, click a point away from the object name in the history tree.
• Click Edit>Deselect All.
• Press Shift+Ctrl+A.
The items are no longer selected.
Selecting the Face, Edge, Vertex, or Object Behind
To select the face, edge, vertex, or object behind another selected face, edge, vertex, or object, do
one of the following:
• Click Edit>Select>Next Behind.
• Right-click in the view window and click Next Behind.
When there are multiple faces behind, the one selected is relatively close to where you right-
click.
• Press the shortcut key B.
When there are multiple faces behind, the one selected relatively close to the cursor.
• Press Ctrl+B.
This option is useful when you are trying to select a face, edge, vertex, or object that is in the inte-
rior of a model, or when you do not want to change the model view to select an item.
Related Topics
Selecting Objects and Surfaces that Lie Inside Other Objects
If you execute the command again, without clearing the current selection(s), the additional
object can be highlighted. You can resize and move the dialog. When you next open it, it uses
that size and location.
Related Topics
Assigning Coordinates to New Objects
Choosing the Movement Mode
Choosing Snap Settings
Drawing Objects
ing a second point, specify its distance from the previously selected point in the x, y, and z direc-
tions in the dX, dY, and dZ text boxes, respectively.
1. Select the desired drawing command.
2. Select Cartesian from the pull-down list in the status bar.
3. Type the point’s x-, y-, and z-coordinates in the X, Y, and Z text boxes.
Hint Press Tab to move from one coordinate text box to the next. Press Ctrl+Tab to move to
the previous coordinate text box.
Hint Press Tab to move from one coordinate text box to the next. Press Ctrl+Tab to move to
the previous coordinate text box.
Note Even though you are inputting spherical coordinates, all data is internally stored in
Cartesian coordinates.
Hint Press Tab to move from one coordinate text box to the next. Press Ctrl+Tab to move to
the previous coordinate text box.
Note When drawing objects other than polylines and helices, by default, the second point you
select is relative to the first point; Relative is automatically selected in the Absolute/
Relative pull-down list in the status bar. Be sure to select Absolute from the Absolute/
Relative pull-down list in the status bar if you want the second point to be relative to the
working coordinate system.
Related Topics
Defining Relative Coordinates
Using Relative Coordinates
When entering a point’s coordinates, you can specify them in absolute or relative coordinates. Rel-
ative coordinates are relative to the reference point, or the previously selected point. Absolute coor-
dinates are relative to the working coordinate system’s origin (0, 0, 0).
To enter a point’s relative coordinates:
1. Click the desired drawing command.
2. Select Relative from the Absolute/Relative pull-down list in the status bar.
When you are in relative mode, the text boxes for a coordinate show an “d” before the coordi-
nate description, to indicate “distance from” the working reference. For example:
Related Topics
Defining Absolute Coordinates
To change the reference point, move the cursor to the desired point and press Ctrl+Click.
You can move the cursor to one of the following points:
• In the same plane as the reference point (in-plane movement mode).
• Perpendicular to the reference point (out-of-plane movement mode).
• If an object is present to snap to a point in 3D space (3D movement mode).
• Along the x-axis.
• Along the y-axis.
• Along the z-axis.
Changes you make to the movement mode persist until you change them again.
Moving the Cursor In Plane
To move the cursor to a point on the same plane as the reference point
1. Click the desired drawing command.
2. Do one of the following:
• Click 3D Model > Movement Mode>In Plane.
• Click In Plane in the movement mode pull-down list in the 3D Modeler Draw toolbar.
The next point you select will be on the same plane as the reference point.
If one of an object's snapping centers is within snapping range, the cursor will snap to the near-
est point in 3D space occupied by the object.
If an object is not within snapping range, 3D movement mode is identical to the in-plane
movement mode.
The cursor’s location, displayed by a circle that indicates it has snapped to a face center,
is (0.5, 0.5, 1.0), a point in 3D space relative to the reference point.
Moving the Cursor Along the X-Axis
To move the cursor to a point away from the reference point in the x direction:
1. Click the desired drawing command.
2. Do one of the following:
• Click Modeler>Movement Mode>Along X Axis.
• Hold the shortcut key X.
• Click Along X Axis in the movement mode pull-down list in the 3D Modeler Draw tool-
bar:
The next point you select will be on the same plane as the reference point in the positive or
negative x direction.
The next point you select will be on the same plane as the reference point in the positive or
negative y direction.
Moving the Cursor Along the Z-Axis
To move the cursor to a point away from the reference point in the z direction:
1. Click the desired drawing command.
2. Do one of the following:
• Click Modeler>Movement Mode>Along Z Axis.
• Hold the shortcut key Z.
• Click Along Z Axis in the movement mode pull-down list in the 3D Modeler Draw tool-
bar:
The next point you select will be on the same plane as the reference point in the positive or
negative z direction.
Grid
Vertex
Edge Center
Face Center
Quadrant
Arc Center
Note By default, the mouse is set to snap to the grid, a vertex, an edge center, a face center,
and the nearest quadrant. To modify the default snap settings for the active design and all
new designs, modify the selections under the Drawing tab in the Modeler Options
dialog box.
Related Topics
Snap Setting Guidelines
Note As you move the cursor, the Measure Information dialog displays the current cursor
location and measurement information from the reference. Clicking on a new vertex
updates the reference to the new location.
With Measure>Edge, Face, or Object selected, the information displayed for each selected
object is the name and:
• The area and volume of a 3D object.
• The area of a face.
• The length of a polyline (in edge selection mode, you can still see this if you select the
polyline in the History tree)
• The length of an edge
• The location of a vertex.
For more information on cursor and reference point behavior in this mode, see Measuring
Position and Distance
3. To use Measure>Edge, Face, or Object to measure the distance and angle between two
selected items:
• Select two points. Click the first and Ctrl-click to select the second.
The Measure Information dialog displays the coordinates of each point, the distance
between the points and the angle between Origin-P1, Origin-P2 line.
• Select two faces, the Measure Information dialog displays the angle/distance between
them.
• The function is similar when you select two edges and when you select an edge and a face.
• You can also measure distance between vertex/face, vertex/edge. In these cases, use the
Select Multi mode.
4. To exit the Measure mode, click Close on the Measure Information dialog.
Related Topics
Measuring Position and Distance
Setting Coordinate Systems
Modifying the Coordinate System Axes View
Choosing Snap Settings
Choosing Movement Mode (3D, in plane, X, Y, or Z)
Select Multi (a mode for selecting objects, faces, edges or vertices)
Measuring Position and Distance
To measure the distance between any cursor location relative to a designated reference point:
• Select Modeler>Measure>Position.
This enables the Measure Position mode opens the Measure Data dialog. The dialog lists the
coordinates of the current reference point (Position1)and the cursor location (Position2). If you
click, it shows the last position as a red square, and the current position as a black cursor. It
also lists the distance between those points, the X, Y, and Z distances, and the angle between
them.
The shortcut menu displays the Hints item. When Hints are on (the default), a text display in
the lower right of the 3D Modeler window, explaining how to set the reference point, and ways
to control the movement mode.
Grid point
Vertex
Edge Center
Face Center
Quadrant
Related Topics
Measure Modes for Objects
Setting Coordinate Systems
Modifying the Coordinate System Axes View
Choosing Snap Settings
Choosing Movement Mode (3D, in plane, X, Y, or Z)
Select Multi (a mode for selecting objects, faces, edges or vertices)
cally becomes the working CS; objects that you draw hereafter will be based on the coordi-
nates of this relative CS. Default planes are created on its xy, yz, and xz planes.
Related Topics
Creating a Relative Coordinate System
Creating an Offset and Rotated Relative CS
Creating a Rotated Relative CS
To create a new relative CS with its axes rotated away from another CS’s axes:
1. In the history tree, select the CS upon which you want to base the new relative CS, making it
the working CS.
2. Click Modeler>Coordinate System>Create>Relative CS>Rotated .
3. Specify the x-axis by selecting a point on the axis in one of the following ways:
• Click the point.
• At the lower right of the modeler window, use the drop down menu to select the system
for expressing coordinates (Cartesian, Cylindrical, or Spherical), select either relative or
absolute coordinates, then select the units, and type the CS origin coordinates in boxes.
To select a point that does not lie in the current plane, use the Movement Mode commands on
the shortcut menu.
4. Specify the xy plane by selecting any point on it in one of the following ways:
• Click the point.
• Type the coordinates of a point that is relative to the previously selected point in the dX,
dY, and dZ boxes, where d is the distance from the previously selected point.
You do not need to specify the z-axis. It is automatically calculated to be at a right angle to the
y-axis.
The new relative CS is created. It has the same origin as the previous working CS, but its axes
are rotated. It is listed in the history tree under Coordinate Systems. It automatically becomes
the working CS; objects that you draw hereafter will be based on the coordinates of this rela-
tive CS. Default planes are created on its xy, yz, and xz planes.
Related Topics
Creating a Relative Coordinate System
Creating an Offset and Rotated Relative CS
Creating an Offset and Rotated Relative CS
To create a new relative CS that is both offset and rotated from an existing CS:
1. In the history tree, select the CS upon which you want to base the new relative CS, making it
the working CS.
2. Point to Modeler>Coordinate System>Create>Relative CS.
3. On the Relative CS menu, click Both .
4. Select the origin in one of the following ways:
of this face CS. Default planes are created on its xy, yz, and xz planes.
Only operations listed in the history tree before the face CS’s creation will affect the face CS, and in
turn, affect objects dependent upon that face CS. A face CS, or objects created on it, is not affected
by operations that occur after it is created.
For example, suppose you create a box, then a face CS on a face of the box, and then a cylinder on
the face CS. If you then edit the box’s dimensions in the Properties dialog box, the cylinder will
move accordingly. But if you rotate the box using the Edit>Arrange>Rotate command, the box
will move, but the cylinder will not move because the operation occurs later in the history tree.
Related Topics
Automatically Creating Face Coordinate Systems
Setting the Working Coordinate System
Modifying Coordinate Systems
Setting Coordinate Systems
Automatically Creating Face Coordinate Systems
You can instruct the modeler to automatically create a new face CS every time you draw on an
object’s face.
1. Click Tools>Options>Modeler Options.
The Modeler Options dialog box appears.
2. Select Automatically switch to face coordinate system.
3. Click OK.
Now, when you select a face, and then click a drawing command, a new face CS will be created on
the face. The modeler automatically sets the new face CS as the working CS. The object you draw
is oriented according to the new face CS.
Note The modeler will not automatically create a new face CS if a face CS has already been
assigned to the selected face.
Related Topics
Creating a Face Coordinate System
Modifying Coordinate Systems
Keep in mind that when you edit a CS, the following will also be affected:
• All objects drawn on the CS.
• All CSs that were defined relative to that CS.
• All objects drawn on a CS that was defined relative to that CS.
There are two ways to modify a coordinate system: you can select the coordinate system in the his-
tory tree in the modeler window, and open its properties dialog. This approach does not also allow
you to change whether the coordinate system is Absolute or Relative, or to change how you express
the coordinates (as Cartesian, Cylindrical, or Spherical).
If you want to also modify the whether the coordinate system is Absolute or Relative, and to
change how your express the coordinate, do the following:
1. Click Modeler>Coordinate System>Edit.
The Select Working CS window appears.
2. Click the CS you want to modify.
3. Click Select.
This selects that coordinate system and enables the editable fields at the lower right of the
Modeler window. After you click the cursor in the first field, you can type in values, and tab to
the next fields.
4. You can select Absolute or Relative as the Coordinate system If you selected a relative CS, fol-
low the directions for creating a relative CS.
If you selected a face CS, follow the directions for creating a face CS.
5. You select the coordinate system from the drop down menus as Cartesian, Cylindrical, or
Spherical.
6. Select the units from the drop down menu.
The value you give here is translated to Cartesian coordinates in the Properties for the Coordi-
nate system.
Related Topics
Setting Coordinate Systems
Creating a Relative Coordinate System
Creating a Face Coordinate System
Modifying the Coordinate System Axes View
Expressing Cartesian, Cylindrical, or Spherical Coordinates
You have choices for expressing the coordinates for as Cartesian, Cylindrical, or Spherical. In each
case, you also specify whether to enter the coordinates as Absolute or Relative to the working coor-
dinate system. Click the cursor in the first text field to begin entering values or variables. Tab to the
next fields, and Enter when your are done. After you enter values or variables in the text fields, they
are evaluated as Cartesian for the Properties window for that coordinate system.
• Cartesian, that is the point’s distance from the origin in the x, y, and z directions in the X, Y,
and Z text boxes.
• Cylindrical, that is, the point’s radius, measured from the origin, in the R text box, the angle
from the x-axis in the Theta text box, and the distance from the origin in the z direction in the
Z text box.
• Spherical, that is, in the point’s radius, measured from the origin, in the Rho text box, the
angle from the x-axis in the Theta text box, and the angle from the origin in the z direction in
the Phi text box.
Related Topics
Defining Absolute Coordinates
Defining Relative Coordinates
Defining Cartesian Coordinates
Defining Cylindrical Coordinates
Defining Spherical Coordinates
2. Click Edit>Delete .
• Alternatively, press Delete.
The CS will be deleted and all objects drawn on it will be deleted. Further, any CS that was
dependent upon the deleted CS will be deleted and any objects that were drawn on the depen-
dent CS will also be deleted.
Related Topics
Setting Coordinate Systems
Creating a Relative Coordinate System
Creating a Face Coordinate System
Modifying the Coordinate System Axes View
Boundary conditions specify the field behavior at the edges of the problem region and object inter-
faces. HFSS and HFSS-IE designs have different menu options for boundaries. Click here for
HFSS-IE boundaries.
You may assign the following types of boundaries to an HFSS design:
Perfect E Represents a perfectly conducting surface.
Perfect H Represents a surface on which the tangential component of the H-field is the
same on both sides.
Impedance Represents a resistive surface.
Radiation Represents an open boundary by means of an absorbing boundary condition
(ABC) that absorbs outgoing waves.
PML Represents an open boundary condition using several layers of specialized
materials that absorb outgoing waves.
Finite Represents an imperfect conductor.
Conductivity
Symmetry Represents a perfect E or perfect H plane of symmetry.
Master Represents a surface on which the E-field at each point is matched to another
surface (the slave boundary) to within a phase difference.
Slave Represents a surface on which the E-field at each point has been forced to
match the E-field of another surface (the master boundary) to within a phase
difference.
Lumped RLC Represents any combination of lumped resistor, inductor, and/or capacitor in
parallel on a surface.
Screening Represents a boundary condition used to replace a surface a planar screen or
Impedance grid with periodic geometry.
Layered Represents a structure with multiple layers as one impedance surface.
Impedance
You may also choose to designate a perfect E, finite conductivity, or impedance boundary as an
infinite ground plane if you want the surface to represent an electrically large ground plane when
the radiated fields are calculated during post processing.
Note Hiding boundaries also turns off a check for boundary overlaps during boundary
assignment. In the case of very large models with many boundaries, hiding boundaries
can prevent delays during boundary assignment. Full model validation will subsequently
check for boundary overlaps.
For convenience, you can access the Edit Global Materials command from the Boundaries menu.
Note By default, the history tree in the 3D modeler window groups sheet objects according to
boundary assignment. To change this, select the Sheets icon and right-click to display
the Group Sheets by Assignment checkbox.
Related Topics
Technical Notes: Boundaries
Zoom to Selected Boundary
Setting Default Boundary Base Names
Designating Infinite Ground Planes
Modifying Boundaries
Deleting Boundaries
Reassigning Boundaries
Reprioritizing Boundaries
Edit Global Materials Environment
Duplicating Boundaries and Excitations with Geometry
Showing and Hiding Boundaries and Excitations
Reviewing Boundaries and Excitations in the Solver View
Setting Default Values for Boundaries and Excitations
Assigning HFSS-IE Boundaries
Zoom to Selected Boundary
To zoom to a selected boundary, right-click on a boundary name in the Project and select the Zoom
to command on the popup menu. This zooms the view in the Modeler window in or out to show the
8-2 Assigning Boundaries
HFSS Online Help
selected boundary. The current orientation does not change. This can be very useful checking the
assigned geometry.
Related Topics
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Deleting Boundaries
Setting Default Boundary/Excitation Base Names
To change the default boundary or excitation base names, so that subsequent names increment from
the base of your choosing:
1. Click Boundary>Set Default Base Name or Excitation >Set Default Base Name.
This displays the Set Default Boundary/Excitation Base dialog. This contains a list of all
boundary and excitation types, and the base names for each. The base names for each type
have editable text fields. The base names for boundaries and excitations are incremented from
the base names here.
3. Click OK to accept the changes or Cancel to close the dialog without accepting changes.
If you want to revert all or selected names to Ansoft defaults, use the Revert All or Revert
Selected buttons.
Related Topics
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Deleting Boundaries
2. For HFSS projects, you can select Infinite Ground Plane if you want the surface to represent
an electrically large ground plane when the radiated fields are calculated during post process-
ing. For PEC boundaries only, multiple infinite ground planes are supported.
Related Topics
Technical Notes: Perfect E Boundaries
Setting Default Boundary/Excitation Base Names.
Getting Started Guides: A Dielectric Resonator Antenna
Getting Started Guides: Patch Antenna
Note You can assign a variable as the resistance and reactance values. Eigenmode designs
cannot contain design parameters that depend on frequency, for example, a frequency-
dependent impedance boundary condition.
Related Topics
Zoom to Selected Boundary
Setting Default Boundary Base Names
Technical Notes: Impedance Boundaries
Assigning Boundaries 8-7
HFSS Online Help
Note Whenever additions/changes are made to radiation boundaries that affect fields, it invalidates those
solutions that can possibly have fields. Meshes are not invalidated.
2. If your project uses a field solution from another source, your "target" project must have radia-
tion boundaries with Advanced Options defined in order to specify where the fields from the
"source" project enter. See the discussion here.
3. Designate the boundary as either:
• Radiating Only - this refers to the original radiating surface properties (the default). If
you select this option, the scattered field formulation is applied. (See Technical Notes). If
you do not select this radio button the total field formulation is applied. (See Technical
Notes).
• Incident Field - the incident field source patterns are projected on these surfaces and are
8-8 Assigning Boundaries
HFSS Online Help
backed by ABC or PML. This is like a generalized space port. HFSS knows the incident
field pattern, applies it to the port and expects a reflected field pattern which radiates back.
In other words, it behaves as if you excited the project by a Norton or Thevenin generator
using an impedance which is the free space wave impedance.
• If you select Radiating Only or Incident Field, you can also specify whether the surface
is used as Reference for FSS, that is, as a Frequency Selective Surface - this surface
become the input surface for calculations of the reflection/transmission coefficients. The
other radiating surface automatically becomes output. Only one FSS can be defined in a
given model. Using the Incident Field option together with Reference for FSS is advan-
tageous for highly reflective and resonant structures. Reflection/Transmission coefficients
for FSS designs can be viewed in the solution data panel as S-parameters or you can create
an S-parameter report.
• Enforced Field - this has the H tangential component of the incident field directly applied
on these surfaces. It is an inhomogeneous Newmann BC. In other words, it behaves as if
you excited the project by an ideal current source (enforced current). If you select
Enforced Field, the Use IE Formulation option is grayed out.
• Model Exterior as HFSS-IE Domain- this uses integral equation formulation., which is
is an exact transparent condition. The IE Boundary will be most effective and efficient for
smaller radiating structures such as RFID antennas. It can be close to or on the structures,
but for performance, 0.5 wavelength is recommended. If it is on a surface, you must turn
off curvilinear elements. The IE boundary should enclose the entire structure by itself, or
with an Infinite ground plane.
• Include for nearfield/far field calculation - If you select Radiation Only, the Include in
near/far field calculation option is grayed out but checked. All Radiation Only surfaces
are included in the near/far field calculation.
When you select Incident Field or Enforced Field, you can designate that the surface is
included in near/far field calculation by checking. If you do not include any surfaces in the
near/far field calculation (whether as Radiating Only, or by checking), when you select
default radiation surfaces at the near/far field calculation setup panel an error message
states that “No radiating surface has been selected.”
Note If you select either Enforced Field or Incident Field you should run a validation check
in order to avoid an invalid setup. The setup is invalid if any of these surfaces are
internal.
If you select either Enforced Field or Incident Field in most cases, you should avoid
internal surfaces. In order to do that, internal objects with Enforced/Incident Field BC
should be substructed to become background, or PEC material should be assigned to
these objects to become "NoSolveinside".
Note Do not define a surface that cuts through an object to be a radiation boundary.
In general, do not define the interface of two internal objects to be a radiation boundary.
The only exception is when one object is a perfectly matched layer boundary (PML) and
the other is the PML base object.
Related Topics
Zoom to Selected Boundary
Setting Default Boundary Base Names
Assigning PML Boundaries
Technical Notes: Radiation Boundaries
Getting Started Guides: A Dielectric Resonator Antenna
Getting Started Guides: UHF Probe
Getting Started Guides: Patch Antenna
antenna, you may find it convenient to select the object and have a boundary applied to all
faces of the object.
You can select the faces of the PML base object to turn into PMLs. In these cases, select only
external, planar faces and exclude faces defined as symmetry boundaries.
3. Click HFSS > Boundaries>PML Setup Wizard.
The PML Setup wizard appears.
4. If you have selected a non-planar object for a PML or one that completely covers another
object, you can select Use Selected Object objectName as PML Cover. If you have selected
object faces, select Create PML Cover Objects on Selected Faces.
5. Type the thickness of each layer in the Uniform Layer Thickness text box. You can assign a
variable as the thickness value.
Note The layer thickness cannot be modified directly after PML objects have been created. If
you want to be able to modify the thickness, assign a variable as the thickness value.
If you do not assign a value, you can select Use Default Formula to have HFSS calculate a
value for you based on geometrical analysis.
6. If the selected faces are on a box object. you can see the option to select Create joining corner
and edge objects.
Edge and corner PML objects will be created to join adjacent PML surfaces together, ensuring
complete coverage.
7. Under Base Face Radiation Properties, click a radio button to specify one of the following:
• Radiating Only - the radiation surface (default).
• Incident Field - the incident field source patterns are projected on these surfaces and are
backed by ABC or PML. This is like a generalized space port. HFSS knows the incident
field pattern, applies it to the port and expects a reflected field pattern which radiates back.
In other words, it behaves as if you excited the project by a Norton or Thevenin generator
using an impedance which is the free space wave impedance.
For Radiating Only or Incident Field, you can also specify whether the surface is used as
Reference for FSS, that is, as a Frequency Selective Surface - this surface becomes the
input surface for calculations of the reflection/transmission coefficients. The other radiat-
ing surface automatically becomes output. Only one FSS can be defined in a given model.
Using the Incident Field option together with Reference for FSS is advantageous for
highly reflective and resonant structures. Reflection/Transmission coefficients for FSS
designs can be viewed in the solution data panel as S-parameters or you can create an S-
parameter report.
If you check Reference for FSS, the PML objects will stay visible.
8. Click Next.
HFSS creates PMLs from the faces you selected. Names are automatically given to the layers.
that start with PML, which is necessary for HFSS to recognize them as PMLs.
Related Topics
Creating PML Boundaries Manually
Modifying PML Boundaries
Guidelines for Assigning PML Boundaries
Technical Notes: PML Boundaries
Assigning Radiation Boundaries
Creating PML Boundaries Manually
See Guidelines for Assigning PML Boundaries.
1. Draw the PML object at the radiation surface, and then select it.
2. In the Properties window, give the object a name with the prefix PML.
Object names that start with PML are necessary for HFSS to recognize them as PMLs.
3. Click HFSS>Boundaries>PML Setup Wizard.
The PML Setup wizard appears.
4. Select Use Selected Object as PML Cover.
5. Select the Corresponding Base Object, the object touching the PML, from the pull-down list.
6. Type the thickness of each layer in the Uniform Layer Thickness text box. You can assign a
variable as the thickness value.
If you do not assign a value, you can select Use Default Formula to have HFSS calculate a
Note If objects are modified after PMLs are created, the PML materials will be invalid and
must be recalculated in the PML Setup Wizard. For example, if the material of the
PML base object is modified, the associated PML materials must be recalculated in the
PML Setup Wizard.
Related Topics
Assigning PML Boundaries
Assigning Radiation Boundaries
Zoom to Selected Boundary
Setting Default Boundary Base Names
5. To specify a layer thickness, click the checkbox to enable the Layer Thickness field, and enter
a value and select units.
Related Topics
Zoom to Selected Boundary
Setting Default Boundary Base Names
Technical Notes: Finite Conductivity Boundaries
Related Topics
Zoom to Selected Boundary
Setting Default Boundary Base Names
Technical Notes: Finite Conductivity Boundaries
Getting Started Guides: A 20 Ghz Waveguide Combiner
2. Select the type of symmetry plane the boundary represents: Perfect E or Perfect H.
3. Click Impedance Multiplier.
If the design includes a port, you must adjust the impedance multiplier or the computed imped-
ances will not be for the full structure.
The Port Impedance Multiplier dialog box appears.
4. Type a value in the Impedance Multiplier box, and then click OK.
Related Topics
Technical Notes: Symmetry Boundaries
Setting the Impedance Multiplier
Technical Notes: Impedance Multipliers
Getting Started Guides: A Dielectric Resonator Antenna
Getting Started Guides: A 20 Ghz Waveguide Combiner
2. You must specify the coordinate system in the plane on which the boundary exists. First draw
the U vector of the coordinate system. HFSS uses the U vector that you draw and the normal
vector of the boundary face to calculate the Vvector. If necessary, you can reverse the direction
of the V vector.
a. Select New Vector from the U Vector pull-down list.
The Master Boundary dialog box disappears while you draw the U vector.
b. Select the U vector’s origin, which must be on the boundary’s surface, either by:
• Clicking the point for the vector origin.
• Typing the point’s coordinates in the X, Y, and Z boxes.
c. Select a point on the u-axis to indicate the U vector direction.
The Master Boundary dialog box reappears and the model display shows the U vector
and V vector as red and blue arrows respectively.
d. If you need to reverse the direction of the V vector, select Reverse Direction.
HFSS will compute the E-field on this boundary and map it to the slave boundary using the
transformation defined by the master and slave coordinate systems.
Related Topics
Technical Notes: Master and Slave Boundaries
Assigning Slave Boundaries
Getting Started Guides: Floquet Ports
2. Select the corresponding master boundary from the Master Boundary pull-down list.
If a master boundary has not yet been defined, return to make this selection when it has been
defined.
3. You must specify the coordinate system in the plane on which the boundary exists. First draw
the U vector of the coordinate system. HFSS uses the U vector that you draw and the normal
vector of the boundary face to calculate the Vvector. If necessary, you can reverse the direction
of the V vector.
a. Select New Vector from the U Vector pull-down list.
The Slave Boundary dialog box disappears while you draw the U vector.
b. Select the U vector’s origin, which must be on the boundary’s surface, in one of the fol-
lowing ways:
• Click the point for the vector origin.
• Type the point’s coordinates in the X, Y, and Z boxes.
Note For Eigenmode problems, the Use Scan Angles to Calculate Phase Delay fields are
disabled.
• Select Field Radiation, and then enter the phase difference, or phase delay, between the
boundaries’ E-fields in the Phase Delay box. The phase delay applies only to this bound-
ary.
Note You can assign a variable as the phi, theta, or phase delay values.
HFSS will compute the E-field on the master boundary and map it to this boundary using the
transformation defined by the master and slave coordinate systems.
Related Topics
Technical Notes: Master and Slave Boundaries
Assigning Master Boundaries
Getting Started Guides: Floquet Ports
2. Select Resistance, Inductance, and Capacitance as needed and specify values and units for
each selected element. Optionally, you can assign a variable to any of these values.
3. To specify where on the surface the current and voltage will be controlled, define a Current
Flow Line. The selection field initially appears as Undefined. Select New Line to define a
vector line on the boundary surface.
Note HFSS and HFSS-IE assume the lumped RLC is assigned to a rectangular face. If you
assign a non-rectangular face, HFSS and HFSS-IE issue a warning, but proceed with the
solution. Using a non-rectangular face can result in less accurate representation of the
lumped RLC. See the technical notes on RLC boundaries for more information.
Related Topics
Technical Notes: Lumped RLC Boundaries
Setting Default Boundary/Excitation Base Names.
Vector Line
To draw a vector line:
1. Select New Line from the dialog’s pull-down list.
The dialog box disappears while you draw the vector line.
2. Select the start point in one of the following ways:
• Click the point.
• Type the point’s coordinates in the in the X, Y, and Z boxes.
3. Select the endpoint using the mouse or the keyboard.
4. Once the line has been defined, you can edit it as follows:
Select Swap End Points from the dialog pull-down list to switch the start and endpoints of the
line, reversing the line’s direction.
3. Click Next or the Screening Impedance tab, depending on the general option setting.
4. If you want to use an external design to define the screening impedance, click the Get Imped-
ance from External Design checkbox to enable the Setup Link button. If you defining an
anisotropic impedance, there will be two buttons: Setup X Direction Link and Setup Y
Direction Link.
5. If you have not selected Use External Design, the Resistance and Reactance fields are
enabled.
In these fields, you set the Resistance and Reactance. If Anisotropic Impedance is checked,
the wizard shows Resistance and Reactance fields for X Axis alignment and Y axis alignment.
Related Topics
Setting Default Boundary/Excitation Base Names.
Assigning Material Property Types
Change the Orientation of an object
Creating a Relative Coordinate System
Creating a Face Coordinate System
Setting the Working Coordinate System
Modifying the Coordinate System Axes View
Technical Notes: Screening Impedance
Get Impedance from External Design
To get impedance from an external design:
1. Click the Setup button to display the Setup Link dialog.
For anisotropic impedance cases, select Setup X Direction Link button to chose a design
which will define the impedance in the X direction. Then select Setup Y Direction Link but-
ton to chose a design which will define the impedance in the Y direction.
The Setup Link dialog has three fields under the General tab: Project File, Design, and Solu-
tion.
2. Specify the Project file for the design that is the source. A browse button [...] lets you look
through your file system. If you do not specify a project file, but select the current model, the
current Project File is automatically filled in.
3. Specify the Design for the source. If the source is in the current design, you can select this from
a drop down menu. If you select the current model, the Project File is automatically filled in.
4. Use the radio button to specify whether to save the source path relative to The project direc-
tory of the source project or This project.
5. Specify the Solution to use. A drop down list lets you select from the available solutions.
The "Default" solution is the product dependent solution of the first Setup.
That is the setup listed first in the source design's project tree (alphanumerical order). A prod-
uct specific solution of this setup becomes the default solution. In most products, it is Last-
Adaptive. In a Transient solution type, it is "Transient."
Note The solution in the source design must provide data for the target design's adaptive
frequency as well as its sweeps. That is, the adaptive frequency for the target design
must be included in the sweep in the source design.
If necessary, you can open the source design and add an appropriate frequency point to
an existing sweep.
6. Use the checkbox specify whether to Force source design to solve in the absence of linked
data in the target design.
7. Use the checkbox to specify whether to preserve the source design solution. Note that in
Extractor mode, the source project will be saved upon exit. Extractor mode means that the
software is opened during the link solely for the purpose of solving.
8. Under the Variable Mapping tab, you can set the desired variable values in the source design.
If the source and target designs contain same named variables, you can choose to Map Vari-
able By Name. In this case, same named variables are mapped automatically.
9. Click OK to close the Setup Link dialog and return to the Screening Impedance Boundary dia-
log.
Related Topics
Assigning Screening Impedance Boundaries
• By default, HFSS assumes the layered structure is external to the design; the outermost
layer of the structure is listed. Select whether this layer is an Infinite, Perfect E, or Per-
fect H layer from the Thickness/Type list.
If the layered structure is within the 3D model, do the following:
a. Select the Internal option.
b. Enter a thickness for the first layer in the Thickness/Type column. You can assign a vari-
able as this value.
6. To change the first layer’s material, click vacuum and follow the procedure for assigning a
material.
7. To add a new layer to the structure:
a. Click New Layer.
The new layer is added at the end of the list.
b. Enter a thickness for the layer in the Thickness/Type column. You can assign a variable
as this value.
c. To change the layer’s material, click vacuum and follow the procedure for assigning a
material.
8. Optionally, to reorder layers, click the first row square and drag the row to the desired position.
9. Optionally, to view the impedance values that will be calculated based on the data provided, do
the following:
a. Enter the frequency at which the solution is being solved in the Test Frequency text box.
b. Click Calculate.
The real and imaginary components of the HFSS-calculated layered impedance value
appear.
Note A warning will be posted if a fast sweep is defined in a design that contains a layered
impedance boundary, since the impedance may only be accurate for the center
frequency.
Related Topics
Technical Notes: Layered Impedance Boundaries
3. Type the boundary’s name in the Name text box or accept the default name. (To change the
default base name to one of your choosing, see Setting Default Boundary/Excitation Base
Names.)
Related Topics
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Deleting Boundaries
HFSS-IE Feature
Note A warning will be posted if a fast sweep is defined in a design that contains a layered
impedance boundary, since the impedance may only be accurate for the center
frequency.
Related Topics
Technical Notes: Layered Impedance Boundaries
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Deleting Boundaries
Assigning Materials
HFSS-IE Feature
Modifying Boundaries
To change the properties of a boundary, do one of the following:
• Double-click the boundary’s icon in the project tree.
The boundary’s dialog box appears, in which you can edit its properties.
• Right-click the boundary in the project tree, and then click Properties on the shortcut menu.
The boundary’s dialog box appears, in which you can edit its properties.
• Click HFSS>List.
The Design List dialog box appears, in which you can modify the properties of one or more
boundaries.
Related Topics
Showing and Hiding Boundaries and Excitations
Deleting Boundaries
Deleting Boundaries
To delete one boundary:
1. Select the boundary you want to delete by selecting its icon in the project tree.
2. On the Edit menu, click Delete .
You can also delete one or more boundaries in the Design List dialog box:
1. Click HFSS menu, click List.
The Design List dialog box appears.
2. Under the Boundaries tab, click the row of the boundary you want to delete.
3. Click Delete.
Related Topics
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Reassigning Boundaries
You can reassign a boundary to another surface. This is useful when you have modified objects
with assigned boundaries, invalidating the boundaries. For example, if you unite two objects with
assigned boundaries, the second object’s boundary will become invalid because united objects
maintain the characteristics of the first object selected. In this case, you would need to reassign the
boundary or delete it
1. Select the object or object face to which you want to assign an existing boundary.
2. Click HFSS>Boundaries>Reassign.
The Reassign Boundary window appears.
3. Select an existing boundary from the list, and then click OK.
The boundary is reassigned to the object or object face.
Note When reassigning a boundary that includes vectors in its definition, HFSS attempts to
preserve the vectors with the new assignment, but this is not always possible.
Alternatively, select the object or object face to which you want to assign an existing boundary.
Right-click the existing boundary in the project tree, and then click Reassign on the shortcut menu.
Related Topics
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Deleting Boundaries
Reprioritizing Boundaries
Each boundary you assign overwrites any existing boundary which it overlaps. You can change the
priority of a previously assigned boundary to be greater than a more recently assigned boundary.
The order of boundaries is important because, for any given triangle of the mesh, only one bound-
ary or excitation can be visible to the solvers. When two boundary definitions overlap, the one with
the higher priority is visible to the solvers.
1. Click HFSS>Boundaries>Reprioritize to reprioritize boundaries.
The Reprioritize Boundaries window appears. The order the boundaries and excitations
appear in the list indicates the order in which they were defined. The lowest priority assign-
ment appears at the top of the list.
Ports are automatically placed at the bottom (highest priority) of the list; you cannot move a
boundary to a higher priority than a port. Magnetic Bias Excitations (if any) have the lowest
priority. Other boundaries and excitations appear between these two extremes.
2. Drag the boundary you want to change to the desired order of priority.
Note The order of boundaries and excitations in the project tree is alphabetical. The order does
not correspond to the order of boundaries and excitations visible to the solvers.
Related Topics
Reviewing Boundaries and Excitations in the Solver View
Hint Use this option to copy and paste boundaries. For example:
1. Select the face to which you want to assign the boundary.
2. Click Modeler>Surface>Create Object From Face.
3. Assign the boundary to the new face object.
4. Copy and paste the new face object to copy and paste the boundary.
Related Topics
Copying and Pasting Objects
Note Hiding boundaries also turns off a check for boundary overlaps during boundary
assignment. In the case of very large models with many boundaries, hiding boundaries
can prevent delays during boundary assignment. Full model validation will subsequently
check for boundary overlaps.
Note Hiding boundaries also turns off a check for boundary overlaps during boundary
assignment. In the case of very large models with many boundaries, hiding boundaries
can prevent delays during boundary assignment. Full model validation will subsequently
check for boundary overlaps.
Note For PML boundaries, the defaults are set via a formula, rather than a value.
Related Topics
Showing and Hiding Boundaries and Excitations
Modifying Boundaries
Deleting Boundaries
Excitations in HFSS, HFSS Transient, and HFSS-IE are used to specify the sources of electromag-
netic fields and charges, currents, or voltages on objects or surfaces in the design. Available excita-
tion differ for each.
• HFSS Excitations
• HFSS-IE Excitations
• HFSS Transient Excitations
After assigning an excitation, you can modify it in some of the following ways, if applicable to the
excitation type:
• Change its properties.
• Delete it.
• Reassign it to another surface.
• Reprioritize it.
• Hide it from view.
• Modify the impedance multiplier.
• Deembed the port.
• For HFSS Transient solutions, render it Active or Passive.
You may assign the following types of excitations to a Driven solution-type HFSS design:
Wave Port Represents the surface through which a signal enters or exits the geometry,
effectively a semi-infinite wavegyude attached to the model.
Lumped Port Represents an internal surface through which a signal enters or exits the
geometry, effectively, a small imedance pole for exiting the structure.
Terminal... Represents a terminal. You can assign terminals manually or automatically.
Floquet Port Used exclusively with planar-periodic structures. Chief examples are planar
phased arrays and frequency selective surfaces when these may be idealized as
infinitely large.
Incident Wave Represents a propagating wave impacting the geometry.
Voltage Source Represents a constant electric field across feed points.
Current Source Represents a constant electric current across feed points.
Magnetic Bias Used to define the net internal field that biases a saturated ferrite object.
You can assign the following types of excitation in an HFSS-IE design:
Lumped Port Represents an internal surface through which a signal enters or exits the
geometry.
Terminal... Represents a terminal. You can assign terminals manually or automatically.
Plane Incident Represents a wave that propagates in one direction and is uniform in the
Wave directions perpendicular to its direction of propagation.
Far Field Wave A Far field wave is sufficiently far (that is, usually more than a wave length
distance) from an antenna to approximate as a plane wave.
Near Field Wave A Near Field wave is close enough to the antenna source for near field effects
to occur, typically within a wave length. Near field waves include evanescent
field behavior.
You can assign the following types of excitation in an HFSS Transient design. For HFSS Transient
designs, the Properties for each excitation includes a Transient tab, enabling you to designate each
excitation as Active or Passive.
Wave Port Represents the surface through which a signal enters or exits the geometry,
effectively a semi-infinite wavegyude attached to the model.
Lumped Port Represents an internal surface through which a signal enters or exits the
geometry, effectively, a small imedance pole for exiting the structure.
Terminal... Represents a terminal. You can assign terminals manually or automatically.
Plane Wave Represents a propagating wave impacting the geometry.
Voltage Source Represents a constant electric field across feed points.
Current Source Represents a constant electric current across feed points.
Related Topics
Technical Notes: Port Solution Theory
Technical Notes: Excitations
Technical Notes: Excitations in the Time Domain
Zoom to Selected Excitation
The setup of wave ports varies slightly depending on whether your solution is modal or terminal.
(Also see Selecting the Solution Type).
When you select an Assign>portType command, depending on your General Options Assignment
options selection for Use wizards, you see either the Wave Port wizard, or a multitab properties
dialog with the General tab selected.
For each port, you type the port’s name in the Name text box or accept the default name. (To
change the default base name to one of your choosing, see Setting Default Boundary/Excitation
Base Names.)
Note A wave port can be placed internal to a model as long as it is backed by a PEC object.
Related Topics
Assigning Wave Ports for Modal Solutions
Assigning Wave Ports for Terminal Solutions
Technical Notes: Wave Ports
Note For analytic port types, you can choose to Align modes analytically using coordinate
systems.
When you have defined an integration line, the table cell under the Integration line heading
changes from "None" to "Defined." Clicking on the cell now shows a drop down list of
options:
• Defined
• None
• Swap Endpoints
• Duplicate Line...
• New Line...
If you change an existing integration line, use the options for this line. If you need to define an
integration line for one or more modes, repeat the process for each. If a solution exists adding
or changing integration lines invalidates them, and issues a warning.
The Characteristic Impedance (Zo) column shows the Zpi method usually used to calculate
the characteristic impedance. However, if there are no conductors on the port and Zpi is near
zero, HFSS uses Zpv.
For definitions of how HFSS defines these values, see Calculating the PI Impedance,and Cal-
culating the PV Impedance.
4. Choose whether to use analytic modes for polarization. The modes area contains three radio
buttons:
• None means that you don’t want to align the E-field of the modes with the integration line.
• Align modes using integration lines causes polarization for non-analytic ports to align
the E-field of the modes with the integration line. There is no restriction on the port geom-
etry, materials, or integration lines.
• Align modes analytically using coordinate system requires that the port corresponds to
an analytic port type. If so, you define the U Axis Line, which must split the port symmet-
rically. The V direction is computed automatically and can be reversed using the "Reverse
V Direction" checkbox. The solver polarizes the fields by aligning them with analytic
mode patterns that are generated on the U-V coordinate system.
5. If desired, you can check the Filter Modes for Reporter checkbox.
This adds a new column to the Mode table, which lets you use a checkbox to designate a mode
For Reporter. For designs with multiple modes, this function will simplify your selections
when you create traces for reports.
6. Click Next or the Post Processing tab to display the Wave Port: Post Processing window.
Note A positive distance value will de-embed into the port. A negative distance value will de-
embed out of the port.
• Alternatively, click Get Distance Graphically to draw a line with a length representing
the de-embed distance. After you draw the line in the 3D window, the Distance field
shows the specified distance. You can subsequently edit this value.
Related Topics
Selecting the Solution Type
Defining Integration Lines
paste operations, if you have opted for boundary duplication, both ports and their associated termi-
nals will duplicate, with modified assignments to match the pasted geometries.
However, a terminal is defined on edge(s) or face(s) of object(s), which are not necessarily on the
same objects as the port face(s). If the object(s) containing the terminal assignment are also copied
and pasted along with the objects containing the port assignment, then the terminals are pasted in
with the ports. However, because the location of the pasted object(s) may coincide with that of their
source object(s), the assignment of terminals to ports is arbitrary, and likely the old ports will get
the additional terminal assignments. If you, however, move the pasted objects to non overlapping
locations, then the terminals will detach from the old port and attach instead to the new one. If you
want to see this in one step, do your copy, but move the original objects out of range before pasting.
Then you will see the proper port/terminal associations established right after the paste without
requiring any action on your part.
Related Topics
Selecting the Solution Type
Auto Assign Terminals
Manually Assigning Terminals
Manually Assigning a Wave Port
Manually Assigning a Lump Port
Set Renormalizing Impedance for Terminals
HFSS Options: General Options Tab
Technical Notes: Terminals
Active and Passive Excitation in HFSS Transient
Set Renormalizing Impedance for Terminals
The setup panel for each terminal includes its post processing renormalizing impedance. You can
set this value either for all excitations, or for a specific port. If a design includes at least one wave
port, the setup panel also includes radio buttons to either Do Not Renormalize Any Terminals, or
Renormalize All Wave Port Terminals.
To set the renormalizing impedance for all excitations:
1. Either right click on the Excitations icon in the Project tree and select Set Terminal Renor-
malizing Impedances, or click HFSS or HFSS-IE>Excitations>Set Terminal Renormaliz-
ing Impedances.
The Set Renormalizing Impedance for Terminals dialog appears.
2. In the field for Impedance, set the value, and select the units from the pull down.
This value can be a variable. This variable can be dependent on the frequency, which allows
use of a dataset for frequency dependent impedance.
3. Click the Apply button to close the dialog and apply the change.
To set the reference for all terminals on a port:
1. Right click on the Port icon in the Project tree and click Set Terminal Renormalizing Imped-
ances.
The Set Renormalizing Impedance for Terminals dialog appears. It differs from the related
command for all excitations by specifying that the Renormalizing Impedance is for terminals
on the selected port.
2. In the field for Impedance, set the value, and select the units from the pull down.
This value can be a variable. This variable can be dependent on the frequency, which allows
use of a dataset for frequency dependent impedance.
3. Click the Apply button to close the dialog and apply the change.
You can also set the Terminal Reference Impedance on a port by selecting the port and editing the
value in the Properties dialog.
In designs with at least one wave port, where you want to view un-renormalized Zo impedance in
either the Matrix data or in a report, you can select the Do Not Renormalize Any Wave Port Ter-
minals radio button..
Related Topics
Auto Assign Terminals
Manually Assigning Terminals
Manually Assigning a Wave Port for Terminal Solutions
Manually Assigning a Lump Port
Plotting in the Time Domain
Technical Notes: Terminals
Auto Assign for Terminals
The HFSS menu lists the HFSS>Excitations>Auto Assign Terminals command. This command
also appears on the shortcut menu when you right-click on Excitations, or on a single port in the
Project tree.
To auto assign terminals:
1. Once one or more ports are defined, you can use the port or Excitation level commands to
Auto Assign Terminals. (HFSS>Excitations>Auto Assign Terminals.)
For each port specified, all conductors contacting the port will be located and the Reference
Conductors for Terminals dialog will display. This resizable dialog contains a table of avail-
able geometries that are Conducting Objects. The example shown includes four conductors.
If you check the Highlight selected conductors box, selecting any conductor in the table high-
lights it in the modeler window.
2. Set the terminal naming by selecting Use conductor name or Use Port object name.
Ports are named by appending the terminal name (the default name is T) to the specified con-
ductor or port base name.
3. For each conductor, you can check the box in the Use as reference column to so designate it.
All other conductors will be considered for terminal assignment.
4. Select OK to close the Reference Conductors for Terminals dialog.
All remaining conductors on each affected port will be used. HFSS will then generate terminal
assignments, create the terminals, and associate the terminals with the correct port.
Note Multiple reference conductors touching a port must all be connected in the plane of the
port.
Existing terminals will not be affected or duplicated.
5. After you add new model objects or new port definitions, you can again Auto Assign Termi-
nals to add new terminals where appropriate.
When you execute Auto Assign Terminals, the conducting faces on a port that touch each
other are recognized as defining a single terminal, as are conducting edges that touch each
other.
Note With complicated arrangement of conductors or geometry that has slight coordinate
misalignments, auto assign may create either too few or too many terminals on a port, so
you should review the result before solving.
Related Topics
HFSS Options: General Options Tab
Manually Assigning Terminals
Manually Assigning a Wave Port for Terminal Solutions
Manually Assigning a Lump Port
Set Renormalizing Impedance for Terminals
Technical Notes: Terminals
Example Projects: Package (terminal)
Active and Passive Excitation in HFSS Transient
Manually Assigning Terminals
If you want a terminal assignment to include multiple geometry selections, you must assign it as a
Single Terminal. Terminals can be defined only after ports are defined. When defining terminals for
a particular port, the right click menu for the port in the project tree has Assign Terminal.
To define a terminal explicitly:
1. Select the face(s) and/or edge(s) that contact the port and which define the terminal. All geom-
etries to be used as the assignment for a terminal should be connected.
2. Assign as an excitation in the modeler window via right mouse click to display the shortcut
menu and select Assign Excitation>Terminal, or on the Project tree, select Excitations and
right click to display the shortcut menu and select Assign>Single Terminal, or from the menu
bar select HFSS>Excitations>Assign>Terminal or HFSS-IE>Excitations>Assign>Termi-
nal.
As a convenience, you can define multiple terminals with a single selection entity per assign-
ment (or a single terminal with just one selection entity) via Assign Excitation >Terminal or
Excitations >Assign>Terminal.
Terminals should be completely contained inside or on the perimeter of their ports. Set up ter-
minal definitions as long as they contact the port in some way. The solver uses a mesh based
test to verify that the number of terminals on a port is equal to the number of distinct conduc-
tors minus one.
3. Unless the Post Processing tab selection for the Port is set to Do Not Renormalize, you can
set a Resistance value and units for the Terminal Renormalizing Impedence. This value can
also be set at the port level, or for all excitations by using the Set Terminal Renormalizing
Impedance command.
Related Topics
Auto Assign Terminals
Manually Assigning a Wave Port for Terminal Solutions
Manually Assigning a Lump Port
Set Renormalizing Impedance for Terminals
Technical Notes: Port Solution Theory
Technical Notes: Terminals
Manually Assigning a Wave Port for Terminal Solutions
1. Select the object face to which you want to assign the port and click HFSS>Excita-
tions>Assign>Wave Port.
2. Specify the convention for terminal naming as "Use conductor Name" or "Use port object
name."
3. Specify which conductors to Use as Reference. By option you can check Highlight selected
conductors.
4. Clicking OK adds the Wave port and terminal to the Project tree.
5. Double click the wave port in the Project tree to display the Properties window for the wave
Note A positive distance value will de-embed into the port. A negative distance value will de-
embed out of the port.
• Alternatively, click Get Distance Graphically to draw a line with a length representing
the de-embed distance. After you draw the line in the 3D window, the Distance field
shows the specified distance. You can subsequently edit this value.
7. For HFSS Transient solutions, you can designate a port as Active or Passive.
Related Topics
Auto Assign Terminals
Manually Assigning Terminals
Manually Assigning a Wave Port for Terminal Solutions
Manually Assigning a Lump Port
Set Renormalizing Impedance for Terminals
Active and Passive Excitation in HFSS Transient
Technical Notes: Port Solution Theory
Technical Notes: Terminals
Technical Notes: Deembedding
A lumped port can be defined as a rectangle from the edge of the trace to the ground or as a wave
port. The default boundary is perfect H on all edges that do not come in contact with the metal or
with another boundary condition.
Their setup varies slightly depending on whether the solution is modal or terminal.
Note Use wave ports to model exterior surfaces through which a signal enters or exits the
geometry.
The lumped ports in HFSS-IE ports are different than those in HFSS. The HFSS-IE lumped ports
impress a one volt difference between the terminal and its reference while an HFSS lumped port
impresses an electric field between the terminal and its reference.
To ensure a valid port, the maximum distance from the terminal to the reference should be less than
a twentieth of a wavelength. If this condition is violated, a warning occurs.
For HFSS-IE:
• For auto assignment to work you must enable Auto-assign terminals on ports on the HFSS-
IE Options: General Options Tab.
Otherwise, for either HFSS or HFSS-IE:
• Manually assign a terminal. Select any connected edge(s) and/or face(s) of conductors that
touch the port.
• Select Excitations>Auto Assign Terminals.
This will bring up a dialog box for you to select the objects used for “reference conductors.”
Related Topics
Assigning Lumped Ports for Modal Solutions
Assigning Lumped Ports for Terminal Solutions
HFSS-IE Options: General Options Tab
Technical Notes: Lumped Ports
Technical Notes: Terminals
Technical Notes: Calculating Characteristic Impedance
Assigning Lumped Ports for Modal Solutions
1. Select a surface to which you want to assign the port and click HFSS or HFSS-IE>Excita-
tions>Assign>Lumped Port to bring up the Lumped Port dialog.
2. Define the complex Full Port Impedance in the Resistance and the Reactance text boxes.
You can assign a variable to these values. This variable can be dependent on the frequency,
which allows use of a dataset for frequency dependent impedance.
3. Click Next to display the Lumped Port: Modes window. The number of Modes is not edit-
9-18 Assigning Excitations
HFSS Online Help
able.
This example illustrates a key requirement to keep in mind when setting up the unit cell--the perim-
eter of a Floquet port must be covered by Master and Slave boundaries.
To set up a Floquet port:
1. Select the top face of the unit cell for the region above the plane, and right-button click Assign
Excitation > Floquet Port.
This displays the Floquet Port dialog with the General tab selected.
2. Specify the A and B directions for the Lattice coordinate system. These define the periodicity
of the planar lattice. The vector arrows must start and end at points on the face of the Floquet
port and must have a common initial point.
3. Click Next to display the Modes Setup window.
This window displays a field for the Number of Modes, a button for access to the Modes Cal-
culator, and a table
In general, Floquet modes are specified by two modal indices and a polarization setting. These
designations resemble the textbook notation for rectangular waveguide modes, such as
``TE10''.
The default mode table specifies a pair of Floquet modes. The default modes both have modal
indices equal to zero and are sometimes called the "specular" modes. Specular modes are
always an essential part of the Floquet mode set, but sometimes one of the two polarizations
may be omitted. For general frequency and scan conditions, other higher-order Floquet modes
will be required. A modes calculator, invoked by selecting the Modes Calculator button, is
available to set these up for the user.
The final column of the mode table is labeled "Attenuation". The numbers in the this column
are computed by the modes calculator to help you decide which modes to keep. The values
represent the modal loss in amplitude along the direction normal to the Floquet port plane in
model units of dB per model unit length.
You should keep in mind that the displayed attenuation for a mode is a function of both the fre-
quency and the scan angle set specified in the modes calculator. When the later includes more
than one scan direction, the attenuation displayed is the "worst case" in that it is the least
amount of attenuation experienced by the mode over all the specified scan directions.
Thus when the table gives a value of 0 dB, at one or more scan directions specified in the
modes calculator the particular mode propagates without attenuation. Similarly, when the table
displays, say 60 dB, a 60 dB per unit length is the least amount of attenuation at all specified
scan directions. At any given direction, only the same or larger attenuations (for example, 70
dB per length) will occur.
• Number of modes - you can trim this value later, as you learn which modes are needed
and which are not.
• Frequency - if the problem setup contains one or more frequency sweeps, you usually set
this value to the highest frequency.
• Scan Angles -enter the values and select units for Phi and Theta, including Start, Stop, and
Step size. The Mode Table Calculator calculates a set of Floquet modes on the basis of
all the angles defined.
These inputs constitute the information required to create a set of recommended modes for
the Floquet port. The inputs are used by the mode selection algorithm but do not affect the
problem setup.
2. Click OK to leave the Mode Table Calculator and to compute the recommended list of
modes.
The new modes table appears on the Modes Setup tab of the Floquet Port properties/setup
window. The attenuation associated with a listed mode represents the minimum (or worst case)
for that mode over the range of scan angles.
Related Topics
Assigning Floquet Ports
4. Select the endpoint of the vector using the mouse or the keyboard.
The endpoint defines the direction and length of the integration line.
The Wave Port or Lumped Port dialog box reappears.
Note You can select a drawing plane (for example, XY or XZ) to constrain the mouse cursor
movement when you define the end point.
Related Topics
Guidelines for Defining Integration Lines
Duplicating Integration Lines
Modifying an Integration Line
Technical Notes: Setting the Field Pattern Direction
Guidelines for Defining Integration Lines
An integration line is a vector that can represent the following:
• A calibration line that specifies the direction of the excitation field pattern at a port. If you are
analyzing more than one mode at a port, define a separate integration line for each mode; the
orientation of the electric field differs from mode to mode.
• An line along which to integrate E.dl to compute a voltage for Zpv or Zvi impedance of a port.
In this case, select two points at which the voltage differential is expected to be at a maximum.
For example, on a microstrip port, place one point in the center of the microstrip, and the other
directly underneath it on the ground plane. In a rectangular waveguide, place the two points in
the center of the longer sides.
For definitions of how HFSS defines these Zpv and Zvi values, see Calculating the PV Imped-
ance, and Calculating the VI Impedance.
Duplicating Integration Lines
After you have defined an integration line for a mode, you can duplicate it along a vector one or
more times. You can then assign the duplicates to additional modes at the port.
1. In the Wave Port dialog box, click the Modes tab.
2. Select the mode row containing the integration line you want to duplicate.
3. Select Duplicate Line from the row’s Integration Line list.
The dialog box disappears while you draw the vector along which to paste the duplicate.
4. Draw the vector along which the duplicate will be pasted:
a. Select an arbitrary anchor point on the edge of the port face in one of the following ways:
• Click the point.
• Type the point’s coordinates in the in the X, Y, and Z boxes.
b. Select a second point using the mouse or the keyboard.
This point defines the direction and distance from the anchor point to duplicate the line.
Note The value fields in the table support Ctrl/C to copy selected text from a cell, and Ctrl/V
to paste text to a selected cell.
You can freely mix differential and single-ended terminal quantities. However, single ended quan-
tities are computed as if no differential pairs existed. So, in the unlikely case of several terminals
where only a subset are combined into pairs, the results may not be as expected.
Related Topics
For plotting differential pairs, see Creating a New Report and specifically see Context Section for
Reports.
Technical Notes: Computing Differential Pairs
Note Whenever additions/changes are made to incident waves that affect fields, it invalidates those
solutions that can possibly have fields. Meshes are not invalidated.
Wave and Incident Wave / Near-Field Wave. There, the link to the "source" project can be estab-
lished.
Note The environment variable SIWAVE_INSTALL_DIR should be set before executing the
parent application like HFSS/Designer because SIwave is launched from HFSS/
Designer and not separately.
Also, in the "target" project, radiation boundaries with Advanced Options must be defined in order
to specify where the fields from the "source" project enter the "target" project.
Incident Plane Wave
An incident Plane wave is a wave that propagates in one direction and is uniform in the directions
perpendicular to its direction of propagation.
1. Select the point for the Plane wave and click HFSS or HFSS-IE>Excitations>Assign>Inci-
dent Wave>Plane Wave.
2. Select the Vector Input Format as Cartesian or Spherical coordinates.
3. Enter the X-, Y-, and Z-coordinates of the Excitation Location and/or Zero Phase Position
(the origin for the incident wave).
4. Click Next or the Cartesian or Spherical Input Vector tab.
5. If you selected Cartesian, the Incident Wave Source: Cartesian Vector Setup page appears.
Define the propagation vector, k, and the E-field polarization vector, E0:
a. Enter the X-, Y-, and Z-components for k vector in the X, Y, and Z boxes.
b. Enter the coordinates for E0 vector in the X, Y, and Z boxes.
A single incident wave will be defined. Continue with Step 8 below.
Note When entering the propagation vector, k , and E-field polarization vector, E0 , using
Cartesian coordinates, keep the following guidelines in mind:
• To define an incident wave traveling in the positive z direction, enter (0, 0, 1) as the
k vector coordinates.
• The magnitude of the E0 vector cannot be zero.
• k must be orthogonal to E0.
6. If you selected Spherical, the Incident Wave Source: Spherical Vector Setup page appears.
a. Under IWavePhi, enter Start and Stop points and the number of sweep Points.
Click View Point List to see the values of φ.
b. Under IWaveTheta, enter values for Start, Stop, and Points.
Click View Point List to see the values of θ.
c. Enter the φ and θ components of E0 in the Phi and Theta boxes.
A spherical grid is created when θ is swept through each φ point. At each grid point, an
incident wave is present traveling towards the origin of the coordinate system for the
design. The number of incident waves and grid points can be calculated by multiplying the
number of φ points by the θ points.
Note Only a single incident wave angle can be defined for periodic structures which are
defined with master and slave boundaries
7. Click Next for the Incident Wave Source: Plane Wave Options page.
8. Select the Type of Plane Wave.
a. If you select Regular/Propagating, no other fields are active.
b. If you select Evanescent, the Propagation Constant fields become active. Enter the Real
and Imaginary parts of the Propagation Constant.
c. If you select Elliptically Polarized, the Polarization Angle and Polarization Ratio
fields become active. (See Polarization of the Electric Field for a technical discussion of
polarization angles, and a definition of Polarization Ratio.)
d. To restore the default (Regular/Propagating), click the Use Defaults button.
9. Click Finish.The incident wave you defined is added to the Excitations list in the Project.
Related Topics
Active and Passive Excitation in HFSS Transient
Technical Notes: Incident Waves
Technical Notes: Evanescent Plane Wave Equations
Incident Hertzian-Dipole Wave
An incident Hertzian-Dipole wave can be specified as either an Electric dipole or a Magnetic
dipole. The Electric dipole simulates the field of an elementary short dipole antenna placed at the
origin. The Magnetic dipole is useful for EMC/EMI applications.
1. Click HFSS>Excitations>Assign>Incident Wave>Hertzian-Dipole Wave.
2. Select the Vector Input Format as Cartesian or Spherical coordinates.
3. Enter the X-, Y-, and Z-coordinates of the Excitation Location and/or Zero Phase Position
(the origin for the incident wave).
4. Click Next.
a. If you selected Cartesian, the Incident Wave Source: Cartesian Vector Setup page
appears.
b. Enter the X-, Y-, and Z-components for the vector I*Dipole Length in the X, Y, and Z
boxes. I is the current amplitude (peak value). Units are Amp-meters (A*m).
(For Magnetic Dipole, step 10 shows the vector definition.)
A single incident wave will be defined. Continue with Step 8 below.
5. If you selected Spherical, the Incident Wave Source: Spherical Vector Setup page appears.
a. Under IWavePhi, enter Start and Stop points and the number of sweep Points.:
Click View Point List to see the values of φ.
Note Only a single incident wave angle can be defined for periodic structures which are
defined with master and slave boundaries
6. Click Next. the Incident Wave Source: Hertzian-Dipole Wave Options page appears.
7. Select the Radius of Surrounding Sphere. Inside this sphere, the field magnitude will be
made equal to the field magnitude calculated on the surface of the sphere. To restore the
default (10 mm), click the Use Defaults button.
8. Specify the type of Dipole as Electric Dipole [Magnetic current loop] or Magnetic Dipole
[Electric current loop].
If you select Magnetic Dipole [Electric Current Loop], and click the back button to view the
Vector Setup, notice that the text indicates that the vector is now defined as:
Im*dl*normal(LoopSurface)
9. Click Finish.The incident wave you defined is added to the Excitations list in the Project.
Related Topics
Technical Notes: Incident Waves
Technical Notes: Spherical Wave (Electric Hertzian Dipole) Equations
Technical Notes: Spherical Wave (Magnetic Hertzian Dipole) Equations
Incident Cylindrical Wave
An incident Cylindrical wave is a wave that simulates the far field of an infinite line current placed
at the origin.
1. Click HFSS>Excitations>Assign>Incident Wave>Cylindrical Wave.
2. Select the Vector Input Format as Cartesian or Spherical coordinates.
3. Enter the X-, Y-, and Z-coordinates of the Excitation Location and/or Zero Phase Position
(the origin for the incident wave).
4. Click Next.
5. If you selected Cartesian, the Incident Wave Source: Cartesian Vector Setup page appears.
Enter the X-, Y-, and Z-components for the I Vector in the X, Y, and Z boxes. I is the current
Note Only a single incident wave angle can be defined for periodic structures which are
defined with master and slave boundaries
7. Click Next. the Incident Wave Source: Cylindrical Wave Options page appears.
8. Select the Radius of Surrounding Cylinder. Inside this cylinder, the field magnitude will be
made equal to the field magnitude calculated on the surface of the cylinder. To restore the
default (10 mm), click the Use Defaults button.
9. Click Finish.The incident wave you defined is added to the Excitations list in the Project.
Related Topics
Technical Notes: Incident Waves
Technical Notes: Cylindrical Wave Equations
Incident Gaussian Beam Wave
An incident Gaussian Beam wave propagates in one direction and is of Gaussian distribution in the
directions perpendicular to its direction of propagation.
1. Click HFSS>Excitations>Assign>Incident Wave>Gaussian Beam.
2. Select the Vector Input Format as Cartesian or Spherical coordinates.
3. Enter the X-, Y-, and Z-coordinates of the Excitation Location and/or Zero Phase Position
(the origin for the incident wave).
4. Click Next.
5. If you selected Cartesian, the Incident Wave Source: Cartesian Vector Setup page appears.
Define the propagation vector, k , and the E-field polarization vector, E0 :
a. Enter the X-, Y-, and Z-components for k vector in the X, Y, and Z boxes.
b. Enter the coordinates for E0 vector in the X, Y, and Z boxes.
Note When entering the propagation vector, k, and E-field polarization vector, E0, using
Cartesian coordinates, keep the following guidelines in mind:
• To define an incident wave traveling in the positive z direction, enter (0, 0, 1) as the
k vector coordinates.
• The magnitude of the E0 vector cannot be zero.
• k must be orthogonal to E0.
6. If you selected Spherical, the Incident Wave Source: Spherical Vector Setup page appears.
a. Under IWavePhi, enter Start and Stop points and the number of sweep Points.
Click View Point List to see the values of φ.
b. Under IWaveTheta, enter values for Start, Stop, and Points.
Click View Point List to see the values of θ.
c. Enter the φ and θ components of E0 in the Phi and Theta boxes.
A spherical grid is created when θ is swept through each φ point. At each grid point, an
incident wave is present traveling towards the origin of the coordinate system for the
design. The number of incident waves and grid points can be calculated by multiplying the
number of φ points by the θ points.
Note Only a single incident wave angle can be defined for periodic structures which are
defined with master and slave boundaries
7. Click Next. The Incident Wave Source: Gaussian Beam Options page appears.
8. Select the Beam Width at Focal Point. By definition, this refers to the radius (wo) of the
beam waist (not the diameter), where the beam waist is the minimum width. To restore the
default (10 mm), click the Use Defaults button.
9. Click Finish.The incident wave you defined is added to the Excitations list in the Project.
Related Topics
Technical Notes: Incident Waves
Technical Notes: Gaussian Beam Equations
incident wave is present traveling towards the origin of the coordinate system for the
design. The number of incident waves and grid points can be calculated by multiplying the
number of φ points by the θ points.
Note Only a single incident wave angle can be defined for periodic structures which are
defined with master and slave boundaries
7. Click Next. The Incident Wave Source: Linear Antenna Wave Options page appears.
8. Select the Length of the Antenna.
9. Select the Radius of Surrounding Cylinder. Inside this cylinder, the field magnitude will be
made equal to the field magnitude calculated on the surface of the cylinder.
10. To restore the defaults (10 mm), click the Use Defaults button.
11. Click Finish.The incident wave you defined is added to the Excitations list in the Project.
Related Topics
Technical Notes: Incident Waves
Technical Notes: Linear Antenna Equations
Far Field Wave
A Far field wave is sufficiently far (that is, usually more than a wave length distance) from an
antenna to approximate as a plane wave. Far field waves are mostly homogeneous.
1. Click HFSS>Excitations>Assign>Far Field Wave or HFSS-IE>Excitations>Assign>Far
Field Wave
2. Click Next or the Far Field Wave Options tab.
A page appears that contains a Setup Link button to browse for a Source of Field and entry
fields for specifying the linked design orientation relative to this design.
Note The solution in the source design must provide data for the target design's adaptive
frequency as well as its sweeps. That is, the adaptive frequency for the target design
must be included in the sweep in the source design.
If necessary, you can open the source design and add an appropriate frequency point to
an existing sweep.
7. Use the checkbox specify whether to Force source design to solve in the absence of linked
data in the target design.
8. Use the checkbox to specify whether to preserve the source design solution. Note that in
Extractor mode, the source project will be saved upon exit. Extractor mode means that the
software is opened during the link solely for the purpose of solving.
9. Under the Variable Mapping tab, you can set the desired variable values in the source design.
If the source and target designs contain same named variables, you can choose to Map Vari-
able By Name. In this case, same named variables are mapped automatically.
10. Click OK to close the Setup Link window and return to the Far Field Incident Wave Source
window or the Near Field Incident Wave Source window.
External Data File for Far Field Wave
You can define a Far Field Incident Wave Source as a data file. The fields can be constant or fre-
quency dependent.
If the file contains constant far fields (not depending on frequency), then the format is very simple.
No keywords are used. The first two lines contain doubles representing start, stop, and num points
for sweeps of theta and phi. Then, the subsequent lines give the complex components of electric
field in the theta and phi directions. All of these are doubles. For these lines, theta will be held con-
stant while phi is swept through all values, then theta will increment to the next value, etc. So the
lines will correspond to (th1, ph1), (th1, ph2), (th1, ph3),…,(th1,phN), (th2,ph1), (th2,ph2), etc…
Note that this format enforces a strict uniform grid of theta and phi samples.
ThetaStart ThetaStop ThetaNumPoints
PhiStart PhiStop PhiNumPoints
E_theta_real E_theta_imag E_phi_real E_phi_imag
E_theta_real E_theta_imag E_phi_real E_phi_imag
E_theta_real E_theta_imag E_phi_real E_phi_imag
Repeat for all theta and phi sweep points
If the file contains frequency-dependent far fields, the data is given in blocks. Keywords (shown
in bold below) are used to identify the frequency information. After initial data for theta and phi,
the file has a keyword and integer for the number of frequencies. Then there is a block for the far
fields at each frequency. Each block starts with a keyword and double for the frequency, followed
by the far field data, given exactly as shown for the constant case above.
Frequency FrequencyValue
E_theta_real E_theta_imag E_phi_real E_phi_imag
E_theta_real E_theta_imag E_phi_real E_phi_imag
E_theta_real E_theta_imag E_phi_real E_phi_imag
… repeat for all theta and phi sweep points
Frequency FrequencyValue
E_theta_real E_theta_imag E_phi_real E_phi_imag
E_theta_real E_theta_imag E_phi_real E_phi_imag
E_theta_real E_theta_imag E_phi_real E_phi_imag
… repeat for all theta and phi sweep points
… repeat for a total of NumFrequencies
Translation of Source Relative to Design
If the coordinate system you are using in the source design (the project/design to which you are
linking) is different from that in the target design (the design in which you are creating the
link), you must define the relationship between those coordinate systems. The relationship
between two coordinate systems can always be defined as a translation and a rotation. The
translation is the offset between the origins of the two coordinate systems, and the rotation can
be defined through the use of Euler angles.
11. Enter the X-, Y-, and Z-coordinates of the Excitation Location and/or Zero Phase Position (the
origin for the incident wave). This represents the translation of the source design’s origin with
respect to the target design’s origin. For instance, if the source design’s origin is located in the
target design at (-2, -2, 1), then the translation between the two coordinate systems is (-2, -2,
1).
12. You can define the Rotation of this Design Relative to the Source Design Euler Angles.
Similarly to the definition of translation, these angles represent the three rotations that the
source design must undergo to align with the target design’s coordinate system. Enter the Euler
angles in the respective text fields and use the pull-down menus to specify the units (degrees or
radians):
• Phi (+ or - rotation about the Z-axis).
• Theta (+ or - rotation about the X-axis).
• Psi (+ or - rotation about resultant Z-axis).
Note The Near field link uses a default mesh density on the surfaces that link to the other
design. If this default mesh density is not sufficient to obtain a desired accuracy, you can
select these surfaces and assign a surface mesh seeding.
Once the Near Field link has obtained the near fields from the other design, it continues
to work with this information regardless of later mesh changes that resulted from
adaptive passes or mesh operations. To enforce the Dynamic Link to use a newly seeded
mesh, clear the linked data by using Clear Linked Data.
Related Topics
Technical Notes: Incident Waves
Clear Linked Data
Using Field Solutions from Other Simulators
HFSS-IE Link
You can link HFSS and HFSS-IE projects. This link is controlled with a "Near Field" or "Far-Field"
Incident Wave source that is grouped with the Excitations.
• Far Field Wave
• Near Field Wave
Related Topics
HFSS-IE Feature
2. Type the value of the source, in volts or amps, in the Magnitude box. You can assign a vari-
able as this value. You can also specify the Phase.
3. Specify the direction of the electric field by drawing a vector.
When the source is selected, an arrow indicates the direction and a letter v indicates the type of
source.
Related Topics
Active and Passive Excitation in HFSS Transient
Modifying Voltage Sources
To change the name, value, or electric field direction of an assigned voltage source:
1. Double-click the source’s icon under Excitations in the project tree.
The Voltage Source dialog box appears.
2. Edit the name or value of the source.
3. To reverse the direction of the e-field:
• Select Swap Endpoints from the E-Field Direction pull-down list.
The start and endpoints of the E-field line are switched; the line’s direction is reversed.
2. Type the value of the source, in volts or amps, in the Magnitude box. You can assign a vari-
able as this value. You can also specify the Phase.
3. Specify the current flow direction by drawing a vector:
When the source is selected, an arrow indicates the direction and a letter i indicates the type of
source.
Related Topics
Active and Passive Excitation in HFSS Transient
Modifying Current Sources
To change the name, value, or current flow direction of an assigned current source:
1. Double-click the source’s icon under Excitations in the project tree.
The Current Source dialog box appears.
2. Edit the name or value of the source.
3. To reverse the direction of the current flow:
• Select Swap Endpoints from the Current Flow Direction pull-down list.
The start and endpoints of the current flow line are switched; the line’s direction is reversed.
Note The Tools>Options>HFSS Options dialog has a setting for Use wizards for data input
when creating new boundaries that controls the appearance of the Next button.
Related Topics
Reprioritizing Boundaries and Excitations.
Technical Notes: Magnetic Bias Sources
Technical Notes: Uniform Applied Bias Fields
Technical Notes: Non-uniform Applied Bias Fields
Technical Notes: Magnetic Saturation
Use the hypertext links above to see the procedure for setting the link of interest. You can link
HFSS and HFSS-IE projects. This link is controlled with a "Near Field" or "Far-Field" Incident
Wave source that is grouped with the Excitations.
Related Topics
Clear Linked Data
Export Results to Thermal Link for ANSYS Mechanical
Modifying Excitations
To change the properties of an excitation, do one of the following:
• Double-click the excitation’s icon under Excitations in the project tree.
The excitation’s properties window appears, in which you can modify its properties.
• Right-click the excitation in the project tree, and then click Properties on the shortcut menu.
The excitation’s dialog box appears, in which you can modify its properties.
• On the HFSS menu, click List.
The Design List dialog box appears. Under the Excitations tab, you can modify the properties
of one or more boundaries.
Related Topics
Active and Passive Excitation in HFSS Transient
Deleting Excitations
To delete one excitation:
1. Select the excitation you want to delete by clicking its icon in the project tree.
2. Click Edit>Delete .
The excitation is removed from the design and the project tree.
For terminal solutions, if you delete a port with terminals associated with it, deleting the port
also removes the associated terminals.
To delete all excitations:
• Click HFSS>Excitations>Delete All.
You can also delete one or more excitations in the Design List dialog box:
1. Click HFSS>List.
The Design List dialog box appears.
2. Under the Excitations tab, click the row of the excitation you want to delete.
3. Click Delete.
Reassigning Excitations
You can reassign an excitation to another surface. This is useful when you have modified objects
with assigned excitations, invalidating the excitations. For example, if you unite two objects with
assigned excitations, the second object’s excitation will become invalid because united objects
maintain the characteristics of the first object selected. In this case, you would need to reassign the
excitation or delete it.
1. Select the object or object face to which you want to assign an existing excitation.
2. Click HFSS>Excitations>Reassign.
The Reassign Excitation window appears.
3. Select an existing excitation from the list, and then click OK.
The excitation is reassigned to the object or object face.
Note When reassigning an excitation that includes vectors in its definition, HFSS attempts to
preserve the vectors with the new assignment, but this is not always possible.
Note Changing the impedance multiplier invalidates solutions in projects where lumped ports
are defined. In such projects, you need to re-solve the project after the change.
Renormalizing S-Matrices
You can renormalize an S-matrix to a specific port impedance when you set up a wave port. (It is
the final step in the Wave Port wizard.) Or you can return to the Wave Port dialog box by double-
clicking the wave port icon in the project tree, and then clicking the Post Processing tab. For
driven modal problems, you can also edit the renormalization settings and impedance value in the
wave port Properties dialog.
To renormalize an S-matrix to a specific port impedance:
1. If you have already set up the wave port on the desired object face, double-click the wave
port’s icon in the project tree.
The Wave Port dialog box appears.
2. Click the Post Processing tab.
The Port Renormalization choices include:
• Do Not Renormalize (the default)
• Renormalize All Modes. This enables the Full Port Impedance text box. The default
impedance for re-normalization of each port is 50 ohms.
For a driven modal solution, if you want to enter a complex impedance, enter it in the follow-
ing form:
<re> + <im>j
(For a driven terminal solution using a waveport, only the real part of the impedance is required.)
• If there are multiple modes, you can select Renormalize Specific Modes. This enables
the Edit Mode Impedances button. This opens a editable table with the impedances for
each mode.
3. Click OK to apply the selected values and close the dialog.
For wave ports in driven modal problems, if you choose to edit the renormalize values through the
Properties dialog:
1. Select the wave port to edit.
The docked Properties dialog shows the properties for the wave port.
2. Check the Renormalize All Modes box.
This enables the Renorm Imped field.
3. Set the Impedance value.
Note You do not need to re-run a simulation in order to renormalize a port. Post-processing
reports are automatically updated to reflect the renormalized S-matrix.
If you export matrix data to Touchstone format, you can choose to override the
renormalization impedances set here. See Exporting Matrix Data.
Related Topics
Exporting Matrix Data
De-embedding S-Matrices
To compute a de-embedded S-matrix:
1. If you have already set up the wave port on the desired object face, double-click the wave
port’s icon in the project tree.
The Wave Port dialog box appears.
2. Click the Post Processing tab.
3. Select Deembed, and then, either:
• Enter the length to be added in the Distance text box. A positive value de-embeds into the
port. A negative value de-embeds out of the port.
You can assign a variable as this value.
• Alternatively, click Get Distance Graphically to draw a line with a length representing
the de-embed distance. After you draw the line in the 3D window, the Distance field
shows the specified distance. You can edit this value.
After you enter the value, a blue arrow depicts the embedding distance in the model window
while the port is selected. After you enter the value, a blue arrow depicts the de-embedding dis-
tance in the graphics window while the port is selected.
In cases of a unit cell modelling equivalent screening impedance, the de-embedding distances
should point to the nearest surfaces of the substrate even if there is a thickness between these
surfaces. Note that a very thick substrate may lead to inaccurate results because HFSS replaces
the composite material of the substrate with a sheet.
Note Deembedding the reference plane of a port with a decaying propagation constant can
result in nonphysical values due to numerical uncertainties. When some of the S
parameters are below the noise floor of the numerical simulation, deembedding them
into the object with a long distance and/or a high decaying factor can magnify the
uncertain low values to non-physical ones.
Hint: Avoid deembedding with long distances when the real part of the propagation
constant is not small enough.
Note You do not need to re-run a simulation in order to de-embed the S-matrix. Post-
processing reports are automatically updated to reflect the de-embedded S-matrix.
Related Topics
Technical Notes: De-embedded S-Matrices
Technical Notes: Deembedding
You can add, remove, and edit materials in two main ways:
• Using the Tools>Edit Configured Libraries>Materials menu command.
• Right-clicking Materials in the project tree and selecting Edit All Libraries.
Editing definitions from the project window does not modify the configured libraries for any partic-
ular design. To consider the current design, use the Tools>Edit Configured Libraries option.
Doing so ensures that new libraries are added to the configured list for the current design. If you
edit materials from this command for the current and then export them, they will also be available
to assign to objects in other designs.
To assign a material to an object, follow this general procedure:
1. Select the object to which you want to assign a material.
2. Click Modeler>Assign Material .
The Select Definition window appears. When the Show all libraries checkbox is selected, the
window lists all of the materials in Ansoft’s global material library as well as the project’s
local material library.
You can also open the Select Definition window in one of the following ways:
• In the Properties dialog box for the object, click the material name under the Attributes
tab. A drop-down menu shows an Edit... button that opens the Select Definition window.
The menu also lists materials included in the current project. Selecting one of these mate-
rials provides another way to assign materials to an object.
• Right-click Model in the project tree, and then click Assign Material on the shortcut
menu.
• Right-click the object in the history tree, and then click Assign Material on the shortcut
menu.
Note You can search the listed materials by name or property value.
If the material you want to assign is not listed, add a new material to the global or local mate-
rial library, and then select it.
4. Click OK.
The material you chose is assigned to the object.
Note For HFSS-IE, problems with dielectrics will generally run more slowly, so HFSS-IE
issues a warning for this case. In HFSS-IE:
• Only isotropic materials are allowed
• Frequency dependent materials are allowed.
• No spatial dependent materials are allowed.
• You cannot set background material in the solver. Solver assumes vacuum as
background material.
Note In the history tree, by default, HFSS groups objects by material. To change the default,
select the object icon and right-click to display the Group Objects by Material
checkbox.
Related Topics
Solve Inside or On a Surface
Assigning DC Thickness
Searching for Materials
Adding New Materials
Assigning Material Property Types
Defining Variable Material Properties
Defining Frequency Dependent Material Properties
Defining Material Properties as Expressions
Defining Functional Material Properties
Viewing and Modifying Material Attributes
Validating Materials
Copying Materials
Removing Materials
Export Materials to a Library
Sorting Materials
Filtering Materials
Working with Materials Libraries
Setting the Temperature of Objects
Assigning DC Thickness
You can select the Assign DC Thickness option to more accurately compute DC resistance of a
thin conducting object for which Solve Inside is not selected. Skin impedance of the object will be
calculated using the defined finite thickness, which can be Automatic (the default), Manually
assigned per object, or Infinite per object. This option also exists for finite conductivity boundaries.
The Assign DC Thickness option on the HFSS>Boundaries menu is enabled if at least one object
contains a good conducting isotropic material (such as copper), and the Solve Inside property is
not selected. If the object meets these conditions, you can assign a DC thickness, either by enabling
the automatic default, or by specifying a value for a selected object.
To see the Assign DC Thickness dialog:
1. Select HFSS>Boundaries>Assign DC Thickness.
This displays the Thickness of Objects for DC Resistance dialog with the DC Thickness tab
selected. Objects to which the thickness can be applied are listed in the Object Name column.
2. Select the objects to assign a value. You can select objects either by:
• Clicking on the Object Name to highlight it.
• Use the Select By Name field to type the object name, and click the Search button.
The first object to match the name is highlighted.
Selecting an object highlights the Thickness field and the Set Thickness button.
Assigning Materials 10-5
HFSS Online Help
3. In the Use Thickness column, you can specify that the value the object uses is Automatic, Infi-
nite, or Manual.
You can disable automatic assignment on the Defaults tab of the Assign DC Thickness dia-
log. The Automatic value is calculated as Thickness ~ 2* Volume / Surface Area
It should be noted that this is a calculation for an "effective" DC thickness to be used by the
correction calculation. For a "thin" object this will work well. For example, a rectangular
microstrip trace described by a box with dimensions 100 by 10 by 1 the volume is 1000 and the
surface area is 2022 resulting in an apparent thickness of .99891, close to the geometric thick-
ness of "1". For arbitrary shapes of "thicker" objects, this calculation will not work as well. For
example, a cube with sides of 1 will have volume of 1 and surface area of 6, and a resulting
apparent thickness of .3333. Another example is the case of a cylindrical wire (e.g. bond wire).
In this case, the automatic effective DC thickness will be about Ro, which gives us the best
approximation of the DC resistance of a cylindrical wire.
The intention is that the auto-thickness will provide an accurate representation the majority of
the time and is superior to not using any DC thickness setting. When the automatic value is not
appropriate, you can override it using the manual technique.
DC thickness impedance is an approximation. It is accurate just for TE/TM waves when the
widths are infinite which clearly never occurs in a "real" design. The fact that the object is
finite causes an increase of the effective impedance due to current crowding/edge effects. Thus
entering the exact geometrical thickness would actually underestimates the impedance. By
returning a DC thickness smaller than the geometric thickness the automatic DC thickness
compensates for this underestimation resulting in a slightly higher impedance as desired.
4. To manually apply a value, enter a Thickness value, select the units and click the Set Thick-
ness button.
This applies the value to the selected object and changes the Use Thickness selection for that
object to Manual.
Note If you enter a “0” for the thickness, HFSS gives a warning that this will cause infinite
impedance that causes isolation.
5. To change the value, select the Clear Thickness button and then enter a different value. You
can also manually select or deselect the box and manually enter or delete a thickness value in
the table.
6. When you have assigned the values you need, click OK to close the dialogue.
Related Topics
Technical Notes: Calculating Finite Thickness Impedance
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
3. In the Search Parameters area, type a value for the property in the Search by Property text
box, and then click Search.
The materials are sorted according to the value you entered. The material with the property
value closest to the one you typed will be selected.
If the selected material is not the one you are searching for, do one of the following:
• Use the keyboard’s arrow keys to scroll up or down the list of materials.
• Type a new value in the Search by Property text box.
pull-down list.
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
7. If the material is linear, enter values for the following material properties in the Value boxes:
• Relative Permeability
• Relative Permittivity
• Bulk Conductivity
• Dielectric Loss Tangent,
• Magnetic Loss Tangent
If the material is a ferrite, enter a value greater than 0 in the Magnetic Saturation Value box.
You may also choose to enter values in the Lande G Factor and Delta H Value boxes. Because
Delta H values are measured at specific frequencies, you should also enter a - Measured Fre-
quency value (default 9.4 Ghz).
Note You may enter a variable name or mathematical expression in the Value box.
8. If one or more of the material properties are dependent on frequency, click Set Frequency
Dependency, and then follow the directions for defining frequency dependent materials.
9. To modify the units for a material property, double-click the Units box, and then select a new
unit system.
10. Click OK.
The new material is added to the material library.
Related Topics
Defining Variable Material Properties
Assigning Material Property Types
Defining Frequency-Dependent Material Properties
Specifying Thermal Modifiers
Assigning Material Property Types
Each material property can be assigned one of the following material property types:
Simple The material is homogeneous and linear.
Anisotropic The material’s characteristics vary with direction.
If the material property is anisotropic, its characteristics are defined by its anisotropy tensor. You
must define three diagonals for anisotropic permittivity, electric loss tangent, conductivity, permea-
bility, and magnetic loss tangent. Each diagonal represents a tensor of your model along an axis.
These tensors are relative to the coordinate system specified as the object’s Orientation property.
By specifying different orientations, several objects can share the same anisotropic material but be
oriented differently.
Related Topics
Setting Coordinate Systems
Creating a Relative Coordinate System
Change the Orientation of an object
Defining Anisotropic Relative Permeability Tensors
Defining Anisotropic Relative Permittivity Tensors
Defining Anisotropic Conductivity Tensors
Defining Anisotropic Dielectric Loss Tangent Tensors
Defining Magnetic Loss Tangent Tensors
2. Enter the conductivity along one axis of the material’s conductivity tensor in the Value box of
the T(1,1) row.
3. Enter the conductivity along the second axis in the Value box of the T(2,2) row.
4. Enter the conductivity along the third axis in the Value box of the T(3,3) row.
The values of the conductivity along the first and second axis apply to all axes that lie in the xy
cross-section being modeled. The values of the conductivity along the third axis applies to the z-
component. These values affect current flowing in dielectrics between the conductors.
These values can also be defined as variables.
Related Topics
Technical Notes: Anisotropic Conductivity Tensors
Setting Coordinate Systems
Creating a Relative Coordinate System
Change the Orientation of an object
Defining Anisotropic Relative Permeability Tensors
Defining Anisotropic Relative Permittivity Tensors
Defining Anisotropic Dielectric Loss Tangent Tensors
Defining Magnetic Loss Tangent Tensors
Defining Anisotropic Dielectric Loss Tangent Tensors
If the material property is anisotropic, its characteristics are defined by its anisotropy tensor. You
must define three diagonals for electric loss tangent. Each diagonal represents a tensor of your
model along an axis.
These tensors are relative to the coordinate system specified as the object’s Orientation property.
By specifying different orientations, several objects can share the same anisotropic material but be
oriented differently.
If electric loss tangent is anisotropic, do the following:
1. In the Dielectric Loss Tangent row in the View/Edit Material window, select Anisotropic
from the Type pull-down list.
Three rows named T(1,1), T(2,2) and T(3,3) are added below the Dielectric Loss Tangent
row.
2. Enter the ratio of the imaginary relative permittivity to the real relative permittivity in one
direction in the Value box of the T(1,1) row.
3. Enter the ratio of the imaginary relative permittivity to the real relative permittivity in the sec-
ond direction in the Value box of the T(2,2) row.
4. Enter the ratio of the imaginary relative permittivity to the real relative permittivity in the third
orthogonal direction in the Value box of the T(3,3) row.
If the electric loss tangent is the same in all directions, use the same values for each direction.
These values can also be defined as variables.
Related Topics
Technical Notes: Anisotropic Dielectric Loss Tangent Tensors
Setting Coordinate Systems
Creating a Relative Coordinate System
Change the Orientation of an object
Defining Anisotropic Relative Permeability Tensors
Defining Anisotropic Relative Permittivity Tensors
Defining Anisotropic Conductivity Tensors
Defining Magnetic Loss Tangent Tensors
Defining Magnetic Loss Tangent Tensors
If the material property is anisotropic, its characteristics are defined by its anisotropy tensor. You
must define three diagonals for anisotropic magnetic loss tangent. Each diagonal represents a tensor
of your model along an axis.
These tensors are relative to the coordinate system specified as the object’s Orientation property.
By specifying different orientations, several objects can share the same anisotropic material but be
oriented differently.
1. In the Magnetic Loss Tangent row in the View/Edit Material window, select Anisotropic
from the Type pull-down list.
Three rows named T(1,1), T(2,2) and T(3,3) are added below the Magnetic Loss Tangent
row.
2. Enter the ratio of the imaginary relative permeability to the real relative permeability in one
direction in the Value box of the T(1,1) row.
3. Enter the ratio of the imaginary relative permeability to the real relative permeability in the
second direction in the Value box of the T(2,2) row.
4. Enter the ratio of the imaginary relative permeability to the real relative permeability in the
third direction in the Value box of the T(3,3) row.
If the magnetic loss tangent is the same in all directions, use the same values for each direction.
These values can also be defined as variables.
Related Topics
Technical Notes: Anisotropic Magnetic Loss Tangent Tensors
Setting Coordinate Systems
Creating a Relative Coordinate System
Change the Orientation of an object
Defining Anisotropic Relative Permeability Tensors
Defining Anisotropic Relative Permittivity Tensors
Defining Anisotropic Conductivity Tensors
Defining Anisotropic Dielectric Loss Tangent Tensors
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
Related Topics
Working with Variables
Assigning Material Property Types
Defining Frequency-Dependent Material Properties
Specifying Thermal Modifiers
Defining Frequency-Dependent Material Properties
HFSS provides several frequency-dependent material models. The Piecewise Linear and Fre-
quency Dependent Data Points models apply to both the electric and magnetic properties of the
material. However, they do not guarantee that the material satisfies causality conditions, and so
they should only be used for frequency-domain applications.
The Debye and Djordjevic-Sarkar models apply only to the electrical properties of dielectric mate-
rials. These models satisfy the Kramers-Kronig conditions for causality, and so are preferred for
applications (such as TDR or Full-Wave Spice) where time-domain results are needed. The HFSS
Design Settings also include an automatic Djordjevic-Sarkar model to ensure ensure causal solu-
tions when solving frequency sweeps for simple constant material properties.
In HFSS, you can assign conductivity either directly as bulk conductivity, or as a loss tangent. This
provides flexibility, but you should only provide the loss once. The solver uses the loss values just
as they are entered.
1. With respect to a material selected in the Select Definition window, in the View/Edit Mate-
2. In the Frequency Dependent Material Setup Option window, do one of the following:
• Select Piecewise Linear Input. This defines the material property values as a restricted
form of piecewise linear model with exactly 3 segments (flat, linear, flat). You will spec-
ify the property's values at an upper and lower corner frequency. Between these corner fre-
quencies, HFSS linearly interpolates the material properties; above and below the corner
frequencies, HFSS extrapolates the property values as constants. This dataset can be mod-
ified with additional points if desired.
• Select Debye Model Input. This is a single-pole model for the frequency response of a
lossy dielectric material. In some materials, up to about a 10-GHz limit, ion and dipole
polarization dominate and a single pole Debye model is adequate. HFSS allows you to
specify an upper and lower measurement frequency, and the loss tangent and relative per-
mittivity values at these frequencies. You may optionally enter the permittivity at optical
frequency, the DC conductivity, and a constant relative permeability.
• Select Multipole Debye Model Input. This lets you provide the data of relative permittiv-
ity and loss tangent versus frequency. Based on this data the software dynamically gener-
ates frequency dependent expressions for relative permittivity and loss tangent through the
Multipole Debye Model. The input dialog plots these expressions together with your input
data through the linear interpolations.
• The generated expressions provide the new value for the material properties of rela-
tive permittivity and loss tangent.
• Both the expressions and data triples can be saved and reloaded.
• Select Djordjevic-Sarkar Model Input. This model was developed for low-loss dielec-
Assigning Materials 10-15
HFSS Online Help
tric materials (particularly FR-4) commonly used in printed circuit boards and packages.
In effect, it uses an infinite distribution of poles to model the frequency response, and in
particular the nearly constant loss tangent, of these materials. HFSS allows you to enter
the relative permittivity and loss tangent at a single measurement frequency. You may
optionally enter the relative permittivity and conductivity at DC.
If you try to enter invalid values for the Djordjevic-Sarkar model, you receive error mes-
sages.
• Select Enter Frequency Dependent Data Points. This allows you to enter, import or edit
frequency dependent data sets for each material property. Any number of data points may
be entered. This is an arbitrary piecewise linear model.
3. Click OK.
A dialog appears, based on your selection.
Piecewise Linear Input
Debye Model Input
Multipole Debye Model Input
Djordjevic-Sarkar
Enter Frequency Dependent Data Points
After you have entered the data for your selection, you return to the View/Edit Material win-
dow. New default function names appear in the material property text boxes. HFSS automati-
cally created a dataset for each material property. Based on a varying property’s dataset, HFSS
can interpolate the property’s values at the desired frequencies during solution generation.
To modify the dataset with additional points, see Modifying Datasets.
Note Neither the piecewise or the loss models ask for frequency dependent conductivity
because there the constant sigma represents the DC loss and the frequency dependent
loss tangent represents the polarization losses.
Related Topics
Piecewise Linear Input
Debye Model Input
Multipole Debye Model Input
Djordjevic-Sarkar
Enter Frequency Dependent Data Points
Technical Notes: Frequency-Dependent Material Properties
Modifying Datasets
HFSS assumes that the material’s property values remain constant between these frequencies.
2. Enter the Upper and Lower Relative Permittivity of the material.
If the permittivity of the material does not vary with frequency, enter the same value you
entered for the permittivity’s lower frequency.
3. Follow the same procedure for entering values for permeability, dielectric loss tangent, and
magnetic loss tangent.
After you have entered the data for your selection, you return to the View/Edit Material win-
dow. New default function names appear in the material property text boxes. HFSS automati-
cally created a dataset for each material property. Based on a varying property’s dataset, HFSS
can interpolate the property’s values at the desired frequencies during solution generation.
To modify the dataset with additional points, see Modifying Datasets.
Note Neither the piecewise or the loss models ask for frequency dependent conductivity
because there the constant sigma represents the DC loss and the frequency dependent
loss tangent represents the polarization losses.
Related Topics
Piecewise Linear Input
Debye Model Input
Multipole Debye Model Input
Djordjevic-Sarkar
Assigning Materials 10-17
HFSS Online Help
HFSS assumes that the material’s property values remain constant between these frequencies.
2. Enter the Upper and Lower Relative Permittivity of the material.
If the permittivity of the material does not vary with frequency, enter the same value you
entered for the permittivity’s lower frequency
3. If you need to specify a value for a High/Optical Frequency, check the box to enable the value
field.
4. For Conductivity or Dielectric Loss Tangent, select the radio button for either At DC or for
After you have entered the data for your selection, you return to the View/Edit Material win-
dow. New default function names appear in the material property text boxes. HFSS automati-
cally created a dataset for each material property. Based on a varying property’s dataset, HFSS
can interpolate the property’s values at the desired frequencies during solution generation.
To modify the dataset with additional points, see Modifying Datasets.
Note Neither the piecewise or the loss models ask for frequency dependent conductivity
because there the constant sigma represents the DC loss and the frequency dependent
loss tangent represents the polarization losses.
Related Topics
Piecewise Linear Input
Multipole Debye Model Input
Djordjevic-Sarkar
Enter Frequency Dependent Data Points
Technical Notes: Frequency-Dependent Material Properties
Modifying Datasets
the good results, you should provide more than 5 frequency points.,
You can also import the data from a tab format text file.
The import data will be shown in the data table, and then can be modified. You can export cur-
rent input data to a file. The file is a tab file with extension .tab (same as dataset import/export
file). Below is an example of the file format. Each row provides Frequency (GHz), Permittiv-
ity, and Loss Tangent.
0.00001 3.8136 0.00128
0.00010 3.7914 0.00520
0.00100 3.7500 0.00700
0.01000 3.7119 0.00700
0.10000 3.6742 0.00700
1.00000 3.6354 0.00700
2.15444 3.6346 0.00702
3.17000 3.6325 0.01073
4.64160 3.6186 0.01500
10.0000 3.5777 0.01750
21.5444 3.5458 0.01750
2. Based on this data the software dynamically generates frequency dependent expressions for
relative permittivity and loss tangent through the Multipole Debye Model. The input dialog
plots these expressions together with your input data through the linear interpolations.
• The generated expressions provide the new value for the material properties of relative
permittivity and loss tangent.
• Both the expressions and data triples can be exported and re-imported.
After you have entered the data for your selection, you return to the View/Edit Material win-
Assigning Materials 10-21
HFSS Online Help
dow. New default function names appear in the material property text boxes. HFSS automati-
cally created a dataset for each material property. Based on a varying property’s dataset, HFSS
can interpolate the property’s values at the desired frequencies during solution generation.
Piecewise Linear Input
Debye Model Input
Djordjevic-Sarkar
Technical Notes: Frequency-Dependent Material Properties
Assigning Frequency Dependent Material: Djordjevic-Sarkar Model Input
Having selected Djordjevic-Sarkar as the model for the frequency dependent material property, you
enter the required values in the dialog displayed.
1. Enter the values for Properties at Frequency:
2. Enter the Properties at DC. This includes Conductivity and can include relative permittivity.
After you have entered the data for your selection, you return to the View/Edit Material win-
dow. New default function names appear in the material property text boxes. HFSS automati-
cally created a dataset for each material property. Based on a varying property’s dataset, HFSS
can interpolate the property’s values at the desired frequencies during solution generation. .
Related Topics
Piecewise Linear Input
Debye Model Input
of existing datasets and the Add/Import dataset...to add or import new dataset.
• Freq As: after a dataset is successfully imported or added, there are two choices available:
"X datapoint" or "Y datapoint".
2. If you select Add/Import dataset, the Add Dataset dialog appears.
This contains the following fields:
• The name field for the current dataset. The default is ds1.
• The Import from File button. This opens a file browser for you to select an existing data-
set.
• The Coordinates table. This contains X and Y text fields in which you can enter data
points. The values you add are interactively displayed on the graph to the right of the
table. You can also Add rows above or below a selected row, Delete rows, or Append a
specified number rows.
3. After you have specified or imported the data points, and OK the dialog, the Enter Frequency
Data Points dialog shows the Dataset Name and the Freq As value.
4. After you OK the Enter Frequency Dependent Data Points dialog shows the new values.
After you have entered the data for your selection, you return to the View/Edit Material win-
dow. New default function names appear in the material property text boxes. HFSS automati-
cally created a dataset for each material property. Based on a varying property’s dataset, HFSS
can interpolate the property’s values at the desired frequencies during solution generation.
To modify the dataset with additional points, see Modifying Datasets.
Note Neither the piecewise or the loss models ask for frequency dependent conductivity
because there the constant sigma represents the DC loss and the frequency dependent
loss tangent represents the polarization losses.
Related Topics
Piecewise Linear Input
Debye Model Input
Multipole Debye Model Input
Djordjevic-Sarkar
Technical Notes: Frequency-Dependent Material Properties
Modifying Datasets
Specifying Thermal Modifiers
To specify Thermal modifiers for a material:
1. In the View/ Edit materials dialog you must enable the View/ Edit Modifier checkbox for Ther-
mal Modifier.
This causes the Properties of the Material table to expand to include a Thermal Modifier col-
umn. By default, the Thermal Modifier property is set to None.
2. Selecting Edit... from the drop down menu, rather than None causes the Edit Thermal Modi-
fier dialog to appear.
3. Select Expression radio button to display the Parameters Modifier text field or the Qua-
dratic radio button to display the tabs for Basic Coefficient Set and Advanced Coefficient
Set.
• With Expression selected, you can write an equation for a thermal modifier in the Parameters
Modifier text field.
Checking Use temperature dependent data set disables the Modifier text field. You can then
use the drop down menu to select Add/Import Dataset. This lets you define the thermal modi-
fier as a data set.
• With the Quadratic radio button selected, in the Basic Coefficient tab, you can edit fields for
the TempRef and units, and fields for C1 and C2 for the following equation:
P(Temp) = Pref[1+ C1(Temp - TempRef) + C2(Temp - TempRef)^2]
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
Related Topics
Defining Variable Material Properties
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
Related Topics
Defining Mathematical Functions
Defining Variable Material Properties
Related Topics
Assigning Materials
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
Warning If you modify a material that is assigned in the active project after generating a
solution, the solution will be invalid.
Related Topics
Validating Materials
Defining Variable Material Properties
Copying Materials
Removing Materials
Export Materials to a Library
Sorting Materials
Filtering Materials
Working with Materials Libraries
Validating Materials
HFSS can validate a material’s property parameters for an Ansoft software product. For example,
it will check if the range of values specified for each material property is reasonable.
If a material’s property parameters are invalid, an error message will appear in the lower-right cor-
ner of the View/Edit Material window. If the parameters are valid, a green check mark will appear
there.
To validate the material attributes listed in the View/Edit Material window:
• Select a product from the Select Ansoft Product area, and then click Validate Now.
Related Topics
Copying Materials
Removing Materials
Export Materials to a Library
Sorting Materials
Filtering Materials
Working with Materials Libraries
Copying Materials
1. In the Select Definition window, select the material you want to copy, and then click Clone
Material.
2. To modify the material’s attributes, follow the directions for modifying materials.
3. Click OK to save the copy in the active project’s material library.
Related Topics
Validating Materials
Copying Materials
Removing Materials
Export Materials to a Library
Sorting Materials
Filtering Materials
Working with Materials Libraries
Removing Materials
1. In the Select Definition window, select a material you want to remove from the active proj-
ect’s material library.
2. Click Remove Material.
The material is deleted from the project material library.
In a project library, you may want to use the Project>Remove Unused Definitions command
to remove selected materials definitions that your project does not require.
Related Topics
Validating Materials
Copying Materials
Export Materials to a Library
Sorting Materials
Filtering Materials
Working with Materials Libraries
Sorting Materials
You can change the order of the materials listed in the Select Definition window. You can sort the
list of materials by name, library location, or material property value.
To change the order of the listed materials:
• Click the column heading by which you want to order the materials.
If the arrow in the column heading points up, the material data will be listed in ascending order
(1 to 9, A to Z) based on the values in the column you chose. If you want the material data to
be listed in descending order (9 to 1, Z to A), click the column heading again. The arrow will
point down.
Note By default, not all of the available properties are displayed in the materials table. Only
the properties commonly used by the product are displayed. To view the complete table
of properties, see Filtering Materials.
Related Topics
Validating Materials
Copying Materials
Removing Materials
Export Materials to a Library
Filtering Materials
Working with Materials Libraries
Filtering Materials
If you want to remove certain materials or material properties from the list in the Select Definition
window, use the filter options under the Material Filters tab. You can filter out materials based on
the product or library with which they are associated. You can also filter out material properties and
types of material properties. And you can remove the filtering in order to see all available material
properties.
To filter materials or material properties listed in the Select Definition window, using the choices
in the Materials tab:
1. The text field under Libraries lists the libraries for the project. Selecting the listed library high-
lights it and cause the table to display the materials in that library.
2. Above the Libraries area, you can check or uncheck boxes to show or hide Project Definitions
and All Libraries.
• With both unchecked, nothing appears in the materials table. With both checked, the table
shows all materials and highlights those used in the project.
• With only Project Definitions checked, the materials table shows only the materials used
in the project.
• With All Libraries checked, the table displays all materials, but may not show all available
properties.
To filter out or show additional material properties in the Materials tab:
1. Click the Material Filters tab.
2. Under Filter Materials and Properties for, select one of the radio buttons:
• Click Select All to select all of the products listed. Click Clear to clear all product selec-
tions.
• Active Design to display properties used in the active design.
• This Product to display properties commonly used by this product.
• All Products to display all properties available. Selecting this enlarges the table of proper-
ties shown under the Materials tab to show all properties possible. You can use the scroll
bars or size the dialog to see all properties.
3. Click the Materials tab to save your selections.
Click Cancel to revert back to the last saved selections.
Related Topics
Validating Materials
Copying Materials
Removing Materials
Export Materials to a Library
Sorting Materials
Working with Materials Libraries
You can modify the view of contents in the 3D Modeler window without changing their actual
dimensions or positions.
What do you want to do?
• Set the View Options
• Rotate the view.
• Pan the view.
• Zoom in or out.
• Fit contents in the view window.
• Show or hide objects.
• Show or hide boundaries or excitations.
• Render objects as wireframes, flat-shaded, or smooth-shaded solids.
• Set the Surface Visualization
• Modify the view orientation.
• Modify the lighting.
• Set the projection view.
• Set the background color.
• Modify the appearance of the coordinate system axes.
• Modify the appearance of the grid.
• Use Clip Planes
Related Topics
Assigning Color to an Object
Hint Alternatively, rotate the view using one of the following methods:
• Hold down the ALT key as you drag the mouse.
• Right-click in the view window, and then click View>Rotate on the shortcut menu.
Hint Alternatively, pan the view using one of the following methods:
• Hold down the SHIFT key as you drag the mouse.
• Right-click in the view window, and then click View>Pan on the shortcut menu.
Hint Alternatively, zoom in or out on the view using one of the following methods:
• Hold down the ALT+SHIFT keys as you drag the mouse.
• Right-click in the view window, and then click View>Zoom on the shortcut menu.
Related Topics
Zooming In or Out on a Rectangular Area
Fitting Objects in the View Window
Zooming In or Out on a Rectangular Area
To magnify or shrink a specific rectangular area in the view window:
When zooming on a view of model objects, the absolute size of the model does not change.
When zooming on a 2D report, axis labels and ticks will adjust after the zoom operation is
complete.
3. To end Zoom mode, click View>Zoom In or View>Zoom Out or press ESC.
Related Topics
Zooming In and Out
Fitting Objects in the View Window
Hint Alternatively, fit all objects in the active view window using one of the following
methods:
• Press CTRL+D.
• Right-click in the view window, and then click View>Fit All on the shortcut menu.
When Fit All is used in a report view, the window is automatically rescaled to fit all traces in the
window and the axis label and ticks are rescaled.
Related Topics
Fitting a Selection in a View Window
Fitting a Selection in a View Window
1. When you are working on a model view, select the objects you want to fit in the view. When
you are working on a report, select the traces you want to fit.
2. To fit the selection in the active view window: Click View>Fit Selection>Active View.
3. To fit the selection in every open view window of the active design: Click View>Fit Selec-
tion>All Views.
Hint Alternatively, fit the selection in the active view window by clicking View>Fit Selection
on the shortcut menu.
Related Topics
Fitting All Objects in a View Window
Note Hiding boundaries also turns off a check for boundary overlaps during boundary
assignment. In the case of very large models with many boundaries, hiding boundaries
can prevent delays during boundary assignment. Full model validation will subsequently
check for boundary overlaps.
Showing Objects
To show one or more objects that are currently hidden:
1. Click View>Active View Visibility .
The Active View Visibility dialog box appears.
2. Select the tab for the objects you want to show or hide. The dialog contains tabs for 3D Mod-
eler objects, Color Key objects, Boundaries, Excitations, and Fields Reporter objects.
3. Under the tab you need, select the Visibility option for the objects you want to show in the
active view window.
• For designs with large numbers of objects, you can resize the dialog for easier selection.
• By default, objects are listed in alphabetical order. You can invert the order by clicking the
Name bar above the Name fields. A triangle in the bar indicates the direction of the listing.
• You can also use the Name field to type in an object name and apply the visibility via the
Show and Hide buttons.
The objects you select and designate as Visible (by selecting the property or using Show) reap-
pear.
Note Hiding boundaries also turns off a check for boundary overlaps during boundary
assignment. In the case of very large models with many boundaries, hiding boundaries
can prevent delays during boundary assignment. Full model validation will subsequently
check for boundary overlaps.
Note Hiding boundaries also turns off a check for boundary overlaps during boundary
assignment. In the case of very large models with many boundaries, hiding boundaries
can prevent delays during boundary assignment. Full model validation will subsequently
check for boundary overlaps.
Hint You can also press F6 (Wire Frame) and F7 (Smooth Shaded) to toggle between these
two views.
Related Topics
Setting the Default View Rendering Mode
Setting the Surface Visualization
Setting the Default View Rendering Mode
To set a default rendering mode for all objects created in the active design and in future designs:
1. Click Tools>Options>Modeler Options.
2. Click the Display tab.
3. Select one of the following from the Default View Render Mode pull-down list.
• Wireframe.
The objects in the view window will be displayed as skeletal structures, enabling you to
see all sides of the objects at one time.
• Smooth Shaded.
The objects in the view window will be displayed as shaded objects with smooth edges.
4. Click OK.
The rendering mode will be applied to all new objects you create.
Note Wire bodies cannot be rendered with a Maximum Normal Deviation value less than 1
degree. When using a setting less than 1 degree all wire bodies will be rendered with a
setting of 1 degree and all closed bodies will be rendered with the dialog box setting.
5. The Save As Default button lets you Save any values you change to the drop down menus for
the fields.
6. The Restore Defaults button lets you return to the original values. Any values you provided
through Save As Default remain on the drop down menus for the fields for surface and normal
deviations
7. Click Apply to apply the current values to the active modeler window, and Close or Cancel to
close the dialog without changing settings.
Related Topics
Rendering Objects as Wireframes or Solids
2. The Add button contains a drop down menu with choices for Specify center, normal, and Use
selection. Of you want to use selection, you must first select a face or a cut plane.
• If you first select a face or cut plane, and then click Add>Use Selection, the clip plane is
a. If you select Add>Specify center, normal, this launches a Measure dialog and enters a
mode for you click to first define the start location, shown as a triad. When you move the
cursor, a rectangle represents the clip plane, and a vector the current direction.
After the second click, the clip plane is active. The handle is visible as a circle with a
sphere at the center, and an arrow pointing the normal for the plane. The Clip Planes dia-
log shows the clip plane name, that it is enabled, shows the cap (which is the plane sur-
face), and shows the handle.The Flip selection lets you reverse the direction of the clip
plane. If you uncheck Show cap and/or show handle, they disappear from the display.
3. With Show Handle enabled, you can use the handle to manipulate the location and orientation
of the clip plane. The handle changes appearance and function relative to the position of the
4. The Options tab for the Clip Planes dialog contains four options.
• Force opaque for the unclipped portion.
• Disable clip plane when drawing a new clip plane.
• Plane handle color
The button shows the current color. Click the button to display a color selection dialog.
Select a default or custom color and click OK.
• Plane handle radius.
This slider lets you resize the radius of the handle to the most convenient size. The radius
resizes dynamically. When you close and reopen the modeler window, the last selected
size persists.
You can save your choices as new defaults.
Related Topics
Copy Image
Exporting Graphics Files
2. Select one of the following grid styles for the active view window:
Dot Displays each grid point as a dot.
Line Displays lines between grid points.
• Click Modeler>Grid Plane, and then select a grid plane: XY, YZ, or XZ.
• Click a grid plane on the pull-down list on the 3D Modeler Draw toolbar:
In HFSS, mesh operations are optional mesh refinement settings that provide HFSS with mesh
construction guidance. This technique of guiding HFSS’s mesh construction is referred to as "seed-
ing" the mesh. Seeding is performed using the Mesh Operations commands on the HFSS menu.
You can instruct HFSS to reduce the maximum size of tetrahedral elements on a surface or within a
volume until they are below a certain value (length-based mesh refinement) or you can instruct
HFSS to refine the surface triangle length of all tetrahedral elements on a surface or volume to
within a specified value (skin depth-based mesh refinement). These types of mesh operations are
performed on the current mesh, that is, the most recently generated mesh.
In a few circumstances, you may also want to create a mesh operation that modifies HFSS’s surface
approximation settings for one or more faces. Surface approximation settings are only applied to
the initial mesh, that is, the mesh that is generated the first time a design variation is solved.
You can also choose to override automatic choice of which mesher HFSS uses, by using the
HFSS>Mesh Operations>Initial Mesh Settings command.
See the technical notes for more details about HFSS’s application of mesh operations.
What do you want to do?
• Perform length-based mesh refinement on object faces.
• Perform length-based mesh refinement inside objects.
• Perform skin depth-based mesh refinement on object faces.
• Modify surface approximation settings for one or more faces.
• Specify automatic or specified model resolution for a selection.
• Specify the initial mesh settings
Related Topics
Plotting the Mesh
Technical Notes: The Mesh Generation Process
Related Topics
Plotting the Mesh
Technical Notes: Surface Approximation Settings
Technical Notes: Guidelines for Modifying Surface Approximation Settings
Technical Notes: The Mesh Generation Process
Related Topics
Plotting the Mesh
Setting the Healing Options
Technical Notes: Model Resolution
Hint Define a new mesh operation rather than modify an existing mesh operation. HFSS will
not re-apply a modified mesh operation.
Applying mesh operations without solving enables you to experiment with mesh refinement in spe-
cific problem regions without losing design solutions. You cannot undo the applied mesh opera-
tions, but you can discard them by closing the project without saving them, or by reverting to the
initial mesh.
Related Topics
Technical Notes: The Mesh Generation Process
Plotting the Mesh
Specifying the Analysis Options
General Options: Analysis Options Tab
Remote Analysis
time and may cause issues for dirty models. Tolerant uses a looser tolerance for surface
representation, which may be better for dirty or very complex geometry.
• Ansoft Classic Mesh--this is based on the HFSS 11 mesher.
9. To make your choice the default, use the Save as default checkbox.
10. Click OK to apply your choices.
The settings will be applied to the initial mesh generated on the selected surface.
Related Topics
Defining Mesh Operations
Note This will not alter any existing meshes that have already made use of one or more mesh
refinement operations. However, deleted mesh operations will not be used again after
reverting to the initial mesh.
Note This pertains to mesh setup operations only. However, if you want to see information
about a mesh that has been generated, see Viewing Mesh Statistics.
Specify how HFSS or HFSS-IE will compute a solution by adding a solution setup to the design.
You can define more than one solution setup per design. Each solution setup includes the following
information:
• General data about the solution’s generation.
• Adaptive mesh refinement parameters, if you want the mesh to be refined iteratively in areas of
highest error.
• If you want to solve of a range of frequencies, you can add a frequency sweep.
Related Topics
Adding a Solution Setup to an HFSS Design
Adding an Solution Setup to an HFSS-IE Design
you to bypass the adaptive analysis process and just perform a frequency sweep. For driven
problems HFSS always requires at least one adaptive pass. Entering 1 will also bypass adaptive anal-
ysis, generating a solution only at the solution frequency you specified.
7. Click OK.
8. Optionally, add a frequency sweep to the solution setup.
Related Topics
Add Dependent Solve Setup
Setting Adaptive Analysis Parameters for HFSS
Technical Notes: The HFSS Solution Process
Copying a Solution Setup
Renaming a Solution Setup
Note For Fast sweeps, HFSS uses the solution frequency as the center frequency if it is within
the frequency range (greater than the start frequency and less than the stop frequency.)
Otherwise the middle of the frequency range is used as the center frequency.
Warning Because the minimum frequency is used to normalize some matrices, if the
frequency is set too low, HFSS tries to solve a nearly-singular matrix, which may
erode the accuracy of the calculations. As a general rule, do not enter a frequency
less than 0.01 times the suggested, or default, value for Minimum Frequency.
ber of passes has not been completed, the adaptive analysis will continue unless the convergence
criteria are reached.
To set the maximum number of passes for an adaptive analysis:
• Under the General tab of the Solution Setup dialog box, enter a value for Maximum Num-
ber of Passes.
For driven problems HFSS always requiring at least one adaptive pass. Entering 1 will bypass adap-
tive analysis, generating a solution only at the solution frequency you specified.
Note The size of the finite element mesh — and the amount of memory required to generate a
solution — increases with each adaptive refinement of the mesh. Setting the maximum
number of passes too high can result in HFSS requesting more memory than is available
or taking excessive time to compute solutions.
Related Topics
Adding a Solution Setup to an HFSS Design
Adding an Solution Setup to an HFSS-IE Design
Setting the Maximum Delta S Per Pass
For designs with ports or Transient Solutions for Device Characterization.
The delta S is the magnitude of the change of the S-parameters between two consecutive passes.
The value you set for Maximum Delta S is a stopping criterion for the adaptive solution. If the
magnitude of the change of all S-parameters are less than this value from one iteration to the next,
the adaptive analysis stops. Otherwise, it continues until the requested number of passes is com-
pleted.
To set the maximum delta S per adaptive pass:
• Under the General tab of the Solution Setup dialog box, enter a value for Maximum Delta S.
Delta S data is available only after HFSS completes two iterations of the adaptive analysis process.
Note Delta S is computed on the appropriate S-parameters - modal or terminal - after the S-
parameters have been de-embedded and renormalized.
Related Topics
Adding a Solution Setup to an HFSS Design
Adding an Solution Setup to an HFSS-IE Design
Viewing the Maximum Magnitude of Delta S Between Passes
Technical Notes: Maximum Delta S
Setting the Maximum Delta Energy Per Pass
For designs with voltage sources, current sources, incident waves or magnetic bias or Transient
Solutions for Field Visualization.
Not applicable to designs with ports.
The delta Energy is the difference in the relative energy error from one adaptive solution to the
next. The value you set for Maximum Delta Energy is a stopping criterion for the adaptive solu-
tion. If the delta Energy falls below this value, the adaptive analysis stops. Otherwise, it continues
until the convergence criteria are reached.
To set the maximum delta Energy per adaptive pass:
• Under the General tab of the Solution Setup dialog box, enter a value for Maximum Delta
Energy.
Delta Energy data is available only after HFSS completes two iterations of the adaptive analysis
process.
Related Topics
Viewing the Delta Magnitude Energy
Technical Notes: Maximum Delta Energy
Setting the Maximum Delta Frequency Per Pass
For Eigenmode solution types
The delta Frequency is the percentage difference between calculated eigenmode frequencies from
one adaptive pass to the next. The value you set for Maximum Delta Frequency Per Pass is a
stopping criterion for the adaptive solution. If the eigenmode frequencies change by a percentage
amount less than this value from one pass to the next, the adaptive analysis stops. Otherwise, it con-
tinues until the maximum number of passes is completed.
To set the Maximum Delta Frequency Per Pass:
• Under the General tab of the Solution Setup dialog, enter a value for Maximum Delta Fre-
quency Per Pass.
Delta Frequency data is available only after HFSS completes two iterations of the adaptive
analysis.
Related Topics
Specifying Convergence on Real Frequency Only
Specifying Convergence on Real Frequency Only
For Eigenmode solution types.
Selecting Converge on Real Frequency Only causes the percent difference calculation among a
set of frequencies to be based only on the real parts of the frequencies; the imaginary parts of the
frequencies are ignored.
• Under the General tab of the Solution Setup dialog box, select Converge on Real Frequency
Only.
Specifying Expressions for Adaptive Convergence
You can specify additional convergence criteria through the use of expressions and output vari-
ables. The Max Delta or the Max Percent Delta defined for expression convergence represents the
difference in values of the expressions between consecutive adaptive passes. If the difference in the
value of the expression between consecutive passes is less than the Max Delta or the Max Percent
Delta value this part of the convergence criteria is satisfied.
• For driven solutions, if the Maximum Delta S, Maximum Delta E, or alternate matrix con-
vergence criteria are achieved in addition to any specified expression convergence criteria, the
adaptive analysis stops. Otherwise, the solution continues until the requested number of passes
is completed.
• For eigenmode solutions, if the Maximum Delta Frequency Per Pass criteria is achieved in
addition to any specified expression convergence criteria, the adaptive analysis stops. Other-
wise, the solution continues until the requested number of passes is completed.
To set expressions as Convergence criteria:
1. Double-click on the setup icon in the Project tree to open the Solution Setup dialog.
2. Click the Expression Cache tab in the Solution Setup and click the Add... button to open the
Add to Expression Cache dialog.
3. Specify the context for the expression you define. For Modal Solution Data, you do not need
context other than the Solution. Other selections require more context:
• Emission Test also requires a digital signal.
• Far Field field also requires a geometry such as an infinite sphere.
• Fields or Near Fields also require a geometry such as a polyline.
4. Under the Trace tab, select from the Category, Quantity and Function lists to create expres-
sions.
Selecting a listed category lists the Quantities and Functions available for each category. If you
have defined one or more output variables, you can see them listed as Quantities by selecting
the Output Variables Category. The Output Variables button opens a dialog that lets you
define additional output variables.
When you have created an expression, it appears in the Expression field of the Trace tab. If
desired, you can use the Range Function button to select range functions to apply to the expres-
13-14 Specifying Solution Settings
HFSS Online Help
sion.
Under the Calculation Range tab, you can view the values of available sweep variables.
Clicking the ellipsis [...] button in the Edit column opens a list of values.
5. When you have created an expression that you want to add to the cache, click the Add Calcu-
lation button.
This adds the selected expression and the associated context to a table in the Expression
Cache tab. You can select any additional expressions with contexts and add them in the same
way.
6. When you have added the expressions you want, click Done to close the Add to Expression
Cache dialog.
The Expression Cache tab of the Solution Setup lists the expressions you have added as a
table.
• The Title field is editable, by default showing the name as built from the expression, but
removing underscores.
• The Expression field shows the full expression. If necessary, you can resize the Solution
Setup dialog. You can also resize each column in the table.
• The Context column shows None for Modal solutions, or the appropriate geometry for
Fields calculations.
• The PP Variables column contains a checkbox that lets you designate post processing
variables, such as for renormalization or deembedding. You can also use this feature to
assign variables to non-model objects (for example, the properties of a solid, sheet or lines
used for field calculations). You can also assign a PP Variable to a coordinate system (CS)
that is not associated with model objects.
To excite particular sources for particular output variables, you can assign a post process
variable to the magnitude of sources you might want to edit, and assign the expression
value in the Expression Cache. With PP Variables, you can control convergence based on
several combinations of active sources.
• The Intrinsics column shows a clickable button that opens an Edit Calculation Range
dialog. If the column button shows None you cannot edit the value. If the button shows
variables, click the ellipsis [...] in the Edit column to display a list of the variable values
that you can select. Click OK to close the Edit Calculation Range dialog and apply your
selections to the Expression Cache.
7. To designate one or more expressions for convergence, click the field for the Convergence col-
umn for each expression.
This opens an Adaptive Convergence dialog.
Check Use this expression for convergence to enable the radio buttons. You can then specify
the Max Delta between passes or the Max Percent Delta criteria. The Max Delta solves a
potential issue if your expression is essentially zero and the numeric noise from pass to pass
causes the maximum percentage delta to remain high. In that case adaptive refinement contin-
ues until you get to the maximum number of passes.
8. Click OK to close the Solution Setup dialog.
Related Topics
Viewing Convergence Data
Viewing the Output Variable Convergence
Specifying Output Variables
Specifying a Source for the Initial Mesh
You may choose to specify a source for the initial mesh from either the current design or another
design. The source mesh should represent a geometrically equivalent model. To specify a source
for the initial mesh:
1. Under the Advanced tab of the Solution Setup dialog box, click the checkbox for Import
Mesh.
This displays the Setup Link dialog. By default, the Source Project checkboxes for Use This
Project and the Source Design checkbox for Use This Design are selected.
Note that when you setup a link to an external source, the Lamda refinement option is dese-
lected under the Options tab to avoid over-refinement of the linked mesh.
If you uncheck Use This Project, you enable fields for selecting a different project and radio
buttons to specify whether to save the source path relative to The project directory of the
selected project or This project.
2. To specify a Source Project file click the ellipsis [...] button to open a file browser window.
When you selected the project, click the Open button to accept the project file for the setup.
Note The solution in the source design must provide data for the target design's adaptive
frequency as well as its sweeps. That is, the adaptive frequency for the target design
must be included in the sweep in the source design.
If necessary, you can open the source design and add an appropriate frequency point to
an existing sweep.
3. For the Source Design, if you leave Use This Project checked, you can uncheck Use This
Design to enable the a dropdown menu for to select from other available designs.
4. For the Source Solution field, you can use the dropdown menu to select from other possible
solutions.
5. Use the checkbox specify whether to Force source design to solve in the absence of linked
data in the target design.
6. Use the checkbox to specify whether to preserve the source design solution. Note that in the
Extractor mode, the source project will be saved upon exit. Extractor mode means that the
software is opened during the link solely for the purpose of solving.
7. The second tab, Variable Mapping, lets you view any variables contained in the Project you
select.
When there are variables in the source design, you can choose to "map" these variables to con-
stant values, expressions or variables in the target designs. Variable mapping becomes more
important when the datalink type requires source and target design to be geometrically identi-
When a variable in the target design has the same name of a source design variable but the 2
variables are not mapped, the Parameter tab will become the active tab with the following
message box popped.
You can exit the Setup Link dialog directly by selecting "Accept Setup and Exit Dialog" or
reexamine the parameter mapping by selecting "Return to Setup Dialog".
In the Setup Link dialog, for linked designs with variables of the same name, you can click
Map Variables by Name to automatically map same named variables. In this example the
variables height and weight are mapped to the Source, whereas the variable does not have a
same named counterpart, and retains its value in the source design.
8. You can select the Additional mesh refinements tab to specify the following:
• For Mesh Operations, you can select radio buttons to either Apply mesh operation in tar-
get design on the imported mesh, or Ignore mesh operations in target design (default).
• For Port Adapt, you can check Perform port adapt in target solve setup.
9. Click OK to accept the setup and close the Setup dialog box.
Related Topics
Clear Linked Data
Setting Lambda Refinement
Clearing Linked Data
Linked data can be mesh, field or some other post-processing data that the source design generated.
The target design for the link caches these data internally to minimize the need to activate the
source design.
If you have previously setup links to a design, the HFSS>Analysis Setup menu contains an option
to Clear Linked Data. This removes the linked data for all links in a design, therefore invalidating
the solutions. You can also clear linked data through HFSS>Results>Clean Up Solutions, which
displays a dialog that includes options that let you selectively delete linked data only, or as part of
other deletions.
Clearing linked data for some link types requires HFSS to revert to the initial mesh. Thus in some
cases, this command removes the current mesh of the target design.
Related Topics
Deleting Solution Data
Setting Lambda Refinement
Lambda refinement is the process of refining the initial mesh based on the material-dependent
wavelength. It is recommended and selected by default. If you select the Use Current Mesh From
option under the Advanced tab, Do Lamda Refinement is deselected. If you make the Specify
Use Current Mesh From selection as the Current design, the Do Lamda Refinement fields are
disabled. If you make the Specify Use Current Mesh From selection as Other design and Setup
the Link, the Do Lamda Refinement fields remain enabled so that you can select it if desired.
To specify the size of target value by which HFSS will refine the mesh:
1. Under the Options tab of the Solution Setup dialog box, select Do Lambda Refinement.
This enables the Target field and the Use free space lambda check box.
2. Enter a value for the wavelength in the Target field or accept the defaults.
The Target defaults depend on the Order of Basis function selections. For example, for Driven
solutions and a First Order basis function, the default target is 0.3333, which means that HFSS
will refine the mesh until most element lengths are approximately one-third wavelength.
For eigenmode solutions and a First Order basis function, the default target is 0.2
If you change the Order of Basis functions in the Solution Setup dialog, the default changes
automatically. Setting the Order of Basis affects the default value of the Lambda Refinement
Note Changing the Lambda refinement target invalidates any solutions that were performed
with the previous lambda refinement.
Related Topics
Setting the Max Order of Solution Basis
Specifying a Source for the Initial Mesh
Note Changing the Lambda refinement target invalidates any solutions that were performed
with the previous lambda refinement.
Related Topics
Adding a Solution Setup to an HFSS Design
Adding an Solution Setup to an HFSS-IE Design
• Under the Options tab of the Solution Setup dialog box, enter a value for percent Maximum
Refinement Per Pass.
Related Topics
Technical Notes: Percent of Tetrahedra Refined Per Pass
Adding a Solution Setup to an HFSS Design
Adding an Solution Setup to an HFSS-IE Design
Note For a solve setup with zero passes, no sweeps, and that is not ports only, validation
produces a warning message.
Related Topics
Adding a Solution Setup to an HFSS Design
Adding an Solution Setup to an HFSS-IE Design
Setting the Minimum Number of Converged Passes
An adaptive analysis will not stop unless the minimum number of converged passes you specify
has been completed.
• Under the Options tab of the Solution Setup dialog box, enter a value for Minimum Con-
verged Passes.
The convergence criteria must be met for at least this number of passes before the adaptive
analysis will stop.
Related Topics
Adding a Solution Setup to an HFSS Design
Setting Matrix Convergence Criteria
For designs with ports.
You can specify different stopping criteria for specific entries in the S-matrix. This is done in the
Matrix Convergence dialog box. The adaptive analysis will continue until the magnitude and
phase of the entries change by an amount less than the specified criteria from one pass to the next,
or until the number of requested passes is completed.
To set the matrix convergence:
1. Under the General tab of the Solution Setup dialog box, select Use Matrix Convergence.
2. Click Set Magnitude and Phase.
The Matrix Convergence dialog box appears.
3. Select one of the following from the Entry Selections pull-down list:
All Sets all of the matrix entries at once. (The default).
Diagonal/Off- Sets all of the diagonal matrix entries at once, all off-diagonal matrix
Diagonal entries at once, or both diagonal and off diagonal entries at once.
Selected Entries Sets individual matrix entries that you will select.
For the selection All, enter the convergence criteria for the Maximum Delta (Mag S) and the
Maximum Delta (Phase S) in the fields to the right.
For the selection Diagonal/Off-Diagonal, first check Diagonal Entries, Off-Diagonal
Entries, or both, to enable the convergence criteria field or fields. Then enter the convergence
criteria for the Maximum Delta (Mag S) and the Maximum Delta (Phase S) in the fields to
the right.
For both of these Entry Selections, you can set the Ignore Phase when Mag is less than
value. See the note on technical issues under step 4 c.
4. If you chose Selected Entries, the Matrix Convergence dialog displays some new fields:
• a table showing columns for Matrix Entry 1, Matrix Entry 2, and the Delta Mag and Delta
Phase.
• Entry 1 and Entry 2 fields which contain drop down lists of ports and associated modes
(or terminals).
• an Insert button with which to move selections from the port list selections to the table
To select the desired ports and mode (or terminal) pairs, do the following:
a. Select Entry 1 and Entry 2 from their drop down lists.
b. In the Magnitude box, enter the maximum change in magnitude from pass to pass from
the Entry 1 to Entry 2.
c. In the Phase box, enter the maximum change in phase, in degrees, from pass to pass from
Entry 1 to Entry 2.
Note: When the Mag S becomes small (near to zero) its phase becomes indefinite and
insignificant due to mathematical issues. In HFSS 10 and 11 there was a 0.05 magnitude
threshold that caused that Phase Margin to be discarded. However, some users may want
to continue running additional passes to stabilize phase margins even when the S-parame-
ter magnitude is below this threshold. For this reason, the magnitude threshold has been
removed. This calls for caution if you want to see a good phase convergence for S12 which
is near to 1. If you set a small delta_phi with small delta_s, after a couple of passes, S12
will converge, but S11 never, since S11 ~0 and its phase changes with the mesh noise
because the phase is indefinite. In other words, under these conditions the adaptive pro-
cess never stops, so you should abort it.
d. Click Insert.
The entries appear in the table above. If you have selected multiple entries, all combina-
tions of matrix entry1 and matrix entry2 populate the table.
Selecting a Row in the table enables the Delete button, if you need to remove a row from
the table.
Clicking in the Delta Mag and Delta Row fields of the selected row enables editing in
those fields.
5. Click OK to close apply the values and close the dialog.
Related Topics
Viewing the Magnitude Margin
Viewing the Phase Margin
Viewing Delta (Mag S)
Viewing Delta (Phase S)
Setting the Order of Basis Functions
You can change the basis functions HFSS uses to interpolate field values from nodal values.
• Under the Options tab of the Solution Setup dialog box, select Order of Basis.
This can be First Order (the default), Zero Order, Second Order, or Mixed order.
Setting the Order of Basis functions affects the default value of the Lambda Refinement in the
Solution setups as follows.
Zero order: driven 0.1, eigenmode 0.1
First order: driven 0.3333, eigenmode 0.2 (as is)
Second order: driven 0.6667, eigenmode 0.4
Mixed order driven 0.6667 eigenmode 0.6667
The Zero order option is useful when a model requires a mesh that produces more than 100,000 tet-
rahedra, but the model size is small compared to wavelength. The higher order options solve pro-
gressively more unknowns for each tetrahedra. Mixed order uses higher order where more accuracy
is required, and lower order where fields are weaker.
Warning If you select Zero Order Solution Basis, all tetrahedra in the model must have edge
lengths less than 1/20th wavelength. Thus, this option is usually selected in
combination with a specific lambda refinement setting.
Related Topics
Technical Notes: Basis Functions
Setting Lambda Refinement
Enable Iterative Solver
Enable Iterative Solver
The iterative solver provides an alternative to the multi-frontal solver when a matrix is well-condi-
tioned for an iterative solution. The iterative solver significantly reduces memory usage, and it can
also provide a savings in the solution time for large simulations.
When you select the Enable Iterative Solver option, HFSS automatically invokes the iterative
solver when it decides that the matrix is conditioned well enough to take advantage of the iterative
approach. HFSS uses the multi-frontal solver if the matrix does not meet this requirement.
For more detail, see the technical notes for Iterative Matrix Solver.
To enable the Iterative solver:
1. On the Solution Setup dialog, Options tab, check the Enable Iterative Solver check box.
This enables the Relative Residual checkbox.
2. Enter a value for the Relative Residual. The residual measures the convergence of the iterative
solver. The default value is 1E-4.
Note The Iterative Solver is not available for zero order basis solutions.
Related Topics
Technical Notes: Iterative Matrix Solver
Enable Use of Solver Domains
If a problem is too large to solve on one machine HFSS can automatically partition a design into
domains that can be solved by separate processes. Before enabling solver domains, you must have
the distributed solve option, and you must have allocated at least three distributed machines to the
solve pool. The number of domains that the solver creates is at least one less than the number of
distributed machines available in the pool. The first machine in the list acts as a master node that
performs the meshing and domain iteration but does not solve a domain.
Domain use can be invoked for a solve when
• The Enable Use of Solver Domains check box under the Solution Setup Options tab is
checked.
• You have provided at least three distributed machines in the pool
• The solver determines that the problem is large enough (the mesh has enough tets) to bother
with domains.
Restrictions on solver domains are that the design and analysis setup cannot include:
• The design cannot contain master and slave boundaries.
• Eigenmode solution type.
• Mixed order basis.
• Fast frequency sweeps.
If any condition is not met, the problem is solved with the non-domain solver defined under the
solution options. When these conditions are met:
• The solver chooses the number of domains to use, based on the machines available. The num-
ber of domains chosen will likely be close to the maximum. The maximum is one less than the
total because the first machine in the pool is used to control domain iterations.
• The solver creates the domain meshes of roughly the same size
• Domain meshes are created every time the global mesh changes (before each adaptive pass)
Note • You provide resources for the distributed solve by adding machines to the
distributed machine pool. A machine can appear in the pool more than once. You
should use this capability to maintain a balanced load.
• Because the domains should be roughly the same size, you should provide balanced
resources.
Related Topics
HFSS Options: Solver Tab
General Options: Analysis Options tab
Configuring Distributed Analysis
Selecting an Optimal Configuration for Distributed Analysis
Balancing Resources for Solver Domains
Technical Notes: Domain Decomposition Method
Balancing Resources for Solver Domains
The Use Solver Domains option for large models requires that you provide resources for the dis-
tributed solve by adding machines to the distributed machine pool.
Because the domains should be roughly the same size, you should provide balanced resources. As
an example of balancing the load, suppose that machine called Patriot has 256 GB and another
called Cutlass has 64 GB. If you want up to five domains, it makes sense to enter Patriot in the pool
four times and Cutlass once.
Under HFSS Options, you should set the Desired RAM Limit (Mem_Limit_Soft) to the memory
desired for each individual domain.
In the example above, a good choice for Mem_Limit_Soft would be 64 GB.
Remember:
• A machine can appear in the pool more than once. The user should use this capability to main-
tain a balanced load.
• The first machine in the pool is used to control domain iterations.
• Under HFSS Options, the Number of Processors is also set per domain.
In the example above, a machine named Patriot has 16 processors and a machine named Cutlass has
8 processors. Four domains will go on Patriot, so Number of Processors should be set to 4. Four
processors on Cutlass will be unused.
Recommendation: it is more important to use memory efficiently than to use all the processors.
Related Topics
HFSS Options: Solver Tab
General Options: Analysis Options tab
Configuring Distributed Analysis
Selecting an Optimal Configuration for Distributed Analysis
Technical Notes: Domain Decomposition Method
Use Radiation Boundary on Ports
If the design includes waveports, the Use Radiation Boundary on Ports option is enabled under
the Advanced options tab of the Solution Setup dialog box.
• If you select this setting, edges which are assigned to ABC and touch a port have an radiation
boundary condition applied during the port solution.
• If you do not select the setting, a perfect conducting boundary condition is used during the port
calculations.
In most cases this setting has a limited effect on the overall fields or post processed quantities.
Port Options
If the design includes waveports, the Port Options options appear under the Advanced options tab
of the Solution Setup dialog box. These options include:
• Maximum Delta Zo - change to Zo specified as a target percentage. The default is 2%.
• Use Radiation Boundaries on Ports
• Set Triangles for Wave Port - unchecked by default.
If you check Set Triangles for Wave Port, the Minimum and Maximum fields are enabled.
You can edit the default values of 100 for the minimum and 500 for the maximum.
For designs with lumped ports, this option is not active. Higher numbers of triangles would not
benefit a solution setup in this case.
13-26 Specifying Solution Settings
HFSS Online Help
Before the first HFSS or Maxwell solve, for this kind of project, you set an initial value for temper-
ature dependent objects..
If you check Enable Thermal feedback from ANSYS Mechanical, a .THM subdirectory to the solu-
tion directory for the Project involved will be created will be created when Workbench imports the
results from HFSS or Maxwell. Within that directory, a new file centroid.xml is written, to be used
for later mapping. The ANSYS Workbench 12 subsequently exports the temperature information to
a file named mechanical.ths in the same Project subdirectory.
Related Topics
Export Transfer File for ANSYS
Re-solving After ANSYS Thermal Link Feedback
Produce Derivatives for Selected Variables
If your design has variables with specified units, the Derivatives tab of the Solution Setup lists
them. Derivatives can be used through the Tune Reports command for interactive exploration of
small variations in the design, without you having to solve again. The "nominal" solution, plus the
derivatives contain all the information needed for you to approximate the solution for small varia-
tions in the design. Furthermore, for Optimetrics, the SNLP optimizer will take advantage of the
derivatives when they are available, which can reduce the number of simulations needed to find the
optimum.
To have HFSS calculate derivatives for any of these variables:
1. Open the Derivatives tab of the Solution Setup
2. For the desired variable, click the checkbox in the Use column.
These derivatives can be used by the Derivative Tuning feature (the Results menu Tune Reports
command) in relation to quantities like S-parameters. They cannot be used for frequencies and local
quantities like fields.
Related Topics
Setting Adaptive Analysis Parameters
Derivative Tuning for Reports
Dependent setups are pasted along with the copied setup. You are warned if the dependent setup is
already in the design and setup is not pasted again.
Note For a solve setup with zero passes, no sweeps, and that is not ports only, validation
produces a warning message.
Related Topics
Disabling a Frequency Sweep
Technical Notes: Frequency Sweeps
Selecting the Sweep Type
For Driven solution types.
Specify the type of sweep you want to perform in the Edit Sweep dialog box. Choose one of the
following sweep types:
Fast Generates a unique full-field solution for each division within a frequency
range. Best for models that will abruptly resonate or change operation in the
frequency band. A Fast sweep will obtain an accurate representation of the
behavior near the resonance. Fast sweeps are disabled if an anisotropic
boundary condition is present.
Discrete Generates field solutions at specific frequency points in a frequency range.
Best when only a few frequency points are necessary to accurately represent
the results in a frequency range.
Interpolating Estimates a solution for an entire frequency range. Best when the frequency
(default) range is wide and the frequency response is smooth, or if the memory
requirements of a Fast sweep exceed your resources.
All discrete basis solutions are solved prior to interpolating sweeps because it
is possible that an interpolating sweep can re-use already solved frequencies
from a discrete sweep.
For Time Domain Reflectometry plots (TDR), you must use an interpolating
sweep.
When you select Interpolating sweeps in the Edit Sweep dialog, the Setup Interpolation options
section is activated. This lets you specify a maximum number of solutions, and other interpolation
values.
If you expect to use the same settings often, you can click the Set Defaults button. To use previ-
ously saved settings, click the Use Defaults button.
Related Topics
Technical Notes: Frequency Sweeps
Click the Advanced Options... button to open the Interpolating Sweep Advanced Options dia-
log.
• DC Extrapolation options
1. Select Extrapolate to DC to enable the DC Extrapolation options.
2. Enter a value for the Minimum Solved Frequency. This value represents the a recom-
mendation for the smallest frequency in the sweep for which a full solution is generated.
The default is 100 Mhz.
Note The Minimum Solved Frequency that you enter is a recommendation, not a requirement.
If the step size is greater than that value, it won't go below the step size (assuming the
stop frequency is a multiple of step size).
If you expect to use the same settings often, you can click the Set Defaults button. To use previ-
ously saved settings, click the Use Defaults button.
Note If a driven setup’s ports-only setup changes and then the problem type switches between
driven modal and driven terminal, HFSS resets the interpolation basis data types for the
interpolating sweep.
The Max Solutions value is the maximum number of solutions that will be solved for the fre-
quency range. For fast sweeps and for interpolating sweeps the default is 250. To change the value:
1. Open the Edit Sweep dialog box (by either viewing the properties of an existing Sweep or by
Adding a Frequency sweep to an existing Setup).
2. Type a value in the Max Solutions box and click OK.
If you expect to use the same settings often, you can click the Set Defaults button. To use previ-
ously saved settings, click the Use Defaults button.
Note HFSS automatically subdivides the interpolating sweep range so that no single subrange
gets too many basis elements. The effect is that you can now (if appropriate) request
hundreds of basis elements in the Max Solutions box for interpolating sweep setup,
without incurring any basis seeding performance penalty.
3. Specify Entry Selections and Mode Selections as desired and click SET, or click individual
waveport cells and select ON.
In the table location corresponding to the selection, the dash in the display is replaced by ON.
For example, selecting the first element in the row list and the fourth element in the column
list, and then Set Selection places an ON in the first row, fourth column. You can select one
entry at a time via the dropdown in the matrix cell, or clear the entire table with the Clear All
button. You can also Clear only the entries specified by the Entry and Mode selection settings
(such as off-diagonal, higher order).
4. Click OK to close apply the selections and close the dialog.
Related Topics
Setup Interpolations Basis
Specifying the Frequency Points to Solve
You can specify the following types of frequency points to solve within a frequency sweep:
Linear Step A linear range of frequency points in which you specify a constant step size.
Linear Count A linear range of frequency points in which you specify the number, or count,
of points within the frequency range.
LogScale A logarithmic range of frequency points in which you specify a frequency
range and a samples number. For Discrete sweeps.
Single Points Individual frequency points. For Discrete sweeps.
Select the type of frequency point entry from the Type pull-down list The Edit Sweep dialog con-
tains a Time Domain Calculation tool that you can use to help calculate frequency step sizes and
maximum frequencies, particularly if you intend to perform Full-Wave Spice analysis.
For Discrete sweeps, HFSS always solves the frequencies from highest to lowest.
Related Topics
Change the Value of an Existing Frequency Point
Specifying Single Frequency Points
Deleting Frequency Points
Insert Frequency Points
Specifying Frequency Points to Solve
4. In the Step Size box, type the difference between frequency points.
HFSS will solve the frequency point at each step in the specified frequency range, including
the start and stop frequencies.
For example, specifying 10 for the start frequency, 20 for the stop frequency, and 2.5 for the
step size for a Discrete sweep instructs HFSS to compute a solution for frequencies of 10,
12.5, 15, 17.5, and 20.
To view a table of the frequencies and count, click the Display button. If the list of frequencies
is longer than the visible display, you can use a scroll bar to view the list to the end of the
count.
5. For Fast sweeps, select Save Fields if you want to save the calculated 3D field solutions asso-
ciated with all port modes at the chosen frequencies.
For Discrete sweeps, select Save Fields (All Frequencies) if you want to save the calculated
3D field solutions associated with all port modes at the chosen frequencies.
If want to save the fields for just one or a few Discrete sweep frequencies, click the Display
button to show a table of frequencies, and select Single Points from the Type pull-down list.
This disables the Save Fields checkbox for the entire sweep, and adds a Save Fields column
with a checkbox for each frequency. You can select the Save Fields check box for the desired
frequency, or click the Save Fields column header to check or uncheck all frequencies.
For Discrete sweeps, HFSS always solves the frequencies from highest to lowest.
Related Topics
Specifying Frequency Points to Solve
Specifying Single Frequency Points
Deleting Frequency Points
Insert Frequency Points
Change the Value of an Existing Frequency Point
Specifying Frequency Points to Solve
To view a table of the frequencies and count, click the Display button. If the list of frequencies
is longer than the visible display, you can use a scroll bar to view the list to the end of the
count.
5. For Fast sweeps, select Save Fields if you want to save the calculated 3D field solutions asso-
ciated with all port modes at the chosen frequencies.
For Discrete sweeps, select Save Fields (All Frequencies) if you want to save the calculated
3D field solutions associated with all port modes at the chosen frequencies.
If want to save the fields for just one or a few Discrete sweep frequencies, click the Display
button to show a table of frequencies, and select Single Points from the Type pull-down list.
This disables the Save Fields checkbox for the entire sweep, and adds a Save Fields column
with a checkbox for each frequency. You can select the Save Fields check box for the desired
frequency, or click the Save Fields column header to check or uncheck all frequencies.
For Discrete sweeps, HFSS always solves the frequencies from highest to lowest.
Related Topics
Specifying Frequency Points to Solve
Specifying Single Frequency Points
Deleting Frequency Points
Insert Frequency Points
Change the Value of an Existing Frequency Point
Specifying Frequency Points to Solve
Related Topics
Specifying Frequency Points to Solve
Specifying Single Frequency Points
Deleting Frequency Points
Insert Frequency Points
Change the Value of an Existing Frequency Point
Specifying Frequency Points to Solve
Related Topics
Change the Value of an Existing Frequency Point
Deleting Frequency Points
Insert Frequency Points
Specifying Frequency Points to Solve
Change the Value of an Existing Frequency Point
To change the value of an existing frequency point in a discrete sweep in the Edit Sweep dialog:
1. Click the Display button in the Edit Sweep dialog to show the frequency and count table for
the sweep. If the list of frequencies is longer than the visible display, you can use a scroll bar to
view the list to the end of the count.
2. Select Single Points from the Type pull-down list in the Edit Sweep dialog.
The Frequency setup changes to single point mode.
3. Either select the text field in the Frequency column and edit an existing value field directly, or:
a. Edit the value in the Single Text box.
b. Select the Frequency row that you want to change.
This enables the Change button.
c. Click the Change button to replace the selected Frequency row value with the Single Text
box value.
4. Select Save Fields if you want to save the calculated 3D field solutions associated with all port
modes at that frequency.
5. Repeat for changing additional points.
Related Topics
Specifying Single Frequency Points
Deleting Frequency Points
Insert Frequency Points
Specifying Frequency Points to Solve
the Display button to list the count and frequency of those points as a table. For longer fre-
quency tables, you can use a slider bar to scroll to through the complete list to see counts and
values.
2. Select Single Points from the Type pull-down list.
The Frequency setup changes to single point mode. If you previously specified a range of fre-
quency points, and clicked the Display button, the frequency table retains those points. This
selection also enables the Insert button between the Frequency setup and the frequency table.
The frequency points table now includes another column that contains a Save Field checkbox
for each row.
Note that selecting a row highlights it and enables the Delete button under the Insert button.
Clicking the cursor in the Frequency columns of the frequency points table makes their values
editable.
3. In the Single text box, type a desired frequency point in the frequency units.
This enables the Insert and Change button.
4. Click Insert.
This inserts the new point in ascending order for the list and the count for each row adjusts.
Clicking Change would replace the frequency value in the selected row.
5. Select the Save Fields column header if you want to save the calculated 3D field solutions
associated with all port modes at that frequency. You can also select, or deselect the checkbox
to specify individual frequencies.
6. Add or edit additional frequency points, and then click OK to save the sweep.
For Discrete sweeps, HFSS always solves the frequencies from highest to lowest.
Related Topics
Specifying Single Frequency Points
Deleting Frequency Points
Change the Value of an Existing Frequency Point
Specifying Frequency Points to Solve
τ
Δt = ------
Nτ
where
• Δt is the time sampling increment.
• τ is the signal rise time.
• Nτ is the number of time steps per signal rise time.
4. Type a value in the Number of Time Points box.
Note that the input time signal duration is determined using N × Δt , where N is the number of
time points.
5. Click Calculate.
• HFSS now determines the Maximum Frequency using
0.5
F max = -------
Δt
Warning Occasionally, HFSS can fail to solve for the minimum frequency during a Discrete
or Interpolating frequency sweep due to a failure of the port solver to converge. If
this happens, try to increase the minimum frequency until the solution process
completes successfully. However, the minimum frequency should be as low as
possible because the low-frequency response determines the steady-state time
response.
• The suggested frequency sweep ranges are estimates. You may have a pulse with a wider
frequency content and HFSS’s recommended frequency sweep range may miss some of
the high frequencies.
Requirements for Full-Wave SPICE
The Full-Wave Spice requirements are as follows:
1. The design problem type in which the solution data panel is opened must be driven terminal.
2. In the Matrix Data panel, for non-imported data, the view type for the solution data must be
"Terminal Data" (not "Modal Data").
3. The data must be interpolating, or it must be discrete.
4. If the data is discrete:
a. It must either be native terminal data, or it must be inferred as terminal. For instance, in a
Touchstone file, the comment line "! Terminal data exported" will cause HFSS to interpret
the data as terminal, while the comment line "! Modal data exported" will cause HFSS to
interpret the data as modal. If HFSS finds neither comment line, it assumes that the data is
terminal.
b. At least 20 frequency points must be provided.
c. HFSS must be able to generate an interpolation basis that converged with <= 0.5% error
using no more than 100 basis elements.
Note The Iterative solver doesn't go off-core for efficiency reasons. Because the Desired RAM
Limit (the soft memory limit) is used for off-core run, it is not appropriate for the
iterative solver. Instead, the iterative solver uses the Maximum RAM Limit (the hard
memory limit). Once the limit is exceeded, iterative solver will issue an "Out of
memory" error message.
Regardless of this setting, processes are limited to 2GB of address space (3GB with appropriate
operating system and boot settings) on 32 bit operating systems and 4TB of address space on 64 bit
operating systems - no matter how much physical memory is installed. See Increasing PC RAM.
Note Regardless of the Desired RAM Limit setting, if allocation fails, the HFSS solver will
automatically switch to off-core mode.
In case you receive an error message regarding insufficient memory on a 64-bit operating system,
you may have reached a point where the sum of physical RAM plus available swap space exceeds
the minimum amount of RAM needed by the off-core solver. Even for the off-core solver, the RAM
usage cannot be made arbitrarily small. In that case you can consider increasing the swap space (the
virtual memory) in the settings of your system.
To specify the Desired RAM Limit of the machine on which HFSS is installed:
1. Click Tools>Options HFSS Options.
2. Click the Solver tab.
3. Select Desired RAM Limit (MB).
4. Type a value for the amount of available memory, in megabytes, in the text box. This setting
affects all HFSS projects for the current user and machine.
Note Ansoft recommends that you use the Desired RAM Limit setting if you wish to limit the
RAM that the MPS (default) solver may allocate. However, the Iterative solver doesn't
go off-core for efficiency reasons. Because the Desired RAM Limit (the soft memory
limit) is used for off-core run tt is not appropriate for the iterative solver. Instead, the
Maximum RAM Limit (the hard memory limit) is used. Once the limit is exceeded,
iterative solver will issue an "Out of memory" error message.
Note Allocation of greater than 2 GB of RAM on 32-bit hardware platforms is only possible
with the appropriate operating system and boot settings, even if more than 2 GB are
physically installed. See Increasing PC RAM.
After you specify how HFSS is to compute the solution, you need to begin the solution process. In
general, the Analyze command applies to the selected setup and associated sweeps, if any, or to a
select sweep. To use this command, right-click on a setup or sweep in the Project tree, and click the
command on the context menu. The Analyze All command applies to all enabled setups, dependent
setups, and sweeps at or below the level invoked in the Project tree. To use this command, either
click HFSS>Analyze All or right-click on the Analysis icon in the Project tree and select Analyze
All from the popup menu.
What do you want to do?
• Solve a single setup with or without sweeps
• Solve a specific sweep
• Enable a queue so that multiple simulations can run sequentially as resources become avail-
able.
• Run more than one simulation, whether multiple setups, or multiple sweeps under a single
setup, or setups with dependencies.
• Monitor queued simulations
• Configure and run remote analysis
• Configure and run distributed analysis
• Monitor the solution process
• Change a solution priority for system resources
• Abort an analysis
• Re-solve after modifying a design
• Re-solve after ANSYS Thermal Link Feedback
Related Topics
Running an Optimetrics Analysis
HFSS computes the 3D field solution inside the structure for a solution, and for a select
sweep, does so for the sweep variables.
To run more than one analysis at a time, follow the same procedure while a simulation is running. If
you have enabled queuing, the next solution setup will be solved when the previous solution is
complete.
Note If a linked dependency in the setup is already simulating (for example, due to setup links
to the same external source for a near or far field wave, or a magnetic bias), HFSS will
not allow another dependent simulation to start until the first use of the source has
completed.
Related Topics
Running an Optimetrics Analysis
Running Simulations14-3
HFSS Online Help
The example here show an analysis invoked from the Project tree popup menu with three setups,
one disabled, two enabled. The first setup has one sweep enabled, and one disabled (greyed
icon).The second setup is disabled, and the third is enabled, with a disabled sweep.
Note The General tab for the Setup includes an “Enabled” checkbox. By default, this is
checked. Unchecking the Enabled checkbox excludes a setup from running
To solve two or more sweeps or two or more parametric analyses under a setup:
1. In the project tree, under the design you want to solve, right-click the setup icon that includes
the sweeps of interest.
2. Click Analyze on the shortcut menu.
Each solution sweep under that setup is solved in the order it appears in the project tree, using
the available machines. The example below shows a setup with two enabled sweeps.
Related Topics
Technical Notes: The Solution Process
Technical Notes: Handling Complicated Models
Solving a Single Setup
Specifying the Analysis Options
Remote Analysis
Monitoring the Solution Process
Aborting Analysis
Running an Optimetrics Analysis
Running Simulations14-5
HFSS Online Help
Remote Analysis
It is possible to solve a project on a different machine from the one on which you are running
HFSS. This is particularly useful when you want to take advantage of a more powerful machine but
it is not convenient to access that machine. This process involves configuring the machine that is to
perform the solving (the remote machine), as well as the machine from which the simulation is to
be launched (the local machine). This can also be extended into distributed analysis, where a speci-
fied analysis, if supported, is concurrently solved on multiple machines.
Local Machine Remote Machine
Note Communication between machines in remote analysis and distributed analysis can
drastically affect performance. Use of a high-speed network system, like Gigabit or
Infiniband, is recommended for optimal performance.
Running Simulations14-7
HFSS Online Help
2. HFSS must be accessible from all remote machines as well as accessible on the local machine.
3. If you use RSM, it must be accessible from all remote machines. In addition, the HFSS engines
must be registered with each initialization of RSM. To do this, on each remote machine:
• On Windows on the local and remote machines, click
Start>Programs>Ansoft>product >Register with RSM. You can also run
RegisterEnginesWith RSM.exe, located in the product subdirectory (for example,
C:\Program Files\Ansoft\hfss13\RegisterEnginesWithRSM.exe).
In each case, you see a dialog confirming the registration. OK the dialog.
• On Linux, run RegisterEnginesWithRSM.pl, located in the product installation direc-
tory. (for example, /apps/ansoft/hfss13/RegisterEnginesWithRSM.pl).
If the RSM service cannot run due to permission issues for the configuration file, it issues an error
message and exits. If your product is not registered with RSM, the analysis will run locally.
Configuring the Local Machine to Solve Remotely
1. Set the Analysis options in HFSS by clicking Tools>Options>General Options to display the
General options dialog, and select the Analysis Options tab.
• Distributed: This option allows you to specify a machine list. See Configuring Distributed
Analysis
To override the machine that you use on a per analysis basis, check Prompt for analysis
machine when launching analysis.
Checking this selection displays the following dialog when you run a simulation.
You select either the local machine, or specify a machine name. You can Save Settings as
Default.
Remote Analysis Options
You also set the Remote Analysis Options in the General options dialog, RSM Service Options
tab.
Select whether to run simulation processes as the user running RSM (Service User), or a Specified
User. If you select Specified user, you must provide the User Name, Password, and any Domain/
Workgroup on which this user is defined. If the name or password is incorrect, the Message win-
dow issues a warning message, and the solver attempts to perform the analysis as the Service User.
Running Simulations14-9
HFSS Online Help
Troubleshooting
Problem: When you try to solve from local to remote machine, an HFSSCOMENGINE process
starts on the remote machine, but the HFSS user interface hangs indefinitely.
This occurs if the remote solve option is enabled after the COM daemon is started, or when the
option "Don't allow exceptions" is selected for the Windows firewall.
Resolution: Remote solve needs either firewall exceptions to be ON or firewall to be completely
turned off.
Problem: When you try to solve from a local to a remote machine, you receive the following error
message:
[error] Unable to locate or start COM engine on 'nomachine' : Unable to reach AnsoftRSMService.
Check if the service is running and if the firewall allows communication. (10:57:13 PM Aug 13,
2009)
Resolution: This message can happen if the machine is not present, the network connection is
down, if there are firewall issues or if the service is not running.
the service and choosing Start. If it still does not start, then check the username/password com-
bination listed in the Log On tab of the service properties.
5. Make sure the user listed in the service is an administrator.
6. Make sure the COM engine is registered with the Ansoft RSM Service. From the Windows
menu, choose Start>All Programs >Ansoft>HFSS 13>Register with RSM to register the
engines.
Error: "Unable to locate or start COM engine on <remote node>: Engine is not registered with the
Ansoft RSM service which is running on this machine."
a. To register the engine, from the Windows menu, select Start >All Programs >Ansoft >
HFSS 13 > Register with RSM
Error: "Unable to locate or start COM engine on <remote node>: Engine is not registered with the
Ansoft RSM service which is running on this machine."
1. To register the engine, go to the Ansoft product installation directory and type:
./RegisterEnginesWithRSM.pl add.
Running Simulations14-11
HFSS Online Help
Distributed Analysis
Distributed analysis allows users to split certain types of analyses and solve each portion of an anal-
ysis simultaneously on multiple machines. Simulation times can be greatly decreased by using this
feature.
HFSS and HFSS-IE support three forms of distributed analysis:
• Distributing rows of a parametric table.
• Distributing domain solves
• Distributing a single or discrete interpolating sweep.
Note Communication between machines in remote analysis and distributed analysis can
drastically affect performance. Use of a high-speed network system, like Gigabit or
Infiniband, is recommended for optimal performance.
Related Topics
Configuring Distributed Analysis
Editing Distributed Machine Configurations
HFSS Options: Solver Tab
Selecting an Optimal Configuration for Distributed Analysis
Configuring Distributed Analysis
To configure distributed analysis you select a distributed machine configuration. This is a list of
machines to use for a simulation, based considerations such as whether the simulation is more
memory intensive or more CPU intensive, relative to the resources available on your network. (See
Selecting an Optimal Configuration for Distributed Analysis for a discussion of issues.) To create
an new distributed machine configuration. or to edit and existing one, see Editing Distributed
Machine Configurations.
To select from an existing configuration:
1. Click HFSS and HFSS-IE>Tools>General Options to display the General Options dialog
and select the Analysis Options tab.
2. Select the Analysis Options tab, and under the Analysis Machine Options, click the Distrib-
uted radio button.
This displays the field for selecting configurations. If no list has been selected or created, the
field is blank. If you have previously created distributed machine configurations, click the field
When you have made a selection, the lower field shows the enab led machines in the configu-
ration.
Running Simulations14-13
HFSS Online Help
This displays the Distibuted Machines Configurations dialog. This lists existing configura-
tions, and shows all machines in the selected configuration, enabled or not. Here you can Add
a new configuration, Edit an existing configuration, Delete a selected configuration, or Clone
an existing configuration, typically to edit the name and contents for other purposes.
4. To create a new configuration, click Add configuration.
This opens the Distributed Analysis Machines dialog. Clicking Edit or Delete also open the
Distributed Analysis Machines dialog, but include the entries for the selected configuration.
Here you can edit the configuration name, view, add, remove, order, test, and enable machines
on the list.
5. Specify the name of the configuration. It cannot be empty and cannot be a previously used
name or a reserved word.
6. For each machine to manually add to the list, under Remote Machine details, specify an IP
address, a DNS name, or a UNC name. You can also use Import Machines from File... to use
a text file to simplify the process.
Control buttons let you Add machine to list (see figure above) or Remove (see figure below)
machines from the list.
Each machine on the current list has an Enabled checkbox. Here you can enable or disable the
listed machines according to circumstance. Above the table, the dialog gives a count of the
In general, HFSS and HFSS-IE use machines in the distributed analysis machines list in the
order in which they appear. If Distributed is selected and you launch multiple analyses from
the same UI, HFSS and HFSS-IE select the machines that are running the fewest number of
engines in the order in which the machines appear in the list. For example, if the list contains 4
machines, and you launch a simulation that requires one machine, HFSS chooses the first
machine in the list. If another simulation is launched while the previous one is running, and
this simulation requires two machines, HFSS chooses machines 2 and 3 from the list. If the
first simulation then terminates and we launch another simulation requiring three machines,
HFSS chooses 1, 4, and 2 (in that order).
The displayed list always shows the order in which you entered them irrespective of the load
on the machines. To control the list order, select one or more machines, and use the Move up
or Move down buttons. Move up and Move down are enabled when you select one or more
adjacent machine names. Also, when you select one or more machine names, you will see a
text field underneath the grid control showing the first machine name, the number of times it
Running Simulations14-15
HFSS Online Help
7. Test Machines- When multiple users on a network are using distributed solve or remote solve,
they should check the status of their machines before launching a simulation to ensure no other
Ansoft processes are running on the machine. To do this, you can select one or more machines
and click the Test Machines button. A Test Machines dialog opens. The test goes through the
current machine list and gives a report on the status of each machine. A progress bar shows
how far testing has gone. An Abort button lets you cancel a test. When the test is complete, you
can OK to close the dialog. If you need to disable or Enable machines from the list based on
the report, you can do so in the Distributed Analysis Machines dialog.
8. Click OK to accept the changes and close the Distributed Analysis Machines dialog. Only
machines checked as Enabled appear on the distributed machines list in the Analysis tab.
Regardless of the machine(s) on which the analysis is actually run, the number of processors
and Desired RAM Limit settings, and the default process priority settings are now read from
the machine from which you launch the analysis. See HFSS Options: Solver Tab.
For more information, see distributed analysis.
Once configured, you can also control these selections via toolbar icons for:
Note The option is only active if there are multiple rows listed in the parametric table, there
are multiple frequency sweeps listed under a given analysis setup, and the number of
distributed analysis machines is two or greater.
Related Topics
Related Topics
Configuring Distributed Analysis
Editing Distributed Machine Configurations
Selecting an Optimal Configuration for Distributed Analysis
HFSS Options: Solver Tab
General Options: Analysis Options Tab
Selecting an Optimal Configuration for Distributed Analysis
With the distributed solve option (DSO) it is possible to assign more than one machine in the DSO
setup panel to a single computer - assuming the computer has multiple cores. For example, a quad
core computer can be listed 4 times in the DSO machine list and each CPU will run a separate sim-
ulation in the sweep. This raises the question of how to configure a distributed solution option
(DSO) in combination with the multiprocessing option to take optimal advantage of the available
hardware. The simplest answer is that for the overwhelming majority of situations the speed
improvement will be greater if additional machines are added to a DSO than if the same CPU’s are
added as multiple processors. That simple answer assumes that there is enough memory for the
DSO simulations.
For multiple DSO simulations on a single machine the total memory needed is the sum of the mem-
ory used by each simulation. For example, assume we are running discrete frequency sweep and
each frequency point needs 3.5GB. Our computer has only 8GB of RAM but is a quad core system.
To keep the computer from going heavily into swap, which is highly inefficient, we would only
want to assign this computer twice to the list of machines in the DSO setup. To take advantage of
the remaining 2 CPU’s then it would make sense to set the number of distributed processors to 2.
(HFSS Options: Solver Tab). This would be the optimum for this setup. In addition one would need
to be sure that the amount of disk space available is also sufficient to fit all the requested simula-
tions - typically hard drive space is not the limiting factor.
Related Topics
Configuring Distributed Analysis
Editing Distributed Machine Configurations
HFSS Options: Solver Tab
General Options: Analysis Options Tab
Running Simulations14-17
HFSS Online Help
Note If HFSS loses its license, it waits for the license to be regained, checking every 2 minutes
or until you abort.
Related Topics
Aborting Analysis
Deleting Solution Data
Post Processing and Generating Reports
14-18 Running Simulations
HFSS Online Help
Creating Reports
Modifying Reports
Creating a Quick Report
Plotting the Mesh
Plotting Field Overlays
Running Simulations14-19
HFSS Online Help
Running Simulations14-21
HFSS Online Help
Head node(s) typically maintains queues. Compute nodes are typically on a high speed network, to
improve scalability of parallel jobs. Services running on nodes interact with each other to manage
resources. End user tools communicate with services to submit/abort/suspend/etc. jobs.
Related Topic
High Performace Computing (HPC) Integration
Command Line Enhancements for Ansoft Desktop Products
Installation of Ansoft Tools
Ansoft Tools must be available on each cluster host where Ansoft jobs may be run.
• On LINUX platform, Ansoft tools may be installed on a shared drive, that is accessible to all
machines in the cluster.
• On Windows platform, Ansoft tools must be installed separately on each host of the cluster.
The Ansoft tools must be accessible using the same path on each host. All cluster users running
Ansoft jobs must have permission to read and execute the files in the Ansoft installation directory
and its subdirectories.
The Temp directory selected during installation must be readable and writable by all user accounts
used to run the Ansoft tools. This temp directory path should be the same on all machines of the
cluster and should be local to every machine. For example, c:\temp on Windows, /tmp on LINUX
Because HPC is offered as a direct integration, you need only install the Ansoft software programs.
No additional configuration is required.
Example
Install the Ansoft tools in directory C:\Program Files (x86)\Ansoft\HFSS13.0 on each node of the
cluster. The same directory pathname must be used on all hosts.
Related Topics
High Performance Computing (HPC) Integration
Firewall Configuration
Installation Directory Examples
Firewall Configuration
If firewall is turned OFF between the machines of the cluster, there is no need for any configura-
tion. If firewall is turned ON, you, or a system administrator, should perform the steps below.
• Windows cluster: Configure firewall by adding exceptions that allow Ansoft programs and ser-
vices to communicate with each other. If you are using standard Windows Firewall, this is
automatically done for you, by the Ansoft installation program. On the other hand, if you are
using a 3rd-party firewall software, it needs to be configured in a similar manner.
• LINUX cluster: Open up the firewall for range of ports denoting ephemeral (or dynamic)
ports. Check with your system administrator on how this can be done on each machine of clus-
ter.
Related Topics
High Performance Computing (HPC) Integration
Installation Directory Examples
Installation Directory Examples
Microsoft Windows Example
Install the Ansoft tools in directory C:\Program Files (x86)\Ansoft\HFSS13.0 on each node of the
cluster. The same directory pathname must be used on all hosts.
LINUX Example
Install the Ansoft tools in a common directory that is accessible using the path /opt/ansoft/hfss13 on
each execution node of the cluster.
Related Topics
High Performance Computing (HPC) Integration
Firewall Configuration
Ansoft Jobs
Ansoft Jobs
For most cluster environments, an Ansoft job will consist of an Ansoft Desktop running in non-
graphical mode, performing a batch solve. The user will submit the job to the scheduler, specifying
an Ansoft Desktop command line to be executed on the cluster. For some schedulers, the user may
Running Simulations14-23
HFSS Online Help
or must specify a script to run instead of specifying the Ansoft Desktop command line; in these
cases, the script will contain the corresponding Ansoft Desktop command line. When the resources
requested for the job are available to the job, the scheduler will start the job. In many cases, the user
submitting the job will not know which host or hosts are allocated to the job. With direct integra-
tion, if the Ansoft job is a distributed job, the Ansoft Desktop will query the scheduler for the hosts
allocated to the job, and it will use the scheduler facilities to launch the distributed engines.
Related Topics
High Performance Computing (HPC) Integration
Running HFSS from a Command Line
Integration with Microsoft Windows® HPC Scheduler
General Guidelines for Submitting Ansoft Jobs
A Job submitted to Windows HPC Cluster is defined by Job properties, Task List and Task proper-
ties. Priority, resource requirements, node preferences, etc. come from Job properties. In the case of
Ansoft jobs, Task List consists of a single task. Properties of this task specify command line that
runs Ansoft Desktop in non-graphical mode to perform analysis of an Ansoft project.
Ansoft Project File and Project Directory for use with Windows HPC Scheduler
Ansoft tools write their results to a subdirectory of the directory containing the Ansoft project file.
The Project Directory (the directory containing the project file) must be accessible to all of the clus-
ter hosts that may run Ansoft jobs. The user account for the job must have permission to read the
project directory, and to create and modify files and subdirectories of this directory. The pathname
of the project file must be accessible to all cluster hosts using the same path name, which is gener-
ally expressed as a UNC pathname.
Example:
The project file is on the user’s workstation (with hostname user1_PC) in directory C:\user1\proj-
ects\new\project1.hfss, and the directory C:\user1\projects is shared with sharename projects.
Correct
When submitting the job, you should use the following pathname to specify the project file:
\\user1_PC\projects\new\project1.hfss
Incorrect
If a local pathname is used, the cluster hosts will not be able to find the user’s project on the work-
station
user1_PC: ' C:\user1\projects\new\project1.hfss '
Related Topics
Integration With Microsoft Windows® HPC Scheduler
Windows® HPC Job Properties
Windows® HPC Task Properties
Windows® HPC Job Templates
14-24 Running Simulations
HFSS Online Help
Running Simulations14-25
HFSS Online Help
node of 2000 MB ensures that nodes allocated to the current job have at least 2000 MB of memory.
A node with 2000 MB of memory may be allocated to the current job, even if another job running
on the node is using 1500 MB of memory, however.
There are several other job properties that are not described here. See the Microsoft documentation
for more details.
Related Topics
Integration With Microsoft Windows® HPC Scheduler
Windows® HPC Job Properties
Windows® HPC Task Properties
Windows® HPC Job Templates
Selecting Computation Resource Units (Job Unit Type)
How to Select the Windows® HPC Job Unit Type
Windows® HPC Job Credentials
High Performance Computing (HPC) Integration
Windows® HPC Task Properties
In general, each job consists of one or more tasks. For Ansoft batch analyses run as Windows HPC
jobs, the job contains one task to control the analysis. This task is equivalent to the Ansoft Desktop
GUI, which controls the analysis when running in interactive mode. The properties of this task
must be set correctly for analysis to be successful.
Some of the main task properties are:
• Task Name - text string that may be used to identify or describe the task
• Working Directory - Working directory where the task is started
• Command Line - The command line executed to start the task
• Minimum and maximum number of computing resource units for the task (The unit type is the
same is the job unit type.)
Of these properties, the Command Line is particularly important. We recommend using the Ansoft
Submit HPC Job dialog to submit jobs because this dialog will assist you in creating a valid task
Command Line. If you use one of the other methods, you must specify the complete command line
for the Desktop task. See Setting the Command Line discussion below.
For Ansoft Jobs, all the compute resource requirements are specified at the job level. At the task
level, the minimum and maximum computing resource units should be set to one if the resource
unit is 'Node'. For any other resource unit, set the minimum/maximum resources units to the
amount of multi-processing per distributed engine, i.e. "Number of Processors, Distributed". The
Desktop task will start additional tasks and child process, if needed, to complete the analysis.
Setting the Command Line
The examples in this section use the HFSS product. The command lines for other products are sim-
ilar.
The task executable should be specified as described in the Installation of Ansoft Tools examples.
The project file should be the last argument in the command line, and it should be specified as
described in the Ansoft Project File and Project Directory examples. The other command line argu-
ments should be selected to start the analysis as a batch job.
For Ansoft Jobs, all the compute resource requirements are specified at the job level. At the task
level, the minimum and maximum computing resource units should be set to one, if the resource
unit is 'Node'. For any other resource unit, set the minimum/maximum resources units to the
amount of multi-processing per distributed engine i.e. "Number of Processors, Distributed". The
Desktop task will start additional tasks and child process, if needed, to complete the analysis.
Example Command Lines:
Command Line that analyzes an HFSS project serially:
"C:\Program Files (x86)\Ansoft\HFSS13\hfss.exe" -ng -local _
-batchsolve \\shared_drive\projs\OptimTee12.hfss
Command Line that analyzes HFSS project serially and monitors analysis progress that is printed to
stdout/stderr: "C:\Program Files (x86)\Ansoft\HFSS13\hfss.exe"_
-ng -monitor -local -batchsolve _
\\shared_drive\projs\OptimTee12.hfss
Command Line that uses four cores for multi-processing of analysis:
"C:\Program Files (x86)\Ansoft\HFSS13\hfss.exe" -ng -monitor _
-local -batchoptions _
"'Hfss/Preferences/NumberOfProcessors'=4" _
-batchsolve \\shared_drive\projs\OptimTee12.hfss
Command Line that runs four distributed engines, on compute units allocated by the HPC Sched-
uler:
"C:\Program Files (x86)\Ansoft\HFSS13\hfss.exe" -ng _
-monitor -distributed -machinelist num=4 _
-batchsolve \\shared_drive\projs\OptimTee12.hfss
Command Line that runs four distributed engines, with each engine using four cores for multi-pro-
cessing:
"C:\Program Files (x86)\Ansoft\HFSS13\hfss.exe" -ng -monitor_
-distributed -machinelist num=4 -batchoptions _
" 'Hfss/Preferences/NumberOfProcessorsDistributed'=4 _
'Hfss/Preferences/NumberOfProcessors'=4" -batchsolve _
\\shared_drive\projs\OptimTee12.hfss
Related Topics
Integration With Microsoft Windows® HPC Scheduler
Windows® HPC Job Properties
Running Simulations14-27
HFSS Online Help
Running Simulations14-29
HFSS Online Help
user. Here is a cluscfg command that may be used to set the user credentials in the credentials
cache:
cluscfg setcreds /password:* /scheduler:cluster_name _
/user:domain\user_name
Here:
• cluster_name = the name of the cluster (hostname of the head node)
• domain = optional domain name; if omitted, the following \ should also be omitted
• user = user name
When this form of the command is used, the user is prompted for the password and also asked if the
password should be remembered (cached).
See the following web page for more information on the cluscfg setcreds command:
http://technet.microsoft.com/en-us/library/cc947669(WS.10).aspx
Related Topics
Integration With Microsoft Windows® HPC Scheduler
Windows® HPC Job Properties
Windows® HPC Task Properties
Windows® HPC Job Templates
Selecting Computation Resource Units (Job Unit Type)
How to Select the Windows® HPC Job Unit Type
Windows® HPC Job Credentials
High Performance Computing (HPC) Integration
Submitting and Monitoring Ansoft HPC Jobs
Jobs may be submitted to the Windows HPC Scheduler using any of the following methods:
• Using the Ansoft Submit HPC Job dialog
• Using the Windows HPC Job Manager GUI
• Using the Windows HPC Command Line Tools
• Using the Windows PowerShell
Client Utilities from the Microsoft HPC Pack, must be installed on the submit host to use any of
these methods to submit a job to a cluster. The Ansoft Submit HPC Job dialog will be unable to
contact the cluster head node if the client utilities are not installed.
This document covers the first method. See the Microsoft documentation for information on the
other three methods.
• Submitting and Monitoring Jobs Using the Ansoft Submit HPC Job Dialog
• The Ansoft Submit HPC Job Dialog
• Specifying the Number of Compute Resource Units for HPC Jobs
Running Simulations14-31
HFSS Online Help
Submitting and Monitoring Jobs Using the Ansoft Submit HPC Job Dialog
In order to submit jobs using the Ansoft Submit HPC Job dialog, the cluster head node hostname
must be set. Selecting the Tools>Windows HPC>Select Head Node... menu item brings up the
Select Head Node dialog.
You can enter the cluster head node name into the dialog. Alternatively, you can click the ellipsis
[...] button to browse the network for the cluster had node.
After setting the cluster head node hostname, select Tools>Windows HPC>Submit HPC Job...
You can select which setups are analyzed in the Analyze Setups section of this dialog. There are
radio buttons to select:
• All setups in the project
Running Simulations14-33
HFSS Online Help
• All setups in a specified design: you selects the design from the dropdown list
• Specify setups: You add one or more setups using the Add Setups... dialog
If you specify multiple setups, they will be processed sequentially in the order displayed in the edit
box.
The Resource Requirements group box controls how compute resources are used. The Distributed
Analysis settings control resource usage for the portion of the analysis that may be distributed to
different hosts. The Non-Distributed Analysis settings control the initial portion of analysis that
runs before the start of any distributed analysis --this initial portion cannot be distributed to sepa-
rate hosts, and must be run on a single host.
There are two Distributed Analysis settings. The Number of engines is the number of analysis
engines that are started in parallel; the engines can run on separate hosts. The Number of cores per
engine setting controls the degree of parallel processing within each engine; these parallel threads
of execution must be on the same host. In the case of HFSS, each distributed engine represents one
domain of a large model, portion of a frequency sweep analysis or portion of an Optimetrics setup
analysis.
There is only one setting for the non distributed analysis because this part of the analysis must
occur on a single host. The Number of cores controls the degree of parallelism used for this part of
the analysis.
Check Log Analysis Progress to log analysis progress to a <projname.progress> file. A Progress
file contains error/warning/info messages and progress text. Progress text is added every two sec-
onds.
Pressing the Next button accepts the current settings, and advances to the Submit HPC Job: Prop-
erties dialog. Pressing the Cancel button dismisses the dialog without submitting the job.
Related Topics
Submitting and Monitoring Ansoft HPC Jobs
The Ansoft Submit HPC Job Dialog
Specifying the Number of Compute Resource Units for HPC Jobs
Running Simulations14-35
HFSS Online Help
• Set Compute resource granularity to core or socket (see How to Select the HPC Job Unit
Type).
• Set Node exclusivity to true.
• Set Number of compute resource units to the number of units that are for exclusive use by
this job.
• Specify an appropriate node list or the node groups via the Job description file.
Example: Suppose the job is run on nodes with 32GB of memory and 8 cores per node. Suppose
each engine requires 8GB memory and that 4 engines can run on each machine. Suppose the Num-
ber of engines specified for this job is 10. Since four engines are run per node, we need three nodes
to run 10 engines. So, 'Number of compute resource units' should be set to 24 cores (3 nodes times
8 cores). The Number of cores per engine should be set to 2.The Number of cores should be set to 8
(or a smaller number, if using 8 cores slows down the analysis)
For a job that is memory intensive. Run one engine per node:
• Set Compute resource granularity to Node
• Set Number of compute resource units to Number of engines.
• Specify appropriate node list or node groups via the Job description file.
Example: Suppose the job is run on nodes with 16GB of memory and 4 cores per node. Suppose
each engine requires 16GB memory, that is, 1 engine can run on each machine. Suppose the Num-
ber of engines specified for this job is 10. So, the Number of compute resource units should be set
to 10 nodes. The Number of cores per engine should be set to 4 (or a smaller number, if using 4
cores slows down the analysis). The Number of cores should be set to 4 (or a smaller number, if
using 4 cores slows down the analysis)
Related Topics
Submitting and Monitoring Ansoft HPC Jobs
Submitting and Monitoring Jobs Using the Ansoft Submit HPC Job Dialog
The Ansoft Submit HPC Job Dialog
Specifying the Number of Compute Resource Units for HPC Jobs
Integration with Platform’s Load Sharing Facility (LSF)
Ansoft products support Windows LSF cluster as well as LINUX LSF cluster. Serial analysis, Multi
Processing and Distributed Analysis is done on compute resource units assigned by LSF. With LSF,
the Ansoft job doesn't require graphics. Ansoft job’s progress can be monitored through LSF com-
mands. If a temp directory is setup by the LSF cluster administrator, analysis engines use this temp
directory, overriding the setting in the Ansoft product.
Related Topic
General Terminology for LSF
What a Scheduler Does
Installation of Ansoft Tools on LSF Cluster
Integration of Ansoft Products with LSF
Running Simulations14-39
HFSS Online Help
Desktop talks to Scheduler Proxy which in turn uses Scheduler commands. It is possible to add a
proxy dll to support new schedulers without changing Desktop.
Related Topic
Integration with Platform’s Load Sharing Facility (LSF)
General Terminology for LSF
What a Scheduler Does
Integration of Ansoft Products with LSF
LSF Job Submission Guidelines
Known Issues for LSF
Troubleshooting for LSF
Workarounds for LSF
Command Line Enhancements for Ansoft Desktop Products
Running Simulations14-43
HFSS Online Help
script pathname is placed in the bsub command line. Then, the hfss command is only processed by
the command processor when the job is started. When using this approach, the shell script should
be accessible from all of the cluster hosts.
Serial job:
bsub -n 1 /opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
~/projects/OptimTee.hfss
The -n 1 option indicates that this job runs on one core.
Serial job that needs a minimum of 4GB:
bsub -n 1 -R "select[mem>4000]" _
/opt/Ansoft/HFSS13/hfss13/hfss -ng _
-BatchSolve ~/projects/OptimTee.hfss
The -R "select[mem>4000]" option indicates that this needs a minimum of 4 GB memory.
Multi-processing job using 4 cores:
bsub -n 4 -R "span[ptile=4]" _
"/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
-batchoptions "\""'HFSS/Preferences/NumberOfProcessors'=4"\""_
~/projects/OptimTee.hfss"
• The -R "span[ptile=4]" option indicates that the four cores need to be on the same machine.
• The -batchoptions option indicates that HFSS should use four cores for multi-processing.
• The entire hfss command is in double quotes, and the double quotes enclosing the -batchop-
tions value are escaped. Each of these double quotes is replaced by the sequence "\"".
Distributed processing job using 4 engines:
bsub -n 4 /opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve -
Distributed ~/projects/OptimTee.hfss
• The -n 4 option indicates that the four cores are needed for the job.
• The -Distributed option indicates that this is a DSO job, so that multiple engines will be
started. Because 4 cores are allocated to the job, the job will run 4 engines.
Distributed processing and multi-processing job using 4 cores, with 2 cores for
multi-processing:
bsub -n 4 -R "span[ptile=2]" ~/projects/OptimTee.csh
Shell script (~/projects/OptimTee.csh):
#!/bin/csh
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
-Distributed -machinelist num=2 -batchoptions _
"'HFSS/Preferences/NumberOfProcessorsDistributed'=2_
Running Simulations14-45
HFSS Online Help
'HFSS/Preferences/NumberOfProcessors'=2" ~/projects/
OptimTee.hfss
• The -n 4 option indicates that the four cores are needed for the job.
• The -R "span[ptile=2]" option indicates that the cores must be allocated in groups of two
cores on the same machine.
• The -machinelist num=2 option indicates that this is a DSO job and that a total of two engines
will be started.
• The 'HFSS/Preferences/NumberOfProcessorsDistributed=2 batchoption indicates that the
distributed analysis engines should use two cores for multi-processing.
• The 'HFSS/Preferences/NumberOfProcessors=2 batchoption indicates that the portion of
the analysis that is not distributed should use two cores for multi-processing.
• The hfss command is placed in the shell script (~/projects/OptimTee.csh). In the bsub com-
mand line, the hfss command is replaced by the shell script pathname.
Windows Examples for LSF
If the hfss command is included in the bsub command line, then the entire hfss command will be
processed by the command processor cmd.exe two times. The hfss command is processed when the
bsub command is processed by the command processor. It will be processed again when the hfss
command is started by the scheduler.
The first three examples show the entire hfss command line enclosed in double quotes ("), while the
double quote (") characters within the hfss command line are replaced by escaped double quotes
(\"). This ensures that the quoted arguments of the hfss command are processed correctly. The
remaining examples show how to use a batch file so that the hfss command line will be processed
by the command processor only once. The hfss command is placed in a batch file, and then the
batch file pathname is placed in the bsub command line. Then, the hfss command is only processed
by the command processor when the job is started. When using this approach, the batch file should
be accessible from all of the cluster hosts.
Serial job:
bsub -n 1 "\"C:\Program Files\Ansoft\HFSS13\hfss.exe\" _
-Ng -BatchSolve \\host\share\projects\OptimTee.hfss"
• The -n 1 option indicates that this job runs on one core.
• The entire hfss command is in double quotes, and the double quotes enclosing the hfss path-
name are escaped. Each of these double quotes is replaced by the sequence \".
Serial job that needs a minimum of 4GB:
bsub -n 1 -R "select[mem>4000]" _
"\"C:\Program Files\Ansoft\HFSS13\hfss.exe\" _
-Ng -BatchSolve \\host\share\projects\OptimTee.hfss"
• The -R "select[mem>4000]" option indicates that this needs a minimum of 4 GB memory.
• The entire hfss command is in double quotes, and the double quotes enclosing the hfss path-
name are escaped. Each of these double quotes is replaced by the sequence \".
Multi-processing job using 4 cores:
bsub -n 4 -R "span[ptile=4]" _
"\"C:\Program Files\Ansoft\HFSS13\hfss.exe\"_
-Ng -BatchSolve -batchoptions _
\"'HFSS/Preferences/NumberOfProcessors'=4\" _
\\host\share\projects\OptimTee.hfss"
• The -R "span[ptile=4]" option indicates that the four cores need to be on the same machine.
• The -batchoptions option indicates that HFSS should use four cores for multi-processing.
• The entire hfss command is in double quotes, and the double quotes enclosing the hfss path-
name and the -batchoptions value are escaped. Each of these double quotes is replaced by the
sequence \".
Distributed processing job using 4 engines:
bsub -n 4 \\host\share\projects\OptimTee.bat
Batch File (\\host\share\projects\OptimTee.bat) Contents:
"C:\Program Files\Ansoft\HFSS13\hfss.exe" _
-Ng -BatchSolve _
-Distributed \\host\share\projects\OptimTee.hfss
• The -n 4 option indicates that the four cores are needed for the job.
• The -Distributed option indicates that this is a DSO job, so that multiple engines will be
started. Because 4 cores are allocated to the job, the job will run 4 engines.
• The hfss command is placed in the batch file \\host\share\projects\OptimTee.bat. In the bsub
command line, the hfss command is replaced by the batch file pathname.
Distributed processing and multi-processing job using 4 cores, with 2 cores for
multi-processing:
bsub -n 4 -R "span[ptile=2]" \\host\share\projects\OptimTee.bat
Batch File (\\host\share\projects\OptimTee.bat) Contents:
"C:\Program Files\Ansoft\HFSS13\hfss.exe" -Ng _
-BatchSolve -Distributed -machinelist num=2 -batchoptions_
"'HFSS/Preferences/NumberOfProcessorsDistributed'=2 _
'HFSS/Preferences/NumberOfProcessors'=2" _
\\host\share\projects\OptimTee.hfss
• The -n 4 option indicates that the four cores are needed for the job.
• The -R "span[ptile=2]" option indicates that the cores must be allocated in groups of two cores
on the same machine.
Running Simulations14-47
HFSS Online Help
• The -machinelist num=2 option indicates that this is a DSO job and that a total of two engines
will be started.
• The 'HFSS/Preferences/NumberOfProcessorsDistributed=2 batchoption indicates that the dis-
tributed analysis engines should use two cores for multi-processing.
• The 'HFSS/Preferences/NumberOfProcessors=2 batchoption indicates that the portion of the
analysis that is not distributed should use two cores for multi-processing.
• The hfss command is placed in the batch file \\host\share\projects\OptimTee.bat. In the bsub
command line, the hfss command is replaced by the batch file pathname.
Known Issues for LSF
• Desktop or remote machine has multiple IP addresses, which we don’t support.
• HFSS 12.1 is able to perform DSO on 2 machines or lesser. Fails to DSO to 3 or more
machines
• There are core dump files at the end of job’s running. Results are computed correctly though
• HFSS 12.1 doesn’t work with LSF versions 7.0.2 and 7.0.3
• On Windows, HFSS should be installed on every machine of cluster
• Firewall should be turned off on the machines in the cluster
• UAC should be disabled on Vista (only Windows)
• Sometimes LSF kills an HFSS job (for e.g. job gets preempted due to a high priority job).
HFSS doesn't handle such a situation gracefully resulting in the presence of .lock file in the
project directory. User needs to manually delete the lock file before continuing with further
analysis.
• When an LSF job is killed, the MainWin services (watchdog, regss, and mwrcpss) could keep
running. The result is that later jobs cannot start on the machine. The fix is to kill off these pro-
cesses before starting a new job
• Statistics monitoring:
HFSS 12.0: In the case of DSO job, LSF doesn't report the job statistics correctly. The statistics
reported correspond to the machine on which HFSS is launched and doesn't take into account
the resources consumed on other machines. (will be fixed in HFSS 12.1)
HFSS 12.1: (LINUX only): Statistics are reported correctly even for DSO jobs (as long as the
LSF installation supports ‘blaunch’ command)
• Analysis fails abruptly when running out of resources (cpu/memory/disk)
The major reason for job failure is due to insufficient resources given to job
Issue is addressed (via graceful failure) in the next release of Ansoft products
Related Topics
Integration with Platform’s Load Sharing Facility (LSF)
General Terminology for LSF
What a Scheduler Does
Installation of Ansoft Tools on LSF Cluster
14-48 Running Simulations
HFSS Online Help
Running Simulations14-49
HFSS Online Help
• For each machine in the network, dump the network interfaces (for e.g. run "ifconfig -a") and
note the output
• Email all 5 logs to development
- Job’s log generated by LSF
- Log generated by Ansoft product
- Entire \\shared_drive\ansdebug folder
- Output from ping command
- Output related to compute node’s network interfaces
Related Topics
Workarounds for LSF
Integration with Platform’s Load Sharing Facility (LSF)
General Terminology for LSF
What a Scheduler Does
Installation of Ansoft Tools on LSF Cluster
Integration of Ansoft Products with LSF
LSF Job Submission Guidelines
Known Issues for LSF
Command Line Enhancements for Ansoft Desktop Products
Aborting an Analysis
Workarounds for LSF
• Some users reported ‘core’ dumps during HFSS analysis, though analysis results are fine.
Workaround: Limit size of core dumps to 0 through the following job submit option:
bsub -C 0 -n <number-of-cores> -q <queue-name>
• HFSS 12.1 is able to perform DSO on 2 machines or lesser. Fails to DSO to 3 or more
machines.
Workaround: Set per-thread stacksize to 10MB
• HFSS 12.1 doesn’t work with LSF versions 7.0.2 and 7.0.3.
Workaround: Copy scheduler dll from HFSS12 (LSF 7.0.3, LSF 7.0.2 issue)
• Check if latest 12.1 patch has the fixes for the above issues.
Related Topics
Integration with Platform’s Load Sharing Facility (LSF)
Integration with PBS (Portable Batch System) Professional from Altair
Engineering
Submitting Ansoft PBS Batch Jobs
The PBS qsub command may be used to submit Ansoft batch jobs. The typical command format is:
qsub qsub_args script
where:
• qsub_args are the options of the qsub command,
• script is the pathname of the job script.
The job script is a shell script containing the Ansoft batch command or commands to be run. If a
batch command line contains any characters that are special to the shell running the script, then
these special characters should be quoted, as needed. The job script may also contain PBS direc-
tives on lines before the first executable line of the script. Any qsub options on the command line
will take precedence over the PBS directives in the job script.
When a PBS batch job is started, the job script runs as the job user in a new shell. In this shell envi-
ronment, the path must include the directory containing the PBS commands. You should ensure that
the path set in the shell startup script, i.e., .cshrc, .profile, .bashrc, etc. includes the directory con-
taining the PBS commands.
Serial PBS Batch Jobs
In the PBS documentation, serial batch jobs are also called single-node jobs. In general, any job
submitted without specifying the -l nodes=value command line argument, will run as a serial or sin-
gle-node job.
See the section on Monitoring Ansoft PBS Batch Jobs for options that can facilitate monitoring of
Ansoft batch jobs.
Parallel PBS Batch Jobs
In the PBS documentation, parallel batch jobs are also called multi-node jobs. When an Ansoft
batch job is run as an PBS parallel job, the PBS scheduler will select the hosts for the distributed
analysis job based on the qsub command line arguments, the PBS resource directives from the job
script, and the status of the hosts when the job is run. The desktop process will be started on one of
these hosts. The desktop process will obtain the list of hosts allocated to the job from the PBS
scheduler, and start analysis processes on these hosts, as needed, using the PBS scheduler facilities.
To run a PBS parallel job, the job must be submitted with a -l nodes=value qsub command line
argument or with a -l nodes=value PBS directive in the job script.
See the section on Monitoring Ansoft PBS Batch Jobs for options that can facilitate monitoring of
Ansoft batch jobs.
Related Topics
Monitoring Ansoft PBS Batch Jobs
Example PBS qsub Command Lines
Example PBS qsub Command Lines
What a Scheduler Does
Running Simulations14-51
HFSS Online Help
qsub Arguments
The PBS qsub command has a large number of options for control of the submission process. In
this section, we review the -l nodes=value command line option with Ansoft parallel batch jobs.
This option or directive has the following format:
-l nodes=node_spec [+node_spec...][#suffix]
where node_spec is one of the following
nodename[:pc_spec[:pc_spec...]]
Host name of the specified node, followed by optional ppn or cpp specifiers.
[N][:property[:property...]][:pc_spec[:pc_spec...]]
Optional number of nodes, followed by optional node properties, followed by optional
ppn or cpp specifiers. If the number N is omitted, then the default value of 1 host is used.
Here, the optional ppn or cpp specifiers pc_spec are of form:
ppn=X
Number of processes (tasks) per node. Default is 1 if not specified.
cpp=Y
Number of CPUs (threads) per process. Default is 1 if not specified.
The optional global suffix, #suffix, which applies to all hosts has one of the following values:
#excl
This suffix requests exclusive access to the allocated nodes.
#shared
This suffix requests shared (i.e., non-exclusive) access to the allocated nodes.
The total number of requested processes is determined by adding up the product of the number of
nodes and the number of processes per node for each node_spec. In general, this should match the
number of distributed engines specified in the Ansoft desktop -Machinelist
num=num_distributed_engines command line option.
The number of CPUs per process (cpp) specified in the PBS qsub command line or in the PBS
directives in the script file should generally match the number of processors per engine specified in
the Desktop -batchoptions value. Both the NumberOfProcessors and NumberOfProcessorsDistrib-
uted should match the PBS cpp value.
See the PBS documentation for a complete list of options for the bsub command, and further infor-
mation on running multi-node jobs.
Related Topics
Integration with PBS (Portable Batch System) Professional from Altair Engineering
Monitoring Ansoft PBS Batch Jobs
Example PBS qsub Command Lines
Example PBS qsub Command Lines
"Single-node jobs." The last example is a PBS "multi-node jobs"; this examples demonstrate how
to specify the allocation of threads, tasks and nodes to a job.
Serial job:
qsub ~/pbs_scripts/OptimTee.sh
Job Script File:
#!/bin/sh
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
~/projects/OptimTee.hfss
Serial job that needs a minimum of 4GB memory and two hours of real (wallclock)
time:
qsub ~/pbs_scripts/OptimTee.sh
Job Script File:
#!/bin/sh
#PBS -l walltime=2:00:00
#PBS -l mem=4gb
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
~/projects/OptimTee.hfss
Multi-processing job using 4 cores:
qsub ~/pbs_scripts/OptimTee.sh
Job Script File:
#!/bin/sh
#PBS -l ncpus=4
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve -batchoptions
"'HFSS/Preferences/NumberOfProcessors'=4" _
~/projects/OptimTee.hfss
• The #PBS -l ncpus=4 directive indicates that four cores or CPUs are allocated to this job.
• The -batchoptions option indicates that HFSS should use four cores for multi-processing.
Distributed processing job using 4 engines on a single host:
qsub ~/pbs_scripts/OptimTee.sh
Job Script File:
#!/bin/sh
#PBS -l ncpus=4
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve -Distributed _
~/projects/OptimTee.hfss
• The #PBS -l ncpus=4 directive indicates that four cores or CPUs are allocated to this job.
• The -Distributed option indicates that this is a DSO job, so that multiple engines will be
started. Because 4 cores are allocated to the job, the job will run 4 engines.
Distributed processing and multi-processing job using 8 cores on two nodes,
running 4 engines (two per node) with 2 cores for multi-processing:
qsub ~/pbs_scripts/OptimTee.sh
Job Script File:
#!/bin/sh
#PBS -l nodes=2:ppn=2:cpp=2#excl
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve -Distributed _
-machinelist num=4 -batchoptions _
"'HFSS/Preferences/NumberOfProcessorsDistributed'=2 _
'HFSS/Preferences/NumberOfProcessors'=2" _
~/projects/OptimTee.hfss
• The PBS directive #PBS -l nodes=2:ppn=1:cpp=2#shared indicates that two nodes are
requested [2], two processes (engines) run on each node [ppn=2], and each process will use
two cores [cpp=2]. The hosts allocated to this job may not be used for any other jobs while this
job is running [#excl].
• The -machinelist num=4 option indicates that this is a DSO job and that a total of four engines
will be started.
• The 'HFSS/Preferences/NumberOfProcessorsDistributed=2 batchoption indicates that the dis-
tributed analysis engines should use two cores for multi-processing.
• The 'HFSS/Preferences/NumberOfProcessors=2 batchoption indicates that the portion of the
analysis that is not distributed should use two cores for multi-processing.
Related Topics
Integration with PBS (Portable Batch System) Professional from Altair Engineering
qsub Arguments
Monitoring Ansoft PBS Batch Jobs
Example PBS qsub Command Lines
Integration with Sun Grid Engine (SGE)
Submitting Ansoft SGE Batch Jobs
The SGE qsub command may be used to submit Ansoft jobs. Typical command formats are:
qsub qsub_args ansoft_exe ansoft_args
qsub qsub_args job_script
qsub qsub_args[ -]
where:
• qsub_args are the options of the qsub command,
• ansoft_exe is the pathname of the Ansoft tool executable to launch,
Running Simulations14-55
HFSS Online Help
start_proc_args /bin/true
stop_proc_args /bin/true
allocation_rule $round_robin
control_slaves TRUE
job_is_first_task FALSE
urgency_slots min
accounting_summary TRUE
The user_lists and xuser_lists parameters are ACLs (access control lists) used to control which
users have permission to use the parallel environment. The user_lists setting gives permission to
use the PE. The xuser_lists setting denys permission to use the parallel environment. The
xuser_lists settings override the user_lists settings.
The start_proc_args and stop_proc_args parameters contain the pathname and arguments for the
parallel environment startup and shutdown scripts. No startup or shutdown scripts are needed for
parallel Ansoft batch jobs. The setting /bin/true may be used as the value for these scripts; this util-
ity does nothing and returns an exit code indicating success (0).
The parallel environment allocation_rule parameter will affect how the analysis engine tasks are
distributed across the hosts allocated to the job. The $round_robin setting distributes the tasks
across the hosts in a round robin fashion, resulting in the load being relatively evenly distributed
over all of the hosts. The $fill_up setting allocates all slots on a host before distributing the tasks to
another host; the result is that most hosts are either fully utilized or completely unused. See the
sge_pe man page for other settings for this parameter.
The control_slaves parameter must be set to TRUE, as described above.
The job_is_first_task parameter also affects how tasks are allocated. When submitting a job to run
in a parallel environment, the number of parallel tasks, n, is specified on the command line. If this
setting is TRUE, then the job process is considered one of the tasks, and only (n-1) additional tasks
are allocated to the job. If the setting is FALSE, then the job process is not considered to be one of
the tasks, and n additional tasks are allocated for the job.
See the sge_pe man page for more information about these and other PE parameters.
A parallel environment does not run tasks directly. Instead, the tasks are distributed to queues asso-
ciated with the parallel environment. In order to complete the setup of a parallel environment, one
or more queues need to be associated with the parallel environment. The queue pe_list parameter is
used to specify the parallel environments (PEs) supported by the queue. This is an important step; if
no queues support a given PE, then jobs submitted to that PE will not run.
Parallel Batch Job Command Line Considerations
The number of engines run on a host will depend on the total number of distributed engines, and the
number of hosts allocated to the job. The memory required on a host depends on the number of
engines running on the host and on the memory needed for each engine. The qsub command -l
resource=value,... or -q queue_list command line options specify that the parallel batch job run on
machines with sufficient memory and other resources.
Related Topics
Running Simulations14-57
HFSS Online Help
You can monitor the progress of a job by checking the standard output file for progress, info and
warning messages, and checking the standard error file for error and fatal messages.
Related Topics
Integration with Sun Grid Engine (SGE)
Monitoring Ansoft SGE Batch Jobs
Example SGE qsub Command Lines
Issue with qrsh (SGE)
Issue with MainWin Core Services for SGE
Example SGE qsub Command Lines
All of the following examples show how to submit Linux HFSS jobs on SGE, but similar command
lines will work for all Ansoft products.
Serial job using command line:
qsub -b y /opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
~/projects/OptimTee.hfss
• The -b y option indicates that hfss is launched directly from the command line, instead of using
a script.
• No queue is specified, so the default queue will be used
Serial job with a hard runtime limit of 15 minutes:
qsub -b y -l h_rt=00:15:00 /opt/Ansoft/HFSS13/hfss13/hfss _
-ng -BatchSolve ~/projects/OptimTee.hfss
• The -l h_rt=00:15:00 option indicates that this job has a "hard" runtime limit of 15 minutes.
Serial job using a script, with a runtime limit specified in the script:
qsub ~/sge/scripts/OptimTee.csh
• The -b y option is absent, so the script ~/sge/scripts/OptimTee.csh will be run when the job
starts.
• The script file OptimTee.csh may contain SGE directives in addition to the command(s) to run.
In this example, a directive with a hard runtime limit if 15 minutes is included in the script.
Script file contents:
#!/bin/csh
#$ -l h_rt=00:15:00
/opt/Ansoft/HFSS13/hfss13/hfss -ng -BatchSolve _
~/projects/OptimTee.hfss
• The SGE directive #$ -l h_rt=00:15:00 is equivalent to including -l h_rt=00:15:00 on the qsub
command line.
Running Simulations14-59
HFSS Online Help
Running Simulations14-61
HFSS Online Help
Running Simulations14-63
HFSS Online Help
Running Simulations14-65
HFSS Online Help
Signature
extern "C" bool FN_PREFIX_IsProductLaunchedInYourEnvironment();
Arguments
None.
Return Value
Returns true if the current process is running as a job of the scheduler. Otherwise, false is
returned.
Notes
For many schedulers, the presence of certain environment variables or their values may be checked
to determine if the current process is running as a job of the scheduler.
GetTempDirectory
Purpose
Get the pathname of the temporary directory provided by the scheduler for the current job. The
pathname is an empty string if the scheduler does not provide a temporary directory for the
current job.
Signature
extern "C" bool FN_PREFIX_GetTempDirectory(char * buffer,
unsigned int* length);
Arguments
buffer: Pointer to a character buffer to contain the temporary directory path name or NULL.
length: Pointer to a location to contain the length of the buffer. Must be a valid pointer to an
unsigned int.
Return Value
If argument buffer is NULL, then then required length of the buffer is stored in the location to
which argument length points, and true is returned.
If argument buffer is not NULL, then the value to which argument length points (the buffer
length) is checked. If it is large enough to contain the pathname of the temporary directory,
including the terminal null byte, then the pathname is copied to the buffer and true is returned.
If the buffer length is insufficient for the pathname of the temporary directory, then the buffer
is unchanged, and false is returned.
Notes
To get the pathname of the temporary directory, the infrastructure first calls this function with a
NULL buffer, and obtains the required length of the buffer for the pathname. After creating a buffer
of the appropriate size, the infrastructure calls this function again, passing the pointer to the buffer
in the buffer argument and a pointer to the size of the buffer in the length argument.
GetMachineListAvailableForDistribution
Purpose
Get the list of hosts allocated to the current job. A host will appear in the list multiple times if
Running Simulations14-67
HFSS Online Help
the scheduler has allocated multiple processors or cores on the host to the job. The number of
times the host appears in the list is equal to the number of processors or cores of the host that
are allocated to the current job. The list is a text string containing a space separated list of host-
names.
Signature
extern "C" bool
FN_PREFIX_GetMachineListAvailableForDistribution(char * buffer,
unsigned int* length);
Arguments
buffer: Pointer to a character buffer to contain the list of machines available for distribution
or NULL.
length: Pointer to a location to contain the length of the buffer. Must be a valid pointer to an
unsigned int.
Return Value
If argument buffer is NULL, then then required length of the buffer is stored in the location to
which argument length points, and true is returned.
If argument buffer is not NULL, then the value to which argument length points (the buffer
length) is checked. If it is large enough to contain the lists of hosts, including the terminal null
byte, then the list is copied to the buffer and true is returned. If the buffer length is insufficient
for the list of hosts, then the buffer is unchanged, and false is returned.
Notes
To get the list of hosts for distribution, the infrastructure first calls this function with a NULL buf-
fer, and obtains the required length of the buffer for the list. After creating a buffer of the appropri-
ate size, the infrastructure calls this function again, passing the pointer to the buffer in the buffer
argument and a pointer to the size of the buffer in the length argument.
The hostnames in the list provided by this function shall be used in calls to LaunchProcess(). These
host names must be in a format that is accepted by that function. See the section below on Launch-
Process.
LaunchProcess
Purpose
Launch a local or remote process to run an analysis engine. This function is called by the
Ansoft desktop application to launch an engine process on a specified host. The hostname is
one of the names in the list provided by the GetMachineListAvailableForDistribution function.
See the GetMachineListAvailableForDistribution section above. If the hostname does not refer
to the local host, then this function shall use the scheduler to launch the engine on the specified
host. If the hostname refers to the local host, then the engine may be started as a child process,
or it may be started using the scheduler.
Signature
Signature
extern "C" bool FN_PREFIX_GetUseRsmForEngineLaunch(void)
Arguments
None.
Return Value
Returns true if the Ansoft RSM service should be used to launch engine processes for this
scheduler. Returns false if the Ansoft RSM service should not be used to launch engine pro-
cesses for this scheduler.
Notes
This function is optional. If not implemented, then it is treated the same as if it was implemented
and returns false.
GetThisJobID
Purpose
Get a string identifying the job currently running in the scheduler environment. This string is
displayed to the end user to identify the job.
Signature
extern "C" bool FN_PREFIX_GetThisJobID(char * buffer, unsigned
int* length);
Arguments
buffer: Pointer to a character buffer to contain the Job ID or NULL.
length: Pointer to a location to contain the length of the buffer. Must be a valid pointer to an
unsigned int.
Return Value
If argument buffer is NULL, then then required length of the buffer is stored in the location to
which argument length points, and true is returned.
If argument buffer is not NULL, then the value to which argument length points (the buffer
length) is checked. If it is large enough to contain the string identifying the current job, includ-
ing the terminal null byte, then the job ID is copied to the buffer and true is returned. If the buf-
fer length is insufficient for the job ID, then the buffer is unchanged, and false is returned.
Notes
To get the job ID, the infrastructure first calls this function with a NULL buffer, and obtains the
required length of the buffer for the job ID. After creating a buffer of the appropriate size, the infra-
structure calls this function again, passing the pointer to the buffer in the buffer argument and a
pointer to the size of the buffer in the length argument.
For many schedulers, the job ID may be obtained from the value of an environment variable.
GetSchedulerDisplayName
Purpose
Get a string identifying the scheduler associated with the current scheduler proxy library. This
string is displayed to the end user to identify the scheduler.
Signature
extern "C" bool FN_PREFIX_GetSchedulerDisplayName(char *
buffer, unsigned int* length);
Arguments
buffer: Pointer to a character buffer to contain the scheduler display name or NULL.
length: Pointer to a location to contain the length of the buffer. Must be a valid pointer to an
unsigned int.
Return Value
If argument buffer is NULL, then then required length of the buffer is stored in the location to
which argument length points, and true is returned.
If argument buffer is not NULL, then the value to which argument length points (the buffer
length) is checked. If it is large enough to contain the scheduler display name, including the
terminal null byte, then the scheduler display name is copied to the buffer and true is returned.
If the buffer length is insufficient for the scheduler display name, then the buffer is unchanged,
and false is returned.
Notes
To get the scheduler display name, the infrastructure first calls this function with a NULL buffer,
and obtains the required length of the buffer for the scheduler display name. After creating a buffer
of the appropriate size, the infrastructure calls this function again, passing the pointer to the buffer
in the buffer argument and a pointer to the size of the buffer in the length argument.
The scheduler display name is generally a fixed string.
Testing Your Scheduler Integration
One way to test these functions is to run the analysis for an Ansoft product in batch mode. When
running in batch mode, a batch log file is created in the same directory as the project file. The batch
log file has the same base name is the project file, with an extension of ".log". For example, if the
project file is TestProject123.hfss, then the batch file is TestProject123.log. The batch log file con-
tains useful information about the analysis run.
See the product specific help for details on running the product in batch mode, and for the com-
mand line options to use for distributed analysis.
• Testing IsProductLaunchedInYourEnvironment
• Testing GetSchedulerDisplayName and GetThisJobID
• Testing GetTempDirectory
• Testing GetMachineListAvailableForDistribution
• Testing LaunchProcess
• Testing GetUseRsmForEngineLaunch
Running Simulations14-71
HFSS Online Help
Testing IsProductLaunchedInYourEnvironment
This function should be tested first. If the Ansoft application is not able to load and run this
function, or if it returns false, then none of the other functions will be called. If the batch anal-
ysis is running in a scheduler environment, and this function returns true, then there will be an
"info" message near the beginning of the batch log indicating that the analysis is running as a
scheduler job. This message will include the scheduler display name returned by the function
GetSchedulerDisplayName, and it will also include the job ID returned by the function
GetThisJobID. If the batch analysis is not running in a scheduler environment, then none of the
messages will include a scheduler display name or job ID.
If this message does not appear when running in a scheduler environment, ensure that the
scheduler proxy library is named correctly, that it is built correctly, that it is installed in the
correct directory, and that the function name prefix is the same is the library prefix converted
to upper case.
Testing GetSchedulerDisplayName and GetThisJobID
As described above, when running a batch job in a scheduler environment, the scheduler dis-
play name and the job ID will appear in an "info" message near the beginning of the batch log.
The values returned by these functions are copied to this message verbatim, so they can be
directly compared to the expected values.
Testing GetTempDirectory
Unfinished. The temp directory displayed in the batch log is the default installation setting, not
the one from the scheduler. The scheduler temp directory is set in AnsoftCOMApplica-
tion::MainFunction(), so it happens for COM engines, but not for the desktop.
Testing GetMachineListAvailableForDistribution
This function is used for distributed analysis. The analysis may be distributed across several
machines if portions of the analysis are independent. For example, frequency sweeps, paramet-
ric analysis and domain decomposition allow different portions of the analysis to be distributed
across machines. The analysis in a batch job will be distributed to multiple processors or hosts
if the the analysis includes a setup that may be distributed (e.g., a frequency sweep or paramet-
ric analysis) and the -Distributed option is included in the desktop command line. The list of
machines is displayed in an "info" message near the beginning of the batch log. The list in the
info message can be directly compared to the expected list of machines.
To verify that the machine list is constructed correctly for a variety of cases, it may be neces-
sary to test several jobs with different resource requirements and verify that the machine list is
correct in each case. For example, one may run batch analyses with the following resource
requirements:
• One processor on one host
• Several processors on one host
• One processor on each of several hosts
• Several processors on each of several hosts
Testing LaunchProcess
This function is used to launch analysis engines in the case where the analysis is distributed across
multiple hosts. The analysis may be distributed across several machines if portions of the analysis
are independent. For example, frequency sweeps, parametric analysis and domain decomposition
allow different portions of the analysis to be distributed across machines. The analysis in a batch
job will be distributed to multiple processors or hosts if the the analysis includes a setup that may
be distributed (e.g., a frequency sweep or parametric analysis) and the -Distributed option is
included in the desktop command line. The list of machines is displayed in an "info" message near
the beginning of the batch log. The batch log may also contain info messages when portions of the
analysis distributed to different machines start or finish. These messages usually include the name
of the host when the analysis ran or will run. One can verify that the analysis is actually running on
the expected host or hosts using the Linux ps command or the Windows Task Manager.
In general, one analysis engine is started for each occurrence of each host in the list of machines
available for distribution. For example, if the list of hosts is "hostA hostA hostA hostB hostB", then
a total of 5 engines would be started, three on hostA and two on hostB. In some cases, an additional
engine is started to perform the portion of the analysis which is not distributed; if this is the case,
the non-distributed engine is idle during the portion of the analysis which is distributed. If this
occurs in the case where the list of hosts is "hostA hostA hostA hostB hostB", then a total of 6
engines would be started, but at most 5 engines would be active at any given time. When each anal-
ysis engine is running, it may start additional child processes to do a portion of the analysis, but
these are not counted as additional analysis engines because the parent of the sub-engine is inactive
(waiting for the sub-engine results) when the sub-engine is active.
Testing should be sufficient to demonstrate that the scheduler proxy library can start multiple
engine processes on the desktop host, and can also start multiple engine processes on other hosts.
Testing GetUseRsmForEngineLaunch
In most cases, this function will not be implemented or tested. If this function is implemented and
returns true, then the Ansoft desktop application will not start the analysis engines using the
LaunchProcess function directly. Instead, the Ansoft desktop application will start one
AnsoftRSMService process on each host using the LaunchProcess function, and the engine
processes will be started by these AnsoftRSMService processes. One may check for these pro-
cesses using the Linux ps command or the Windows Task Manager. One AnsoftRSMService pro-
cess should run on each host. These processes will be named ansoftrsmservice.exe or
AnsoftRSMService.exe. These processes will be started on each host before any analysis engine is
started on the host, and will remain running until the job is complete.
Troubleshooting Custom Scheduler Integration
• None of the Proxy Functions are Called
• Troubleshooting IsProductLaunchedInYourEnvironment Function
• Troubleshooting GetSchedulerDisplayName
• Troubleshooting GetThisJobID
• Troubleshooting GetTempDirectory
Running Simulations14-73
HFSS Online Help
• Troubleshooting GetMachineListAvailableForDistribution
• Troubleshooting LaunchProcess
• Troubleshooting GetUseRsmForEngineLaunch
None of the Proxy Functions are Called
There are several problems which could result in none of the proxy functions being called.
The scheduler proxy library must be installed in the schedulers subdirectory of the Ansoft installa-
tion directory. The installation directory is set in the registry entry HKEY_CURRENT_USER/
Software/Ansoft/Product/Version/Desktop/InstallationDirectory, where
Productis the Ansoft product name (eg, HFSS) and Versionis the Ansoft product version (e.g.,
12.0).
The scheduler proxy library name must match "*_scheduler.dll" on Windows and
"lib*_scheduler.so" on Linux. If the library name does not match this format, then the library will
not be loaded. In addition, the
function name prefix must be the same as the library name prefix converted to upper case. For
example, if the library name prefix is "abc", then the function name prefix is "ABC". In this exam-
ple, the library name is "abc_scheduler.dll" on Windows, and "libabc_scheduler.so" on Linux. In
this example, the full name of the IsProductLaunchedInYourEnvironment function is
ABC_IsProductLaunchedInYourEnvironment on Windows and Linux, and it must have extern "C"
linkage.
Verify that the compile and link flags follow the guidelines in the section "Build Information",
above. Incorrect compile or link flags may prevent the library from being loaded by the Ansoft
product.
If there is a problem with calling the IsProductLaunchedInYourEnvironment function,
then none of the other functions will be called. The other functions are only called if the IsPro-
ductLaunchedInYourEnvironment function is successfully called and returns true.
Troubleshooting IsProductLaunchedInYourEnvironment Function
Verify that the conditions specified in the section "None of the Proxy Functions are Called" are met.
Verify that this function returns true when called in an environment running under the scheduler,
and that it returns false when called in an environment not running under the scheduler.
Troubleshooting GetSchedulerDisplayName
Verify that the IsProductLaunchedInYourEnvironment function returns true when run-
ning in the scheduler environment.
Verify that the scheduler display name is a valid ASCII string.
Verify that, if argument buffer is NULL, then the required length of the buffer is stored in the loca-
tion to which argument length points, and true is returned. The required buffer length must include
space for the string null terminator.
Verify that, if argument buffer is not NULL and the value to which argument length points (the buf-
fer length) is large enough to contain the display name, including the terminal null byte, then the
display name is copied to the buffer and true is returned.
14-74 Running Simulations
HFSS Online Help
Troubleshooting GetThisJobID
Verify that the IsProductLaunchedInYourEnvironment function returns true when run-
ning in the scheduler environment.
Verify that the job ID is a valid ASCII string.
Verify that, if argument buffer is NULL, then the required length of the buffer is stored in the loca-
tion to which argument length points, and true is returned. The required buffer length must include
space for the string null terminator.
Verify that, if argument buffer is not NULL and the value to which argument length points (the buf-
fer length) is large enough to contain the job ID, including the terminal null byte, then the job ID is
copied to the buffer and true is returned.
Troubleshooting GetTempDirectory
Verify that the IsProductLaunchedInYourEnvironment function returns true when run-
ning in the scheduler environment.
Verify that the temporary directory name is a valid ASCII string.
Verify that, if argument buffer is NULL, then the required length of the buffer is stored in the loca-
tion to which argument length points, and true is returned. The required buffer length must include
space for the string null terminator.
Verify that, if argument buffer is not NULL and the value to which argument length points (the buf-
fer length) is large enough to contain the temporary directory pathname, including the terminal null
byte, then the temporary directory pathname is copied to the buffer and true is returned.
Troubleshooting GetMachineListAvailableForDistribution
Verify that the IsProductLaunchedInYourEnvironment function returns true when run-
ning in the scheduler environment.
Verify that the list of hosts is a valid ASCII string containing a space separated list of host names. A
host name will appear in the list a number of times equal to the number of processors or cores avail-
able to the job on that host.
Verify that, if argument buffer is NULL, then the required length of the buffer is stored in the loca-
tion to which argument length points, and true is returned. The required buffer length must include
space for the string null terminator.
Verify that, if argument buffer is not NULL and the value to which argument length points (the buf-
fer length) is large enough to contain the list of hosts, including the terminal null byte, then the list
of hosts is copied to the buffer and true is returned.
Troubleshooting LaunchProcess
Verify that the IsProductLaunchedInYourEnvironment function returns true when run-
ning in the scheduler environment.
The hostName argument is a host name from the list returned by the GetMachineListAvailable-
ForDistribution function. Verify that the LaunchProcess function can accept host names in the for-
mat returned by the GetMachineListAvailableForDistribution function.
Running Simulations14-75
HFSS Online Help
The exePathName argument is the pathname of the analysis engine executable to be started. This
pathname may contain spaces or other characters special to the shell. Ensure that the LaunchPro-
cess function is able to handle such cases.
The arg1 and arg2 arguments may contain newlines, tabs, single quotes, spaces, dollar signs, and
other characters which may be special to the shell. Ensure that the LaunchProcess function is able
to handle such cases. If needed, the newline characters may be replaced by other whitespace char-
acters. One or both of these arguments could also be an empty string; verify that the empty string is
correctly passed to the engine process command line.
If a scheduler command is used to launch the engine process on a remote machine, the engine com-
mand line may be processed by the shell twice, once when the scheduler command is processed by
the shell, and again when the engine command is processed by the shell. In such cases, the quoting
of characters special to the shell will need to be take these two passes through the shell into
account. In some implementations, it may be necessary or convenient to use different approaches
for launching engine processes on the local machine and on remote machines; if this is done, verify
that the approach used to determine whether the hostName argument represents the local machine
is correct.
Troubleshooting GetUseRsmForEngineLaunch
In most cases, this function will not be implemented. If it is implemented, then follow the sugges-
tions below.
Verify that the IsProductLaunchedInYourEnvironment function returns true
when running in the scheduler environment.
If the RSM should be used for launching engines, verify that this function returns true. Otherwise,
verify that this function returns false.
Note The Windows Task Manager does not indicate a reduced priority for the HFSS solver. It
only lists the priority of the engine manager, which appears normal, not the actual
engine. The actual engine is in a separate thread, whose priority is not visible in the
Windows Task Manager.
Running Simulations14-77
HFSS Online Help
Aborting an Analysis
To end the solution process before it is complete:
• Right-click In the Progress window and click Abort.
HFSS ends the analysis immediately.
The data for the currently solving pass or frequency point is deleted. All previously solved solu-
tions are retained. For example, if you abort between the third and fourth adaptive pass, the solu-
tions for the third pass will be available, and any solutions for the fourth pass are discarded.
To abort the solution process after the current adaptive pass or solved frequency point is complete:
• Right-click the Progress window, and click Clean Stop on the shortcut menu.
HFSS ends the analysis after the next solved pass or frequency point.
If you request a clean stop between the third and fourth adaptive pass, the solutions for the third and
fourth pass will be available once the fourth pass has finished solving.
Ansoft Application as an LSF Job
If you have an Ansoft application running as an LSF job, you can use the command “bkill –s SIG-
TERM jobid” to terminate an Ansoft application. Here jobid is the LSF job id. The response will
be “Job <jobid> is being signaled”. The response is the same whether the job is actually being sig-
naled or not.
This works correctly on a 32 bit version of Windows XP, using a 32 bit version of LSF.
In cases where the SIGTERM parameter is ignored, the command kills the LSF job, but does not
clean the lock files, and other files may not be in a consistent state. See http://www.vital-it.ch/sup-
port/LSF/programmer/advanced.html for a detailed description under Signal Handling in Windows.
Unix/Linux
For UNIX/Linux, you can use TERM commands. Sigterm handling for Unix is done in Desktop
library. You can abort a running batchsolve on Unix by sending a TERM signal to hfss.exe
Related Topics
Integration with Platform’s Load Sharing Facility (LSF)
Running Simulations14-79
HFSS Online Help
Running Simulations14-81
HFSS Online Help
After an analysis that includes thermal feedback from ANSYS Workbench 12, you can see temper-
ature changes expressed in Temperature field overlays (both visually in the overlay and in the color
key) as well as in the Solution data.
In the Solution data Profile tab you will see a new entry for Maximum Delta T, for the change in
temperature from the previous simulation. The first appearance shows an N/A value, as shown
here:
This simulation feedback loop from Ansoft to ANSYS Workbench 12 and back can continue until
you decide that Temperature delta reported in the Solution Report low and stable for the designs.
Related Topics
Export Transfer File for ANSYS
Enable Thermal Feedback from ANSYS Mechanical
Running Simulations14-83
HFSS Online Help
Optimetrics enables you to determine the best design variation among a model's possible varia-
tions. You create the original model, the nominal design, and then define the design parameters that
vary, which can be nearly any design parameter assigned a numeric value in HFSS. For example,
you can parameterize the model geometry or material properties. You can then perform the follow-
ing types of analyses on your nominal HFSS design:
Parametric In a parametric analysis, you define one or more variable sweep definitions,
each specifying a series of variable values within a range. For example, you
can parameterize component values. (See Variables in HFSS for more
information.) Optimetrics solves the design at each variation. You can then
compare the results to determine how each design variation affects the
performance of the design. Parametric analyses are often used as precursors to
optimization solutions because they help to determine a reasonable range of
variable values for the optimization analysis.
Optimization For an optimization analysis, you identify the cost function and the
optimization goal. Optimetrics changes the design parameter values to meet
that goal. The cost function can be based on any solution quantity that HFSS
can compute.
Optimetrics 15-1
HFSS Online Help
Sensitivity In a sensitivity analysis, you use Optimetrics to explore the vicinity of the
design point to determine the sensitivity of the design to small changes in
variables.
Tuning Tuning allows you to change variable values interactively while monitoring
the performance of the design. If you want to ensure that tuning does not
resolve variations already solved by parametric setup, you must check Save
Fields Mesh in the Options tab of the optimetrics setup.
Statistical In a statistical analysis, you use Optimetrics to determine the distribution of a
design's performance, which is caused by a statistical distribution of variable
values.
Note Sweeping or using a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
You can also Link to ANSYS Design Xplorer. This permits you to manage an HFSS Optimetrics
simulation from the ANSYS Workbench.
Related Topics
Getting Started Guide: Optimizing Waveguide T-Junction
Setting up a Parametric Analysis
Setting up an Optimization Analysis
Setting up a Sensitivity Analysis
Tuning a Variable
Setting up a Statistical Analysis
Parametric Overview
Optimization Overview
Sensitivity Analysis Overview
Statistical Analysis Overview
Tuning Overview
Using Distributed Analysis
15-2 Optimetrics
HFSSOnline Help
Parametric Overview
Running a parametric analysis enables you to simulate several design variations using a single
model. You define a series of variable values within a range, or a variable sweep definition, and
HFSS generates a solution for each design variation. You can then compare the results to determine
how each design variation affects the performance of the design.
You can vary design parameters that are assigned a quantity, such as geometry dimensions, material
properties, and boundary and excitation properties. (See the online help topic for the specific
parameter you want to vary.) The number of variations that can be defined in a parametric sweep
setup is limited only by your computing resources.
To perform a parametric analysis, you first create a nominal design. A nominal design is created
like any other design, except that variables are assigned to those aspects of the model you want to
change. All variables must be defined before you start the parametric analysis. Although you are
not required to solve the nominal design before performing a parametric analysis, doing so helps
ensure that the model is set up and operates as intended. Alternatively, you can perform a validation
check on the nominal design before performing a parametric analysis.
Parametric analyses are often used as precursors to optimization analyses because they enable you
to determine a reasonable range of variable values for an optimization analysis.
Related Topics
Setting up a Parametric Analysis
Optimetrics 15-3
HFSS Online Help
Note Once you have created a parametric setup, you can copy and paste it, and then make
changes to the copy, rather than redoing the whole process for minor changes.
Note Sweeping or using a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
Related Topics
Adding a Variable Sweep Definition
Specifying a Solution Setup for a Parametric Setup
Using Distributed Analysis
Parametric Overview
Adding a Parametric Sweep from a File
Note Sweeping a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
15-4 Optimetrics
HFSSOnline Help
Optimetrics 15-5
HFSS Online Help
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
3. If you selected Linear step as the sweep type, type the step size in the Step box.
The step size is the difference between variable values in the sweep definition. The step size
determines the number of design variations between the start and stop values. HFSS will solve
the model at each step in the specified range, including the start and stop values. The step size
can be negative, when the Stop value is less than the Start value
If you selected another sweep type, type the number of points, or variable values, in the sweep
definition in the Count text box. For Decade count and Octave count, the Count value spec-
ifies the number of points to calculate in every decade or octave. For Exponential count, the
Count value is the total number of points. The total number of points includes the start and
stop values.
Related Topics
Synchronizing Variable Sweep Definitions
Synchronizing Variable Sweep Definitions
By default, variable sweep definitions are nested. Alternatively, you can synchronize the variable
sweep definitions if they have the same number of sweep points.
15-6 Optimetrics
HFSSOnline Help
For example, if you synchronize a sweep definition that includes values of 1, 2, and 3 inches with a
second sweep definition that includes values of 4, 5, and 6 inches, HFSS will solve 3 design varia-
tions. The first variation is solved at the variable values of 1 and 4; the second variation is solved at
the variable values 2 and 5; and the third variation is solved at the final variable values 3 and 6.
To synchronize variable sweep definitions:
1. Under the Sweep Definitions tab of the Setup Sweep Analysis dialog box, select the rows
containing the sweep definitions you want to synchronize.
2. Click Sync.
The synchronized sweeps are given a group number, which is listed in the Sync # column.
Optionally, view the design variations that are to be solved in table format under the Table tab.
Related Topics
Specifying Variable Values for a Sweep Definitions
Modifying a Variable Sweep Definition Manually
You can manually modify the variable values that are solved for a parametric setup by explicitly
changing, adding, or deleting existing points in a variable sweep definition under the Table tab of
the Setup Sweep Analysis dialog box.
To manually modify a variable sweep definition:
1. Click the Table tab of the Setup Sweep Analysis dialog box.
The design variations HFSS solves for the parametric setup listed in table format.
2. Do one of the following:
• To modify a variable value, click a value text box in the table and type a new value.
• To delete a variable value from the sweep definition, click the row you want to delete, and
then click Delete.
• To add a new variable value to the sweep definition, click Add. Then click in the value
text box and type a new value.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
Your modifications are tracked and available for viewing at the bottom of the Setup Sweep Analy-
sis dialog box under the Sweep Definitions tab. The operations you performed are listed with
descriptions.
Warning If you modify an original sweep definition using the Add/Edit Sweep dialog box
after you have manually modified its table of design variations, your manual
modifications become invalid and are removed. A warning is displayed to inform
you that your manual values are about to become invalid, so you can decide whether
or not to proceed.
Optimetrics 15-7
HFSS Online Help
Related Topics
Adding a Variable Sweep Definition
Overriding a Variable’s Current Value in a Parametric Setup
Adding a Parametric Sweep from a File
Note Alternatively, you can select the Override option first, and then type a new variable
value in the Value box.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
Related Topics
Adding a Variable Sweep Definition
Modifying a Variable Sweep Definition Manually
Specifying a Solution Setup for a Parametric Setup
To specify the solution setup that HFSS analyzes when it solves a parametric setup:
1. In the Setup Sweep Analysis dialog box, click the General tab.
2. Select the solution setup you want HFSS to use when it solves the parametric setup.
HFSS solves the parametric setup using the solution setup you select. If you select more than
one, results are generated for all selected solution setups.
15-8 Optimetrics
HFSSOnline Help
Related Topics
Specifying the Solution Quantity to Evaluate for Parametric Analysis
Specifying a Solution Quantity’s Calculation Range
Specifying the Solution Quantity to Evaluate for Parametric Analysis
When you add a parametric setup, you can identify one or more solution quantities to be presented
in the Post Analysis Display dialog box. The solution quantities are specified by mathematical
expressions that are composed of basic quantities, such as output variables. When you view the
results, HFSS extracts the solution quantities and lists them in the results table.
1. In the Setup Sweep Analysis dialog box, click the Calculations tab.
This displays a table that will show Solutions and associated Calculations. Below the table, are
control buttons to Setup Calculations... and Delete.
2. Click Setup Calculations.
This displays the Add/Edit Calculation dialog. The dialog contains panes to set the Context,
the Trace tab for the Calculation Expression, and the Calculation Range tab for the Calcu-
lation Range.
Follow the procedure to Setup Calculations for Optimetrics.
3. Click Add Calculation to add the expression in the Add/Edit Calculation dialog Calculation
Expression field to the Calculations tab of the Setup Sweep Analysis dialog.
4. Click Done to close the Add/Edit Calculation dialog.
Related Topics
Specifying a Solution Quantity’s Calculation Range
Specifying Output Variables
Setup Calculations for Optimetrics.
Setup Calculations for Optimetrics
The Setup dialogs for each of the Optimetrics types include a Setup Calculations button. Clicking
this displays the Add/Edit Calculation dialog box. The dialog box contains distinct panes and tabs
to set the Context, the Calculation Expression, and the Calculation Range.
The Context pane contains fields for the Report Type to use, the Solution, and depending on the
Report Type selection, the Geometry.
The Trace tab contains fields for the Calculation expression, and, to build the expression, a Cate-
gory list, a Quantity list with a Text Filter field, and a list of Functions available for the selected
Category. The Range function button opens a dialog in which you can define a range function to
apply a function to the expression.
The Category list for the Trace tab includes Variables and Output Variables. An Output Variables...
button lets you open a dialog box to define and edit the Output Variables.
Optimetrics 15-9
HFSS Online Help
Note The calculation you specify must be able to be evaluated into a single, real number.
Related Topics
Specifying a Solution Quantity to Evaluate
Setting a Range function
15-10 Optimetrics
HFSSOnline Help
Optimetrics 15-11
HFSS Online Help
variables that were swept during the parametric analysis remain constant.
Optionally, to modify the constant values of other swept variables, do the following:
a. Click Set Other Sweep Variables Value.
The Setup Plot dialog box appears. All of the other solved variable values are listed.
b. Click the row with the variable value you want to use as the constant value in the plot, and
then click OK.
10. Select the solution quantity results you want to plot on the y-axis from the Y pull-down list.
The x -y plot appears in the view window.
You can modify the display by right-clicking in the graph area. See Creating Reports for
details on these operations.
11. To view profile information about the analysis, click the Profile tab on the Post Analysis Dis-
play dialog.
12. When more than one parametric analysis has been run, use the left and right arrows to select a
profile.
13. Click Close to close the Post Analysis Display dialog.
Related Topics
Plotting Solution Quantity Results vs. a Swept Variable
Viewing Solution Data for an Optimetrics Design Variation
Using Distributed Analysis
If you have purchased the appropriate license, HFSS supports distributed solve, which involves dis-
tributing rows of a parametric table during Optimetrics solve.
If you do a distributed solve, HFSS launches solver engines on multiple machines, assuming that
you have configured your machines appropriately.
To run a distributed analysis:
1. Under Optimetrics in the project tree, right-click the specific parametric setup.
A shortcut menu appears.
2. Select Distribute Analysis from the shortcut menu.
Note After you define a parametric sweep, a shortcut menu becomes available when you
right-click the setup name.
While the analysis is running, you can access parent and child progress bars. By default, only
the main progress bar is displayed, while the child progress bars (or subtasks) remain hidden.
You can toggle between showing and hiding the child progress bars.
To show the child progress bars:
• Right-click the progress window, and select Show Subtask Progress Bars.
To hide the child progress bars:
15-12 Optimetrics
HFSSOnline Help
• Right-click the progress window, and select Hide Subtask Progress Bars.
Related Topics:
General Options: Analysis Options Tab: Solving Remotely (Windows Only)
Setting Up Distributed Analysis with Licensing
Optimetrics 15-13
HFSS Online Help
15-14 Optimetrics
HFSS Online Help
Optimization Overview
Optimetrics interfaces with Ansoft’s products to enable the optimization of a wide variety of design
parameters based on variable geometry, materials, excitations, component values, etc. Optimization
is the process of locating the minimum of a user-defined cost function. Optimetrics modifies the
variable values until the minimum is reached with acceptable accuracy.
Related Topics
Setting Up an Optimization Analysis
Choosing an Optimizer
Choosing an Optimizer
Conducting an optimization analysis allows you to determine an optimum solution for your prob-
lem. In HFSS optimization analyses, you have five choices of optimizer, though in most cases, the
Sequential Nonlinear Programming optimizer is recommended.
• Sequential Nonlinear Programming (SNLP)
• Sequential Mixed Integer NonLinear Programming (SMINLP)
• Quasi Newton
• Pattern Search
• Genetic Algorithm
All five optimizers assume that the nominal problem you are analyzing is close to the optimal solu-
tion; therefore, you must specify a domain that contains the region in which you expect to reach the
optimum value.
All five optimizers allow you to define a maximum limit to the number of iterations to be executed.
This prevents you from consuming your remaining computing resources and allows you to analyze
the obtained solutions. From this reduced range, you can further narrow the domain of the problem
and regenerate the solutions.
All optimizers also allow you to enter a coefficient in the Add Constraints window to define the
linear relationship between the selected variables and the entered constraint value. For the SNLP
and SMINLP optimizers, the relationship can be linear or nonlinear. For the Quasi Newton and Pat-
tern Search optimizers, the relationship must be linear.
Quasi Newton
If the Sequential Non Linear Programming Optimizer has difficulty, and if the numerical noise is
insignificant during the solution process, use the Quasi Newton optimizer to obtain the results. The
Quasi Newton optimizer works on the basis of finding a minimum or maximum of a cost function
which relates variables in the model or circuit to overall simulation goals. The user marks one or
more variables in the project and defines a cost function in the optimization setup. The cost func-
tion relates the variable values to field quantities, design parameters like force or torque, power
loss, etc. The optimizer can then maximize or minimize the value of the design parameter by vary-
ing the problem variables.
Sir Isaac Newton first showed that the maximum or minimum of any function can be determined by
setting the derivative of a function with respect to a variable (x) to zero and solving for the variable.
This approach leads to the exact solution for quadratic functions. However, for higher order func-
tions or numerical analysis, an iterative approach is commonly taken. The function is approximated
locally by a quadratic and the approximation is solved for the value of x. This value is placed back
into the original function and used to calculate a gradient which provides a step direction and size
for determining the next best value of x in the iteration process.
In the Quasi-Newton optimization procedure, the gradients and Hessian are calculated numerically.
Essentially, the change in x and the change in the gradient are used to estimate the Hessian for the
next iteration. The ratio of the change in cost to the change in the values of x provides the gradient,
whereas, the ratio of the change in the gradients to the change in the values of x provides the Hes-
sian for the next step and is know as the quasi-Newton condition. In order to perform the Quasi-
Newton optimization, at least three solutions are required for each parameter being varied. This can
have a significant computational cost depending upon the type of analysis being performed.
There are numerous methods described in the literature for solving for the Hessian and the details
of the method used by Optimetrics are beyond the scope of this document. However, as the Quasi-
Newton method is, at its heart, a gradient method, it suffers from two fundamental problems com-
mon to optimization. The first is the possible presence of local minima. The figure below illustrates
the problem of local minima. In this scenario, you can see that in order to find the minimum of the
function over the domain, a number of factors will determine the overall success including the ini-
tial starting point, the initial set of gradients calculated, the allowable step size, etc. Once the opti-
mizer has located a minimum, the Quasi-Newton approach will locate the bottom and will not
search further for other possible minima. In the example shown, when the optimizer begins at the
point labeled "Starting Point 1" the minima it finds is a local minima and not a good global solution
to the problem.
The second basic issue with Quasi-Newton optimization is numerical noise. In gradient optimiza-
tion, the derivatives are assumed to be smooth, well behaved functions. However, when the gradi-
ents are calculated numerically, the calculation involves taking the differences of numbers that get
progressively smaller. At some point, the numerical imprecision in the parameter calculations
becomes greater than the differences calculated in the gradients and the solution will oscillate and
may never reach convergence. To illustrate this, consider the figure shown below. In this scenario,
the optimizer is looking for the point labeled "minimum". Three possible solutions are labeled A, B
and C, with each arrow indicating the direction of the derivative of the function at that point. If
points A and B represent the last two solution points for the parameter, then it is easy to see that the
changes in the magnitude and the consistent direction of the derivatives will serve to push the solu-
tion closer to the desired minimum. If, however, points A and C are the last two solution points
respectively, the magnitude indicates the proper direction of movement, but the derivatives are
opposite, possibly causing the solution to move away from the minimum, back in the direction of
point A.
In order to use the Quasi-Newton optimizer effectively, the cost function should be based on
parameters that exhibit a smooth characteristic (little numerical noise) and a starting point of
the optimization should be chosen somewhat close to the expected minimum based on an
understanding of the physical problem being optimized. This becomes increasingly difficult,
however, when multiple parameters are being varied or when multiple parameters are to be
optimized. In addition, the computational burden of multivariate optimization with Quasi-
Newton increases geometrically with the number of variables being optimized. As a result, this
method should only be attempted when 1 or 2 variables are being optimized as a time.
For more information regarding Quasi-Newton optimization methods, see the following refer-
ence:
Schoenberg, Ronald. Optimization with the Quasi-Newton Method. Aptech Systems, Inc.
2001.
Related Topics
Optimization Setup for Quasi Newton Optimizer
Pattern Search
If the noise is significant in the nominal project, use the Pattern Search optimizer to obtain the
results. It performs a grid-based simplex search, which makes use of simplices: triangles in 2D
space or tetrahedra in 3D space. A simplex is a Euclidean geometric spatial element having the
minimum number of boundary points, such as a line segment in one-dimensional space, a triangle
in two-dimensional space, or a tetrahedron in three-dimensional space.
The cost value is calculated at the vertices of the simplex. The optimizer mirrors the simplex across
one of its faces based on mathematical guidelines and determines if the new simplex provides bet-
ter results. If it does not produce a better result, the next face is used for mirroring and the pattern
continues. If no improvement occurs, the grid is refined. If improvement occurs, the step is
accepted and the new simplex is generated to replace the original one. The figures below illustrate a
triangular simplex mirrored several times to demonstrate the pattern search approach in two vari-
ables and the simplices superimposed on a 2D cost function to demonstrate the convergence toward
a minimum in the cost function.
The Pattern Search algorithms are extensible to three variable optimization by using tetrahedral
simplices, however, they are not easily represented in graphical form. Generally, Pattern Search
algorithms are not used when more than three variables are used in the optimization.
When there is no improvement in the cost function regardless of the direction the simplex is mir-
rored, then the simplex is subdivided into smaller simplices and the process restarted.
Pattern Search algorithms have several advantages over Quasi-Newton algorithms. First, they are
less sensitive to noise because the cost function is evaluated at all node points on the simplex and
the numerical noise averages out over the simplex. The second advantage is that the number of ini-
tial solutions is generally smaller. However, since the pattern search does not use gradient informa-
tion to locate the minimum the process converges more slowly toward the true minimum, taking
more steps to successively divide the simplices as the minimum is approached.
Related Topics
Optimization Setup for Pattern Search Optimizer
Like Quasi Newton, the SNLP optimizer assumes that the noise is not significant. It does reduce the
effect of the noise, but the noise filtering is not strong.
The SNLP optimizer approximates the FEA characterization with Response Surfaces (RS). With
the FEA-approximation and with light evaluation of the cost function, SNLP has a good approxi-
mation of the cost function in terms of the optimization variables. This approximation allows the
SNLP optimizer to estimate the location of improving points. The overall cost approximations are
more accurate. This allows the SNLP optimizer a faster practical convergence speed than that of
quasi Newton.
The SNLP Optimizer creates the response surface using a polynomial approximation from the FEA
simulation results available from past solutions. The response surface is most accurate in the local
vicinity. The response surface is used in the optimization loop to determine the gradients and calcu-
late the next step direction and distance. The response surface acts as a surrogate for the FEA simu-
lation, reducing the number of FEA simulations required and greatly speeding the problem.
Convergence improves as more FEA solutions are created and the response surface approximation
improves.
The SNLP method is similar to the Sequential Quadratic Programming (SQP) method in two ways:
Both are sequential, updating the optimizer state to the current optimal values and iterating.
Sequential optimization can be thought of as walking a path, step by step, toward an optimal goal.
SNLP and SQP optimizers are also similar in that both use local and inexpensive surrogates. How-
ever, in the SNLP case, the surrogate can be of a higher order and is more generally constrained.
The goal is to achieve a surrogate model that is accurate enough on a wider scale, so that the search
procedures are well lead by the surrogate, even for relatively large steps. All functions calculated
by the supporting finite element product (for example, Maxwell 3D or HFSS) is assumed to be
expensive, while the rest of the cost calculation (for example, an extra user-defined expression) —
which is implemented in Optimetrics — is assumed to be inexpensive. For this reason, it makes
sense to remove inexpensive evaluations from the finite element problem and, instead, implement
them in Optimetrics. This optimizer holds several advantages over the Quasi Newton and Pattern
Search optimizers.
Most importantly, due to the separation of expensive and inexpensive evaluations in the cost calcu-
lation, the SNLP optimizer is more tightly integrated with the supporting FEA tools. This tight inte-
gration provides more insight into the optimization problem, resulting in a significantly faster
optimization process. A second advantage is that the SNLP optimizer does not require cost-deriva-
tives to be approximated, protecting against uncertainties (noise) in cost evaluations. In addition to
derivative-free state of the RS-based SNLP, the RS technique also proves to have noise suppression
properties. Finally, this optimizer allows you to use nonlinear constraints, making this approach
much more general than either of the other two optimizers.
Related Topics
Optimization Setup for SNLP Optimizer
Sequential Mixed Integer NonLinear Programming
The Sequential Mixed Integer Nonlinear Programming (SMINLP) optimizer is equivalent to the
SNLP optimizer with only one difference. Many problems require variables take only discrete val-
ues. One example might be to optimize on the number of turns in a coil. To be able to optimize on
number of turns or quarter turns, the optimizer must handle discrete optimization variables. The
SMINLP optimizer can mix continuous variables among the integers, or can have only integers,
and works if all variables are continuous. The setup resembles the setup for SNLP, except that you
must flag the integer variables.supporting integer variables. You can set up internal variables based
on the integer optimization variable.
For example, consider N to be an integer optimization variable. By definition it can only assume
integer values. You can establish another variable, which further depends on this one: K = 2.345 *
N, or K = sin(30 * N). This way K has a discrete value, but is not necessarily integer. Or, one can
use N directly as a design parameter.
Related Topics
Optimization Setup for SMINLP Optimizer
Genetic Algorithm
Genetic Algorithm (GA) optimizers are part of a class of optimization techniques called stochastic
optimizers. They do not use the information from the experiment or the cost function to determine
where to further explore the design space. Instead, they use a type of random selection and apply it
in a structured manner. The random selection of evaluations to proceed to the next generation has
the advantage of allowing the optimizer to jump out of a local minima at the expense of many ran-
dom solutions which do not provide improvement toward the optimization goal. As a result, the GA
optimizer will run many more iterations and may be prohibitively slow.
The Genetic Algorithm search is an iterative process that goes through a number of generations
(see picture below). In each generation some new individuals (Children / Number of Individuals)
are created and the grown population participates in a selection (natural-selection) process that in
turn reduces the size of the population to a desired level (Next Generation / Number of Individuals).
When a smaller set of individuals must be created from a bigger set, the GA selects individuals
from the original set. During this process, better fit (in relation to the cost function) individuals are
preferred. In the elitist selection, simply the best so many individuals are selected, but if you turn
on the roulette selection, then the selection process gets relaxed. An iterative process starts select-
ing the individuals and fills up the resulting set, but instead of selecting the best so many, we use a
roulette wheel that has for each selection-candidate divisions made proportional to the fitness level
(relative to the cost function) of the candidate. This means that the fitter the individual is, the larger
the probability of his survival will be.
Related Topics
Optimization Setup for Genetic Algorithm Optimizer
Optimization Variables in Design Space
Cost Function
Advanced Genetic Algorithm Optimizer Options
Optimization Variables and the Design Space
Once the optimization variables are specified, the optimizer handles each of them as an n-dimen-
sional vector x. Any point in the design space corresponds to a particular x-vector and to a design
instance. Each design instance may be evaluated via FEA and assigned a cost value; therefore, the
n
cost function is defined over the design space (cost(x): R → R , where n is the number of optimi-
zation variables.
In practice, a solution of the minimization problem is sought only on a bounded subset of the Rn
space. This subset is called the feasible domain and is defined via linear constraints.
Note • You can define more than one optimization analysis setup per design.
• Once you have created an optimization analysis setup, you can copy and paste it,
and then make changes to the copy, rather than redoing the whole process for minor
changes.
To provide a broad range of capability, Optimetrics incorporates the following types of numerical
optimizers:
• Sequential Nonlinear Programming (SNLP)
• Sequential Mixed Integer Nonlinear Programming (SMINLP)
• Quasi Newton
• Pattern Search
• Genetic Algorithm
Click on the links above to view the setup procedure for each optimizer. Options for the analysis
are listed in the table.
The following optional optimization solution setup options can also be used:
• Modify the starting variable value.
• Modify the minimum and maximum values of variables that will be optimized.
• Exclude variables from optimization.
• Modify the values of fixed variables that are not being optimized.
• Set the minimum and maximum step size between solved design variations (For the Quasi
Newton and Patterns Search optimizers, Variables tab).
• Set the minimum and maximum focus size. (For the SNLP and SMINLP optimizers, Vari-
ables tab).
• Set Linear constraints.
• Request that Optimetrics solve a parametric sweep before an optimization analysis.
• Request that Optimetrics solve a parametric sweep during an optimization analysis.
• Automatically update optimized variables to the optimal values during an optimization or
after an optimization analysis is completed.
• Change the norm used for the cost function calculation (Advanced Option)
Note Sweeping or using a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
Related Topics
Optimization Overview
Choosing an Optimizer
Optimization Setup for the Quasi Newton Optimizer
Following is the procedure for setting up an optimization analysis using the Quasi Newton Opti-
mizer. Once you have created a setup, you can Copy and Paste it, and then make changes to the
copy, rather than redoing the whole process for minor changes.
1. Set up the variables you want to optimize in the Design Properties dialog box.
2. Click HFSS >Optimetrics Analysis>Add Optimization .
The Setup Optimization dialog box appears.
3. Under the Goals tab, select the optimizer by selecting Quasi Newton from the Optimizer
pull-down list. Selecting Quasi Newton enables the Acceptable Cost and Noise fields.
4. Type the maximum number of iterations you want Optimetrics to perform during the optimiza-
tion analysis in the Max. No. of Iterations text box.
5. Under Cost Function, add a cost function by selecting the Setup Calculations button to open
the Add/Edit Calculation dialog.
6. Type the value of the cost function at which the optimization process should stop in the
Acceptable Cost text box.
7. Type the cost function noise in the Noise text box.
8. If you want to select a Cost Function Norm Type:
• Check the Show Advanced Option check box.
The Cost Function Norm Type pull-down list appears.
• Select L1, L2, or Maximum.
A norm is a function that assigns a positive value to the cost function.
For L1 norm the actual cost function uses the sum of absolute weighted values of the indi-
vidual goal errors. For L2 norm (the default) the actual cost function uses the weighted
sum of squared values of the individual goal error. For the Maximum norm the cost func-
tion uses the maximum among all the weighted goal errors. (For further details, see Expla-
nation of the L1, L2, and Max Norms in Optimization.)
The norm type doesn’t impact goal setting that use as condition the “minimize” or “maxi-
mize” scenarios.
9. In the Variables tab, specify the Min/Max values for variables included in the optimization,
and the Min/Max Step Size for the analysis.
You may also override the variable starting values by clicking the Override checkbox and
entering the desired value in the Starting Value field.
10. In the General tab, specify whether Optimetrics should use the results of a previous Paramet-
ric analysis or perform one as part of the optimization process.
Enabling the Update design parameters’ value after optimization checkbox will cause Opti-
metrics to modify the variable values in the nominal design to match the final values from the
optimization analysis.
11. Under the Options tab, if you want to save the field solution data for every solved design vari-
ations in the optimization analysis, select Save Fields And Mesh.
Note Do not select this option when requesting a large number of iterations as the data
generated will be very large and the system may become slow due to the large I/O
requirements.
You may also select Copy geometrically equivalent meshes to reuse the mesh when geome-
try changes are not required, for example when optimizing on a material property or source
excitation.This will provide some speed improvement in the overall optimization process.
Optimization Setup for the Pattern Search Optimizer
Following is the procedure for setting up an optimization analysis using the Pattern Search Opti-
mizer. Once you have created a setup, you can Copy and Paste it, and then make changes to the
copy, rather than redoing the whole process for minor changes.
1. Set up the variables you want to optimize in the Design Properties dialog box.
2. Click HFSS >Optimetrics Analysis>Add Optimization .
The Setup Optimization dialog box appears.
3. Under the Goals tab, select the optimizer by selecting Pattern Search from the Optimizer
pull-down list. Selecting Pattern Search enables the Acceptable Cost and Noise fields.
4. Type the maximum number of iterations you want Optimetrics to perform during the optimiza-
tion analysis in the Max. No. of Iterations text box.
5. Under Cost Function, add a cost function by selecting the Setup Calculations button to open
the Add/Edit Calculation dialog.
6. Type the value of the cost function at which the optimization process should stop in the
Acceptable Cost text box.
7. Type the cost function noise in the Noise text box.
8. If you want to select a Cost Function Norm Type:
• Check the Show Advanced Option check box.
The Cost Function Norm Type pull-down list appears.
• Select L1, L2, or Maximum.
A norm is a function that assigns a positive value to the cost function.
For L1 norm the actual cost function uses the sum of absolute weighted values of the indi-
vidual goal errors. For L2 norm (the default) the actual cost function uses the weighted
sum of squared values of the individual goal error. For the Maximum norm the cost func-
tion uses the maximum among all the weighted goal errors. (For further details, see Expla-
nation of the L1, L2, and Max Norms in Optimization.)
The norm type doesn’t impact goal setting that use as condition the “minimize” or “maxi-
mize” scenarios.
9. In the Variables tab, specify the Min/Max values for variables included in the optimization,
and the Min/Max Step Size for the analysis.
You may also override the variable starting values by clicking the Override checkbox and
entering the desired value in the Starting Value field.
10. In the General tab, specify whether Optimetrics should use the results of a previous Paramet-
ric analysis or perform one as part of the optimization process.
Enabling the Update design parameters’ value after optimization checkbox will cause Opti-
metrics to modify the variable values in the nominal design to match the final values from the
optimization analysis.
11. Under the Options tab, if you want to save the field solution data for every solved design vari-
ations in the optimization analysis, select Save Fields And Mesh.
Note Do not select this option when requesting a large number of iterations as the data
generated will be very large and the system may become slow due to the large I/O
requirements.
You may also select Copy geometrically equivalent meshes to reuse the mesh when geome-
try changes are not required, for example when optimizing on a material property or source
excitation.This will provide some speed improvement in the overall optimization process.
Optimization Setup for the SNLP Optimizer
Following is the procedure for setting up an optimization analysis using the Sequential Nonlinear
Programming (SNLP) Optimizer. Once you have created a setup, you can Copy and Paste it, and
then make changes to the copy, rather than redoing the whole process for minor changes.
1. Set up the variables you want to optimize in the Design Properties dialog box.
2. Click HFSS >Optimetrics Analysis>Add Optimization .
The Setup Optimization dialog box appears.
3. Under the Goals tab, select the optimizer by selecting Sequential Nonlinear Programming
from the Optimizer pull-down list.
4. Type the maximum number of iterations you want Optimetrics to perform during the optimiza-
tion analysis in the Max. No. of Iterations text box.
5. Under Cost Function, add a cost function by selecting the Setup Calculations button to open
the Add/Edit Calculation dialog.
6. If you want to select a Cost Function Norm Type:
• Check the Show Advanced Option check box.
The Cost Function Norm Type pull-down list appears.
• Select L1, L2, or Maximum.
A norm is a function that assigns a positive value to the cost function.
For L1 norm the actual cost function uses the sum of absolute weighted values of the indi-
vidual goal errors. For L2 norm (the default) the actual cost function uses the weighted
sum of squared values of the individual goal error. For the Maximum norm the cost func-
tion uses the maximum among all the weighted goal errors. (For further details, see Expla-
nation of the L1, L2, and Max Norms in Optimization.)
The norm type doesn’t impact goal setting that use as condition the “minimize” or “maxi-
mize” scenarios.
7. In the Variables tab, specify the Min/Max values for variables included in the optimization,
and the Min/Max Focus for the analysis.
You may also override the variable starting values by clicking the Override checkbox and
entering the desired value in the Starting Value field.
8. In the General tab, specify whether Optimetrics should use the results of a previous Paramet-
ric analysis or perform one as part of the optimization process.
Enabling the Update design parameters’ value after optimization checkbox will cause Opti-
metrics to modify the variable values in the nominal design to match the final values from the
optimization analysis.
9. Under the Options tab, if you want to save the field solution data for every solved design vari-
ations in the optimization analysis, select Save Fields And Mesh.
Note Do not select this option when requesting a large number of iterations as the data
generated will be very large and the system may become slow due to the large I/O
requirements.
You may also select Copy geometrically equivalent meshes to reuse the mesh when geome-
try changes are not required, for example when optimizing on a material property or source
excitation.This will provide some speed improvement in the overall optimization process.
Optimization Setup for the SMINLP Optimizer
Following is the procedure for setting up an optimization analysis using the Sequential Mixed Inte-
ger Nonlinear Programming (SMINLP) Optimizer. Once you have created a setup, you can Copy
and Paste it, and then make changes to the copy, rather than redoing the whole process for minor
changes.
1. Set up the variables you want to optimize in the Design Properties dialog box.
2. Click HFSS >Optimetrics Analysis> Add Optimization .
The Setup Optimization dialog box appears.
3. Under the Goals tab, select the optimizer by selecting Sequential Mixed Integer Nonlinear
Programming from the Optimizer pull-down list.
4. Type the maximum number of iterations you want Optimetrics to perform during the optimiza-
tion analysis in the Max. No. of Iterations text box.
5. Under Cost Function, add a cost function by selecting the Setup Calculations button to open
the Add/Edit Calculation dialog.
6. If you want to select a Cost Function Norm Type:
Note Do not select this option when requesting a large number of iterations as the data
generated will be very large and the system may become slow due to the large I/O
requirements.
You may also select Copy geometrically equivalent meshes to reuse the mesh when geome-
try changes are not required, for example when optimizing on a material property or source
excitation.This will provide some speed improvement in the overall optimization process.
Optimization Setup for the Genetic Algorithm Optimizer
Following is the procedure for setting up an optimization analysis using the Genetic Algorithm
Optimizer. Once you have created a setup, you can Copy and Paste it, and then make changes to
the copy, rather than redoing the whole process for minor changes.
1. Set up the variables you want to optimize in the Design Properties dialog box.
2. Click HFSS >Optimetrics Analysis>Add Optimization .
The Setup Optimization dialog box appears.
3. Under the Goals tab, select the optimizer by selecting Genetic Algorithm from the Optimizer
pull-down list.
Setting up an Optimetrics Analysis 15-29
HFSS Online Help
4. Click the Setup... button to modify the Advanced Genetic Algorithm Optimizer Options.
5. Under Cost Function, add a cost function by selecting the Setup Calculations button to open
the Add/Edit Calculation dialog.
6. If you want to select a Cost Function Norm Type:
• Check the Show Advanced Option check box.
The Cost Function Norm Type pull-down list appears.
• Select L1, L2, or Maximum.
A norm is a function that assigns a positive value to the cost function.
For L1 norm the actual cost function uses the sum of absolute weighted values of the indi-
vidual goal errors. For L2 norm (the default) the actual cost function uses the weighted
sum of squared values of the individual goal error. For the Maximum norm the cost func-
tion uses the maximum among all the weighted goal errors. (For further details, see Expla-
nation of the L1, L2, and Max Norms in Optimization.)
The norm type doesn’t impact goal setting that use as condition the “minimize” or “maxi-
mize” scenarios.
7. In the Variables tab, specify the Min/Max values for variables included in the optimization,
and the Min/Max Focus for the analysis.
You may also override the variable starting values by clicking the Override checkbox and
entering the desired value in the Starting Value field.
8. In the General tab, specify whether Optimetrics should use the results of a previous Paramet-
ric analysis or perform one as part of the optimization process.
Enabling the Update design parameters’ value after optimization checkbox will cause Opti-
metrics to modify the variable values in the nominal design to match the final values from the
optimization analysis.
9. Under the Options tab, if you want to save the field solution data for every solved design vari-
ations in the optimization analysis, select Save Fields And Mesh.
Note Do not select this option when requesting a large number of iterations as the data
generated will be very large and the system may become slow due to the large I/O
requirements.
You may also select Copy geometrically equivalent meshes to reuse the mesh when geome-
try changes are not required, for example when optimizing on a material property or source
excitation.This will provide some speed improvement in the overall optimization process.
pleted, the optimization continues by performing another iteration, that is, by solving another
design variation.
If the maximum number of iterations has not been reached, the optimizer performs iterations until
the acceptable cost function is reached or until the optimizer cannot proceed as a result of other
optimization setup constraints, such as when it searches for a variable value with a step size smaller
than the minimum step size.
Note The Genetic Algorithm optimizer does not use the Max. No. of Iterations criteria.
Acceptable Cost
The acceptable cost is the value of the cost function at which the optimization process should stop;
otherwise known as the stopping criterion.The cost function value must be equal to or below the
acceptable cost value for the optimization analysis to stop. The acceptable cost may be a negative
value.
Related Topics
Cost Function
Adding a Cost Function
Cost Function Noise
The numerical calculation of the electromagnetic field introduces various sources of noise to the
cost function, particularly because of changes in the finite element mesh. You must provide the
optimizer with an estimate of the noise. The noise indicates whether a change during the solution
process is significant enough to support achievement of the cost function.
For example, if the cost function, c, is
2
c = 10000 ⋅ S 11
where |S11| is the magnitude of the reflection coefficient, at the minimum, |S11| is expected to be
very small, S 11 ≈ 0 .
From the solution setup, the error in |S11| is expected to be E S11 ≈ 0.01 . The perturbed cost func-
tion is therefore
2
c perturbed = 10000 ⋅ ( S 11 + E S11 )
min
Near the minimum, the error in the cost function Ec is given by
2
E c = c perturbed – c min = 10000 ⋅ ( 0.0 + 0.01 ) – ( 10000 ⋅ 0.0 ) = 1.0
Following is the general procedure for adding a cost function with a single goal:
1. Under the Goals tab of the Setup Optimization dialog box, click Setup Calculations...
The Add/Edit Calculation dialog box is displayed.
2. In the Add/Edit Calculation dialog box, follow these general steps to set up a cost function.
a. Set the Context for the calculation.
b. Choose the Category of available data type depending upon the Solution type of the
design being optimized.
c. Select the Quantity to add to the Calculated Expression field. Available quantities
depend upon the Category selection.
d. You may optionally make a selection from the function list to apply to the calculated
expression.
e. When the Calculation Expression has the desired equation, click Add Calculation to
add the expression to the cost function table.
f. Repeat to add additional calculations to the cost function or click Done to exit the Add/
Edit Calculation dialog box and return to Setup Optimization.
3. To modify the Solution on which the calculation is based, click in the Solution column and
select the solution from which the cost function is to be extracted from the pull-down list.
4. To edit the calculation on which to base the cost function goal, select Edit from the pull-down
list.
5. In the Condition text box, click one of the following conditions from the pull-down list:
<= Less than or equal to
= Equal to
>= Greater than or equal to
Minimize Reduce the cost function to a minimum value
Maximize Identify a maximized condition
6. In the Goal text box, type the value of the solution quantity that you want to be achieved dur-
ing the optimization analysis. If the solution quantity is a complex calculation, the goal value
must be complex; two goal values must be specified. The Minimize and Maximize options do
not require you to specify a Goal value.
7. Optionally, if you have multiple goals and want to assign higher or lower priority to a goal,
type a different value for the goal's weight in the Weight text box. The goal with the greater
weight is given more importance. If the goal is a complex value, the weight value must be
complex; two weight values must be specified. The weight value cannot be variable dependent.
Note Click the Edit Goal/Weight button to open the Edit Goal Value/Weight dialog box
where you can modify weights for all goals simultaneously; as well as, set the Goal
Values to expressions.
8. Specify other options (such as acceptable cost, noise, and number of passes), and then click
OK.
The optimization stops when the solution quantity meets the acceptable cost criterion.
Related Topics
Setting a Goal Value
Cost Function
Acceptable Cost
Goal Weight
Adding/Editing a Cost Function Calculation
The Add/Edit Calculation dialog box allows you to define the mathematical equation for one or
multiple cost functions. It represents the calculation to be performed on the optimization variables
to compare to the goal values. To set up a calculation for a cost function:
1. In the Context section of the dialog:
• Select the Report Type with a pull-down selection list containing the available types for
this design.
• Select the Solution from the drop down selection list. This lists the available setups and
sweeps. As a minimum, the LastAdaptive solution is available.
• Select the Geometry from the drop down selection list or select none (the default). This
modifies the list of quantities available to the ones that apply to the specific geometry.
2. The Output Variables button opens the Output Variables dialog box allowing you to create
special output variables to be used in the cost function.
3. The Calculated Expression field in the Trace tab is used to enter the equation to be used for
the cost function. To enter an expression, you may type it directly into the field or use the Cat-
egory, Quantity, and Function lists as follows:
• Select the Category, these depend on the Solution type and the design. This lets you spec-
ify the category of information to be used in the cost function.
• Select a Quantity from the list. Available quantities depend upon the Solution type, as
well as the Geometry and Category selection. Selecting a Quantity automatically enters it
into the Calculated Expression field.
• Select a Function to apply to the value in the calculated expression.
• For swept variables, the RangeFunction button opens the Set Range Function dialog to
apply functions to the expression that apply over the sweep range.
4. The Calculation Range tab applies to swept variables and allows you to specify the range of
the sweep over which to apply the calculation.
5. When the desired Calculated Expression has been obtained, click the Add Calculation but-
ton to add the entry to the cost function table. You may add multiple entries to the table simply
by changing the Calculated Expression and using the Add Calculation button.
6. To update or edit a selected cost function, enter the desired Calculated Expression and click the
3. After you select a variable from the Variable pull-down list, you can select a range of values
for the calculation range as follows:
a. Select Range.
b. In the Start text box, type the starting value of the range.
c. In the Stop text box, type the final value of the range.
4. To select a single value for the calculation range:
a. Select Single Value.
b. In the Value text box, type the value of the variable at which the cost function goal is to be
extracted.
5. Click Update, and then click OK.
Setting a Goal Value
A goal is the value you want a solution quantity to reach during an optimization analysis. It can be
a real value or a complex value. If the solution quantity is a complex calculation, the goal value
must be complex. You can type the goal value in the Goal text box. Alternatively, you can use the
Edit Goal/Value Weight dialog box to specify the goal value as a single value, a mathematical
expression, or a value dependent on a variable such as frequency.
Related Topics
Specify a single goal value.
Specify an expression as the goal value.
Specify a variable-dependent goal value.
Specifying a Single Goal Value
1. Under the Goals tab in the Setup Optimization dialog box, click Edit Goal/Weight.
The Edit Goal/Weight dialog box appears.
2. Under the Goal Value tab, click Simple Numeric Value from the Type list.
3. If the goal value is complex, click real/imag in the pull-down list to the right if you want
to specify the real and imaginary parts of the goal value.
Alternatively, click mag/ang if you want to specify the magnitude and angle of the goal
value.
4. Type the goal value in the Goal Value table.
If the goal value is complex, type both parts of the goal value in the text box below the
Goal Value heading. For example, type 1, 1 to specify the real part of the goal value as 1
and the imaginary part as 1.
If the goal value is real, type a real goal value in the text box below the Goal Value head-
ing.
5. Click OK.
The goal value you specified appears in the Goal text box.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
5. Type a corresponding goal value for that variable value in the text box below the Goal
Value heading.
6. Click Add to add another row to the reference curve.
7. Repeat steps 4, 5, and 6 until you have specified the reference curve.
8. Click OK.
The goal value is listed as being variable dependent in the Goal text box.
Goal Weight
If an optimization setup has a cost function made up of multiple goals, you can assign a different
weight to each goal. The goal with the greater weight is given more importance during the cost cal-
culation.
The error function value is a weighted sum of the sub-goal errors. Each sub-goal, at each frequency
at which it is evaluated, gives rise to a (positive) error value that represents the discrepancy
between the simulated response and the goal value limit. If the response satisfies the goal value
limit, then the error value is 0. Otherwise, the error value depends on the differences between the
simulated response and the respective goal limit. The error function may be defined as follows:
G Nj
Wj
∑ ∑ ei------
Nj
j i
where
• G is the number of sub-goals.
• Wj is the weight factor associated with the jth sub-goal.
• Nj is the number of frequencies for the jth sub-goal.
• ei is the error contribution from the jth sub-goal at the ith frequency.
The value of ei is determined by the band characteristics, target value, and the simulated response
value. The choices for band characteristics are <=, =, and >=.
= ei = si – gi
⎧ 0 si ≥ gi
>= ei = ⎨
⎩ gi – si si < gi
If the total error value is within the acceptable cost, the optimization stops.
Related Topics
Adding a Cost Function
Cost Function
Note If you choose to solve a parametric setup before an optimization analysis, a variable's
starting value is ignored if a more appropriate starting value is calculated for it during the
parametric analysis.
Note To revert to the default starting value, clear the Override checkbox.
Related Topics
Setting the Min. and Max. Variable Values for Optimization
Step Size
Setting the Min and Max Focus
Modifying the Starting Variable Value for Sensitivity Analysis
Modifying the Starting Variable Value for Statistical Analysis
Setting the Min. and Max. Variable Values for Optimization
For every optimization setup, Optimetrics automatically sets the minimum and maximum values it
will consider for a variable being optimized. Optimetrics sets a variable's minimum value equal to
approximately 50% of its starting value. (The starting value is the variable's current value set for
the nominal design.) Optimetrics sets the variable's maximum value equal to approximately 150%
of the starting value. During the optimization analysis, variable values that lie outside of this range
are not considered.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
Related Topics
Override the default min and max variable values for a single optimization setup.
Setting up an Optimetrics Analysis 15-39
HFSS Online Help
Change the default min and max variable values for every optimization setup.
Overriding the Min. and Max. Variable Values for a Single Optimization Setup
1. In the Setup Optimization dialog box, click the Variables tab.
All of the variables that were selected for optimization analysis are listed.
2. Type a new value in the Min or Max text box for the value you want to override, and then
press Enter.
The Override option is now selected. This indicates that the value you entered is used for this
optimization analysis; the variable's current Min or Max value in the nominal design is
ignored.
• Alternatively, you can select the Override option first, and then type a new value in the
Min or Max text box.
3. Optionally, click a new unit system in one of the Units text boxes.
To revert to the default minimum and maximum values, clear the Override option.
Changing the Min. and Max. Variable Values for Every Optimization Setup
1. Make sure that the variable's minimum and maximum values are not being overridden in any
single optimization setup.
2. If the variable is a design variable, do the following: Click HFSS>Design Properties.
If the variable is a project variable, do the following: Click Project>Project Variables.
The Properties dialog box appears.
3. Select Optimization.
4. Type a new value in the Min or Max text box for the value you want to override, and then
press Enter.
5. Click OK.
When Optimetrics solves an optimization setup, it does not consider variable values that lie
outside of this range.
Step Size
To make the search for the minimum cost value reasonable, the search algorithm is limited in two
ways. First, you do not want the optimizer to continue the search if the step size becomes irrelevant
or small. This limitation impacts the accuracy of the final optimum. Second, in some cases you do
not want the optimizer to take large steps either. In case the cost function is suspected to possess
large variations in a relatively small vicinity of the design space, large steps may result in too many
trial steps, which do not improve the cost value. In these cases, it is safer to proceed with limited
size steps and have more frequent improvements.
For these two limitations, the optimizer uses two independent distance measures. Both are based on
user-defined quantities: the minimum and maximum step limits for individual optimization vari-
ables. Since the particular step is in a general direction, these measures are combined together in
order to derive the limitation for that particular direction.
The step vector between the ith and (i+1)th iterate is as follows:
si = xi + 1 – xi
T
si = si si
A more general distance measure incorporates some "stretching" of the design space:,
T T
si = s i D Ds i
D
where the matrix D incorporates the linear operation of the stretching of design space. The simplest
case is when the D matrix is diagonal, meaning that the design space is stretched along the orthog-
onal direction of the base vectors.
si <1
D min
si >1
D max
where Dmax has diagonal elements equal to the inverse of Max. Step values of the corresponding
optimization variables.
Related Topics
Setting the Min. and Max. Step Sizes
Cost Function
Adding a Cost Function
Setting up an Optimetrics Analysis 15-41
HFSS Online Help
Related Topics
Step Size
Setting the Min and Max Focus
For the SNLP, SMINLP and Genetic Algorithm optimizers, the min focus and max focus criteria
allow you to specify a sub-range of parameter values where the optimizer should look when per-
forming the optimization. This focus box is where you suspect the optimal solution will be, so it is
a hint for the optimizer.
is sent.
Equalizing the influence of different optimization variables.
The optimizer seeks optimal values for the optimization variables. These variables are usually
quantities with specified units. The change in one variable could be measured in [mm] and the
change in other variable could be measured in [mA]. Instead of those units, the optimizer uses
internal abstract units, so that a change in one variable changes the design behavior about as much
as the same change in another variable, where changes are measured in the respective internal
abstract units. When you define the focus box, the unit of the abstract internal unit is defined as the
difference of the upper and lower focus limits. This way you can use the focus box to equalize the
influence of different optimization variables on the design behavior.
To set the Min and Max Focus values:
1. In the Setup Optimization dialog box, click the Variables tab.
2. Optimetrics displays Min. Focus and Max. Focus columns, with default values for each vari-
able to be optimized.
If you do not have an initial guess based on your knowledge of the problem, make the focus
box equal to the domain; that is, the physical limits. This tells SNLP to search the entire deci-
sion space.
• In the Min. Focus text box, type the minimum value of the focus range. Optionally, mod-
ify the unit system in the Units text box.
• In the Max. Focus text box, type the maximum value of the focus range. Optionally, mod-
ify the unit system in the Units text box.
• Click OK.
Solving a Parametric Setup Before an Optimization
Solving a parametric setup before an optimization setup is useful for guiding Optimetrics during an
optimization.
To solve a parametric setup before an optimization setup:
1. In the Setup Optimization dialog box, click the General tab.
2. In the Parametric Analysis pull-down list, click the parametric setup you want Optimetrics to
solve before optimization.
Note The parametric setup must include sweep definitions for the variables you are
optimizing.
Related Topics
Solving a Parametric Setup During an Optimization
Solving a Parametric Setup During an Optimization
Solving a parametric setup during an optimization analysis is useful when you want Optimetrics to
solve every design variation specified in the parametric setup at each optimization iteration. A cost
function goal could then depend on the value of the variable swept in the parametric setup.
To solve a parametric setup during an optimization analysis:
1. In the Setup Optimization dialog box, click the General tab.
2. In the Parametric Analysis pull-down list, click the parametric setup you want Optimetrics to
solve during an optimization.
3. Select Solve the parametric sweep during optimization.
4. Optionally, you can adjust the sweep values to be used during the optimization.
a. Click on the Goal tab, click Setup Calculations to specify a calculation.
The Add/Edit Calculation dialog box is displayed.
b. Click the Calculation Range tab.
c. Click the Edit button for the sweep to be modified.
d. In the pop-up dialog box, select the sweep values to use.
e. Close the pup-up dialog box. Click Done to close the Add/Edit Calculation dialog.
Automatically Updating a Variable's Value After Optimization
When Optimetrics finds an optimal variable value by solving an optimization setup, it can automat-
ically update that variable's current value set for the nominal model to the optimal value.
1. In the Setup Optimization dialog box, click the General tab.
2. Select Update design parameters' values after optimization.
When optimization is complete, the current variable value for each optimized variable is
changed to the optimal value.
Changing the Cost Function Norm
You can select the norm to be used in the calculation of the cost goal.
1. In the Setup Optimization dialog box, click the Goals tab.
2. Select Show Advanced Options.
3. Select a norm from the pull-down in the Cost Function Norm Type field. The options are L1,
L2, and Maximum. L2 is the default.
Related Topics
Explanation of L1, L2 and Max Norms in Optimization
Cost Function
N
Cost = Max W i ⋅ ε i
1
For all the above situations N is the number of individual goals wi εi are individual weighting fac-
tors and residual error respectively. A minimization of the cost function is performed during opti-
mization since it makes sense to minimize the error in the sense of the chosen norm type.
The graphical representation of the error is possible and depends upon the actual condition being
used. If a “<” condition is used, the error can be represented as below:
If a “=” condition is used, the error is double-sided and can be represented as below:
The norm type doesn’t impact goal setting that use as condition the “minimize” or “maximize” sce-
narios. Note that when using “minimize” or “maximize” settings for the condition there should be a
single goal setting which in this case coincides with the cost function.
Related Topics
Cost Function
Example of a More Complex Cost Function
As an example of a more sophisticated cost function, consider the figure. It belongs to a connector
simulated in HFSS with more than four ports.
The cost function given here concentrates only on a signal sent into port in_1. Suppose the specifi-
cations to be met are: reflection, backward cross talk and forward cross talk all smaller than or
equal to -20 dB, of which the forward cross talk is the most important.
The first three entries in the cost function enforce those specifications, with the weight for the for-
ward cross talk being a larger number than the other weights. The actual values for the weights are
somewhat arbitrary and serve as examples only. For this cost function, as long as specifications are
not met, the optimizer puts the most effort in getting the forward cross talk close to its specification.
Once the three specifications have been satisfied, their contributions to the cost function become
zero, and only the fourth entry remains. Remember that the connector has more than four ports, so
satisfying the given specs does not guarantee maximum transmission.
The fourth line tries to maximize the transmission by asking for S(out_1, in_1) to be 0 dB. That will
never be reached, but its presence forces the optimizer to improve the connector a bit beyond the
specifications.
The cost function norm type specifies how the four lines are combined into one cost function with
one value. With L1 and L2, all four contribute simultaneously, rather than only the largest of the
four at any one time.
Related Topics
Cost Function
Adding a Cost Function
• Uniform Mutation Probability: If this is more than zero (recommendation is to have still
a small probability here), then there will be some children whose features are simply a
completely random design (design variables randomly selected over the domain).
• Individual Mutation Probability controls, for each child, the likelihood of a mild muta-
tion.
• Variable Mutation Probability. If the child will be mutated, this probability controls at
the variable level the likelihood of a mutation of the variables.
• Standard Deviation is the standard deviation of the selected distribution that is being
used for the mutation and it is measured relatively to the optimization-domain.
9. When you have completed the Reproduction setup in the Genetic Algorithm Optimizer
Reproduction Setup dialog, click OK to close it and return to the Advanced Genetic Algo-
rithm Optimizer Options dialog.
10. In the Advanced Genetic Algorithm Optimizer Options dialog, specify the children as a
Number of Individuals.
11. Set the Pareto Front value.
This is the number of the very best individuals (identified relative to the cost function) to keep
for future generations.
12. Set the Next Generation parameters. The Next Generation is selected from the Parents, the
children, and the Pareto front.
• Number of individuals value field -- specify the number of individuals to survive to form
the next generation for the optimizer to use.
• Roulette selection checkbox -- if checked, this enables the Selection pressure value
field. This number defines how many times more probable is the selection of the best indi-
vidual over the worst individual in an elementary spin of the roulette wheel.
13. Click OK to accept the settings for the Genetic Algorithm and to close the dialog.
Related Topics
Setting up an Optimization Analysis
Adding a cost function
Optimization Overview
Acceptable Cost
Explanation of L1, L2, and Max Norms in Optimization
Choosing an Optimizer
Note Do not select this option when requesting a large number of iterations as the data
generated will be very large and the system may become slow due to the large I/O
requirements.
You may also select Copy geometrically equivalent meshes to reuse the mesh when geome-
try changes are not required, for example when optimizing on a material property or source
excitation.This will provide some speed improvement in the overall optimization process.
The following optional sensitivity analysis setup options can also be used:
• Modify the starting variable value.
• Modify the minimum and maximum values of variables that will be solved.
• Exclude variables from the sensitivity analysis.
• Set the initial displacement.
• Modify the values of fixed variables that are not being modified during the sensitivity
analysis.
• Set linear constraints.
• Request that Optimetrics solve a parametric sweep before a sensitivity analysis.
• You can also request that Optimetrics solve a parametric sweep during a sensitivity anal-
ysis.
Note Sweeping or using a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
Related Topics
Sensitivity Analysis Overview
Setting the Maximum Iteration Per Variable
Setting the Maximum Iterations Per Variable
The Max. No. of Iterations/Sensitivity Variable value is the maximum number of design varia-
tions that Optimetrics solves per variable during a sensitivity analysis. This value is a stopping cri-
terion; if the maximum number of iterations has been completed, the sensitivity analysis stops. If
the maximum number of iterations has not been completed, the sensitivity analysis continues by
performing another iteration, that is, by solving another design variation. It performs iterations until
the approximate error in master output value is reached or until Optimetrics cannot proceed as a
result of other sensitivity setup constraints, such as when it searches for a variable value that is
larger than the maximum value.
To set the maximum number of iterations for a sensitivity analysis:
• Under the Calculations tab of the Setup Sensitivity Analysis dialog box, type a value in the
Max. No. of Iterations/Sensitivity Variable text box.
Related Topics
Setting Up an Output Parameter
Setting Up an Output Parameter
Following is the general procedure for adding an output parameter to a sensitivity setup:
1. Under the Calculations tab of the Setup Sensitivity Analysis dialog box, click Setup Calcu-
lations to open the Add/Edit Calculations dialog box.
2. In the Add/Edit Calculations dialog box, set up output parameter calculations to be evaluated
for sensitivity.
3. To modify the solution from which the output parameter is to be extracted, click in the Solu-
tion column and select from the options in the pop-up list.
4. You can modify the Calculation specified by clicking on the output parameter in the table and
selecting Edit.
5. For output parameters based on swept variable, you must choose a single value in the Calcula-
tion Range at which to evaluate the output parameter.
6. If the output parameter is based on a swept variable, in the Calculation Range column, set the
value of the variable at which the output parameter is to be computed.
7. If you have more than one output parameter, select Master Output if you want Optimetrics to
Setting up an Optimetrics Analysis 15-53
HFSS Online Help
use the output parameter to base its selection of solved design variations.
Note During a sensitivity analysis, the design variations that Optimetrics selects to solve are
close to the design point, but not so close that numerical noise (from the finite element
mesh) affects the analysis. The algorithm that Optimetrics uses to determine the design
variations to solve must be based on only one output parameter and that output
parameter’s numerical noise. If you have defined more than one output parameter, be
sure to select Master Output for the output variable on which you want the selection of
design variations to be based.
Related Topics
Selecting a Master Output
Specifying a Solution Quantity for an Output Parameter
When setting up an output parameter, you must identify the solution quantity on which to base the
output parameter. Solution quantities are specified by mathematical expressions that are composed
of basic quantities, such as matrix parameters; and output variables.
The Add/Edit Calculation dialog box allows you to define the mathematical equation for one or
multiple output parameters. To set up an output parameter:
1. In the Context section of the dialog:
• Select the Report Type with a pull-down selection list containing the available types for
this design.
• Select the Solution from the drop down selection list. This lists the available setups and
sweeps. As a minimum, the LastAdaptive solution is available.
• Select the Geometry from the drop down selection list or select none (the default). This
modifies the list of quantities available to the ones that apply to the specific geometry.
• When selecting a geometry, you may also be required to specify a point within the geome-
try where the calculation is to be performed.
2. The Output Variables button opens the Output Variables dialog box allowing you to create
special output variables to be used in the output parameter.
3. The Calculation Expression field in the Trace tab is used to enter the equation to be used for
the output parameter. To enter an expression, you may type it directly into the field or use the
Category, Quantity, and Function lists as follows:
• Select the Category, these depend on the Solution type and the design. This lets you spec-
ify the category of information to be used in the output parameter.
• Select a Quantity from the list. Available quantities depend upon the Solution type, as
well as the Geometry and Category selection. Selecting a Quantity automatically enters it
into the Calculation Expression field.
• Select a Function to apply to the value in the calculated expression.
• For swept variables, the RangeFunction button opens the Set Range Function dialog to
apply functions to the expression that apply over the sweep range.
4. The Calculation Range tab applies to swept variables and allows you to specify the range of
the sweep over which to apply the calculation.
5. When the desired Calculation Expression has been obtained, click the Add Calculation but-
ton to add the entry to the calculation table in the Setup Sensitivity Analysis dialog box. You
may add multiple entries to the table simply by changing the Calculation Expression and
using the Add Calculation button.
6. To update or edit a selected cost function, enter the desired Calculation Expression and click
the Update Calculation button.
7. Click Done to return to the Setup Sensitivity Analysis dialog box.
Note The solution quantity you specify must be able to be evaluated to a single, real number.
Related Topics
Setting the Calculation Range of an Output Parameter
Setting the Calculation Range of an Output Parameter
The calculation range of a solution quantity determines the intrinsic variable value at which the
solution quantity is to be extracted. For a sensitivity setup, the calculation range must be a single
value. If you specified that the solution quantity be extracted from a frequency sweep solution, by
default, Optimetrics uses the starting frequency in the sweep. If you specified that the solution be
extracted from the last adaptive solution, Optimetrics uses the adaptive frequency defined in the
solution setup.
1. Under the Calculations tab of the Setup Sensitivity Analysis dialog box, click in the Calcula-
tion Range column of the table for the calculation to be modified.
The Edit Calculation Range dialog box appears.
2. In the table, click the Edit button in the row to be modified.
If you choose to solve a parametric setup during the sensitivity analysis, the variables swept in
that parametric setup are available in the pop-up list dialog box. If you sweep a variable in the
parametric setup that is also a sensitivity variable, that variable is excluded from the sensitivity
analysis.
Other examples of available variables include frequency, if you selected an S-parameter solu-
tion quantity; and phi or theta, if the solution quantity is a radiated field quantity.
3. Click on the value for the calculation range in the list and dismiss the pop-up dialog box.
4. Click OK in the Edit Calculation Range dialog box to accept the new value for the intrinsic
variable, and return to the Setup Sensitivity Analysis dialog box.
Related Topics
Setting Up an Output Parameter
Modifying the Starting Variable Value for Sensitivity Analysis
The design point of the sensitivity analysis is the starting value of the sensitivity variable and is
usually the first variation to be solved. Optimetrics automatically sets the starting value of a vari-
able to be the current value set for the nominal design. You can modify the design point for each
sensitivity setup.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
1. In the Setup Sensitivity Analysis dialog box, click the Variables tab.
All of the variables that were selected for the sensitivity analysis are listed.
2. Type a new value in the Starting Value text box for the value you want to override, and then
press Enter.
The Override option is now selected. This indicates that the value you entered is to be used for
this sensitivity analysis; the current value set for the nominal model will be ignored.
• Alternatively, you can select the Override option first, and then type a new variable value
in the Starting Value text box.
3. Optionally, click a new unit system in one of the Units text boxes.
To revert to the default starting value, clear the Override option.
Related Topics
Setting Up a Sensitivity Analysis
Setting the Min. and Max. Variable Values
For every sensitivity setup, Optimetrics automatically sets the minimum and maximum values that
it will consider for a sensitivity variable. Optimetrics sets a variable’s minimum value equal to
approximately one-half its starting value. (The starting value is the variable’s current value set for
the nominal design.) Optimetrics sets the variable’s maximum value equal to approximately 1.5
times the starting value. During sensitivity analysis, variable values outside this range are not con-
sidered.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
Related Topics
Override the default minimum and maximum variable values for a single sensitivity setup.
Change the default minimum and maximum variable values for every sensitivity setup.
Overriding the Min. and Max. Variable Values for a Single Sensitivity Setup
1. In the Setup Sensitivity Analysis dialog box, click the Variables tab.
All of the variables that were selected for sensitivity analysis are listed.
2. Type a new value in the Min or Max text box for the value you want to override, and then
press Enter.
The Override option is now selected. This indicates that the value you entered is to be used for
this sensitivity analysis; the variable's current Min or Max value set in the nominal design is
ignored.
• Alternatively, you can select the Override option first, and then type a new value in the
Min or Max text box.
3. Optionally, click a new unit system in one of the Units text boxes.
To revert to the default minimum and maximum values, clear the Override option.
Related Topics
Setting Up a Sensitivity Analysis
Changing the Min. and Max. Variable Values for Every Sensitivity Setup
1. Make sure the variable's minimum and maximum values are not being overridden in any sensi-
tivity setup.
2. If the variable is a design variable, do the following: Click HFSS>Design Properties.
If the variable is a project variable, do the following: Click Project>Project Variables.
The Properties dialog box appears.
3. Select Sensitivity.
4. Type a new value in the Min or Max text box for the value you want to override, and then
press Enter.
When Optimetrics solves a sensitivity setup, it does not consider variable values that lie out-
side of this range.
Related Topics
Setting Up a Sensitivity Analysis
Setting the Initial Displacement
The initial displacement is the difference in a variable's starting value and the next solved design
variation. During the sensitivity analysis, Optimetrics does not consider an initial variable value
that is greater than this step size away from the starting variable value.
1. In the Setup Sensitivity Analysis dialog box, click the Variables tab.
2. Optimetrics displays the Initial Disp. column, with default values for each sensitivity variable.
3. In the Initial Disp. text box, type the initial displacement value. Optionally, modify the unit
system in the Units text box.
Related Topics
Setting Up a Sensitivity Analysis
Solving a Parametric Setup Before a Sensitivity Analysis
Solving a parametric setup before a sensitivity setup is useful for guiding Optimetrics in a sensitiv-
ity analysis.
Note The parametric setup must include sweep definitions for the sensitivity variables.
Note Sweeping or using a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
9. If you want to save the field solution data for the design variations solved during analysis,
select Save Fields.
Related Topics
Statistical Analysis Overview
Related Topics
Setting up a Statistical Analysis
Specifying the Solution Quantity to Evaluate for Statistical Analysis
When you add a statistical setup, you can identify one or more solution quantities to evaluate. The
solution quantities are specified by mathematical expressions that are composed of basic quantities.
When you view the results, HFSS displays the distribution of the solution quantities.
1. In the Calculations tab of the Setup Statistical Analysis dialog box, click Setup Calcula-
tions.
The Add/Edit Calculations dialog box is displayed, allowing you to define one or more math-
ematical expressions for statistical evaluation.
2. In the Context section of the dialog:
• Select the Report Type with a pull-down selection list containing the available types for
this design.
• Select the Solution from the drop down selection list. This lists the available setups and
sweeps. As a minimum, the LastAdaptive solution is available.
• Select the Geometry from the drop down selection list or select none (the default). This
modifies the list of quantities available to the ones that apply to the specific geometry.
• When selecting a geometry, you may also be required to specify a point within the geome-
try where the calculation is to be performed.
3. The Output Variables button opens the Output Variables dialog box allowing you to create
special output variables to be used in the output parameter.
4. The Calculation Expression field in the Trace tab is used to enter the equation to be used for
the solution quantities. To enter an expression, you may type it directly into the field or use the
Category, Quantity, and Function lists as follows:
• Select the Category, these depend on the Solution type and the design. This lets you spec-
ify the category of information to be used in the output parameter.
• Select a Quantity from the list. Available quantities depend upon the Solution type, as
well as the Geometry and Category selection. Selecting a Quantity automatically enters it
into the Calculation Expression field.
• Select a Function to apply to the value in the calculated expression.
• For swept variables, the RangeFunction button opens the Set Range Function dialog to
apply functions to the expression that apply over the sweep range.
5. The Calculation Range tab applies to swept variables and allows you to specify the range of
the sweep over which to apply the calculation.
6. When the desired Calculation Expression has been obtained, click the Add Calculation but-
ton to add the entry to the calculation table in the Setup Statistical Analysis dialog box. You
may add multiple entries to the table simply by changing the Calculated Expression and using
the Add Calculation button.
7. To update or edit a selected cost function, enter the desired Calculation Expression and click
Note The solution quantity you specify must be able to be evaluated to a single, real number.
Related Topics
Setting up a Statistical Analysis
Setting the Maximum Iterations for a Statistical Analysis
Setting the Solution Quantity's Calculation Range
The calculation range of a solution quantity determines the intrinsic variable value at which the
solution quantity is extracted. For a statistical setup, the calculation range must be a single
value.For a Driven Modal or Driven Terminal design, if you specified that the solution be extracted
from the last adaptive solution, Optimetrics uses the adaptive frequency defined in the solution
setup. If you specified that the solution quantity be extracted from a frequency sweep solution,
Optimetrics will use the starting frequency in the sweep by default.The calculation range should be
set during the setup of the solution quantity for statistical evaluation. In order to modify the calcula-
tion range, do the following:
1. Under the Calculations tab of the Setup Statistical Analysis dialog box, click in the Calcula-
tion Range column of the table for the calculation to be modified.
The Edit Calculation Range dialog box appears.
2. In the table, click the Edit button in the row to be modified.
If you choose to solve a parametric setup during the statistical analysis, the variables swept in
that parametric setup are available in the pop-up list dialog box. If you sweep a variable in the
parametric setup that is also a statistics variable, that variable is excluded from the statistics
analysis.
Other examples of available variables include frequency, if you selected an S-parameter solu-
tion quantity; and phi or theta, if the solution quantity is a radiated field quantity.
3. Click on the value for the calculation range in the list and dismiss the pop-up dialog box.
4. Click OK in the Edit Calculation Range dialog box to accept the new value for the intrinsic
variable, and return to the Setup Statistical Analysis dialog box.
Related Topics
Setting up a Statistical Analysis
Setting the Distribution Criteria
For every statistical setup, Optimetrics automatically sets the distribution criteria to be uniform
within a 10% tolerance of the variable's starting value. You can modify the distribution type and
criteria for a single statistical setup or for every statistical setup.
Related Topics
Override the default distribution criteria for a single statistical setup.
Uniform distributions such as variable “length” above use only the Tolerance value, and do not
have a cutoff probability.
Edit Distribution
When setting the distribution type for a variable, you have the option of changing the distribution
parameters from the default values.
1. If the distribution type is Gaussian, do the following:
a. Type the lower limit of the distribution in the Cutoff Probability text box. This is a value
=>0 and < 0.1.
b. Type the mean value of the distribution in the Mean text box.
c. Type the standard deviation of the distribution in the Std Dev text box.
HFSS solves design variations using a Gaussian distribution within the specified mean
and standard deviation values.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
1. In the Setup Statistical Analysis dialog box, click the Variables tab.
All of the variables selected for the statistical analysis are listed.
2. Type a new value in the Starting Value text box for the value you want to override, and then
press Enter.
The Override option is now selected. This indicates that the value you entered is to be used for
this statistical analysis; the current value set for the nominal model will be ignored.
• Alternatively, you can select the Override option first, and then type a new variable value
Tuning Overview
Tuning a variable is useful when you want to manually modify its value and immediately perform
an analysis of the design. For example, it is useful after performing an optimization analysis, in
which Optimetrics has determined an optimal variable value, and you want to fine tune the value to
see how the design results (for example, traces in a report) are affected.
A design can be updated after a tuning analysis to reflect a design variation solved during a tuning
analysis and the results, including field solutions if you select Save Fields and Mesh on the
Options tab of the setup.
Related Topics
Tuning a Variable
Tuning a Variable
If you want to ensure that tuning does not resolve variations already solved by an optimization
setup, you must check Save Fields and Mesh in the Options tab of that setup.
1. Before a variable can be tuned, you must specify that you intend for it to be used during a tun-
ing analysis in a Project or Design Properties dialog box.
2. After running the simulation, click HFSS >Optimetrics>Tune .
The Tune dialog box appears., listing the variables which have been included for tuning.
5. In the Sim. Setups column, select the solution setup you want HFSS to use when it solves the
specified design variation.
HFSS solves the analysis using the solution setup you select. If you select more than one,
results are generated for all selected solution setups.
Checking the Tune box for a Sim Setup enables the Real Time checkbox, the Browse available
variations checkbox, and the Snap radio buttons. Clearing the Tune box disables those selec-
tions.
6. In the Nominal text box for the variable you want to tune, type the value of the variable you
want HFSS to solve, or drag the slider to increase or decrease its value.
Warning Variable values must be single real numbers, or expressions that evaluate to single
real numbers. Complex numbers cannot be used as the values of variables in any
optimetric analysis.
Alternatively, if you want HFSS to solve a range of values, specify a linear range of values
with a constant step size:
a. Select the Sweep check box. (You must have cleared the Browse available variations
checkbox).
b. In the text box below the Step value, type the starting value in the variable range.
c. Type the step size, or difference between variable values in the sweep definition, in the
Step text box. The step size determines the number of design variations between the start
and stop values. HFSS solves the model at each step in the specified range, including the
start and stop values.
d. In the text box just below the variable name, type a stopping value in the variable range.
7. If you have cleared the Real Time checkbox, click Tune to apply the changes you have made
to the variable values.
Note Sweeping or using a complex variable is not allowed in any optimetrics setup, including
optimization, statistical, sensitivity, and tuning setups.
8. Changing a variable value with the sliders of by typing in the text field enables the Save and
Reset buttons.
Clicking Save opens a Save As dialog with a name field, and an Apply tuned values to design
checkbox.
Clicking Reset changes the variable values back to what they were originally.
9. If you have changed one or more included variables, clicking Close on the Tuning dialog
opens the Apply Tuned Variation dialog. This lists the included variables and the values for
each tuning. If you have tried multiple values, they are listed, and the current value is high-
lighted. Select another value to change the highlight. Click OK to apply the highlighted values
to the design, or Don’t Apply to ignore the changes from the original variable values.
If you have applied variant values, you should see the new values listed in the relevant Design
or Project Properties lists of variables and values, and if the changes affect plots or physical
features of a model, those changes should also appear.
Click Cancel to close the dialog and go back to the Tune dialog.
Related Topics
Applying a Tuned State to a Design
Tuning Overview
Resetting Variable Values after Tuning
Applying a Tuned State to a Design
You can apply the variable values solved during a tuning analysis to the nominal design in one of
the following three ways:
• When closing the Tune dialog box:
1. Click Close to exit the Tune dialog box.
The Apply Tuned Variation dialog box appears.
2. Click the design variation you want to apply, and then click OK.
The variable values from the solved design variation become the current variable values
for the nominal design. If you have applied variant values, you should see the new values
listed in the relevant Design or Project Properties lists of variables and values, and if the
changes affect plots or physical features of a model, those changes should also be appar-
ent.
• When saving a tuned state.
• When reverting to a tuned state.
Saving a Tuned State
You can save the settings in the Tune dialog box, including the variable values you specified for a
tuning analysis. Saved states are only available during the current session of the Tune dialog box;
they are not stored for the next session.
1. After tuning a variable, click Save in the Tune dialog box.
A Save As dialog box appears.
ues.
4. Click OK to return to the Tune dialog box.
Related Topics
Reverting to a Saved Tuned State
Reverting to a Saved Tuned State
You can revert to a group of saved settings in the Tune dialog box, including the variable values
you specified for a specific tuning analysis. Saved states are only available during the current ses-
sion of the Tune dialog box; they are not stored for the next session.
1. In the Tune dialog box, click Revert.
The Revert dialog box appears.
2. Type the name of the tuned state you want to apply or click a name in the pull-down list.
3. Select Apply tuned values to design if you want to update the model to the selected tuned
state's variable values.
4. Click OK to return to the Tune dialog box.
Related Topics
Saving a Tuned State
Resetting Variable Values after Tuning
If you want to reset variable values to the values they were set to when you started the current ses-
sion of the Tune dialog box:
• After tuning a variable, click Reset in the Tune dialog box.
Solutions for the design variations solved during tuning analyses remain available for post pro-
cessing.
when an adaptive analysis is specified in the solution setup or when you request that fields be saved
for each solved point in a frequency sweep. If the nominal design is not included in the optimiza-
tion analysis, all field solutions are deleted.
To save the fields for all design variations solved during an optimization analysis:
1. Open an Edit Sweep dialog by either adding a sweep or right-click on a an existing sweep to
view the short cut menu and selecting Properties.
2. Select the Options tab.
3. Click the Save Fields And Mesh check box. Optionally, select Copy geometrically equiva-
lent mashes.
HFSS will save the field solution data for every solved design variation in the optimization
setup.
Related Topics
Saving Field Solutions for Optimetrics Analyses
Saving Field Solutions for a Sensitivity Setup
In order to preserve disk space, by default HFSS does not save field solution data for every solved
design variation in a sensitivity analysis. It only saves the field solutions for the nominal design
when an adaptive analysis is specified in the solution setup or when you request that fields be saved
for each solved point in a frequency sweep. If the nominal design is not included in the sensitivity
analysis, all field solutions are deleted.
To save the fields for all design variations solved during a sensitivity analysis:
1. Open the Setup Sensitivity Analysis dialog box.
2. Select the Options tab.
3. Click the Save Fields And Mesh check box. Optionally, select Copy geometrically equiva-
lent mashes.
HFSS will save the field solution data for every solved design variation in the sensitivity anal-
ysis.
Related Topics
Saving Field Solutions for Optimetrics Analyses
Saving Field Solutions for a Tuning Analysis
In order to preserve disk space, by default HFSS does not save field solution data for every design
variation solved in a tuning analysis. It only saves the field solutions for the nominal design when
an adaptive analysis is specified in the solution setup or when you request that fields be saved for
each solved point in a frequency sweep. If the nominal design is not included in the tuning analysis,
all field solutions are deleted.
To save the fields for all design variations solved during a tuning analysis:
• In the Tuning dialog box, select Save Fields.
HFSS will save the field solution data for every solved design variation in a tuning analysis.
Related Topics
Saving Field Solutions for Optimetrics Analyses
Saving Field Solutions for a Statistical Setup
In order to preserve disk space, by default HFSS does not save field solution data for every design
variation solved in a statistical analysis. It only saves the field solutions for the nominal design
when an adaptive analysis is specified in the solution setup or when you request that fields be saved
for each solved point in a frequency sweep. If the nominal design is not included in the statistical
analysis, all field solutions are deleted.
To save the fields for all design variations solved during a statistical analysis:
1. Open the Setup Statistical Analysis dialog box.
2. Select the Options tab.
3. Click the Save Fields And Mesh check box. Optionally, select Copy geometrically equiva-
lent mashes.
HFSS will save the field solution data for every solved design variation in the statistical setup.
Related Topics
Saving Field Solutions for Optimetrics Analyses
Note This option is available with all Optimetrics setups, and is applied when these
analyses generate geometrically-equivalent values. However, it is most relevant
to parametric sweep, where such equivalences are more likely to occur.
The Copy geometrically equivalent mesh option is not recommended for use when the frequency
is varying, since meshing is frequency-dependent. You may wish to turn this option off when the
first geometrically equivalent variation requires numerous passes after the initial mesh, but the
other geometrically-equivalent variations require fewer additional passes, so that it is cheaper to
start with the initial mesh each time.
Note Alternatively, you can select the Override option first, and then clear the Include option
for the variable you want to exclude.
3. Click OK.
Note Alternatively, you can select the Override option first, and then type a new value in the
Value text box.
Linear Constraints
Once the optimization variables are specified, the optimizer handles each of them as an n-dimen-
sional vector x. Any point in the design space corresponds to a particular x-vector and to a design
instance. Each design instance may be evaluated via Finite Element Analysis and assigned a cost
value; therefore, the cost function is defined over the design space (cost(x): Rn→R), where n is the
number of optimization variables.
In practice, a solution of the minimization problem is sought only on a bounded subset of the Rn
space. This subset is called the feasible domain and is defined via linear constraints.
You may constrain the feasible domain of a design variable by defining linear constraints for the
optimization process. The feasible domain is defined as the domain of all design variables that sat-
isfy all upper and lower bounds and constraints. Linear constraints are defined by the following
inequalities:
∑ αij xi < cj ∀j
i
where
• αij are coefficients.
• cj is a comparison value for the jth linear constraint.
• xi is the ith designer parameter.
Related Topics
Setting a Linear Constraint
5. Click a condition, < (less than) or > (greater than), from the pull-down list.
6. Type the inequality value, which should be a constant value, in the text box to the right of the
condition.
7. Click OK.
You return to the Linear Constraint dialog box. The left-hand side of the constraint appears
in the LHS (left-hand side) column. The condition is listed in the Condition column, and the
inequality value is listed in the RHS (right-hand side) column.
Related Topics
Modifying a Linear Constraint
Deleting a Linear Constraint
Linear Constraints
Modifying a Linear Constraint
1. Do one of the following:
• If you are setting up an optimization analysis: In the Setup Optimization dialog box,
click the Variables tab.
• If you are setting up a sensitivity analysis: In the Setup Sensitivity Analysis dialog box,
click the Variables tab.
2. Click Linear Constraint.
The Linear Constraint dialog box appears.
3. Click the row listing the constraint you want to modify, and then click Edit.
The Edit Linear Constraint dialog box appears.
4. Optionally, click a Coeff text box and type a new coefficient value.
5. Optionally, click a different condition, < (less than) or > (greater than), in the pull-down list.
6. Optionally, type a different inequality value in the text box to the right of the condition, and
then click OK.
You return to the Linear Constraint dialog box. The new coefficient value, the condition, and
the inequality value appear in the LHS (left-hand side), Condition, and RHS (right-hand side)
columns, respectively.
Deleting a Linear Constraint
1. Do one of the following:
• If you are setting up an optimization analysis: In the Setup Optimization dialog box,
click the Variables tab.
• If you are setting up a sensitivity analysis: In the Setup Sensitivity Analysis dialog box,
click the Variables tab.
2. Click Linear Constraint.
The Linear Constraint dialog box appears.
3. Click the row listing the constraint you want to delete, and then click Delete.
The constraint is deleted.
Related Topics
Viewing an Optimetrics Solution's Profile Data
Viewing an Optimetrics Solution's Profile Data
At any time during or after the Optimetrics solution process, you can see an overview of the com-
puting resources or profile data that was used by HFSS as it solved each design variation. Optimet-
rics writes the variation information to the profile table before the solve. It then updates the entry
with end data (end time, elapsed time, etc) once the solve variation is completed.
1. In the project tree, right-click the Optimetrics solution setup of interest, and then click View
Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. Click the Profile tab.
3. Select the Optimetrics setup with the results you want to view from the pull-down list at the
top of the dialog box.
4. Optionally, to examine more detailed profile data for a specific design variation, do the follow-
ing:
a. Click a design variation in the table.
b. Click Solver Profile.
The Solutions dialog box appears with the profile data for the selected design variation.
The profile line for the matrix solver is in the following format:
Solver 123
where:
• 1 is the precision type: M (mixed) or D (double)
• 2 is the matrix data type: R (real) or C (complex)
• 3 is the symmetry type: S (symmetric), A (asymmetric), H (hermitian)
Related Topics
Viewing a Solution's Profile
Viewing Solution Data for an Optimetrics Design Variation
Viewing Results for Parametric Solution Quantities
1. In the project tree, right-click the parametric setup for which you want to view the results cal-
culated for the solution quantities, and then click View Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. Select the parametric setup with the results you want to view from the pull-down list at the top
of the dialog box.
3. If it is not already selected, select Table as the view type.
The results for the selected solution quantities are listed in table format for each solved design
variation. The variation column in the table lists the entries in order. Clicking the Vision
header inverts the order. Clicking other headers sorts the entries by value, and clicking again
inverts the order.
4. Optionally, select Show complete output name.
The complete name of the solution for which the results are being displayed will be listed in
the column headings.
5. Optionally, click a design variation in the table, and then click Apply (at the far right side of
the dialog box).
The design displayed in the 3D Modeler window is changed to represent the selected design
variation.
Related Topics
Plotting Solution Quantity Results vs. a Swept Variable
Plotting Solution Quantity Results vs. a Swept Variable
To plot solution quantity results versus a swept variable's values on a rectangular (x - y) plot:
1. In the project tree, right-click the parametric setup for which you want to view the results, and
then click View Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. If it is not already selected, select Plot as the view type.
3. Select the variable with the swept values you want to plot on the x-axis from the X pull-down
list.
4. Only one sweep variable at a time can be plotted against solution quantity results. Any other
variables that were swept during the parametric analysis remain constant.
Optionally, to modify the constant values of other swept variables, do the following:
a. Click Set Other Sweep Variables Value.
The Setup Plot dialog box appears. All of the other solved variable values are listed.
b. Click the row with the variable value you want to use as the constant value in the plot, and
then click OK.
5. Select the solution quantity results you want to plot on the y-axis from the Y pull-down list.
The xy plot appears in the view window.
6. Right-click in the plot area to get the shortcut menu where you can set modify the plots display
properties, print, copy to the clipboard, or export the data to a file.
Viewing Cost Results for an Optimization Analysis
To view cost values versus completed iterations in data table format:
1. In the project tree, right-click the optimization setup for which you want to view the cost
results, and then click View Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. Under the Result tab, select Table as the view type, if it is not already selected.
The cost value at each solved design variation is listed in table format.
Setting up an Optimetrics Analysis 15-87
HFSS Online Help
3. Optionally, click a design variation in the table, and then click Apply.
HFSS now points to the selected design variation as the nominal solution and as a result, the
design displayed in the Modeler window is changed to represent the selected design variation.
Click Revert to return the design in the view window to the original value.
Related Topics
Plotting Cost Data for an Optimization Analysis
Viewing Solution Data for an Optimetrics Design Variation
Plotting Cost Results for an Optimization Analysis
To view cost values versus completed iterations in rectangular (x-y) plot format:
1. In the project tree, right-click the optimization setup for which you want to view the cost
results, and then click View Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. Under the Result tab, select Plot as the view type.
A plot of the cost value at each iteration appears.
Viewing Output Parameter Results for a Sensitivity Analysis
To view actual output parameter values versus design point in data table format:
1. In the project tree, right-click the sensitivity setup for which you want to view the parameter
results, and then click View Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. Under the Result tab, select Table as the view type, if it is not already selected.
The following values are listed in table format:
• The regression value of the output parameter at the design point is listed in the Func.
Value column.
• The first derivative of the regression is listed in the 1st D column.
• The second derivative of the regression is listed in the 2nd D column.
3. Click Apply.
HFSS now points to the selected design variation as the nominal solution and as a result, the
design displayed in the Modeler window is changed to represent the selected design variation.
Click Revert to return the design in the view window to the original value.
Related Topics
Plotting Output Parameter Results for a Sensitivity Analysis
Viewing Solution Data for an Optimetrics Design Variation
Plotting Output Parameter Results for a Sensitivity Analysis
To plot output parameter results versus sensitivity variable values on a rectangular (xy) plot:
1. In the project tree, right-click the sensitivity setup for which you want to view the output
parameter results, and then click View Analysis Result on the shortcut menu.
The Post Analysis Display dialog box appears.
2. Under the Result tab, select Plot as the view type.
3. Select the sensitivity variable with the sweep values you want to plot on the x-axis from the X
pull-down list.
4. Select the output parameter results you want to plot on the y-axis from the Y pull-down list.
The xy plot appears in the Post Analysis Display dialog box.
The plot displays actual output parameter results for each solved design variation. It also dis-
plays a parabola that best fits these results. The parabola is a more accurate representation of
sensitivity around the design point than any individual solved design variation.
Viewing Distribution Results for a Statistical Analysis
1. In the project tree, right-click the statistical setup for which you want to view the distribution
results calculated for the solution quantities, and then click View Analysis Result on the short-
cut menu.
The Post Analysis Display dialog box appears.
2. Select the statistical setup with the results you want to view from the pull-down list at the top
of the dialog box.
3. To view the results in tabular form, select Table as the view type.
The distribution results for the selected solution quantities are listed in table format for each
solved design variation.
4. Optionally, click a design variation in the table, and then click Apply (at the far right side of
the dialog box).
The design displayed in the 3D Modeler window is changed to represent the selected design
variation.
5. To view the results in graphic format, select Plot as the view type.
6. Type the number of bins you want to plot on the x-axis.
7. Select the solution quantity for which you want to plot distribution results on the y-axis from
the Y pull-down list.
A histogram plot appears in the Post Analysis Display dialog box. It displays the distribution
of the selected solution quantity.
8. Optionally, click a design variation in the table, and then click Apply (at the far right side of
the dialog box).
HFSS now points to the selected design variation as the nominal solution and as a result, the
design displayed in the Modeler window is changed to represent the selected design variation.
Click Revert to return the design in the view window to the original value.
Related Topics
Plotting Distribution Results for a Statistical Analysis
5. When you have added the calculations of interest, click OK to save the setup.
An icon for the Design Xplorer setup appears under Optimization in the Project tree.
6. To create a .xml file with the setup information for Design Xplorer, first Save your project.
7. Then right-click on the setup and select Export External Connector Addin Configuration.
This displays a browser dialog that you can use to navigate your file system, and name and
saves the .xml file. The .xml file contains information regarding the HFSS path along with the
setup, variables, and simulation results that you specified.
8. If you have an ANSYS Workbench installation you can perform additional steps. You should
have provided a path to the Workbench installation in the Tools>General Options dialog Mis-
cellaneous tab, to provide a path.
9. Then click Create Workbench Project.
This lets you name a Workbench project containing the information in the setup. The ANSYS
Workbench will be launched with the connection to the HFSS project established. To this con-
nection, you can add a Design Xplorer Setup. See the documentation of Ansys Workbench for
details on Design Xplorer.
When HFSS has completed a solution, you can display and analyze the results in the following
ways:
• View solution data including the following: convergence information, computing resources
that were used during the solution process, mesh statistics, and matrices computed for the S-
parameters, impedances, and propagation constants during each adaptive, non-adaptive, or
sweep solution. For eigenmode solutions, you can view the real and imaginary parts of the fre-
quency and quality factor Q computed for each eigenmode. Solution data can also be viewed
while HFSS is generating a solution.
• View analysis results for Optimetrics solutions.
• Plot field overlays - representations of basic or derived field quantities - on surfaces or objects.
• Create 2D or 3D reports of S-parameters, basic and derived field quantities, and radiated field
data.
• Plot the finite element mesh on surfaces or within 3D objects.
• Create animations of field quantities, the finite element mesh, and defined project variables.
• Scale an excitation’s magnitude and modify its phase.
• Export Transfer File for ANSYS
Note Except in the case of non-model boxes drawn in the global coordinate system (CS), non-
model objects cannot be used for any fields post processing operation You can use non-
model boxes drawn in the global CS for post processing operations, including
integration and solution domaining.
Note If you receive a message that the eigenmodes have not converged, it may indicate that
the existing mesh is too coarse. You may need to refine the mesh.
Related Topics
Viewing Solution Data for an Optimetrics Design Variation
Viewing the Number of Completed Passes
At any time during the solution process, you can view the number of adaptive passes (solve —
error analysis — refine cycles) that have been completed and that have yet to be completed. When
the solution is complete, you can view the number of adaptive passes that were performed. If the
solution converged within the specified stopping criteria, fewer passes than requested may have
been performed.
To view the number of passes:
• In the project tree, right-click the solution setup of interest, and then click Convergence on the
shortcut menu.
The Solution Data window appears. The Convergence tab is selected.
The number of completed and remaining passes is listed in the Number of Passes area.
Viewing the Max Magnitude of Delta S Between Passes
For solutions with ports.
At any time during or after the solution process, you can view the maximum change in the
magnitude of the S-parameters between two consecutive passes. This information is available after
two or more passes are completed.
To view the maximum magnitude of delta S between passes:
• In the project tree, right-click the solution setup of interest, and then click Convergence on the
shortcut menu.
The Solution Data window appears. The Convergence tab is selected.
The Max. Mag. Delta S column lists the maximum magnitude of delta S from one pass to the
next.
The Max. Mag. Delta S area lists the target change in magnitude of delta S and the change in
magnitude of delta S between the last two solved passes.
Note Delta S is computed on the appropriate S-parameters - modal or terminal - after the S-
parameters have been de-embedded and renormalized.
Note You can renormalize mathematically, without having to re-solve, by accessing the
postprocessing tab on the port definition panel and de-selecting the Deembed selection
box.
Related Topics
Setting the Maximum Delta S Per Pass
Technical Notes: Maximum Delta S
Viewing the Output Variable Convergence
At any time during or after the solution process, you can view the real and imaginary values of the
output variable.
To view the output variable convergence, use the Reporter to create a plot that displays the output
variable values.
Related Topics
Specifying Expressions for Adaptive Convergence
Viewing the Delta Magnitude Energy
For designs with voltage sources, current sources, or incident waves. Not applicable to designs
with ports.
At any time during or after the solution process, you can view the difference in the relative energy
error from one adaptive pass to the next. The change in the magnitude of delta energy is available
after two or more passes are completed.
To view the delta magnitude E between passes:
• In the project tree, right-click the solution setup of interest, and then click Convergence on the
shortcut menu.
The Solution Data window appears. The Convergence tab is selected.
The Delta Mag. Energy column lists the delta energy from one pass to the next.
The Delta Mag. Energy area lists the target change in delta energy and the change in delta
Energy between the last two solved passes.
Related Topics
Setting the Maximum Delta Energy Per Pass
Technical Notes: Maximum Delta Energy
Note When the Mag S becomes small (near to zero) its phase becomes indefinite and insignificant due
to mathematical issues so that Phase Margin will be discarded.
Related Topics
Setting Matrix Convergence Criteria
Technical Notes: Phase Margin
Viewing the Max Delta (Mag S)
For solutions in which convergence criteria for specific S-matrix entries were specified.
At any time during or after the solution process, you can view the maximum difference of the S
matrix magnitudes between two consecutive passes. The Max Delta (Mag S) is available after two
or more passes are completed.
To view the Mag S between passes:
• In the project tree, right-click the solution setup of interest, and then click Convergence on the
shortcut menu.
The Solution Data window appears. The Convergence tab is selected.
The Max Delta (Mag S) column lists the Max Delta (Mag S) from one pass to the next.
Related Topics
Setting Matrix Convergence Criteria
Technical Notes: Max Delta (Mag S)
Viewing the Max Delta (Phase S)
For solutions in which convergence criteria for specific S-matrix entries were specified.
At any time during or after the solution process, you can view the maximum difference of the S
Matrix phase between two consecutive passes. The Max Delta (Phase S) is available after two or
more passes are completed.
To view the Max Delta (Phase S) between passes:
• In the project tree, right-click the solution setup of interest, and then click Convergence on the
shortcut menu.
The Solution Data window appears. The Convergence tab is selected.
The Max Delta (Phase S) column lists the Max Delta (Phase S) from one pass to the next.
Related Topics
Setting Matrix Convergence Criteria
Technical Notes: Max Delta (Phase S)
Viewing the Maximum Delta Frequency
For Eigenmode solutions.
At any time during the solution process, you can view the maximum delta frequency, the largest
percent difference in the resonant frequencies from one adaptive pass to the next. It is a measure of
the stability of the computed frequencies from pass to pass and is available after two or more passes
are completed.
To view the maximum delta frequency between passes:
• In the project tree, right-click the solution setup of interest, and then click Convergence on the
shortcut menu.
The Solution Data window appears. The Convergence tab is selected.
The Max Delta Freq. % column lists the maximum delta frequency from one pass to the next.
The Max Delta Freq. % area lists the target maximum delta frequency and the maximum
delta frequency between the last two solved passes.
Related Topics
Technical Notes: Maximum Delta Frequency
The matrix solver writes specific information in some of these fields as outlined below:
Task The matrix solver task reports the type of solution performed by the solver,
based on the physics of the problem. It is always of the form "Solver pdsn"
(e.g. Solver MRS2), where
• p, the precision type is: M (mixed) or D (double)
• d, the matrix data type is: R (real) or C (complex)
• s, the symmetry type is: S (symmetric), A (asymmetric), or H (hermitian)
• n, the number of processors used. You specify the number of available
processors on the local machine in the HFSS or HFSS-IE options. If a
solve does not use all available processors (local or distributed), the
number reported may be less than the number available.
Information: The matrix solver information line includes three sets of information (for
example, 960885 matrix, 3030MB disk offcore)
• # matrix: The size of the matrix that was solved (the number of
unknowns)
• # disk: The amount of hard disk space used during the calculation of the
matrix solution
• "offcore": After the disk information, the word "offcore" may appear.
This means that the solver could not place all of the data it needs to
calculate the matrix solution in physical memory. If this word does not
appear, then the solver was able to fit the necessary data into physical
memory (known as "in-core"). If the matrix solver must solve off-core,
smaller blocks of the data to be solved are created on disk, each block is
then solved in physical memory, and then the matrix solution is
reassembled. As a result of this additional processing, the time required to
calculate a solution is higher.
To Export the Profile data:
1. Open the Solution Data dialog with the Profile tab selected.
2. Click the Export Profile button.
This opens a file save dialog that lets you provide a file name and location.
3. Click Save.
The data is saved in a text file with a .prof extension.
Related Topics
Viewing an Optimetrics Solution’s Profile Data
and the previous value, and increments the Number of Values field.
Incrementing or deincrementing the Number of Values fields, and the clicking Update
Values updates the table based in the current Start and End value fields (given the range
restriction within the initial range).
The Delete button enabled only if a value is selected. Delete removes the selected value
and decrements the Number of Values field.
Click OK to apply the changes to the Solutions dialog Matrix Data tab and close the
Edit Sweep dialog, or Cancel to close the dialog without applying the changes.
If you choose to export the matrix data for the Fast or Interpolating sweep after modifying
the frequencies in the Edit Sweep dialog box, only those frequencies displayed under the
Matrix Data tab will be exported.
The data is displayed in the table. By default, Waveports are listed in alphabetical, then numer-
ical order, just as they appear in the excitation tree. To change the port order, change setting for
Default Matrix sort order in the HFSS or HFSS-IE General options. You may also want see
how you can Reorder Matrix Data.
7. Optionally, Check Passivity.
This passivity check tests whether the S-parameter data from HFSS is passive or not. If the S-
Matrix is not passive at one or more frequencies, this check displays a dialog that identifies the
worst frequency violation and identifies the passivity in that case.
Related Topics
Selecting the Matrix Display Format
Viewing Solution Data for an Optimetrics Design Variation
Exporting Matrix Data
Renaming Matrix Data
Reordering Matrix Data
Exporting Equivalent Circuit Data
Technical Notes: Passivity
The available formats depend on the matrix type being displayed. When selected, dB formatting
only applies to S -matrix data, even if other matrix types are displayed. The column heads in the
display identify the format for the matrix type.You can display matrix data in the following formats.
Magnitude, Phase Displays the magnitude and phase (in degrees) of the matrix type.
(deg)
Real, Imaginary Displays the real and imaginary parts of the matrix type.
dB, Phase (deg) Displays the magnitude in decibels and phase in degrees of the
matrix type.
Magnitude Displays the magnitude of the matrix type.
Phase (deg) Displays the phase in degrees of the matrix type.
Real Displays the real parts of the matrix type.
Imaginary Displays the imaginary parts of the matrix type.
dB Displays the magnitude in decibels of the matrix type.
Related Topics
Renaming Matrix Data
Reordering Matrix Data
Exporting Matrix Data
1. In the project tree, right-click the solution setup of interest, and then click Matrix Data on the
shortcut menu.
The Solution Data window appears. The Matrix Data tab is selected.
2. Select the type of matrix you want to view: S-matrix, Y-matrix, Z-matrix, Gamma, or Zo
(characteristic impedance.)
3. Click Export Matrix Data.
A file browser appears.
4. Type the name of the file you are exporting to in the File name text box.
5. Select one of the following file formats from the Save as type pull-down list:
*.nmf Neutral file format Neutral file format defined by the MAFET
Consortium. When you save to this format, you are
presented a dialog that lets you specify the number
of digits precision for the renormalizing impedance.
*.m MATLAB The Mathworks’ MATLAB file in which the
elements of the S-, Y-, or Z-matrix are arranged in a
series of rows.
*.cit Citifile Common Instrumentation Transfer and Interchange
file format. It is an ASCII format defined by
instrument and CAE designers.
6. For Touchstone files, you see a Combine Sweeps option on the Export Network Data solu-
tion dialog. This lets you combine sweeps into a single output file if:
• You can combine any combination of discrete, interpolating, and fast sweeps, as long as
the ranges don’t overlap except possibly at the endpoints. (Note that the interpolated
sweeps incorporate pre-solved data.)
• The files must not have overlaps in the frequencies. (They can meet at a single frequency.
For example, you can combine sweeps from 8 to 10 GHz with sweeps from 10 to 12 GHz,
and 8-10 GHz and 11-13GHz, but not sweeps from 9 to 11 GHz and 10 to 11 GHz.)
a. Select the Combine Sweeps button to display a Combine Interpolating Sweeps For
Export dialog with a list of sweeps.
b. Select the sweeps to combine and click Combine.
This closes the Combine Interpolating Sweeps for Export dialog.
7. Click Save.
The data is exported to the file.
• By default, wave ports are listed in alphabetical, then numerical order, just as they appear
in the excitation tree. You can change this order to creation order and back without invali-
dating the solution on the HFSS Options dialog.
• If you select Touchstone format, you are first presented with a dialog in which you can
specify the Number of Digits precision, and Override the Solution Renormalization. If so,
you co specify the export renormalizing impedance (an integer value). Here you also can
specify and whether to include Gamma and Impedance Comments, and Number of
Digits Precision (Default 15).
• If you select Neutral File Format, you are presented with a Specify Export Renormaliz-
ing Impedance dialog that lets you specify the Number of digits precision for the save
file.
Note If you modify the display of solved frequencies in an Interpolating or Fast sweep under
the Matrix Data tab (by clicking Edit Freqs and then modifying the values in the Edit
Sweep dialog box,) only those frequencies listed will be exported to the file.
Note If there are differential pairs, the sort order is still specified) in terms of the underlying
terminal names, but the entries that make up the pair should appear in the appropriate
sort location for the terminals that are used to define them.
will enable you to include wave effects in the circuit simulations. You can also export a W-Element
model for a port.
Note You must have a frequency sweep solution and five or more frequency points to
successfully export an equivalent circuit data file. See the Choosing Frequencies for
Full-Wave SPICE topic of the online help for suggestions about the frequency range of
the sweep.
The GUI lets you export full-wave Spice for a model that contains differential pairs, but
it will silently export the data in its original single-ended form. The full-wave Spice
model is a "broadband" equivalent circuit (that is, its S-parameters match those of the
HFSS solution across the whole frequency sweep range.)
Certain discrete sweeps permit Full-Wave SPICE exports. It is allowed if the discrete
data is evenly spaced, includes DC, and has at least 500 frequency points.
1. In the project tree, right-click the solution setup of interest, and then click Matrix Data on the
shortcut menu.
The Solution Data window appears. The Matrix Data tab is selected.
2. Click Equivalent Circuit Export.
The Equivalent Circuit Export Options dialog box appears.
3. Type the name or browse to the directory in which you want to store the data.
enables the text field for the file name, and depending on the format selection, other options
may be enabled.
• Desired Fitting Error (percent)
• Maximum Order
HFSS supports Full Wave Spice Export from a driven modal design as long as all ports have
exactly one mode each. However, HFSS does not support definition of differential pairs in a
driven modal design.
6. Optionally, select Use Common Ground to combine the negative reference nodes for all of
the ports into a single reference node.
7. Optionally, select Enforce Passivity. Selecting this enforces passivity in the output file. Pas-
sive devices can only dissipate or temporarily store energy, but never generate it. (You can also
check passivity from the Matrix Data tab using the Check Passivity button.)
This option is useful in cases where the transient simulation fails due to passivity violations in
the circuit model. This circuit model is based on fitting a rational function to the S-parameter
data computed by the field solver. Small errors in the data fitting can result in non-passive
behavior. Selecting the Enforce Passivity option will take more CPU time, but ensures that the
resulting model will be passive.
The passivity check tests whether the S-parameter data from HFSS is passive or not. For more
information see Passivity.
8. Optionally, select Lumped Element Export (Low Bandwidth) if you want to save the data as
a low-frequency circuit model using simple lumped elements (resistors, capacitors, inductors,
and dependent current sources). The low-bandwidth model is only going to be accurate in a
limited frequency range around the adaptive solution frequency
This option is not enabled for Spectre export.
9. Optionally, select Partial Fraction Expansion for Matlab if you want to specify a file that
expands the partial fractions for use in Matlab. The partial fractions involved describe the fre-
quency response of the low-bandwidth model from the previous step.
10. You can also select Combine Sweeps to select and combine available sweeps into a single out-
put file.
By option you can Export W-Element Data.
11. Click OK.
The S-matrices are written to the data file that you specified in the equivalent circuit data for-
mat.
Related Topics
Exporting W-Element Data
Note For the RLGC Format, if only a single frequency solution is selected (e.g. LastAdaptive)
then Rs and Gd parameters are ignored.
Related Topics
Technical Notes: Calculating the W-Elements
Viewing Mesh Statistics
To view an adaptive solution's mesh information, either during or after the solution process:
1. In the Project tree, right-click the solution setup of interest, and then click Mesh Statistics on
the shortcut menu.
The Solutions dialog box appears with the Mesh Statistics tab selected.
For HFSS projects, the table lists the design elements and for each includes: Num Elements,
Min edge length, Max edge length, RMS edge length, min tet vol., max tet vol., mean tet vol.
and standard deviation.
For HFSS-IE projects, the Mesh data table is similar but includes min, max, and mean element
Related Topics
Monitoring the Solution Process
Deleting Reports
Deleting Reports
To use Delete All Reports:
1. Click HFSS>Results>Delete All Reports. You can also rightclick on the Results folder in the
Project tree to display the shortcut menu, and click Delete All reports.
All items under the Results folder in the Project tree are removed.
To use Delete for a selected report:
1. Select a report icon in the Project tree, and right-click to display the shortcut menu.
2. Click Delete on the shortcut menu or the “X” icon on the toolbar to delete the selected report.
Related Topics
Clear Linked Data
Deleting Solution Data
The picture below shows the interface of the Steady-State Thermal solver after the link has been
defined. It also shows the commands, available through right-clicking, to Import the thermal Load
from HFSS or Maxwell and to Export the temperature distribution to HFSS or Maxwell.
Click OK.
5. For Maxwell transient solution types only, you must also specify the desired Start and Stop
Integration times for the power loss density distribution to be used in ANSYS Workbench.
6. When you are finished making the desired selections, click the Export button.
This opens a file browser in which you can specify a file name and location for the coupling
file you wish to export. The file is in ANSYS Link format, and uses a .xml extension.
7. Click Done to close the Export ANSYS Ansys Transfer File dialog box.
Related Topics
Export Transfer File for ANSYS
Exporting 3D Model Files
Exporting the Model Geometry to ANSYS Workbench
Re-solving After ANSYS Thermal Link Feedback
For HFSS Terminal solutions, you can select a Terminal Exciation Type as Incident Voltage or
Total Voltage.
For HFSS modal solutions and terminal solutions with the Terminal Exciation Type set as Inci-
dent Voltage, the dialog displays information for design sources in table format.
Note You may not enter a negative voltage. To obtain the equivalent of a negative magnitude,
add or subtract 180 degrees from the phase value.
If you use a design variable as a scaling factor note that solutions are invalidated if the
variable is changed.
If the model contains symmetry planes, the Edit Sources dialog alerts you that you may
need to adjust the scaling factor accordingly.
At least one source should be excited (non-zero). If you set all sources to zero, you will
receive a warning, but the values do go through.
4. In the Offset Phase text box, enter the new phase for the source.
The phase of the source is changed by the value that you enter.
5. Optionally, if your solution type is driven terminal, you may specify a complex reference
impedance:
a. For the selected terminal, select Terminated.
This disables the values to the left of the checkbox, and enables the Resistance and Reac-
tance text boxes. Use the scroll bar to view them.
b. Enter the Resistance and the Reactance and select the units. Ohms is the default.
6. By option, you can click a checkbox to Include Post Processing Effects.
Checking this box also enables an Apply button.
7. For HFSS, if an incident wave is present, use the radio buttons at the bottom of the panel to
select one of the following field types to use:
Scattered Fields The differential field formed by subtracting the incident field from the
total field.
Total Fields The physically measurable field that exists with the model present and a
non-zero incident field.
Incident Fields The plane-wave field that would exist in the absence of the model.
For HFSS-IE, these options do not appear in the Edit Sources dialog. The Port Processing
effects are always on, and the entered voltages in Edit Sources are always in TotalVoltage
form.
8. Click OK to apply the changes and close the dialog, or click Apply to view the changes with-
out closing the dialog.
The magnitude and phase are assigned to the selected excitation.
Note When you scale an excitation, keep in mind that the original value of the excitation
remains unchanged.
Related Topics
Guidelines for Scaling a Source’s Magnitude and Phase
Guidelines for Scaling a Source's Magnitude and Phase
When specifying the factor by which the value of the source is scaled, keep the following guide-
lines in mind:
For ports, driven • The excitation’s magnitude specifies time-averaged incident power in
modal case watts.
• If you are using a symmetry plane, remember to scale the input signal
appropriately. For example, if you have one symmetry plane, use an input
value of 0.5 watts to excite the full structure with 1 watt; if you have two
symmetry planes, use an input value of 0.25 watts to excite the full
structure with 1 watt, and so forth.
• Generally, use the default value of 1. This specifies that the solution’s E-
and H-fields be scaled such that the excitation wave delivers 1 watt of
power. To view the solution at some other power, enter a positive value.
• Only port-mode combinations with non-zero magnitudes will be used.
For voltage and • The source magnitude for voltage and current sources specifies peak
current sources value volts and peak value amperes, respectively.
• If you have defined multiple voltage and current sources, you can
"remove" them by setting their magnitudes to 0. This enables you to
easily observe the effects that individual or specific groups of sources
have on the problem.
For incident • Source magnitude specifies peak value E-field in volts per meter.
waves • When you scale the incident E-field, the scattered E-field and the total E-
field are scaled as well.
• This scaling factor affects all incident angles in the incident wave setup.
For ports, driven • The excitation’s magnitude specifies peak value volts. This is the sum of
terminal case the incident and reflected waves at this terminal. See the equations here.
For Eigenmodes • Source magnitude is unitless and represents a relative value.
• When you enter a scaling factor for an eigenmode the relative source
magnitude is amplified by this value. Exactly one eigenmode must be
excited by setting its scaling factor to a non-zero positive number.
Ports of Transient • See Ports and Edit Sources Behavior for Transient Network
Network solutions
When specifying the new phase for ports, generally use zero. This zero-phase solution results from
excitations phased in such a way that, at ωt = 0, peak values occur at the port faces.
Ports and Edit Sources Behavior for Transient Network
Transient Network solutions support the following port features:
1. Just as in Driven Terminal we have two types of ports namely wave ports and lumped ports.
2. Both port types are restricted to be single TEM terminal ports such as coax and gap ports.
3. Waveports are matched loaded.
4. Lumped ports are loaded with the user defined "Full Port Impedance".
5. Both ports support renormalization of the spectral quantities S-parameters and far fields
including antenna parameters.
6. Neither port supports renormalization of transient quantities.
Edit Sources involves specifying the incident voltages at the terminals of the ports not the total
voltages. This means that all ports are terminated with the port settings and if the edit source for a
given port is set to zero it means that port is loaded with the port setting and it does not imply a
short. As mentioned above, transient fields are not affected by any renormalization but the fre-
quency domain far fields and antenna parameters are affected by renormalization.
For HFSS Transient, Edit Sources is disabled.
Creating Animations
An animated plot is a series of frames that displays a field, mesh, or geometry at varying values. To
create an animated plot, you specify the values of the plot that you want to include, just as an ani-
mator takes snapshots of individual drawings that make up a cartoon. Each value is a frame in the
animation. You specify how many frames to include in the animation.
Note Each animation frame requires memory for storage which depends upon the mesh size
and type of plot. Memory usage may become very large during plot animations. To
reduce memory usage, specify the minimum number of frames possible. See General
Options for more information.
You can export the animation to animated Graphics Interchange Format (GIF) or to Audio Video
Interleave (AVI) format.
Related Topics
General Options: Miscellaneous Options Tab
Creating Phase Animations
Creating Frequency Animations
Creating Geometry Animations
Controlling the Animations Display
Exporting Animations
will be the first frame displayed, resulting in a total of 11 frames in the animation.
d. If the design has multiple project or intrinsic variables, click the Design Point tab to set
the values of the non-animated variables.
1. Click the Design Point tab.
2. Deselect the Use defaults checkbox.
In the table, select the row corresponding to the variable setting of interest.
3. Click OK.
The animation begins in the view window. The play panel appears in the upper-left corner of
the desktop, enabling you to stop, restart, and control the speed and sequence of the frames.
Related Topics
Controlling the Animation’s Display
Creating Frequency Animations
1. Create a field overlay plot to animate.
In the Create Field Plot dialog box, make sure to select a sweep solution to plot from the
Solution pull-down list.
2. Click HFSS>Fields>Animate .
If you already created an animation, the Select Animation dialog box appears. Selecting an
existing animation from that list starts it. To create a new animation, click New.
The Setup Animation dialog box appears.
3. Type a name for the animation in the Name text box or accept the default name.
4. Optionally, type a description of the animation in the Description text box.
5. Under the Swept Variable tab, select Frequency from the Swept Variable list.
6. Select the frequency values you want to include in the animation from the Select values list.
Use the Shift key to select a series of values, and the Ctrl key to select values that are not in
sequence.
7. If the design has multiple project or intrinsic variables, click the Design Point tab to set the
values of the non-animated variables.
a. Click the Design Point tab.
b. Deselect the Use defaults checkbox.
In the table, select the row corresponding to the variable setting of interest.
8. Click OK:
The animation begins in the view window. It will display one frame for each frequency value
you selected.
The play panel appears in the upper-left corner of the desktop, enabling you to stop, restart,
and control the speed and sequence of the frames.
Related Topics
Controlling the Animation’s Display
Creating Geometry Animations
Geometry animations may be created to evaluate the effect of varying geometry variables on the
model. You must define at least one variable associated with the geometry prior to creating a geom-
etry animation. Following is the general procedure for creating an animation that varies a part of the
model geometry.
1. Right-click in the view window, point to View, and then click Animate.
If multiple geometries can be varied in the design, the Select Drawing dialog box appears,
proceed to step 2. If only one geometry is variable, proceed to step 3.
2. In the Select Drawing dialog box:
a. Select the geometry variable to vary in the animation.
b. Select the object you want to animate.
Note If previous animations have been created for this project, the Select Animation dialog
will appear. You may choose an animation setup from the list if one is associated with
the geometry variable of interest and the animation will start. If no existing animation
setup is acceptable, select New and continue at Step 3 below.
4. Click OK.
The animation begins in the view window. It will display one frame for each variable value.
The play panel appears in the upper-left corner of the desktop, enabling you to stop, restart, and
control the speed and sequence of the frames.
Related Topics
Controlling the Animation’s Display
Controlling the Animation’s Display
When an animation is displayed in the view window, the Animation window, also called the play
panel, appears in the upper-left corner of the desktop. It has buttons that enable you to control the
speed and sequence of the frames, start and stop the animation and export the animation. Click an
area of the window below to learn its function.
Animation Each dot on the slider represents a frame in the animation. Drag the slider to
slider the right to display the next frame in the animated plot. Drag the slider to the
left to display the previous frame in the animation.
Plays the plot’s animation sequence backwards.
Drag the Speed slider to the top to increase the speed of the animation. Drag
the Speed slider to the bottom to decrease its speed.
Frame The current frame and phase at which the plot is being displayed is listed
inform- below the control buttons.
ation
Enables you to export the animation to an animated Graphics Interchange
Format (GIF) or to Audio Video Interleave (AVI) format.
Closes the animation window.
Exporting Animations
1. Create the animation you want to export.
2. In the play panel, click Export.
The Save As dialog box appears.
3. Follow the procedure for saving a new file. Select Animated GIF File (.gif) or AVI File (.avi)
as the file type.
The Animation Options dialog box appears.
4. To replace colors in the file with 256 shades of gray, select Grayscale.
Grayscale animations tend to use less memory than full color animations.
5. For AVI format export, specify the Compression factor (the default is 85) and one of the fol-
lowing Compression types:
INTEL Indeo
Cinepak
Microsoft Video 1
None
6. For GIF format export, specify the number of loops. The default “0” denotes infinite loops.
7. Click OK to close the Animations Options dialog.
The animation is exported to the file format you specified.
Creating Reports
After HFSS or HFSS-IE has generated a solution, all of the results for that solution are available for
analysis. One of the ways you can analyze your solution data is to create a 2D or 3D report, or
graphical representation, that displays the relationship between a design’s values and the corre-
sponding analysis results. You create reports using either the Create Quick Report command, or
the Create <type> Report commands. The Quick Report feature lets you select from a list of pre-
defined categories (such as S-parameters) from which to create a rectangular plot.
For each solution <type> (Eigenmode, Modal, Fields, Far Fields and Emission test, and Terminal),
the Results menus present a list of Create <type> Report commands based on the solution data of
direct interest for the design. For example, for the Eigenmode solution type, the Results menu con-
tains templates for Eigenmode Parameters and for Fields.These appear on the menus as Create
Eigenmode Parameters Report and Create Fields Report. For the Modal and Terminal Solution
types, several different types appear, appropriate to each solution type. Each of these Create
<type> Report menu items includes a further cascading menu that lists the Display Types available
for that report. For some reports you can modify the Display Type from the Properties for that
Report.
If you have created custom report templates (for example, including your company name or other
format changes), you can also create a report based on that template by selecting HFSS or HFSS-
IE>Results>Report Templates>PersonalLib><templateName>.
Related Topics
Creating a Quick Report
Creating a New Report
Modifying Reports
Modifying the Background Properties of a Report
Creating Custom Report Templates
Plotting in the Time Domain
3. Select the one or more categories for the report from the list and click OK.
A rectangular plot for each selected category displays. The new plot or plots appear in the Proj-
ect tree under the Results icon.
Related Topics
Creating Reports
Modifying Reports
Creating Custom Report Templates
Note The Quantity text field can be used to filter the Quantity list by typing in text. This is
useful if the Category selected produces a lengthy Quantities list.
e. Range Function button -- opens the Set Range Function dialog. This applies to the cur-
rently specified Quantity and Function.
4. In the X (Primary Sweep) section, make selections for the following:
a. Select the Primary value(s) from the drop down menu.
To select an X component that is different than the Primary Sweep, uncheck the Default
field to enable the X field and browse [...] button. Click the browse [...] button to display
the Select X Component dialog. This lets you specify the X component as you do the Y;
that is, in terms of Categories which define the selectable Quantities, and Functions to
apply. After making selections, OK the dialog to assign the X component.
b. If sweeps are available, you can select the browse [...] button to display a dialog that lets
you select particular sweep or sweeps, or all sweeps.
c. The Families tab provides a way to select from valid solutions for sweeps where a simula-
tion has multiple variables defined (for example, for a parametric sweep). If so, the vari-
ables other than the one chosen as the X (Primary sweep), are listed under the Families
tab with columns for the variable, the value, and an Edit column with an ellipsis [...] but-
ton. See Using Families tab for Reports.
5. Update Report setting
• Real Time checked -- enable real time updates for all reports while the reports are being
edited.
• Real Time unchecked -- enables drop down menu to Update All Reports or Update
Report. Reports will only be updated with one of these user selectable update options or
upon exiting the report dialog. This can be useful if you expect a trace to take time to dis-
play. You can then add additional traces without having to wait.
6. The Report dialog command buttons permit you create a new report with the settings you pro-
vide, or to modify an existing report.
• Output Variables - opens the Output Variables dialog.
• Add Trace - this is enabled when you have created or selected a report. Add one or more
traces to include in the report.
• Update Trace - updates the selected traces in a report based on further processing or
changes.
• New Report. Adds a report to the Project tree under the Results icon. The new Report is
displayed in the Project window.
• Options - opens the Report Setup Options dialog. This contains a checkbox for using the
advanced mode for editing and viewing trace components. This mode is automatic if the
trace requires it. It also contains a field for setting the maximum number of significant dig-
its to display for numerical quantities.
• Close - closes the Report dialog.
7. Click New Report to create a new report in the Project tree.
The report appears in the view window. It will be listed in the project tree under Reports.
Traces within the report also appear in the project tree. Some plots may take time to complete.
Performing a File>Save in such cases after the plot has been created will permit you to review
the plot later without having to repeat the calculation time when you reopen the project later.
8. To speed redraw times for changed plots, perform a Save. This saves the data that comprises
expressions.For example if re(S11)*re(S22) is requested over multiple widths, each of the S11
and S22 are stored when you save. If you do not do a save of a changed plot, the changed ver-
sion is not stored.
Related Topics
Creating Reports
Modifying Reports
Creating a Quick Report
Using Families tab for Reports
Context Section for Reports
Plotting in the Time Domain
Context Section for Reports
In the Context section make selections from the following field or fields, depending on the design
and solution type.
1. Solution field with a drop down selection list. This lists the available solutions, whether
sweeps or adaptive passes. The selections for HFSS Transient include Transient, and for Tran-
sient Network includes Spectral.
2. Domain field with a drop down selection list. Whether this field appears, and the domains
listed depend on the Solution type and the <type> selected. For modal and terminal solution
data r reports, the domain can be Sweep or Time.
Before you can examine the time domain, you must perform an Interpolating sweep for a
driven solution (Modal or Terminal). If you select Time, the TDR Options button is enabled.
Select it and follow the directions for time-domain plotting.
3. Geometry field with a drop down selection list. For field and radiated field reports, this applies
the quantity to a geometry or radiated field setup.
4. Show field with a drop down selection list for Differential pairs or Terminals. This field
appears for designs using terminal solutions that have differential pairs defined. It lets you plot
either differential pair data, or single-ended terminal data, or both in the same plot without hav-
ing to disable or enable differential pairs under the Excitations heading in the Project tree. Note
that single-ended quantities are computed as if no differential pairs existed. So in the unlikely
case of several terminals where only a subset is combined into pairs, the results may not be as
expected.
5. Derivative field with a drop drown selection list of none, all, and specific variables for which
you specified Use on the Derivatives tab of the solution setup. You can use derivatives in some
Optimetrics situations, and with the Derivative Tuning feature in the Reporter.
Related Topics
Creating Reports
Modifying Reports
Using Families tab for Reports
Selecting the Report Type in HFSS Transient
Using Families Tab for Reports
The Families tab of the Report dialog provides a way to select from valid solutions for sweeps
where a simulation has multiple variables defined (for example, for a parametric sweep). If so, the
variables other than the one chosen as the X (Primary sweep), are listed under the Families tab
with columns for the variable, the value, and an Edit column with an ellipsis [...] button. You can
make selections for the following.:
1. Select the Sweeps radio button (the default) to list the swept variables you can select.
2. With the Sweeps radio button selected, click the ellipsis [...] button to display a list of variable
values for a particular variable. You can use a scroll bar to navigate the list.
• To select all values, click the checkbox for Use all values. This writes “All” in the value
field for that variable. You can also select individual values by clicking on them.
• To select a range of values, hold down the shift key, and click again.
• To select intermittent additional values, hold the CTRL key and click additional. The val-
ues you select are highlighted in the list, and are also listed in the Values column for that
variable.
• To select all, use the Select All button. This highlights the complete list, as well as listing
all values for the variable in the Value field.
16-42 Post Processing and Generating Reports
HFSS Online Help
Modifying Reports
To modify the data that is plotted in a report:
1. In the project tree, click the report you want to modify.
2. Right-click Modify Report.
The Report dialog appears.
3. The Report dialog command buttons permit you create a new report with the settings you pro-
vide, or to modify an existing report.
• Output Variables - opens the Output Variables dialog.
• Add Trace - this is enabled when you have created or selected a report. Add one or more
traces to include in the report.
• Update Trace - updates the selected traces in a report based on further processing or
changes.
• New Report - adds a report to the Project tree under the Results icon. The new Report is
displayed in the main window.
• Options - opens the Report Setup Options dialog. This contains a checkbox for using the
advanced mode for editing and viewing trace components. This mode is automatic if the
trace requires it. It also contains a field for setting the maximum number of significant dig-
its to display for numerical quantities.
• Close - closes the Report dialog.
The updated report appears in the view window.
4. Update Report setting
• Real Time checked -- enable real time updates for all reports while the reports are being
edited.
• Real Time unchecked -- enables drop down menu to Update All Reports or Update
Report. Reports will only be updated with one of these user selectable update options or
upon exiting the report dialog. This can be useful if you expect a trace to take time to dis-
play. You can then add additional traces without having to wait.
5. In the Context section you make selections depending on the design and solution type.
6. The Families tab provides a way to select from valid solutions for sweeps where a simulation
has multiple variables defined (for example, for a parametric sweep). If so, the variables other
than the one chosen as the X (Primary sweep), are listed under the Families tab with columns
for the variable, the value, and an Edit column with an ellipsis [...] button. See Using Families
tab for Reports.
7. In the Y Component section of the dialog make selections for the following:
a. Categories - those depend on the Solution type and the design. For example, Eigenmode
quantities include Eigenmodes, variables, output variables, and the design. Driven solu-
tions include such categories as S parameters.
Note The Quantity text field can be used to filter the Quantity list by typing in text. This is
useful if the Category selected produces a lengthy Quantities list.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
8. In the X (Primary Sweep) section, make selections for the following:
a. Select the Primary value(s) from the drop down menu.
To select an X component that is different than the Primary Sweep, uncheck the Default
field to enable the X field and browse [...] button. Click the browse [...] button to display
the Select X Component dialog. This lets you specify the X component as you do the Y;
that is, in terms of Categories which define the selectable Quantities, and Functions to
apply. After making selections, OK the dialog to assign the X component.
b. If sweeps are available, you can select the browse [...] button to display a dialog that lets
you select particular sweep or sweeps, or all sweeps.
c. The Families tab provides a way to select from valid solutions for sweeps where a simula-
tion has multiple variables defined (for example, for a parametric sweep). If so, the vari-
ables other than the one chosen as the X (Primary sweep), are listed under the Families
tab with columns for the variable, the value, and an Edit column with an ellipsis [...] but-
ton. See Using Families tab for Reports.
You can also view and edit the properties of Reports and their traces via their Properties win-
dows. See Modifying the Background Properties of a Report.
You can also modify the display type of an existing plot from the Properties dialog for that plot.
Select the Report icon in the Project tree to display the Properties dialog. Selecting the Display
Type field displays a menu with selections available for that plot.
Once you make a selection, the plot display updates for the current selection.
Note Remember that for many excitations of interest for plotting, you can control the default
base names through the dialog described here: Setting Default Boundary/Excitation Base
Names.
This may save you the need to edit individual names in the plots.
Related Topics
Modifying the Background Properties of a Report
Modifying the Legend in a Report
Creating Custom Report Templates
Working with Traces
Editing the Display Properties of Traces
Setting Default Boundary/Excitation Base Names
Discarding Report Values Below a Specified Threshold
Add Trace Characteristics
Adding Data Markers to Traces
Modifying the Background Properties of a Report
The standard Zoom and Fit commands operate on reports. To modify the appearance of a report, or
the display properties an object in a report.
1. Open the report you want to modify.
2. You must select an editable object in the report to be able to edit its properties. Click on an
object to select it and to view its Properties in the docked properties window. To open a float-
ing Properties window, either double click on the selected object, or click Edit>Properties on
the toolbar.
The selectable objects in reports are as follows:
• Header -- this lets you edit the Properties for the text displayed at the top of the report,
including the Title font, Company Name, Show Design Name, Subtitle Font. The plot title
is tied to the report's name and is not a Header property. If you change the report name in
the Project tree, plot title synchronizes. The Company Name and the Show Design Name
checkbox are grouped in the Properties dialog as Subtitle. Edits to the Subtitle Font Prop-
erty affects both of them.
• General -- this dialog (or General tab for other Report properties windows) lets you edit
the background color (the perimeter around the trace display) for the plot, the contrast
color (the trace display background), the Field width, the Precision, and whether to use
scientific notation for marker and delta marker displays. (X and Y notation display is set
separately, in the Axis property tabs.)
• Legend -- this lets you edit the Properties for whether to Show Trace Name, Solution
Name, and Variation Key. At least one of these three must be selected. You can also edit
the Font, the background color of the Legend box, the Border Color, the Border Width,
Grid Color (for the lines between Trace descriptions), and the Grid line width. Also see
Modifying the Legend in a Report
• Traces -- you can select traces either in the Legend or on the plot. The properties for
traces include: Color, Line Style, Line Width, Trace Type, whether to Show a symbol,
Symbol Frequency, Symbol style, whether to Fill symbol, symbol color, and whether to
Show arrows. See Editing the Display Properties of Traces.
• X or Y Axis Tab-- the defaults for most of these values are set in the Report 2D Options
Axis tab.
• Specify name -- checkbox for specifying the Axis name.
• Name -- this describes the axis to which the following properties/options refer. These
are selected in the Report dialog.
• Axis Color -- set the color by double clicking to display the Set color dialog. Select a
default or custom color and click OK.
• Text Font -- click the cell to display the Edit Text Font dialog. The dialog lets you
select from a list of available fonts, styles, sizes, effects, colors, and script. The dialog
also contains a preview field. OK the selections to apply the font edits and to close the
dialog.
• Manual Format (section)
• Number format -- select from the drop down menu, Auto, Decimal, or Scientific
notation.
• Field Width -- enter a real value.
• Field Precision -- enter a real value.
• X or Y Scaling Tab -- These properties provide control over scaling.
• Axis Scaling -- use the drop down menu to select scaling as Linear or Log. For
the Y axis, all zero or negative values are discarded before log scaling is applied.
• Specify Min -- check box
• Min -- text entry in same units as axis units. Saved as SI internally.
• Specify Max -- check box
• Max -- text entry in same units as axis units. Saved as SI internally.
• Specify Spacing -- check box
• Spacing -- text entry in same units as axis units. Saved as SI internally
• Manual Units (section)
• Auto Units -- use the check box compute the correct units for the axis.
• Units -- click on the cell to select from a menu of available units if you have not
checked Auto Units.
• Infinity Visualization (section)
• Map Infinity Mode -- checkbox.
Each axis now can be set to treat infinity values in a user defined way. When you
check the Map Infinity Mode, any infinity values in the input data get the infini-
tyMap value (negative infinity get the value*-1 and positive infinity the positive
value specified). This can be useful if there are zeros, or very small values that
HFSS treats as zero, in the data, for example, dB Gain.
• Map Infinity To -- enter a real value for the Map Infinity Mode.
3. Edit the properties, and OK the dialog to apply the changes.
Related Topics
Modifying Reports
Working with Traces
Discarding Report Values Below a Specified Threshold
Modifying the Legend in a Report
Editing the Display Properties of Traces
Creating Custom Report Templates
Setting Report2D options
Zoom in or out.
Fit contents in the view window.
Modifying the Legend in a Report
The legend in a report is a list of the curves being plotted. For each curve, the legend gives the
name, shows the line color, and lists the setup and the adaptive pass used to generate the curve.
To show or hide a legend in a report:
1. Make the report the active view.
2. Use View>Active View Visibility or the Show/Hide icons on the toolbar to display or hide the
report.
Either command displays the Active View dialog.
3. Select the Legends tab.
This lists the legend (or legends) in the report.
4. Check the visibility checkbox, and OK the dialog to close it and apply the change.
To edit the display properties of a legend:
1. Select the legend in a report by clicking on the Curve Info panel to display a docked properties
window, or right-click on the legend and select Edit>Properties to display the floating proper-
ties window.
This lets you edit the Properties for whether to Show Trace Name, Solution Name, and Varia-
tion Key. At least one of these three must be selected.
You can also edit the Font by clicking the Font cell to display the Edit Text Font dialog. The
dialog lets you select from a list of available fonts, styles, sizes, effects, colors, and script. The
dialog also contains a preview field. OK the selections to apply the font edits and to close the
dialog
You can also edit the background color of the Legend box, the Border Color, the Border
Width, Grid Color (for the lines between Trace descriptions), and the Grid line width.
2. Click OK to close the Properties window and apply the selections.
To change the display name for traces, see Editing Trace Properties.
To move a legend in a report:
1. Click and hold and the legend.
The cursor changes to crossed lines with arrow tips.
2. Still holding, drag the legend to a new location and release.
The legend is released and the crossed lines change back to a mouse pointer.
To resize a legend in a report:
1. Position the mouse tip over the edge you want to resize.
The mouse pointer changes to a horizontal or vertical line with arrow tips.
2. Click and drag the horizontal or vertical edge to the desire size.
3. Release.
Related Topics
Editing Trace Properties
Showing Objects
Hiding Objects
Modifying Reports
Creating Custom Report Templates
Discarding Report Values Below a Specified Threshold
Setting Report2D options
Editing the Display Properties of Traces
Creating Custom Report Templates
You can edit properties from any report type and save it as a template. This can save repeated edit-
ing of properties (for example, the company name, or color schemes) when you create other
reports. Once you create templates, you can access them from the Results>Report Tem-
plates>PersonalLib menu.
See Modifying the Background Properties of a Report for a discussion of format changes you can
make to any report.
To save an edited report as a template:
1. In the Project Tree, right-click on the report name of interest to display the shortcut menu and
click Save as Template:
This displays the Report Save As file browser. By default, the directory is your Ansoft\<pro-
ductName>\userlib\ReportTemplates directory.
2. Typically, you accept the directory.
3. You must provide a file name, which will be given an *.rpt extension.
It is good practice to give the template a descriptive name, showing both the kind of format
you begin with (such as XY Plot or 3D Plot) and apt description of the distinguishing edits
(such as for company name, or color scheme). Once, saved, this name will appear on the Per-
sonalLib menu.
4. The Save As Type field currently supports the Ansoft Report Format (*rpt) format.
5. Click Save to save the template to the PersonalLib menu.
All *.rpt templates in the directory appear on the Results>Report Templates>PersonalLib menu.
Selecting a report from the PersonalLib menu opens a report that you can then Modify to add traces
or perform other edits.
Related Topics
Modifying Reports
Setting Report2D options
Zoom in or out.
Fit contents in the view window.
Modifying the Background Properties of a Report
Modifying the Legend in a Report
Working with Traces
Editing the Display Properties of Traces
Discarding Report Values Below a Specified Threshold
You can also modify the display type of an existing plot from the Properties dialog for that plot.
Select the Report icon in the Project tree to display the Properties dialog. Selecting the Display
Type field displays a menu with selections available for that plot.
Once you make a selection, the plot display updates for the current selection.
Related Topics
Selecting the Report Type
Creating Reports
Modifying Reports
Creating Custom Report Templates
Creating 2D Rectangular Plots
A rectangular plot is a 2D, x-y graph of results.
1. On the Results menu (HFSS menu or right-click on Results on the Project tree), click Create
<type> Report, and select Rectangular Plot.
The Report dialog appears.
2. In the Context section make selections from the following field or fields, depending on the
design and solution type.
a. Solution field with a drop down selection list. This lists the available solutions, whether
sweeps or adaptive passes.
b. Domain field with a drop down selection list. Whether this field appears, and the domains
listed depend on the Solution type and the <type> selected. For modal and terminal solu-
tion data reports, the domain can be Sweep or Time.
Before you can examine the time domain, you must perform an Interpolating sweep for a
driven solution (Modal or Terminal). If you select Time, the TDR Options button is
enabled. Select it and follow the directions for time-domain plotting.
c. Geometry field with a drop down selection list. For field and radiated field reports, this
applies the quantity to a geometry or radiated field setup.
3. Under the Trace tab, Y component section, specify the information to plot along the y-axis:
a. In the Category list, click the type of information to plot.
b. In the Quantity list, click the value to plot.
c. In the Function list, click the mathematical function of the quantity to plot.
d. Value field displays the currently specified Quantity and Function. You can edit this field
directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
4. On the Trace tab, X (Primary sweep) line, specify the quantity to plot along the x-axis in one
of the following ways:.
• Select the sweep variable to use from the drop down list.
• If sweeps are available, you can select the browse button to display a dialog that lets you
select particular sweep or sweeps, or all sweeps. The quantity will be plotted against the
primary sweep variable listed.
5. On the Families tab, confirm or modify the sweep variables that will be plotted.
6. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity will be plotted against the swept variable values or quan-
tities you specified on an x-y graph. The plot is listed under Results in the project tree and the
traces are listed under the plot. When you select the traces or plots, their properties are dis-
played in the Properties window. These properties can be edited directly to modify the plot.
7. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
You can also modify the display type of an existing plot from the Properties dialog for that plot.
Select the Report icon in the Project tree to display the Properties dialog. Selecting the Display
Type field displays a menu with selections available for that plot.
Once you make a selection, the plot display updates for the current selection.
Related Topics
Sweeping a Variable
Working with Traces
Add Trace Characteristics
Delta Markers in 2DPlots
1. On the Results menu (HFSS menu or right-click on Results on the Project tree), click Create
<type> Report, and select Rectangular Stacked Plot.
The Report dialog appears.
2. In the Context section make selections from the following field or fields, depending on the
design and solution type.
a. Solution field with a drop down selection list. This lists the available solutions, whether
sweeps or adaptive passes.
b. Domain field with a drop down selection list. Whether this field appears, and the domains
listed depend on the Solution type and the <type> selected. For modal and terminal solu-
tion data reports, the domain can be Sweep or Time.
Before you can examine the time domain, you must perform an Interpolating sweep for a
driven solution (Modal or Terminal). If you select Time, the TDR Options button is
enabled. Select it and follow the directions for time-domain plotting.
c. Geometry field with a drop down selection list. For field and radiated field reports, this
applies the quantity to a geometry or radiated field setup.
3. Under the Trace tab, Y component section, specify the information to plot along the y-axis:
a. In the Category list, click the type of information to plot.
b. In the Quantity list, click the value to plot.
c. In the Function list, click the mathematical function of the quantity to plot.
d. Value field displays the currently specified Quantity and Function. You can edit this field
directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
4. On the Trace tab, X (Primary sweep) line, specify the quantity to plot along the x-axis in one
of the following ways:.
• Select the sweep variable to use from the drop down list.
• If sweeps are available, you can select the browse button to display a dialog that lets you
select particular sweep or sweeps, or all sweeps. The quantity will be plotted against the
primary sweep variable listed.
5. On the Families tab, confirm or modify the sweep variables that will be plotted.
6. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity will be plotted against the swept variable values or quan-
tities you specified on an x-y graph. The plot is listed under Results in the project tree and the
traces are listed under the plot. When you select the traces or plots, their properties are dis-
played in the Properties window. These properties can be edited directly to modify the plot.
7. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
You can also modify the display type of an existing plot from the Properties dialog for that plot.
Select the Report icon in the Project tree to display the Properties dialog. Selecting the Display
Type field displays a menu with selections available for that plot.
Once you make a selection, the plot display updates for the current selection.
Related Topics
Sweeping a Variable
Working with Traces
Add Trace Characteristics
Delta Markers in 2DPlots
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
4. On the Trace tab Y (Secondary sweep) lines, specify the information to plot along the y-axis
in one of the following ways:
• Select the sweep variable to use from the drop down list.
• If sweeps are available, you can select the browse button to display a dialog that lets you
select particular values. The quantity will be plotted against the primary sweep variable
listed.
5. On the Trace tab X (Primary sweep) lines, specify the information to plot along the x-axis in
one of the following ways:
• Select the sweep variable to use from the drop down list.
• If sweeps are available, you can select the browse button to display a dialog that lets you
select particular values. The quantity will be plotted against the primary sweep variable
listed.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
4. On the Trace tab Y (Secondary sweep) lines, specify the information to plot along the y-axis
in one of the following ways:
• Select the sweep variable to use from the drop down list.
• If sweeps are available, you can select the browse button to display a dialog that lets you
select particular values. The quantity will be plotted against the primary sweep variable
listed.
5. On the Trace tab X (Primary sweep) lines, specify the information to plot along the x-axis in
one of the following ways:
• Select the sweep variable to use from the drop down list.
• If sweeps are available, you can select the browse button to display a dialog that lets you
select particular values. The quantity will be plotted against the primary sweep variable
listed.
6. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity or quantities will be plotted against the values you speci-
fied on an x-y-z graph. The plot is listed under Results in the project tree.When you select the
traces or plots, their properties are displayed in the Properties window. These properties can be
edited directly to modify the plot.
7. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
Related Topics
Sweeping a Variable
Working with Traces
Add Trace Characteristics
Creating 2D Polar Plots
In HFSS, a polar plot is a 2D circular chart divided by the spherical coordinates R and theta, where
R is the radius, or distance from the origin, and theta is the angle from the x-axis. Following is the
general procedure for drawing a polar graph of results:
1. On the Results menu ( HFSS menu or right-click on Results on the Project tree), click Create
<type> Report, and select Polar plot from the report type menu.
The Report dialog appears.
2. In the Context section make selections from the following field or fields, depending on the
design and solution type.
a. Solution field with a drop down selection list. This lists the available solutions, whether
sweeps or adaptive passes.
b. Domain field with a drop down selection list. Whether this field appears, and the domains
listed depend on the Solution type and the <type> selected. For modal and terminal solu-
tion data reports, the domain can be Sweep or Time.
Before you can examine the time domain, you must perform an Interpolating sweep for a
driven solution (Modal or Terminal). If you select Time, the TDR Options button is
enabled. Select it and follow the directions for time-domain plotting.
c. Geometry field with a drop down selection list. For field and radiated field reports, this
applies the quantity to a geometry or radiated field setup.
3. In the Trace tab Polar Component area, specify the information to plot:
a. On the Category drop down list, click the type of information to plot.
b. On the Quantity list, click the values to plot. Use CTRL-click to make multiple selec-
tions.
c. In the Function list, click the mathematical function to apply to the quantity for the plot.
d. The Value field displays the currently specified Quantity and Function. You can edit this
field directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
4. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity will be plotted against the swept variable values or quan-
tities you specified on an x-y graph. The plot is listed under Results in the project tree and the
traces are listed under the plot. When you select the traces or plots, their properties are dis-
played in the Properties window. These properties can be edited directly to modify the plot.
5. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
Related Topics
Reviewing 2D Polar Plots
Sweeping a Variable
Working with Traces
Add Trace Characteristics
a. On the Category drop down list, click the type of information to plot.
b. On the Quantity list, click the values to plot. Use CTRL-click to make multiple selec-
tions.
c. In the Function list, click the mathematical function to apply to the quantity for the plot.
d. The Value field displays the currently specified Quantity and Function. You can edit this
field directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
4. On the Trace tab Theta (Secondary Sweep) line, select the sweep variable from the drop
down list and specify all values or select values to plot along the theta-axis:
5. On the Trace tab Phi (Primary Sweep) line, select the sweep variable from the drop down
list, and specify all values or select values to plot along the phi-axis:
6. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity or quantities will be plotted against the R-, phi-, and
theta-axes on a 3D polar graph. The plot is listed under Results in the project tree. When you
select the traces or plots, their properties are displayed in the Properties window. These proper-
ties can be edited directly to modify the plot.
7. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
Related Topics
Sweeping a Variable
Working with Traces
Add Trace Characteristics
Creating Smith Charts
A Smith chart is a 2D polar plot of S-parameters upon which a normalized impedance grid has been
superimposed. Following is the general procedure for creating a Smith chart of results:
1. On the Results menu ( HFSS menu or right-click on Results on the Project tree), click Create
<type> Report, and select Smith Chart from the report type menu.
The Report dialog appears.
2. In the Trace tab Polar Component area, specify the information to plot:
a. On the Category drop down list, click the type of information to plot.
b. On the Quantity list, click the values to plot. Use CTRL-click to make multiple selec-
tions.
c. In the Function list, click the mathematical function to apply to the quantity for the plot.
d. The Value field displays the currently specified Quantity and Function. You can edit this
field directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
3. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity will be plotted against the values you specified on a polar
plot. In addition, each circle on the plot is labeled with values of R, measuring normalized
resistance, and each line is labeled with values of X, measuring normalized reactance. The plot
is listed under Results in the project tree and the traces are listed under the plot. When you
select the traces or plots, their properties are displayed in the Properties window. These proper-
ties can be edited directly to modify the plot.
4. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
Related Topics
Reviewing 2D Polar Plots
Sweeping a Variable
Working with Traces
Add Trace Characteristics
Creating Smith Contour Charts
A Smith contour chart is a polar plot of S-parameters upon which a normalized impedance grid has
been superimposed. Following is the general procedure for creating a Smith chart of results:
1. On the Results menu (HFSS menu or right-click on Results on the Project tree), click Create
<type> Report, and select Smith Chart from the report type menu.
The Report dialog appears.
2. In the Trace tab Mag area, specify the information to plot:
a. On the Category drop down list, click the type of information to plot.
b. On the Quantity list, click the values to plot. Use CTRL-click to make multiple selec-
tions.
c. In the Function list, click the mathematical function to apply to the quantity for the plot.
d. The Value field displays the currently specified Quantity and Function. You can edit this
field directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
3. On the Trace tab (Secondary Sweep) line, select the sweep variable from the drop down list
and specify all values or select values to plot along the theta-axis:
To select an Secondary sweep component that is different than the default, uncheck the Default
field to enable the X field and browse [...] button. Click the browse [...] button to display the
Select X Component dialog. This lets you specify the X component as you do the Y; that is, in
terms of Categories which define the selectable Quantities, and Functions to apply. After mak-
ing selections, OK the dialog to assign the X component.
a. If sweeps are available, you can select the browse [...] button to display a dialog that lets
you select particular sweep or sweeps, or all sweeps.
b. The Families tab provides a way to select from valid solutions for sweeps where a simula-
tion has multiple variables defined (for example, for a parametric sweep). If so, the vari-
ables other than the one chosen as the X (Primary sweep), are listed under the Families
tab with columns for the variable, the value, and an Edit column with an ellipsis [...] but-
ton. See Using Families tab for Reports.
4. On the Trace tab (Primary Sweep) line, select the sweep variable from the drop down list,
and specify all values or select values to plot along the phi-axis:
To select an X component that is different than the default, uncheck the Default field to enable
the X field and browse [...] button. Click the browse [...] button to display the Select X Com-
ponent dialog. This lets you specify the X component as you do the Y; that is, in terms of Cat-
egories which define the selectable Quantities, and Functions to apply. After making
selections, OK the dialog to assign the X component.
a. If sweeps are available, you can select the browse [...] button to display a dialog that lets
you select particular sweep or sweeps, or all sweeps.
b. The Families tab provides a way to select from valid solutions for sweeps where a simula-
tion has multiple variables defined (for example, for a parametric sweep). If so, the vari-
ables other than the one chosen as the X (Primary sweep), are listed under the Families
tab with columns for the variable, the value, and an Edit column with an ellipsis [...] but-
ton. See Using Families tab for Reports.
5. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity will be plotted against the values you specified on a polar
plot. In addition, each circle on the plot is labeled with values of R, measuring normalized
resistance, and each line is labeled with values of X, measuring normalized reactance. The plot
is listed under Results in the project tree and the traces are listed under the plot. When you
select the traces or plots, their properties are displayed in the Properties window. These proper-
ties can be edited directly to modify the plot.
6. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
Related Topics
Reviewing 2D Polar Plots
Sweeping a Variable
Working with Traces
Add Trace Characteristics
field directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
5. On the Trace tab X (Primary sweep) line, select the sweep variable from the drop down list,
and specify all values or select values.
6. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The Y quantity will be listed at each variable value or additional quantity value you specified.
The data table is listed under Results in the project tree. The plot is listed under Results in the
project tree and the traces are listed under the plot. When you select the traces or plots, their
properties are displayed in the Properties window. These properties can be edited directly to
modify the plot.
7. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
You can also modify the display type of an existing plot from the Properties dialog for that plot.
Select the Report icon in the Project tree to display the Properties dialog. Selecting the Display
Type field displays a menu with selections available for that plot.
Once you make a selection, the plot display updates for the current selection.
If you choose to print a data table:
• Selecting print "All" prints the whole table for current data page (if there are more than one
data page)
• Selecting print "Pages" prints user specified pages
• If the table is bigger than the screen view (that is, it has scroll bar), printing first scrolls right,
prints until no more scrolling and then scroll down.
• The Page number appears at the bottom of the page, aligned at center
• The table layout of each page follows the screen, but with no scroll bar will be printed, and no
data page bar as on screen.
Related Topics
Sweeping a Variable
Working with Traces
Add Trace Characteristics
Creating Radiation Patterns
A radiation pattern is a 2D polar plot displaying the intensity of near- or far-field radiation patterns.
It is divided by the spherical coordinates R and theta, where R is the radius, or distance from the
origin, and theta is the angle from the x-axis. Following is the general procedure for drawing a radi-
ation pattern of results:
1. Click HFSS>Results>Create <type> Report, or right click on the Results icon in the Project
tree and click Create <type> Report.
2. In the display type menu, click Radiation Pattern.
The Report dialog box appears, and a Radiation Pattern Plots icon appears under Results in
the Project tree.
3. In the Context section make selections from the following field or fields, depending on the
design and solution type.
a. Solution field with a drop down selection list. This lists the available solutions, whether
sweeps or adaptive passes.
4. In the Trace tab Mag Component area, specify the information to plot along the R-axis, or the
axis measuring magnitude:
a. On the Category drop down list, click the type of information to plot.
b. On the Quantity list, click the values to plot. Use CTRL-click to make multiple selec-
tions.
c. In the Function list, click the mathematical function to apply to the quantity for the plot.
d. The Value field displays the currently specified Quantity and Function. You can edit this
field directly.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
5. In the Trace tab Ang (Primary sweep) line, specify the sweep variable from the drop down
list, and specify all values or select values.
6. Click New Report.
This creates a new report in Project tree, displays the report with the defined trace, and enables
the Add Trace button on the Report dialog.
The function of the selected quantity or quantities will be plotted against the values you speci-
fied on a 2D polar plot. The plot is listed under Results in the project tree and the traces are
listed under the plot. When you select the traces or plots, their properties are displayed in the
Properties window. These properties can be edited directly to modify the plot.
7. Optionally, add another trace to the plot by following the procedure above, using Add Trace
rather than New Report.
You can also modify the display type of an existing plot from the Properties dialog for that plot.
Select the Report icon in the Project tree to display the Properties dialog. Selecting the Display
Type field displays a menu with selections available for that plot.
Once you make a selection, the plot display updates for the current selection.
Related Topics
Sweeping a Variable in a Report
Working with Traces
Add Trace Characteristics
Delta Markers in 2D Reports
To view the difference between any two marker points in a report:
1. Set the first marker by left-clicking and holding the mouse button.
2. Move the mouse without releasing left button to another position, and then release the left but-
ton to create second marker.
In the marker text window, you see the difference between the two markers instead of the X, Y
value of marker.
Related Topics
Setting Report2D options
Working with Traces
Editing the Display Properties of Traces
Adding Data Markers to Traces
Plotting in the Time Domain
The idea behind Time-Domain Reflectometry (TDR) is to excite a structure with a step function,
and inspect the reflections as a function of time. Before you can examine the time domain, you
must perform an Interpolating sweep for a driven solution (Modal or Terminal or Transient). You
can then select Time from the Domain list in the Report dialog. You also need to specify the input
signal, whether step or impulse.
With Time selected as the domain, you can select from several Categories and associated Quanti-
ties to plot, for example mag(S11). When you plot in the Time domain, every frequency domain
Post Processing and Generating Reports 16-67
HFSS Online Help
quantity is first converted to the time-domain before the formula is evaluated. For example, if you
type in
S11 / ( 1 - S11 )
and plot it in the time domain the reporter will plot
IFFT(S11 * input) / ( 1 - IFFT(S11 * input) )
It will NOT plot
IFFT( S11/ ( 1 - S11) * input )
The two expressions are not equivalent.
If you select Time Domain Impedance as the Category, you can select the TDRZ quantity. This is
defined as
TDRZ(t) = Zref * ( 1 + IFFT(S11 * input) ) / ( 1 - IFFT(S11 * input) )
where "input" denotes the Fourier transform of the input signal (step or impulse) and "IFFT(.)"
denotes the inverse FFT.
This equation is the instantaneous ratio of the time-domain voltage v(t) to the time-domain current
i(t). That is because voltage and current are defined (in the frequency domain) in terms of the inci-
dent and reflected waves a and b, respectively, as
V = sqrt(Zo) * (a + b) = sqrt(Zo) * ( 1 + Sii ) * a
I = 1/sqrt(Zo) * (a - b) = 1/sqrt(Zo) * ( 1 - Sii ) * a
This lets the incident wave be the input step signal, and so when we take the inverse FFT of V and
I, we get v(t) and i(t) in the time domain. Taking their ratio as a function of time then yields
TDRZ(t). By default, Zo is equal to 50 Ohm.
To create a plot in the Time Domain:
1. For a design with an existing sweep setup, follow steps 1 - 4 for creating a report for design.
2. In the Report dialog box, in the Domain list, click Time.
This enables the TDR Options button and for terminal solution data reports includes the Ter-
minal TDR Impedance in the Category list.
3. Click the TDR Options button.
The TDR Options dialog box appears.
4. Select the input signal type, Step or Impulse.
A Step describes a sustained change in the signal, whereas the Impulse is a brief excitation.
Impulse is a very narrow rectangular pulse, with zero rise and fall time, width of 1 time step,
and height of 1/(time step).
Selecting Step enables the Rise Time field, and Impulse disables it.
5. If you selected Step, enter the rise time of the pulse in the Rise Time text box.
The rise time should be appropriate for the frequency context.
With a band width from DC to fmax, the best time resolution that can be achieved is 1/(2fmax).
A rise time of 1/(2fmax) is the shortest rise time that can be resolved. However, a rise time of 0
s gives equally valuable information, so 0 is the default in this panel. See the example plot.
6. Enter the total time on the plot in the Maximum Plot Time text box.
The default maximum plot time in the TDR Options dialog is related to the delta frequency df
in the frequency sweep: it is 1/2df, since that is the extent of time for which the IFFT gives
information. This is often very long relative to the time delay that corresponds to the length of
your device under test, so you may want to reduce this value. Alternatively, you can adjust the
time axis of your TDR plot after it has been created.
7. Set the number of time points to plot in the Delta Time text box. By default, this is set to the
number of points in the frequency sweep.
The delta time is based on the bandwidth of the sweep: with a frequency sweep from DC to
fmax, the smallest time resolution you can obtain is given by 1/(2fmax). The IFFT algorithm
provides data points as a spacing of 1/(2fmax), but you can smoothly interpolate between points
by setting a finer resolution, e.g. to 1/(10fmax), at the expense of extra computation time.
8. Optionally, under TDR Window, modify the window type and width.
9. You can use the Save as Default to set the current values as a default, and the Use Defaults
button to use previously saved options. Note that when you select a trace, the initial displayed
values are those of the selected trace.
10. Click OK.
Optionally, to plot Terminal TDR impedance (that is, rather than calculate the S-parameter for
waveport1 versus frequency, instead calculate the delay versus time at a particular impedance),
do the following:
a. In the Category list, click Terminal TDR Impedance.
b. In the Quantity list, click a quantity to plot.
The default impedance (Zo) for the TDRZ quantity is 50 Ohms, unless you specified dif-
ferently when you Set Renormalizing Impedance for Terminals when you created the ter-
minals in the model. If you need a different impedance value, you can either edit the value
in the Report dialog (as shown below), or you can create an Output Variable representing
Zo × (1+Sii)/(1-Sii) with the Zo of your choice. To edit the Zo value in the Report dialog:
1. For the Category, select Terminal TDR Impedance, and the Port and Function of
interest.
c. In the Function list, click the mathematical function of the quantity to plot.
3. Click Done.
The report appears in the view window. It will be listed in the project tree.
If S11 = 0 at DC, the time-domain step response will settle to zero and the TDRZ step response
settles to Zref. If S11 is nonzero at DC, the time-domain step response will settle to a nonzero
value and TDRZ will settle to a value different from Zref. The time-domain impulse response
will always settle to zero, since it can be seen as the derivative of the step response. The TDRZ
impulse response will always settle to Zref.
The plot below shows the difference between a short nonzero rise time and zero rise time for a
transmission line segment of 94 Ohm. Note that the trace with zero rise time starts at the cor-
rect line impedance while the other starts at the renormalizing impedance. Other than that, one
trace is a shifted version of the other. The reason the plot with finite rise time starts at 50 ohms
is that the time-domain voltage and current are still at their steady state values, so v = Zref * i.
As the pulse arrives, the TDRZ response changes from the steady-state behavior because
there's a reflection from the transmission line back to the exciting source, which has a different
SpatialresolutionΔx = c ⁄ ( 2B ) (1)
where c is the speed of light in the medium and B is the bandwidth of the signal. Since TDR is
usually based on a frequency band that starts at DC, the spatial resolution becomes
Δx = c ⁄ ( 2F max ) (2)
where Fmax is the highest frequency in the frequency sweep. For example, if Fmax = 15 GHz
and the medium has εr=4, the spatial resolution will be (1.5E8 m/s)/(3E10 /s) = 5 mm.
A spatial resolution of c/(2Fmax) corresponds to a resolution in time
Δt = 1 ⁄ ( 2F max ) (3)
Let N be the number of points in the IFFT. N equals the number of time samples, and it also
equals twice the number of frequency samples. The density of frequency samples in the fre-
quency sweep influences the total time T as follows:
2F max ⁄ ( Δf ) = N ( number of points in IFFT ) = T ⁄ Δt (4)
So increasing the density of the frequency samples leads to an increase in total time T. In practical
case, this often leads to a long tail in the TDR plot with little useful information. Therefore, the
TDR Options interface lets you set the maximum plot time to a smaller value.
The TDR Options interface also lets you choose a smaller Δt than given by equation (3) above.
When you choose a smaller Δt, you increase Fmax by "zero padding", i.e. adding zero values for S11
beyond the calculated frequency sweep. Whether this is justified depends on your judgment. It
leads in practice to a smoother TDR signal.
HFSS also lets you set the rise time of your input signal. The rise time should be at least 1/(2Fmax).
Even this rise time is a bit short for comfort, as it equals the duration of only one time sample. An
input signal with a longer rise time has a smaller high-frequency content and will lead to reduced
“ringing” in the TDR response.
A Hamming or Hann filter will also reduce the high-frequency content and tends to lead to a
smoother TDR response. With these filters, one can select a width. A width of 100% is often a good
choice.
Related Topics
Interpolating sweep for a driven solution (Modal or Terminal or Transient).
Creating a report for design
TDR Windowing Functions
Perform TDR on Report
TDR Windowing Functions
Windowing functions cause the FFT of the signal to have non-zero values away from ω. Each
window function trades off the ability to resolve comparable signals and frequencies versus the
ability to resolve signals of different strengths and frequencies. The window type list includes:
Bartlett A high dynamic range function, with lower resolution, designed for
wide band applications.
1 2πn
w ( n ) = a 0 – a 1 ------------- – --- – a 2 cos ⎛ -------------⎞
n
N–1 2 ⎝ N – 1⎠
where a0=0.62; a1=0.48; a2=0.38
Blackman A high dynamic range function, with lower resolution, designed for
wide band applications.
2πn 4πn
w ( n ) = a 0 – a 1 cos ⎛⎝ -------------⎞⎠ + a 2 cos ⎛⎝ -------------⎞⎠
N–1 N–1
where a0 =(1-α)/2; α1=1/2; α2=α/2
2πn-⎞
w ( n ) = 0.5 ⎛⎝ 1 – cos ------------
N – 1⎠
Kaiser Selecting the Kaiser plot also enables a field to specify an associ-
ated Kaiser parameter. The larger the Kaiser parameter, the wider
the window. The parameter controls the trade off between width of
the central lobe and the area of the side lobes.
e. Range Function button -- opens the Set Range Function dialog. This applies currently
specified Quantity and Function.
Post Processing and Generating Reports 16-77
HFSS Online Help
3. In the Report dialog specify the X axis information (for example Primary Sweep).
4. Click Add Trace.
A trace is added to the traces list under its report icon in the Project tree. The trace represents
the function of the quantity you selected and will be plotted against other quantities or swept
variable values. Selecting a Trace in the Project tree displays the Properties window for that
Trace. Selecting a trace in the report or legend displays the display Properties window for that
trace.
Trace icons can be selected, copied, and pasted for their definitions or their data. They can be
selected and deleted from the Project tree.
By the default, the Trace name is the definition (the category, quantity and function). The trace
will be visible in the report when you click Add Trace.
Trace properties can be edited directly in the respective Properties windows or edited in the
Report dialog. To change the name or definition of a trace, see Editing Trace Properties. To
edit other display properties of a trace, see Editing the Display Properties of Traces
Related Topics
Removing Traces
Editing Trace Properties
Editing the Display Properties of Traces
Discarding Report Values Below a Specified Threshold
Add Trace Characteristics
Adding Data Markers to Traces
Setting Report2D options
Copy and Paste of Report and Trace Definitions
Copy and Paste of Report and Trace Data
Delta Markers in 2D Reports
Editing Trace Properties
To edit trace properties such as the name, the component definition, or the context, or the variables
select the trace in the Project tree.
To edit a trace name:
1. Select the trace in the Project tree.
This displays a docked Properties window for the Trace.
2. Check the Specify Name box.
This enables editing of either the Name field in the docked properties dialog, or the Trace label
text in the Project tree. Editing this name changes the display in the Legend and in the Project
Note To control the display of the Solution Name and Variation Key in the Legend, see Report
2D: Legend Tab.
ties window.
The display properties window for a trace includes a General tab and an Attributes tab.
The General tab properties apply to the general appearance of the plot. They include the Back-
ground color, Contrast color, Field width, and Whether to use Scientific notation for marker
and delta marker displays. (X and Y notation display is set separately, in the Axis property
tabs.)
The Attributes Tab properties apply specifically to the Trace. The defaults are set in the
Report2D options. They include:
• Name -- not editable by selecting the trace from the Report. It shows the characteristics of
the trace as defined in the Report dialog.
To edit a trace name, see Editing Trace Properties
• Color -- shows the Trace color. Double click to open a Color dialog. You can select from
Basic colors, or custom colors. You can define up to 16 custom colors by selecting or by
editing the Hue, Saturation, Luminescence, and the Red, Green, and Blue values.
• Line style -- a drop down menu lets you select Solid, Dot, Dash, or Dot-dash.
• Line width -- a text field lets you edit the numeric value.
• Trace type -- the drop down menu contains entries for Continuous, Discrete, Bar-Zero,
Bar Infinity, Stick Zero, Stick Infinity, Histogram, Step, and Stair.
• Show Symbol -- whether to show a symbol at the data points on the line.
• Symbol Frequency -- how often to show symbols on the trace.
• Symbol Style -- use a drop down menu to select from box, circle, vertical ellipse, horizon-
tal ellipse, vertical up triangle, vertical down triangle, horizontal left triangle, horizontal
right triangle
• Fill Symbol -- use the check box to set the symbol display as a solid or as hollow.
• Symbol Arrows -- use the check box to use arrows on the curve ends
.
Note So that curves with single points always appear, Box is the default symbol. For HFSS
11, None cannot be selected as the symbol.
3. Edit the properties of interest and OK the Properties window to apply the changes and close the
window.
Related Topics
Setting Report2D options
Working with Traces
Editing Trace Properties
Add Trace Characteristics
Adding Data Markers to Traces
Removing Traces
16-80 Post Processing and Generating Reports
HFSS Online Help
that let you add markers to traces. A marker appears as “mN” at the marked point, where N incre-
ments from 1 as you place additional markers. Each marker can be selected and has editable prop-
erties including name, font, background and color. As you place markers, one or more marker
legends may be displayed, depending on the View>Active View Visibility settings for the legends.
The main marker legend appears in the upper left of the plot, and lists the marker names and their X
and Y values in a table. You can control the number format for the table values via the properties
window, general tab. Under Marker/Other Number format, you can specify field width, precision,
and whether to use scientific notation. This value is independent of the Axis tab number properties.
A separate marker legend appears for Delta Markers, as described for the Delta Marker command.
When you enter Marker mode, the cursor arrow is accompanied by an “m” while a circle on the
selected trace shows the current position for a potential marker.
To end Marker mode, right-click to display the shortcut menu, and select End Marker Mode.
The available Marker mode commands and associated icons are the following:
• Marker -- this command lets you place a marker at an arbitrary point on a selected trace.
• X Marker -- this command adds a movable marker at the origin of the plot with a vertical line
rising from the X axis. To move an X marker, click on the X label and drag it to the desired
location. The label at the bottom of the line gives the X coordinate, and flag on the vertical line
identifies the Y coordinate on the trace. A trace property lets you lock the drag feature to leave
the marker in place. This marker is not cleared by the Clear All command, and must be deleted
by selecting it and using the Edit Delete command.
• Maximum -- places a marker at the Maximum value on the selected trace.
• Minimum -- places a marker at the Minimum value on the selected trace.
• Delta Marker enters delta marker mode, placing a circle on the selected trace. Clicking
on the trace sets an initial point and subsequent clicks on arbitrary points on the trace place
additional markers until you leave marker mode. These markers have their own legend, which
includes the following information for each pair of markers specified.:
• Next Peak -- moves a selected marker on the next peak on a trace. You must exit marker
mode and select a marker to enable this command.
• Next Minimum -- moves a selected marker to the next minimum on a selected trace. You
must exit marker mode and select a marker to enable this command.
• Previous Peak -- moves a selected marker on the previous peak on a selected trace. You
must exit marker mode and select a marker to enable this command.
• Previous Minimum -- places a marker on the previous minimum on a selected trace.
You must exit marker mode and select a marker to enable this command.
• Next Data Point (Right) -- moves a selected X marker to the next data point.
• Previous Data Point (Left) -- moves a selected X marker to the previous data point.
• Next Curve -- selects the next curve in the report, based on the order in the trace legend.
• Previous Curve -- selects the previous curve in the report, based on the order in the trace leg-
end.
• Clear All -- clears all markers on a report except X Markers.
Related Topics
Setting Report2D options
Working with Traces
Add Trace Characteristics
Removing Traces
Discarding Report Values Below a Specified Threshold
Modifying the Legend in a Report
Editing the Display Properties of Traces
Zoom in or out.
Fit contents in the view window.
Showing Objects
Hiding Objects
Delta Markers in 2D Reports
Related Topics
Working with Traces
Removing Traces
Editing the Display Properties of Traces
Modifying Background Properties of a Report
Modifying Reports
Add Trace Characteristics
Add Trace Characteristics
You can add or clear additional characteristics to a selected trace. To add additional characteristics
to a selected trace:
1. Select a trace in a report plot or legend.
2. Click Report 2D>Trace Characteristics, or right-click on the selected trace to display the
short cut menu.
3. Select Trace Characteristics>Add....
This displays the Add Trace Characteristics dialog.
4. Select the Category, and then an associated Function to apply. The available categories
depend on the plot, and Category enables the display of associated functions.
Note If the report or trace definition contains properties that do not exist in the target design
(for example, a port name) an error will be posted that indicates a solution does not exist
for this trace
Note You must copy and paste trace definitions between the same report types. For example,
you cannot copy a trace from a Modal Solution Data report and paste it in a Far Fields
report.
Right click on the report name in the project tree and select Copy Definition from the shortcut
menu.
To paste the Report Definition:
Right click on Results in the project tree of the target design and select Paste.
A new report is created and it contains the copied definitions.
To copy an individual Trace Definition(s):
Right click on the trace or traces under a report name in the project tree and select Copy Defini-
tion.
To paste the Trace Definition(s):
Right click on the report in the target design to which you would like to copy the trace or traces and
select Paste.
A new trace(s) is added to the report and it contains the copied trace definition(s).
Note If you copy and paste a report or trace definition to a design which contains a definition
with the same name, then an incremented number is appended to the pasted report or
trace name.
Related Topics
Copying to the Clipboard as Images
Copy and Paste of Report and Trace Data
Copy and Paste of Report and Trace Data
You can copy and paste report and individual trace data within a single design or across designs.
The report and trace definitions and all underlying data within the report or trace are copied and
pasted to the target design or report.
To copy all data from a report:
Right click on the report name in the project tree and select Copy Data, or use the menu bar
Edit>Copy Data, or right click within a plot to display a shortcut menu with Copy Data.
To paste copied report data:
Right click on Results in the project tree of the target design and select Paste.
To copy data from an individual trace(s) in a report:
Right click on the trace or traces under a report name in the project tree and select Copy Data.
To paste copied trace data:
Right click on the report in the target design to which you would like to copy the trace data and
select Paste.
Note If you copy and paste report or trace data which contains the same name definition as a
report or trace in the target design then an incremented number will be appended to the
pasted name.
Related Topics
Copying to the Clipboard as Images
Copy and Paste of Report and Trace Definitions
All Values option, and then select the point values on which you want to plot.
Note All maximum near-field data calculated by HFSS is at their maximum over the selected
line object; if you plot the parameter over a sweep of values, the parameter will have the
same value at each point on the plot.
Related Topics
Sweeping a Variable in a Report
Sweeping Values Across a Sphere
1. Set up a near-field sphere or a far-field infinite sphere.
2. In the Report dialog box, click the sphere geometry of interest in the Geometry list.
3. For the Sweeps variable corresponding to phi, select the ellipsis [...] button.
This displays a small dialog.
4. Clear the Use all values checkbox to enable selection and editing of the sweep values.
All of the possible values for the phi variable are listed in the dialog. The values are the result
of the range of phi you specified during the infinite sphere’s setup. To modify the values of phi
to be plotted across the sphere, do the following:
a. Click Edit Sweep.
b. Specify the following information:
Step or Count Whether to sweep by steps, or by linear count, decade count, octave
count, or exponential count.
Start Value The point where the rotation of phi begins.
End Value The point where the rotation of phi ends.
Step or Count The number of values between the start value and the end value.
c. Click Update Values, and then click OK.
The values listed are updated to reflect the new number of points.
5. To plot the selected quantity or quantities at every value of phi, select All Values.
To plot the selected quantity or quantities at specific values of phi, clear the All Values option,
and then select the phi values at which you want to plot.
6. For the Sweeps variable corresponding to theta, follow steps 4 and 5 for modifying the values
of theta, if necessary, and specifying the theta values at which to plot the selected quantity or
quantities.
Note All antenna parameters and maximum far-field data calculated by HFSS is at their
maximum over the selected object; if you plot the parameter over a sweep of values, the
parameter will have the same value at each point on the plot.
cos Cosine
cosh Hyperbolic cosine
crestfactor Peak/RMS (root mean square) for the selected simulation quantity
dB(x) 20*log10(|x|)
dBm(x) 10*log10(|x|) +30
dBW(x) 10*log10(|x|)
db10normalize 10*log [normalize(mag(x))]
db20normalize 20*log [normalize(mag(x))]
deriv Derivative of first parameter over second parameter.
even Returns 1 if integer part of the number is even; returns 0 otherwise
exp Exponential function (the natural anti-logarithm)
formfactor Returns root mean square RMS/Mean Absolute Value for the selected
simulation quantity.
iae Returns the integral of the absolute deviation of the selected quantity from
a target value that is entered via the additional argument. To use this
function, you need to open the Add Trace Characteristics dialog and select the
Error category.
im Imaginary part of the complex number
int Truncated integer function
integ Integral of the selected quantity. Uses trapezoidal area.
integabs Absolute value of integral.
ise Returns the integral of the squared deviation of the selected quantity from
a target value that is entered via an additional argument. To use this
function, you need to open the Add Trace Characteristics dialog and select the
Error category.
itae Returns the time-weighted absolute deviation of the selected quantity
from a target value that is entered via an additional argument.To use this
function, you need to open the Add Trace Characteristics dialog and select the
Error category.
itse Returns the time-weighted squared deviation of the selected qty from a
target value that is entered via an additional argument.To use this function,
you need to open the Add Trace Characteristics dialog and select the Error
category.
j0 Bessel function of the first kind (0th order)
j1 Bessel function of the first kind (1st order)
ln Natural logarithm
log10 Logarithm base 10
lsidelobex The ‘x’ value for the left side lobe: the next highest value to the left of the
max value.
lsidelobey The ‘y’ value for the left side lobe: the next highest value to the left of the
max value.
mag Magnitude of the complex number
max Maximum of magnitudes.
max_swp Maximum value of a sweep.
min Minimum magnitudes.
min_swp Minimum value of a sweep.
nint Nearest integer
normalize Divides each value within a trace by the maximum value of the trace. ex.
normalize(mag(x))
odd Returns 1 if integer part of the number is odd; returns 0 otherwise
overshoot Obtains the peak overshoot over a point (double argument)
per Calculates period.
pk2pk Peak to peak. Difference between max and min of the first parameter over
the second parameter. Returns the peak-to-peak value for the selected
simulation quantity.
pkavg Returns the ratio of the peak to peak-to-average for the selected quantity.
pmax Period max.
pmin Period minimum
prms Period Root Mean Square.
pulsefall9010 Pulse fall time of the selected simulation quantity according to the 90%-
10% estimate.
pulsefront9010 Pulse front time of the selected simulation quantity according to the 10%-
90% estimate.
pulsefront3090 Pulse front time of the selected simulation quantity according to the 30%-
90% estimate.
pulsemax Pulse maximum from the front and tail estimates for the selected
simulation quantity.
pulsemaxtime Time at which the maximum pulse value of the selected simulation
quantity is reached.
pulsemin Pulse minimum from the front and tail estimates for the selected
simulation quantity.
pulsemintime Time at which the minimum pulse value of the selected simulation
quantity is reached.
pulsetail50 Pulse tail time of the selected simulation quantity from the virtual peak to
50%.
pulsewidth5050 Pulse width of the selected simulation quantity as measured from the 50%
points on the pulse front and pulse tail.
PulseWidth
Functions
pw_plus Pulse width of first positive pulse
pw_plus_max Max. Pulse width of input stream
pw_plus_min Min. Pulse width of input stream
pw_plus_avg Average of the positive pulse width input stream
pw_plus_rms RMS of the positive pulse width input stream
pw_minus_max Max. Pulse width of input stream
pw_minus_min Min. Pulse width of input stream
pw_minus_avg Average of the negative pulse width input stream
pw_minus_rms RMS of the negative pulse width input stream
polar Converts the complex number in rectangular to polar
re Real part of the complex number
rect Converts the complex number in polar to rectangular
rem Fractional part
ripple Returns the ripple factor (AC RMS/Mean) for the selected quantity.
rms Returns total root mean square of the selected quantity.
rmsAC Returns the AC RMS for the selected quantity.
rsidelobex The ‘x’ value for the right side lobe: the next highest value to the right of
the max value.
rsidelobey The ‘y’ value for the right side lobe: the next highest value to the right of
the max value.
sgn Sign extraction
sin Sine
sinh Hyperbolic sine
1 + S ij
------------------ .
1 – S ij
Active S- Assume ak is a complex number representing magnitude and phase for the
parameter kth source.
n a km
ActiveS pm = ∑ ---------
a pm
× S pk
k=1
Where n is the total number of ports, p is the port of interest, m is the
mode of interest, and k is the port numbering index.
Active Y-
1
parameter ActiveY pm = --------------------------
ActiveZ pm
Active Z-
m 1 + ActiveS pm
parameter ActiveZ pm = Z 0 × -----------------------------------
1 – ActiveS pm
Active VSWR
1 + mag ( ActiveS 11 )
ActiveVSWR = --------------------------------------------------
1 – mag ( ActiveS 11 )
Antenna Params HFSS-calculated quantities that include peak directivity, radiated power,
accepted power, radiation efficiency including the total and component
values at Phi and Theta, max U, and array factors. For far-field setups, the
decay factor for lossy materials is calculated as a constant for all far
fields.
Normalized For designs with plane incident waves. RCS is not supported for other
Bistatic RCS types of incident waves.
The normalized radar cross section.
σ-
-------
2
λ0
where λ0 is the wavelength of free space.
Radar Cross- For designs with Plane Incident Waves. (RCS is not supported for other
Section (Bistatic types of incident waves).
RCS) The radar cross-section (RCS) or echo area, σ, is measured in meters
squared and represented for a bistatic arrangement (that is, when the
transmitter and receiver are in different locations as shown in the linked
figure). This is represented by
2
4πr 2 E scat
σ = -----------------------------
2
E inc
where
• Escat is the scattered E-field.
• Einc is the incident E-field.
Complex For designs with Plane Incident Waves. (RCS is not supported for other
(Bistatic) RCS types of incident waves)
The equation for complex (bistatic) RCS is calculated as:
E scat
σ = 2 πR -------------
E inc
where
• Escat is the scattered E-field.
• Einc is the incident E-field.
This form retains the phase information.
Monostatic RCS For designs with Plane Incident waves. (RCS is not supported for other
types of incident waves) A proper incident angle sweep should exist at the
incident wave source setup before HFSS can plot Monostatic RCS.
The radar cross-section (RCS) or echo area when the transmitter and
receiver are at the same location.
For Monostatic RCS, you need not be concerned with the Theta and Phi
values defined in the radiation sphere. Only the incident wave Theta and
incident wave Phi are used in calculating a Monostatic RCS plot.
The following diagram shows the bistatic RCS concept, with separate transmitting and receiv-
ing antennas.
Incident Wave
Target
R1
Transmitting antenna
Scattered Wave
R2
Bistatic RCS
Receiving antenna
Each Category item that you select causes the Quantity list to offer quantities appropriate to
selected category. Category selection for a Variable of an Output Variable lists those available
in each case. Selecting Antenna Parameters as Category causes the Quantity list to show
Antenna parameters.
3. Select the Quantity to apply to the selected Category.
If the Category item you select is rE, Gain, Directivity, or Realized Gain, you will need to
specify the polarization of the electric field by selecting from the Quantity list. This ability to
plot the gain of certain vector components (polarizations) of the electric field allows you to
evaluate how well your antenna radiates in desired polarizations.
Total The combined magnitude of the electric field components.
Phi The phi component.
Theta The theta component.
X The x-component.
Y The y-component.
Z The z-component.
LHCP The dominant component for a left-hand, circularly polarized field.
RHCP The dominant component for a right-hand, circularly polarized field.
CircularLHCP The polarization ratio for a predominantly left-hand, circularly polarized
antenna.
CircularRHCP The polarization ratio for a predominantly right-hand, circularly polarized
antenna.
SphericalPhi The polarization ratio for a predominantly φ-polarized antenna.
2
4πU RHCP ( θ ,φ ) 4π rE RHCP ( θ ,ϕ )
Gain RHCP = -------------------------------------- = -------------------------------------------------
P acc 2ηP acc
θ̂ – jφˆ 2
4π rE ( θ ,ϕ ) • ⎛⎝ --------------⎞⎠
2
= ------------------------------------------------------------
2ηP acc
4. You can also select a function to apply to the your selections for the Category and Quantity
(for example, mag).
As you make selections in the Report dialogue for Category, Quantity, and Function, the Y
field shows the combined calculation they describe.
5. Click New Report to create the Report.
The new report based on your selections is displayed.
Related Topics
Selecting a Function
Setting a Range Function
Working with Traces
Creating Reports
Modifying Reports
Technical Notes: Antenna Parameters
Technical Notes: Polarization of the Electric Field
Technical Notes: Spherical Cross-Sections
φ
x y
Plotting Horizontal Cross-Sections of Far Fields
When plotting far fields, a horizontal cross-section results from holding theta fixed and sweeping
phi through a range of values.
1. Click the ellipsis [...] button for the sweep variable corresponding to theta.
To the right, all of the possible values for the theta variable are listed. The values are the result
of the range of theta you specified during the infinite sphere’s setup.
2. Select the fixed value that theta should take in the plot.
HFSS will display values for the horizontal cross-section at selected theta cuts of the problem
region at a set of phi rotations.
The figure shown below demonstrates the orientation of the sphere on which the field is com-
puted when θ is the fixed variable:
x y
Selecting a Near-Field Quantity to Plot
When plotting near-field quantities, the quantity can be a value that was calculated by HFSS, a
value from a calculated expression, or an intrinsic (inherent) variable value such as frequency or
theta.
To select a near-field quantity to plot:
1. When you create the report, specify the Report Type as "Near Fields."
2. In the Report dialog box, select one of the following categories:
Variables Intrinsic variables, such as frequency or theta, or user-defined project
variables, such as the length of a quarter-wave transformer.
Output Variables User defined expressions applied to derive quantities from the original
field solution.
Near E The radiated electric field in the near region.
Max Near Field The maximum radiated electric field in the near region.
Params
Near Normalized The resultant plot is: field quantity / (maximum field quantity value over
Antenna the entire infinite sphere).
3. If you selected the Near E category, specify the polarization of the electric field by selecting
one of the following types of quantities from the Quantity list:
NearETotal The combined magnitude of the electric field components.
NearEPhi The phi component of the electric field.
NearETheta The theta component of the electric field.
NearEX The x-component of the electric field.
time.
5. OK the specified values or Cancel, Use Defaults, or Save As Default as appropriate.
Plotting Imported Solution Data
1. In the Solution pull-down list in the Report dialog box, click the imported data you want to
plot.
2. Follow the procedure for creating a report.
Setting a Range Function
To apply a range function to the Y, Z, or Mag component of a trace:
1. Click the Range Function button in the Reports dialog.
This opens the Set Range Function dialog. The functions available are the same as described
in the Selecting a Function section, with the exception of those for the Eye Measurements cat-
egory.
2. Click the Specified radio button on the Range function line.
This enables the Range Function fields.
3. Select the Category, and then an associated Function to apply. The available categories
depend on the plot, and Category enables the display of associated functions.
Selecting a Function.
Selecting a function causes the display of a description in the Purpose field. If the function
requires a value (such as the XatYVal Math function or the pw_minus_max Pulse Width func-
tion), the table below the function field displays the name, editable value field, unit, and
description.
4. Use the Over Sweep drop down menu to select from available sweeps.
5. To select from available Sweeps, or to edit them, use the ellipsis [...] button and uncheck Use
All Sweeps.
This enables a list of the sweeps. The sweep(s) you select is displayed on the Over Sweep line.
You can use the buttons to Clear All Selections or Select All sweeps.
6. Select the Sweeps Default or Edited radio buttons to specify whether to accept the default or
edited sweeps.
7. To edit the sweeps further, select the ellipsis button to display an Edit Sweep dialog.
For frequency variables, this lets you specify a single value, linear step, linear count, decade
count, octave count, or exponential count. You can Add legal values to the list of sweep val-
ues, Update the list for changes, or Delete selected entries.
8. Click OK to apply the range function.
Related Topics
Selecting a Function
Eye Measurement Range Function Parameters
Eye Measurement Range Function Parameters
The Eye Measurement category of range functions provide the means to evaluate several character-
istics of eye diagrams. Each of the Eye Measurement functions includes the following parameters.
Specify the Value by editing the Value text field for the parameter name. Specify the unit for the
parameter by selecting from the Unit drop down menu.
Related Topics
Setting a Range Function
Van Hann A moderate dynamic range function, designed for narrow band
applications.
2πn-⎞
w ( n ) = 0.5 ⎛ 1 – cos ------------
⎝ N – 1⎠
Weber
Welch This approach applies a parabola-shaped window to the frequency
domain data. It is based on the Bartlett method but splits the signal
into overlapping segments, which are then windowed. The intent is
to balance the influence data the centerof the function.
Related Topics
Perform FFT on a Report
FFT Window Functions
Apply FFT to Report Functions
Perform TDR on a Report
Apply FFT to Report Functions
The choices include:
ang_deg Angle (phase) of a complex number, cut at +/-180
ang_rad Angle in radians
arg
cang_deg Cumulative angle (phase) of the first parameter (a complex number) in
degrees, along the second parameter (typically sweep variable). Returns a
double precision value cut at +/-180.
cang_rad Cumulative angle of the first parameter in radians along a second
parameter (typically a sweep variable) Returns a double precision value.
dB(x) 20*log10(|x|)
dB 10normalize 10*log [normalize(mag(x))]
dB 20normalize 20*log [normalize(mag(x))]
dBc
b. Insert part or all of the expression using the options in the Calculation and Function sec-
tions.
4. Click Add to add the new variable to the list.
5. Repeat steps 2 through 5 to add additional variables.
6. When you are finished adding output variables, click Done to close the Output Variables
window.
Related Topics
Deleting Output Variables
Building an Expression Using Existing Quantities
Viewing the Output Variable Convergence
Building an Expression Using Existing Quantities
When you are entering an expression for a new output variable, you can insert part or all of the
expression using the options in the Calculation and Function sections of the Output Variables
window.
To add an input variable by inserting part or all of the expression:
1. Click HFSS>Results>Output Variables or, in the Project Tree, right-click on Results and
select Output Variables from the short-cut menu.
The Output Variables window appears.
2. In the Output Variables section, enter a name for the new variable in the Name box.
3. To insert a quantity:
a. From the Report Type pull-down list, select the type of report from which you want to
select the quantity.
b. From the Solution pull-down list, select the solution from which you want to select the
quantity.
c. From the Category list, select the type of quantity you want to enter.
d. From the Quantity list, select the quantity or the geometry.
e. From the Function list, select a ready-made function (this option is the same as inserting
the function from the Function section).
f. If applicable, from the Domain list, select the solution domain.
g. Click Insert Into Expression.
The selected quantity is entered into the Expression area of the Output Variables sec-
tion.
4. To insert a function:
a. In the Function section, select a ready-made function from the pull-down list.
b. Click Insert Function into Expression.
The function appears in the Expression area of the Output Variables section.
5. When you are finished defining the variable in the Expression area, click Add to add the new
variable to the list.
6. Repeat steps 2 through 6 to add additional variables.
7. When you are finished adding output variables, click Done to close the Output Variables
window.
Related Topics
Adding a New Output Variable
Building an Expression Using Existing Quantities
Related Topics
Adding a New Output Variable
This gives you a plot with initially two identical curves, one on top of the other. You can then right-
click on Results in the Project tree and select Tune Reports. The Report Tuning window appears.
You can use the slider to tune one curve interactively while the other curve stays to provide a refer-
ence. This way you can see interactively how small changes in variables affect the result. You can
then apply those offsets to the original variable values and re-solve the design.
If an HFSS design has ports, they are listed Port Field Display icon in the Project tree. The modes
for each port appear under the port name.
Select a port name to display a Properties dialog with the properties for that port, or for individual
Modes listed under that port. These are used as subsequent plot defaults for the port field display.
Your control of port field displays is purely through the docked Property window. You can edit the
Scale Factor field, which governs the sizes of the arrows. If multiple solutions or frequencies are
available, you can select from a dropdown menu.
If no 2D solutions exist for the selected port or mode, the Status line of the Properties dialog will
say "No solutions available."
Depending on the view you begin with, and the location and size of the mode in the design, you
may want to right click on the selected mode to display a Zoom to Region command.
The difference between the Port Field Display and the Field Overlay is that the Port Field Display
gives the pure 2D port solution. A Field Overlay provides a the 3D field solution on the port, which
is the sum of the excitation in the port and the reflections by the 3D structure. The Port Field dis-
play lets you examine the field patterns with which the 3D structure is excited.
Related Topics
Plotting Field Overlays
You can also overlay existing 3D Polar Plots of near or far fields on the model window by using the
HFSS or HFSS-IE>Fields>Plot Fields>Radiation command, or by right-clicking on Field Over-
lays in the Project tree and selecting Plot Fields>Radiation Field.
To plot a basic field quantity:
1. Select a point, line, surface, cutplane, or object to create the plot on or within.
2. Click HFSS or HFSS-IE>Fields>Plot Fields., or right-click on Field Overlay icon in the Proj-
ect tree and select Plot Fields, or right click in the modeler window, and select Plot Fields
from the context menu.
3. On the Plot Fields menu, click the field quantity you want to plot.
The available selections depend on the solved solution. For definitions of the usual quantities,
see the list under Quantity command.
If you select a scalar field quantity, a scalar surface or volume plot will be created. If you select
a vector field quantity, a vector surface or volume plot will be created. If you select a vector
quantity, you will be able to specify a Steamline plot. If the quantity you want to plot is not
listed, see Named Expression Library.
For projects with Temperature dependent materials, the HFSS or HFSS-IE>Fields>Plot
Fields>Other... menus selections include Temperature.
After you select the field quantity to plot, the Create Field Plot dialog box appears.
The Specify Name field shows a name based on the field quantity you selected, and the Quan-
tity list shows the field quantity selected.
4. To specify a name for the plot other than the default, select Specify Name, and then type a new
name in the Name text box.
Note Multiple selection should be used when there is a discontinuous field on a surface. If not,
the field on both sides of the surface is plotted and each interferes with the other.
10. If you selected a vector quantity, you can use the checkbox to select Streamline plot. Stream-
lines are often used to indicate magnetic flux lines, etc. in plots. See Setting Field Plot Attri-
butes for adjusting the streamline display and Setting Fields Reporter Options for setting
Streamline defaults.
If you want to update the field overlay before then, to view progress in the solution, select the
Field icon in the Project tree that contains the field plot of interest, right-click to display the
short cut menu, and select Update Plots.
To turn off the display of the plot, right click on the plot and select Plot Visibility from the
short-cut menu. Unchecking Plot Visibility turns off the plot display.
Related Topics
Plotting Derived Field Quantities
Overlaying 3D Polar Plots on Models
Select Objects.
Select Faces.
Creating an Object List
Selecting the Face or Object Behind
Using the Fields Calculator
Port Field Display
Setting a Plot’s Visibility
Technical Notes: Field Overlays
Technical Notes: Field Quantities
Technical Notes: Specifying the Phase Angle
Overlaying 3D Polar Plots on Models
You can overlay existing 3D Polar Plots or near or far fields on the model window by using the
HFSS or HFSS-IE>Fields>Plot Fields>Radiation command, or by right-clicking on Field Over-
lays in the Project tree and selecting Plot Fields>Radiation Field. You can edit the visibility, trans-
parency and scale of the polar plot by using a dialog.
1. Create one or more 3D Polar Plots for your model.
2. Click the HFSS or HFSS-IE>Fields>Plot Fields>Radiation command, or by right-clicking
on Field Overlays in the Project tree and selecting Plot Fields>Radiation Field.
3. Check the Visible box and click Apply to cause that plot to appear in the model window. You
can also edit the Transparency and scale. Other properties of the 3D plot are controlled in its
properties window.
Related Topics
Plotting Field Overlays
Creating 3D Polar Plots
Plotting Derived Field Quantities
Derived field quantities are field quantity representations that have been deduced from the original
field solution using the Fields Calculator.
1. Select a point, line, surface, or object to create the plot on or within.
2. On the HFSS or HFSS-IE menu, or right-click on the Field Overlays icon in the Project tree,
and point to Fields>Named Expression.
3. Select the derived quantity you want to plot, and then click OK.
The Create Field Plot dialog box appears.
4. To specify a name for the plot other than the default, select Specify Name, and then type a new
name in the Name text box.
5. Select the solution to plot from the Solution pull-down list.
6. To specify a folder other than the default in which to store the plot, select Specify Folder, and
then click a folder in the Plot Folder pull-down list, or type the name you wish to use. Plot
folders are listed under Field Overlays in the project tree.
7. Under Intrinsic Variables, select the frequency and phase angle at which the field quantity is
evaluated.
8. Select the derived field quantity to plot from the Quantity list.
9. Select the volume, or region, in which the field will be plotted from the In Volume list.
This selection enables you to limit plots to the intersection of a volume and the selected object.
10. Click Done.
The derived field quantity you created in the Fields Calculator is plotted on the surfaces or
objects you selected. The new plot is listed in the project tree under Field Overlays.
Related Topics
Using the Fields Calculator
Technical Notes: Field Quantities
Technical Notes: Specifying the Phase Angle
Add Trace Characteristics
4. Click OK.
Related Topics
Technical Notes: Calculating the SAR
Creating Vector Field Plots
A vector plot uses arrows to illustrate the magnitudes of the x-, y-, and z-components of field quan-
tities. Vector plots can be created on surfaces or volumes.
1. Do one of the following:
a. To create a vector surface plot, select the faces on which you want to plot the fields.
b. To create a vector volume plot, select the objects within which you want to plot the fields.
2. Click HFSS or HFSS-IE>Fields>Plot Fields.
3. On the Plot Fields menu, click the vector field quantity you want to plot.
4. Follow the procedure for plotting field overlays.
If you select a vector quantity, you can also check Streamline for the plot.
Related Topics
Modifying Field Plot Attributes
Plotting Field Overlays
Modifying Field Plots
1. Click HFSS or HFSS-IE>Fields>Modify Plots , or in the Project tree, select the Field
Overlays icon, right-click, and select Modify Plots or use the "m" hotkey.
The Select Field Plot(s) dialog box appears.
Optionally, you can right-click on an existing plot listed under the Field Overlays in the Project
tree, bypass the Select Field Plot dialog and go to step 3
2. Select the plot you want to modify in the Select column, and then click OK.
The Modify Field Plot dialog opens.
• Optionally, click the Specify Name check box to enable the name field.
• Optionally, click the Specify Folder field enable the Plot Folder drop down.
• Optionally, select a different Solution from the dropdown menu.
• Optionally, select a different field type, if available.
3. Under Intrinsic Variables, specify the frequency and phase at which the field quantity will be
evaluated.
4. Optionally, select a different field quantity to plot from the Quantity list.
• To choose a calculated expression, select Calculator from the Category pull-down list. If
you choose Calculator, click the Fields Calculator button to display the calculator.
• To choose a predefined field quantity, select Standard from the Category pull-down list.
Select from the Quantity list.
5. Select the volume, or region, in which the field will be plotted from the In Volume list.
16-122 Post Processing and Generating Reports
HFSS Online Help
This selection enables you to limit plots to the intersection of a volume and the selected object.
6. Click Apply to make the changes and leave the dialog open, or click Done to apply the
changes and close the dialog.
The field quantity is plotted on the surfaces or within the objects you selected. The modified
plot is listed in the specified plot folder in the project tree.
The plot uses the attributes specified in the Plot Attributes dialog box.
Related Topics
Setting a Plot’s Visibility
Technical Notes: Specifying the Phase Angle
Add Trace Characteristics
Setting Field Plot Attributes
Setting Field Plot Attributes
After creating a mesh or field overlay on a surface or volume, you can modify its appearance by
changing the settings in the Plot Attributes dialog box. You will modify the settings for a plot
folder and all plots in that folder will use the same attributes.
1. Click HFSS or HFSS-IE>Fields>Modify Plot Attributes , or in the Project Manager
window, select the Field Overlays icon, and select Modify Attributes or use the "a" hotkey.
The Select Plot Folder window appears.
2. In the Select Plot Folder window, select the plot you want to modify, and then click OK. (You
can also select the specific plot in the Project tree, and select Modify Attributes from the right
click menu.
A dialog box with attribute settings for the selected plot (whether for an E Field plot or a Mesh
Overlay plot) appears.
3. For an E Field Plot, under the following tabs in the dialog box, you can control the following
plot attributes: For Mesh plot attributes, see below.
Color map The number of colors used and how they are displayed.
Scale The scale of field quantities.
Related Topics
Setting a Plot’s Visibility
Plotting the Mesh
Plotting Field Overlays
Modifying Field Plot Colors
1. Click HFSS or HFSS-IE>Fields>Modify Plot Attributes , or in the Project tree, right
click on the Field Overlays icon and select Modify Plots from the short-cut menu, or use the
"m" hotkey.
The Select Plot Folder window appears.
2. Select the plot folder you want to modify, and then click OK.
All plots in the selected folder will be modified.
A dialog box with attribute settings for the selected folder appears.
3. Click the Color Map tab.
4. Select one of the following color types:
Uniform Field quantities are plotted in a single color. Choose the plot color from
the Color palette.
Ramp Field quantities are plotted in shades of a single color. Choose the plot
color from the Color palette. The shade of the color corresponds to its
field value.
Spectrum Field quantities are plotted in multiple colors. Choose a color spectrum
from the pull-down list. Each field value is assigned a color from the
selected spectrum.
You can choose Save as Default, if you want to use the current settings.
Select Real time mode if you want these, or subsequent changes to take effect immediately in
the view window.
If this option is cleared, click Apply when you want to see the changes.
Plot Title
Color Map
Range of Plotted
Field Values
Related Topics
Modifying Field Plot Colors
Moving the Color Key
Moving the Color Key
Click on the active field overlay plot’s color key and drag it to a new location.
Related Topics
Setting the Color Key Visibility
Modifying the Field Plot Scale
To change how field quantities are scaled on the field overlay plot:
1. Click HFSS or HFSS-IE>Fields>Modify Plot Attributes or in the Project tree, right
click on the Field Overlays icon and select Modify Plots from the short-cut menu, or use the
"m" hotkey.
The Select Plot Folder window appears.
2. Select the plot folder you want to modify, and then click OK.
All plots in the selected folder will be modified.
A dialog box with attribute settings for the selected folder appears.
3. Click the Scale tab.
4. Optionally, to change the number of divisions in the field plot scale, set the Num. Division
field to a new value. You can click Save as Default, if desired.
5. Select one of the following scale options:
Auto The full range of field values will be plotted on the selected surface or
volume. Selecting Auto enables the Auto Scale Options and disables the
Min and Max fields. By default, precision is not limited and auto-min is
the actual computed min on the plotted geometry.
Use Limits Only the field values between the minimum and maximum values will be
plotted. Field values below or above these values will be plotted in the
colors assigned to the minimum or maximum limits, respectively.
Selecting Use Limits enables the Min and Max fields and disables the
Auto Scale Options.
Field values have a precision of at most 6 decimal places (field solution
files are saved in floating precision), so Min/Max numbers are displayed
to this precision.
Specify Values This enables a Scale Values button..
6. Optionally, use the Units drop down menu to select the default unit of measure for the plot.
The units specified here appear on the Color map for the fields plot, and for the properties dia-
log for the field quantities.
7. If you selected Use Limits, enter the lowest field value to be plotted in the Min. text box and
the highest field value to be plotted in the Max. text box.
If you selected Auto, the Auto Scale Options are enabled. You should only changed for cases
where auto-min is a small number. Use the 'Limits Max/Min precision to' checkbox to enable
setting the drop down menu for the precision limit. The auto-min is the greater of the follow-
ing:
• Actual computed Min
• Max/pow(10, num digits of field precision)
If you selected Specify Values, you can click the Scale Values button. This opens a dialog
with an editable, scrollable list of the current scale values. To apply the changes you make,
click the OK button. To close the dialog without make changes, click Cancel.
8. If you selected Auto or use Limits, you can select one of the following options:
Linear Field values are plotted on a linear scale.
Log Field values are plotted on a logarithmic scale. If field plots have negative
and positive values and when auto-scale is selected, the log-scale choice
automatically sets the Min value as the Max/Min Ratio. (If field plots
have all negative values, Log is not allowed.)
9. Select Real time mode if you want the changes to take effect immediately in the view win-
dow.
If this option is cleared, click Apply when you want to see the changes.
10. Optionally, you can use the Save As Default button to save the following to registry:
• Whether to limit field precision,
• The number of digits of field precision,
• Whether to use log/linear scale.
Auto scale is the default for new plots. For scalar-in-volume plots, iso-surface (rather than
cloud) is the default display
11. Click Close to dismiss the window.
Modifying Vector Field Plot Arrows
To change the appearance of a vector field plot’s arrows:
1. Click HFSS or HFSS-IE>Fields>Modify Plot Attributes .
The Select Plot Folder window appears.
2. Select the plot folder you want to modify, and then click OK.
All plots in the selected folder will be modified.
A dialog box with attribute settings for the selected folder appears.
3. Click the Marker/Arrow tab.
4. Under Arrow Options, select one of the following arrow types:
Line The arrows are displayed as 2D/flat.
Cylinder The arrow tails are displayed as cylinders. The arrowheads are displayed
as 3D/round.
Umbrella The arrow tails are displayed as 1D lines. The arrowheads are displayed
as 3D/round.
5. Use the Size slider to increase (move to the right) or decrease (move to the left) the length and
dimensions of the arrows. The arrows are resized relative to the size of the model geometry.
6. Select Map Size to scale the size of the arrows to the magnitude of the field quantity being
plotted.
7. Select Arrow tail to include tails on all arrows.
8. Click the Plots tab.
9. HFSS plots arrows on a grid that is superimposed on the surface or object you selected for the
plot. Under Vector plot, use the Spacing slider to increase (move to the right) or decrease
(move to the left) the distance between arrows (grid points.)
• Select Uniform if you want the arrows to be spaced equally.
10. Select Real time mode if you want the changes to take effect immediately in the view win-
dow.
If this option is cleared, click Apply when you want to see the changes.
11. Click Close to dismiss the window.
Related Topics
Plotting the Mesh
Setting a Plot’s Visibility
Modifying Scalar Field Plot Isovalues
1. Click HFSS or HFSS-IE>Fields>Modify Plot Attributes .
The Select Plot Folder window appears.
2. Select the plot folder you want to modify, and then click OK.
All plots in the selected folder will be modified.
A dialog box with attribute settings for the selected folder appears.
3. Click the Plots tab.
4. If the plot is a scalar surface plot, do the following:
a. Select one of the following isosurface display types in the IsoValType pull-down list:
Line Lines are drawn along the isovalues.
Fringe Color is constant between isovalues.
Tone Color varies continuously between isovalues.
Gourard Color varies continuously across the plot.
b. Optionally, if you selected Fringe or Tone, select Outline to add a border line between
isovalues.
5. If the plot is a scalar volume plot, do the following:
4. Under Marker options, select one of the marker types to represent the field quantity at the
point:
• Sphere
• Box
• Tetrahedron
• Octahedron
5. Use the Size slider to increase (move to the right) or decrease (move to the left) the size of the
marker.
6. Select Map size to scale the size of the marker to the magnitude of the quantity being plotted.
7. Select Real time mode if you want the changes to take effect immediately in the view win-
dow.
If this option is cleared, click Apply when you want to see the changes.
8. Click Close to dismiss the window.
Related Topics
Drawing a Point
Modifying Line Plots
Field quantities can be plotted directly on a line object. Scalar quantities are plotted as 3D color-
shaded lines. Vector quantities are plotted as arrows that are based on the line.
To modify the appearance of line plots:
1. Click HFSS or HFSS-IE>Fields>Modify Plot Attributes .
The Select Plot Folder window appears.
2. Select the plot folder you want to modify, and then click OK.
All plots in the selected folder will be modified.
A dialog box with attribute settings for the selected folder appears.
3. Click the Plots tab.
4. Select one of the following isosurface display types in the IsoValType pull-down list:
Fringe Color is constant between isovalues.
Tone Color varies continuously between isovalues.
Gourard Color varies continuously across the plot.
5. Select one of the following styles for the line object in the Line style pull-down list:
Cylinder The line object is shaped like a cylinder.
Solid The line object is a 3D solid.
1. Click View>Active View Visibility . Alternatively, you can select the Active View Vis-
ibility icon from the toolbar.
The Active View Visibility dialog box appears.
2. Click the FieldsReporter tab.
3. In the Visibility column, select the field overlay or mesh plots you want to display. Clear the
plots you want to hide from view.
Only the selected plots will be visible.
Related Topics
Plotting the Mesh
Setting a Plot’s Visibility
Saving a Field Overlay Plot
Field overlay and mesh plots are saved in the project file; however, you can save a plot to HFSS
Field Plot File format (.dsp) and then open it in HFSS.
Note Plots stored in the same folder will use the same color key. The Auto scale setting will
be based on the maximum field solution value present in a plot.
5. Under Intrinsic Variables, specify the frequency and phase angle at which the field quantity
is evaluated.
6. Click OK.
Related Topics
Technical Notes: Specifying the Phase Angle
Related Topics
Opening the Fields Calculator
Context Area
Calculator Stack
Registers
The Stack Commands
Input Commands
General Commands
Scalar Commands
Vector Commands
Output Commands
Calculating Derived Output Quantities
Named Expression Library
Opening the Fields Calculator
To open the Fields Calculator, do one of the following:
• Click HFSS or HFSS-IE>Fields>Calculator
or
• Right-click Field Overlays in the project tree, and then click Calculator on the shortcut menu.
The Fields Calculator window appears.
To view information on a command or screen area, click over the button or screen area on the illus-
tration below.
Context Area
The panel at the upper right of the window identifies the context to be used for the calculations. The
top line identifies the design. Depending on the design, text entry boxes allow you to select a Solu-
tion, Field Type, Freq, Phase, IWavePhi and IWaveTheta. The IWavePhi and IWaveTheta are
available only for incident wave projects in which the wave is defined with spherical coordinates.
The Field Type here is not related to the edit sources. This is a general term among Ansoft products
(HFSS, Maxwell, and Q3D). Some products have more than one field type for different solution
types. If only one Field Type is available the box is grayed out.
The Change Variable Values button opens a Set Variable Values dialog. By default it has Use
Nominal Design checked. Unchecking the box lets you select another variable value. OK the dialog
to accept the selection.
Related Topics
Opening the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
The Calculator Stack
The calculator is made up of a stack of registers. Registers are displayed in the register display area
at the center of the calculator window. Each register can hold:
• Field quantities such as the H-field or E-field.
• Functional or constant scalars and vectors.
• Geometries — points, lines, surfaces, or volumes — on which a field quantity is to be evalu-
ated.
To perform a computation on the field solution, you must first load a basic field quantity into a reg-
ister on the stack. Once a quantity is loaded into a register, it can be:
• Manipulated using mathematical operations such as curls, gradients, cross products, diver-
gences, and dot products.
• Integrated over lines, surfaces, or subvolumes of the solution region — either predefined sur-
faces, volumes, and lists, or lines, surfaces, and volumes that were defined using the Draw
commands.
• Exported to a file, allowing you to superimpose saved solutions.
Related Topics
Registers
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Registers
Calculator registers hold field quantities, numbers, vectors, and geometries. No registers are cre-
ated until you load something into the calculator; therefore, this part of the window is initially
blank. As items are loaded into the calculator, it creates new registers to hold them.
Each register is labeled with its contents as follows:
Vec Vector quantities, which have both direction and magnitude at each point in space.
The x-, y-, and z-components of these quantities are stored in the register.
Scl Scalar quantities, which have a magnitude only.
Cvc Complex vector quantities.
Csc Complex scalar quantities.
Pnt Points.
Lin Lines.
Srf Surfaces.
Vol Volumes.
SclLin Scalar value on a line.
VecLine Vector value on a line.
SclSrf Scalar value on a surface.
VecSrf Vector value on a surface.
When examining calculator registers, keep the following in mind:
• To move or delete calculator registers, use the stack commands.
• To save a register to a disk file, use the Write command.
Related Topics
Enlarging the Register Display Area
Units of Measure
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Enlarging the Register Display Area
If there are too many registers to fit into the display area, do one of the following:
• Use the scroll bars to view the hidden registers.
• Enlarge the calculator window using the window’s borders.
Related Topics
Registers
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Units of Measure
Unless you are prompted specifically for the unit of measure, all measurements should be assumed
to be in SI base units, not model units.
Related Topics
Registers
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Stack Commands
Use these commands to manipulate the registers in the calculator stack.
Push
Reloads the quantity in the top register onto the top of the stack, creating a new register. The con-
tents of the top two registers are identical.
Pop
Deletes the top register from the stack.
RlUp
Rolls the top register to the bottom of the stack, moving the other registers up the stack.
RlDn
Rolls the bottom register to the top of the stack, moving the other registers down the stack.
Exch
Exchanges the top two registers in the stack.
Clear
Clears the contents of the stack.
Undo
Use this command to undo the effect of the last operation you performed on the contents of the top
register. Successive Undo commands act on any previous operations.
Note You cannot undo a simple operation such as loading a field quantity, constant, function,
or geometry into the calculator. Instead, use the Pop or Clear commands to delete these
items from the calculator stack.
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Input Commands
Use the following commands to load data onto the top of the calculator stack:
Quantity Basic field quantities, such as E and H, and simple derived quantities such as
volume current.
Geometry Geometries such as planes, points, polylines, face lists, and volumes
Constant Predefined constants such as π, ε0, and conversion factors between various
units of measurement.
Number Vector and scalar constants, including complex numbers.
Function User-defined or intrinsic variables
Geom Settings Number of equally spaced points used to integrate fields and other quantities
on a line.
Read Previously-saved calculator registers containing field quantities.
Output Vars This button appears only for eigenmode problems. Freq is the only value
there. Evaluation for Freq returns a complex value.
These quantities can be manipulated using the Stack commands, General commands, Scalar com-
mands, and Vector commands. The results of these calculations can then be examined using the
Output commands.
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Quantity Command
The Input command loads a field quantity into the top register of the calculator. Phasors in the cal-
culator are peak phasors. The Poynting command in the calculator therefore implements the
Poynting vector for peak phasors. Calculations which compute either average or instantaneous time
domain quantities must adhere to the peak phasor conventions.
The available quantities are:
E The electric field, E
H The magnetic field, H
Jvol The volume current density, Jvol
Related Topics
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Geometry Command
The Fields Calculator Geometry command opens a dialog that lets you select a geometry to load
into the top register of the calculator. Do this to:
• Find the value of derived field quantities on any point, line, surface, or volume.
• Plot quantities directly from the calculator.
• Display a previously defined isosurface, maximum or minimum field point using the Draw
command.
The following types of geometries are available:
Point - See drawing a point object. Points you draw are listed in the history tree, and in the
Calculator Geometry dialog when you select Point.
Line- See drawing a line object. Lines you draw are listed in the history tree, and in the Calculator
Geometry dialog when you select Line. To set the number of points on a line, see Geom Settings .
Surface - Sheet objects and face lists which you can make, (for example of radiation boundaries)
are listed under surface in the history tree and in the Calculator Geometry dialog when you select
Surface.
Due to the ambiguity of the normal vector of a sheet, the result may require a multiplication by ( 1 ) or ( -1 ).
Volume - 3D objects, Regions, and object lists of 3D objects including AllObjects are available in
the Calculator Geometry dialog when you select Volume.
Coord - Coordinate systems are available in the Calculator Geometry dialog when you select
Coord.
To load a geometry into the calculator:
1. In the Fields Calculator, click Geometry.
The Geometry dialog box appears.
2. Select a geometry type.
A list of all applicable geometries appears.
3. Click the geometry.
4. Click OK to load the geometry.
Note Consider a box (Box2) that is completely enclosed in a bigger box (Box1), so that no
faces of Box2 are touching any faces of Box1.
Box2 is actually implicitly subtracted from Box1 as is done in our solvers. So Box1 is
used as if Box2 were already subtracted from Box1. Volume(Box1) is Box1 excluding
Box2, and Surface(Box1) contains faces from both Box1 and Box2.
Related Topics
Using the Fields Calculator
Input Commands
Domain command
Export Command
Geom Settings
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Constant Command
The Constant command loads one of these four predefined constants, or conversion constant into
the top register of the calculator:
Pi π
Epsi0 The permittivity of free space, ε0 = 8.85418782 x 10–12 C2/Nm2
Mu0 The permeability of free space, μ0 = 4π x 10–7 Wb/Am
c The speed of light in vacuum, c = 2.99792458 x 108 m/s
conversion Displays the Enter Units Conversion Factor dialog. This lists a range of
constant Quantities (such as frequency, resistance, and others) along with a list of Units
(Hz to Thz, and rps) to convert From and To. The ratio of the Units From to the
Units to is displayed for the selected values as Conversion Factor.
Related Topics
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Number Command
The Number command enters one of the following into the top register of the calculator:
Scalar A scalar constant. To enter a constant scalar number:
1. Click Number.
The Input Number dialog box appears.
2. Select Scalar.
3. Type the scalar value in the Value text box.
4. Click OK to load the number into the top register.
Vector A vector constant.
To enter a constant vector:
1. Click Number.
The Input Number dialog box appears.
2. Select Vector.
3. Enter the x-, y-, and z-components of the vector.
4. Click OK to load the vector into the top register.
Complex A complex constant. Complex constants are entered in the form C=A+jB,
where A represents the real part of the constant and B represents the
imaginary part.
1. Click Number.
The Input Number dialog box appears.
2. Select Scalar or Vector.
3. Select Complex.
4. Enter the real and imaginary components of the number.
5. Click OK to load the number into the top register.
Related Topics
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Function Command
Any functions you use must be defined prior to using this operation.
Enters one of the following into the top register of the calculator:
Scalar A scalar function.
To enter a function:
1. Click Function.
The Function dialog box appears.
2. Select Scalar.
3. Select the function from the list.
4. Click OK to load the functional scalar into the top register.
Vector A vector function, in which the values of the vector’s x-, y-, and z-components
are given by functions.
To enter a functional vector:
1. Click Function.
The Function dialog box appears.
2. Select Vector.
3. Select the function from the list.
4. For each component of the vector, click SetX, SetY, and SetZ.
5. Click OK to load the functional vector into the top register.
Note The predefined variables X, Y, Z, RHO, THETA, R, and PHI and any functions that
you created can be used to define functional scalar and vector quantities.
Related Topics
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Geom Settings Command
Clicking the Geom Settings button opens the Geometric Settings dialog box. The dialog box
allows you to specify the line discretization, the number of equally-spaced points used to integrate
fields and other quantities on a line. The default is 1000 points.
Related Topics
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Post Processing and Generating Reports 16-147
HFSS Online Help
Read Command
This command copies the contents of a disk file into the top register. The register must be one that
has been saved using the Write output command.
To read in a register:
1. Click Read.
2. Use the file browser to specify the register’s file name and directory path. A .reg extension is
automatically assumed for register files.
3. Click OK.
The contents of the file are copied to the top register in the stack.
Related Topics
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Output Vars [Input for Eigenmode problems]
This button appears in the Inputs column of the Fields calculator only for Eigenmode problems.
Freq is the only value listed. After you push Freq to the stack, you can click Eval to return a com-
plex value.
Related Topics
Setting the Solution Type
Using the Fields Calculator
Input Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
General Commands
Use these Fields Calculator commands to perform operations on both vector and scalar quantities.
+ (Add) / (Divide) Smooth
-- (Substract) Neg Complex
* (Multiply) Abs Domain
+ (Add)
The Domain command is often used to limit a calculation or plot to the intersection of a surface
and an object or group of objects. If you export a domain filtered numeric, points that are filtered
out by the domain will not be written out.
Related Topics
Using the Fields Calculator
Export Command
Steps for Calculating the Complex Vector Electric Field
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Steps for Calculating the Complex Vector Electric Field
These are the field calculator steps to obtain the real part, the imaginary part, and the magnitude of
the x-directed, y-directed, and z-directed components of the phasor electric field. For each of these
vector components, the magnitude should be equal to sqrt(real^2+imag^2), but the need to interpo-
late values and the calculation sequence means that HFSS does not give this value unless the speci-
fied location is directly on a mesh element node.
1. Calculate real part of complex vector electric field (in x, y, and z directions):
a. Qty > E
b. Complex > Real
c. Geometry > Point > fieldcalc_point
d. Value
e. Eval
2. Calculate imaginary part of complex vector electric field (in x, y, and z directions):
a. Qty > E
b. Complex > Imag
c. Geometry > Point > fieldcalc_point
d. Value
e. Eval
Use the real and imaginary components to manually calculate the magnitude as the sqrt
(Real^2+imag^2).
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Scalar Commands
Use these commands to perform operations on scalar quantities.
Vec? Makes the scalar quantity in the top register a vector component.
1/x Takes the inverse of the scalar quantity in the top register.
Pow Raises a scalar quantity to the power you specify.
( Square Root) Takes the square root of the quantity in the top register.
Trig Takes a selected trigonometric value of the value in the top register of the
calculator stack
d/d? Takes the partial derivative of the quantity in the top register.
∫ (Integral) Takes the integral of a scalar quantity over a volume, surface, or line.
Min Computes the minimum of a scalar field quantity on a line, surface, or volume.
Max Computes the maximum of a scalar field quantity on a line, surface, or
volume.
∇ (Gradient) Takes the gradient of the scalar quantity in the top register.
ln Takes the natural logarithm (base e) of the scalar quantity in the top register.
log Takes the logarithm (base 10) of the scalar quantity in the top register
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Vec? Command
Makes the scalar quantity in the top register a vector component. Choose from the following:
VecX The x-component of a vector.
VecY The y-component of a vector.
VecZ The z-component of a vector.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Trig
Takes one of the following trigonometric values of the value in the top register of the calculator
stack:
Sin Sine.
Cos Cosine.
Tan Tangent.
Asin Arcsine.
Acos Arccosine.
Atan Arctangent.
Atan2 Arctangent squared.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
d/d? (Partial Derivative) Command
Takes the partial derivative of the quantity in the top register:
d/dx Takes the partial derivative of the quantity with respect to x.
d/dy Takes the partial derivative of the quantity with respect to y.
d/dz Takes the partial derivative of the quantity with respect to z.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
∫ (Integral) Command
Takes the integral of a scalar quantity over a volume, surface, or line. The top register must contain
a geometry and the second register must contain the scalar quantity to be integrated.
To perform an integration:
1. Load a quantity into the top register of the calculator, and perform any required operations on
it.
2. Use one of the Geometry commands to load the line, surface, or volume over which the quan-
16-154 Post Processing and Generating Reports
HFSS Online Help
tity is to be integrated.
Note If you computed the tangent or normal of the quantity to be integrated, you do not have
to load a geometry onto the calculator stack. HFSS integrates the tangential or normal
component of the quantity over the line on which you computed its tangent, or the
surface on which you computed its normal.
3. Choose the ∫ command to integrate the scalar quantity over the geometry.
To find the numerical results of an integration, use the Eval command.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Min Command
Computes the minimum of a scalar field quantity on a line, surface, or volume. Two options are
available:
Value Finds the magnitude of the minimum value of the field.
Position Finds the point where the minimum field value occurs. You can then:
• Plot the minimum field value at the point using the Plot command.
• Plot basic field quantities at the point.
• Load the point into the calculator.
• Change the point’s location.
These commands operate in the same way as the Max commands. Use the Eval command to dis-
play the actual minimum field value or the coordinates of the point where it occurs.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Max Command
Computes the maximum of a scalar field quantity on a line, surface, or volume. Two options are
available:
Value Finds the magnitude of the maximum value of the field.
Position Finds the point where the maximum field value occurs. You can then:
• Plot the maximum field at the point using the Plot command.
• Plot field quantities at the point.
• Load the point into the calculator.
• Change the point’s location.
To compute the maximum field value:
1. Load a field quantity into the calculator, and perform any necessary operations on it. Keep the
following in mind:
• You cannot find the maximum value of a vector quantity. Therefore, make sure that the
result is a scalar.
• Before computing the maximum value of a complex quantity, you must find the real part
of the quantity using the Cmplx/Real or Cmplx/AtPhase commands.
2. Load a point, line, or volume into the calculator using one of the Geometry commands.
3. Do one of the following:
• Choose Max/Value to compute the maximum field value on the geometry.
• Choose Max/Position to identify the point at which this value occurs.
Use the Eval command to display the actual maximum field value or the coordinates of the point
where it occurs.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
∇ (Gradient) Command
Takes the gradient of the scalar quantity in the top register.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
16-156 Post Processing and Generating Reports
HFSS Online Help
Ln Command
Takes the natural logarithm (base e) of the scalar quantity in the top register.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Log Command
Takes the logarithm (base 10) of the scalar quantity in the top register.
Related Topics
Using the Fields Calculator
Scalar Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Vector Commands
Use these commands to perform operations on vector quantities.
Scal? Replaces the vector in the top register with a scalar quantity whose value is a
component of the vector.
Matl Multiplies or divides the vector field quantity in the top register by a material
property, or if you select MassDensity as the material property, produces a
scalar that operates like a named variable.
Mag Takes the magnitude of the vector quantity in the top register. The magnitude
of a complex vector is defined to be the length of the real vector resulting from
taking the modulus of each component of the original complex vector.
Dot Takes the dot product of the vector quantities in the top two registers.
Cross Takes the cross product of the vector quantities in the top two registers.
Divg Takes the divergence of the vector quantity in the top register.
Curl Takes the curl of the vector quantity in the top register.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Cross Command
Takes the cross product of the vector quantities in the top two registers.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Divg Command
Takes the divergence of the vector quantity in the top register.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Curl Command
Takes the curl of the vector quantity in the top register.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Tangent Command
.
Vector quantity
Line
Magnitude
Tangential Component
To take the tangent of a vector:
1. Load a vector quantity into the top register.
2. Load a line into the top register using the Geometry/Line command.
3. Click Tangent.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Normal Command
Computes the normal component of a vector quantity on a surface such as a cutplane or object sur-
face. This is the equivalent of taking the dot product of the quantity with the surface’s unit normal
Normal = A ( x, y, z ) • n̂
vector:
Vector quantity
A(x,y,z)
Surface
Note Because surface normals of sheets are not well defined the fields calculator can produce
incorrect results if an expression is evaluated on a sheet. To enforce the correct direction
of the surface normal of a sheet, a faceted 3D object (such as a box) can be defined such
that one of its planar faces is coincident with the sheet. Because surface normals of a
valid object are always defined in an outward direction in HFSS, the fields calculator
uses the surface normal of the face of the 3D object that is coincident with the sheet.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Unit Vec Command
Computes the normal or tangent unit vector. The unit vector is a "wild card" entry. The context is
specified at the time of plotting, integrating, or report generation.
Select from the following:
Tangent Computes the unit vector tangent to the line specified at the time of
plotting, integrating, or report generation based on the context.
Normal Computes the unit vector normal to the surface specified at the time of
plotting, integrating, or report generation based on the context.
CoordSys(X) Computes the unit vector in the X-dimension of the relative coordinate
system in the top register of the calculator stack. Add the relative CS as
a geometric object using the Geometry/Coord command.
CoordSys(Y) Computes the unit vector in the Y-dimension of the relative coordinate
system in the top register of the calculator stack. Add the relative CS as
a geometric object using the Geometry/Coord command.
CoordSys(Z) Computes the unit vector in the Z-dimension of the relative coordinate
system in the top register of the calculator stack. Add the relative CS as
a geometric object using the Geometry/Coord command.
Related Topics
Using the Fields Calculator
Vector Commands
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Output Commands
Use these commands to compute or evaluate expressions and to output the data in the calculator.
Value command Computes the value of a field quantity at a point.
Eval command Numerically evaluates and displays the results of calculator operations.
Write command Saves the contents of the top register to a disk file.
Export command Saves field quantities in a format that can be read by other modeling or
post-processing software packages.
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Value Command
This computes the value of a field quantity at a point. Use it to find:
• The magnitude of a scalar field quantity at that point.
• The x-, y-, and z-components of a vector field quantity at that point.
To find the value of a field quantity at a point:
1. Load the field quantity into the top register, and perform any needed operations on it.
2. Load the appropriate point into the calculator using the Geometry/Point command.
3. Click Value.
To view the numerical results of this operation, use the Eval command.
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Eval Command
This command numerically evaluates and displays the results of calculator operations such as inte-
grations, maximum or minimum field computations, field values at points, and so forth. The quan-
tity to be evaluated must be in the top register. The Eval command computes the numerical results
of the operation, which replace the contents of the register.
For instance, to find the current around a loop, you must numerically evaluate the following inte-
°∫
gral for that loop: I = H • dl .
Since H and I are complex quantities, you will need to evaluate the real part of H to obtain the real
part of I, then evaluate the imaginary part of H to obtain the imaginary part of I. To do this:
1. Load H into the calculator using the Qty command.
2. Take the real part of H using the Cmplx/Real command.
3. Load the rectangular loop using the Geom/Line command. Create the loop, a closed polyline,
to integrate over.
4. Click Tangent to get the component of H along the line.
5. Take the integral around the loop using the ∫ command.
6. Click Eval to evaluate the integral. The real part of I appears in the top register.
7. Repeat this process using the imaginary part of H (found with the Cmplx/Imag command) to
obtain the imaginary part of I.
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Write Command
This command saves the contents of the top register to a disk file. Use this command to:
• Save registers for use during a later post-processing session.
• Save a field quantity for use when post processing a different model.
To save a register:
1. Click Write.
2. If the register includes numeric with a constrained quantity (such as jsurf), you see a dialog
that gives a choice of constraining geometries. For example:
a format that can be read by other modeling or post-processing software packages. Two options are
available for defining the grid points on which to export:
Input grid points from Maps the field quantity to a customized grid of points. Before using this
file command, you must create a file containing the points and units.
Calculate grid points Maps the field quantity to a three-dimensional cartesian grid. You
specify the dimensions and spacing of the grid in the x, y, and z
directions, with units that you specify. The initial units are taken from
the model.
To export a field quantity to a customized grid:
1. Load the quantity into the top register for the fields calculator, and perform any operations on
it.
2. If desired, load a volume using the Geometry command.
You can use the Domain command to limit the calculation to the volume you specify. If you
export a Domain filtered numeric, points that are filtered out by the domain will not be written
out.
3. Click the Export button in the Fields Calculator.
This opens the Export Solution dialog.
4. Type or select the name of the file in which the field quantity is to be saved in the Output File
Name text box. You can use the file icon to open the file browser to specify the file name and
directory path. A .reg extension is automatically assigned to this file.
5. Click either the Input grid points from file radio button if you have a created a .pts file con-
taining the grid points, or click the Calculate grid points radio button. For each grid dimen-
sion (X, Y, and Z), enter the following:
Minimum The minimum x-, y-, or z-coordinate of the grid, and unit of measure.
Maximum The maximum x-, y-, or z-coordinate of the grid, and unit of measure.
Spacing The distance between grid points, and unit of measure.
When you export fields on a 1D or 2D line/surface from the field
calculator, the start and stop values must be the same for one or two of
the XYZ start/stop ranges. If you specify a zero spacing for a
dimension, the export uses only the minimum value.
• If you select Input grid points from file, either type the name and directory of the file
containing the points on which the field is to be mapped, or, click on the file icon and use
Note The .pts file should contain the units to use for the export as shown in this file stub:
Unit=mm
-5.5 -5.5 -5.21475
-5.5 -5.5 -5.14425
-5.5 -5.5 -5.07375
-5.5 -5.5 -5.021
• If you select Calculate grid points button. For each grid dimension (X, Y, and Z), enter
the following:
Minimum The minimum x-, y-, or z-coordinate of the grid, and unit of measure.
Maximum The maximum x-, y-, or z-coordinate of the grid, and unit of measure.
Spacing The distance between grid points, and unit of measure.
When you export fields on a 1D or 2D line/surface from the field
calculator, the start and stop values must be the same for one or two of
the XYZ start/stop ranges. If you specify a zero spacing for a
dimension, the export uses only the minimum value.
6. For larger files, you may want to uncheck the Include points in output file box. If you
uncheck the box, the file header will include minimum, maximum and spacing information
from which you can recalculate the grid points.
7. Click OK to export the file.
The field quantity is mapped to the grid and saved to the file you specified (.reg extension.).
Related Topics
Using the Fields Calculator
Input Commands
Domain command
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Calculating Derived Field Quantities
The Named Expressions panel displays expressions that can be included in register definitions by
name. You can add additional expressions to the Named expression list by creating the expression
in the register display area, and the clicking the Add button. This lets you add to the Named expres-
sion library.
Click on a named expression to select it. When a named expression has been selected, the Copy to
Stack button is activated. Click Copy to Stack to push the expression on the top of the stack.
When an HFSS design is open and a Solution Setup has been performed, the following predefined
named expressions are available:
Related Topics
Named Expression Library
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Named Expression Library
The named expression library in the Fields Calculator provides a way to conveniently calculate fre-
quently used quantities. The library comes with several predefined expressions. You can combine
calculator Input commands in any legal fashion, including complex quantities, to produce new
named expressions.
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Exiting the Fields Calculator
Click Done to exit the Fields Calculator.
Related Topics
Using the Fields Calculator
In addition to the online help, you can also view a pdf format HFSS Fields Calculator Cookbook: A
Brief Primer and Collection of Step-byStep Calculator Recipes for Use in Fields Post Processing.
. in pdf format.
Note When computing near and far fields, keep in mind that you must have defined at least
one radiation or PML boundary in the design. At any time you may change the radiation
surfaces that HFSS uses when calculating the radiated fields without needing to re-solve
the problem, but the radiation-type boundary is still required.
Related Topics
Setting Up a Near-Field Sphere
Setting Up a Near-Field Line
Drawing Non-Model Objects
Computing Maximum Near Field Parameters
Setting up a Far-Field Infinite Sphere
Defining Antenna Arrays
Computing Antenna Parameters
Technical Notes: Radiated Fields
2. Use the Sphere tab define the Name, Radius, and sampling of Phi and Theta for the near-
field sphere. The radius is measured from the origin of the sphere’s coordinate system, which
you specify under the Coordinate System tab. You can assign a variable to the radius, and a
post-processing variable will often make sense in this context.
Specify the sphere’s sampling in terms of Start, Stop, and Step Size angles given in radians or
degrees. To verify your settings, use the View Sweep Points button to display a list of the theta
and phi sweep points. See Spherical Cross-Sections in the Technical Notes for guidelines for
setting phi and theta.
You can use Save as Defaults to set the current values as the default for new near-field sphere
setups.
3. Use the Coordinate Systems tab to specify the orientation of the sphere.
Use global coordinate system is selected by default, but in some cases the orientation of the
antenna requires the use of a local coordinate system. In this case, select Use local coordinate
system, and choose a local coordinate system that you created previously in the modeler.
4. Use the Radiation Surface tab to select the solved surface from which to calculate radiated
fields.
Use Boundary Radiation Surfaces is selected by default, indicating that the radiated fields
will be calculated using the assigned radiation or PML surface. For some models you may find
it it more efficient and/or accurate to use an interior surface. In this case, select Use Custom
Radiation Surface, and choose a face list that you previously created in the modeler.
Notes
You must have defined at least one radiation or PML boundary in the design for HFSS to compute
near-field quantities, regardless of which radiation surfaces you instruct HFSS to use when calcu-
lating the near fields. You do not need to re-solve the problem if you modify radiation surfaces in
the Near Field Radiation Sphere Setup dialog.
Related Topics
Selecting Faces
Creating a Face List
Radiated Fields Post Processing
Assigning PML Boundaries
Assigning Radiation Boundaries
Technical Notes: Spherical Cross-Sections
Setting up a Near-Field Line
To evaluate the near field along a line, set up a near-field line. The near-field line can be a polyline
with one or more segments. To plot near-field values along the line, you will select the line object
from the Geometry list in the Traces dialog box when you create a report.
1. Draw a polyline in post-processing mode.
2. Click HFSS or HFSS-IE>Radiation>Insert Near Field Setup>Line.
3. Under the Near Field Line Setup tab, type a name for the line in the Name text box.
4. Select the polyline along which you want to evaluate the near fields from the Choose Line list.
5. Specify the Number of points in the line.
This is the total number of equally spaced points on the line. Specifying points on the line will
enable you to plot the near-field values across a normalized distance, that is, to create a value
versus distance plot of a near-field quantity on the line.
You can click the View Sweep Points button to view a dialog that lists the points.
6. Click the Radiation Surface tab.
By default, the Use Boundary Radiation Surfaces radio button is selected.
To specify a surface other than an assigned radiation or PML boundary over which to integrate
the radiated fields, you must first create a face list. To create a facelist see Creating a Face
List.The face list cannot include a face that lies on a PML object.
If you have created one or more face lists, the Use Custom Radiation Surface radio button is
enabled.
a. Select Use Custom Radiation Surface.
This enables the Choose from existing face list field.
b. Select a defined face list from drop down menu.
HFSS will use the surfaces in the face list as the radiating surfaces when calculating the near
fields.
7. Click OK.
You must have defined at least one radiation or PML boundary in the design for HFSS to compute
near-field quantities, regardless of which radiation surfaces you instruct HFSS to use when calcu-
lating the near fields. You do not need to re-solve the problem if you modify radiation surfaces in
the Near Field Line Setup window.
Note For parts of the near-field line lying outside of the model region, near-field
approximation is calculated. However, if parts of the line lie inside the model region, the
model fields are used to compute interpolated values. A section of the near-field line is
considered to overlap the model if it lies in the enlarged model region after accounting
for symmetry planes.
Related Topics
Assigning PML Boundaries
Assigning Radiation Boundaries
Radiated Fields Post Processing
Computing Maximum Near-Field Parameters
You must have defined at least one radiation or PML boundary in the design for HFSS to compute
maximum field data for the near-field region.
1. Right-click the Sphere or Line icon in the project tree, and then click Compute Max Param-
eters on the shortcut menu.
The Select Solution dialog box appears.
2. Under the Solutions tab, select the solution for which you want HFSS to compute the near-
field parameters.
3. Under the Intrinsic Variables tab, select the solved frequency point at which you want HFSS
to compute the near-field parameters.
The Max Field Data window appears, listing the following information:
Total
X
Y
Z
Phi
Theta
LHCP
RHCP
Ludwig 3/X dominant
Ludwig 3/Y dominant
Note When calculating the maximum far-field values, the distance r is factored out of the E-
field. Therefore, the units for the maximum field data values are given in volts.
Related Topics
Radiated Fields Post Processing
Assigning PML Boundaries
Assigning Radiation Boundaries
Technical Notes: Maximum Near-Field Data
Setting up a Far-Field Infinite Sphere
To evaluate radiated fields in the far-field region, you must set up an infinite sphere that surrounds
the radiating object. To plot far-field values across the sphere, you will select the sphere object from
the Geometry list in the Traces dialog box when you create a report.
1. Click HFSS or HFSS-IE>Radiation>Insert Far Field Setup>Infinite Sphere.
The Far Field Radiation Sphere Setup window appears.
2. Use the Sphere tab define the Name, Radius, and sampling of Phi and Theta for the near-
field sphere. The radius is measured from the origin of the sphere’s coordinate system, which
you specify under the Coordinate System tab. You can assign a variable to the radius, and a
post-processing variable will often make sense in this context.
Specify the sphere’s sampling in terms of Start, Stop, and Step Size angles given in radians or
degrees. To verify your settings, use the View Sweep Points button to display a list of the theta
and phi sweep points. See Spherical Cross-Sections in the Technical Notes for guidelines for
setting phi and theta.
You can use Save as Defaults to set the current values as the default for new near-field sphere
setups.
3. Use the Coordinate Systems tab to specify the orientation of the sphere.
Use global coordinate system is selected by default, but in some cases the orientation of the
antenna requires the use of a local coordinate system. In this case, select Use local coordinate
system, and choose a local coordinate system that you created previously in the modeler.
4. Use the Radiation Surface tab to select the solved surface from which to calculate radiated
fields.
Use Boundary Radiation Surfaces is selected by default, indicating that the radiated fields
will be calculated using the assigned radiation or PML surface. For some models you may find
it it more efficient and/or accurate to use an interior surface. In this case, select Use Custom
Radiation Surface, and choose a face list that you previously created in the modeler.
Note Do not use a sheet-object based face list as the radiation computation surface.
You can use the Save as Default to set the current values as a default, and the Use Defaults button
to use previously saved options.
Note You must have defined at least one radiation or PML boundary in the design for HFSS to
compute far-field quantities, regardless of which radiation surfaces you instruct HFSS to
use when calculating the far fields. You do not need to re-solve the problem if you
modify radiation surfaces in the Far Field Radiation Sphere Setup window.
Related Topics
Radiated Fields Post Processing
Assigning PML Boundaries
Assigning Radiation Boundaries
Technical Notes: Spherical Cross-Sections
Creating a Face List
Defining Antenna Arrays
Define a regular or custom antenna array when you want HFSS to compute antenna array radiation
patterns and antenna parameters for designs that have only a single array element. HFSS models the
array radiation pattern by applying an "array factor" to the single element’s pattern when far fields
are calculated.
The "regular uniform array" geometry defines a finite 2D array of uniformly spaced, equal-ampli-
tude elements. This is a natural specification after phased array applications. The "custom array"
geometry defines an arbitrary array of identical elements distributed in 3D space with individual
user-specified complex weights.
If you define an antenna array, the antenna setup icon in Project tree changes from a single antenna
an array icon.
Related Topics
Radiated Fields Post Processing
Defining a Regular Antenna Array
Defining a Custom Antenna Array
Defining a Regular Antenna Array
A regular antenna array is a finite 2D array geometry of uniformly spaced, equal-amplitude cells
with a linear phase shift.
1. Click HFSS or HFSS-IE>Radiation>Antenna Array Setup.
The Antenna Array Setup window appears.
2. Under the Array Type tab, select Regular Array Setup.
3. Click the Regular Array tab.
4. Under First Cell Position, enter the xyz-coordinates where the first cell is placed.
5. Under Directions, define the lattice vectors:
a. To the right of U Vector, enter the vector coordinates in the X, Y, and Z text boxes along
which the cells in the U-direction are placed.
b. To the right of V Vector, enter the vector coordinates in the X, Y, and Z text boxes along
which the cells in the V-direction are placed.
6. Under Distance Between Cells, enter the distance between cells in the U-direction and the dis-
tance between cells in the V-direction in the design units.
7. Under Number of Cells, enter the number of unit cells in the U-direction and the number of
unit cells in the V-direction.
8. Under Scan Definition, specify the scan direction in one of the following ways:
• Select Use settings from slave boundary. If the design includes a master/slave set, you
can select this to use that scan angle.
• Select Use Custom Scan Angles to directly enter the scan angles in degrees, in the radia-
tion coordinate system in the Theta and Phi text boxes.
• Select Use Differential Phase Shift to enter the phase difference in degrees, between
adjacent elements, in the In U direction and In V direction text boxes.
9. Click OK.
The array factor will be applied, using the information you specified, when far fields are calcu-
lated.
Related Topics
Radiated Fields Post Processing
After you have selected the setup by one of these two methods. the Antenna Parameters dia-
log box appears.
2. Under the Solutions tab, select the solution for which you want HFSS to compute antenna
parameters.
3. Under the Intrinsic Variables tab, select the solved frequency point at which you want HFSS
to compute antenna parameters.
The Antenna Parameters window appears. If the design includes ports, the following antenna
parameters are listed:
Maximum intensity (Max U)
Peak directivity
Peak gain
Peak realized gain
Radiated power
Accepted power
Incident power
Radiation efficiency
Front to Back Ratio
Decay Factor
Warning The computed values of max U and peak directivity depend on the user-determined
set of aspect angles chosen for the computation of the radiated fields. If this set does
not encompass the actual peak intensity of the radiated pattern, the displayed results
for these three parameters will be inaccurate.
Note Accepted Power is computed from the raw S-parameter data. Post-processing operations
are excluded from the calculation, for example, renormalized S-parameters.
Gain and realised gain are very close to each other when the antenna is matched. However, for
designs with a multi-port antenna, gain and realized gain can be different if incident and
accepted power are different. There can be a small reflection at the ports and accepted power
may still be small if energy injected in one port exits the model through a different port. A
review of the S-matrix can show this to be the case. This does not happen in a single port
antenna, which is what most users base their expectations on.
If the design does not have ports, the following antenna parameters are listed:
Maximum
intensity (Max U)
Peak directivity
Radiated power
4. Click More to view the following maximum far-field data:
Total
X
Y
Z
Phi
Theta
LHCP
RHCP
Ludwig 3/X dominant
Ludwig 3/Y dominant
Note When calculating the maximum far-field values, the distance r is factored out of the E-
field. Therefore, the units for the maximum field data values are given in volts.
Related Topics
Radiated Fields Post Processing
Exporting Antenna Parameters and Maximum Field Data
Technical Notes: Antenna Parameters
Technical Notes: Maximum Far-Field Data
Add Trace Characteristics
Exporting Antenna Parameters and Maximum Field Data
The Antenna Parameters dialog displays the calculated antenna parameters and Maximum Field
data for a setup. The dialog also includes a buttons to Export antenna parameters and to Export
Fields. The fields can be exported in the.csv format and imported into reporter as a table.
To export the antenna parameters to a text file:
1. Click the Export button on the Antenna Parameters dialog.
This displays a file browser.
2. Specify the file name and location (or accept the defaults).
3. Click Save.
This saves the text file and closes the browser.
To export the maximum field data to a comma separated format file:
1. Click the Export Fields button on the Antenna Parameters dialog
This displays a file browser
2. Specify the file name and location (or accept the defaults.
3. Click Save.
This saves the comma separated text file and closes the browser.
The first line of the file describes the contents of each succeeding row by column.
Far fields format:
Index, Phi(rad), Theta(rad), rEPhi(mag ang), rETheta(mag ang)
Near fields format:
Index, X, Y, Z, Ex(mag ang), Ey(mag ang), Ez(mag ang)
Related Topics
Radiated Fields Post Processing
Computing Antenna Parameters
Technical Notes: Antenna Parameters
Technical Notes: Maximum Far-Field Data
Related Topics
Setting Mesh Plot Attributes
Setting Mesh Plot Attributes
1. Click HFSS or HFSS-IE>Field Overlays>Modify Plot Attributes .
The Select Folder window appears.
2. Select the folder containing the mesh plot you want to modify, and then click OK.
All plots in the selected folder will be modified.
A dialog box with mesh plot attribute settings appears.
3. Click the mesh plot you want to modify in the Plot list.
4. Use the Scale factor slider to increase (move to the right) or decrease (move to the left) the
percentage of the tetrahedra size.
For example, a scale factor of 80% draws the tetrahedra at 80% of their original size.
5. Use the Transparency slider to increase (move to the right) or decrease (move to the left) the
transparency of the plot.
This is useful for viewing objects or plots behind the current plot.
Very fine gives the most accurate display, though using the most memory.
11. Click the Save as default button if you want the tab’s settings to apply to mesh plots created
after this point.
12. Select Real time mode if you want the changes to take effect immediately in the view win-
dow.
If this option is cleared, click Apply when you want to see the changes.
13. Click Close to dismiss the dialog box.
Related Topics
Plotting the Mesh
The simulation technique used to calculate the full 3D electromagnetic field inside a structure is
based on the finite element method. Although its implementation is largely transparent, a general
understanding of the method is useful in making the most effective use of HFSS.
The HFSS Technical Notes provide an overview of the finite element method and its implementa-
tion in HFSS. They also describe how modal S-parameters are computed from the simulated elec-
tric and magnetic fields and how they can be converted to "nodal" or "voltage" based pseudo-S-
parameters used in circuit theory.
Information is included on the following:
• The Finite Element Method • Integral Equation Method Used in HFSS-IE
• The HFSS Solution Process • Transient Solution Theory
• Domain Decomposition • Excitations
• S-Parameters • Materials
• Radiated Fields • Parametric Analysis
• Geometric Objects • Sensitivity Analysis
• Boundaries • Tuning Analysis
• Modes to Terminals Conversion
By representing field quantities in this way, the system can transform Maxwell’s equations into
matrix equations that are solved using traditional numerical methods.
Rectilinear Elements and Curvilinear Elements
In the Finite Element Method (FEM), the physical domain is subdivided into many small elements.
In the global coordinates (x, y, z), the field quantities to be solved are expanded by a set of basis
functions. Since the basis functions are associated with each element, it is more convenient to write
them in the local coordinates (u, v, w), which are independent of the shape of the element. The local
coordinates and the global coordinates are linked by a transformation through a so-called Jocobian.
If the transformation is linear, the elements are called rectilinear elements, with straight edges and
planar faces; if the transformation is non-linear, such as quadratic or cubic, the elements are called
curvilinear elements, with curved edges and/or curved faces. So the curvilinear elements are a more
general type of elements than their rectilinear counterparts. While they may not always conform
exactly to the curved boundaries, the curvilinear elements conform better with less number of ele-
ments than the rectilinear ones. As a result, they generate more accurate and usually faster FEM
solutions.
Basis Functions
Various interpolation schemes, or basis functions, can be used to interpolate field values from nodal
values.
• A first order tangential element basis function interpolates field values from both nodal values
at vertices and on edges.
First order tangential elements have 20 unknowns per tetrahedron.
• A zero order basis function makes use of nodal values at vertices only — and therefore
assumes that the field varies linearly inside each tetrahedron.
Zero order tangential elements have six unknowns per tetrahedron.
• A second order tangential element interpolates field values from nodal values at vertices, on
edges and on faces.
Note HFSS does not generate an initial mesh each time it starts the solution process. The
initial mesh is generated only if a current mesh is unavailable.
Related Topics
Reverting to the Initial Mesh
Seeding the Mesh
Guidelines for Seeding the Mesh
Length-Based Mesh Refinement
Skin Depth-Based Mesh Refinement
Surface Approximation Settings
Guidelines for Modifying Surface Approximation Settings
Meshing Region Vs. Problem Region
Mesh Refinement on Ports
Model Resolution
Seeding the Mesh
In HFSS, mesh operations are optional mesh refinement settings that enable you to provide HFSS
with engineering guidance based on your knowledge of the parts of the model geometry that are
critical to the structure’s electromagnetic performance. Providing such guidance to HFSS prior to
beginning the adaptive analysis process can reduce (sometimes extensively) the number of passes
necessary to converge upon a field solution as well as the final number of tetrahedra in the mesh for
that solution. Although adaptive analysis convergence targets areas where field behavior is found,
refining the mesh using more than the standard criteria, such as material characteristics, can result
in finding areas of critical field behavior as soon as the first few passes are solved.
The technique of guiding HFSS’s mesh construction is referred to as "seeding" the mesh. Seeding is
performed using the Mesh Operations commands on the HFSS menu.
You can instruct HFSS to refine the length of tetrahedral elements on a surface or within a volume
until they are below a certain value (length-based mesh refinement) or you can instruct HFSS to
refine the surface triangle length of all tetrahedral elements on a surface or volume to within a spec-
ified value (skin depth-based mesh refinement.) These types of mesh operations can be defined at
any time. If you apply them before the adaptive solution process, they are used to refine the initial
mesh after it has been generated. You can also choose to apply mesh operations without generating
a solution, in which case the mesh operations are applied to the current mesh.
In a few circumstances, you may also want to define a mesh operation that modifies HFSS’s surface
approximation settings for one or more faces. Surface approximation settings are only applied to
the initial mesh.
Related Topics
Defining Mesh Operations
Technical Notes: The Mesh Generation Process
Guidelines for Seeding the Mesh
While seeding the mesh is not required, it is useful in the following conditions:
• Seeding the mesh inside a volume in the model geometry where regions of strong electric
or magnetic fields (with strong capacitive or inductive loading) are expected. Examples
include a capacitively loaded gap in a resonant structure, sharp waveguide angles or cor-
ners, or gaps between multi-coupled lines in filter structures.
• Seeding the mesh on every face of higher aspect ratio boundaries, such as long PCB traces
or on the surfaces of long wires. Spacing the mesh points roughly equal to the trace width
of the wire diameter enables you to more accurately capture the behavior of the high-
aspect structure from the first adaptive pass.
Related Topics
Defining Mesh Operations
Length-Based Mesh Refinement
When you request length-based mesh refinement, you instruct HFSS to refine the length of tet-
rahedral elements until they are below a specified value. The length of a tetrahedron is defined
as the length of its longest edge.
You can specify the maximum length of tetrahedra on faces or inside of objects. You can also
specify the maximum number of elements that are added during the refinement. When the ini-
tial mesh has been generated, the refinement criteria you specified will be used to refine the
initial mesh.
Related Topics
Assigning Length-Based Mesh Refinement on Object Faces
Assigning Length-Based Mesh Refinement Inside Objects
Skin Depth-Based Mesh Refinement
When you request skin depth-based mesh refinement, you instruct HFSS to refine the surface
triangle length of all tetrahedral elements on a face to within a specified value. A layered mesh
is created based on the surface mesh. The layers are graded based on the skin depth and num-
ber of layers you specify.
During skin depth-based mesh refinement, HFSS creates a series of layers that are planes par-
allel to the object face, and that are spaced within the specified skin depth. For each point on
the surface of the face, a series of points (P0, P1, P2, ..., Pn) are added to the mesh, where n is
the number of layers. P0 is the point on the surface and the distance from P0 to Pn is the skin
depth. The points are spaced in a non-uniform manner, with the distance between them
decreasing in a geometric progression, as you move from Pn to P0.
For example, if
Skin Depth: 12 mm
Number of Layers of Elements: 4
then
Distance [P0,P1]: 0.8 mm.
Distance [P1,P2]: 1.6 mm.
Distance [P2,P3]: 3.2 mm.
Distance [P3,P4]: 6.4 mm.
Distance [P0,P4]: 0.8 + 1.6 + 3.2 + 6.4 = 12 mm
The skin depth-based refinement first satisfies the surface triangle edge length criterion, then
introduces the series of points to each additional layer. If a limit has been placed on mesh
growth, one of the following happens:
• The limit is set high enough to complete the skin depth refinement.
• The limit is set high enough to satisfy the surface triangle edge length criterion, but not
high enough to complete the depth seeding.
• The limit is not set high enough to satisfy even the surface triangle edge length criterion.
Because refining by skin depth can add many seeding points, you should first refine the surface
of the object using length-based mesh refinement to obtain an accurate count of the number of
points HFSS will add when refining by skin depth. This allows you to reach the surface edge
length criterion and approximate the number of elements in the mesh and the number of points
on the surfaces before proceeding to skin depth seeding.
The refinement criteria you specified are used to refine the current mesh.
Related Topics
Assigning Skin Depth-Based Mesh Refinement on Object Faces
Surface Approximation Settings
Object surfaces in HFSS may be planar, cylindrical or conical, toroidal, spherical, or splines. The
original model surfaces are called true surfaces. To create a finite element mesh, HFSS first divides
all true surfaces into triangles. These triangulated surfaces are called faceted surfaces because a
series of straight line segments represents each curved or planar surface.
For planar surfaces, the triangles lie exactly on the model faces; there is no difference in the loca-
tion or the normal of the true surface and the meshed surface. When an object’s surface is non-pla-
nar, the faceted triangle faces lie a small distance from the object’s true surface. This distance is
called the surface deviation, and it is measured in the model’s units. The surface deviation is greater
near the triangle centers and less near the triangle vertices.
The normal of a curved surface is different depending on its location, but it is constant for each tri-
angle. (In this context, "normal" is defined as a line perpendicular to the surface.) The angular dif-
ference between the normal of the curved surface and the corresponding mesh surface is called the
normal deviation and is measured in degrees.
The aspect ratio of triangles used in planar surfaces is based on the ratio of circumscribed radius to
the in-radius of the triangle. It is unity for an equilateral triangle and approaches infinity as the tri-
angle becomes thinner.
17-8 Technical Notes
HFSS Online Help
You can modify the surface deviation, the maximum permitted normal deviation, and the maximum
aspect ratio of triangles settings on one or more faces at a time in the Surface Approximation dia-
log box. (Click HFSS>Mesh Operations>Assign>Surface Approximation.)
The surface approximation settings are applied to the initial mesh.
Note For the initial mesh, all the vertices of the triangles lie on the true surfaces. During
adaptive meshing, the vertices are added to the meshed surfaces, not to the true surfaces.
Related Topics
Modifying Surface Approximation Settings
Technical Notes: Guidelines for Modifying Surface Approximation Settings
Technical Notes: The Mesh Generation Process
Guidelines for Modifying Surface Approximation Settings
If you intend to modify the surface approximation settings for an object face or faces, keep the
following guidelines in mind:
• When necessary, override the default surface approximation settings to represent curved
surfaces more accurately. More accurate representation will increase the mesh size and
consume more CPU time and memory. The default settings are adequate for most circum-
stances.
• If you want to obtain a faster solution by using a cruder representation of curved surfaces,
set the coarser setting for the whole object, not just a single face.
• It is difficult for HFSS to satisfy aspect ratio demands if the aspect ratio value is set close
to 1 because an arbitrary shape cannot be filled with only equilateral triangles. Therefore,
setting the aspect ratio to 1 can lead to unreasonably large meshes. HFSS limits the aspect
ratio to 4 for planar objects and 1.2 for curved objects.
Related Topics
Modifying Surface Approximation Settings
Technical Notes: Surface Approximation Settings
Meshing Region Vs. Problem Region
HFSS distinguishes between the problem region and the meshing region. The problem region is the
region in which the solution is generated and the mesh is refined. The meshing region, which
includes the problem region, is the area in which an initial mesh is generated. After an initial mesh
is generated, the mesh is refined only in the problem region.
The problem region encompasses an area that is just large enough to include the entire design, but
no larger. HFSS automatically defines the problem region during the solution process. If you are
interested in effects outside of the structure, such as radiated effects, then you can create a virtual
object to expand the size of the problem region to include these areas.
The meshing region, like the problem region, is a box that completely encloses the structure. How-
ever the meshing region must be at least 10 times larger than the model. The part of the meshing
region not occupied by objects is considered to be the background object. The background extends
to the boundaries of the meshing region and fills in any voids not occupied by objects. Since the
background object is defined as a perfect conductor, no solution is generated inside the background
even though an initial mesh is generated for it. HFSS automatically defines the meshing region dur-
ing the solution process.
The problem region and the meshing region are illustrated below.
Problem Region
Meshing
Region
Device
Perfect
Conductor
Background Object
Model Resolution
Model Resolution is a setting that determines the smallest details of a model that the mesher
should capture and represent in the mesh.
Many times the analysis starts with the geometry already drawn in a different tool for different pur-
pose. Some tools are designed for manufacturing and the resulting models contain lots of extra
details not needed for electromagnetic analysis. If the user removes such details in the original tool
the results will be better. But if the user does not have access to the original drawing tool or redraw-
ing the model without these details is not possible, Model Resolution is another way to remove the
details from analysis.
When the user sets the model resolution length to be L, the mesher will start with a surface repre-
sentation of the model accurate to the modeler's tolerance limit. Then it will progressively remove
edges, move points, merge points etc., within the allowable model resolution limit and simplify the
surface mesh. During this process, tiny fillets, rounds, and chamfer protrusions are removed.
Other common model translation anomalies are also handled using Model Resolution. For exam-
ple, some geometry engines will blindly export all of the surfaces as splines. When a user imports
such a model for analysis, it would result in very large number of triangles. If the surface can be
represented by a smaller set of triangles using Model Resolution, this procedure would reduce the
number of triangles in the surface mesh.
The user can start with a model resolution length around 0.1*wavelength. If the model resolution
length chosen by the user is too large, the mesher will detect it and report it as an error. The model
resolution length is specified in the user units of the modeler. It can be set on selected bodies only.
The default value is 100* the tolerance limit of the ACIS modeler.
Related Topics
Specifying Model Resolution
Port Solutions
The excitation field pattern at each port must be calculated before the full 3D electromagnetic field
inside a structure can be calculated. HFSS calculates the natural field patterns (or modes) that can
exist inside a transmission structure with the same cross-section as the port. The resulting 2D field
patterns serve as boundary conditions for the full 3D problem.
• Excitation Fields
• Wave Equation
• Mesh Refinement on Ports
• Modes
• Multiple Ports on the Same Face
• Port Accuracy
• Calculating Characteristic Impedance
• Complex Propagation Constant
Excitation Fields
HFSS assumes that each port is connected to a uniform waveguide that has the same cross-section
as the port. A waveguide supports an infinite number of modes with a given field pattern and prop-
agation constant.
Therefore, the excitation field is one of the modes specified for a port where mode m can be
expressed by:
jωt – γ m z
E m ( x, y, z, t ) = ℜ E m ( x, y )e (1)
where
• ℜ is the real part of a complex number or function.
• Em(x,y) is the electric field mode pattern of mode m.
• γ m=αm + jβm is the complex propagation constant of mode m, where
• αm is the attenuation constant of mode m.
• βm is the propagation constant of mode m that determines, at a given time t, how the
phase angle varies with z.
• ω =2πf is angular frequency of oscillation,
• j is the imaginary unit, –1 .
In this context, the x- and y-axes are assumed to lie in the cross-section of the port; the z-axis lies
along the direction of propagation.
Wave Equation
The field pattern of a traveling wave inside a waveguide can be determined by solving Maxwell’s
equations. For each mode m, the port solver solves the following equation obtained from Max-
well’s equation.
⎛1 – γm z⎞ 2 – γm z
∇×⎜ ------ ∇×E m ( x, y )e ⎟ – k 0 ε r E m ( x, y )e = 0 (1)
⎝ μr ⎠
where
• k0 = ω/c is the wave number of free-space
• μr(x,y) is the complex relative permeability.
• εr(x,y) is the complex relative permittivity.
By solving the equation, the electric field mode pattern Em(x,y) and the propagation constant γm
are both obtained for all the modes specified for a given port.For the current based impedance cal-
culations, the port solver also solves independently for Hm(x,y) using a corresponding equation for
the magnetic field.
Also note that the excitation field pattern computed by the port solver is valid only at a given fre-
quency. A different excitation field pattern is computed for each frequency point of interest.
Mesh Refinement on Ports
The port solver computes mode patterns and propagation constants based on solutions of a finite
element system of equations. The finite element mesh associated with each port is a 2D mesh of tri-
angles corresponding to the faces of the tetrahedra that lie on the planar port surface. The port
solver performs an iterative refinement of the triangular mesh.
User settings for the iterative refinement can be found under Port Options in the Advanced tab of
the Solution Setup window. Those settings are reflected in the flow chart below that describe the
refinement procedure where #Triangles refer to the number of triangles of the current mesh in the
refinement process. The numerical implementation of ΔZo(k) in the flow chart is actually based on
relative difference when |Zo(k)| > 1.0. Moreover, for terminal projects the comparison is done for
each entry of the terminal characteristic impedance matrix rather than the modal impedances such
that the worst entry in the impedance matrix satisfies the user specified value.
For a good technical discussion of the port solution procedure, refer to the following:
Jin-Fa Lee, Din-Kow Sun, and Zoltan J. Cendes, "Full-Wave Analysis of Dielectric Wave-
guides Using Tangential Vector Finite Elements," IEEE Transactions on Microwave Theory
and Techniques, vol. 39, No 8, August 1991.
Related Topics
Technical Notes: The Mesh Generation Process
Modes
For a waveguide or transmission line with a given cross-section, there is a series of basic field
patterns, or modes, that satisfy Maxwell’s equations at a specific frequency. Any linear combi-
nation of these modes can exist in the waveguide. A user is responsible to specify the number
of modes to be included in a wave port but not for lumped ports since they are restricted to
contain only one mode. In general, in order to obtain accurate S-parameters the number of
modes defined for a given port should be the same or greater than the number of propagating
modes at the highest frequency of interest. Note that the port solver automatically determines
what modes should be included based on the specified number of modes. The modes included
in a port are based on a sorting criteria to extract the dominant set of modes out of the infinite
set of possible modes. If there is no prior knowledge to the number of propagating modes, the
user can do a ports only solution while specifying a reasonably large number of modes and
view the 'Gamma' values in the Matrix Data panel to determine what modes are propagating.
If a port is defined on a surface where there is a geometrical discontinuity in the normal direc-
tion of the port, it may not be enough to include only the propagating modes for accurate S-
parameters. If possible, it is recommended to avoid this case by modeling a short section of the
port transmission line such that all the higher order modes have decayed and do not contribute
to the field on the port surface. The length of the constant cross-section segment that has to be
included in the model depends on the value of the mode’s attenuation constant, α.
Degenerate Modes
Degenerate modes refer to the case when a set of modes have the same complex propagation
constant which means that any linear combination of those modes is still a valid set of natural
(or eigen) modes. When you become aware that a wave port contains degenerate modes as a
part of the requested modes, you should use the Mode Alignment feature in HFSS.
Multiple Ports on the Same Face
Visualize a port face on a microstrip that contains two conducting strips side by side as two
separate ports. If the two ports are defined as being separate, the system simulates the case in
which the two ports are connected to uncoupled transmission structures. It is as if a conductive
wall separates the excitation waves. However, in actuality, there will be electromagnetic cou-
pling between the two strips.
To model this coupling accurately, analyze the two ports as a single port with multiple modes.
In general, if there are N disconnected conductors in the port cross-section, at least N - 1 modes
are required for an accurate solution. For example, if the port consists of two adjacent
microstrip lines surrounded by a conducting enclosure, N = 3; therefore at least two modes
should be defined on the port. Assign an equal number of terminals as modes. Refer to Assign-
ing Wave Ports for Terminal Solutions for more information.
If the multi-conductor port plane is near discontinuities within the 3D model, additional modes
beyond N - 1 may be necessary. However, if you define terminals on a multi-conductor port,
the presence of non-quasi transverse electromagnetic (TEM) modes will adversely affect the
entries of any computed terminal matrices. Therefore, rather than increase the number of
modes beyond the required N - 1, extend the port outward until any higher-order modes have
sufficient attenuation to be omitted from consideration.
Port Accuracy
Generally, the port accuracy defaults, specified under the Port Options in the Advanced tab of
the Solution Setup window, are adequate. You may want improved port accuracy under the
following conditions:
• You are interested primarily in the port impedances. Port impedances are computed as part
Related Topics
Renormalizing S-Matrices
P
Z pi = -------- (1)
I⋅I
The power and current are computed directly from the simulated fields. The power passing through
a port is equal to the following:
P =
°∫ E × Hds (2)
s of the port.
where the surface integral is over the surface
The current is computed by applying Ampere’s law to a path around the port:
.
I =
°∫ H • dl (3)
l
While the net current computed in this way will be near zero, the current of interest is that flowing
into the structure, I-, or that flowing out of the structure, I+. In integrating around the port, HFSS
keeps a running total of the contributions to each and uses the average of the two in the computa-
tion of impedances.
Calculating the PV Impedance
The Zpv impedance is the impedance calculated from values of power (P) and voltage (V):
V•V
Z pv = ------------- (1)
P
where the power and voltage are computed directly from the simulated fields.
The power is computed in the same way as the Zpi impedance. The voltage is computed as follows:
V =
°∫ E • dl (2)
l
The result over which HFSS integrates is referred to as the impedance line — which is defined
when the ports are set up. To define the impedance line for a port, select the two points across
which the maximum voltage difference occurs. You must define an integration line to specify
where the maximum voltage difference will be.
Calculating the VI Impedance
The Zvi impedance is given by:
Z vi = Z pi Z pv
For TEM waves, the Zpi and Zpv impedances form upper and lower boundaries to a port’s actual
characteristic impedance. Therefore, the value of Zvi approaches a port’s actual impedance for
TEM waves.
Impedance Multipliers
If a symmetry plane has been defined (allowing the model of a structure to be cut in half), the
impedance computations must be adjusted by specifying an impedance multiplier. The need for this
multiplier can be understood by looking at how the use of symmetry affects the computation of Zpv.
In cases where a perfect E plane of symmetry splits a structure in two, only one-half of the voltage
differential and one-half of the power flow can be computed by the system. Therefore, since the Zpv
impedance is given by:
V•V
Z pv = -------------
P
the computed value is one-half the desired value. An impedance multiplier of 2 must be specified in
such cases.
In cases where a perfect H plane of symmetry splits a structure in two, only one-half of the power
flow is seen by the system but the full voltage differential is present. Therefore, structures split in
half with perfect H symmetry planes result in computed impedances that are twice those for the full
structure. An impedance multiplier of 0.5 must be specified in such cases.
If multiple symmetry planes are used or if only a wedge of a structure is modeled, you must adjust
the impedance multiplier accordingly.
If you have defined a symmetry plane, the computed impedances will not be for the full structure.
Generally, use one of the following values for the impedance multiplier:
• If the structure has a perfect E plane of symmetry, use 2. Such models have one-half of the
voltage differential and one-half of the power flow of the full structure, resulting in imped-
ances that are one-half of those for the full structure.
• If the structure has a perfect H plane of symmetry, enter 0.5. Such models have the same volt-
age differential but half the power flow of the full structure, resulting in impedances that are
twice those for the full structure.
• If the structure has a combination of perfect H and perfect E boundaries, adjust accordingly.
For example, you do not have to enter an impedance multiplier for a structure with both a per-
fect E and perfect H boundary since you would be multiplying by 2 and 0.5.
Related Topics
Setting the Impedance Multiplier
Calculating Terminal Characteristic Impedance Matrix
See Modes to Terminals Conversion.
Complex Propagation Constant
Each port is assumed to be connected to a transmission structure that has the same cross-section as
the port. The complex propagation constant, γ, of these transmission lines is computed by HFSS,
and is given by γ = α + j β, where:
• α is the attenuation constant of a signal in the transmission structure. It is the real component
of the propagation constant and has units of nepers per meter.
• β is the phase constant associated with the wave. It is the imaginary component of the propaga-
tion constant and has units of radians per meter.
Under the Matrix Data tab of the Display Items Dialog, gamma can be displayed as magnitude/
phase, real/ imaginary, magnitude, phase, real, or imaginary.
Calculating the Effective Wavelength (Lambda)
The effective wavelength, λeff, is calculated from
2π
λ eff = ------
β
where β is the phase constant associated with the wave.
Under the Matrix Data tab of the Solution Data dialog box, lambda is displayed when
Gamma is selected as the matrix type.
Calculating the Relative Permittivity (Epsilon)
The relative permittivity, εr, is calculated using
c
λ eff = ----------
εr f
where
• λeff is the effective wavelength given in meters.
• c is the speed of light.
• f is the frequency of the wave.
Under the Matrix Data tab of the Solution Data dialog box, epsilon is displayed when
Gamma is selected as the matrix type.
The Adaptive Analysis Process
An adaptive analysis is a solution process in which the mesh is refined iteratively in regions where
the error is high, which increases the solution’s precision. You set the criteria that control mesh
refinement during an adaptive field solution. Many problems can be solved using only adaptive
refinement.
Following is the general process followed during an adaptive analysis:
1. HFSS generates an initial mesh, and applies lambda refinement and manual refinements.
2. Using this mesh, HFSS computes the electromagnetic fields that exist inside the structure
when it is excited at the solution frequency. (If you are running a fast frequency sweep, an
adaptive solution is performed only at the specified solution frequency.)
3. Based on the current finite element solution, HFSS estimates the regions of the problem
domain where the exact solution has strong error. Tetrahedra in these regions are refined.
4. HFSS generates another solution using the refined mesh.
5. HFSS recomputes the error, and the iterative process (solve — error analysis — refine) repeats
until the convergence criteria are satisfied or the requested number of adaptive passes is com-
pleted.
6. If a frequency sweep is being performed, HFSS then solves the problem at the other frequency
points without further refining the mesh.
Maximum Delta S
For designs with ports.
The delta S is the change in the magnitude of the S-parameters between two consecutive passes. If
the magnitude and phase of all S-parameters change by an amount less than the Maximum Delta S
Per Pass value from one iteration to the next, the adaptive analysis stops. Otherwise, it continues
until the requested number of passes is completed.
For example, if you specify 0.1 as the Maximum Delta S Per Pass, HFSS continues to refine the
mesh until the number of requested passes is completed or until the magnitude of the complex delta
of all S-parameters changes by less than 0.1.
The maximum delta S is defined as
N N – 1⎞
Max ij mag ⎛ S – S
⎝ ij ij ⎠
where:
• i and j cover all matrix entries.
• N represents the pass number.
Related Topics
Viewing the Maximum Magnitude of Delta S Between Passes
Maximum Delta E
For designs with voltage sources, current sources, or incident waves.
Not applicable to designs with ports.
The delta E is the difference in the relative energy error from one adaptive solution to the next. It is
a measure of the stability of the computed field values from pass to pass. As the solution converges,
delta E approaches zero.
The Maximum Delta E Per Pass value is a stopping criterion for the adaptive solution. If the delta
E falls below this value, the adaptive analysis stops. Otherwise, it continues until the convergence
criteria are reached.
The data represents the delta E for all tetrahedra.
Note When the Mag S becomes small (near to zero) its phase becomes indefinite and insignificance due
to mathematical issue so that Phase Margin will be discarded.
For lossless problems, the maximum delta frequency is the largest percent change in the real part of
the frequency for any of the calculated modes. For lossy problems, the maximum delta frequency is
the greater of two quantities: the largest percent change in the real part of the frequency over all the
modes, and the largest percent change in the imaginary part of the frequency.
Max Delta (Mag S)
For solutions in which convergence criteria for specific S-matrix entries were specified.
The Max delta(Mag S) is the maximum difference of S-Matrix magnitudes between two consecu-
tive passes. If the difference in magnitudes of the S matrices change by an amount less than the
Maximum Delta Mag S value from one pass to the next, this satisfies the part of the convergence
criteria.
N N – 1⎞
Max ⎛ MagS – MagS
⎝ ij ij ⎠
Matrix Solvers
HFSS includes two solvers. The default solver and the Iterative Matrix Solver. See Enable Iterative
Solver for a discussion of when to use the Iterative Matrix solver. For details on the default solver
see Direct Matrix Solver. For details on the Iterative Matrix solver see Technical Notes: Iterative
Matrix Solver.
Direct Matrix Solver
Direct methods obtain an exact solution to the following linear system of equation
Ax = b (1)
where A is a matrix, b a right hand side and x the solution. A matrix solver using a direct method is
called a direct matrix solver.
The most widely known direct method is Gaussian elimination, which uses elementary matrix oper-
ations to compute the solution. Most other direct solution techniques are either a variant of Gauss-
ian elimination or are based upon a particular factorization of the equations that will allow an exact
computation. One of the most commonly used such techniques is the LU decomposition, which is
introduced below.
where L is a lower triangular matrix (has elements only on the diagonal and below) and U is an
upper triangular matrix (has elements only on the diagonal and above).
With the help of (2), we can equivalently solve (1) by first solving for y such that
Ly = b (3)
The advantage of decomposition (2) is that the solution of triangular set of equations (3) and (4) is
quite trivial. Namely, they can be solved directly by forward substitution and by backward substitu-
tion respectively. Furthermore, the factors in (2) are computed only once and can be reused in (3)
and (4) for different right hand sides.
In LU decomposition, the major storage is for matrix A, factor L and factor U. The major operation
is the decomposition (2), which is roughly equivalent to a matrix-matrix multiplication; while the
operation in (3) and (4) combined, is equivalent to a matrix-vector multiplication. The total compu-
tational cost is S+mT with S>>T in general, where S is the number of operations for decomposition
(2), m the number of right hand sides, and T the number of operations for both forward substitution
and for backward substitution.
Direct methods are best used for solving system matrix equations with moderate size or with a large
number of right hand sides. As the system to be solved becomes larger, the overhead associated
with the more complicated iterative methods becomes less of an issue, and the iterative methods
should outperform the direct methods. For sparse systems, the use of direct methods is complicated
by the possible introduction of more nonzero entries (fill-in) such that the L and U factors become
much denser than the original matrix A.
Iterative Matrix Solver
This section contains information on the Iterative Matrix Solver.
• Guidelines for Using the Iterative Solver
• Multiprocessing and the Iterative Solver
• Iterative Solver Technical Details
Guidelines for Using the Iterative Solver
1. The iterative solver works most efficiently when it is enabled for designs that do not contain
many excitations. (For example, the number of excitations is less than twice the number of pro-
cessors.)
2. If you choose to take advantage of the iterative solver, and your analysis includes interpolating
sweeps or discrete sweeps, the adaptive solution should be well converged at the higher end of
the frequency band.
3. The Relative Residual provides a stopping criteria. The residual measures the convergence of
the iterative solver to the solution of the matrix equation. Its value affects the performance of
the iterative solver as follows:
• Default is 1E-4. This gives accurate S-parameters and fields, indistinguishable from those
generated by the direct solver. Ansoft recommends this residual.
• With a larger residual, for example, 1E-3 or 1E-2, the iterative process will stop with
fewer iterations and the solution will be less converged. S-parameters won't differ much
from those of a direct solution, for example, a difference in third or second digit. Fields
and antenna patterns are visually the same.
• A residual of 0.1 can be used for quick adaptive mesh refinement early in the adaptive pro-
cess, but S-parameters will be noticeably different.
• A residual of 1 should never be used. The interface will not allow a residual above 0.1.
Multiprocessing and the Iterative Solver
In computing the pre-conditioner, the iterative solver uses multiple processors, if set under
Tools>Options>HFSS Options, just like the multi-frontal solver does. The operations involved
are very similar. After that, there is one iterative process per excitation. Each iterative process can
only use one processor. If you have one excitation and multiple processors, you will see that
HF3D.exe uses only one processor at this stage. If you have multiple excitations and multiple pro-
cessors, HF3D.exe will use multiple processors at this stage. For example, with four processors and
eight excitations, HF3D will perform the iterative processes for four excitations first, and for the
other set of four excitations next.
Iterative Matrix Solver Technical Details
The iterative solver always saves significant memory - easily a factor two with simulations of inter-
mediate size, and more with larger simulations. It is also faster than the multi-frontal solver with
large simulations.
The following table shows asymptotic behavior with large simulations. N = number of unknowns.
This shows that the iterative solver has a better asymptotic behavior both in RAM and in time.
Time RAM
Multi-frontal Solver N 1.7 N 1.3
Iterative Solver N 1.2 N 1.0
The iterative solver uses a preconditioner that is based on the next-lower order. Therefore, there is
no iterative solver option when you solve with zeroth order.
Consider the matrix equation
Ax = b (1)
As aforementioned, the exact solution for e in (3) is impossible since it requires A-1. However, if an
approximation M ≈ A is available, the error e can be approximated in (3) by
–1
e = M r (5)
It is (4)-(6) that form the foundation of the iterative solution method. A matrix solver using the iter-
ative solution method is called an iterative matrix solver. The method starts with an initial guess
x = x0 and repeats (4)-(6) until the approximation x to x is within tolerance, or the number of
iterations exceeds a given number. In the former case, it is said the solution converges; while in the
latter, it doesn’t.
The residual r is used for measuring the closeness of x to x. Since A and b in (1) can be scaled by
the same factor without altering x, so does the residual r in (4). It typically makes more sense to
replace ||r|| as the stopping criterion with the relative residual:
(7)
r
res = -------
b
D. K. Sun, J. F. Lee and Z. J. Cendes, "Construction of nearly orthogonal Nedelec bases for rapid
convergence with multilevel preconditioned solvers", SIAM Journal on Scientific Computing, Vol.
23, No. 4, pp. 1053-1076, 2001.
I. Bardi, G. Peng and Z.J. Cendes, "Improvements in Adaptive Mesh Refinement and Multi-level
methods in High Frequency Electromagnetics", ACES Symposium, 2002.
Related Topics
Enable Iterative Solver
Single Frequency Solution
A single frequency solution generates an adaptive or non-adaptive solution at a single frequency,
the solution frequency specified in the Solution Setup dialog box, and is often the first step in per-
forming a frequency sweep. An adaptive solution is one in which a finite element mesh is created
and automatically refined in the areas of highest error — increasing the accuracy of succeeding
adaptive solutions. The procedure for performing a single frequency solution is shown below.
Frequency Sweeps
Perform a frequency sweep when you want to generate a solution across a range of frequencies.
You may choose one of the following sweep types:
Fast Generates a unique full-field solution for each division within a frequency
range. Best for models that will abruptly resonate or change operation in the
frequency band. A Fast sweep will obtain an accurate representation of the
behavior near the resonance.
Discrete Generates field solutions at specific frequency points in a frequency range.
Best when only a few frequency points are necessary to accurately represent
the results in a frequency range.
Interpolating Estimates a solution for an entire frequency range. Best when the frequency
range is wide and the frequency response is smooth, or if the memory
requirements of a Fast sweep exceed your resources.
Note When performing a Fast sweep, no port mode may cross cut-off in the frequency
range. If this occurs, an error message appears listing the port and mode violating this
condition.
The procedure for a Discrete frequency sweep is shown below, where n equally spaced frequencies
are included in the sweep.
Set f = f0
f = fnext
Yes
if F <Flast
No
End
Be aware that HFSS uses the finite element mesh refined during an adaptive solution at the solution
frequency or, if you did not request an adaptive solution, the initial mesh generated for the problem.
It uses this mesh without further refinement.
The procedure for an Interpolating sweep is shown below, where n frequencies determined by the
system are included in the sweep.
Set f = f0
Solution Types
Driven Modal Solution
Choose the Driven Modal solution type when you want HFSS to calculate the modal-based S-
parameters of passive, high-frequency structures such as microstrips, waveguides, and transmission
lines. The S-matrix solutions will be expressed in terms of the incident and reflected powers of
waveguide modes.
Driven Terminal Solution
Choose the Driven Terminal solution type when you want HFSS to calculate the terminal-based S-
parameters of single and multi-conductor transmission line ports. The S-matrix solutions will be
expressed in terms of voltages and currents on the terminals.
Eigenmode Solution
Choose the Eigenmode solution type to calculate the eigenmodes, or resonances, of a structure.
The Eigenmode solver finds the resonant frequencies of the structure and the fields at those reso-
nant frequencies.
Eigenmode Solutions
The Eigenmode solver can find the Eigenmodes of lossy as well as lossless structures, and can cal-
culate the unloaded Q of a cavity. Q is the quality factor, and is a measure of how much energy is
lost in the system. Unloaded Q is the energy lost due to lossy materials and boundary conditions.
Because ports and other sources are restricted for eigenmode problems, the Q calculated does not
include losses due to those sources.
The following restrictions apply to Eigenmode solution designs:
• No excitations may be defined.
• Radiation boundaries may not be defined.
• Frequency sweeps are not available.
• You may not view or plot the S-matrix data.
• Designs cannot include ferrite materials.
If a material or boundary condition, other than finite conductivity, varies with frequency, the eigen-
mode solution procedure will evaluate the frequency dependant property at the user specified mini-
mum frequency and use that value during the S and T matrix assembly. This may limit the accuracy
of the solved Eigenmodes depending on how significant the property varies from the minimum fre-
quency to the eigen frequency.
Related Topics
Calculating the Resonant Frequency
Calculating the Quality Factor
Calculating the Resonant Frequency
Eigenmodes are the resonances of the structure. The eigenmode solver finds the resonant frequen-
cies of the structure and the fields at those resonant frequencies. For a Driven Solution, HFSS
solves the following matrix equation (for a lossless case):
2
Sx + k o Tx = b (1)
where
• S and T are matrices that depend on the geometry, the materials, and the mesh.
• x is the electric field solution.
• ko is the free-space wave number.
• b is the value of the source defined for the problem.
However, in order to find the resonances of the structure, the eigenmode solver sets b to zero, and
solves the equation
2
Sx + k o Tx = 0 (2)
for sets of (ko,x), one ko for every x. The variable x is still the electric field solution, and ko is the
free space wave number corresponding to that mode. The resonant frequency of the eigenmode can
be found using:
,
ko c
f = -------- (3)
2π
where
• c is the speed of light.
Calculating the Quality Factor
Q is the unloaded quality factor, and is a measure of how much energy is lost in the structure due to
lossy materials. Because ports and other sources are restricted for Eigenmode solutions, the Q cal-
culated does not include losses due to those sources.
HFSS uses the following equation to calculate the approximate quality factor:
Mag ( freq )-
Q = ----------------------------- (1)
2 ⋅ I m ( freq )
The Fields Calculator can also be used to calculate Q. In general, the equation for Q is
U
Q = ( 2π ) ( freq ) ---- (2)
P
where:
• U is the total energy stored in the cavity.
• P is the power lost, from resistive losses, for example.
Field Solutions
During the iterative, adaptive solution process, the S-parameters typically stabilize before the full
Electric field solution. Therefore, when you are interested in analyzing the field solution or quanti-
ties computed from the field solutions associated with a structure, it is advisable to use tighter con-
vergence criteria.
In addition, for any given number of adaptive iterations, the magnetic field (H-field) is less accurate
than the solution for the electric field (E-field) because the H-field is computed from the E-field
using the relationship: .
∇×E
H = -------------
– jωμ
Field Overlay Plots
In HFSS, field overlays are representations of basic or derived field quantities on surfaces or
objects. The objects on which you plot the fields may be pre-existing parts of the model geometry
or they may be objects that you draw in post-processing mode.
If you select a surface, HFSS will plot the field quantities on the surface. If you select an object,
HFSS will plot the field quantities within the volume of the object.
You can choose to create a scalar plot or a vector plot of the fields. A scalar plot can use several
user selectable plot types to illustrate the magnitude of field quantities on surfaces or volumes. A
vector plot uses arrows to illustrate the magnitudes of the x-, y-, and z-components of field quanti-
ties.
Field Quantities
The default field quantities that can be plotted, their definitions, and associated units are as follows
(see the following note for issues in HFSS-IE for plotting magnetic and electric current):
jωt
Ex ( t ) = ℜ Ex e (1)
where
• ℜ is the real part of a complex number or function.
• ω is angular frequency, 2πf.
• j is the imaginary unit, – 1 .
• t is the time.
On the other hand, if Ex is an "RMS" phasor, an additional factor of 2 is required as
follows:
jωt
Ex ( t ) = ℜ 2 Ex e (2)
As a consequence of these equations, the peak physical field, max (Ex(t)) observed over a full time
cycle is max(Ex(t)) = |Ex| for peak phasors and max(Ex(t)) = 2 |Ex| for RMS phasors.
Additionally, given field phasors E and H, to compute the time-averaged power flow through a sur-
face, the normal component of the real part of the complex Poynting vector is integrated over the
surface. The correct form of the complex Poynting vector S depends on which phasor representa-
tion is used.
1
For peak phasors,S = --- E × H∗ .
2
For RMS phasors, E= ExH*.
The conventions used by HFSS are as follows:
• Each propagating mode incident on a port contains 1 watt of time-averaged power.
• Circuit gap sources are specified in a peak sense. That is, if a voltage gap source magnitude is
5 volts, then the time domain circuit source behaves as v(t) = 5cosωt. Likewise for a current
gap source.
• Plane wave sources are specified in a peak sense. That is, if the plane wave magnitude is 5 V/
m, then the plane wave incident field magnitude is E ( t ) = 5 cos ( k ⋅ r + ω t ) .
• Radiated power, as computed by the fields post processor, is a time-averaged quantity com-
puted using the complex Poynting vector.
• Phasors in the Fields Calculator are peak phasors. The Poynting vector button in the calculator
therefore implements the Poynting vector for peak phasors,
1
S = --- E × H∗ .
2
Calculations that compute either average or instantaneous time domain quantities must adhere
to the peak phasor conventions.
Calculating the SAR
The specific absorption rate (SAR) is a measure of the amount of electromagnetic energy absorbed
in a lossy dielectric material. The SAR is a basic scalar field quantity that can be plotted on surfaces
or within objects in HFSS.
HFSS uses the following equation to calculate the SAR: σ ∗ E2/(2ρ).
where
• σ = the material’s conductivity. This is defined as: σbulk+ωε0εrtgδ
• ρ = the mass density of the dielectric material in mass/unit volume.
There are two types of SAR Field Overlay plots available in HFSS: local SAR, and average SAR.
When calculating the local SAR, HFSS uses the equation above to calculate the SAR at each mesh
point on an overlay plot. HFSS interpolates the values between the mesh points across the plot.
17-34 Technical Notes
HFSS Online Help
When plotting the average SAR, for each mesh point on the plot, HFSS reports the SAR averaged
over a volume that surrounds that point. The volume is determined by the settings for the material’s
mass density and mass of the material surrounding each mesh point set in the Specific Absorption
Rate Setting dialog box.
The Certification SAR quantity provided in the Fields Calculator is a numerical modeling of the
peak spatial-average SAR in the standard. When plotting the certification SAR, HFSS applies an
IEEE standard procedure.1 The IEEE procedure makes the following assumptions:
• The peak E-field will reside on the surface of the phantom.
• The volume used for the integration will be an equal sided cube contained completely inside
the phantom with an axis normal to the surface at the location of the peak value of the local
SAR.
Related Topics
Modifying SAR Settings
1. IEEE std C95.3 -2002. Its title is "IEEE recommended practice for measurements and computations
of radio frequency electromagnetic fields with respect to human exposure to such fields,100 kHz-300
GHz." Similar standards exist for international and European applications. For a brief introduction to
SAR standards, read "An Update on SAR Standards and the Basic Requirements for SAR Assessment"
(http://conformity.com/artman/publish/feature_193.shtml).
Technical Notes 17-35
HFSS Online Help
div(D) = ρ div(B) = 0
The mathematical framework of the Discontinuous Galerkin family of numerical methods for Max-
well’s equations has been presented by Jan Hesthaven and Tim Warburton [8, 9]. To apply the DG
method, we choose basis and test functions local to each mesh element T, in a similar way to the
Finite Element Method:
(2)
∂D
∫ ------- ⋅ ϕ =
∂t ∫ curl(H) ⋅ ϕ – ∫ J ⋅ ϕ = ∫ curl(ϕ) ⋅ H – ∫ div(ϕ × H) –∫ J ⋅ ϕ
T T T T T T
As is the case
T with the frequency-domain
T Tfinite-element solver,
T the DGTD method is free of spuri-
ous solutions [10] and supports higher-order basis functions. In the time domain, the use of high
orders minimizes dispersion errors occurring during the simulation of electrically large problems.
The DGTD solver not only employs high-order elements but allows mixed element orders in the
same mesh, known as hp-adaptivity, to optimize accuracy and solution times.
Following the same approach as in the Finite Volume Method, the divergence term containing vol-
ume integrals is transformed into surface integrals:
(3)
∂------
∫ ∫ curl(ϕ) ⋅ H + ∫ ( n × H ) ⋅ ϕ–∫ J ⋅ ϕ
D-
⋅ϕ =
∂t
T T ∂T T
∂B
∫ ∫ ∫
------- ⋅ ϕ = – curl(ϕ) ⋅ E – ( n × E ) ⋅ ϕ
∂t
T T ∂T
The tangential fields n × E and n × H are then evaluated as upwind fluxes at the surface of T by
using a Riemann solver [11]. Separating the treatment inside the element from its surface provides
a robust and flexible framework to take into account boundary conditions. This separation also
enables various combinations of locally implicit and locally explicit time-integration schemes for
instance to achieve an optimum trade-off between speed and memory, without compromising accu-
racy and stability.
Related Topics
Transient Solution Theory
Local Time Stepping
Materials in Time Domain
Excitations in Time Domain
Analysis Setup in Time Domain
References for Time Domain
Parallelism is naturally exploited with this scheme by partitioning the computational domain into
sub-domains and solving each sub-domain concurrently on multi-core or many-core systems.
Related Topics
Transient Solution Theory
Discontinuous Galerkin Finite Element Method
Materials in Time Domain
Excitations in Time Domain
Analysis Setup in Time Domain
References for Time Domain
Materials in Time Domain
In any time-domain method, handling frequency-dependent material parameters is not straightfor-
ward. Two important cases, frequently encountered in electromagnetic simulations, are (1) non-per-
fectly conducting metals and (2) lossy dielectric materials.
In most high-frequency applications, one does not solve for fields inside non-perfectly conducting
metals. Rather, the skin effect is expressed with a boundary condition on the surfaces of the metal.
Since the skin impedance is frequency dependent, containing a factor √(frequency), a suitable way
has to be found to approximate this in the time domain. In HFSS Transient, the Padé approximation
[ ] is used. With this approximation one can expect accurate results over a very wide band which
includes the highest frequency of interest. Near DC, a modest reduction in accuracy is to be
expected.
Lossy dielectric materials can be described by a bulk conductivity σ or by a loss tangent tan(δ). If
the conductivity is the only loss mechanism, the relation between the two is tan(δ) = σ/(2π×fre-
quency ×ε0εr). In any case, the loss tangent of a material is frequency dependent, and a suitable way
has to be found to approximate it in the time domain. In HFSS Transient, when a lossy dielectric is
specified with a certain loss tangent at the highest frequency of interest, the Debye model is used to
describe the material for all frequencies. The Debye model is more realistic than the assumption of
a constant loss tangent. If one uses the Debye model in the frequency domain as well, one can
expect the same results as in the time domain, except when the material touches a port. That case is
discussed in the next section.
Related Topics
Transient Solution Theory
Discontinuous Galerkin Finite Element Method
Local Time Stepping
Excitations in Time Domain
Analysis Setup in Time Domain
References for Time Domain
For this model then Va is the incident voltage and Vb is the reflected voltage seen at the port. We
know from the definition of voltage and current on a transmission line that for the total voltage, VT,
the following is true:
VT = Va + Vb (1)
If we apply Kicrchkoff's voltage law to the equivalent circuit shown in Figure 2 we see it yields the
result shown in (3). This is the port model for a terminal port in HFSS.
To be consistent then the same terminal port excitation is used in HFSS Transient. Therefore if you
define an incident voltage signal in the transient setup that signal is applied to the 3D model as a
voltage source of twice the user defined amplitude in series with the terminal impedance.
Note As a consequence of the above discussion, one needs to be careful when comparing
results with a circuit tool or textbooks using the voltage source shown in Figure 2. If one
volt is used for the voltage source in the circuit simulator, this should be compared with
a HFSS transient simulation with edit sources set to 0.5 volt.
Before considering an example one more point needs to be made. In the reporter for HFSS Tran-
sient when plotting the voltage at a given port the options are Input( ) and Output( ). Input is the
user defined incident voltage (Va in the Figure 2) and Output is the reflected voltage (Vb = VT -
Va). We can see then that to view the total voltage at the port terminals one needs to create an out-
put variable that is the sum of Input ( ) and Output( ). We will consider two examples to illustrate
this.
Consider the HFSS Transient model of a simple coax shown in the Figure 3. It is an air filled 50Ω
line that has a center section with a smaller inner radius that results in an impendence of 91.5 ohm
in that part of the line. Each section of this air filled coax (the two 50 Ω and the one 91.5 ohm sec-
tions) has a length of 100mm. This length has a time delay of 1/3 nS. This was simulated in HFSS
Transient using the incident voltage signal shown in the inset for Figure 3.
This model was simulated with a single 50 Ω terminal port on one end and a matched termination
on the opposite end. The response seen at the port is shown below in Figure 4.
Figure 4 shows the Input and Output signals at the port terminal (Cylinder1_T1). Remember that
Input( ) is the incident signal as shown in Figure 3. If one uses the equations for reflection and
transmission to compute the amplitude of the signal at the 3 points shown in the figure these text-
book equations would give 0.29, -0.27,-.02 respectively. We can see that the reflected voltage is
accurately computed for the applied signal.
For an example where one might be more interested in the total voltage a second case was consid-
ered. The same HFSS Transient model was simulated with the same incident signal, but this time
the port terminal impedance was set to 30 Ω. The HFSS Transient response for this simulation is
shown in the Figure 5.
For the time between 0.1 - 0.2 nS the textbook response says that VT should be 1.25V. Again that is
the total voltage and if you add together the 2 curves shown in the plot you would get the correct
response of 1.25V in that range.
Related Topics
Transient Solution Theory
Discontinuous Galerkin Finite Element Method
Local Time Stepping
Materials in Time Domain
Analysis Setup in Time Domain
References for Time Domain
Analysis Setup in Time Domain
Two classes of analyses exist: those focused on device characterization, and more general analyses.
In the case of device characterization, one is interested in quantities like S-parameters and/or time-
domain output at ports due to excitation of a specific port. This requires that excitations be “on”
one at a time. For each active port and mode, a separate simulation is done. These simulations are
independent and can be distributed over a network, to be executed in parallel. Each active port and
mode will employ an excitation with the same time profile.
In the more general analysis type, all active ports and modes are “on” simultaneously. Each one can
have an excitation with a different time profile. This type of analysis gives you more freedom, but
S-parameters cannot be extracted.
In both classes of simulations, fields can be saved and visualized.
Related Topics
Transient Solution Theory
Discontinuous Galerkin Finite Element Method
Local Time Stepping
Materials in Time Domain
Excitations in Time Domain
References for Time Domain
References for Time Domain
[1] Z. Cendes, D.N. Shenton, and H. Shahnasser. “Magnetic field computation using Delaunay triangu-
lation and complementary finite element method”, IEEE Trans. on Magnetics, 19(6):2551, 1983.
[2] A. Taflove, “Application of the Finite-Difference Time-Domain Method to Sinusoidal Steady-State
Electromagnetic-Penetration Problems, Electromagnetic Compatibility”, IEEE Transactions on
Volume EMC-22, Issue 3, Aug. 1980 Page(s):191 – 202
[3] T. Weiland, “A discretization method for the solution of Maxwell's equations for six-component
Fields”, Electronics and Communications, vol. 31, no. 3, pp. 116-120, 1977
[4] P. Bonnet, X. Ferrières, B. Michielsen, and P. Klotz, “Time Domain Electromagnetics”, S. M. Rao,
Ed., Academic Press, 1997, ch. 9, pp. 307-367.
[5] D. Baumann, C. Fumeaux, and R. Vahldieck, "Field-Based Scattering-Matrix Extraction Scheme for
the FVTD Method Exploiting a Flux-Splitting Algorithm," IEEE Trans. on Microwave Theory and
Tech., vol. 53, no. 11, Nov. 2005.
[6] J-F. Lee, R. Lee, and A.C. Cangellaris, “Time-Domain Finite-Element Methods”, IEEE Trans.An-
tennas Propag., vol. 45, pp. 430-442, Mar. 1997.
[7] B. Cockburn, G. Karniadakis, and C.-W Shu, “Discontinuous Galerkin Methods: Theory, Compu-
tation and Applications”, Lecture Notes in Computational Science and Engineering (Springer-Ver-
lag, New York, 2000), Vol. 11.
[8] J. Hesthaven,T. Warburton, “Nodal high-order methods on unstructured grids”, Journal of Compu-
tational Physics, v.181 n.1, p.186-221, September 1 2002.
[9] J. Hesthaven and T. Warburton, “Nodal Discontinuous Galerkin Methods Algorithms, Analysis, and
Applications”, Springer series: Texts In Applied Mathematics, vol. 54, 2007.
[10] A. Buffa, I. Perugia, “Discontinuous Galerkin approximation of the Maxwell eigenproblem”,SIAM
J. Numer. Anal. 44, 2198, 2006.
[11] Leveque, Randall, “Finite Volume Methods for Hyperbolic Problems”, Cambridge University Press,
2002.
[12] L. Fezoui, S. Lanteri, S. Lohrengel and S. Piperno, “Convergence and stability of a Discontinuous
Galerkin time-domain method for the 3D heterogeneous Maxwell equations on unstructured mesh-
es”, ESAIM: Math. Model. and Numer. Anal., Vol. 39, No. 6, pp. 1149-1176, 2005.
[13] R.A. Chilton and R. Lee, "The discrete origin of FETD-Newmark late time instability, and a correc-
tion scheme," J. Comp. Physics, vol. 224, pp. 1293-1306, 2007.
where the excitation vector b is commonly called the right-hand-side or RHS. The number of RHS
vectors depends on the total number of modes used to excite the problem.
HFSS provides three distinct solution methods. By default, a direct solver is used and is the pre-
ferred method for small to medium size problems and/or problems with a large number of modes.
A major strength of the direct solver is the ability to provide a solution for a large number of modes
with relatively small computational overhead for the multiple RHS. However, if the problem size is
too large for the machine memory, the second option is to use the iterative solver which can handle
larger problems but requires a complete solution for each RHS. The iterative solver modifies the
matrix equation (1) by multiplying both sides with a pre-conditioner, M, in order to enable a faster
solution:
MAx = Mb (2)
Both the direct solver and the iterative solver work only with a single machine's shared memory.
This limitation is addressed in HFSS with the introduction of an advanced solving technique called
the Domain Decomposition Method (DDM) which enables the use of distributed memory across
many different machines to solve very large problems.
• Basic DDM Theory
• Computational Memory
• Computational Time
Basic DDM Theory
DDM has emerged as a powerful and attractive technique due to its inherent parallelism which
enables the use of distributed memory. DDM is based on a divide-and-conquer philosophy where
instead of solving a large and complex problem directly, the original problem as defined by the
mesh is partitioned into smaller, possibly repetitive, and easier to solve sub meshes or sub-domains.
In this approach it is critical to enforce continuity of electromagnetic fields at the interfaces
between adjacent sub-domains through some suitable boundary conditions.
To illustrate the basic idea of DDM, we solve (1) by decomposing the original problem into two
domains. Subsequently, we have:
⎡ A11 A12 ⎤ ⎡ x1 ⎤ ⎡ b1 ⎤
⎢A ⎥⎢ ⎥ = ⎢ ⎥ (3)
⎣ 21 A22 ⎦ ⎣x2 ⎦ ⎣b2 ⎦
where Aii, xi and bi, i=1,2 are system matrix, solution vector and RHS for domain i, respectively
and A12, A21 are the coupling matrices between the two domains. To solve in parallel sub-domain
problems, one popular domain decomposition algorithm is of Jacobi type:
(4)
⎡ A11 A12 ⎤ ⎡ A11 0 ⎤ ⎡ 0 A12 ⎤
⎢A = + .
⎣ 21 A 22 ⎥⎦ ⎢⎣ 0 A 22 ⎥⎦ ⎢⎣ A 21 0 ⎥⎦
Using (4) and applying iteration, (3) can be solved as
(n) ( n−1) (5)
⎡ A11 0 ⎤ ⎡ x1 ⎤ ⎡b ⎤ ⎡ 0 A12 ⎤ ⎡ x1 ⎤
⎢ 0 = ⎢ 1⎥−⎢ .
⎣ A 22 ⎥⎦ ⎢⎣ x 2 ⎥⎦ ⎣b 2 ⎦ ⎣ A 21 0 ⎥⎦ ⎢⎣ x 2 ⎥⎦
Through some simple algebra, equation (5) leads to two coupled systems:
(n) (n – 1) (n) (n – 1)
A 11 x 1 = b 1 – A 12 x 2 A 22 x 2 = b 2 – A 21 x 1 (6)
By setting x1(0) = 0 and x2(0) = 0 and, we have initial guess xi(1) = Aii-1bi which is the local solution
of each sub-domain problem. These initial solutions are then refined through coupling matrices A12
and A21 until equilibrium is reached.
The approach (5) is known as a stationary Jacobi solution of (3) which unfortunately converges
rather slowly. A more advanced approach is to apply as a preconditioner
−1 −1
⎡ A11 0 ⎤ ⎡ A11 A12 ⎤ ⎡ x1 ⎤ ⎡ A11 0 ⎤ ⎡ b1 ⎤
⎢ 0 = ,
A 22 ⎥⎦ ⎢⎣ A 21 A 22 ⎥⎦ ⎢⎣ x 2 ⎥⎦ ⎢⎣ 0 A 22 ⎥⎦ ⎢⎣b 2 ⎥⎦
(7)
⎣
leading to:
⎡ I A11−1A12 ⎤ ⎡ x1 ⎤ ⎡ A11−1b1 ⎤
⎢ −1 ⎥ ⎢ ⎥ = ⎢ −1 ⎥ . (8)
⎣ A 22 A 21 I ⎦ ⎣ x 2 ⎦ ⎣ A 22 b 2 ⎦
Related Topics
Domain Decomposition Method
Basic DDM Theory
Computational Memory
Computational Time
Computational Memory
Using domain decomposition we need to solve (factorize) A11, A22 compared to solving A using
the standard method. When a direct solver is used, DDM is inherently more memory efficient since
a series of smaller matrices are needed to be solved compared to a large matrix. This is evident by
assuming that domains are equally partitioned so that (e.g. two domains) N1 = N2 = N/2 where N1,
N2, and N are numbers of unknown for the sub-domains and the original problem respectively.
Memory requirement for original problem typically scales as C1Na where C1 is a constant and α >
1. For an M domain decomposition solve, the total memory requirement is
N α
MC 1 ⎛ -----⎞ = M
1–α α
C1 N
⎝ M⎠
For example, if α = 1.5, using 2-domains we save about 30% of total memory. Also keep in mind
that the memory can be distributed across different machines enabling a problem to be solved
which is not possible on a single machine.
Related Topics
Domain Decomposition Method
Basic DDM Theory
Computational Time
Computational Time
A domain decomposition solution consists of three steps:
1. Mesh partitioning, a relatively fast process. HFSS will automatically partition the mesh into
roughly equivalent sized mesh sub-domains to balance memory and solution times for the
domains.
2. Matrix-assembly/solve where both A and M are solved in parallel
3. Domain iteration where we solve MAx=Mb via an iterative solver.
The solution time for solving the entire system (1) without DDM requires C2Nβ operations with a
direct solver where C2is a constant and β > 1 (and typically larger than α). For an M domain
DDM solve, the factorization time of step 2 above is dominated by the most time consuming (i.e.
largest) domains, given as:
N β
C 2 ⎛ -----⎞ = M C 2 N
–β β
⎝ M⎠
Therefore, given β > 1, this stage exhibits a super-linear speed-up. This type of speed-up is com-
monly referred to as "scalable".
For step 3 the major computation is on the matrix-vector multiplication (MA)x which can be paral-
lelized. In each iteration, the master node produces a new solution vector x and then sends its
appropriate components to each domain (cpu/node/machine). Each domain then sends back to the
master the vector y=MAx which is used by the master to produce a new solution vector x. This pro-
cess goes on until x converges. In this step, the cost of matrix-vector multiplication per iteration is
also scalable with respect to number of domains. Therefore if the iteration number remains rela-
tively unchanged as number of domains increases, the domain decomposition solver can exhibit
overall scalable performance.
Related Topics
Domain Decomposition Method
Computational Memory
Basic DDM Theory
n̂ × ( E inc + E scat ) = 0
The above relation only specifies the scattered field on the surface of the conductor. To fully under-
stand the system, we need to be able to calculate the scattered field everywhere; one way to do this
is to calculate the induced current which generates the scattered electric field.
The field generated by a current is
1 2
E ( r ) = --------- ( ∇∇ • + k ) ∫ J ( r' ) G ( r – r' ) dr'
j ωε
and J is the surface current density. Combining the relationship between current and scattered field
with the boundary condition yields the EFIE
1 2
n̂ × E inc = n̂ × --------- ( ∇∇ • + k ) ∫ J ( r' ) G ( r – r' ) dr'
j ωε
The unknown current density is within the integral operator; these types of equations are known as
integral equations. Also note the integral is a convolution. Electromagnetic integral equations are
convolutions, and this allows us to make an analogy to system theory. The Green's function is the
transfer function, or the impulse response of the system, and the incident electric field is the output.
Our task is to find the input, or the current density, from the output knowing the transfer function.
Solving the EFIE is typically done through a finite element technique. We divide the surface of the
conductor into many, many triangles, and on each triangle we assume a current distribution. This
converts EFIE into a matrix equation, and in the electromagnetics literature this technique is called
the method of moments (MoM).
The EFIE is just one of many different integral equations used in electromagnetics. We can vary the
boundary conditions we enforce, or the method we use to specify the field everywhere. For exam-
ple, if on the surface of the conductor, we enforce the continuity of the magnetic field, following a
similar procedure yields the magnetic field integral equation (HFIE). All of them are similar in
form to the EFIE and are solved in a similar manner.
References:
1. Roger Harrington, Time Harmonic Electromagnetic Fields, McGraw-Hill, New York, NY
1961.
2. Andrew Peterson, Scott Ray, Raj Mittra, Computational Methods for Electromagnetics, IEEE
Press, New York, NY 1998.
S-Parameters
One of the most important features of HFSS is the capability to categorize an electromagnetic
structure in a compact manner using the concept of S-parameters. S-parameters are available for
projects that contain ports and this document focuses on the case when the S-parameters are related
to the eigen modes of the ports. The use of S-parameters for terminals are described in Modes to
Terminals Conversion.
At each port, the modal representations of the electric and magnetic fields assuming K modes are:
K
E = ∑ ( a m + bm ) em
m=1
K
H = ∑ ( am – bm ) hm
m=1
where am and bm are unitless complex amplitudes of the incident and reflected modal fields, respec-
tively. Given a particular electromagnetic structure, it can be categorized in terms of the incident
and reflected/transmitted modal amplitudes using the NxN generalized S-matrix, S:
b = Sa
where a and b are unitless complex modal coefficient vectors. The size of these vectors, N, is the
total number of modes obtained by adding up the number of the modes on all ports.
An entry of the S-matrix, Sij, specifies the multiplication factor to be applied to the incident modal
amplitude aj to get the reflected/transmitted modal amplitude bi given that all the other incident
modes are turned off. This can be described mathematically as:
bi
S ij = ----
aj
ak = 0 , k ≠ j
HFSS automatically provides an S-matrix when a project contains ports. The following links con-
tain information on various topics related to S-matrices.
• Post Processed S-Matrices
• Passivity
• Alternative Matrix Characterizations
Post Processed S-Matrices
HFSS automatically computes the generalized S-matrix during the solve time when a project con-
tains ports. The S-matrix can be modified after solution time by applying post processing transfor-
mations. The following post processing transformations are supported by HFSS:
• Renormalized S-Matrices
• De-embedded S-Matrices
Renormalized S-Matrices
Before a structure’s generalized S-matrix can be used in a high frequency circuit simulator to com-
pute the reflection and transmission of signals, it must be normalized to the appropriate impedance.
For example, if a generalized S-matrix has been normalized to 50 ohms, it can be used to compute
reflection and transmission directly from signals that are normalized to 50 ohms.
To renormalize a generalized S-matrix to a specific impedance, HFSS first calculates a unique
impedance matrix Z, associated with the structure defined as follows:
–1
Z = Z0 ( I – S ) ( I + S ) Z0
where
• S is the n x n generalized S-matrix.
• I is an n x n identity matrix.
• Z0 is a diagonal matrix having the characteristic impedance (Z0) of each port as a diagonal
value.
The renormalized S-matrix is then calculated from the unique impedance matrix using this relation-
ship:
–1
SΩ = YΩ ( Z – ZΩ ) ( Z + ZΩ ) ZΩ
where
• Z is the structure’s unique impedance matrix.
• ZΩ and YΩ are diagonal matrices with the desired impedance and admittance as diagonal val-
ues. For example, if the matrix is being renormalized to 50 ohms, then ZΩ would have diago-
nal values of 50.
Visualize the generalized S-matrix as an S-matrix that has been renormalized to the characteristic
impedances of the structure. Therefore, if a diagonal matrix containing the characteristic imped-
ances of the structure is used as ZΩ in the above equation, the result would be the generalized S-
matrix again.
HFSS needs to calculate the characteristic impedance of each port in order to compute a renormal-
ized S-matrix.
The S-matrices initially calculated by HFSS are generalized S-matrices that have been normalized
to the impedances of each port; however, you can compute S-matrices that are normalized to spe-
cific impedances, such as 50 ohms.
To convert a generalized modal S-matrix to a renormalized modal S-matrix, HFSS first needs to
compute the characteristic impedance at each port. There are several ways to compute characteris-
tic impedance. Two methods — the Zpv and Zvi methods — require an impedance, or integration,
line.
HFSS will always calculate Zpi impedance, the impedance calculation using power and current,
which are well-defined for a port because they are computed over the area of the port. Zpv and Zvi
are not calculated by default. This is because v is computed by integrating along a user-defined
integration line. If Zpi is very small (less than 10^-14) HFSS uses Zpv (if it is non-zero). In this
case, a warning says that the design has too few conductors touching the lumped port. To renormal-
ize the solution to a Zpv or Zvi characteristic impedance, you must define an integration line.
De-embedded S-Matrices
If a uniform length of transmission line is added to (or removed from) a port, the S-matrix of the
modified structure can be calculated using the following relationship S' = γl S γl ,
e e
where
• γl is a diagonal matrix with the following entries:
e
γ1 l1
e 0 0
γ2 l2
0 e 0
γ3 l3
0 0 e
• γ =α + jβ is the complex propagation constant, where:
• α is the attenuation constant of the wave.
• β is the propagation constant of the uniform transmission line at port i.
• lι is the length of the uniform transmission line that has been added to or removed from the
structure at port i. A positive value indicates that a length of transmission line has been
removed from the structure.
The value of γ for each port is automatically calculated by HFSS.
Related Topics
De-embedding S-Matrices
Alternative Matrix Characterizations
–1
Z = Z0 ( I – S ) ( I + S ) Z0
where
• S is the n x n generalized S-matrix.
• I is an n x n identity matrix.
17-54 Technical Notes
HFSS Online Help
• Z0 is a diagonal matrix having the characteristic impedance (Z0 ) of each port as a diagonal
value.
Under the Matrix Data tab of the Display Items Dialog, the Z-matrix can be displayed as magni-
tude/ phase, real/ imaginary, magnitude, phase, real, or imaginary.
Calculating the Y-Matrix
The admittance matrix, Y, is simply the inverse of the impedance matrix, Z.
Under the Matrix Data tab of the Solution Data dialog box, the Y-matrix can be displayed as mag-
nitude/ phase, real/ imaginary, magnitude, phase, real, or imaginary.
Passivity
Passive devices can only dissipate or temporarily store energy, but never generate it. The math-
ematical definition of passivity is based upon the following condition:
Q = I - conjugate(transpose(S)) * S must be a positive semidefinite matrix.
where:
• S is the S-parameter matrix
• I is an identity matrix.
A positive semidefinite matrix has only non-negative eigenvalues. The passivity test computes
the eigenvalues of the matrix Q above at each frequency in the sweep. If any of the eigenvalues
is negative, and larger (in magnitude) than the specified passivity tolerance, then a violation of
passivity is reported to the user. The default value for passivity tolerance is .0001 tolerance
above 1.0 magnitude.
Radiated Fields
When HFSS calculates radiation fields, the values of the fields over the radiation surface are used
to compute the fields in the space surrounding the device. This space is typically split into two
regions — the near-field region and the far-field region. The near-field region is the region closest
to the source. In general, the electric field E(x,y,z) external to the region bounded by a closed sur-
face may be written as
E ( x, y, z ) =
∫ ( 〈 jωμ0Htan〉 G + 〈 Etan × ∇G〉 + 〈 Enormal ∇G〉 )ds (1)
s
where
• s represents the radiation boundary surfaces.
• j is the imaginary unit, –1 .
• ω is the angular frequency, 2πf.
• μ0 is the relative permeability of the free space, 4π×10-7 Wb/Am.
• Htan is the component of the magnetic field that is tangential to the surface.
• Enormal is the component of the electric field that is normal to the surface.
• Etan is the component of the electric field that is tangential to the surface.
• G is the free space Green’s function, given by
– jk 0 r – r ′ μr εr
e
G = ------------------------------------- (2)
r – r′
where
• k 0 is the free space wave number, ω μ0 ε0 = ω ⁄ c
• r and r ′ represent field points and source points on the surface, respectively.
• ε0 is the permittivity of free space, 1/(c2μ0)
• εr is the relative permittivity of a dielectric.
• μr is the relative permeability of a dielectric.
This r dependence is characteristic of a spherical wave, a key feature of far fields. The far field is a
spherical TEM wave with the following equation:
E = η 0 H × r̂ (3)
When calculating the near fields, HFSS uses the general expressions given in (eq. 1). You must
specify the radial coordinate r. Because it can be used to compute fields at an arbitrary radius from
the radiating structure, this command can be useful in EMC applications.
Note If HFSS calculates the near fields in a problem containing an incident wave, the radius at
which the fields are calculated is very important. If the radius is within the solution
region, then the fields calculated are either the total fields or the scattered fields
depending upon which is selected. If the radius is outside the solution region, then the
fields calculated are only the scattered fields.
When calculating the far fields, the previously discussed far-field approximations are used, and the
result is valid only for field points in the far-field region.
Warning A radiation or PML boundary or Floquet port must have been defined in the design
for HFSS to calculate radiated fields.
Related Topics
Assigning Boundaries
Assigning Excitations
Spherical Cross-Sections
Maximum Near Field Data
Selecting a Far Field Quantity to Plot
Spherical Cross-Sections
When you set up a spherical surface over which to analyze near or far fields, you specify a range
and step size for phi and theta. These indicate the spherical direction in which you want to evaluate
the radiated fields. For every value of phi there is a corresponding range of values for theta, and
vice versa. This creates a spherical grid. Each grid point indicates a unique direction along a line
that extends from the center of the sphere through the grid point. The radiated field is evaluated in
this direction. The number of grid points is determined by the step size for phi and theta.
The sphere can be defined according to any defined coordinate system and before or after a solution
has been generated.
Note For parts of the sphere outside of the model region, near-field approximation is
calculated. However, if parts of the sphere are inside the model region, the model fields
are used to compute interpolated values. A section of the sphere is considered to overlap
the model if it lies in the enlarged model region after accounting for symmetry planes.
φ
x y
When HFSS evaluates the radiated fields, it needs at least two directions along which to plot the
fields. Therefore, if the step size for phi is zero, then the step size for theta must be greater than
zero, and vice versa. This ensures that the fields are plotted in at least two directions.
When setting up the sphere, phi and theta angles must be specified between -360 degrees (deg) and
360 degrees (deg), or the equivalents in radians (rad). If deg nor rad is specified, HFSS assumes
the value to be in degrees.
Following are additional guidelines for specifying Phi in the Near Field Radiation Sphere Setup
window or the Far Field Radiation Sphere Setup window:
Start The point where the rotation of phi begins. The Start value must be equal to or
greater than one.
Stop The point where the rotation of phi ends. The Stop value must be greater than the
Start value and less than 360. If the Stop value is equal to the Start value, then
HFSS assumes that only one angle should be used and the Step Size value will be
ignored.
Step Size The number of degrees or radians (spherical grid points) between the sweep of phi.
For example, to divide a sweep from 0° to 180° into 10° increments, you would
enter 10. Entering zero for the Step Size causes the sweep to consist of one point,
the start value. If the Step Size value is zero, then HFSS assumes that only one
angle should be used.
Related Topics
Setting up a Far-Field Infinite Sphere
Setting up a Near-Field Sphere
Maximum Near-Field Data
The parameters listed in the Max Field Data window remain the same regardless of the geometry
over which they were calculated. However, the coordinates displayed change depending on the
geometry.
On a sphere, the coordinates — phi and theta — of the maximum value are listed under Phi and
Theta. The values are given in volts per meter. Along a line, the coordinates — x, y, and z — of the
maximum values are listed under X, Y, and Z. The values are given in volts per meter, and the coor-
dinates are given in meters.
The following parameters are listed:
Total The maximum of the total E-field.
X The maximum E-field in the x-direction.
Y The maximum E-field in the y-direction.
Z The maximum E-field in the z-direction.
Phi The maximum E-field in the φ-direction.
Theta The maximum E-field in the θ-direction.
LHCP The maximum left-hand circularly polarized component, which is equal to
1-
------ ( E θ – jE φ ) .
2
Array Factors
HFSS enables you to compute antenna array radiation patterns and antenna parameters for designs
that have analyzed a single array element. You can define array geometry and excitation. HFSS
models the array radiation pattern by applying an "array factor" to the single element’s pattern.
Two array geometry types are supported. The "regular uniform array" geometry defines a finite 2D
array of uniformly spaced, equal-amplitude elements. This is a natural specification after analyzing
a single-unit cell of an infinite array. The regular array type may be scanned to a user-specified
direction. Scan direction can be specified in terms of spherical coordinate angles in the radiation
coordinate system. The regular array geometry type also allows scan specification in terms of dif-
ferential phase shifts between elements.
The "custom array" geometry allows for greater flexibility. It defines an arbitrary array of identical
elements distributed in 3D space with individual user-specified complex weights.
The complex weights Wn in (eq. 2) may be written in terms of a (real) voltage amplitude An and
(real) phase ψ n as:
j ψ n.
Wn = An e (3)
To scan a regular array in the direction (φ0, θ0), the element phases ψ n are set to
ψ n = – k r n ⋅ rˆo (4)
where
(5)
jk r n ⋅ ( r̂ – rˆ0 )
N
AF ( φ, θ ) = ∑ e . (6)
n=1
For a "regular" uniform array with element spacing defined by lattice vectors u and v, the element
position vectors rn may be written in the doubly-indexed form
r mn = ( m – 1 ) u + ( n – 1 ) v (7)
with m = 1, 2, ..., Nu and n = 1, 2, ...., Nv. The total number of elements in the array is given by
N = NuNv.
The array factor (eq. 6) for the Nu x Nv array becomes
Nu Nv
jk r mn ⋅ ( r̂ – rˆ0 )
AF ( φ, θ ) = ∑ ∑ e . (8)
= 1 n = Uniform
Scan Specification formRegular 1 Arrays
The scanning phase (eq. 4) is written in terms of the scan direction r̂ 0 . Alternatively, for a reg-
ular uniform array, the scanning phase may be written in terms of the differential phase shift
between elements.
To develop this alternate scanning phase description, (eq. 7) is used to rewrite the expression
(eq. 4) in doubly-indexed form as follows:
ψ mn = – k r mn ⋅ rˆ0 = – k ( m – 1 ) u ⋅ rˆ0 – k ( n – 1 ) v .⋅ rˆ0 (9)
(Let us define ψu as the differential phase between adjacent elements in the u direction. Simi-
larly, let us define ψv as the differential phase between adjacent elements in the v direction.
Then
ψ u ≡ ψ m + 1, n – ψ m, n = – k u ⋅ rˆ0 (10)
and
ψ v ≡ ψ m, n + 1 – ψ m, n = – k v ⋅ rˆ0. (11)
Thus in the case of a regular uniform array, the angle pair (ψu, ψv) may act as a
substitute scan definition for the more general (φ0, θ0).
Custom Arrays
Once you have imported the array factor information from a text file, HFSS uses (eq. 8) to compute
the array factor. When a custom array is defined, no scan direction is set and the array factor phase
weights are those specified on an element-by-element basis in the geometry file.
The text file must have the following format. Coordinate values are assumed to be model units, and
phase and amplitude are in SI units (radians and volts respectively):
N
0 0 0 64.04mV 0
10cm 0 0 184.97mv 30deg
20 0 0 394.87mv 60deg
0 10 0 696.36mv 0
10 10 0 1.066 30deg
20 10 0 1.459 60deg
0 20 0 1.808 0
10 20 0 2.051 30deg
20 20 0 64.04mv 60deg
The information will appear as follows in the Custom Array Definition window:
Power Normalizations
When the array factor feature is in use, the power normalization used to compute realized gain,
gain, and directivity are modified as follows.
Let P inc acc rad
element , P element , and P element denote the incident, accepted, and radiated power
of the single array element. When the array factor feature is invoked for an array of N elements, the
array incident power, array accepted power, and the array radiated power will be computed simply
as the sums of the corresponding element powers. Symbolically
⎛ N ⎞
= ⎜⎜ ∑ A n ⎟ P inc
inc 2
Parray ⎟ element
⎝n = 1 ⎠
⎛ N ⎞
= ⎜ ∑ An ⎟ P acc
acc 2
P array
⎜ ⎟ element
⎝n = 1 ⎠
⎛ N ⎞
= ⎜ ∑ An ⎟ P rad
rad 2
P array
⎜ ⎟ element
⎝n = 1 ⎠
Here An as defined in equation (3) is the real amplitude weight applied to element n.
Caution: The above array power formulas are applicable when a unit cell of an infinite array has
been analyzed using linked boundary condition to take into account mutual coupling from adjacent
elements. For array elements that have been analyzed in isolation, only the incident power formula
is rigorous, and the accepted and radiated power normalizations are generally not accurate.
Antenna Parameters
Generally, when dealing with radiated fields, you are also interested in the antenna properties of the
radiated bodies. HFSS calculates the following antenna properties:
• Maximum intensity (Max U)
• Peak directivity
• Peak gain
• Peak realized gain
• Radiated power
• Accepted power
• Incident power
• Radiation efficiency
• Decay Factor
Warning A radiation or PML boundary must have been defined in the design for HFSS to
calculate radiated fields.
Related Topics
Computing Antenna Parameters
Polarization of the Electric Field
At each aspect angle in the far field of a radiating source, the electric and magnetic field vectors lie
in a fixed plane. Over time, the instantaneous electric field vector traces out a figure or shape in this
plane. This figure defines the polarization state of the field.
In general, this figure is an ellipse and is called the polarization ellipse. The wave is said to be ellip-
tically polarized when the instantaneous electric field traces out an ellipse. As a special case, the
polarization ellipse may be a circle, in which case the wave is circularly polarized. Elliptical and
circular polarization have two different states, left and right, distinguished by the sense of rotation
of the electric field vector. Some of these figures, or states, are shown below. In each case the direc-
tion of propagation is off the screen.
Circular ω
ω
ω
Elliptical
Spherical Polar
The most fundamental description of the polarization state of a radiated field is spherical polar,
which is the electric field phasor resolved in the directions of unit theta and phi vectors of the
reference coordinate system. In this description, the field may be written as E = ( E θ ,E φ ) .
The polarization ratio for a predominantly φ-polarized antenna is equal to
Eφ
------
Eθ
The polarization ratio for a predominantly θ-polarized antenna is equal to
Eθ
------
Eφ
Ludwig-3 Polarization
Arthur C. Ludwig wrote a classic paper [Ref. 1]on the definition of cross polarization. In par-
ticular, his third definition is often used since it describes the field components that are typi-
cally measured on a far-field antenna test range. Using his definition, the radiated field may be
written as E = En, Ey where
E x = E θ cos φ – E φ sin φ
E y = E θ sin φ + E φ cos φ
and phi is the usual azimuthal angle in the reference spherical coordinate system.
[1] Arthur C. Ludwig, The Definition of Cross Polarization, IEEE Transactions on Antennas and Prop-
agation, vol. AP-21 num. 1, pp. 116 -119, Jan. 1973.
Circular Polarization
For antennas designed to receive or transmit circularly polarized fields, a meaningful descrip-
tion is in terms of pure left and right circular states. In this description, the field may be written
as E = ER, EL where
1
E R = ------- ( E θ + jE φ )
2
1 ·
E L = ------- ( E θ – j E φ ) .
2
Axial Ratio
Axial ratio is defined as the ratio of the major to the minor axis of the polarization ellipse.
1. Ex and Ey are orthogonal complex-valued field components. If either is zero, HFSS treats the
field as linearly polarized. However, if neither Ex and Ey is zero:
2. Compute circular components E- and E+ from:
E- = Ex - jEy
E+ = Ex + jEy
3. If E+ = 0 or E- = 0 HFSS understands the field as perfectly circular, the axial ratio is 1. Other-
wise, for the elliptical polarization case, HFSS determines the tilt angle τ from:
phase(E-/E+) = 2τ
4. Rotate the original data to coincide with the axes of the polarization ellipse.
E' x = E x cos τ – E y sin τ
field vectors into which the given field vector has been resolved." [Ref. 2] HFSS computes the fol-
lowing six polarization ratios at each selected aspect angle:
E
Circular ⁄ LHCP = -----L-
ER
E
Circular ⁄ RHCP = -----R-
EL
E
Spherical ⁄ Phi = -----φ-
Eθ
E
Spherical ⁄ Theta = -----θ-
Eφ
E
Ludwig 3 ⁄ X = -----x
Ey
E
Ludwig 3 ⁄ Y = -----y
Ex
[2] IEEE Standard Definitions of Terms for Antennas, IEEE Transactions on Antennas and Propaga-
tion, vol. AP-31 num. 6, Nov. 1983.
Max U
The radiation intensity, U, is the power radiated from an antenna per unit solid angle. HFSS calcu-
lates the radiation intensity in the direction in which it has the maximum value. The maximum
intensity of the radiation is measured in watts per steradian and is calculated by
2
1--- ---------
E 2
U (θ,φ) = -r
2 η0
where
• U (θ,φ) is the radiation intensity in watts per steradian.
• |E | is the magnitude of the E-field.
• η0 is the intrinsic impedance of free space — 376.7 ohms.
• r is the distance from the antenna, in meters.
Related Topics
Computing Antenna Parameters
Peak Directivity
Directivity is defined as the ratio of an antenna’s radiation intensity in a given direction to the radi-
ation intensity averaged over all directions. Peak directivity, in turn, is the maximum directivity
over all the user-specified directions of the far-field infinite sphere.
Directivity is a dimensionless quantity represented by
4π U
directivity = -----------
P rad
where
• U is the radiation intensity in watts per steradian in the direction specified.
• Prad is the radiated power in watts.
Note The peak directivity displayed in the Antenna Parameters window is the directivity in
the direction of maximum radiation intensity, Umax.
• For a lossless antenna, the directivity will be equal to the gain. However, if the antenna has
inherent losses, the directivity is related to the gain by the radiation efficiency of the antenna.
Related Topics
Setting up a Far-Field Infinite Sphere
Computing Antenna Parameters
Peak Gain
Gain is four pi times the ratio of an antenna’s radiation intensity in a given direction to the total
power accepted by the antenna. Peak gain, in turn, is the maximum gain over all the user-specified
directions of the far-field infinite sphere.
The following equation is used to calculate gain in HFSS:
U
gain = 4π ----------
P acc
where
• U is the radiation intensity in watts per steradian in the direction specified.
• Pacc is the accepted power in watts entering the antenna.
Gain can be confused with directivity, since they are equivalent for lossless antennas. Gain is
related to directivity by the radiation efficiency of the antenna. If the radiation efficiency is 100%,
they are equal.
Note Because the gain is calculated from the input signal at the port, a port must be defined for
this quantity to be displayed.
Related Topics
Setting up a Far-Field Infinite Sphere
Note Because the gain is calculated from the input signal at the port, a port must be defined for
this quantity to be displayed.
Related Topics
Setting up a Far-Field Infinite Sphere
Computing Antenna Parameters
Radiated Power
Radiated power is the amount of time-averaged power (in watts) exiting a radiating antenna struc-
ture through a radiation boundary.
For a general radiating structure in HFSS, radiated power is computed as
P rad = ℜ ∫ E × H∗ ⋅ ds
s
where
• Prad is the radiated power in watts.
• ℜ is the real part of a complex number.
• s represents the radiation boundary surfaces.
• E is the electric field.
• H* is the conjugate of the magnetic field.
• ds is the local radiation-boundary unit normal directed out of the 3D model.
Note The accuracy of the computed radiated power depends on the accuracy of E and H. In
some cases it is possible that the computed radiated power may deviate slightly from the
actual radiated power.
The accuracy of the computed radiated power depends on the accuracy of E and H on the absorbing
boundary. In some cases it is possible that the computed radiated power may deviate slightly from
the actual radiated power. To increase the accuracy of the radiated power, seed the mesh on the
absorbing boundary.
Related Topics
Computing Antenna Parameters
Accepted Power
The accepted power is the time-averaged power (in watts) entering a radiating antenna structure
through one or more ports.
Fundamentally in HFSS, accepted power is computed as
P acc = Re ∫ E × H∗ ⋅ dS
A
where
• Pacc is the accepted power in watts.
• Re is the real part of a complex number.
• A is the union of all port boundaries in the model, including Wave and Lumped Ports, but
excluding Floquet ports.
• E is the electric field.
• H* is the conjugate of the magnetic field.
• dS is the local port-boundary unit normal directed into the 3D HFSS model.
Example: Consider the simple case of a single port antenna modeled in a modal project. Then the
general expression for accepted power reduces to
2 2
P acc = a ( 1 – s 11 )
where
• |a | is the complex modal excitation specified in the Edit Sources window.
• s11 is the single-entry generalized scattering matrix.
Note Because the accepted power is calculated from the input signal at the port, a port must be
defined for this quantity to be displayed.
Thus when |s11| approaches 1 (total reflection), Pacc approaches zero. When |s11| approaches 0
(perfect match), Pacc = |a |2, the total power carried by the incident mode.
In the multiport case the physical interpretation of accepted power can sometimes be confusing. By
the fundamental definition, energy that leaves the antenna structure through a port reduces accepted
power. This, in a multiport antenna, energy cross coupled from an excited port to a different port
reduces accepted power.Therefore in such cases, even if an excited port is well-matched, Pacc may
be small.
In the Edit Sources window of a terminal project, you specify total voltage V instead of model inci-
dent power. Using the underlying model S-matrix, HFSS converts the terminal excitation to total
fields at the ports, and then applies the general definition.
Related Topics
Computing Antenna Parameters
Incident Power
Incident power for an antenna structure is defined in terms of accepted power under special condi-
tions. In HFSS the incident power flow on a transmission structure is defined as the accepted power
when that structure is terminated in a conjugate-matched load. Thus we write a general definition:
P inc = P acc
conjugate match
For a transmission structure that may be modeled with a real characteristic impedance, this defini-
tion is equivalent to the zero-reflective case where the transmission structure is terminated in a
matched load. For example, in the simple example discussed in this section on accepted power, set-
ting S11 = 0 produced the incident power as:
2
P inc = P acc = a
S 11 = 0
However, there is an important difference in the case of Lumped ports with complex impedance,
and Wave ports renormalized to complex impedance. In these cases, the conjugate-match and zero-
reflection definitions of incident power give different results, but only the conjugate-match defini-
tion used by HFSS enforces the important property that Pacc<Pinc.
In the Edit Sources window of a terminal project, you specify total voltage V instead of the modal
incident power. Using the underlying modal S-matrix, HFSS converts the terminal excitation to
total fields at the ports, and then applies the general definition. As a result of this procedure, the
incident power in a terminal project depends on both the user-specified stimulation as well as the
model itself.
Related Topics
Computing Antenna Parameters
Radiation Efficiency
The radiation efficiency is the ratio of the radiated power to the accepted power given by
P rad
e = ----------
P acc
where
• Prad is the radiated power in watts.
Note Because the radiation efficiency is calculated from the accepted power, a port must be
defined for radiation efficiency to be displayed.
Related Topics
Computing Antenna Parameters
Decay Factor
When Global Environment Material is lossy, strictly speaking, the far field is zero, since the
Green’s function is:
1 – kr 1 – ( α + jβ )r
g = --- e = --- e
r r
where
k = jωμ ( σ + jωε ) = α + jβ
Against that fact, HFSS calculates the far field using the imaginary part of vector k.
You can then modify the magnitude of the field pattern by using the real part (α) of the propagation
constant, which is displayed as “Decay Factor)
1 sh ( 2 v ) + sin ( 2 v )
R = ------ ------------------------------------------- (2)
σδ ch ( 2 v ) – cos ( 2 v )
1 sh ( 2 v ) – sin ( 2 v )
X = ------ ------------------------------------------- (3)
σδ ch ( 2 v ) – cos ( 2 v )
where
δ = 2
----------- (4)
ωμσ
h
v = --- (5)
δ
where h is the layer thickness.
Similar skin impedance is assigned to surfaces of 3D objects of good conductors, which are of
NoSolveInside and Thickness for DC Resistance is set.
– γz γz
Et = ∑ an en(x, y) e + ∑ b n e n(x, y) e (1)
n n
– γz γz
Ht = ∑ an hn(x, y) e – ∑ b n h n(x, y) e (2)
n n
Here the an and bn are the intensities of the forward and backward traveling modal waves e n and
h n are the transverse electric and magnetic field patterns. Note that the an and bn are considered to
be dimensionless quantities here, while e n and h n have the normal units for electric and magnetic
fields. For this discussion’s purpose, assume that each port is defined at z = 0; this permits the
removal of exponential terms in the above equations.
Terminal Voltages and Currents
It is possible to define a set of voltages for a port by establishing a number of different integration
paths across the port. If a port supports N quasi-TEM modes of propagation, one can set up N dif-
ferent open contours of integration, C1, C2, ... CN, and define N different voltages, v1, v2, ... vN,
according to the integral formulas
Alternatively, you can define a set of currents {ik}using a set of closed contours of integration {Dk}:
v k = – ∫ E t ⋅ dl. (3)
C
k
ik =
°∫ Ht ⋅ dl. (4)
D
k
These closed contour paths are set when you define the terminals on a port.Ansoft HFSS does not
require you to set up the voltage integration paths separately. The software automatically infers the
voltage paths from the chosen current contours using a power conservation relationship.
Each definition produces a set of relationships between the modal intensities and the voltages or
currents. Since the total transverse fields can be expanded as a linear combination of modes, we can
rewrite the previous equations as
t kn = – ∫ e n(x, y) ⋅ dl (7)
C
k
Since there are N possible voltage ndefinitions andn N quasi-TEM modes, there are NxN matrices
that relate the terminal voltages and currents to the following modal intensities:
[ i k ] = [ u kn ] ( [ a n ] – [ b n ] ) (11)
[ v k ] = [ t kn ] ( [ a n ] + [ b n ] ) (12)
Now introduce the matrices T = [tkn] and U = [ukn] to represent these transformations. Note that the
units of T are volts, while the units of U are amperes.
In summary, the 3D Post Processor could be used to load different modal field patterns and manu-
ally perform the integrals defined previously over each terminal contour line. This would be a
tedious and error-prone process, which HFSS’s modes-to-terminals conversion feature eliminates.
Related Topics
Terminal Based Models for Circuit Analysis
Terminal Characteristic Impedance Matrix
Differential Pairs
Calculating the W-Elements
W-elements are a distributed model for transmission lines used in certain HSPICE-compatible cir-
cuit simulators. The W-element models in HFSS are computed from the 2D port solutions.
Z = R + jωL = γ * Z0 (1)
Extensions to the multi conductor case are possible but are beyond the scope of this discussion.
There are two flavors of W-element export in HFSS: Tabular and RLGC. (You see them in the
Equivalent Circuit Export Options panel.) The more basic "RLGC" format fits the computed RLGC
data to the model equations repeated below. For RLGC format RG parameters are frequency depen-
dent such that HSPICE computes them as
R(f) = Ro + Rs * sqrt(f) (3)
G(f) = Go + Gd * f (4)
where Ro is the low frequency resistance and Go is the low frequency conductance. Rs and Gd rep-
resent the high-frequency asymptotes due to skin effect and loss tangent, respectively. L and C are
assumed to be fixed over the frequency band.
Thus the "RLGC" format uses four matrices (Ro, Rs, Go, Gd) to model frequency dependence for
R(f) and G(f), and it neglects the frequency dependence of L and C.
In contrast the "Tabular" format is not fitting the data to this simplified model: it is printing out the
actual RLGC values at each frequency as computed by HFSS from the port solution.
Under some conditions, during W-Element export, HFSS may issue a warning that “One or more of
the diagonal terms in the W-element <designated> matrix for some frequency are negative for a
<specified port>.”
Technical Notes 17-79
HFSS Online Help
This signifies a non-physical result. A negative diagonal entry in the RLGC matrices indicates that
the model is non-passive at that frequency (i.e. can produce energy, which is probably not realistic
for a metal interconnect.)
This can be caused by a number of things:
• Interpolating sweeps.
• Non-causal dielectric material models, such as the traditional constant loss tangent, constant
permittivity dielectric model. The Djordjevic or Debye models in HFSS would be the preferred
ones to use here.
• Allowing radiation boundaries on the ports.
• Solving to a very low frequency (one so low that the field solution from the full-wave solver
contains significant numerical errors.)
It is also possible to convert the terminal-based admittance and impedance matrices into a terminal-
based “pseudo-S-matrix” Sp. To do this, a reference impedance matrix must be specified. Then
standard formulas are used to convert the terminal impedance matrix Z into the terminal S-matrix
1⁄2 –1 –1 ⁄ 2
S p = Z ref ( Z + Z ref ) ( Z – Z ref ) Z ref
Zref can be either a user defined diagonal reference impedance matrix or the terminal characteristic
impedance matrix, Zo, which is the matched case for terminal-based models.
The terminal S-matrix Sp relates the intensities of the incident and reflected pseudo-waves at the
terminals.
β = Sp α
These pseudo-waves are defined by:
1 –1 ⁄ 2
α = --- Z ref ( v + Z ref i )
2
1 –1 ⁄ 2
β = --- Z ref ( v – Z ref i )
2
Note that the units of α and β are watts1/2. The terminal voltages and currents can also be written
in terms of the pseudo-waves.
1⁄2
v = Z (α + β)
–1 ⁄ 2
i = Z (α – β)
Unlike true waveguide modes, the pseudo-waves α and β have no associated propagation constant.
The pseudo-waves represent linear combinations of several modes, which may all have differing
propagation constants. HFSS is still capable of performing de-embedding on the terminal-based S-
matrix, but this is accomplished by first de-embedding the modal S-matrix and then performing the
transformation back to a terminal-based S-matrix.
For the normalization of terminal voltages in the Fields Post Processor, see Scaling a Source’s
Magnitude and Phase.
Related Topics
Modes to Terminals Conversion
Terminal Characteristic Impedance Matrix
Differential Pairs
Terminal Characteristic Impedance Matrix
Consider the situation illustrated below. A 3D structure with one multi-mode waveguide port is
loaded by an N-port matrix impedance Z. The structure contains internal sources, which generate
outgoing waves that exit through the waveguide port and strike the impedance Z. If Z does not
match the impedance of the waveguide in some sense, a reflection will occur from this load and
will return to the 3D structure, where it is interpreted as an incident wave.
i
a +
3D structure v Z
b _
An optimal choice of Z will prevent any reflections from the load returning as an incident wave a.
Note that the circuit equations at the load are v = -Zi (the minus sign is due to the sense of the cur-
rent i). By replacing the voltages and currents with their modal expansions, the voltage becomes
v = T ( a + b ) = – ZU ( a – b ) .
Rearranging this to isolate a and b, it is determined that:
( T + ZU ) a + ( T – ZU ) b = 0
Now notice that if we select T = ZU ; the incident wave a vanishes. Corresponding to this condition
is an “optimal” choice Z0 for the impedance Z:
–1
Z 0 = TU
Z0 is the terminal characteristic impedance matrix for the multi-mode waveguide port. This value
of impedance will completely absorb any linear combination of modal waves leaving the port. As
such, it should be of interest to circuit designers wishing to control reflections. In the important,
special case of a lossless waveguide, it can be shown that Z0 = TTT is a real-valued, symmetric
impedance matrix. It is then easy to synthesize a network of resistors with the specified matrix
impedance.
Related Topics
Modes to Terminals Conversion
Terminal Based Models for Circuit Analysis
Differential Pairs
Geometric Objects
Following are supplemental technical details about working with geometric objects and compli-
cated models:
• Bondwires
• Healing and Meshing
• Detecting and Addressing Model Problems to Improve Meshing
• Handling Complicated Models
Bondwires
A bondwire is a thin metal wire that connects a metal signal trace with a chip. You can choose to
draw a standard JEDEC 4-point bondwire, as shown below:
where
h1 = the height between the bond pad point and the top of the loop.
h2 = the height between the lead point and the bond pad point.
diameter = thickness of the wire.
D = the distance between the start and end points, and D/8 is the distance divided by 8.
Or you can choose to draw a JEDEC 5-point or Low bondwire, as shown below:
where
α = the angle between the horizontal plane and the wire at the bond pad point.
β = the angle between the horizontal plane and the wire at the lead point.
D = the distance between the start and end points, D/2 is the diistance divided by 2, and D/8 is the
distance divided by 8.
When drawing the bondwire, you first select the bond pad point, a point in 3D space that defines
the bond pad position in a horizontal plane. Then you select the lead point, which indicates the dis-
tance the wire covers in the horizontal plane. HFSS will use the distance between the bond pad and
lead points to calculate the height between the bond pad and the lead point, or h2, a value that you
can modify in the Bondwires dialog box.
For the JEDEC types, notice that the horizontal distance on the wire is calculated as the total length
divided by 8. (This horizontal distance is shown in the JEDEC 4 and 5-point figure as “D/8.”) For
the Low type, the horizontal distance is affected by the Alpha and Beta values as well as the length.
Related Topics
Drawing Bondwires
Healing and Meshing
Potential problems with 3D Models
This section lists problems that can prevent a 3D model from being meshed successfully. Subse-
quent sections will describe how these problems can be detected and addressed.
ACIS errors
The underlying solid modeling technology used by Ansoft’s 3D products Maxwell, HFSS and Q3D
is provided by the ACIS geometric modeler. You can create models directly in the drawing environ-
ment of these Ansoft products using primitives, such as boxes, cylinders, etc. and operations on
primitives, such as Boolean operations. In addition, you can import models produced by other CAD
tools in a variety of formats such as STEP, IGES, etc. In Ansoft’s 3D products, all models have to
be stored internally in ACIS’ native format, known as sat format. When you import models into
Ansoft products, translators are invoked that convert the models to sat format. Often, models that
were created in other CAD tools were created initially for other purposes than electromagnetic
analysis, such as for mechanical design or just for display purposes. They may have imperfections
that make them illegal to ACIS. Further, there can be compatibility issues between different ver-
sions and even flavors of modeling tools. All this can lead to errors in imported 3D models.
If you use Ansoft products to create geometry models, and thereby avoid model import and transla-
tion, you are unlikely to encounter such problems.
Mixed dimensionality
Even if a model is imported and translated without errors, there is a restriction to be aware of. ACIS
can handle mixed-dimensionality models. One of the goals of Ansoft’s use of the ACIS modeling
system is to create a valid volumetric mesh for simulation. Mixed-dimensionality models will not
yield a valid volumetric mesh. Therefore, the Ansoft tools will not mesh objects with mixed dimen-
sionality, so-called non-manifold objects. For instance, imagine a 3D object representing a curved
metal plate with a small but finite thickness. If it reaches zero thickness somewhere while having
non-zero thickness elsewhere, it has mixed dimensionality, 2D as well as 3D. You will get an error
message saying that the object is non manifold. Of course, 2D and 3D objects can co-exist in a
model, but any one object cannot be both 2D and 3D.
Intersecting objects
Another restriction is that Ansoft 3D tools don’t allow partial intersections (also known as partial
overlaps) between 3D objects. Each element of the mesh has to belong unambiguously to one
object. There is no problem if one object is enclosed completely inside a bigger object, but partial
intersections lead to ambiguities. As long as there are partial object intersections, the mesh genera-
tor will not attempt to create a mesh. Instead, you will get an error message notifying you which
objects are intersecting.
After you run a validation check, you can right-click on an intersection error message in the Mes-
sage window, and select Go to reference from the shortcut menu. This selects the intersecting
objects.
You must remove the intersections before you can proceed. You can do this by changing the shapes
of objects slightly, or by subtracting one object from the other.
Caveat: if as a result of a subtraction the model has pairs of true surfaces that are coincident, that
is, smooth curved surfaces that fit exactly one inside the other, you make it harder for the mesh gen-
erator to create a mesh. This is because ACIS will create segmentations on each of these surfaces,
and these segmentations are not guaranteed to fit. Setting a small value for Surface Deviation
under Mesh Operations >Assign>Surface Approximation increases your chance of success in
such a case, but it is better to avoid such situations if you can.
Small features and misalignment
When there are no ACIS errors in the model, no non-manifold objects and no partial object inter-
sections, the mesh generator can be invoked to create a valid mesh for the electromagnetic analysis.
Even if the geometry is valid, mesh generation can still fail. Possible causes are the presence of
very short edges, very small faces, long and thin sliver faces, and slight misalignments between
faces that are supposed to be coincident.
Related Topics
Technical Notes: Detecting and Addressing Model Problems to Improve Meshing
Manual healing adds tolerant stitching, geometry simplification (such as small-feature removal)
and tight en gaps settings to this. You can remove small features at this stage if you wish. However,
the usual approach is to apply auto-healing at this stage and leave small-feature removal until later.
At any time after import, you can perform a Validation Check: HFSS>Validation Check. This will
enable you to focus on bodies and body pairs that need attention before a mesh can be created. Note
that you can set the Modeler Validation settings for Warning Only, Basic, and Strong.
1. Select the objects that have ACIS errors, such as failing api_check_entity(), and the objects
that have non-manifold features, i.e. mixed dimensionality.
2. Invoke Modeler->Model Analysis->Analyze Objects.
This will bring up an Analysis Options dialog where you set the strictness of the entity check,
detection and thresholds for holes, chamfers and blends, thresholds for small feature detection.
1. Good
2. Null Body
3. Analysis not performed
4. Invalid entities found
5. Small-entity errors
Invalid-entity errors are ACIS errors and non-manifold errors. Small-entity errors are small faces,
sliver faces and small edges that are optionally detected based on user-defined parameters.
3. If errors still persist, choose "offending" faces and edges and click on Delete.
This will replace the selected face/edge entity by a tolerant edge/vertex respectively.
In order to avoid unintended changes, it is good practice to do the following:
1. At the bottom of the Model Analysis window, check the box "Auto Zoom to Selection."
2. Select one face or edge at a time
3. Decide for each face and edge whether you want to delete it.
Note Healing causes changes to the geometry and topology of the body being healed.
Validation check has to be re-run after healing is done to identify body pairs that
intersect. It is possible that after healing, bodies that were disjoint before now overlap.
In some cases the replacement of the face/edge by tolerant edge/vertex will fail. If the object
remains invalid, you know at this point what parts of the object are invalid. You will need to change
that part of the object manually, either in Ansoft’s drawing environment or in the original CAD
tool, to make it pass. Often, the invalid entities are in small details that can be changed without
noticeably affecting the results of the electromagnetic analysis. For example, it may be possible to
create a small object, well placed in the "offending" region, and to unite it with or subtract it from
the problematic object, such that the "offending" details don’t exist anymore.
Three: Removing Object Intersections
If there are any intersecting objects, a Validation Check will list them. You must eliminate object
intersections before a mesh can be created. After you run a validation check, you can right-click on
an intersection error message in the Message window, and select Go to reference from the shortcut
menu. This selects the intersecting objects.
In complicated models, before making changes, it is good practice to inspect the overlap visually. A
way to do this is to:
1. Duplicate both objects and place the copies outside the model.
2. Perform Boolean Intersect on the copies.
This will show you what causes the intersection and will help you decide how to remove it.
3. Then, delete the copies.
The easiest way to eliminate object overlap is to subtract one object from the other, in the order that
leaves the desired material in the region of overlap. If the overlap is very small and you can choose
the order of subtraction, choose one that does not create coincident true surfaces, if possible.
Caveat: if as a result of a subtraction the model has pairs of true surfaces that are coincident, that is,
smooth curved surfaces that fit exactly one inside the other, you will make it harder for the mesh
generator to create a mesh. This is because ACIS will create segmentations on each of these sur-
faces, and these segmentations are not guaranteed to fit. Setting a small value for Surface Devia-
tion under Mesh Operations>Assign>Surface Approximation increases your chance of success
in such a case, but it’s better to avoid such situations if you can.
A way to eliminate object intersections without subtraction is to split one object in parts, in such a
way that some parts are completely enclosed in the other object, and some parts are completely out-
side the other object. Even for complicated objects, this is possible through a sequence of Boolean
operations on the objects and copies of the objects.
At this point, the geometry has no ACIS errors, no non-manifold objects and no partial object inter-
sections. A mesh can be created for the electromagnetic analysis.
The procedure for fixing face improper intersections is similar. When it occurs, the error report lists
a pair of faces intersecting.
1. You can detach those faces (using Modeler>Surface>Detach Faces), and others if necessary.
2. Select the faces and invoke either the Modeler>Model Healing>Stitch Sheets command (see
Stitch Sheets) or Modeler>Boolean>Unite (see Uniting Objects).
3. Once the imporper intersections have been corrected, you can stitch the set of faces back to the
original model.
Four: Removing Small Features
Even though, in principle, the geometry may be ready for a mesh to be created, it is possible that
small features in the geometry lead to a mesh that is unnecessarily large and contains long and thin
tetrahedra that make the simulation converge slower. Small features may even cause the mesh gen-
eration to fail. By small, we mean details on an object that are thousands of times smaller than the
main features of the object, and that, in most cases, are unintended consequences of the drawing
history in another CAD tool. Therefore, it is advantageous to remove small features.
You may have noticed that you could have invoked small-feature removal at several earlier stages.
There is no objection to doing it earlier. See Object Overlap Settings for Complicated Models. The
reason why it is presented here as stage four is that the previous stages were necessary while this
one is optional.
To start the small-feature removal:
1. Click HFSS>Modeler>Analysis Options and specify the Entity Check level, make selections
for holes, chamfers, and blends, their thresholds, as well as for edges, faces and slivers.
2. Select objects and invoke object analysis through Modeler>Model Analysis>Analyze
Objects.
Alternatively, without objects selected, use Modeler>Model Analysis>Show Analysis Dia-
log>Objects and select objects from the list. In the Model Analysis window, invoke Per-
form>Analyze Objects.
The software will report according to the Analysis Options settings, such as holes smaller than
a given radius, the smallest edge length and the smallest face area.
3. Upon clicking OK, the analysis is performed.
As a result of the analysis, the software presents a list of all holes, chamfers, blends, faces and
edges that don’t meet the thresholds set by you in the Analysis Options.
4. Check the box "Auto-Zoom to Selection" at the bottom of the Model Analysis window and
click on items in the list.
Inspect them visually and decide whether they can be deleted. It is good practice to delete them
one by one rather than deleting many at once in order to prevent unintended changes.
Sometimes, an edge or face cannot be deleted, and you get a message notifying you. In that
case, either ignore it, or revisit it after deleting some other details first, or revisit it later manu-
ally in the 3D drawing environment.
At this point, the geometry has no ACIS errors, no non-manifold objects and no partial object
intersections. Furthermore, there are fewer small features that were unintended or unimportant
for the electromagnetic analysis, so the quality of the model has improved.
Five: Aligning Objects
Objects that touch each other in imported geometries don’t always have well-aligned faces. Often,
this is a consequence of the limited level of precision in the imported file. Misaligned faces can
cause tiny object intersections or tiny gaps between objects, which in turn can lead to an inefficient
mesh or even a failure to create the mesh.
To repair such occurrences in an automated way, you can select groups of objects and invoke Mod-
eler>Model Analysis>Analyze Interobject Misalignment. This will yield face pairs from differ-
ent bodies that are slightly misaligned with respect to each other.
In the window that shows this list, check the box "Auto-Zoom to Selection" and select face pairs
from the list. When you decide that faces should be aligned, click Align Faces. In some cases, face
alignment will fail if the topology of the body would change by a large amount after alignment. In
that case, you can decide to ignore it, as it may not be a problem, or revisit it later manually in the
Modeler environment.
Note In complicated models, the Interobject Misalignment analysis can take a long time if
you select all objects before launching the analysis. If you don’t know which pairs of
objects to analyze, just let the mesh generator try to make a mesh. If the mesh fails, a list
will be presented to you of misalignments that the mesh generator finds suspicious but
didn’t want to adjust without permission. Not every misalignment in the list is always a
problem: this is a list of features that might need your attention.
Note As face misalignments between touching objects can cause small object intersections,
this alignment capability can already serve a useful role in stage three.
Note Remember that Healing always purges the history. If you heal an object for which you
need to recover the history, use the Undo command. If you want to heal an object for
which you want to keep the history, you should make a copy of the object for that
purpose.
Boundaries
Boundary conditions specify the field behavior on the surfaces of the problem region and object
interfaces. This area of the technical notes includes information about the following boundary
types:
• Perfect E
• Impedance
• Radiation
• PML
• Finite Conductivity
• Symmetry
• Master and Slave
• Lumped RLC
• Screening Impedance
• Layered Impedance
• Infinite Ground Planes
and the following subjects:
• Frequency-Dependent Boundaries
• Default Boundary Assignments
Perfect E Boundaries
In HFSS, perfect E boundaries represent perfectly conducting surfaces in a structure.
By default, all HFSS model surfaces exposed to the background are assumed to have perfect E
boundaries; HFSS assumes that the entire structure is surrounded by perfectly conducting walls.
The electric field is assumed to be normal to these surfaces. The final field solution must match the
case in which the tangential component of the electric field goes to zero at perfect E boundaries.
The surfaces of all model objects that have been assigned perfectly conducting materials are auto-
matically assigned perfect E boundaries.
Impedance Boundaries
In HFSS, impedance boundaries represent surfaces of known impedance. The behavior of the field
at the surface and the losses generated by the currents flowing on the surface are computed using
analytical formulas; HFSS does not actually simulate any fields inside the resistor.
Similar to finite conductivity boundaries, the following condition applies at impedance boundaries:
E tan = Z s ( n̂ × H tan )
where
• n̂ is the is the unit vector that is normal to the surface.
+ x
V -
If the current density, J, is uniform over the rectangle then the equation (1)
n̂ × E = Z s n̂ × J (1)
where
• E = E on the rectangle, and
• J = J on the rectangle.
L
The circuit quantities and fields are related as follows:
V = ∫ E ⋅ dL = EL (3)
x=0
w
I = ∫ J ⋅ x̂ dy = Jw (4)
y=0
V EL
Z = --- = ------- (5)
I Jw
Substituting equation (1) into equation (5) results in the following equation:
L
Z = Z s ---- (6)
w
Thus, when L = w, the equivalent circuit impedance is equal to the impedance on one square. Hence
the units ohms per square.
If in this example L = 2w, the impedance would be equal to one-half of the circuit equivalent
impedance for the rectangle, or the circuit equivalent impedance of one "square" of the rectangle is
equal to the impedance of that square. Therefore, when entering the surface impedance for an
object, you must enter the impedance per square.
Radiation Boundaries
When solving radiating (i.e. antenna) and scattering (i.e. Radar Cross Section) structures in an
unbounded, infinite domain, HFSS truncates the problem into a bounded domain and prescribes the
appropriate truncation condition. This is generally known as the “radiation boundary condition”.
Theoretically, the radiation boundary condition should be a “transparent” condition. In other words
it should not produce any unphysical reflection as a result of the artificial truncation. HFSS offers
three types of radiation boundaries: first-order absorbing boundary condition (ABC), perfectly
matched layers (PML), and boundary integral equations (IE).
ABC and PML Boundaries
Both the ABC and PML boundaries attempt to minimize reflections by absorbing all outgoing
waves at the truncation boundary. Because of this, they can only be prescribed at convex surfaces.
This is because for concave surfaces, outgoing waves will re-enter the problem domain and should
therefore not be completely eliminated. While PMLs absorb any kind of waves including guided
waves, ABC imitates radiation to homogeneous background space.
ABCs only absorbs normal or near normal incident waves. Thus in order to produce accurate
results, it must be placed sufficiently far away from structures. The typical recommendation is at
least a quarter wavelength from the radiating source, although in some cases the radiation boundary
may be located closer than one-quarter wavelength, such as portions of the radiation boundary
where little radiated energy is expected. ABC is a local condition and thus preserving the sparse
nature of the FEM formulation.
PMLs absorb all outgoing waves by adding artificial material layers that are designed such that all
of the incident waves impinging upon them are completely transmitted with minimal reflections.
Thus PMLs can be placed closer than ABCs. Furthermore, the PML absorbs a much wider range of
waves in terms of frequency and direction whereas ABC absorbs only normally incident waves
accurately. However, PMLs in general makes it more difficult for the iterative solver to reach con-
vergence compared to ABCs. PMLs also preserves the sparse nature of the FEM formulation.
Boundary Integral Equations
The boundary integral equations (IE) is an exact transparent condition. The Sommerfeld radiation
condition at infinity as required by physics is enforced exactly through the employment of appro-
priate Green’s functions via an integral equation method. This hybridization is commonly known as
the finite element-boundary integral (FEBI) method. Unlike ABC and PML, the IE boundary can
be of arbitrary shape, both concave and convex. It can be placed very close to the structures and
17-98 Technical Notes
HFSS Online Help
produce accurate results. Since analytic Green’s functions are known only for a few specific situa-
tions, HFSS requires that the IE boundary is not allowed to touch any other boundary except an
infinite ground plane. In addition, the IE boundary does not work with symmetry planes. If the IE
boundary is placed on a true surface, HFSS requires users to turn off curvilinear elements. Further-
more, from the performance point of view, a minimum distance of 0.05 wavelengths is recom-
mended (like for PMLs). The IE condition is a non-local condition, producing a partial sparse and
partial dense system matrix. For this reason when simulating electrically large structures, the IE
condition typically requires more RAM and CPU than either ABC or PML. Thus the IE ABC will
be most effective and efficient for smaller radiating structures such as RFID antennas.
Related Topics
Assigning Radiation Boundaries
Technical Notes: PML Boundaries
PML Boundaries
Perfectly matched layers (PMLs) are fictitious materials that fully absorb the electromagnetic fields
impinging upon them. These materials are complex anisotropic.
There are two types of PML applications: free space termination and guided wave termination.
With free space termination, PMLs are associated with a surface that radiates into free space
equally in every direction. PMLs are more appropriate than radiation boundaries in this case
because PMLs enable radiation surfaces to be located closer to radiating objects, reducing the prob-
lem domain. Any homogenous isotropic material, including lossy materials like ocean water, can
surround the design.
With reflection-free termination of guided waves, the structure continues uniformly to infinity. Its
termination surface radiates in the direction in which the wave is guided. Reflection-free PMLs are
appropriate for simulating phased array antennas because the antenna radiates in a certain direction.
Related Topics
Assigning PML Boundaries
Material Tensors Applied at PML Boundaries
Tensor Entries
Boundaries at PML Surfaces
PML_XYZ
PML_XY
PML_Y
PML_X
To ensure that there will not be any reflection at the PML/air interface, the bi-axial diagonal mate-
rial tensors for x-, y- and z-directed PMLs (PML_X, PML_Y, and PML_Z) are as follows.
For PML_X:
[ε] 1 [μ] 1
------- = ---
- CC -------- = ---
- C C
ε0 C μ0 C
For PML_Y:
[ ε -]
------ 1- [ μ -]
------- 1-
= C --- C = C --- C
ε0 C μ0 C
For PML_Z:
[ ε -]
------ 1- [ μ -]
------- 1-
= C C --- = C C ---
ε0 C μ0 C
where C = a - jb.
The tensors designated as PML_X characterize an x-directed PML corresponding to a PML wall in
the yz plane. Similarly, PML_Y and PML_Z are designated tensors for y- and z-directed PMLs.
PMLs of different directions must be joined in order to construct a box with PML walls. To ensure
complete coverage where the edges and corners of two PMLs meet, create edge and corner PML
objects. The tensors of an edge object joining PML_X and PML_Y are as follows for PML_XY:
[ ε ]-
------ [-------
μ ]-
= 1 1 C2 = 1 1 C2
ε0 μ0
A similar tensor construction rule is valid for joining x- and z-directed and y- and z-directed PMLs.
The tensor for a corner object is a follows for PML_XYZ:
[ ε ]-
------ [ μ -]
-------
= CCC = CCC
ε0 μ0
Note This example in shows the material in GLOBAL coordinate system, while the Material
Manager shows the materials in LOCAL coordinate system assigned to the object, which
are then rotated to the global coordinate system by the solver.
Related Topics
Tensor Entries
Boundaries at PML Surfaces
PML Boundaries
Tensor Entries
Entering the matrices of the anisotropic materials doesn’t require a special procedure. The usual
anisotropic material definitions can be used for any PML structure. However, keep in mind that the
efficiency of the PMLs depends on the material values assigned to them.
Setting the complex parameter C ensures that the electromagnetic field decays strongly in the
PMLs. Back reflections from the bounding PECs are then kept below a prescribed bound. To
accomplish this, the following inequalities have to be satisfied:
– ln ρ
e ≥ ------------------- = e min
2 D min H
– ln d
e ≤ ------------------- = e max
2 D max h
where
1 ω min
D min = α min + β min = ---------- + -----------
r max c
1 ω max
D max = α max + β max = --------- + ------------
r min c
• e=a=b
• a and b are the real and imaginary parts of C.
• H is the thickness of the PML object.
• ωmax and ωmin are the minimum and maximum angular frequencies.
• rmax and rmin are the minimum and maximum distance of a radiating object to the PML sur-
face.
• ρ is the bound for back reflection.
• d is the maximum decay characterizing the element. (d is approximately 3* 10-3.)
• h is the thickness of one finite element.
• c is the velocity of light in vacuum.
Related Topics
Material Tensors Applied at PML Boundaries
Boundaries at PML Surfaces
PML Boundaries
Boundaries at PML Surfaces
After embedding a structure in PMLs, the next step is to specify boundaries on the outer surface of
the box. The simplest way is to bound the box either with perfect electric conductors (PECs) or per-
fect magnetic conductors (PMCs.) In general, use PECs because they reduce the problem size.
Related Topics
Tensor Entries
PML Boundaries
Boundaries at PML Surfaces
Material Tensors Applied at PML Boundaries
Finite Conductivity Boundaries
In HFSS, finite conductivity boundaries represent imperfect conductors. At such boundaries, the
following condition holds:
E tan = Z ( n̂ × H tan )
where
• Etan is the component of the E-field that is tangential to the surface.
• Htan is the component of the H-field that is tangential to the surface.
• Zs is the surface impedance of the boundary. When the thickness is much larger than the skin
depth (1 + j )/(δσ) can be used. When not, Zs can be calculated from the transmission line
model used at a layer impedance boundary condition.
• δ is the skin depth, 2 ⁄ ( ωσμ ) , of the conductor being modeled.
• ω is the frequency of the excitation wave.
• σ is the conductivity of the conductor.
• μ is the permeability of the conductor.
The fact that the E-field has a tangential component at the surface of imperfect conductors simu-
lates the case in which the surface is lossy.
The surfaces of any objects defined to be non-perfect conductors are automatically set to finite con-
ductivity boundaries. Note that HFSS does not attempt to compute the field inside these objects; the
finite conductivity boundary approximates the behavior of the field at the surfaces of the objects.
The finite conductivity boundary condition is valid only if the conductor being modeled is a good
conductor, that is, if the conductor’s thickness is much larger than the skin depth in the given fre-
quency range. If the conductor's thickness is in the range or larger than the skin depth in the given
frequency range, HFSS takes the thickness into account, if it has been defined.
Symmetry Boundaries
In HFSS, symmetry boundaries represent perfect E or perfect H planes of symmetry. Symmetry
boundaries enable you to model only part of a structure, which reduces the size or complexity of
your design, thereby shortening the solution time.
When you are defining a symmetry plane, keep the following requirements in mind:
• A plane of symmetry must be exposed to the background.
• A plane of symmetry must not cut through an object drawn in the 3D Modeler window.
• A plane of symmetry must be defined on a planar surface.
• Only three orthogonal symmetry planes can be defined in a problem.
Perfect E Vs. Perfect H Symmetry Boundaries
In general, use the following guidelines to decide which type of symmetry boundary to use, a
perfect E or a perfect H:
• If the symmetry is such that the E-field is normal to the symmetry plane, use a perfect E
symmetry plane.
• If the symmetry is such that the E-field is tangential to the symmetry plane, use a perfect H
symmetry plane.
The simple rectangular waveguide shown below illustrates the differences between the two
types of boundaries. The E-field of the dominant mode signal (TE10) is shown. The waveguide
has two planes of symmetry, one vertically through the center and one horizontally.
The horizontal plane of symmetry is a perfect E surface. The E-field is normal and the H-field
is tangential to that surface. The vertical plane of symmetry is a perfect H surface. The E-field
is tangential and H-field is normal to that surface.
Electric field of TE10 Mode
For common problems, you can usually decide which symmetry boundary to use by reviewing
the geometry. For example, if the structure is a microstrip, the flux lines of the E-field run
between the ground plane and the conductive strip; therefore, the E-field is tangential to any
vertical symmetry plane that slices a microstrip in half.
Symmetry and Port Impedance
If a symmetry plane has been defined, the computed port impedances will not match the port
impedance of the full structure unless an impedance multiplier is specified.
Note Port impedance is only calculated when a port has been defined. If you are solving a
problem without ports, you do not need to specify an impedance multiplier.
point on the slave boundary match the E-field to within a phase difference at each corresponding
point on the master boundary. They are useful for simulating devices such as infinite arrays.
Unlike symmetry boundaries, E does not have to be tangential or normal to these boundaries. The
only condition is that the fields on the two boundaries must have the same magnitude and direction
(or the same magnitude and opposite directions).
When creating matching boundaries, keep the following points in mind:
• Master and slave boundaries can only be assigned to planar surfaces. These may be the faces of
2D or 3D objects.
• The geometry of the surface on one boundary must match the geometry on the surface of the
other boundary. For example, if the master is a rectangular surface, the slave must be a rectan-
gular surface of the same size.
• If the mesh on the master boundary does not match the mesh on the slave boundary exactly, the
solution will fail. Normally HFSS automatically forces the mesh to match on each boundary;
however, in some cases, the mesh cannot be forced to match. To prevent the solution from fail-
ing, create a virtual object on the slave boundary that exactly matches any extra object on the
master boundary, or create a virtual object on the master boundary that exactly matches any
extra object on the slave boundary.
• To make a surface a master or slave boundary, you must specify a coordinate system that
defines the plane on which the selected surface exists. When HFSS attempts to match the two
boundaries, the two coordinate systems must also match each other. If they do not, HFSS will
transpose the slave boundary to match the master boundary. When doing this, the surface to
which the slave boundary is assigned is also transposed. If, after doing this, the two surfaces do
not occupy the same position relative to their combined defined coordinate system, an error
message appears.
For example, consider the following figure:
U V
V U
Slave Master
To match the coordinate system of the master boundary, the coordinate system on the slave
boundary must rotate 90 degrees counterclockwise; however, when this is done, you get the
following:
The two surfaces do not correspond and thus the mesh will not match, causing an error mes-
sage.
• The angle between the axes defined by the u point and v point must be identical for the master
and slave boundary.
Calculating the E-Field on the Slave Boundary
The E-field on the slave boundary is forced to match the E-field on the master boundary. The mag-
nitude of the E-field on both boundaries is the same; however, the fields may be out of phase with
each other.
The function relating the electric field on the slave boundary, ES, to the electric field on the master
boundary, EM, depends on the type of problem you are solving. For example, consider an infinite
array simulation for a rectangular array. If the array excited to radiate in the direction (θ, φ) in
spherical coordinates. The fields above the array experience a phase delay of
Ψ = k ( rˆo • v )
where
• r̂ 0 is the unit vector in the direction of scan.
Similar to impedance boundaries, the following condition holds at lumped RLC boundaries:
E tan = Z s ( n̂ × H tan )
where
• n̂ is the is the unit vector that is normal to the surface.
• Etan is the component of the E-field that is tangential to the surface.
• Htan is the component of the H-field that is tangential to the surface.
• Zs is the surface impedance of the boundary, Rs + jXs, where
• Rs is the resistance in ohms/square.
• Xs is the reactance in ohms/square.
Unlike impedance boundaries, you are not required to supply the impedance per square, but you
must supply the actual values for R, L, and C. HFSS then determines the impedance per square of
the lumped RLC boundary at any frequency.
A Fast frequency sweep is supported for this boundary condition.
Layered Impedance Boundaries
A layered impedance boundary is used to model multiple layers in a structure as one impedance
surface. The effect is the same as an impedance boundary condition, except that HFSS calculates
the reactance and resistance values for the surface based on data you enter for the layered structure.
Surface roughness is also taken into account.
The reactance and resistance values are calculated differently for internal and external layered
impedance boundaries. For external layered impedance boundaries, HFSS calculates the imped-
ance for the side of the surface in contact with the computational domain and assigns this value to
the boundary. For internal layered impedance boundaries, HFSS calculates the average impedance
value for the two sides of the surface in contact with the computational domain and assigns this
value to the boundary.
The layered impedance boundary is supported for single-frequency solutions and Discrete and
Interpolating frequency sweeps.
Impedance Calculation for Layered Impedance Boundary
The impedance of the layered structure is calculated by recursively calling the impedance calcula-
tion formulation known from transmission line theory:
Z inputk + 1 ch ( γ k d k ) + Z wk sh ( γ k d k )
Z inputk = Z wk ---------------------------------------------------------------------------------
Z inputk + 1 sh ( γ k d k ) + Z wk ch ( γ k d k )
where
• Z inputk is the input impedance for the kth layer.
μ 0 μ rk
Z wk = ---------------
-
ε 0 με rk
• ch is the hyperbolic cosine function.
• sh is the hyperbolic sine function.
• γ k = k 0 – ε rk μ rk
where
• γ is the propagation coefficient.
• k0 is the free space wave number, ω μ 0 ε 0 , where ω is the angular frequency, 2πf.
• εrk is the relative complex permittivity of the Kth layer.
• μrk is the relative complex permeability of the Kth layer.
where
ε rk = epsr k – j ⎛⎝ --------------- + epsr ⋅ tan de⎞⎠
sigma
•
ωε 0
• μ rk = mur k – j ( mur k ⋅ tan dm k )
s 1.6
K w = 1 + exp ⎛ – ⎛ ------⎞ ⎞
⎝ ⎝ 2 h⎠ ⎠
where, further:
• h is the surface roughness.
• s is the skin depth.
Infinite Ground Planes
To simulate the effects of an infinite ground plane, select the Infinite ground plane check box
when setting up a perfect E, finite conductivity, or impedance boundary condition. The selection
only affects the calculation of near- and far-field radiation during post processing. The 3D Post Pro-
cessor models the boundary as a finite portion of an infinite, perfectly conducting plane.
Conceptually, a boundary condition designated as an infinite ground plane divides the problem
region into the half above it, where the entire model resides, and the half below it, where the radi-
ated fields are set to zero. Antenna parameters involving radiated power will be consistent with
these properties.
Lossy ground planes may be approximated by selecting the Infinite ground plane check box when
assigning a finite conductivity or impedance boundary. The effects of these boundaries are incorpo-
rated into the field solution in the usual manner, but the radiated fields in the 3D Post Processor are
computed as if the lossy ground planes were perfectly conducting.
When defining an infinite ground plane, keep the following requirements in mind:
• An infinite ground plane in a model must be exposed to the background.
• An infinite ground plane must be defined on a planar surface.
• The total number of infinite ground planes and symmetry planes cannot exceed three.
• All infinite ground planes and symmetry planes must be mutually orthogonal.
• For impedance, layered impedance, or finite conductivity boundaries only one infinite ground
plane can exist in a design. For perfect E boundary conditions, multiple antenna ground planes
are supported
Frequency-Dependent Boundaries and Excitations
In general, boundary and excitation parameters cannot depend on intrinsic functions. An exception
is when a parameter depends on the variable Freq, which represents the solution frequency. The
following boundary parameters can be assigned an expression that includes Freq:
• Impedance boundary - the Resistance and Reactance parameters.
• Finite conductivity boundary - the Conductivity parameter. If a material is specified, the mate-
rial can be frequency dependent.
• Slave boundary - the Phase parameter.
• Lumped RLC boundary - Resistance, Inductance, and Capacitance parameters.
• Layered impedance boundary - materials assigned on layers can be frequency dependent.
Note Dependence on Freq is supported for single-frequency solutions and for Discrete and
Interpolating frequency sweeps. If a Fast sweep is requested, the solution will be valid
for the center frequency, but may not be valid at other frequencies.
Einc
Hinc
Computational Domain
εrs,μrs
εr1,μr1
εr3,μr3
εr2,μr2
Radiation BC
Et=Einc +Es
Ht = Hinc+Hs
Computational Domain
εrs,μrs
εr1,μr1
εr3,μr3 For a Dirichlet BC
εr2,μr2 n x Es = -n x Einc
Radiation BC
• Special treatments on
• Ports
• Impedance BCs
• PMC
Total Field Description: Usual Approach
When the incident field is known, everywhere, the solvers take the usual approach. Both E and H
jump with n x Einc and n x Hinc on the interfaces, respectively.
Et3,Ht3
Et1,Ht1 εr3,μr3
εr1,μr1 Et2,Ht2
εr2,μr2 εrs,μrs
Es,Hs
Radiation BC
E s, H s
Einc
Et3,Ht3 n
Et1,Ht1 εr3,μr3 kinc
εr1,μr1 Et2,Ht2
εr2,μr2 εrs,μrs
Es,Hs
Radiation BC
Einc
Et3,Ht3 n
t1
E ,H t1 εr3,μr3 kinc
εr1,μr1 Et2,Ht2
εr2,μr2 εrs,μrs
Es,Hs Et=Einc +Es
Ht = Hinc- Hs
Radiation BC = Space Port
Related Topics
General Approach for Scattered and Total Field Decomposition
Scattered and total field formulation pros and cons
Where the Solvers Apply Scattered or Total Field Formulations
Summary for Total and Scattered Fields
Excitations
Assigning excitations to an HFSS design enables you to specify the sources of electromagnetic
fields and charges, currents, or voltages on objects or surfaces. This area of the Technical Notes
includes information on the following topics:
• Wave Ports
• Lumped Ports
• Terminals
• Floquet Ports
• Incident Waves
• Voltage Sources
• Current Sources
• Magnetic Bias Sources
• Dembedding
Wave Ports
By default, the interface between all 3D objects and the background is a perfect E boundary
through which no energy may enter or exit. Wave ports are typically placed on this interface to pro-
vide a window that couples the model device to the external world.
HFSS assumes that each wave port you define is connected to a semi-infinitely long waveguide that
has the same cross-section and material properties as the port. When solving for the S-parameters,
HFSS assumes that the structure is excited by the natural field patterns (modes) associated with
these cross-sections. The 2D field solutions generated for each wave port serve as boundary condi-
tions at those ports for the 3D problem. In addition to serving as a boundary condition, a wave port
also supplies port impedances and propagation constants that are useful in describing waveguides
or transmission lines.
A wave port is restricted to reside at an external boundary of a 3D problem. In some instances, it
makes sense to get around this restriction by defining a wave port in the interior of a 3D domain by
capping the wave port surface with a PEC object. In doing this, in effect the wave port is viewed as
residing at the external boundary of a 3D problem. However, in general lumped ports should be
used when defining ports in the interior of a 3D domain.
Often there is a need to have a particular field direction of a mode pattern for consistent results.
There are two different methods in HFSS to accomplish this task. The most basic method is where,
in the presence of an integration line, HFSS resolves 180 degree ambiguity by enforcing the electric
field mode pattern to have a positive line integral along the integration line for that mode (Mode
Polarity). The second more advanced option is where HFSS aligns electric field mode patterns,
when appropriate, in specific directions (Mode Alignment). This second option consists of a man-
ual but general approach and an automated approach for a few port types. For more in-depth dis-
cussions refer to the following topics:
• Mode Polarity
• Mode Alignment
Related Topics
Assigning Wave Ports for Modal Solutions
Mode Polarity
When HFSS computes an excitation mode pattern, the direction of the field at ωt = 0 is arbitrary;
the field can point in one of at least two directions. This document addresses how to remove the
ambiguity of the field direction when a mode is not part of a set of degenerate modes. For the case
of degenerate modes, there is no unique mode alignment and this topic is addressed in Mode Align-
ment.
In the figure below, at ωt = 0 the electric field pattern of the mode can point either up (left image)
or down (right image). Either direction is correct - unless a preferred direction is specified. This
issue becomes of concern when inspecting the phase angle of S-parameters.
For example, consider a 3D model containing two single-mode ports of the type shown in the fig-
ure. The phase of the computed S-parameters linking the two ports will flip by 180 degrees if the
polarity of the mode at either port is reversed. Therefore when transmission S-parameter phase is of
interest in models such as this, the user has the responsibility to properly set the mode polarity at
each port.
To specify the polarity of a mode, a mode calibration must be performed by creating an appropriate
integration line. For instance, if the preferred direction is up then the integration line should be
drawn at the center of the waveguide starting at the bottom and ending at the top. In general, a
mode calibration is automatically performed if an integration line has been defined for a mode
where HFSS ensures that the real part of the line integral of the electric field of that mode is posi-
tive.
Mode Alignment
In some cases the requested set of modes to be used with a wave port contains degenerate modes.
For that case, the modes that are degenerate need special care in obtaining a unique orientation of
the mode patterns which is important, for example, when a specific orientation for a given mode is
intended to excite the structure.
For example, in the case of a square waveguide the first two dominant modes form a degenerate
mode set. Therefore, in order to guarantee that the typically desired orientation of the modes (TE01
17-116 Technical Notes
HFSS Online Help
and TE10) are used for an HFSS simulation, the user needs to enable one of the two supported mode
alignment options. The first option is general but manual and requires detailed user knowledge of
the mode patterns while the other is restricted to a few basic port types where HFSS automatically
aligns the modes.
The general mode alignment option is enabled by defining appropriate integration lines for the
modes that should be aligned and selecting Align modes using integration lines in the Modes tab
of the Wave Port setup window. Note that not all modes requested for a wave port need to have an
integration line defined - only the ones for which mode alignment is desired. It is important that
you draw integration lines that make sense for the modes to be aligned along and that all the modes
that form a set of degenerate modes have a line defined. For example, if the first two modes of a
square waveguide should be TE10 and TE01, you should draw two lines through the center of the
waveguide where one line starts at the bottom and ends at the top while the other line starts on the
left side and ends on the right side.
You enable the automated mode alignment option by selecting Align modes analytically using
coordinate system in the Modes tab of the Wave Port setup window. By selecting this option, the
user will be asked to draw a local coordinate system which is used to automatically align the modes
in pre-defined directions. This option is only available for a select few port types discussed in
Analytic Port Types.
In order to get intended outcome of either alignment option, it is necessary to include all modes in a
set of degenerate modes. For example, assume that modes 3, 4, 5, and 6 are degenerate. You should
either include all of them by specifying at least 6 modes or none of them by specifying at most 2
modes.
Analytic Port Types
Analytic mode alignment is available for certain port types by selecting Align modes analytically
using coordinate system in the Modes tab in the Wave Port setup window. If analytic mode align-
ment is selected for a port that is not supported, the port setup becomes invalid. Here is a summary
of the validation for analytic mode alignment:
• The port geometry must correspond to a known analytic type, as follows:
• Rectangular. The port must have four linear edges which meet at right angles. Square
ports are a special case of rectangular.
• Circular. The port must have all curved edges. The radius, perimeter, and area of the face
must be consistent with those of an ideal circle.
• Faceted Circular. The port must have at least 16 edges, all linear and of equal length. The
radius, perimeter, and area of the face must be consistent with those of an ideal polygon.
• Circular or Faceted Coax.
Explicit. The port face must have one set of inner and one set of outer edges. The inner
radius, outer radius, face area and perimeter must be consistent with an ideal coaxial circle
or polygon.
Implicit. The port face itself must be circular or faceted circular, and it must have a circu-
lar or faceted circular conducting object touching it and aligned with the face center.
• The port must be assigned to a single face of a 3D object whose material is isotropic. Assign-
ment to sheets is not allowed, as this makes it difficult to determine the object material.
• No other material can contact the port, except for the inner conductor of a coax.
• Only Perfect E and Finite Conductivity boundaries can contact the port.
When reading legacy projects prior to v12, HFSS automatically tests ports with the "Polarize E
Field" option enabled. If they qualify for analytic alignment, that option will be selected, and U-V
lines will be set from the first two modal integration lines.
Related Topics
Assigning Wave Ports for Modal Solutions
Technical Notes: Wave Ports
Technical Notes: Mode Alignment
Lumped Ports
Lumped ports resemble wave ports, but can be located internally and have a complex user-defined
reference impedance. Lumped ports are restricted to single mode ports and the S-parameters are
always based on the user defined reference impedance. This mainly because no transmission line is
being modeled in the interior domain which suggests an interpretation of the lumped port as a mea-
surement probe being connected to the surface of the lumped port with the reference impedance
specified by the user.
When a lumped port is used internal to a 3D problem, it makes sense to place the lumped port at a
location where the field distribution would approximately be the same as the dominant mode of the
port definition in the absence of the lumped port. A typical example of this is when a rectangular
port is drawn between a conductor trace and a ground plane with the face oriented perpendicular to
both conductors. The port mode resulting from this case is a parallel plate mode which will often
closely resemble the field distribution at that location in the absence of the port.
A perhaps unsuspected result of using a complex reference impedance is that the S-parameters can
be greater than one even for a passive device.
Note When a lumped port is used as an internal port, the conducting cap required for a
traditional wave port must be removed to prevent short-circuiting the source.
Terminals
HFSS can categorize microwave structures in terms of a black-box that relates voltages and cur-
rents flowing in and out of a given structure. The black-box has several terminals, each with an
associated voltage/current pair. In HFSS, these terminals reside inside wave ports that enable post
processing of a modal representation of the black-box into the terminal representation.
When a terminal project is solved using HFSS, the number of modes for a port is determined by the
number of terminals touching the port. If N+1 distinct conductors touch the port, there are N termi-
nals and one reference conductor usually referred to as ground. The modal port representations of
the electric and magnetic fields are:
N
E = ∑ ( an + bn )en (1)
n=1
N
H = ∑ ( an – bn )hn (2)
n=1
where an and bn are unitless complex amplitudes of the ingoing and outgoing modal fields, respec-
tively. The modal black-box representation of a given structure is given by HFSS in terms of the
generalized scattering matrix, S,
b = Sa (3)
where a and b are the unitless complex modal coefficient vectors. In order to obtain a terminal rep-
resentation of the black-box, N integration paths Ci and N integration loops Li are used to define N
voltages and N currents, respectively,
N
i = ∫ ( E ⋅ dl ) = ∑ ( an + bn ) ∫ en ⋅ dl (4)
Ci n=1 Ci
N
= ∑ ( an + bn )Tin i = 1,2... ,N
n=1
N
ii =
°∫ ( H ⋅ dl ) = ∑ ( an – bn ) °∫ hn ⋅ dl (5)
Ci n=1 Ci
N
= ∑ ( an – bn )Uin i = 1,2... ,N
n=1
i = U(a – b) (7)
Combining these equations with (3), yields the following circuit or terminal description of the
black-box representation of the structure
i = Yv (8)
where α and β are ingoing and outgoing pseudo waves, respectively. The St matrix is obtained by
assuming that the voltages and currents are measured by some device with a given renormalizing
impedance. This assumption leads to the following relations.
(11)
1⁄2
v = Z ref (α + β)
–1 ⁄ 2
i = Z ref (α – β) (12)
where Zref is a renormalizing impedance matrix representing the measuring device. In HFSS, the
user has the option to use the terminal characteristic impedance matrix, Zo, as the renormalizing
impedance matrix by using the 'Do Not Renormalize' option in the port post processing tab. This
means that the measuring device is perfectly matched to the transmission line. By default, all the
terminals are individually renormalized which results in Zref being a diagonal renormalizing
impedance matrix. An expression for St is obtained by using equations (8) - (12)
amounts of system noise. A differential pair is an effective way to remove noise from a signal
because when a receiver processes a differential signal it simply subtracts the voltages from the
two traces. This can dramatically reduce the amount of noise in the differential signal compared to
if the traces were driven individually (single-ended signals).
In HFSS, a differential pair can be defined for two terminals residing in the same wave port or for
terminals that reside in two different wave ports or lumped ports. In the case of wave ports,
matched differential pairs can be defined by not renormalizing the wave ports involved in the dif-
ferential pair definitions.
Related Topics
Technical Notes: Computing Differential Pairs
Computing Differential Pairs
To obtain various differential pair quantities, we first define differential and common voltages vd
and vc in terms of the singled-ended terminal voltage pairs v1 and v2, (see Setting up Differential
Pairs).
The differential and common voltages vd and vc are defined by
vd = v1 – v2 (1)
v1 + v2
v c = ----------------
2
Consistent with power conservation, the corresponding differential and common currents, repre-
sented as id and ic respectively, are defined by
(2)
i1 – i2
i d = --------------
2
ic = i1 + i2
Equations (1) and (2) can be concisely represented as
v = Qe (3)
i = Q-Tu
where
v1 i1 vd id
v = i = e = u =
v2 i2 vc ic
In the single-ended case, the characteristic impedance for a pair of transmission lines may be writ-
ten in the form of a matrix relating the voltages and currents on the two (uncoupled) lines,
(1) (7)
v1
= Z ref 0 i1
v2 (2) i2
0 Z ref
where Z(1)ref and Z(2)ref are the user-specified renormalizing impedances. In the differential case,
the matrix equation relating differential and common currents and voltages is written as:
(d) (8)
vd
= Z ref 0 id
vc (c) ic
0 Z ref
In this case, Z(d)ref and Z(c)ref denote the user-specified differential and common renormalizing
impedances, respectively.
Floquet Ports
The Floquet port in HFSS is used exclusively with planar-periodic structures. Chief examples are
planar phased arrays and frequency selective surfaces when these may be idealized as infinitely
large. The analysis of the infinite structure is then accomplished by analyzing a unit cell. Linked
boundaries most often form the side walls of a unit cell, but in addition, at least one "open'' bound-
ary condition representing the boundary to infinite space is needed. The Floquet port is a special-
ized boundary condition to handle this case.
The Floquet port is closely related to a Wave port in that a set of modes, here "Floquet modes", is
used to represent the fields on the port boundary. Fundamentally, Floquet modes are plane waves
with propagation direction set by the frequency and geometry of the periodic structure. Just like
Wave modes, Floquet modes have propagation constants and experience cut-off at a sufficiently
low frequency.
When a Floquet port is present, HFSS performs a modal decomposition that gives additional infor-
mation on the performance of the radiating structure. As in the case of a Wave port, this informa-
tion is cast in the form of an S-matrix interrelating the Floquet modes. In fact, if Floquet ports and
Wave ports are simultaneously present, the S-matrix will interrelate all Wave modes and all Floquet
modes in the model. Floquet ports can be combined with lumped ports, but not with terminal ports.
Related Topics
Technical Notes: Formula Summary for HFSS Floquet Modes
Formula Summary for HFSS Floquet Modes
• Planar array lattice is specified by lattice vectors a and b.
• Lattice angle α defined by a * b = abcosα
• Unit cell area A
• Global material is lossless, isotropic, and homogeneous, and specified by real εr and μr.
c = b – ( b ⋅ â )â (2)
c
ŷ = -- (3)
a c
where â = ---
Unit vector r̂ adenotes scan direction. In the global coordinate system (GCS) the components of
s
r̂ s are given by (sinθscosφs, sinθssinθφs, cosθs) where scan angles θs and φs are specified as
spherical angles in the GCS.
ψa = μ r ε r k s r̂ ⋅ a (4)
ψb = μ r ε r k 0 r̂ s ⋅ b (5)
m ,nε { … ,– 2 ,– 1 ,0 ,1 ,2 ,… } (6)
2πm ψ a
ka = - + ------
---------- If kz ≠ 0 (7)
a a
2πn ψ b
kb = - + ------
--------- (8)
b ab
kx = ka (9)
kb
k y = ----------- – k a cot α (10)
sin α
2 2 2
k c = kx + ky (11)
2 2
kz = μr εr k 0 – k c (12)
1 – jk x x –jk y y
ψ mn ( x ,y ) = ---e e (13)
A
17-124 Technical Notes
HFSS Online Help
(1) k y x̂ – k x ŷ (14)
Ψ mn = ----------------------- ψ mn ( x ,y ) ( kc ≠ 0 )
kc
(2) k x x̂ + k y ŷ (15)
Ψ mn = ----------------------- ψ mn ( x ,y ) ( kc ≠ 0 )
kc
˜ (1) 1
Ψ mn = --- ( sin θ s x̂ – cos θ s ŷ ) ( kc ≠ 0 ) (16)
A
˜ (2) 1
Ψ mn = --- ( sin θ s x̂ + cos θ s ŷ ) ( kc ≠ 0 ) (17)
A
TE TE (1)
e mn = N mn Ψ mn (18)
TE TE
TE
h mn = Y mn ẑ × emn (19)
TE
kz 1
Y mn = ----------- ----- (20)
μ0 k0 η0
TE 1
Nmn = μ r k 0 ------------ η 0 (21)
kz
TE
ẑemn = 0 (22)
TE TE ⎛ k c⎞
TE
ẑh mn = – ẑ Ymn Nmn ⎜ -----⎟ ψ mn (23)
⎝ k z⎠
TE TM (2)
e mn= N mn Ψ mn (24)
TM TM
TM
h mn = Y mn ẑ × e mn (25)
εr k
TM 0 1
Y mn = ---------- ----- (26)
kz η0
1 kz (27)
N mn = -------------- ------------ η 0
TM
εr k0 kz
TM ⎛ k c⎞ (28)
TM
ẑe mn = – ẑ N mn ⎜ -----⎟ ψ mn
⎝ k z⎠
TM
ẑh mn = 0 (29)
If kZ = 0, use the preceding kz ≠ 0 formulas with kZ = α where 0 < α <<1 is a small constant.
If kC = 0
TEM1 TEM1
h mn =Y TEM ẑ × e mn (31)
TEM 2 TEM2
h mn = Y TEM ẑ × e mn (33)
ε 1 (34)
----r- ------
TEM
Y =
μr η0
TEM 1
N = ---------------- (35)
TEM
Y
Incident Waves
There are different kinds of incident wave sources in HFSS. Analytical wave forms are defined by
formulas. The following analytical wave forms exist:
• Plane Wave
• Evanescent Plane Wave
• Electric Spherical Wave (Electric Hertzian Dipole)
• Magnetic Spherical Wave (Magnetic Hertzian Dipole)
• Cylindrical Wave
• Gaussian Beam
• Linear Antenna
Numerical Wave Forms can come from the solution of another HFSS project or from a non-HFSS
project via DataLink. Two numerical wave forms exist:
• Near Field Wave
• Far Field Wave
Plane Wave
An incident plane wave is a wave that propagates in one direction and is uniform in the directions
perpendicular to its direction of propagation. The angle at which the incident wave impacts the
device is known as the angle of incidence.
ku
LO
d
r0
r-r0
GO r P
E inc = E 0 e – j k 0 k u ( r ⋅ r 0 )
where
• Einc is the incident wave.
• E0 is the E-field polarization vector.
• k0 is the free space wave number. It is equal to ω μ0 ε0 .
ku
LO
d
r0
r-r0
GO r P
d = ku • ( r – r0 ) α = Re ( k )
– αd – jkd
β = Im ( k ) E = E0 e e
k β – jα
H 0 = ---------------- ( k μ × E 0 ) = ---------------- ( k μ × E )
ωμ 0 μ r ωμ 0 μ r
Related Topics
Incident Waves
θ r
1/2
1/2
Hr = 0 Hθ = 0
kI m l sin θ 1 1 – jkr
H θ = j --------------------- 1 + ------- – -----------2- e HΦ = 0
4πη r jkr ( kr )
Related Topics
Technical Notes 17-129
HFSS Online Help
Incident Waves
Cylindrical Wave
The analytical formulas of a Cylindrical Wave are:
LO
r0
r-r0
ρ0
ρ
E0
GO r P
– jkρ
C1 e e jπ ⁄ 4
E z ( ρ ) = ------------------ where C 1 = ZI k ⁄ 8π e
ρ
– jkρ
C2 e
H φ ( ρ ) = ------------------ with C2 = C1 ⁄ Z
ρ
Related Topics
Incident Waves
Gaussian Beam
The analytical formulas of a Gaussian Beam are:
ku
LO
L
r0
r-r0
GO r P
Where
L = ( r – r0 ) • ku D = ( r – r0 ) × ku ⎛ Lλ ⎞ 2 0.5
W ( L ) = W 0 1 + ⎜ -----------------⎟
⎝ πW 2 n⎠
2 2 0
⎛ πW 0 n⎞ Lλ
2
R ( L ) = L 1 + ⎜ -----------------⎟ Ψ ( L ) = atan ----------------
2
⎝ Lλ ⎠ π W0 n
2
⎛ D ⎞
2 2 ⎜ – jk • ( r – r 0 ) – jk --------------- + j Ψ ( L )⎟
inc W0 –D ⁄ W ( L ) ⎝ 2R ( L ) ⎠
E = E 0 ------------- e e
W( L)
2
E = E 0 × exp ( – tt ) (1)
where
t – 1.5
tt = 2 × f max × --------------- (2)
f max
where
0876
f max = ------------ (3)
t rise
Related Topics
Incident Waves
Linear Antenna
The analytical formulas of a linear antenna are:
R P(r, θ, φ, )
θ' θ
dz r
1/2
z’
y
1/2
Related Topics
Incident Waves
Voltage Sources
A voltage source in HFSS can be defined on surface located anywhere in the 3D problem space, but
it typically makes sense to place the source on a surface between two conductors such that a user
defined total voltage is maintained between the conductors.
A voltage source is implemented in HFSS by forcing the electric field on the source surface to
maintain a user-specified voltage drop along the voltage line. You can specify any surface as the
source surface, but the prescribed field pattern is best suited for rectangular planar surfaces or non-
planar surfaces obtained from the side wall surface of cylinders with uniform cross sections such as
17-132 Technical Notes
HFSS Online Help
a circular cylinder. The enforced electric field pattern is obtained by projecting a static uniform
field onto the source surface with the electric field in the direction of the user defined voltage line.
A voltage source cannot be used to extract S-parameters. For S-parameter computations of an
HFSS design involving a mixture of ports and voltage sources, all the voltage sources are shorted
by treating the voltage source surface as a perfect electric conductor.
Current Sources
A current source in HFSS can be defined on a surface located anywhere in the 3D problem space,
but it typically makes sense to place the source on a surface between two conductors such that it
injects the user defined total current onto the conductors. A current source is implemented in HFSS
by weakly enforcing the jump across the source surface of the tangential component of the mag-
netic field, Δ H , to be related to a surface current density, Js :
n̂ × Δ H = Js
where n̂ is the unit normal of the surface. The surface current density can be expressed as
Js = J 0 û where J 0 is the magnitude and û is the unit vector in the direction of current flow.
The unit vector is in the direction of the user defined current flow direction line. The magnitude is
obtained by first assuming that the surface is a rectangle such that the width, w, is equal to the area
divided by the length of the current flow direction line. The magnitude is set equal to the total cur-
rent specified by the user divided by w. Note that any source surface is allowed but considering the
definition of the surface current density it is recommended to only use a planar rectangular surface.
A current source cannot be used to extract S-parameters. For S-parameter computations of an HFSS
design involving a mixture of ports and current sources, all the current sources are kept opened by
treating the current source surface as a natural boundary condition where no special behavior of the
electric field is explicitly enforced.
Magnetic Bias Sources
When you create a ferrite material, you must define the net internal field that biases the ferrite by
assigning a magnetic bias source. The bias field aligns the magnetic dipoles in the ferrite, produc-
ing a non-zero magnetic moment. In HFSS, a ferrite’s permeability tensor is a direct result of an
applied static magnetic bias field. The static field causes the tensor to assume an hermitian form,
with cross coupling terms between field components perpendicular to the bias.
When the applied bias field is assumed to be uniform, you will specify net internal bias field as well
as the tensor coordinate system through a rotation from the global coordinate system. When the
applied bias field is non-uniform, neither specified coordinate system rotations nor specified bias
are allowed. The permeability tensor’s local coordinate system and bias field are calculated on a
tetrahedron by tetrahedron basis, both of which are determined by the calculated static solution.
HFSS references the static solution project as the source of the non-uniform magnetostatic field
information during solution generation.
Multiple uniform bias excitations may be included in a design, but only non-uniform bias is
allowed. In addition, a design cannot contain a bias excitation of both types. If only one excitation
is included in a design, its type can be changed from uniform to non-uniform, and visa versa.
Related Topics
Technical Notes: Uniform Applied Bias Fields
Technical Notes: Non-uniform Applied Bias Fields
Uniform Applied Bias Fields
The applied DC bias that causes ferrite saturation is always in the positive z direction of the tensor
coordinate system. Initially the tensor coordinate system is assumed to be aligned with the fixed
coordinate system; the tensor’s z-axis is the same as the model’s z-axis. To model other directions
of applied bias, the permeability tensor must be rotated so that its z-axis lies in another direction on
the fixed coordinate system. This is accomplished by specifying the rotation angles about the axes
when you assign a magnetic bias source to a model surface.
The rotation angles should be defined in the Magnetic Bias Source dialog box in such a way that
the tensor coordinate system is obtained in the following manner:
1. Rotating the tensor coordinate system by α degrees (from the X Angle) around the fixed x-
axis.
2. Rotating the resulting tensor coordinate system by β degrees (from the Y Angle) around the
new y-axis.
3. Rotating the new tensor coordinate system by γ degrees (from the Z Angle) around the new z-
axis.
This concept is illustrated in the following graphic. In the first panel, the permeability tensor is
rotated α degrees about the x-axis. In the second panel, the tensor is rotated β degrees about the y'-
axis (the new y-axis). In the third panel, the tensor is rotated γ degrees about the z''-axis (the new z-
axis). The resulting tensor has the coordinate system (x''y''z'') relative to the fixed coordinate sys-
tem.
1.
z x 3. y’
2.
z’ y’ x’ y’’
z’’ x’’
α β γ
y z’ x’
x y’ z’’
For example, to model the DC bias in the x direction you would rotate the tensor coordinate
system so that its z-axis lies along the x-axis of the fixed coordinate system. To do this you
would enter 0 for the X Angle, 90 for the Y Angle, and 0 for the Z Angle.
Non-uniform Applied Bias Fields
To accurately model a ferrite in an applied static magnetic bias field, the non-uniform magnetic bias
fields must also be calculated. In HFSS, a ferrite’s permeability tensor is a direct result of an
applied static magnetic bias field. The static field causes the tensor to assume an hermitian form,
with cross coupling terms between field components perpendicular to the bias. A uniform bias field
is difficult to achieve in practice. Even if the bias field is nearly uniform, a non-ellipsoidal-shaped
ferrite material will have non-uniform demagnetization, resulting in non-uniform fields in the fer-
rite.
Use the magnetostatic solver provided in the Maxwell 3D Field Simulator to generate a solution for
non-uniform magnetostatic fields. Once a solution is generated it may be imported into HFSS.
Note To specify the non-uniform bias field, you must have purchased the Maxwell 3D Field
Simulator. Refer to the Maxwell 3D Field Simulator documentation for instructions on
solving for non-uniform magnetostatic fields.
Deembedding
Deembedding means adding or subtracting transmission line. In HFSS only wave ports and Floquet
ports are allowed to be deembedded where the S-parameters are modified as described in Deem-
bedding S-Matrices. Fields used for visualization and the calculator can also be modified by select-
ing Include Post Processing Effects in the Edit Sources panel. The new results appear
instantaneously.
This section shows an example where subtracting transmission line can be useful and an example
where adding transmission line can be useful.
Consider the aperture-coupled patch antenna shown in Fig. 1. A microstrip trace located below a
ground plane feeds a patch antenna located above the ground plane. A slot in the ground plane cou-
ples power from the microstrip trace to the antenna.
microstrip trace
ground plane
slot
patch antenna
A port is located at the beginning of the trace. It cannot be located very close to the slot, since a port
has to be located in a position where a clean transmission-line mode is expected, at some distance
from the first discontinuity. The port is shown in Fig. 2. One edge coincides with the ground plane.
The other edges are such that the port width is several times the trace width and the port height sev-
eral times the substrate thickness. The red arrows represent the port field solution. Notice that the
three non-ground-plane edges don't influence the port solution noticeably, so this port is large
enough.
The S-parameter characteristic is shown in Fig. 3 in a rectangular plot and in Fig. 4 in a Smith
chart. Note that the resonance frequency in Fig. 3 corresponds to the point in Fig. 4 where the curve
is closest to the center of the chart. Also note that the curve circles the chart several times.
Relative Permittivity
The permittivity of dielectrics is assumed to be complex, as follows:
ε = ε' – j ε''
which can also be expressed as
ε''
ε = ε' ( 1 – j −− ⎞
ε' ⎠
where ε′ is the real portion of ε and from which the relative permittivity is defined as:
ε' = ε r ε 0
where ε0 is the permittivity of free space.
ε′′/ε′ is the dielectric loss tangent.
If a material’s losses due to bulk conductivity will be significant, such as in semiconductor dielec-
tric materials, an additional bulk conductivity value, σ, must be added. From the time harmonic
form of Maxwell’s equations, the complex permittivity, εc is defined as
∇ × H = ( σ + jωε )E = jωε c E
where
σ
ε c = ε ( 1 – j tan δ – j ------- ⎞
ωε ⎠
Bulk Conductivity
HFSS is capable of including conductivity in the model either as a bulk material loss factor, similar
to dielectric loss tangent, or as an impedance boundary condition applied to the outer surfaces of
the object. The choice of bulk material loss instead of the boundary condition is made by selecting
Solve Inside in the Properties window.
The choice between bulk material loss and the surface boundary condition is problem dependent.
The boundary condition should be applied whenever the conductor is much thicker than the skin
depth at the solution frequency. In this case, the unknowns within the conductor are not included in
the unknown vector, resulting in a smaller matrix and a faster analysis. However, if the conductor is
not thick relative to the skin depth, the bulk material conductivity must be used to arrive at an accu-
rate solution. With this assumption, the wave equation reduces to
–1
∇×⎛⎝ --------- ∇×E⎞⎠ = ( j ωε + σ ) E
j ωμ
The threshold where HFSS will automatically chose whether an object will be solved inside can be
accessed via the Tools>Options>HFSS Options>Solver tab.
Note If you plan to do a fast frequency sweep for a design that includes dielectrics, make sure
that the dielectric or magnetic loss tangent does not vary significantly over the requested
frequency range. If they do, the results may not be what you expect. In cases where the
loss tangent does vary significantly over the frequency range in which you are interested,
copy and solve the design several times, adjusting the loss tangent and associated
frequency range for the copied design so that the loss tangent is relatively stable over the
design’s requested frequency range.
Ferrite Materials
Ferrite materials are used to model the interaction between a microwave signal and a material
whose magnetic dipole moments are aligned with an applied bias field. The gyrotropic quality of
the ferrite is evident in the permeability tensor which is Hermitian in the lossless case. The Hermi-
tian tensor form leads to the non-reciprocal nature of the devices containing microwave ferrites. If
the microwave signal is circularly polarized in the same direction as the precession of the magnetic
dipole moments, the signal interacts strongly with the material. When the signal is polarized in the
opposite direction to the precession, the interaction will be weaker. Because the interaction between
the signal and material depends on the direction of the rotation, the signal propagates through a fer-
rite material differently in different directions.
If you assign a ferrite material to an object, you must assign a magnetic bias source to the object.
Magnetic Saturation
A material with a non-zero magnetic saturation is considered to be a ferrite. When a ferrite is placed
in a uniform magnetic field, the magnetic dipole moments of the material begin to align with the
field. As the strength of the applied bias field increases, more of the dipole moments align. The
magnetic saturation, Ms, is a property that describes the point at which all of the magnetic dipole
moments of the material become aligned. At this point, further increases in the applied bias field
strength do not result in further saturation. The relationship between the magnetic moment, M and
the applied bias field, H, is shown below.
Magnetic Moment M M
s
0
Applied bias field H
The magnetic saturation, 4πM, is entered in gauss.
Lande G Factor
The Lande g factor is a ferrite property that, on a microscopic level, describes the total magnetic
moment of the electrons according to the relative contributions of the orbital moment and the spin
moment. When the total magnetic moment is due entirely to the orbital moment, g is equal to one.
When the total magnetic moment is due entirely to the spin moment, g is equal to two. For most
microwave ferrite materials, g has a range from 1.99 to 2.01. The Lande g factor is dimensionless.
Delta H
Delta H is the full resonance line width at half-maximum, which is measured during a ferromag-
netic resonance measurement. It relates to how rapidly a precessional mode in the biased ferrite will
damp out when the excitation is removed. The factor ΔΗ doesn’t appear in the permeability tensor;
instead, the factor α appears. The factor α is computed from
γμ 0 ΔH
α = – -----------------
2ω
The factor α changes the κ and χ terms in the permeability tensor from real to complex, which
makes the tensor complex non-symmetric (where it had been hermitian for lossless ferrites).
Enter the full resonance line width at half maximum in the Delta H value box. Delta H is measured
at a specific frequency. That frequency needs to be entered by the user at the interface. 9.4 Ghz is
the frequency where Delta H is typically measured.
Anisotropic Materials
Anisotropic materials have characteristics that vary with direction. These characteristics are
defined by their anisotropy tensors. You must define three diagonals each for anisotropic permittiv-
ity, electric loss tangent, conductivity, permeability, and magnetic loss tangent. Each diagonal rep-
resents a tensor of your model along an axis. The alignment of the materials axis with respect to the
object is discussed in Assigning Material Property Types.
• Anisotropic relative permeability tensors
• Anisotropic relative permittivity tensors
17-144 Technical Notes
HFSS Online Help
Related Topics
Assigning Material Property Types
Setting Coordinate Systems
Creating a Relative Coordinate System
Change the Orientation of an object
Relative Permeability
Anisotropic Relative Permeability Tensors
Relative Permittivity
Bulk Conductivity
Dielectric Loss Tangent
Magnetic Loss Tangent
where
• μ1 is the relative permeability along one axis of the material’s permeability tensor.
• μ2 is the relative permeability along the second axis.
• μ3 is the relative permeability along the third axis.
• μ0 is the permeability of free space.
The relationship between B and H is:
x→μ Bx Hx
y→v By = μ Hy
z→w Bz Hz
To specify the relative permeability for an anisotropic material, enter the μ1, μ2, and μ3 values in
the Value boxes of the T(1,1), T(2,2), and T(3,3) rows, respectively. If the relative permeability is
the same in all directions, use the same value for μ1, μ2, and μ3. These values can also be entered as
variables.
Anisotropic Relative Permittivity Tensors
The permittivity tensor for an anisotropic material is described by
ε1 ε0 0 0
ε = 0 ε2 ε0 0
0 0 ε3 ε0
where
• ε1 is the relative permittivity of the material along one tensor axis.
• ε2 is the relative permittivity along the second axis.
• ε3 is the relative permittivity along the third axis.
• ε0 is the permittivity of free space.
The relationship between E and D is then
x→μ Dx Ex
y→v Dy = ε Ey
z→w Dz Ez
To specify the relative permittivity for an anisotropic material, enter the ε1, ε2, and ε3 values in the
Value boxes of the T(1,1), T(2,2), and T(3,3) rows, respectively. These values can also be entered
as variables.
Anisotropic Conductivity Tensors
The conductivity tensor for an anisotropic material is described by
σ1 0 0
[σ] = 0 σ2 0
0 0 σ3
where
• σ1 is the conductivity along one axis of the material’s conductivity tensor.
• σ2 is the conductivity along the second axis.
• σ3 is theconductivity along the third axis.
x→μ Jx Ex
y→v Jy = σ Ey
z→w Jz Ez
To specify the conductivity for an anisotropic material, enter the σ1, σ2, and σ3 values in the Value
boxes of the T(1,1), T(2,2), and T(3,3) rows, respectively. The values of σ1 and σ2 apply to axes
that lie in the xy cross-section being modeled. The values of σ3 apply to the z-component. These
values affect current flowing in dielectrics between the conductors. These values can also be
entered as variables.
Anisotropic Dielectric Loss Tangent Tensors
The dielectric loss tangent tensor for an anisotropic material is described by
ε' 1 ( 1 – j tan δ 1 ) 0 0
[ε] = 0 ε' 2 ( 1 – j tan δ 2 ) 0
0 0 ε' 3 ( 1 – j tan δ 3 )
where
• tanδ1 is the ratio of the imaginary relative permittivity to the real relative permittivity in one
direction.
ε″ 1
tan δ 1 = -------
ε′ 1
• tanδ2 is the ratio of the imaginary relative permittivity to the real relative permittivity in the
second direction.
ε″ 2
tan δ 2 = -------
ε′ 2
• tanδ3 is the ratio of the imaginary relative permittivity to the real relative permittivity in the
third orthogonal direction.
ε″ 3
tan δ 3 = -------
ε′ 3
• ε′ 1 , ε′ 2 , and ε′ 3 are the real relative permittivities specified earlier.ε
x→μ Dx Ex
y→v Dy = [ ε ] Ey
z→w Dz Ez
To specify the electric loss tangent for an anisotropic material, enter the tanδ1, tanδ2, and tanδ3 val-
ues in the Value boxes of the T(1,1), T(2,2), and T(3,3) rows, respectively. These values can also
be entered as variables.
Anisotropic Magnetic Loss Tangent Tensors
The magnetic loss tangent tensor for an anisotropic material is described by
μ' 1 ( 1 – j tan δ M1 ) 0 0
[μ] = 0 μ' 2 ( 1 – j tan δ M2 ) 0
0 0 μ' 3 ( 1 – j tan δ M3 )
where
• tanδM1 is the ratio of the imaginary relative permeability to the real relative permeability in
one direction.
μ″ 1
tan δ M1 = --------
μ′ 1
• tanδM2 is the ratio of the imaginary relative permeability to the real relative permeability in the
second direction.
μ″ 2
tan δ M2 = --------
μ′ 2
• tanδM3 is the ratio of the imaginary relative permeability to the real relative permeability in the
third orthogonal direction.
μ″ 3
tan δ M3 = --------
μ′ 3
• μ′ 1 , μ′ 2 , and μ′ 3 are the real relative permeabilities specified earlier.
x→μ Bx Hx
y→v By = [ μ ] Hy
z→w Bz Hz
To specify the magnetic loss tangent for an anisotropic material, enter the tanδM1 , tanδM2, and
tanδM3 values in the Value boxes of the T(1,1), T(2,2), and T(3,3) rows, respectively. These values
can also be entered as functions.
Anisotropic Materials and Ports
An anisotropic material can be in contact with a port under the following conditions:
• One principal axis of the anisotropic material is aligned normal to the port.
Frequency-Dependent Material Properties
The properties of some materials vary with the frequency of the field excitation. This frequency
dependence is often linear within a certain frequency range and constant outside of the frequency
range, as shown below,
where
• epsrlower is the relative permittivity of a material below the frequency range 20 - 50 GHz.
• epsrupper is the relative permittivity of a material above the frequency range 20 - 50 GHz.
• flower is the lower frequency, below which the material property is constant.
• fupper is the upper frequency, above which the material property is constant.
Technical Notes 17-149
HFSS Online Help
In general, to account for this variance within a given frequency range, use the Piecewise Linear
Material Input window dialog box to specify a property’s values at frequencies below and above
the frequency range. Based on these values, HFSS automatically creates a linear dataset that speci-
fies the property’s values at the desired frequencies during solution generation. This dataset can be
modified with additional points if desired.
Debye Materials
If the material is a lossy dielectric with a lower frequency near DC, use the Loss Model Material
Input dialog box to specify the material’s conductivity at DC or, if you prefer, its loss tangent
value at the lower frequency. HFSS also enables you to specify the lossy dielectric material’s high
frequency/optical permittivity.
In materials commonly encountered in mircowave applications ion and dipole polarization domi-
nate. These polarization types can be described by Debye’s relaxation polarization model:
( ε rstatic – ε roptical )
ε rcomplex = ε roptical + ---------------------------------------------
1 + j ωτ
where
τ = the relaxation time.
εrstatic = the static permittivity.
εroptical = the high frequency/optical permittivity.
HFSS uses the values you specify in the Loss Model Material Input dialog box in Debye’s equa-
tion above to determine the relative permittivity at any frequency.
Debye’s model is valid for most microwave applications. If the frequency exceeds the limit of
Debye’s model, other models that take atomic and electron polarization into account are available.
Frequency-dependent materials are appropriate for problems solved using a discrete or interpolat-
ing sweep. In a fast sweep, frequency dependent material properties are evaluated at the center fre-
quency which may result in less accurate results at the sweep extremes, depending on the sweep
range and frequency dependence of material property.
In the simulation of high speed connectors or PCB boards, it is important to take the losses into
account. Especially, in the case of transient analysis, where the improper specification of the fre-
quency dependence of the materials would lead to unphysical results. This section discusses the
loss mechanism of dielectric materials. Magnetic losses could also be taken into account, but mate-
rials commonly encountered in these applications are non-magnetic.
A lossy dielectric material is characterized by two measured values at a certain frequency: dielec-
tric constant εr and loss tangent tgδ. There are two problems with the specification of the frequency
dependence of dielectric materials:
• The frequency range, in which the solution has to be calculated, is much wider than the range
where measured material data are available. It is very common to have just two measured
points. A low frequency point, which can be taken as DC value and a higher frequency point,
which serves to describe the behavior of the material at high frequency. The question arises:
What is an appropriate model across the measured range as well as outside the measured
range?
• A measurement always suffers from errors. If the measured data are not consistent, it could
cause unphysical effects during the time domain analysis. A question arises again: how to
check whether the measured data are consistent, and how to adjust them if they are not.
To answer the questions raised we need to discusses the polarization loss mechanism of dielectric
materials.
Figure 1 shows the different polarization mechanisms occur in the frequency domain. It can be seen
from the figure that up to the microwave region, ion and dipole polarization dominate. These polar-
ization types can be described by Debye’s relaxation polarization model:
(1)
( ε rstatic – ε roptical )
ε rcomplex = ε roptical + ---------------------------------------------
1 + j ωτ
where
τ is the relaxation time,εrstatic,and εroptical are the static and high frequency permittivity, respec-
tively. Debye’s model is valid for the most of microwave applications. If the frequency exceeds the
limit of Debye’s model, there exists other models which take the atomic and electron polarization
into account [1].
The question is now how to fit Debye’s model to the actual material characteristics. In order to do
this, let us express the real part of the dielectric constant and the conductivity from Eq. (1):
ε rstatic = ε r1 (4)
and
The critical need is to predict the high frequency behavior of the material.
If we know εroptical from measurement, the high frequency behavior of Debye’s model is set. We
just need to calculate the relaxation time as:
(6)
b − b2 − 4
τ=
2ω 2
where
ω 2ε o (ε rstatic − ε roptical )
b=
σ2 (7)
and
σ 2 = ω 2ε oε r 2 tan δ 2 − σ o (8)
Knowing τ, Eqs. (2) and (3) prescribe the material characteristic in the whole frequency region.
If we do not know εroptical , it can be calculated by simultaneously solving the following two equa-
tions to get εroptical and τ:
( ε rstatic – ε roptical )
ε r2 = ε roptical + ---------------------------------------------
2
- (9)
1 + ( ωτ )
2
ω ε o τ ( ε rstatic – ε roptical ) (10)
σ 2 = σ o + -------------------------------------------------------------
2
-
1 + ( ωτ )
where εr2 is measured and σ2is determined by Eq.(8).
Solving equations (9) and (10), we get:
(11)
ε ε − ε r2
τ = o rstatic
σ2 −σo
This method also yields the parameters of the Debye’s model, but the accuracy of the method, espe-
cially at high frequencies, depends on the accuracy and the consistency of the measurement at
frequency f2.
Typical Debye’s model material characteristics can be seen in Fig. 2, where ε' = εr.
ωτ (ε rsrtatic − ε roptical )
ε '' = (12)
1 + (ω 2τ ) 2
1 + (ω 2τ ) 2
ε roptical = ε rstatic − ε rstatic − ε r 2 ( ) (13)
(ω 2τ ) 2
The model was verified by using a double strip line filled by FR4 material. A 10 mils section of the
line was modeled by HFSS and de-embedded into a 34 inch long line. The structure of HFSS model
can be seen in Fig. 3.
The calculated and measured frequency response of S12 can be seen in Fig. 5. The agreement
between the calculated and measured values is good.
The transient response of the line to an input pulse also has been calculated. The schematic arrange-
ment of the model in Maxwell Spice is shown in Fig. 6. The output signal is plotted in Fig. 7. The
green curve is the transient response of an ideal reference line (lossless) of the same length.
[1] E.U. Condon and Hugh Odishaw, Handbook of Physics, McGraw Hill Book Company, Inc., New
York Toronto London, 1958. Pp. 4-113 – 4-119.
[2] G.R. Strobl, The Physics of Polymers, Chapter 5, 2nd Ed. Springer, NY, 1977.
Related Topics
Defining Frequency-Dependent Material Properties
For information on how to create, edit and use scripts in HFSS see:
. in html format.
. in pdf format.
The pdf of the scripting guide provides a format and function better suited for printing than the
chm. You can print ranges of pages encompassing topics and subtopics as needed.
You can also access help for the scripting commands via the menu bar:
• Click Help>Scripting Contents
• Click Help>Scripting Index
• Click Help>Search Scripting
Recording a Script
Once you start to record a script, your subsequent actions are added to the script. Each interface
command has one or more associated script commands that are recorded to the script. The script is
recorded to a text file in .vbs (VBScript) file format.
1. On the Tools menu, click Record Script.
The Save As dialog box appears.
2. Use the file browser to locate the folder in which you want to save the script, such as:
C:\Ansoft\HFSS13\Scripts
Then double-click the folder’s name.
3. Type the name of the script in the File name text box, and then click Save.
The script is saved in the folder you selected by the file name filename.vbs.
4. Perform the steps that you want to record.
5. When you have finished recording the script, click Stop Script Recording on the Tools menu.
Scripting 18-1
HFSS Online Help
Scripting18-3
HFSS Online Help
18-4 Scripting
19
ANSYS Workbench Integration
Overview
ANSYS Workbench combines the strength of its core product solvers with the project management
tools necessary to manage project workflow. In ANSYS Workbench, analyses are built as systems,
which can then be combined into a project. The project is driven by a schematic workflow that
manages the connections between the systems.
From the schematic, you can interact with applications (called workspaces) that are native to
ANSYS Workbench and that display within the ANSYS Workbench interface. Native workspaces
include: Project Schematic, Engineering Data, and Design Exploration (Parameters and Design
Points).
You can also launch applications that are data-integrated with ANSYS Workbench, meaning the
application’s interface remains separate, but the data from the application communicates with the
native ANSYS Workbench data. Thus, data can be passed back and forth between any Ansoft
product on a Workbench Project Schematic and any supported ANSYS or Ansoft desktop product.
Depending on the application, data integration can include basic actions such as saving projects, as
well as more complex actions such as the coupling of Ansoft product variables to Workbench
Design Exploration parameters.
Data-integrated applications include the following Ansoft products: Designer 6.1, HFSS 13.0,
Maxwell/RMxprt 14.0, Q3D Extractor 10.0, and Simplorer 9.0.
Note For detailed information on working with ANSYS Workbench, please refer to the
Workbench documentation.
Note If you choose not to integrate the product with ANSYS 13.0 during installation, you can
perform this step after installation.
2. In the Integration with ANSYS 13.0 dialog box, ensure that the Yes radio button is selected,
You can confirm that ANSYS 13.0 is “aware” of the Ansoft integrated applications via the ANSYS
Workbench Options dialog, which shows the paths to the integrated Ansoft applications.
Objects, such as instances of Ansoft projects, that are placed on a Workbench Project Schematic are
referred to as systems. Ansoft circuit/system products: Rmxprt 14.0, Designer 6.1, and Simplorer
9.0, appear on Workbench Project Schematics as systems with two “cells” – Setup and Solution.
Ansoft field products: HFSS 13.0, Maxwell 14.0, and Q3D Extractor, add an additional Geometry
cell. If you invoke ANSYS DesignXplorer to use variables for refining a design, a Parameters
cell is added with a link to the associated Workbench Parameter Set. Refer to the ANSYS 13.0
Workbench help for details on working with systems, cells, and parameter sets.
Ansoft desktop products integrate with Workbench commands, services, and DesignXplorer in a
similar manner. Here are some of the ways in which Ansoft products integrate with Workbench:
• Adding new analysis systems
• Importing existing desktop projects
• Editing models
• Analyzing models
• Performing parameter studies
• Scripting
In addition to these major features, Workbench also allows you to Archive, Save, Backup,
Duplicate, and Delete Ansoft projects used in a Workbench project. Progress information and
messages from integrated Ansoft projects are also displayed in Workbench.
Note Detailed information for how to use ANSYS Workbench 13.0 for these operations can be
found in the ANSYS 13.0 documentation and online help.
or by selecting it from the context menu in the Workbench Project Schematic window:
Parameters from the Ansoft project are exposed to Workbench through the DesignXplorer setup.
The Ansoft system’s cell status on the Workbench project is updated as changes are made in the
Ansoft application desktop.
Scripting in Workbench
Scripts that include Ansoft projects can be recorded and played back via Workbench.
In this example, HFSS coax model Solution provides heat loss data as a thermal load to the ANSYS
Thermal Setup. The resulting analysis shows a thermal “hotspot”, providing the user with the
information needed to adjust the design’s material to fix the problem.
In this example, the Maxwell 3D electromagnetic force density Solution is used as the load in
ANSYS Structural to determine how these forces deform the motor’s stator and coils.
Glossary of Terms
Glossaries 20-1
HFSS Online Help
cost function In an optimization setup, a cost function is based on goal values specified for
at least one solution quantity. Optimetrics changes the design parameter values
to fulfill the cost function. The cost function can be based on any solution
quantity that HFSS can compute, such as field values, S-parameters, and
eigenmode data.
design variation A single combination of variable values that is solved during a parametric or
optimization setup.
Euler Angles Euler angles are used in Ansoft software to carry out a coordinate
transformation from one coordinate system to another. The Swiss
mathematician and physicist Leonhard Euler first developed the classical
rotation theorem to describe rotations in 3D space. The angles used are Euler
angles and can be used to describe any 3D rotation. These angles, given by (ö,
è, ø) represent a series of sequential rotations about two axis of the coordinate
system. The first rotation (ö) represents a rotation about the Z-axis of the
source coordinate system (X, Y, Z) which results in an intermediate coordinate
system denoted by (X’’, Y’’, Z’’). The second rotation (è) represents a rotation
of the intermediate coordinate system about the X’’-axis, again resulting in an
intermediate coordinate system denoted by (X’, Y’, Z’). The third and final
rotation (ø) represents a rotation about the Z’-axis of the intermediate
coordinate system. The final rotation completes the rotation and results in the
“target” coordinate system denoted (X, Y, Z).
For further information see, Eric W. Weisstein, “Euler Angles.” From
MathWorld – A Wolfram Web Resource.
http://mathworld.wolfram.com/EulerAngles.html .
goal In an optimization setup, a goal is the value of a solution quantity that you
want to be achieved during the optimization. A goal is represented as one row
in the cost function table. Each cost function defined in an optimization setup
must include at least one goal.
nominal design The original model on which Optimetrics analyses are based.
sweep definition See variable sweep definition.
variable sweep A set of variable values within a range that Optimetrics drives HFSS to solve
definition when a parametric setup is analyzed. A parametric setup can include one or
more sweep definitions.
20-2 Glossaries
Index
Index-1
changing priority of 14-77 Antenna Parameters
monitoring 14-18 calculated by HFSS 16-96
Optimetrics 15-1 antenna parameters
re-solving 14-79 decay factor 17-75
starting 14-1 exporting 16-181
stopping 14-78 antenna properties
analytic port types 17-117 accepted power 17-73
Analyze All command axial ratio 17-68
using 14-3 computing 16-179
animations incident power 17-74
controlling the display 16-34 max far-field data 17-60
exporting 16-35 maximum radiation intensity 17-70
frequency 16-32 overview 17-66
geometry 16-33 peak directivity 17-71
overview 16-31 peak gain 17-71
phase 16-31 peak realized gain 17-72
anisotropic materials polarization 17-67
about 17-143 polarization ratio 17-69
and ports 17-148 radiated power 17-72
assigning 10-9 radiation efficiency 17-74
conductivity tensor 17-145 arc lines
electric loss tangent tensor 17-146 center-point arcs 7-7
magnetic loss tangent tensor 17-147 three-point arcs 7-6
permeability tensor 17-144 arcs
permittivity tensor 17-145 center-point 7-7
anisotropy three-point 7-6
conductivity 17-145 array factor
electric loss tangent 17-146 and power normalizations 17-65
magnetic loss tangent 17-147 calculation 17-61
permeability 17-144 scan angle 17-61
permittivity 17-145 arrays
anisotropy tensors defining custom 16-179
defining conductivity 10-11 defining regular 16-178
defining dielectric loss tangent 10-12 arrows
defining magnetic loss tangent 10-13 modifying in plots 16-129
defining relative permeability 10-10 types in plots 16-129
defining relative permittivity 10-11 assigning excitations
ANSYS HFSS-IE 6-5
enable thermal feedback 13-27 AtPhase
ANSYS Workbench 12 Calculator General Commands 16-150
thermal link 14-80 attenuation constant 17-18
antenna arrays auto-save file 3-12
defining custom 16-179 average SAR
defining regular uniform 16-178 calculation of 17-34
Index-2
Axial Ratio setting in a parametric setup 15-11
definition 16-95 Calculator
axial ratio 17-68 General commands
AtPhase 16-150
B CmplxImag 16-150
CmplxMag 16-150
background color, setting 11-24 CmplxPeak 16-150
basis functions CmplxPhase 16-150
low-order solution basis 13-23 CmplxReal 16-150
mixed oder 13-20 Con 16-150
mixed order 13-23, 17-3 Imag 16-150
overview 17-3 Real 16-150
BIstatic RCS calculator
equations 16-97 entering values and geometries 16-141
bondwires exporting 16-165
drawing 7-30 general operations 16-148
overview 17-83 output commands 16-163
boolean commands registers 16-139
imprint projection 7-89 scalar operations 16-152
boundaries stack commands 16-140
and frequency dependence 17-109 stacks 16-138
assigning 8-1 units assumed as SI 16-140
assigning at face intersections 7-83 vector operations 16-157
default assignments 17-110 capacitors
deleting 8-39 modeling lumped 8-26
duplicating with geometry 8-43 Cartesian
editing properties of 8-38 coordinates on grid 11-26
HFSS-IE 6-4 entering coordinates 7-111
hiding 8-44 setting as grid type 11-26
moving to different surfaces 8-40 category
reassigning 8-40 traces 16-92
reprioritizing 8-41 center-point arcs 7-7
setting default values 8-47 Chamfer command
types of 8-1 3D modeler 7-87
Boundary changing material properties 10-27
Zoom to selected 8-2 characteristic impedance
boxes, drawing 7-21 and renormalized S-parameters 17-53
plotting 16-93
C specifying impedance lines 9-26
Zpi impedance 17-16
calculated expressions
Zpv impedance 17-16
plotting 16-120
Zvi impedance 17-16
calculation range
circles, drawing 7-15
setting for a cost function 15-35
circuit types, modeling 8-26
Index-3
circular polarization 17-68 cones, drawing 7-22
clean stop 14-78 Conj
cleaning up solutions 16-19 Calculator General Commands 16-150
clear linked data 13-19 connecting objects 7-76
clearing selections 7-108 constraints
clip planes 11-16 setting linear 15-81
cloning objects context section
before intersecting 7-82 reports 16-41
before subtracting 7-81 context-sensitive help 2-1
before uniting 7-79 convergence
closed objects 7-4 in solution process 17-4
cloud plots 16-130 on real frequency only 13-13
CmplxImag output variable 13-13
Calculator General Commands 16-150 viewing output variable 16-4
CmplxMag convergence criteria
Calculator General Commands 16-150 matrix 13-22
CmplxPeak maximum number of passes 13-11
Calculator General Commands 16-150 minimum converged passes 13-21
CmplxPhase minimum number of passes 13-21
Calculator General Commands 16-150 setting delta Energy 13-12
CmplxReal setting maximum delta S 13-12
Calculator General Commands 16-150 convergence data
color key for design variations 15-85
moving 16-127 mag margin 17-20
setting visibility 16-126 maximum delta Energy results 16-4
colors maximum delta S results 16-3
assigning to objects 7-60 number of passes completed 16-3
default for objects 7-60 output variable 16-4
default for outlines 7-60 phase margin 17-20
of field overlays 16-125 plotting 16-7
of highlighted objects 7-98 viewing 16-2
of selected objects 7-98 viewing the mag margin 16-5
setting background color 11-24 viewing the max delta (Mag S) 16-5
command properties 1-33 viewing the max delta (phase S) 16-6
command-line options 1-45 viewing the maximum delta frequency 16-6
Complex (Bistatic) RCS viewing the phase margin 16-5
equations for 16-97 coordinate systems
complex numbers creating face 7-129
in calculator registers 16-139 creating relative 7-127
complex propagation constant 17-11 default planes 7-130
complex weight 17-61 deleting 7-132
conductivity 17-141 enlarging axes 11-25
anisotropic 17-145 hiding axes 11-25
defining anisotropy tensors 10-11 modifying 7-130
Index-4
modifying view of axes 11-25 current coordinate system
operations affecting 7-130 about 7-126
overview 7-126 current flow direction 9-50
setting the working CS 7-127 current flow lines 8-26
showing axes 11-25 current sources
shrinking axes 11-25 assigning 9-50
specifying for matching boundaries 8-22 editing 9-50
coordinates scaling the magnitude 16-27
entering absolute 7-114 setting the phase 16-27
entering Cartesian 7-111 technical note 17-131
entering cylindrical 7-112 curvilinear elements 17-2
entering relative 7-114 custom arrays
entering spherical 7-113 geometry file setup 17-63
copy command setting up 16-179
for report and trace definitions 16-84 custom report templates
copying and pasting objects 7-61 creating 16-49
copying materials 10-31 customizing
copying to the clipboard 7-62 keyboard shortcuts 1-25
copyright notices 1-100 cylinders, drawing 7-20
corners cylindrical coordinates, entering 7-112
removing rounded 7-77
cost function D
adding 15-32
plotting results vs. iteration 15-88 data tables
setting a goal 15-32 exporting 3-25
setting the calculation range 15-35 importing 3-56
specifying solution quantity for 15-35 data tables, creating 16-64
viewing results vs. iteration 15-87 data types for convergence
count sweep setup 13-34
setting for sweep definitions 15-6 dataset expressions
covering faces 7-75 adding 3-94
covering lines 7-74 using 3-100
CPU time datasets
viewing for solution tasks 16-7 adding 3-94
vs. real time 16-7 and frequency-dependent materials 10-14
creating modifying 3-95
rcustom report templates 16-49 DC thickness
creating a User Defined Primitive 7-55 assigning 10-5
cross sevction Debeye’s model 17-148, 17-149
assigning to a line 7-11 Debye materials
cross-sections technical notes 17-149
creating 7-76 decade count sweep definitions 15-6
plotting spherical 17-57 decay factor
CTRL+A shortcut keys 7-94 antenna parameter 17-75
Index-5
de-embedding deleting objects 7-63
S-matrices 9-62 delta between markers
theory 17-54 in reports 16-67
deembedding delta E, See maximum delta Energy 13-12
technical notes 17-133 delta frequency, maximum 16-6
default impedance delta H 17-143
changing 16-69 delta S, See maximum delta S 13-12
default variable value density of grid 11-27
overriding for a parametric setup 15-8 dependent variables
defaults 7-60, 7-61 definition 3-86, 3-90, 3-96
assigned boundaries 17-110 derivative tuning 16-113
auto cover closed polylines 7-74 derivatives
auto cover polylines 7-74 calculating for variables. 13-29
background color 11-24 derived field quantities
basic field quantities 17-32 plotting 16-120
clone objects before intersecting 7-82 design variables
clone objects before subtracting 7-81 deleting 3-93
clone objects before uniting 7-79 See local variables 3-88
color of highlighted objects 7-98 design variations
color of selected objects 7-98 manually modifying points 15-7
field plot attributes 16-124 viewing all in a parametric setup 15-4
lighting 11-22 viewing solution data 15-85
mesh plot attributes 16-185 Design Xplorer
open Properties window after drawing objects 1- exporting setup 15-91
32 designs
rendering mode 11-13 in project tree 1-29
SAR settings 16-121 inserting in project 4-2, 6-3
setting face CS 7-130 setting up 4-1
setting for boundary values 8-47 desktop
setting for excitation values 8-47 menu bar 1-17
snap settings 7-120 overview 1-15
view orientation 11-20 status bar 1-27
degenerate modes 17-14 toolbars 1-19
Delete Last Operation command detaching edges 7-75
3D Modeler 7-64 detaching faces 7-75
deleting dielectric loss tangent 17-142
boundaries 8-39 defining anisotropy tensors 10-12
excitations 9-55 differential pairs
field overlay plots 16-134 admittance and impedance matrices 17-121
materials 10-32 computing 17-120
polyline segments 7-63 computing the S-matrix 17-122
projects 3-14 setting up 9-28
solution data 16-19 Directivity
start points and end points 7-63 definition 16-95
Index-6
directivity, peak 17-71 overview 7-4
discard below value 16-82 planes 7-31
Discrete frequency sweep 17-27 points 7-31
Discrete sweeps polylines 7-9
saving fields 13-38 rectangles 7-17
saving fields at single frequencies 13-40 regular polygons 7-17
specifying single frequencies 13-40 regular polyhedrons 7-22
disk space spheres 7-19
setting amount for warning 3-65 spiral using UDP 7-29
display types, of reports 16-51 spirals 7-27
distributed analysis 15-12 splines 7-8
licensing 14-12 straight line segments 7-5
distributed machine configurations three-point arcs 7-6
editing and creating 14-13 toruses 7-23
distribution criteria drawing plane 7-133
setting for statistical setups 15-62 Driven Modal solutions
Djordjevic-Sarkar Model input overview 17-29
use in Frequency Dependent materials 10-15 setting 4-3
domain decomposition Driven Terminal solutions
theory 17-47 overview 17-29
donuts, See toruses 7-23 setting 4-3
draft angles duplicates and parent objects 7-67
and sweeping objects 7-71 duplicating
draft types boundaries 8-43
and sweeping objects 7-71 excitions 8-43
drawing integration lines 9-27
region 7-34 duplicating objects
drawing a model along a line 7-68
overview 7-1 and mirroring 7-69
drawing commands around an axis 7-68
wrap 7-73 overview 7-67
drawing objects
bondwires 7-30 E
boxes 7-21
center-point arcs 7-7 edges
circles 7-15 creating objects from 7-83
cones 7-22 detaching 7-75
cross-sections 7-76 moving along normal’moving edges 7-79
cylinders 7-20 removing 7-75
ellipses 7-15 rounding 7-86
equation based curve 7-14 selecting all face 7-105
for post processing 7-33 selecting all object 7-105
helices 7-24 edges, selecting 7-104
non model 7-33 effective wavelength 17-18
Index-7
E-field moving to another surface 9-56
specifying direction of 9-48 scaling the magnitude 16-27
e-field setting default values 8-47
specifying direction of 9-26 setting the phase 16-27
E-fields types of 9-1
calculating on slave boundary 17-106 exponential count sweep definitions 15-6
mapping to other surfaces 17-104 export
relating master and slave boundary 8-24 from the calculator 16-165
Eigenmode Export command
setting Maximum delta Frequency 13-13 fields calculator
Eigenmode problems fields calculator
Freq input for Fields Calculator 16-148 Export command 16-165
Eigenmode solutions export results
overview 17-29 Ansys Mechanical 16-21
setting 4-3 exporting
viewing solution data 16-18 2D model files 3-22
eigenmodes 3D model files 3-22
minimum frequency to search for 13-9 animations 16-35
specifying number of 13-10 antenna parameters 16-181
ellipses, drawing 7-15 data tables 3-25
Emission test equivalent circuit data files 16-14
selecting quantity to plot 16-102 field overlay plots 16-133
energy error 13-12 materials to libraries 10-33
epsilon 17-18 matrix data 16-11
equation based surface maximum field data 16-181
drawing 7-18 W-element data 16-17
equations based curve, drawing 7-14 expressions
equivalent circuit export options 16-14 dataset 3-100
error tolerance defining 3-96
for interpolating sweeps 13-35 including in functions 3-95
Eval command intrinsic functions in 3-97
fields calculator 16-163 piecewise linear functions in 3-99
example projects using as cost function goal 15-37
listing 1-66 valid operators 3-97
Excitation extruding faces 7-77
Zoom to selected 9-3 eye measurements
excitation fields 17-11 range functions 16-104
excitations
and frequency dependence 17-109 F
deleting 9-55
duplicating with geometry 8-43 face coordinate system
editing properties of 9-54 about 7-126
hiding 8-44 creating 7-129
invalidated 9-56 creating automatically 7-130
Index-8
operations affecting 7-130 plotting quantities 16-95
faces reports 16-50
copying 7-82 vertical cross-sections 16-100
covering 7-75 far-field pattern 17-61
creating coordinate system on 7-129 Fast frequency sweep 17-26
creating face lists 7-103 Fast sweeps
creating objects from 7-82 modifying matrix data 16-9
detaching 7-75 saving fields 13-38
extruding 7-77 ferrite materials
intersections 7-83 adding to libraries 10-9
moving along a vector 7-78 properties of 10-9
moving along the normal 7-77 ferrites
removing 7-75 about 17-142
selecting 7-100 and delta H 17-143
selecting all object 7-101 and lande G 17-143
selecting behind 7-108 and magnetic saturation 17-142
selecting by name 7-102 assigning bias field 9-51
uncovering 7-75 assigning magnetic bias sources 9-51
families tab FFT on reports 16-105
reports dialog 16-42 field overlay plots 16-117, 16-120
far field default settings 16-134
definition 17-56 hiding color key 16-126
far field quantities modifying attributes 16-123
Antenna Params calculated 16-96 modifying colors of 16-125
Axial Ratio 16-95 modifying field quantities 16-122
Bistatic RCS 16-97 modifying phase 16-117
Complex (Bistatic) RCS 16-97 modifying plot scale 16-127
Directivity 16-95 moving color key 16-127
Gain 16-95 on lines 16-132
Monostatic RCS 16-97 SAR 17-34
Polarization Ratio 16-95 SAR settings 16-121
rE 16-95 scalar plots 16-121
Realized Gain 16-95 vector plots 16-122
far field region field pattern direction, specifying 17-116
definition for post processing 16-117, 16-171 field quantities
far fields defaults 17-32
and radiation boundaries 16-174 phase angle 16-150
calculation of 17-56 plotting basic 16-117
computing antenna parameters 16-179 plotting derived 16-120
computing max data 16-179 within tetrahedra 17-2
defining antenna arrays 16-177 field reports 16-50
horizontal cross-sections 16-100 field solutions
infinite spheres 16-176 linking from simulations 9-32
plotting on spherical cross-sections 17-57 saving at all frequency points 13-38
Index-9
saving for a parametric setup 15-74 rounding edges 7-86
saving for a sensitivity setup 15-75 filtering for object selection 7-95
saving for a statistical setup 15-74, 15-76 filtering materials 10-35
saving for a tuning analysis 15-74, 15-75 finite array patterns 17-61
saving for all Optimetrics setups 15-74 finite conductivity boundaries
saving for an optimization setup 15-74 and frequency dependence 17-109
fields assigning 8-17
saving at specific frequency points 13-40 conditions applied at 17-102
fields calculator guidelines for assigning 17-102
Eval command 16-163 finite element mesh, overview 17-2
Value command 16-163 finite element method, overview 17-2
Write command 16-164 fitting all objects in view 11-8
Fields Reporter options 3-74 fitting selections in view 11-8
file formats fixed variables
animated GIF 16-35 setting values during analyses 15-80
.asol 3-2 floquet ports
.avi 16-35 technical note 17-122
data table 16-12 free space lambda refinement 13-19, 13-20
.dsp 16-133 free space termination, and PMLs 17-99
Ensemble ver. 6+ 16-12 Freq variable 17-109
.gds 3-26 frequency 17-12
.hfss 3-2 frequency animations 16-32
HFSS ver. 6+ 16-12 frequency depedent data points
.hfssresults 3-2 adding for materials 10-23
HSpice 16-14 frequency dependent materials
.lib 16-14 Djordjevic-Sarkar model 10-15
Libra 16-12 frequency points
.m files 16-12 choosing for full-wave SPICE 13-42
Maxwell Spice 16-14 deleting from solution 13-41
Neutral Model Format 16-12 inserting in solution 13-41
nmf 16-12 frequency sweep
PSpice 16-14 range for full-wave SPICE 13-42
.sat 3-22 frequency sweeps
.sm2 3-22, 3-26 adding to designs 13-31
.sm3 3-22 and adaptive analysis 13-31
.sNp 16-12 and bypassing adaptive analysis 13-2, 13-12
.sp 16-14 and lumped RLC boundaries 17-107
.spc 16-14 error tolerance 13-35
Touchstone 16-12 Fast sweep overview 17-26, 17-27
files Interpolating sweep overview 17-28
auto-save 3-12 linear step frequencies 13-37
HFSS 3-2 maximum number of solutions 13-35
importing 3-26 minimum number of solutions 13-34
fillet command overview 17-26
Index-10
selecting type 13-32 setting weight of 15-32
setting points to solve 13-37 using an expression for 15-37
setting single frequencies 13-40 goal weight
settings for 13-31 setting 15-32
frequency-dependent materials gradient background colors 11-24
and lossy dielectrics 17-148, 17-149 grid settings
defining 10-14 choosing 11-26
FSS surfaces density 11-27
assigning reference surface for radiation boundar- dots or lines 11-26
ies 8-9, 8-12, 8-14 grid plane 11-27
full-wave SPICE spacing 11-27
choosing frequencies 13-42 style 11-26
guidelines for calculating maximum frequency type 11-26
13-43 visibility 11-27
guidelines for calculating step size 13-43 ground planes
functions lossy 17-109
defining 3-95 group delay
for traces 16-83 plotting 16-93
reserved names in HFSS 3-95 guide 1-55
selecting for a quantity 16-88
valid operators 3-97 H
healing
G stitch sheets 7-52
Gain helices, drawing 7-24
definition 16-95 helix
gain, peak 17-71 drawing segmented polygon with UDP 7-25
gain, peak realized 17-72 drawing segmented rectangular with UDP 7-26
Generate History command 7-90 help
geometry animations 16-33 about conventions used 2-3
Getting Started guides 1-53 Ansoft technical support 2-1
global coordinate system on context 2-1
about 7-126 on dialog boxes 2-1
global materials on menu commands 2-1
Ansoft 10-36 HFIE
user-defined 10-36 link to HFSS via radiation exchange 9-47
glossary Solution setup 6-6
of terms 17-1 HFSS
goal command-line options 1-45
setting a complex value 15-36 getting started 1-1
setting a real value 15-36 introduction 1-1
setting a single value 15-36 setting options 3-64
setting as variable dependent 15-37 HFSS Options dialog
setting for cost function 15-36 solving inside threshold 10-4
Index-11
HFSS-IE impedance boundaries
excitations 6-5 and frequency dependence 17-109
infinite ground plane boundaries 8-34 assigning 8-7
integral equation method 17-50 conditions applied at 17-96
hiding overview 17-96
boundaries 8-44 impedance boundary
color key 16-126 units 17-97
excitations 8-44 impedance lines
field overlay plots 16-133 See integration lines 9-26
objects 11-9 impedance matrix
selections 11-9 for differential pairs 17-121
hiding windows 1-15 method of calculation 17-54
High Performance Computing integration 14-20 plotting parameters 16-93
history impedance multiplier
viewing outline of merged objects 3-81 and symmetry planes 17-104
History operations setting 9-59
setting visualization 3-81 theory behind 17-17
history tree imperfect conductors, modeling 8-17
controlling view of objects 1-37, 1-42 importing
operations affecting CSs 7-130 data tables 3-56
operations affecting face CS 7-130 files 3-26
operations affecting relative CS 7-126 solution data 3-55
selecting object groups 7-97 imprint projection command 7-89
Unclassified folder 1-38 incident power 17-74
Upgrade Version 1-42 incident waves
holes assigning 9-32
moving 7-78 near fields calculation 17-57
resizing 7-77 scaling the magnitude 16-27
horizontal cross-sections 16-100 scaling the phase 16-27
HPC integration 14-20 inductors
HSpice files modeling lumped 8-26
exporting to 16-14 infinite arrays 17-61
defining custom 16-179
I defining regular 16-178
infinite ground plane boundaries 8-34
i_ boundary type 17-110 infinite sphere, defining 16-176
Imag infinity visualization 16-47
Calculator General Commands 16-150 initial displacement
impedance setting 15-57
and symmetry 17-104 initial mesh
changing 16-69 source from current or other design 13-16
characteristic, calculating 17-15 initial mesh settings 12-13
renormalizing S-matrices 9-60 initial mesh, reverting to 12-11
renormalizing S-parameters 17-53 in-plane movement mode 7-116
Index-12
input signal, for time domain reports 16-67 lambda refinement
input time signal duration 13-42 setting 13-19, 13-20
inserting lande G factor 17-143
line segments 7-13 layered impedance boundaries
inserting designs 4-2, 6-3 and frequency dependence 17-109
integral equation method assigning 8-31, 8-35
technical note 17-50 external vs. internal 17-107
integration lines impedance calculation 17-107
and multiple modes 9-27 impedance calculation formula 17-108
defining 9-26 surface roughness calculation 17-108
deleting 9-28 legacy HFSS projects
duplicating 9-27 opening 3-6
guidelines for defining 9-27 translation overview 3-6
modifying 9-28 legends in reporrts 16-48
reversing direction of 9-28 length of transmission line
swapping endpoints 9-28 adding to ports 9-62
Interpolating sweep 17-28 subtracting from ports 9-62
Interpolating sweeps length-based refinement
modifying matrix data 16-9 inside objects 12-4
interpolating sweeps on faces 12-3
error tolerance 13-35 libraries
intersecting faces 7-82 editing methods for user and system 10-36
intersecting objects 7-81 licensing
intrinsic functions 3-97 distributed analysis 14-12
introduction to HFSS 1-1 lighting 11-22
invalid excitations 9-56 line
isosurface display 16-130 assigning dimensions 7-11
Iterative matrix solver 17-22 line segments
inserting 7-13
J linear constraints
deleting 15-82
JEDEC 4-point bondwires 17-83 modifying 15-82
JEDEC 5-point bondwires 17-83 setting 15-81
joining objects 7-79 linear count sweep definitions 15-6
linear materials
K adding to libraries 10-8
properties of 10-8
keyboard shortcuts
linear polarization 17-67
custom 1-25
linear step frequencies 13-37
customizing 1-25
linear step sweep definitions 15-6
dialogue 1-25
lines
assigning cross section 7-11
L between grid points 11-26
lambda 17-18 converting to arcs 7-85
Index-13
converting to splines 7-85 non-uniform 17-133
covering 7-74 uniform 17-132
drawing center-point arc segments 7-7 magnetic bias sources
drawing straight segments 7-5 assigning to ferrites 9-51
drawing three-point arc segments 7-6 magnetic loss tangent 17-142
field plots on 16-132 defining anisotropy tensors 10-13
integration 9-26 magnetic saturation 17-142
value vs. distance plots 16-86 magnifying objects 11-6
link magnitude
Thermal to Ansys 16-21 setting maximum change for matrix entries 13-22
linking from simulations 9-32 magnitude margin 16-5
Linux Map Infinity Mode 16-47
Setting Up a Printer 1-4 markers
system requirements 1-4 adding to plot traces 16-81
local SAR delta between markers 16-67
calculation of 17-34 markers, point plot 16-131
local variables master boundaries
adding 3-88 assigning 8-22
units in definition 3-88 guidelines for assigning 17-104
log of solution tasks 16-7 matching boundaries
lossy ground planes 17-109 assigning 8-22
low-order solution basis 13-23 defining coordinate systems 17-105
Ludwig-3 17-68 guidelines for assigning 17-104
Lumped Port wizard 9-18 material browser
lumped ports accessing 10-1
for modal solutions 9-18 material characteristics
for terminal solutions 9-19 magnetic loss tangent 17-142
guidelines for assigning 17-118 permeability 17-140
overview 17-118 material properties
lumped RLC boundaries anisotropic 10-9
and frequency dependence 17-109 changing units of 10-9
and frequency sweeps 17-107 conductivity 17-141
assigning 8-26 defining frequency dependent 10-14
conditions applied at 17-107 defining variables for 10-14
overview 17-107 delta H 17-143
lumps, multiple 7-85 dielectric loss tangent 17-142
lande G 17-143
M magnetic loss tangent 17-142
magnetic saturation 17-142
M3DFS permeability 17-140
as source of field information 9-51 permittivity 17-141
MAFET Consortium 16-12 simple 10-9
mag margin 17-20 types of 10-9
magnetic bias using expressions for 10-26
Index-14
using functions for 10-26 setting 13-12
using variables for 10-14 viewing results 16-4
materials maximum delta frequency 16-6
about ferrites 17-142 maximum delta S
adding to library 10-8 setting 13-12
assigning to objects 10-1 viewing results 16-3, 16-4
copying, cloning 10-31 maximum far-field data
deleting 10-32 computing 16-179
exporting to libraries 10-33 overview 17-60
filtering 10-35 maximum near-field data
global 10-36 computing 16-175
modifying 10-28 overview 17-59
removing from libraries 10-32 maximum number of iterations
search by name 10-7 setting for a sensitivity analysis 15-53
search by property 10-7 setting for an optimization 15-30
solving inside an object 10-4 setting for statistical analysis 15-60
solving on object surface 10-4 maximum number of passes, setting 13-11
sorting 10-34 maximum number of solutions 13-35
user-defined database 10-36 maximum refinement
validating 10-30 solution setup options 13-21
viewing 10-28 Maximum refinement per pass
mathematical functions setting maximum 13-20
See functions 3-95 maximum step size
matrices, admittance setting for optimization analysis 15-42
computing from S-parameters 17-55 maximum variable
method of calculation 17-55 Optimetrics calculation of 15-39, 15-56
matrices, impedance maximum variable value
method of calculation 17-54 changing for all setups 15-64
relationship to S-parameters 17-53 overriding for a sensitivity setup 15-56
matrix convergence, setting 13-22 overriding for all optimization setups 15-40
matrix data overriding for all sensitivity setups 15-57
display format 16-10 overriding for an optimization setup 15-40
exporting 16-11 Maxwell Spice files
for design variations 15-85 exporting to 16-14
modifying frequencies 16-9 Measure Mode
renaming 16-14 distance between two points 7-123
reordering 16-14 Measure mode
viewing 16-9 position 7-123
matrix entries memory
selecting convergence criteria 13-22 setting hard limit 13-49
max delta (Mag S) 16-5 setting soft limit 13-48
max delta (phase S) 16-6 used during solution 16-7
max U 17-70 menu bar
maximum delta Energy overview 1-17
Index-15
menus meshing region 17-9
shortcut menus 1-22 Message window
Merged objects about 1-34
viewing outlines 3-81 displaying 1-34
Mesh new messages 1-35
statistics 16-17 Min and Max focus
mesh SNLP optimizer 15-42
color in plots 16-183 minimum frequency
for discrete frequency sweep 17-27 failure to solve 13-43
for fast frequency sweep 17-26 minimum frequency, setting 13-9
matching on master/slave boundaries 17-105 minimum number of converged passes, setting 13-21
plotting 16-183 minimum number of passes, setting 13-21
purpose of 17-2 minimum number of solutions 13-34
size vs. accuracy 17-4 minimum rise time 13-42
mesh generation minimum step size
and surface approximation settings 17-8 setting for optimization analysis 15-42
Copy geometric equivalent meshes options 15-77 minimum variable value
copy geometrically equivalent meshes 15-77 changing for all setups 15-64
process 17-5 Optimetrics calculation of 15-39, 15-56
reverting to initial mesh 12-11 overriding for a sensitivity setup 15-56
Mesh operations overriding for all optimization setups 15-40
model resolution 12-9 overriding for all sensitivity setups 15-57
mesh operations overriding for an optimization setup 15-40
applying without solving 12-12 mirroring objects 7-65
defining 12-1 Mixed order
initial mesh settings 12-13 noted used with domains 13-25
modifying surface approximation 12-7 mixed order
surface approximation overview 17-8 basis function 13-23
mesh plots basis functions 13-20
color of mesh 16-183 operation of 17-4
creating 16-183 mixed order basis 17-3
setting attributes 16-183 modal solutions
tetrahedra scale factor 16-183 assigning lumped ports 9-18
transparency 16-183 assigning wave ports 9-5
mesh refinement selecting 4-3
based on material-dependent wavelength 13-19, modal S-parameter reports 16-50
13-20 mode alignment
defining mesh operations 12-1 technical note 17-116
maximum refinement per pass 13-20 model analysis
on ports 17-12 Modeler menu command 7-36
setting lambda refinement 13-19, 13-20 model resoliution
without solving 12-12 mesh operations 12-9
meshing modes 17-13
detecting and addressing problems 17-86 and lumped ports 9-18
Index-16
conversion to nodes/terminals 17-77
degeneate 17-14 N
multiple at wave ports 9-5 named expressions
multiple modes and integration lines 9-27 plotting 16-120
port field display 16-115 near field
relationship to voltages or currents 17-78 definition 17-56
simultaneously propagating 17-77 near field region
modes, multiple definition for post processing 16-117, 16-171
for multi-conductor ports 17-14 near fields
See multiple modes 17-104 calculation of 17-56
simultaneously propagating 17-77 computing max parameters 16-175
modifying in Properties window 1-33 effect of radius on calculation 17-57
modifying objects 7-59 effect of radius on calculations 17-57
monitoring solutions 14-18 effect of radius on total or scallered fields 17-57
Monostatic RCS line setup 16-173
description 16-97 plotting on spherical cross-sections 17-57
movement mode plotting quantities 16-101
3D 7-117 radius in calculation 17-57
along x-axis 7-118 reports 16-50
along y-axis 7-119 sphere setup 16-172
along z-axis 7-119 new projects, creating 3-3
choosing 7-116 Next Behind command 7-108
in plane 7-116 nodes
out of plane 7-117 conversion from modes 17-77
Movement mode,3D 7-133 nominal design 15-1
moving faces non-adaptive solution
a specified distance 7-77 single frequency 17-25
along a vector 7-78 non-manifold
along the normal 7-77 mixed dimensionality 17-84
moving holes 7-78 non-model objects 7-33
moving objects 7-64 non-uniform magnetic bias 17-133
moving the cursor normalized distance
along x-axis 7-118 overview 16-86
along y-axis 7-119 notes
along z-axis 7-119 saving with project 3-63
in 3D space 7-117 number of passes
in plane 7-116 setting maximum 13-11
out of plane 7-117 setting minimum 13-21
selecting movement modes 7-116 setting minimum converged 13-21
moving windows 1-16 number of processors, setting 13-47
multiple modes number of time points 13-42
and lumped ports 9-17, 17-118
and symmetry planes 17-104
at wave ports 9-5
Index-17
offsetting objects 7-67
O ohms per square 17-97
object history old HFSS projects, opening 3-6
viewing outline of merged objects 3-81 online help
object orientation pdf file 2-1
changing 7-65 open objects 7-4
objects opening
associating with faces 7-129 existing projects 3-4
bondwires 7-30 field overlay plots 16-134
boxes 7-21 legacy HFSS projects 3-6
center-point arcs 7-7 recent projects 3-5
circles 7-15 operating systems
cones 7-22 Windows 1-2
converting polyline segments 7-85 Optimetrics
creating from faces 7-82 Copy geometric equivalent meshes 15-77
creating from intersections 7-81 overview 15-1
creating object lists 7-99 tuning a variable 15-70
cylinders 7-20 types of analyses 15-1
deleting parts on a plane 7-83 viewing analysis results 15-85
drawing relative to 7-127 viewing solution data 15-85
duplicates and parents 7-67 Optimization
ellipses 7-15 norms, L1, L2, and Max 15-45
equation based curve 7-14 optimization 15-15
for post processing 7-33 optimization analysis
helices 7-24 choosing variables to optimize 3-100
modifying 7-59 optional settings 15-24
non model 7-33 overview 15-15
planes 7-31 plotting cost vs. iteration results 15-88
points 7-31 setting up 15-24
polylines 7-9 viewing cost vs. iteration results 15-87
rectangles 7-17 optimization setups
regular polygons 7-17 adding 15-24
regular polyhedrons 7-22 adding a cost function 15-32
separating 7-85 procedure for defining 15-24
setting temperature 7-46 setting a goal 15-32
spheres 7-19 setting the max. iterations 15-30
spirals 7-27, 7-29 solving 14-1
splines 7-8 optimizers 15-15
straight lines 7-5 options
three-point arcs 7-6 setting in HFSS 3-64
toruses 7-23 orientation
types of 7-4 changing for objects 7-65
ways to select 7-93 creating new view directions 11-21
octave count sweep definitions 15-6 deleting view directions 11-21
Index-18
setting in view window 11-20 parametric sweep
orthographic view 11-23 distributed analysis 15-12
outer boundary type 17-110 parent objects
out-of-plane movement mode 7-117 and duplicates 7-67
output parameter pasting objects 7-61
adding to sensitivity setup 15-53 pattern search optimizer 15-15
plotting results 15-88 pausing a script 18-2
setting calculation range 15-55 peak directivity 17-71
specifying solution quantity for 15-54 peak gain 17-71
viewing results in table format 15-88 peak phasors
output variable and gap sources 17-34
viewing convergence 16-4 and incident waves 17-34
output variables calculating 17-33
deleting 16-112 peak realized gain 17-72
specifying 16-110 perfect conductors, modeling 8-5
perfect E boundaries
P and symmetry planes 17-103
assigning 8-5
panning the view 11-5 impedance multiplier for 17-17
parameterizing overview 17-96
See variables 3-85 perfect H boundaries
parameters and symmetry planes 17-103
assigning variables to 3-100 assigning 8-6
parametric analysis impedance multiplier for 17-17
setting up 15-4 perfectly matched layers, See PML boundaries 8-11
solution quantity results 15-11, 15-86 permeability 17-140
parametric setup anisotropic 17-144
adding 15-4 permittivity 17-141
overview 15-4 anisotropic 17-145
parametric setups perspective view 11-23
adding sweep definitions 15-4 phase
adding to a design 15-4 modifying for field overlays 16-117
plotting solution quantity results 15-87 setting for excitations 16-27
setting the calculation range 15-11 setting maximum change for matrix entries 13-22
solution quantity results 15-11, 15-86 phase angle
solving 14-1 in the calculator 16-150
solving before optimization 15-43 phase animations 16-31
solving before sensitivity analysis 15-57 phase constant 17-18
solving during optimization 15-44 phase delay
solving during sensitivity analyses 15-58, 15-68 defining for matching boundaries 8-24
specifying a solution setup 15-8 phase difference
specifying solution quantities for 15-9 defining for matching boundaries 8-24
using results for optimization 15-43 phase margin 16-5, 17-20
using results for sensitivity analysis 15-57 phasors
Index-19
peak 17-33 recalculating materials 8-15
RMS 17-33 specifying boundaries at 17-102
piecewise linear functions point of reference 7-116
dataset expressions in 3-100 point plots
for material properties 10-14 markers 16-131
using in expressions 3-99 points
planes measuring distance between 7-123
created with coordinate system 7-130 points, drawing 7-31
default 7-31 polar
drawing 7-31 coordinates on grid 11-26
setting the grid plane 11-27 setting as grid type 11-26
planes of periodicity, modeling 17-104 polar plots
planes of symmetry, modeling 8-21 creating 2D 16-58
play panel 16-34 creating 3D 16-60
plots creating radiation patterns 16-66
adding markers 16-81 creating Smith charts 16-61
convergence data 16-7 creating Smith contour charts 16-62
deleting field overlays 16-134 information displayed 16-60
distribution results for statistical analyses 15-90 polarization 17-67
hiding 16-133 circular 17-68
mesh 16-183 linear 17-67
modifying field overlays 16-123 Ludwig-3 17-68
modifying field quantities 16-122 spherical 17-68
named expressions 16-120 Polarization Ratio
on spherical cross-sections 17-57 definition 16-95
opening field overlays 16-134 polarization ratio 17-69
parametric solution quantity results 15-87 polygons, drawing 7-17
saving field overlays 16-133 polyhedrons, drawing 7-22
plotting polylines
basic quantities 16-117 assigning cross section 7-11
characteristic port impedances 16-93 center-point arcs 7-7
derived quantities 16-120 connecting between planes 7-76
group delay 16-93 connecting with sheet objects 7-76
on spherical cross-sections 17-57 converting segments 7-85
TDR impedance 16-93 converting to sheet objects 7-74
VSWR 16-93 covering 7-74
PML boundaries defining sweep paths 7-72
applications for 17-99 drawing 7-9
assigning 8-11 plotting value vs. distance 16-86
creating automatically 8-11 setting up near-field 16-173
creating manually 8-13 spline segments 7-8
guidelines for assigning 8-15 straight line segments 7-5
material tensors at 17-100 three-point arcs 7-6
modifying 8-15 port adapt options
Index-20
solution setup 13-26 specifying for 3D polar plots 16-61, 16-63
port field accuracy specifying for 3D rectangular plot 16-56, 16-58
overview 17-14 specifying for data tables 16-65
port field display specifying for radiation patterns 16-66
field display Printers
port fields 16-115 Linux 1-4
port impedance, plotting in time domain 16-67 Solaris 1-4
port solutions printing
overview 17-11 from help pdf 2-1
setting only 13-8 from HFSS 3-60
ports priority of boundaries, changing 8-41
and anisotropic materials 17-148 priority, changing simulation 14-77
and mesh refinement 17-12 problem region 17-9
assigning lumped ports 9-17 profile information
assigning wave ports 9-4 for design variations 15-85
internal to model 17-118 for Optimetrics solutions 15-86
multiple 17-14 viewing 16-7
scaling the magnitude 16-27 Progress window
setting the phase 16-27 monitoring solutions 14-18
use absorbing boundary 13-26 Project Manager window
ports only solutions overview 1-27
setting 13-8 showing 1-27
position project tree
measuring 7-123 auto expanding 1-28
post processing field overlays 16-117
overview of options 16-1 field plot folders 16-117
viewing convergence data 16-2 showing 1-27
viewing matrix data 16-9 project variables
viewing profile data 16-7 adding 3-85
post processing objects and material properties 10-14
points 7-31 deleting 3-88
power naming conventions 3-85
accepted 17-73 units in definition 3-85
incident 17-74 projection view 11-23
radiated 17-72 projects
power flow creating new 3-3
and perfect E symmetry planes 17-17 default names 3-1
and perfect H symmetry planes 17-17 deleting 3-14
Poynting vector managing 3-1
for peak phasors 17-34 opening existing 3-4
for RMS phasors 17-34 opening legacy HFSS 3-6
primary sweep opening recent 3-5
modifying the variable 16-86 renaming 3-11
specifying for 2D rectangular plots 16-53, 16-55 saving 3-10
Index-21
saving active 3-11 graphic for bistatic 16-98
saving automatically 3-12 Radar Cross Section (RCS)
saving copies 3-11 Bistatic RCS 16-97
saving new 3-10 definition 16-97
saving notes 3-63 diagram 16-98
propagation constant 17-11 Monostatic 16-97
and de-embedding 17-54 radiated fields
plotting 16-93 calculation of 17-56
viewing 17-17 post-processing capabilities 16-171
properties requires at least two directions for plot 17-58
report backgrounds 16-46 radiated power 17-72
Properties window radiation boundaries
modifying command properties 1-33 and far fields 16-174
set to open after drawing objects 1-32 assigning 8-8
properties window conditions applied at 17-98
material properties 10-27 FSS surfaces 8-9, 8-12, 8-14
PSpice files guidelines for assigning 17-98
exporting to 16-14 overview 17-98
Purge History command radiation efficiency 17-74
3D Modeler 7-90 radiation intensity, maximum 17-70
radiation patterns, creating 16-66
Q radius, on polar grid 11-26
RAM
Q factor 17-31 available to HFSS 13-48
viewing results 16-18 used during solution 16-7
quality factor 17-31 RAM requirements
quantities Windows 1-2
plotting far field 16-95 range functions
plotting field 16-94 eye measurements 16-104
plotting near field 16-101 RCS
plotting S-parameter 16-92 Bistatic RCS 16-97
quasi newton optimizer 15-15 Complex (Bistatic) 16-97
queued simulations diagram 16-98
removing 14-6 Monostatic 16-97
viewing 14-6 Radar Cross Section 16-97
queuing all simulations rE
Analysis Option 3-66 definition 16-95
Real
R Calculator General Commands 16-150
real frequency only convergence 13-13
Radar
Realized Gain
Radar Cross Section 16-97
definition 16-95
RCS for Plane Incident Waves 16-97
reassigning boundaries 8-40
radar cross section
reassigning excitations 9-56
Index-22
recording a script 18-1 report properties
rectangles, drawing 7-17 discard below value 16-82
rectangular contour plots Report setup options 3-83
creating 16-57 report templates
rectangular plots creating 16-49
creating 2D 16-52 report types, selecting 16-50
creating 3D 16-56 Reports
of parametric solution quantity results 15-87 apply FFT 16-105
rectangular stacked plots background properties 16-46
creating 2D 16-54 reports
reference point adding traces 16-77
moving relative to 7-116 context section 16-41
selecting 7-116 creating 16-37
setting 7-111 creating 2D polar plots 16-58
reflection-free termination, and PMLs 17-99 creating 2D rectangular plots 16-52
region creating 2D rectangular stacked plots 16-54
drawing 7-34 creating 3D polar plots 16-60
registers 16-139 creating 3D rectangular plots 16-56
regular arrays creating data tables 16-64
calculation of 17-62 creating radiation patterns 16-66
scan specification 17-63 creating rectangular contour plots 16-57
setting up 16-178 creating Smith charts 16-61
regular polygons, drawing 7-17 creating Smith contour charts 16-62
regular polyhedrons, drawing 7-22 display types 16-51
relative coordinate system finding delta between markers 16-67
about 7-126 modifying data in 16-44
creating 7-127 overview 16-37
operations affecting 7-126 plotting far-field quantities 16-95
relative coordinates, entering 7-114 plotting field quantities 16-94
relative permeability 17-140 plotting near-field quantities 16-101
defining anisotropy tensors 10-10 selecting a function 16-88
relative permittivity 17-141 specifying time or frequency domain 16-41, 16-
defining anisotropy tensors 10-11 52, 16-54, 16-58, 16-64
viewing 17-18 sweeping variables 16-86
remote analysis 14-7 types of 16-50
renaming value vs. distance 16-86
matrix data 16-14 reports dialog
renaming projects 3-11 familes tab 16-42
rendering objects reprioritizing
as shaded solids 11-13 boundaries 8-41
as wireframes 11-13 Reset command
setting default for 11-13 in Tuning dialog box 15-73
renormalizing S-matrices 9-60 resistive surfaces
reordering matrix data 16-14 modeling 8-7
Index-23
modeling layered structures 8-31, 8-35 active projects 3-11
resistors automatically 3-12
modeling lumped 8-26 new projects 3-10
resizing holes 7-77 saving copies 3-11
resizing objects 7-69 scalar field plots
resizing windows 1-16 cloud plots 16-130
re-solving a problem 14-79 creating 16-121
resonant frequency 17-30 isosurface display 16-130
resuming a script 18-2 transparency 16-131
rise time scalar operations 16-152
for time domain reports 16-67 scale
rise time, minimum 13-42 modifying for field overlays 16-127
RMS scaling
and radiated power 17-34 magnitude of excitations 16-27
RMS phasors objects 7-69
calculating 17-33 scaling a source
rotating transient network 16-30
and sweeping objects 7-72 scan angles
objects 7-64 defining for slave boundaries 8-24
the view 11-4 scattered fields
roughness, surface 17-108 effect of radius on near field calculation 17-57
rounded corners scattered wave
removing 7-77 graphic for RCS 16-98
RSM Service options scripts
setting 3-67 pausing 18-2
running a script 18-2 recording 18-1
resuming 18-2
S running 18-2
stop recording 18-2
SAR stopping execution of 18-3
calculating 17-34 secondary sweep
modifying settings 16-121 modifying the variable 16-86
saving specifying for 3D polar plots 16-61, 16-63
field overlay plots 16-133 seeding the mesh 17-6
tuned states 15-72 segmented polygon helix
saving fields drawing with UDP 7-25
at all frequency points 13-38 segmented rectangular helix
at specific frequency points 13-40 drawing with UDP 7-26
for a parametric setup 15-74 Select All command 7-94
for a sensitivity setup 15-75 Select All Visible command 7-94
for a statistical setup 15-74, 15-76 selecting
for a tuning analysis 15-74, 15-75 all face edges 7-105
for all Optimetrics setups 15-74 all object edges 7-105
saving projects 3-10 all object faces 7-101
Index-24
all visible objects setups, dependent solution 13-4
selecting setups, solution 13-1
all objects in design 7-94 sheet objects 7-4
clearing a selection 7-108 sheets
edges 7-104 thicken to make 3D objects 7-73
face behind 7-108 shortcut keys
faces 7-100 CTRL+A 7-94
faces by name 7-102 shortcut menus
filter by area 7-95 overview 1-22
multiple objects 7-94 Show Queued Simulations command
object behind 7-108 using 14-6
objects 7-93 showing
objects by area 7-95 selections 11-10
objects by name 7-95 some objects 11-10
vertices 7-106 showing windows 1-15
selecting objects shrinking objects 11-6
by variable 7-109 signal rise time 13-42
history tree groups 7-97 signals
sensitivity analysis minimum rise time 13-42
choosing variables to include 3-101 simulations
optional settings 15-52 changing priority of 14-77
setting up 15-52 monitoring 14-18
sensitivity setups re-solving 14-79
adding 15-52 running Optimetrics 14-1
adding an output parameter 15-53 starting 14-1
procedure for defining 15-52 stopping 14-78
setting initial displacement 15-57 single frequency points 13-40
setting the max. iterations 15-53 single frequency solution 17-25
separating bodies 7-85 method for computing 17-25
Sequential Mixed Integer NonLinear Programming single frequency solutions
(SMINLP) Optimizer 15-15 specifying 13-2, 13-12
Sequential Nonlinear Programming (SNLP) Optimiz- skin depth-based refinement
er optimizer 15-15 creation of layers 17-7
setting on faces 12-5
reference point 7-111 slave boundaries
termpature for objects 7-46 and frequency dependence 17-109
setting object color 7-60 assigning 8-24
setting object transparency 7-61 guidelines for assigning 17-104
setting outline color 7-60 S-matrices
setting the drawing plane 7-133 de-embedding 9-62
setting the movement mode 7-133 renormalizing 9-60
setting up designs 4-1 S-matrix
setting up projects 4-1 for differential signals 17-122
setup link dialog 9-53 smetal boundary type 17-110
Index-25
Smith charts, creating 16-61, 16-62 maximum delta S per pass 13-12
snap settings maximum number of passes 13-11
choosing 7-120 maximum refinement per pass 13-20
guidelines for 7-121 memory limit 13-49
modes 7-120 minimum frequency 13-9
setting default 7-120 minimum number of converged passes 13-21
SNLP optimizer minimum number of passes 13-21
setting Min and Max focus 15-42 number of eigenmodes 13-10
Solaris number of processors 13-47
Setting Up a Printer 1-4 setting up adaptive analyses 13-11
solid objects 7-4 solution frequency 13-7
solution data solving ports only 13-8
deleting 16-19 solution settings, specifying 13-1
for design variations 15-85 solution settings, specifying dependent 13-4
importing 3-55 solution setup
viewing 16-2 data types for convergence 13-34
viewing convergence data 16-2 port adapt options 13-26
viewing eigenmode 16-18 solution setups
solution frequency adding 13-1
and Fast sweeps 13-7 adding dependent 13-4
setting 13-7 choosing for a parametric analysis 15-8
solution process solution type
overview 17-5 overview 17-29
tetrahedra used during 16-7 setting 4-3
viewing memory used during 16-7 solutions
viewing profile data 16-7 after modifying the model 14-79
viewing tasks performed 16-7 at single frequency 17-25
solution quantity changing priority of 14-77
calculation range for optimization 15-35 monitoring 14-18
calculation range for parametric setups 15-11 re-solving 14-79
calculation range for sensitivity 15-55 starting 14-1
calculation range for statistical 15-62 stopping 14-78
plotting parametric setup results 15-87 Solutions window
specifying for cost function 15-35 displaying 14-18
specifying for output parameter 15-54 solver domains
specifying for parametric setups 15-9 theory 17-47
specifying for statistical setups 15-61 solving 14-1
solution settings batch solution 1-45
adding frequency sweeps 13-31 inside an object 10-4
available memory 13-48 on surface 10-4
convergence on real frequency 13-13 parametric setup before optimization 15-43
lambda refinement 13-19, 13-20 parametric setup before sensitivity analysis 15-57
matrix convergence 13-22 parametric setup during optimization 15-44
maximum delta Energy per pass 13-12 parametric setup during sensitivity analysis 15-
Index-26
58, 15-68 plotting distribution results 15-90
solving remotely 14-7 setting up 15-60
sorting materials 10-34 viewing distribution results 15-89
spacing between grid points 11-27 statistical setups
S-parameters adding 15-60
de-embedding 17-54 procedure for defining 15-60
plotting quantities 16-92 setting the max. iterations 15-60
renormalized 17-53 specifying solution quantities for 15-61
specific absorption rate status bar
see SAR 16-121 overview 1-27
spheres step size
drawing 7-19 setting constraints for optimization 15-42
plotting value vs. distance 16-87 setting for sweep definitions 15-6
setting up infinite 16-176 step size between frequencies 13-37
setting up near-field 16-172 stitch sheets command 7-52
spherical coordinates, entering 7-113 stopping a script 18-3
spherical cross-sections 17-57 stopping an analysis 14-78
spherical polar 17-68 stopping criteria
spinning the view 11-4 matrix convergence 13-22
spirals maximum delta Energy 13-12
drawing 7-27, 7-29 maximum delta S 13-12
splines maximum number of passes 13-11
converting to straight lines 7-85 minimum number of converged passes 13-21
drawing 7-8 minimum number of passes 13-21
splitting objects on a plane 7-83 stopping criteria for optimization
square (unit of) 17-97 maximum number of iterations 15-30
stack 16-138 stopping criteria for sensitivity analysis
stack commands max. iterations 15-53
clear 16-140 stopping frequency 13-37
exch 16-140 stopping script recording 18-2
loading into 16-141 streamline
performing operations on 16-148 Fields Reporter Options tab 3-74
pop 16-140 plot attribute settings 16-123
push 16-140 plot selection 16-117
rldn 16-140 subtracting objects 7-80
rlup 16-140 surface approximation
undo 16-140 guidelines for setting 17-9
starting frequency 13-37 modifying settings 12-7
starting variable value overview 17-8
overriding for optimizations 15-39 surface roughness 17-108
overriding for sensitivity 15-55 surface visualization
overriding for statistical 15-67 setting 11-14
statistical analysis surfaces
choosing variables to include 3-102 covering 7-75
Index-27
creating face lists 7-103 TDR Options dialog box 16-67
detaching 7-75 temperature
uncovering 7-75 setting for objects 7-46
sweep definitions templates for reports
See variable sweep definitions 15-4 creating 16-49
sweep variables in reports tensor coordinate system 17-132
modifying values 16-86 terminal
normalized distance 16-86 conversion from modes 17-77
normalized line 16-86 terminal lines
spherical coordinates 16-87 and differential pairs 9-28
sweeping terminal solutions
faces along normal 7-73 assigning lumped ports 9-19
sweeping objects assigning wave ports 9-8
along a path 7-72 setting 4-3
along a vector 7-71 terminal S-parameter reports 16-50
and draft angles 7-71 terminals
and twisting 7-72 scaling the magnitude 16-27
around an axis 7-70 setting a complex impedance 16-27
draft types 7-71 Test Machines
overview 7-70 Distributed Analysis Machines dialog 14-16
symmetry boundaries tetrahedra
and multiple modes 17-104 color in plots 16-184
assigning 8-21 display options 16-184
guidelines for assigning 17-103 field quantities within 17-2
overview 17-103 scale factor in plot 16-183
symmetry planes setting number added each pass 13-20
and impedance 17-104 used during solution 16-7
and multiple modes 17-104 thermal feedback from ANSYS 13-27
guidelines for modeling 17-103 thermal link
Perfect E vs. Perfect H 17-103 ANSYS Workbench 12 14-80
symmetry planes, modeling 8-21 thermal link to Ansys Mechanical 16-21
Sync # column 15-6 thermal quadratic parameters 10-25
synchronizing sweep definitions 15-6 theta, on polar grid 11-26
system material libraries 10-36 thicken sheets 7-73
system requirements three-point arcs 7-6
Windows 1-2 time
real vs. CPU 16-7
T viewing for solution tasks 16-7
time domain
TDR Impedance specifying for report 16-67
changing default value 16-69 technical notes 5-2, 5-6, 5-8, 5-10, 17-36, 17-37,
TDR impedance 17-38, 17-39, 17-44, 17-45
plotting 16-93 time profile
TDR impedance, plotting 16-67 for transcient solutions 5-5
Index-28
time steps per rise time 13-42 history tree 1-38
T-junction Getting Started guide 1-53 uncovering faces 7-75
toolbars uniform magnetic bias 17-132
overview 1-19 uniting objects 7-79
toruses, drawing 7-23 units
total fields as part of variable definitions 3-85
radius and near fields calculation 17-57 of impedance boundaries 17-97
Traces setting for design 7-3
display properties 16-79 Upgrade Version
traces History tree 1-42
adding characteristics 16-83 User Defined Primitives 7-29, 7-55
adding to reports 16-77 user defined primitives
categories 16-92 customization 7-57
copy and paste definitions 16-84 user interface
removing 16-84 overview 1-15
Traces dialog box 16-37 user material libraries 10-36
trademark notices 1-100
transcient solutions V
technical notes 5-2, 5-6, 5-8, 5-10, 17-36, 17-37,
17-38, 17-39, 17-44, 17-45 validating materials 10-30
translating legacy projects 3-6 validation check 3-19
transparency Value command
assigning to objects 7-61 fields calculator 16-163
default for objects 7-61 value vs. distance plots 16-86
in scalar field plots 16-131 variable
of mesh plots 16-183 for output convergence 13-13
traveling waves selecting objects by 7-109
at ports 17-11 variable sweep definitions
tuning adding to parametric setups 15-4
choosing variables to tune 3-102 manually modifying 15-7
Tuning Reports command 16-113 overview 15-4
tuning analysis setting values to solve 15-6
resetting variable values after 15-73 synchronizing 15-6
reverting to a state 15-73 tracking changes to 15-7
saving a state 15-72 viewing all design variations 15-4
setting up 15-70 variable-dependent goal 15-37
twisting objects variables
while sweeping 7-72 add array 3-91
adding local variables 3-88
adding project variables 3-85
U and object parameters 7-4
UDPPrimitiveTypeInfo assigning to material properties 10-14
data structure 7-56 assigning to parameters 3-100
Unclassified folder choosing to optimize 3-100
Index-29
choosing to tune 3-102 orientation 11-20
dataset expressions in 3-100 pan 11-5
defining sweep definitions 15-4 projection 11-23
deleting from design 3-93 rotate 11-4
deleting from project 3-88 spin 11-4
dependent 3-86, 3-90, 3-96 view direction 11-20
excluding from Optimetrics analyses 15-79 zoom 11-6
including in functions 3-95 zoom on rectangle 11-6
including in sensitivity analysis 3-101 visibility
including in statistical analysis 3-102 hiding objects 11-9
material properties 10-14 of color key 16-126
min. and max values for optimization 15-39 of field overlay plots 16-133
min. and max values for sensitivity analysis 15-56 of mesh on field plots 16-130
output 16-110 showing objects 11-10
overriding default value for a parametric setup 15- visualization options
8 for boundaries 8-44
overview 3-85 for excitations 8-44
predefined in HFSS 3-95 Visualize hiistory of objects
setting default value 3-86 Setting option for 3-81
setting distribution criteria 15-62 voltage differentials
setting fixed values 15-80 and perfect E symmetry planes 17-17
setting range of values 15-56 and perfect H symmetry planes 17-17
setting range of values for optimization 15-39 voltage sources
tuning 15-70 assigning 9-48
types in HFSS 3-85 editing 9-48
updating to optimized values 15-44 setting the phase 16-27
.vbs file format 18-1 technical note 17-131
VBScript voltage standing wave ratio
.vbs file format 18-1 plotting 16-93
vector field plots
creating 16-122 W
modifying arrows 16-129
vector operations 16-157 Wave Port wizard 9-5
vertex, selecting 7-106 wave ports
vertical cross-sections 16-100 analytic port types 17-117
vertices, selecting 7-106 for modal solutions 9-5
video drivers for terminal solutions 9-8
recommended 1-2 overview 17-115
view direction 11-20 specifying multiple modes 9-5
view options W-element
background color 11-24 warning message 17-79
fit all in view 11-8 W-element data
lighting 11-22 exporting 16-17
modifying 11-1 windows
Index-30
moving and resizing 1-16
show or hide 1-15
wireframe objects 11-13
working coordinate system
about 7-126
selecting 7-127
wrap objects command 7-73
Write command
fields calculator 16-164
X
XY drawing plane 7-133
Y
Y-parameters, plotting 16-93
Z
zero order basis functions 17-3
Zo
changing default impedance 16-69
Zoom
to selected boundary 8-2
to selected excitation 9-3
zooming
in and out 11-6
on rectangular area 11-6
Z-parameters, plotting 16-93
Zpi
definition of 17-16
Zpv
definition of 17-16
Zvi
definition of 17-16
Index-31
Index-32