Icepak Updates

Highlights

• 2-way thermal coupling to HFSS, Q3D, and Maxwell design types

• 1-way thermal coupling to SIwave DC IR solver in AEDT

• Import .tzr archive from Classic Icepak interface

• 2D & 3D profile boundary conditions using datasets

• Workflow Improvements

‐ Solution setup streamlined

‐ Rotated PCB components

‐ MCAD fan objects can be simplified into Icepak primitives

• Mesher Improvements

‐ General mesh speed and quality improvements

‐ Allow for simplified stair-step meshing

‐ Control over uniform mesh sizing

‐ Added the capability to enforce 2D cut cell meshing in a specified coordinate direction

• Classic Icepak Enhancements

‐ Job submission to supported schedulers – within and across Windows/Linux platforms

‐ Ability to export unencrypted ECXML files

‐ Monte Carlo radiation model added (BETA)

‐ Per Object meshing controls & Mesh re-use (BETA)

NEW

NEW

NEW

NEW

2-Way Electro-Thermal Coupling

• Valid for HFSS, Q3D, and Maxwell design types

• Utilizes thermal modifier for materials and temperature feedback in electromagnetic design

• New 2-way Coupling controller in Icepak design

3

HFSS Design of a High Power Waveguide Load

• Allows for additional Icepak iterations between material updates

Maxwell Design of Planar Transformer

SIwave DCIR Workflow Migrated to AEDT

• DCIR solver now available within AEDT

• 1-way connection to Icepak for electro-thermal analysis

• Delivers automation capabilities to DCIR workflow

Workflow Wizard(Beta)

Power Density

Voltage

Temperature

Import Archived Projects from Classic Icepak Interface

• File > Open → Select files of type…‐ Icepak Classic Project (*.tzr)

• List of translator limitations in online help

Workflow Improvements

6

• Dataset-based boundary conditions‐ 1D for Temperature-dependent

‐ 2D & 3D for non-uniform

➢ Power, Temp, Pressure, Velocities, Heat Flux, Heat Transfer Coefficient

• Streamlined Solution Setup – Common options can be set in one location‐ Temperature/Flow selections

‐ Gravity on/off

NEW

Workflow Improvements

• PCB Objects created on rotated Coordinate Systems have axis aligned mesh

• MCAD Fan Object simplification‐ Simplistic method to convert complex MCAD fan object to Icepak primitive

Mesher Improvements

8

• General Mesh improvements‐ Mesh loading – up to 13X faster

‐ Memory usage – up to 80% reduction

‐ Quality computation – up to 6X faster

• Stair-step (cartesian) Meshing

• SmartSlider‐ Continuing improvements for coarse levels 1 & 2

Level 1

Level 2

Mesh Settings: Uniform Mesh Parameter Options

• For 3D or 2D MLM, option to control initial mesh size when uniform mesh params is enabled‐ Use average: Initial size using computed average of X, Y, Z max element sizes

‐ Keep XYZ max sizes: Initial size using X, Y, Z max element sizes in respective coordinate direction

Use average: 4 levels to get 2-cell across gap1.7M cells

Keep XYZ max sizes:1 level to get 2-cell across gap30K cells

2.5D MLM Meshing

• 2D MLM is not used if assembly contain non-extrudable shapes (reverts to 3D cut cell)

• For PCB/CAD configurations, 2D MLM can be enforced if an “extrusion” direction is specified

• If “Auto”, 3D cut cell is used when the 2D direction cannot be determined from the shapes

Assembly boundary intersecting CADenclosure meshed using 2.5D MLM

Classic Icepak Enhancements

• Job submission to supported schedulers – within and across Windows/Linux platforms‐ Supports LSF, PBSPro, and SGE

‐ Supports cross-platform job submission →Windows to Linux

• Export Un-encrypted ECXML format‐ Can programmatically create models for import into Icepak

‐ Same object/setup/mesh compatibility as encrypted ECXML

11

Thank You!

Appendix

Launching FLUENT using Scheduler

• Scheduler support FLUENT (similar to Fluent launcher)

• On Windows‐ Microsoft Computer

Cluster pack

‐ Remote Linux schedulers –LSF, SGE and PBSPro

• On Linux‐ LSF, SGE and PBSPro

MS Job Scheduler Remote Linux

Remote Linux Nodes

• Icepak and FLUENT host processes running on Windows machine, FLUENT nodes spawn on remote cluster nodes

• Remote solver path – Path to FLUENT on linux cluster

• Remote working directory – Local working directory on linux cluster

• Remote cluster head node – Cluster head node name (where the rest of compute nodes will be spawn from)

• Remote spawn command – Command to start compute node0 on head node‐ RSH, SSH or plink (recommended)

• Copy to remote command – Command to copy local files to remote working directory

Remote Linux Nodes (Cont’d)

• LSF Option‐ LSF queue – specify queue name for job to

wait until dispatched

• SGE Options‐ SGE qmaster – specify SGE host (if different

from cluster head node)

‐ SGE queue – specify SGE queue name for job to wait until dispatched

‐ SGE pe – specify the parallel environment settings

• PBSPro‐ N/A

LSF option

SGE Options

Scheduler on Linux

• Assume network path accessible from cluster‐ Remote Icepak ROOT – network path to where

Icepak is installed

‐ Remote solve path – network path to where FLUENT is installed

• LSF and SGE options similar to Remote Linux node setup

• PBSPro has option to specify PBS submission host

