Training

Copyright 2009 Altair Engineering, Inc. Proprietary and Confidential. All rights reserved.Copyright 2009 Altair Engineering, Inc. Proprietary and Confidential. All rights reserved.

AcuSolve/AcuConsole Introductory Training Course

Copyright 2009 Altair Engineering, Inc. Proprietary and Confidential. All rights reserved.

Table of Contents

Sec. No. Description Slide No.

1 Introduction A.5

2 AcuSolve Overview A.9

3 AcuSolve Features A.15

4 AcuConsole Overview A.25

5 Demo Problem Pipe Flow A.31

6 Acusim Programs A.45

7 Workshop1 Conjugate Heat Transfer A.57

8 Solver Commands A.89

9 Workshop2 Blower (Using Reference Frame) A.117

10 Input File Review (Workshop2) A.135


Table of Contents (Continued)


11 Workshop3 Blower2 (Using Sliding Mesh) A.145

12 Post Processing A.159

13 Program Options A.171

14 Workshop4 Compressible Nozzle A.179

15 AcuSolve Mesh Files A.199

16 Boundary Conditions A.205

17 Workshop5 Rigid Body Motion A.215

18 Solution Strategy A.233

19 Workshop6 Flexible Ring (P-FSI) A.247

20 Restarting Simulations A.283


Table of Contents (Continued)


21 Heat Transfer Modeling A.293

22 Workshop7 Natural Convection A.315

23 Turbulence Modeling A.343

24 Workshop8 Honey in Tea (Species Concentration) A.355

25 Working with Expressions and Units A.371

26 Setting User Preferences A.379


Introduction


IntroductionIntroduction

ACUSIM Software, Inc. acquired by Altair Engineering, Inc. January 2011

AcuSolve development mission:

Develop a fast, robust, and accurate finite element based Computational Fluid

Dynamics (CFD) solver

First AcuSolve customer established in 1997

Current AcuSolve customers in the United States, Canada, Mexico, India, Japan, Current AcuSolve customers in the United States, Canada, Mexico, India, Japan,

England, France, Germany, Brazil, Singapore, China

AcuConsole - The Pre-Processor for AcuSolve

Support

E-Mail

[email protected]

Phone (USA based, country code +1)

650-988-9700 - ext 2

A.6


Altair HyperWorks : Licensing System

HWU Pool

Licensing system based on HWUs not per product

The use of units is spread out

All HyperWorks software shares the pool of HWUs

A.7


A.8


AcuSolve Overview


AcuSolve OverviewAcuSolve Overview

A general-purpose incompressible and weakly compressible flow solver

Uses a finite element formulation

Good to Mach number 0.7-0.8

Enables rapid, quality solutions without iterating on solution procedures

Robustness, Speed, Accuracy, Functionality

Provides engineers and scientists with seamless integration into design and analysis Provides engineers and scientists with seamless integration into design and analysis

applications

A.10



Flow solver

CAD Package

Pre-Processor

AcuConsole

Third Party Mesh Generator and/or Input File Writer

A.11

Analysis

AcuSolveDirect Coupling Fluid/Structure

Interaction

Structural Solver

Acoustic Analysis

CAA Output

Translators / Direct Readers

Third Party Post-Processor



Markets currently using AcuSolve:

Automotive

Electronic cooling

Chemical mixing

Home Appliances

Medical and medical equipment

Oil/Gas and offshore platforms

Boat design

Train aerodynamics

Universities

National labs

Renewable Energy

Etc. . .

A.12

Particle Paths from AcuTrace



Why choose AcuSolve?

AcuSolves differentiation via Finite Elements:

Robustness

Relatively insensitive to element topology and mesh quality

Superior performance on anisotropic tetrahedral meshes

Most problems solved on first attempt

Speed Speed

Scalable parallel on shared and distributed memory parallel machines

Customers have solved 2,000,000 elements on a 2 GB memory Windows PC and over

400,000,000 on large Linux clusters

A.13



AcuSolves differentiation via Finite Elements:

Accuracy

Highly accurate in space and time while globally and locally conservative

All variables, including turbulence are discretized to second order accuracy

AcuSolve has demonstrated up to fourth order accuracy on some specific cases

(turbulent channel flow)

Functionality

Rich set of features Rich set of features

Robustness, Speed, Accuracy, Functionality

Better Technology.Better Results!

A. 14


AcuSolve Features


AcuSolve FeaturesAcuSolve Features

Conservation equation systems in 3D

Incompressible Stokes and Incompressible / Weakly-Compressible Navier-Stokes

equations

Thermal analysis and conjugate heat transfer

Multi-layered thermal shell

Multi-species transport equations

RadiationRadiation

Gray body enclosure radiation

View factor computation

Solar radiation

Computational Aero-Acoustic (CAA)

Pseudo-compressibility

CAA output/interface support

A.16

Vehicle Cabin Heating / Cooling



Turbulence Models

One-equation Spalart-Allmaras RANS model

Standard Wall Function no lowerbound y+ limit

Low-Re formulation

Smagorinsky and dynamic subgrid LES models

Hybrid RANS/LES model

k- and SST under development

Arbitrary Lagrange Eulerian (ALE) Mesh Motion

Flexible mesh movement

Free surface modeling

Sliding mesh

Rigid body motion

Fluid/Structure Interaction (FSI)

Modal Analysis P-FSI

External Code DC-FSI

A.17

Rigid Body Motion

with Free Surface



Rotating Flows

Multiple frames of reference

Rotating/Sliding mesh

Component Technology

Fan component

Heat exchanger component

Rich Set of Material Options

Newtonian and non-Newtonian fluids

Porous media

Melting and heat of formation

User-defined function

A.18

Sliding Mesh - Train Passing

Fixed Railcar



Full Set of Boundary Conditions

Dirichlet and Neumann boundary conditions

Periodic and axisymmetric conditions

Thermal periodic condition

Integrated surface boundary condition

General two-point constraint

Experimental data imposition

Dynamic BC activation

Non-reflecting BC

User-defined function

External Code Surface

A.19



Highly Effective Solver Technology

Fast and robust iterative linear solvers

A novel and highly efficient iterative solver for the fully coupled pressure/velocity equation

system

A companion fully coupled temperature/flow iterative equation solver

Fully parallel on shared/distributed memory machines, transparent to user

Solution StrategySolution Strategy

Fast steady state solver

Second-order time-accurate transient analysis

No CFL based stability limit

Automatic time-stepping algorithms

A.20



Advanced finite element technology

Galerkin/Least-Squares finite element method

Equal-order (nodal) interpolation for all solution fields, including pressure

Unstructured mesh:

4-node tetrahedron

5-node pyramid

6-node wedge

8-node brick 8-node brick

10-node tetrahedron

Particle Tracer

Laminar

Turbulent diffusion

Parallel computation

A.21



Platform OSHP HP-UX 11.0

HPIPF HP-UX 11.0 (Itanium)

Supported Platforms

LINUX Redhat 7.1 (Intel IA32) LINUX64 Redhat WS 3 (x86_64) LINUXIPF Redhat 2.1AW (Itanium)

WIN Windows 2000/XP/Vista/7 (IA32)WIN64 Windows XP/Vista/7/HPC (x64)

A.22



All links below are password protected, so you need an account via

www.acusim.com - Client Login link at upper-right!!!

Software Distribution

http://www.acusim.com/webapps/document/release/

Documentation and Training

http://www.acusim.com/webapps/document/documentation/ http://www.acusim.com/webapps/document/documentation/

Tutorials

AcuSolve

http://www.acusim.com/webapps/document/as_tutorials/

AcuConsole

http://www.acusim.com/webapps/document/ac_tutorials/

A.23


AcuConsole Overview


AcuConsole OverviewAcuConsole Overview

A GUI-based pre-processor for AcuSolve

Visualization Area - mesh and geometry display

Data tree

Data tree Manager

View Manager

Information Area

Panel Area

A.26

Geometry Reader

No Geometry clean-up

Mesh Generator

AcuSolve launcher

AcuSolve process monitor



Import ( water-tight models)

CAD: Parasolid, Pro-E, ACIS, Discrete (STL, Surf Mesh, etc.), Catia reader

Raw mesh (from ICEM-CFD, Harpoon, etc.)

AcuSolve input file (.inp)

Third party formats: Fluent .cas/.msh file, Patran Neutral file, etc.

Mesh Generation

Generates mesh directly on the CAD model Generates mesh directly on the CAD model

Auto Tet mesh with boundary layer, Extrusion, Periodicity

AcuSolve

Problem set-up : Global parameters, Boundary conditions, etc.

Generate AcuSolve input files

Launch AcuSolve : Directly or via PBS/LSF

Monitor solution via AcuProbe

Launch visualizers : FieldView, EnSight, ParaView etc.

A.27



AcuConsole

AcuSolve

AcuProbe

AcuMeshSim

AcuImport

AcuPrep

AcuView

A.28

AcuImport

PYTHON INTERFACE

Database, Graphics, GUI Engine,CAD Reader, AcuSolve Utilities



AcuMeshSim, AcuSolve and other executables can be run on a different machine /

OS from that running AcuConsole.

Python interface simplifies AcuConsole customization.

Ideal for CAE Automation

Modular architecture allows us to substitute different components without major

changes in the code.changes in the code.

Database uses HDF5 format, which is efficient for storing large amounts of data.

A.29


AcuConsole Demo Pipe Flow


AcuConsole Demo AcuConsole Demo -- Pipe FlowPipe Flow

Objectives

Learn the basic interaction with AcuConsole

Import geometry into AcuConsole

Set-up the problem to solve a laminar pipe-flow

Launch and Monitor AcuSolve

Post-Process using AcuProbe and ParaView

GivenGiven

CAD model of a simple pipe

A.32



Launch AcuConsole

For Windows users, go to

Start programs Acusim SoHware AcuConsole V1.8a

For Linux users, type

acuConsole

Create a new database

In the menu bar click on

File New

New database dialog opens

Navigate to the folder in which the simulation files are to be stored

Type demo as the File name and click Save

The File name (demo.acs) will be seen in the title bar

Visible entity is set to None as there is no Geometry/Mesh

A.33


Data tree

Global

Mesh/geometry

independent

Model

Mesh/geometry

dependent


A.34



Problem Description

Double-click or right-clickopen on Problem DescripIon beneath Global in the Data tree

In the Panels area, set problem parameters

Title: pipe flow

Sub Title: Re about 1000

Turbulence equation: laminar

Mesh type: Fixed

A.35



Auto Solution Strategy

Use the defaults

Steady state analysis

Max time steps: 100

Flow only

A.36



Import CAD

In the menu bar click on File Import

Choose a file to open dialog opens. Change the Files of Type to Acis File or Parasolid

File.

Navigate to the directory in which the CAD model is present and select pipe.SAT or

pipe.x_t. Click Open

Import Geometry dialog opens.

If Acis file is loaded, change the Geometry units from 1000 mm to 1 m. Click Ok to load If Acis file is loaded, change the Geometry units from 1000 mm to 1 m. Click Ok to load

the geometry.

Visible entity changes to Geometry

A.37



Right-click on Model and select Purge.

The region is in default Volume group and 3 faces in default Surface.

Rename default volume to Fluid.

Surface Grouping

Surfaces New to create two Surfaces New to create two

groups, inflow and outflow

Rename default to wall

Click on inflow Add To and

pick inflow face.

Repeat with outflow and wall

A.38



Global Mesh Attributes

Mesh size type: Relative

Relative mesh size: 0.05

Tools Generate Mesh

Click Ok in Launch AcuMeshSim dialog

A.39


Monitor the mesh generation process in AcuTail window

Check the mesh statistics in AcuTail window

To view the mesh on CAD model

Right click on Surfaces and select

display type as solid & wire


A.40



Fluid

Water

Inflow

Mass flux: 0.5 kg/sec

Outflow

Outflow Outflow

Wall

Wall

A.41



Launch AcuSolve

Problem name: demo

Generate AcuSolve input files

Launch AcuSolve

A.42



Progress monitor

AcuSolve log data

Tools AcuProbe

A.43



Post process in Paraview

Tools ParaView

Ok to specify demo.1.Log file

Surface pressure contours are displayed

Refer to ParaView manual for more details

A.44


Acusim Programs


Acusim ProgramsAcusim Programs

Simulation process consists of running multiple programs:

acuConsole - construct models, write input files

acuMakeLib/acuMakeDll - compile user functions

acuRun - script to run preparatory and solver programs

acuPrep - read input files and prepare data for solver run

acuView - compute view factor for radiation problems

acuSolve - perform the CFD simulation

acuTrans - translate the output of acuSolve acuTrans - translate the output of acuSolve

Refer to the Programs Reference Manual downloadable via Client Login

A.46



AcuConsole

Construct models using two main modes of operation

Import geometry, generate mesh, set up CFD simulation

Import existing mesh/input file, set up CFD simulation

Data tree

VisualizationArea

Information AreaPanels

Area

Data tree

Data tree Manager

CPU UsageMonitor