Scheduler configuration on Linux

PBSPro option

Submission options (Solve dialog)

• LSF option removed from “Script file”

• Script uses setup in Parallel Settings

• Submission options remain available but should not combined with Scheduler

Mesh reuse (aka PreMeshed Assembly)

• Reuse meshes already generated for an assembly from another project or an external mesher

• Mesh can be reused‐ Only in assembly

‐ When geometries are identical (object names, types, etc. can be different)

• When mesh reuse is enabled, per-assembly mesh controls/settings are disabled

Mesh reuse option

Mesh reuse approach

• Only mesh cells from external meshes are preserved

• Face grouping (zones etc.) are discarded

• Mesh cells from external meshes are post-processed to correspond to grid input and grid mapping of current assembly‐ No new cells are generated in the process

‐ Shape in current assembly can be made hollow even though external mesh for that shape exists (vice versa not supported)

‐ Priority can be different and overlapped mesh cells sorted according to current priority setting

Mesh reuse example

• 5 boundary layers on internal surface of cylinder

• Tetrahedra used to fill other regions

FLUENT mesh in Icepak

Mesh in FLUENT mesher application

Mesh reuse example (Cont’d)

Premeshed as solid

Imported as hollowNote: vice versa not supported since no new cells are generated.

Mesh reuse example (Cont’d)

Imported mesh will be sorted automatically to objects based on current object priorities

Increasingpriority

Mesh reuse example (Cont’d)

• Multiple assemblies referring to same existing mesh

• Translation automatically determined by mesher

• No rotation support (yet)

PreMeshed mesh formats

• Fluent mesh (.msh) • Icepak mesh (grid_output)• Simple node/cell connectivity*

Node/Cell connectivity format

• Simple text-based format

Number of nodes, faces and cells

Cell connectivitynn n1 n2 n3 … n_nn

Node definition

7 0 4Nodes:1 4.36548e-04 6.23864e-04 2.83204e-042 4.32944e-04 6.24124e-04 2.87566e-043 4.29784e-04 6.23864e-04 2.91673e-044 4.32988e-04 6.25934e-04 2.88711e-045 4.35890e-04 6.23864e-04 2.90695e-046 4.36422e-04 6.19886e-04 2.86436e-047 4.32544e-04 6.19886e-04 2.92359e-04Cells:4 1 2 3 4 4 4 3 1 5 4 3 6 1 5 5 6 1 2 7 3

PerObject Mesh (BETA)

• PerObject mesh controls‐ Mesh reuse

➢ Reuse externally generated mesh on object based on specified local coordinates system

‐ Mesh separate

➢ Mesh object separately in specified local coordinates system

• Enable via env var‐ ICEPAK_PEROBJECT_MESH

PerObject Mesh Reuse

• Perobject mesh reuse‐ Add – add new perobject mesh

configuration entry

‐ Object – select object(s)

‐ Mesh files – select existing mesh

• Valid mesh format similar to assembly mesh reuse‐ Icepak mesh (grid_output)

‐ FLUENT mesh (*.msh)

• Only mesh inside objects are used, everything outside is ignored Add entry

PerObject Mesh Reuse (Cont’d)

Local coordinate of cylinder• Show – display local axes• Copy – copy orientation from

other CADs

PerObject Mesh Reuse (Cont’d)

Mesh is non-conformal between cylinder and cabinet

PerObject Mesh Separately

3 CAD PCBs• 25 degree inclined• 120 degree

between PCBs• 3 layer board• Local Z points in

thickness direction

PerObject Mesh Separately (Cont’d)

• Enable “Mesh object separately”• Objects on each PCB have same local

coordinates (block.1, M1_B, M2_T), etc.• 2.5D meshing is used if “Enforce 2D cut cell

for all objects” is enabled• 2.5D direction follows local Z direction,

regardless of assembly 2.5D direction• Mesh always generated in local coordinates

system

PerObject Mesh Separately (Cont’d)

Mesh is shape-aligned for each PCB

2.5D in local coordinates meshes PCB layers optimallyPCBs are non-conformal with Cabinet

Monte Carlo radiation model (BETA)

• Monte Carlo radiation model‐ Recommended model for solids

that participate in radiation

‐ Model parameters set in “Options”

• Monte Carlo is BETA‐ ICEPAK_ENABLE_MONTE_CARLO

• Does not work if there are assemblies in model

Participating materials

• Transparent and participating properties associated with material specifications

• “Radiation behavior” ‐ Opaque or Participate – solid/fluid materials‐ Opaque or Semi transparent – surface materials

• Edit to specify radiative properties‐ All fluids are participating by default‐ Disable radiation option removed in 2019 R1

• Radiation behavior for solids is BETA‐ ICEPAK_ENABLE_PARTICIPATING_SOLIDS

Participating objects

• Objects with participating material will inherit correct radiation behavior

• Object surface must be assigned transparent material

Sample problem

• Bulb inside a can‐ Bulb surface temperature – 2000K

‐ Polycarbonate (JSME) lens

➢ Absorption/scattering coefficients – 0 (i.e., transparent material)

➢ Refractive index – 1.0

➢ Diffuse fraction – 1.0 (in surface material definition)

Polycarbonate lens

Sample problem (Cont’d)

Opaque case Transparent case

Unencrypted ECXML

• Unencrypted ECXML allows import/export of text-based XML file for supported objects and BCs‐ Uncheck “Encrypt data” when exporting