A.47



acuMakeLib/acuMakeDll

Compile User Defined Functions (UDF)

acuMakeLib - Unix and Linux platforms

acuMakeDll Win

These scripts compile user coding, then create a dynamic shared library (Linux/Unix) or a

dynamic linked library (Windows) that is loaded by AcuSolve at runtime and executed when

necessary.

Example:

To compile user functions that are in a file named usrFunction.c, execute the following

command:

Linux/Unix: acuMakeLib -src usrFunction.c

Windows: acuMakeDll -src usrFunction.c

A.48



acuRun

Script that runs appropriate programs to launch simulations on single processor or

parallel compute systems.

acuRun has various different functions that will be executed depending on the type of physics being solved:

prep: prepare the input data for acuSolve prep: prepare the input data for acuSolve view: perform the view factor computation solve: launch the solver

prep,solve: prepare the input data for acuSolve, then launch the solver all: run all necessary modules for the simulation (prep, view, solve)

A.49



acuRun

To execute from within acuConsole, point to the icon in the Tools menu or on the main

toolbar:

The following panel appears:

Equivalent command line argument:acuRun -do all -pb demo -np 2

Both methods run a problem named demo, write the results to the directory ACUSIM.DIR, runall necessary solver modules (acuPrep, acuView, acuSolve), and utilize a single processor.

A.50



acuRun

We could also accomplish the same results by executing each command in succession without using acuRun:

Equivalent series of command line arguments:Prepare the input:

acuPrep -pb demo -nsd 1

Compute the view factors:acuView -pb demo -np 1

Launch the solver:acuSolve -pb demo -np 1

Remember: There are many options for each of the programs.. -h option lists them all.

A.51



acuSig

Signal a running AcuSolve job

Stop job at end of current time step (clean stop)

acuSig -stop

Stop job as soon as possible

acuSig -halt

Stop job after a certain time step is completed

acuSig sts 200 acuSig sts 200

Signal job to output results at end of current time step

acuSig -out

Many more options

acuSig -h

A.52



acuTrans / acuOut

Programs to translate solution data for post processing

To execute from within acuConsole, point to the icon in the Tools menu or on the main toolbar:

The following panel appears:

Equivalent command line argument:acuTrans out to tableacuTrans out to statsacuTrans out to info

A.53



Additional acuTrans Examples

Get statistics on nodal velocity at steps 5 through 15

acuTrans out outv velocity to stats ts 5:15

Translate mass flux at inflow to a raw table

acuTrans osi osiv mass osis "inflow" to table

Translate heat flux at nodes of the wall to a raw table

acuTrans osf osfv heat osfs "wall surface" to table

Translate heat fluxes of all surface output nodes to a raw table Translate heat fluxes of all surface output nodes to a raw table

acuTrans out extout -outv surface_heat_flux to table

**Note that internal nodes will have a value of zero

Visualize all nodal and surface node data with FieldView

acuTrans out extout to fieldview

A.54



There are many more utility programs

Some available through AcuConsole, some not

See MANIFEST.txt in the distribution for complete list

bin (supported programs):===========================================================================

| File | Type | Description |===========================================================================

|+acuDmg | Python | Directory management tool || acuDplace | Perl | Determine optimum dplace value for Altix || acuDplace | Perl | Determine optimum dplace value for Altix || acuEnSight6To5 | Script | Convert an EnSight6 file to EnSight5 || acuFmt | Exec | ASCII/binary conversion of AcuSolve files || acuGetData | Exec | Get AcuSolve results data || acuImport | Exec | Import CFD files to AcuSolve |...

bin (unsupported programs):===========================================================================

| File | Type | Description |===========================================================================

| acuCheckBadTets | Script | Check for tets with internal no-slip BC || acuCheckTets | Script | Check/correct node ordering of tet mesh || acuCp | Perl | Copy an input file(s) in a new directory || acuCpi | Exec | Standard MPI PI (3.1415) test |

A.55


Workshop 1 Conjugate Heat Transfer


Workshop 1 Workshop 1 -- Conjugate Heat TransferConjugate Heat Transfer

Create the database

File New

Browse to Workshop1 directory

Enter name as conj_pipe

Select Save

Import the geometry

File Import File Import

Set type to Acis File or Parasolid

Select cht_pipe.SAT or cht_pipe.x_t > Open

If Acis file is selected, change Geometry units from

1000 mm to 1 m

Volume and Surface Group Option = By part name

Separate internal faces = On

Ok to import

Visible entity set to Geometry

A.58



Click PRB from the Data tree Manager

Expand the Global branch

Double-click Problem Description

Set Title to pipe flow

Set Sub title to conjugate heat transfer

Set Temperature equation to Advective diffusive Set Temperature equation to Advective diffusive

Set Turbulence equation to Spalart-Allmaras

Double-click Auto Solution Strategy

Review the default settings to be used

A.59



Click MAT from the Data tree Manager

Right-click Material Model and select New

Right-click Material Model 1, select Rename and type Steel

Enter on keyboard to accept

Double-click Steel

Set Medium to Solid

Set Density to 7865 kg/m3 Set Density to 7865 kg/m3

Set Specific Heat to 460 J/kg-K

Set Conductivity to 61 W/m-K

A.60



Click MSH on the Data tree Manager

Double-click Global Mesh Attributes Set Relative mesh size to 0.03

3% of bounding box largest edge

Minimize the Global branch

File Save

Expand Model and Volumes branches

Right-click Surfaces and select Display off

Right-click Volumes and select Purge

Right-click Volumes and select Volume Manager

Set Display to on for both volumes

Change name of inner_pipe to water and outer_pipe to steel

A.61



Click on Columns to see those available for Volume Manager

Make sure Medium and Material Model are active - then Ok

For the water volume, set Medium to Fluid and Element Set Material Model to Water

For the steel volume, set Element Set Medium to Solid and Element Set Material Model to

Steel

Click Close when finished

Minimize VolumesMinimize Volumes

Set display of Volumes off and Surfaces on

A.62



Expand Surfaces

Surfaces are based on their original parent Volume

The surfaces between the two volumes are separated into two different groups

Right-click surfaces and select Purge

Right-click Surfaces and select Surface ManagerRight-click Surfaces and select Surface Manager

Select New twice to create two new groups

Click on Columns and enable Simple BC Type

A.63



In the Surface Manager, rename Surface 1 to Inlet and click Add to

Select the circular surface at the minimum X end and hit Done

Set Display for Inlet to off

Set Simple BC Type to Inflow

A.64


Rename Surface 2 to Solid_Outer and click Add to

Select the outermost cylinder surface and click Done

Set Display for Solid_Outer to Off

Rename inner_pipe to Outlet - a single surface at the maximum Y end

Set Simple BC Type to Outflow - set Display to off

Rename outer_pipe to Solid_Ends - the two end surfaces of the solid pipe volume -

set Display to off


A.65



In the Surface Manager, rename inner_pipe_int to Fluid_int - the surface between

solid and fluid, but attached to the fluid volume

Rename outer_pipe_int to Solid_int - the matching surface, but attached to the solid

volume

Click Close to close the Surface Manager

A.66



Click BC from the Data tree Manager

Expand Inlet under Surfaces

Double-click Simple Boundary Condition Set Inflow type to Mass flux Set Mass flux to 5 kg/sec Set Temperature to 273 K

Expand Solid_Outer Double-click Simple Boundary Condition Set Temperature BC type to Value Set Temperature to 300 K

A.67



Define boundary layer elements growing from Fluid

wall

Click MSH in the Data tree Manager

Expand Fluid_Int

Click in the box next to Surface Mesh Attributes

Set Mesh size type to None Set Mesh size type to None

No additional control on size

Set Boundary layer flag to On

Set Resolve to Total layer height

Calculated from other settings

Set First element height to 0.02m

Set Growth rate to 1.3

Set Number of layers to 5

A.68



Launch the mesh generator

Tools Generate Mesh or use the icon

Accept the defaults

Click Ok

NOTE: The mesh generator works directly

on the CAD model stored in the

database, rather than a faceted database, rather than a faceted

representation.

A.69



Monitor the mesh generation process in the

AcuTail window

Check the mesh statistics in the AcuTail

window

~12000 Nodes

~66000 volume elements

By default the boundary layer prisms are By default the boundary layer prisms are

split to tets

A.70



Notice that Visible entity is now set to Mesh

Right-click Surfaces and select Display On

Change the display type

Right-click Surfaces

Select Display type

Select solid & wire Select solid & wire

Boundary Layers

A.71



Cut-Plane Visualization

Right-click Model and select Cut Plane

Set Clip to on

Set Clip to Down to reverse clip

Set Display to mesh

Set Color to volumes

Hold Ctrl key to change view while moving mouse

A.72



Explore the features in Cut-plane dialog to visualize the mesh at various locations

and with different settings.

Hold the Ctrl key and use the mouse to maneuver the geometry without changing the

cut plane

A.73



Scale the mesh from L/D = 5 to L/D = 15 for the

simulation

Simulate 3X length with the same mesh count

MeshOp Transform Coordinates

Set the Scaling factors in X/Y/Z to 3.0, 1.0, 1.0

Click Apply to perform the scaling

Click Close to close the dialog

A.74



Launch AcuSolve

Tools AcuSolve

Or, click on the red arrow icon in the toolbar.

Click Ok with defaults

A.75



Monitor dialog provides two options

Stop run - stop: Signals AcuSolve to stop the

analysis at end of current time step

Output results - output: Signals AcuSolve to

output results at end of current time step

A.76



Monitor the residuals in acuProbe

Click Tools AcuProbe

Expand Residual ratio

Right-click Final and select Plot All

Review other options for plotting surface integrations, etc.

A.77



Post process in ParaView

ParaView is an open-source application for visualizing two and three dimensional data

sets (www.paraview.org)

ParaView supports from single processor workstation to multi processor distributed

memory super computers

This can visualize meshes containing upto 6 billion structured cells and 250 million

unstructured cells

A.78



ParaView GUI

Menu Bar

Toolbars

Pipeline Browser

A.79

Object Inspector

3D View



Launch ParaView from AcuConsole

Click Tools ParaView or click on the ParaView icon in tool bar

In the Launch ParaView dialog make sure path to conj_pipe.1.Log is provided.

Click Ok to accept it.

ParaView GUI opens with data populated in

the pipeline browser and object inspector

Click Apply in the object inspector to accept

the default properties and for displaying the

model in 3D View

A.80



Model display and properties

If interested in setting the properties, Users can adjust the properties in the Object

inspector tabs before hitting the Apply button.

Under Properties tab, by default all the properties are loaded

Under Display tab, Users can adjust the display of the model.

To color the model with Temperature select it from the drop down list next to Color

By in the display tab

A.81



Filters

Filters are functional units that process the data to generate, extract, or derive features

from the data.

There are many filters available in ParaView

The most common are

Calculator

Contour

Clip Clip

Slice

Threshold

Glyph

Stream Tracer

A.82



Clip Filter

Intersects the geometry with a half space. The effect is to remove all the geometry on

one side of a user defined plane

Make sure conj_pipe.1.Log is selected in pipeline browser

In the menu bar click Filters> Common > Clip

In the object inspector set the Normal to (0,1,0) and uncheck the Show Plane

Click Apply.

Under the display tab select Velocity in the box next to Color By. Under the display tab select Velocity in the box next to Color By.

Click on Edit Color Map button in the Display tab and set the legend as desired

A.83



Slice Filter

Intersects the geometry with a plane. The effect is similar to clipping except that all that

remains is geometry where the plane is located

Make sure clip1 is selected in the pipeline browser

In the menu bar click Filters> Common > Slice

In the object inspector set the Normal to (0,1,0) and uncheck the Show Plane

Click Apply.

Under the display tab select Temperature in the box next to Color By. Under the display tab select Temperature in the box next to Color By.

Click on Edit Color Map button in the Display tab and set the legend as desired

A.84



Contour Filter

Extracts the points, curves, or surfaces where a scalar field is equal to a user-defined

value. This surface is often also called an isosurface

Make sure conj_pipe.1.Log is selected in the pipeline browser.

Put off the display button (eye symbol) next to Slice1 and put On for conj_pipe.1.Log

In the menu bar click Filters > Common > Contour

In the object inspector select temperature in the list next to Contour By

A.85

Set the user defined value to 285 and hit Apply

Under the Display tab select pressure from the list next to Color By.



Stream Tracer Filter

Seeds a vector field with points and then traces those seed points through the (steady

state) vector field

Make sure conj_pipe.1.Log is selected in the pipeline browser.

Put off the display button (eye symbol) next to Contour1 and put On for

conj_pipe.1.Log

In the menu bar click Filters > Common > Stream Tracer

Click Apply in the object inspector to visualize the stream lines

A.86

Click Apply in the object inspector to visualize the stream lines

Straight lines are seen from inlet to outlet



Generate Tubes Filter

Makes streamlines look fancy and colors them with some property

In the menu bar click Filters > Alphabetical > Generate Tubes

In the object inspector, select velocity from the list next to Vectors and set the Radius

to 0.05. Click Apply

In the Display tab select Pressure from the list next to Color By

A.87



Glyph Filter

Places a glyph, a simple shape on each point in the mesh. Glyphs may be oriented by a

vector and scaled by a vector or scalar

In the menu bar click Filters > Common > Glyph

Select velocity from the list next to Vectors, set the Shaft Radius to 0.01 and

Maximum Number of Points to 500

Click Apply

In the Display tab, select Pressure in the list next to Color By

A.88

In the Display tab, select Pressure in the list next to Color By


Solver Commands


Solver CommandsSolver Commands

All solver commands are read by acuPrep from an ASCII text file (input file)

This file may be generated in a number of ways:

Using AcuConsole

Using mesh generators that support AcuSolve as an export format

Manually

We will discuss the format of the input file and show some examples of commands, but

the main focus of the training, as you have seen, is on generating the file using

AcuConsoleAcuConsole

A.90



Commands have the following general syntax:

COMMAND ( qualifier ) {parameter1 = value1...

parameterN = valueN}

COMMAND is the name of the command, such as ANALYSIS

qualifier (including the parentheses) is a mandatory qualifier

parameter1 to parameterN are optional parameters.

Commands are format free and case insensitive, except in double quoted strings.

All text after a hash mark, #, is a comment; except in double-quoted strings.

ANALYSIS {mode = static # Run as static for now

}

A.91



There are two types of commands: Functional & Declarative

Functional commands perform operations at the time they are read:

AUTO_SOLUTION_STRATEGY

RESTART

RUN

INCLUDE INCLUDE

ASSIGN

QUIT

Placement of functional commands is important.

Declarative commands define the problem parameters.

They are order independent. NODAL_BOUNDARY_CONDITION commands may be specified before or after the

COORDINATE command; even though the former depend on the latter.

A.92



Some commands require a qualifier

Qualifiers distinguish one use of the command from another:

MATERIAL_MODEL( "air" ) {density_model = "air at std. atm."viscosity_model = "air"

}MATERIAL_MODEL( "aluminum" ) {MATERIAL_MODEL( "aluminum" ) {

density_model = "aluminum"conductivity_model = "aluminum"

}

If a command accepts a qualifier, one must be given.

If a command does not require a qualifier, there must be none.

A.93



There are two types of qualifiers:

User-given name:

Any double-quoted string: air, my #1 BC.

Used to reference a command by another command

DENSITY_MODEL( "air at std. atm." ) {density = 1.225

}MATERIAL_MODEL( "air" ) {

density_model = "air at std. atm."viscosity_model = "air"

} Enumerated:

Select from a specific list of values:

NODAL_INITIAL_CONDITION( velocity ) {default_values = { 1, 0, 0 }

}

A.94



Commands have zero or more parameters

Most parameters have default values

Parameters are persistent; they change only if the command is reissued with that

parameter:

DENSITY_MODEL( "air with bouyancy" ) {density = 1.225density = 1.225

}DENSITY_MODEL( "air with bouyancy" ) {

density = 1.2}

Seven types of parameters:

String, Enumerated, Boolean, Integer, Real, List and Array

A.95



String is any user-given value enclosed in a pair of double-quotes.

Typically used to refer to a particular issuance of another command

May contain up to 1023 characters

SIMPLE_BOUNDARY_CONDITION( "inflow" ){element_set = "channel"

}

Enumerated is a set of options available for a given parameter.Enumerated is a set of options available for a given parameter.

Parameter shape of ELEMENT_SET command accepts: four_node_tet,

five_node_pyramid, six_node_wedge, eight_node_brick and ten_node_tet

ELEMENT_SET( "channel" ) {shape = eight_node_brick

}

A.96



Boolean turns an option on or off. Values on, yes and true are equivalent; so are off, no and false.

TIME_INCREMENT {auto_time_increment = on

}

Integer is an integer value. An integer parameter may have a valid range. An integer parameter may have a valid range. Some integer values may have special meaning.

NODAL_OUTPUT {output_frequency = 10

}

Real is a floating point value. A real parameter may have a valid range.

NODAL_OUTPUT {output_time_interval = 0.3

}A.97



List is a set of strings providing a list of user-specified commands:

Order of strings in the list is important

TIME_SEQUENCE {Staggers = { "flow stagger", "turb stagger" }

}

Array is a set of integers, floating point numbers, or both:

The array may be specified directly in the input file: The array may be specified directly in the input file:

PERIODIC_BOUNDARY_CONDITION( "axisymmetric PBC" ) {rotation_axis = { 0, 0, 0 ; 0, 0, 1 }

} The array may be read from an external file:

COORDINATE {coordinates = Read( "channel.crd" )

}

A.98



Arithmetic expressions may be used in integer, real and array parameters:

ASSIGN {variable = SHIFTvalue = Sin( PI/8 + Asin(.3) )

}MULTIPLIER_FUNCTION( "shifted half sin" ) {

type = cubic_splinecurve_fit_variable = timecurve_fit_variable = timecurve_fit_values = { 0.0, SHIFT + Sin(0.0*PI) ;

0.1, SHIFT + Sin(0.1*PI) ;1.0, SHIFT + Sin(1.0*PI) ; }

}

Operations +, -, *, /, ^ (for power) and parentheses are available.

Standard C math functions, Abs(x), Acos(x), ..., Tanh(x), plus Max(x,y) and

Min(x,y) are available.

Variables E, PI and EPS (machine precision) are predefined.

A.99



Values may be read from an environment variable:

SIMPLE_BOUNDARY_CONDITION( "inflow" ) {x_velocity = Env( "INLET_VELOCITY" )

} In UNIX cshell the variable is set as

cshell-prompt> setenv INLET_VELOCITY 20 This is particularly useful for parametric studies

foreach vel ( 5 10 15 20 )echo "Processing velocity " $vel " "setenv INLET_VELOCITY $velacuRunacuTrans out to stats > STATS.$vel

end Strings may also be imported

COORDINATES {coordinates = Read(Env("PROBLEM") . ".crd")

}

A.100


The solver commands are specified entirely through the Data tree

in AcuConsole:


Data tree

Each branch Each branch houses differentcommands

A.101



The commands are organized into the Global and Model branches

Global commands are mesh independent (problem name, physical models to use,

material models, etc.)

Model commands involve information about the mesh (boundary values for specific

faces, nodes, etc.)

A.102



Double clicking on a node in the tree shows the options for specific commands:

For example, double clicking on Problem Description brings up the following options

Global Problem Description

The current settings will cause the following lines to be written to the input file:

A.103



Common Global Commands

Auto Solution Strategy

Automatically determine the appropriate linear solver settings and time stepping strategy

based on the equations present

Global Auto Solution Strategy

Equivalent input file command:Equivalent input file command:

A.104




Multiplier Function

Multiplier Function is visible only when All or PB* is selected from Data tree Manager.

Right-click on Multiplier Function and select New. Multiplier Function 1 is generated.

Rename to Linear Ramp. Double click on Multiplier Function 1 to view the properties in

Panels Area.

Time varying scale factor that can be applied to boundary conditions, time step size, etc.

Equivalent input file command:

A.105




Material Model

Specify material properties

Global Material Model Water

Equivalent input file commands:

A.106




Body Force

Define momentum, species, and thermal body forces

Global Body Force Gravity


A.107




Nodal Output

Define the frequency at which to write nodal results to disk

Global Output Nodal Output


A.108




Nodal Initial Condition

Specify the initial conditions for the simulation

Global Nodal Initial Condition


A.109



Overview of Modeling Commands

Modeling commands apply to 1 of 4 types of entities

Volume Elements (Volumes)

Surface Elements (Surfaces)

Periodic node pairs (Periodics)

Nodes (Nodes)

Each entry can be expanded to show the available sets and options for this type of

entity:entity:

A.110



Common Modeling Commands

Element Set

Define a group of volume elements and assign attributes

Model Volumes Name Element Set


A.111




Simple Boundary Condition

Apply boundary conditions to a set of surface faces

Model Surfaces Name Simple Boundary Condition


SIMPLE_BOUNDARY_CONDITION( Inlet ){surfaces = Read(...)shape = tri3element_set = Fluidtype = inflowinflow_type = mass_fluxmass_flux = 20temperature_type = valuetemperature = 422.04

}


A.112




Periodic Boundary Condition

Apply periodic conditions to a set of node pairs

Model Periodics Name Periodic Boundary Condition


PERIODIC_BOUNDARY_CONDITION( Periodicity ){variable = alltype = periodicnodal_pairs = Read( ... )

}


A.113




Nodal Boundary Condition

Apply boundary conditions to a set of nodes for a specific variable

Model Nodes Name Variable Name


NODAL_BOUNDARY_CONDITION( Test Data x-vel ){nodes = Read( ... )variable = x_velocitytype = scattered_datascattered_data = Read( ... )active_type = alwaysprecedence = 1reference_frame = nonemultiplier_function = none

}


A.114



Many more commands exist

Most are available within AcuConsole

Expand the branches in the model tree to see what is there

For a complete list, see AcuSolve Command Reference Manual

A.115


A.116


Workshop 2 Blower


Workshop 2 Workshop 2 -- BlowerBlower

Purposes of the Workshop

Import geometry and create Surface and Volume sets

Build Reference Frame and discuss rotating problems

Define Global and Surface mesh parameters

Define Boundary Conditions

Apply the Reference Frame to Volumes and Surfaces

Generate an all-tet mesh

View a mesh cut plane

Run AcuSolve

Monitor solution with AcuProbe and create a UDF

A.118



Create the database

File New


Enter name as blower1

Select Save

Import the geometry

File Import File Import

Set type to Acis File or Parasolid

Select blower_asm.SAT or blower_asm.x_t

If Acis file is selected, change the Geometry units

from 1000 mm to 1 m

Set Volume and Surface Group Option to By part

name

Toggle Separate internal faces On

Ok to import

A.119






Set Title to Blower CFD

Set Sub title to reference frame

Set Turbulence equation to Spalart-Allmaras Set Turbulence equation to Spalart-Allmaras

Double-click Nodal Initial Condition

Set Eddy viscosity to 1.e-5

**Note: The turbulent eddy viscosity (t) is typically set to 10-20 x laminar kinematic viscosity

A.120



The analysis will first be done with a rotating reference frame

Click PB* from the Data tree Manager

Right-click Reference Frame and select New

Right-click the created Reference Frame 1 and select

RenameRename

Change the name to Impeller_RF and press Enter on

keyboard

Double-click Impeller_RF

Select Open Array for Angular velocity

Set Z-component to 10.47 rad/sec

Angular velocity is 10.47 rad/sec (or 100 RPM) about Z-axis

Click OK

A.121



Build a coarse mesh to shorten the workshop solution

time

Click MSH from the Data tree Manager

Double-click Global Mesh Attributes

Set Relative mesh size to 0.04

Minimize the Global branch

Right-click Model and select Purge to delete

empty groups

File Save

For a reference frame analysis, the reference frame is

applied to the volume close to the impeller. Nothing

needs to be done to the boundary between the

stationary volume and the reference frame volume.

A.122



Expand Model and Volumes branches

blower_main is the bulk volume

blower_imp is the volume near the impeller

Right-click Volumes and select Volume Manager

Click on Columns and activate Reference Frame

Rename blower_main to Fluid_Main

Rename blower_imp to Fluid_Impeller

Set Material Model to Water for both volumes

Set Reference Frame to Impeller_RF for Fluid_Impeller

Close the panel

A.123



Expand Surfaces

Right-click Surfaces and select Surface Manager

Click on Columns to make sure Simple BC Type is enabled

Click New twice to create two new surfaces

Rename Surface 1 to Inlet

Click Add to for Inlet, pick the circular surface at the

maximum Z-location, and middle-clickmaximum Z-location, and middle-click

Set Simple BC Type for Inlet to Inflow

Set Display to off for Inlet

Rename Surface 2 to Outlet

Click Add to for Outlet, pick the circular surface at the

maximum Y-location, and middle-click

Set Simple BC Type for Outlet to Outflow

Set Display to off for Outlet

A.124



The remaining surfaces in blower_main are the outer walls of the blower

Rename blower_main to Walls and turn off its display

The surfaces in blower_imp_int and blower_main_int are between the two volumes. In

this case they can be in the same group.

Rename blower_main_int to Interface and turn off its display

Select Add to for Interface, select the 3 surfaces of the disk (currently in Select Add to for Interface, select the 3 surfaces of the disk (currently in

blower_imp_int) and middle-click

Click on blower_imp_int (now empty) and hit Delete

Set Simple BC Active for Interface to off

No boundary condition needed between the volumes

The remaining surfaces are the blower impeller

Rename blower_imp to Impeller

Click Close to close the surface manager

A.125



Expand Interface

Activate Surface Mesh Attributes

Set Absolute mesh size to 0.01 m

Expand Walls


Set Absolute mesh size to 0.025 m Set Absolute mesh size to 0.025 m

A.126




Expand Inlet

Double-click Simple Boundary Condition

Set Inflow type to Mass flux

Set Mass flux to 2.0 kg/sec

A.127



Expand Impeller


The impeller is a no-slip wall in the rotating

reference frame

Set Reference frame to Impeller_RF

Click MSH from the Data tree Manager


Set Absolute mesh size to 0.005 m Set Absolute mesh size to 0.005 m

With the meshing parameters defined, the model is

ready to be meshed

Save the database

A.128



Select Tools Generate Mesh

Items to check

.ams file name

This is the meshing control file written by AcuConsole

Mesh output directory

The location of the mesh files to be written by

AcuConsoleAcuConsole

Click Ok to start the meshing process

Monitor the process via the AcuTail window that opens

Mesh has ~27,000 nodes

Watch for notification that meshing is complete

A.129



Right-click Surfaces, select Display On

Right-click Surfaces, select Display type, and solid &

wire to see surface mesh

Turn on/off display of various surfaces

Right-click on surface name

Display on / Display off Display on / Display off

Experiment with Transparency

A.130



View a mesh cut plane

Right-click Model and select Cut Plane

Select Mid Z to position plane

Use the wheel to move the position to approximately Z = 0

Turn Clip to on with the radio button

Set Display to mesh via the pull-down

Set Color to volumes

To modify the position of the model (rotate, pan, etc.) hold

the Ctrl key on the keyboard while performing mouse

operations

Set Cut Plane Visible to false

Close

A.131



The model is ready to solve

Tools AcuSolve

Verify:

Problem name

Problem and Working directories

Generate AcuSolve input files and Launch AcuSolve

set to Onset to On

Click Ok to start the solver

AcuTail starts with the .Log file history

The AcuSolve Controller opens

A.132



The .Log file shows residual and solution ratios

for each equation

Residual Ratio - measure how well the solution

matches the governing equations

Solution Ratio - measure how the answers

change from iteration to iteration (also time

step to time step for a steady state problem)

AcuSolve controller

stop - stops the run and writes requested

output at end of current time step

output - writes requested output at end of

current time step

About 25 time steps to converge

A.133



Tools -> AcuProbe to track pressures

Expand Surface Output

Expand Inlet

Right-click pressure and hit Plot

Expand Outlet

Right-click pressure and hit Plot

The pressure rise is about 475 Pa

Build a UDF to monitor pressure rise

Click the User Function icon

Enter Name as Press_Rise

Define Function as shown

Right-click appropriate quantity and Copy Name, then

Paste in Function

Apply when complete

Expand User function and plot Press_Rise

A.134


Input File Review


Input File ReviewInput File Review

Open input file from Workshop 2 - blower1.inp

Problem Description panel

Writes ANALYSIS and EQUATION commands

A.136



Auto Solution Strategy panel

Writes AUTO_SOLUTION_STRATEGY command

Advanced Solution Strategy branch controls the following commands:

TIME_SEQUENCE

Individual STAGGER commands

TIME_INCREMENT

TIME_INTEGRATION TIME_INTEGRATION

LINEAR_SOLVER_PARAMETERS

CONVERGENCE_CHECK_PARAMETERS

These are not written unless needed!

A.137



Reference Frame panel

Called Impeller_RF

Writes REFERENCE_FRAME command

A.138



Material model panel for Water

Predefined in AcuConsole

Writes MATERIAL_MODEL command

A.139



Nodal Output panel

Defaults for AcuConsole

Writes NODAL_OUTPUT command

A.140



Element Set panel

Writes ELEMENT_SET command

A.141



Inlet Simple Boundary Condition panel

Writes SIMPLE_BOUNDARY_CONDITION command (truncated here)

A.142



Surface Output panel

Activated by default in AcuConsole (can be turned off by default in the preferences if

you like)

Writes SURFACE_OUTPUT command

A.143



Other important commands handled automatically in AcuConsole

COORDINATE command

RUN command

A.144


Workshop 3 Blower 2


Workshop 3 Workshop 3 -- Blower2Blower2

Purposes of the Workshop

Modify the previous blower database to run as a sliding mesh case

Open and modify an existing database

Build Mesh Motion

Define Boundary Conditions

Apply the Mesh Motion to Volumes and Surfaces

Write AcuSolve input files

Project solution from Workshop2 to mesh of Workshop3

Import Nodal Initial Condition files

Run AcuSolve

A.146



Open existing database

File -> Open


Select the blower2 database

NOTE: Could also continue from existing database

File -> Save As to change name to blower2.acs in the Workshop3 directory

A.147






Set Sub title to sliding mesh

Set Analysis type to Transient

Set Mesh type to Fully specified Set Mesh type to Fully specified

Double-click Auto Solution Strategy

Verify Analysis type set to Transient

Set Initial time increment to 0.002 sec

Set Max stagger iterations to 3

Gives better convergence at each time step

Verify Flow and Turbulence On

A.148



Click ALE from the Data tree Manager to define

the mesh motion

Right-click Mesh Motion and select New

Right-click Mesh Motion 1 and Rename

Rename to Impeller_Rot and press Enter

Double-click Impeller_Rot to open the panel

Set Type to Rotation

Select Open Array for Angular velocity

Set Z-component to 10.47 rad/sec

Click OK

NOTE: Simulation set to run for 0.2 sec = 1/3

revolution. Usually take meaningful data after

running 1 or 2 full revolutions.

A.149



Click OUT from the Data tree Manager

Expand Output

Double-click Nodal Output

Set Time step frequency to 2

Writes nodal output every 2 time steps

Set Output initial condition to On Set Output initial condition to On

Writes initial condition file

Right-click Time History Output and select New

Rename Time History Output 1 to monitor

Double-click new name monitor

Set Type to Coordinates via pull-down

Click on Open Array for Coordinates

Set coordinate to ( 0.095, 0.105, 0.0 )

Center of outlet nozzle entry region

A.150




Expand Model and Volumes

Expand Fluid_Impeller and double-click Element Set

Set Mesh motion to Impeller_Rot

Rotate the entire element set

Set Reference frame to None Set Reference frame to None

Minimize Volumes

Fluid_Main remains as in Workshop 2


Expand Surfaces and Impeller


Set Reference frame to None

Set Mesh motion to Impeller_Rot

Rotate the impeller surfaces

A.151



Click ALE from the Data tree Manager

Expand Interface

For the moving mesh problem, this is the

sliding boundary

Activate Interface Surface

Set Gap factor to 0

Values of 0 for Gap factor and/or Gap yield no Values of 0 for Gap factor and/or Gap yield no

limit on match search distance

Surface must be split to yield two sets of nodes

and surfaces

Right-click Interface, select Mesh Op. and

Split Internal Faces

Splits nodes with one set attached to

Fluid_Main and one attached to

Fluid_Impeller

~ 27,000 nodes >> ~30,000 nodes

A.152



Tools -> AcuSolve

Verify:

Problem name blower2


Generate AcuSolve input files and Launch

AcuSolve set to Off

Click Ok to generate the input files

blower2.inp and MESH.DIR directory

A.153



Project Workshop 2 solution to Workshop 3 mesh to use as initial conditions

Open AcuSolve Command Prompt and use cd to change to Workshop 2 directory

acuProj -crd ../Workshop3/MESH.DIR/blower2.crd

Creates blower1.eddy.nic, blower1.pres.nic, blower1.vel.nic in Workshop2 directory

Multi-column nodal-initial-condition files with node number and quantity or quantities

Import Nodal Initial Condition files to Workshop 3

Return to AcuConsole GUI for Workshop 3 with BAS selected in tree manager

Expand Global and double-click Nodal Initial Condition

Set Pressure initial condition type to Nodal Values

Click Open Array for Nodal Values under Pressure

Click Read from Array Editor window

Set Files of type to All files (*.*) and browse to Workshop2 directory

Select blower1.pres.nic and select Open

Repeat for Velocity (use blower1.vel.nic) and Eddy viscosity (use blower1.eddy.nic)

A.154



The model is ready to solve

Tools -> AcuSolve

Verify:

Problem name blower2


Generate AcuSolve input files and Launch Generate AcuSolve input files and Launch

AcuSolve set to On

Click Ok to start the solver

AcuTail starts with the .Log file history

The AcuSolve Controller opens

A.155



Tools -> AcuProbe to plot time history point

Expand Time History

Expand node 1

Right-click x-velocity and select Plot

A.156



Advanced Boundary Conditions

Rather than define the mass flow at the inlet, let

AcuSolve calculate the mass flow and pressure rise

based on the impeller rotation


Expand Inlet


Set Inflow type = Stagnation pressure

Set Stagnation pressure to 0.0

Set Eddy viscosity to 1.e-6

Run the problem as before

A.157


A.158


Post Processing


Post ProcessingPost Processing

AcuSolve generates four types of output data

Nodal, such as nodal output at a certain time step

Time Series, such as integrated mass flux at inlet as a function of time/time step or the

solution at a specific location

Surface Nodes, such as heat flux at each node of a wall surface at a certain time step

CAA sample data, such as divergence of Lighthill stress

acuTrans (or acuOut for a GUI) may be used to translate from internal format to the

desired format

A.160



All internal files are stored in ACUSIM.DIR directory

They are accesses through ADB (libadb.a) C-callable API &

Python through import acudb

Perl through use Acudb ;

Shell through acuGetData program

All programs (eg., acuTrans, acuOut) are written on top of ADB

Vast majority of the files are in binary

ADB handles all cross platform binary compatibilities ADB handles all cross platform binary compatibilities

Files written on one platform may be read on any platform

All supported programs can read ASCII files generated on Windows

The Windows end-of-line carriage return (Ctrl-M) character is properly handled on all

platforms

A.161



Many Options for Processing AcuSolve Results

Export data to files using acuTrans & acuTrace

Nodal results, surface integrals, volume integrals, statistical quantities, streamlines, etc.

Import nodal results into visualization packages

Display boundary surfaces, iso-surfaces, coordinate surfaces, vectors, etc.

Plot various solution quantities using acuProbe

Time history of integrated surface and volume quantities, values at specified nodes,

convergence measures, etc.convergence measures, etc.

Write custom scripts to extract data from the AcuSolve database

API exists for C, Python, Perl, C-Shell

A.162



Translating data using AcuTrans

Export data to tables, visualization packages, compute statistics, etc

Refer to the Programs Reference Manual

Examples (command line):

Translate surface integrated velocity to table format: Translate surface integrated velocity to table format:

acuTrans -osi -osiv step,velocity -to table Translate time history data to table format:

acuTrans -oth -othv step,velocity,temperature -to table Compute statistics of the nodal pressure and velocity fields:

acuTrans -out -to stats -outv pressure,velocity

A.163


Translating data using AcuOut

GUI wrapper for acuTrans available through acuConsole or Command-Line acuOut


A.164



Particle tracing using AcuTrace

Computes the trajectory of massless particles through the simulation domain

Particles do not affect the flow

Operates on steady and transient flow solutions

Tracing performed in the downstream direction only

Also able to perform interpolation of the results to specific points without doing any

tracing

Examples:

Trace the trajectory of particles whose coordinates are defined in the file

seed_coordinates.dat

acuTrace -seed seed_coordinates.dat -to table

A.165



Visualization within FIELDVIEW

Launch FIELDVIEW from AcuConsole and automatically read results from solution

database (no additional files written):

Translate to FIELDVIEW using AcuTrans Translate to FIELDVIEW using AcuTrans

Regions, split grid/results files supported

acuTrans out to fieldview

A.166


Visualization within ParaView

Launch ParaView from AcuConsole and automatically read results from solution

database (no additional files written):

Translate to EnSight using AcuTrans, then import into ParaView:


Translate to EnSight using AcuTrans, then import into ParaView:

acuTrans out to ensight

A.167


Visualization within EnSight

Launch EnSight from AcuConsole and automatically read results from solution database

(no additional files written):

Translate to EnSight using AcuTrans


Translate to EnSight using AcuTrans

EnSight gold and EnSight 6 formats supported

acuTrans out to ensight

A.168



Plotting with AcuProbe

Launch AcuProbe from the command line using:acuProbe

Launch from AcuConsole by clicking the following icon:

A.169


Program Options


Program OptionsProgram Options

Each program requires zero or more options

Options may be given on the command line:

acuRun -pb channel -np 2

Options may be placed in the configuration file, Acusim.cnf:

problem= channelproblem= channel

num_processors= 2and the program invoked as:

acuRun

Command line options take precedence over configuration files and defaults.

A.172


Program OptionsProgram Options

Each option has a (long) descriptive and a (short) abbreviated name:

Following are equivalent:

acuRun -pb channel

acuRun -problem channel Following configuration options are equivalent:

pb= channel

problem= channel Short names are typically used for command line option and long names for the

configuration file.

Most options also have default values

A.173

Training

Documents

altair engineering

altair hyperworks

acusolve features

acusolve overviewcopyright

current acusolve customers

acusolve mesh files

acusolve development

table of contents continuedsec