optimate904ncfgj_userguide

8/9/2019 Optimate904ncfgj_UserGuide

1/40

USER GUIDE

Optimate Version 9.04.007

© 2014 CD-adapco


2/40

Optimate User Guide ii

Version 9.04.007

Contents

Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

New In 9.04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Run Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Design Sweeps . . . . . . . . . . . . . . . . . . . . . . . . . . 4Optimization using SHERPA. . . . . . . . . . . . . . . . . . . . 4

Single-objective . . . . . . . . . . . . . . . . . . . . . . . 4Multi-objective . . . . . . . . . . . . . . . . . . . . . . . 4

Design of Experiments Mode. . . . . . . . . . . . . . . . . . . . 5Sensitivity and Screening . . . . . . . . . . . . . . . . . . . 5Response Surface Modeling . . . . . . . . . . . . . . . . . . 6

Stochastic Analysis . . . . . . . . . . . . . . . . . . . . . . . . 6

Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Design Parameters . . . . . . . . . . . . . . . . . . . . . . . . 7Part Swapping . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Motions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Region Physics Values. . . . . . . . . . . . . . . . . . . . . . . 8Boundary Physics Values . . . . . . . . . . . . . . . . . . . . . 8Base Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Field Functions . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Interface and Capabilities Description . . . . . . . . . . . . . . . . . 9Run Mode Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 9Variables Tab . . . . . . . . . . . . . . . . . . . . . . . . . 10

Definition Mode . . . . . . . . . . . . . . . . . . . . . . 10Removal of Variables . . . . . . . . . . . . . . . . . . . . 12

Outputs Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Reports Recording . . . . . . . . . . . . . . . . . . . . . 12Recording Modes . . . . . . . . . . . . . . . . . . . . . 12Import from RSM . . . . . . . . . . . . . . . . . . . . . 13Plots and Scenes Recording . . . . . . . . . . . . . . . . . 13Requirements . . . . . . . . . . . . . . . . . . . . . . . 13

Assembly Tab . . . . . . . . . . . . . . . . . . . . . . . . . 13Simultaneous Jobs . . . . . . . . . . . . . . . . . . . . . 13Cores per STAR-CCM+ Job . . . . . . . . . . . . . . . . . 14


3/40

Optimate User Guide ii i

Version 9.04.007

Macro Insertion Point . . . . . . . . . . . . . . . . . . . 14Macros To Be Inserted . . . . . . . . . . . . . . . . . . . 14STAR-CCM+ Run Options . . . . . . . . . . . . . . . . . 15Optimate Save Option . . . . . . . . . . . . . . . . . . . 16Number of STAR-CCM+ Runs. . . . . . . . . . . . . . . . 17Check Frequency . . . . . . . . . . . . . . . . . . . . . 17Maximum Run Time . . . . . . . . . . . . . . . . . . . . 17Tokens Required. . . . . . . . . . . . . . . . . . . . . . 17Licensing Options . . . . . . . . . . . . . . . . . . . . . 18Study Directory . . . . . . . . . . . . . . . . . . . . . . 18CAD Directory . . . . . . . . . . . . . . . . . . . . . . 18Image Directory . . . . . . . . . . . . . . . . . . . . . . 19Macro Directory . . . . . . . . . . . . . . . . . . . . . . 19Build Study . . . . . . . . . . . . . . . . . . . . . . . . 19

Run Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Open HEEDS Post . . . . . . . . . . . . . . . . . . . . . 20

HEEDS POST can also be launched outside of Optimate to view the re-sults. . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Run . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Pause/Resume . . . . . . . . . . . . . . . . . . . . . . 20Share Design . . . . . . . . . . . . . . . . . . . . . . . 21Print Message File . . . . . . . . . . . . . . . . . . . . . 21

File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Save . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Save As . . . . . . . . . . . . . . . . . . . . . . . . . . 21Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Tools Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 21Set Optimate Solver . . . . . . . . . . . . . . . . . . . . 21Set HEEDS Post . . . . . . . . . . . . . . . . . . . . . . 22Configure Microsoft Queue . . . . . . . . . . . . . . . . . 22Configure Linux Queue. . . . . . . . . . . . . . . . . . . 23Manage Remote Profiles . . . . . . . . . . . . . . . . . . 24Options. . . . . . . . . . . . . . . . . . . . . . . . . . 25

Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Running the Baseline Model . . . . . . . . . . . . . . . . . . . 27Local Jobs from Optimate . . . . . . . . . . . . . . . . . . . . 27

Local Jobs in Batch . . . . . . . . . . . . . . . . . . . . . . . 27Linux. . . . . . . . . . . . . . . . . . . . . . . . . . . 27Windows . . . . . . . . . . . . . . . . . . . . . . . . . 27

Remote Execution . . . . . . . . . . . . . . . . . . . . . . . 28Requirements for running a remote execution study . . . . . . 28Creating a remote profile . . . . . . . . . . . . . . . . . . 28Placement of required scripts . . . . . . . . . . . . . . . . 28

Generic Queue Cluster Jobs . . . . . . . . . . . . . . . . . . . 28


4/40

Optimate User Guide iv

Version 9.04.007

Microsoft Queue Cluster Jobs . . . . . . . . . . . . . . . . . . 30Resuming Jobs . . . . . . . . . . . . . . . . . . . . . . . . . 30Extending Jobs . . . . . . . . . . . . . . . . . . . . . . . . . 30

Post-Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 31STAR-CCM+. . . . . . . . . . . . . . . . . . . . . . . . . . 31

HEEDS POST . . . . . . . . . . . . . . . . . . . . . . . . . 31File Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . 32

Built Projects . . . . . . . . . . . . . . . . . . . . . . . . . . 32Running and Completed Projects . . . . . . . . . . . . . . . . . 33

Debugging . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Message File . . . . . . . . . . . . . . . . . . . . . . . . . . 34STAR-CCM+ Log Files . . . . . . . . . . . . . . . . . . . . . 34HEEDS Post . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . 35


5/40

Optimate User Guide 1

Optimate

DescriptionOptimate is an add-on for STAR-CCM+ that allows users to setup multipleSTAR-CCM+ runs without scripting. It also provides users the ability toperform design exploration, optimization, design of experiment androbustness studies without leaving the STAR-CCM+ environment.

Optimate allows users to do the following:

• Select a run mode based on the goals of the analysis

• Select variables from an existing simulation file to vary. Variables

can be geometry modifications or boundary conditions.• Define the values for each variable

• Select reports, plots, and scenes from the simulation file that will berecorded for each STAR-CCM+ job

• Run the STAR-CCM+ jobs on a local machine or setup the jobs to besubmitted on a cluster

• Post-process individual cases using STAR-CCM+ or post-process thedata from the set of analyses using HEEDS POST

Optimate uses technology from Red Cedar Technology to execute, monitorand post-process the Design Exploration studies. The SHERPA searchalgorithm is used for the Optimization and Pareto Optimization modes ofOptimate.

Optimate is designed to be used when STAR-CCM+ is the only analysis toolin the automation or optimization process. If an additional tool is beingused (e.g., Abaqus, Excel, etc.) an external optimization package will needto be used. If this is the case, Optimate can help create the necessary batchscripting to run STAR-CCM+. This script usually includes importing a newCAD file, remeshing the geometry, running the analysis and exporting

results. A more detailed description of this can be found in the UsingExternal Optimizer.


6/40


Requirements

Typically, a simulation file will be loaded in STAR-CCM+ before Optimateis launched. Users should verify that the simulation file produces acceptableresults and the required post-processing has already been set up. If a

simulation file is not loaded into STAR-CCM+, Optimate will open butusers will only be able to start a local job.

If Optimate will be modifying geometry, a process must exist in thesimulation to robustly mesh the modified geometry. This process will mostlikely include 3D-CAD, mesh operations, or surface wrapping.

When jobs are executed for an Optimate project, each job will be run untilthe stopping criteria are met within the simulation file. There is an option toclear the solution and start from scratch. Users should be mindful of thisand the stopping criteria should be set accordingly. For example, a pipe

flow analysis has been converged and run to 200 iterations. Using Optimatethe radius of the pipe will be changed, the case remeshed and run. Themaximum iterations should be set to a value greater than 200 iterations toallow STAR-CCM+ enough iterations to converge the solution in a robustmanner.

To build and run Optimate projects, users will need to install the OptimateNetbeans module (nbm) and the Optimate solver. The Optimate Netbeansmodule will need to be installed on the machine that will be used to setupthe cases. The Optimate solver will need to be installed on the machinewhere the jobs will be executed.

New In 9.04

There have been several enhancements to Optimate for the current release.This section will give a brief introduction of features that have been addedor modified in the current version of Optimate, more detail on these featurescan be found in this documentation under the affected tabs.

Remote execution of STAR-CCM+ from within the Optimate Interface

Optimate now has the ability to submit STAR-CCM+ jobs on a remoteworkstation or cluster. This means Optimate can run and post process inreal time on a local machine, which submitting each individual evaluationto a remote machine.


7/40


Automat ic CAD Robustness Studies

Users can now check the robustness of their parametric CAD by running aCAD robustness study. The CAD robustness study gives failure rates for theregeneration of CAD and can pinpoint areas of the design space where theCAD fails to update properly. A CAD Robustness study can only be run on

STAR-CCM+ generated CAD.

Create a response surface from a set of existing designs

A response surface can now be generated from a set of existing designs.These designs can be exported from a previous study through HEEDS Post,or can be a set of designs completely defined by the user.

Addi tion of Kr ig ing and Rad ial Bas is func tion response surfaces

Optimate now supports the creation of the Kriging and Radial Basis

function response surfaces in addition to the existing linear and quadraticresponse surfaces.

Use a response surface model as the source for any study

A response surface from an previously completed design exploration studycan now be used to as the source of any study. This allows the user to savea significant amount of time since no additional simulations have to be run.

Better control over optimization study from the interface

Optimate now allows the user to pause or stop the study directly from theinterface.

Misc Enhancements

• Interface improvements for setting up a Windows HPC environment.

• Multi-select and delete all for reports, plots and scenes

• Various bug fixes and improvements to the interface

Run ModesOptimate can be run in multiple ways. The appropriate run mode is selectedbased on the goals of the analysis as described below. Choosing theappropriate mode will determine how many STAR-CCM+ runs areexecuted and how the inputs for each run are determined.


8/40


Design Sweeps

In Design Sweeps mode the values for the variable are supplied by userbefore the job is started. This mode is applicable when replicating testresults, creating aerodynamics loads databases, compressor maps or any

application when the configuration for each job is known a priori. There isno optimization taking place in Design Sweeps mode. The variables used inDesign Sweeps mode must be defined using the ‘Minimum, Maximum, N’method, the List method, or a CSV file.

Running in Design Exploration mode requires either theSTAR-CCM+/Optimate or STAR-CCM+/Optimate+ products and relatedlicensing features.

Optimization using SHERPA

Single-objective

When the single-objective run option is selected, the input values areselected by the optimization algorithm to meet the specific goals of theanalysis. Possible goals include minimizing pressure drop, maximizingoutlet uniformity, minimizing component temperatures, and minimizingstress. The user is able to define the minimum and maximum value for eachvariable and the search algorithm is allowed to choose any value within thebounds during the analysis. The optimization algorithm being used is theSHERPA search algorithm by Red Cedar Technology.

The variables used in Optimization mode must be defined using the‘Minimum, Maximum, Resolution/Increment’ method.

When using the single-objective run option, users must define at least oneobjective. If multiple objectives are defined, a linear weighting will be usedto combine the objectives. Because the weighting of possibly competingobjectives is defined a priori, running an analysis in Optimization modewith return one best design.

Running the single-optimization option requires the

STAR-CCM+/Optimate+ product and related licensing features.

Multi-objective

Using the multi-objective run option triggers a Pareto Optimization. ParetoOptimization is a formulation for investigating multi-objectiveoptimization problems. It is particularly well suited when the twoobjectives are competitive in nature. In such cases there is no singleoptimum design. Rather there is a curve along which all designs are


9/40


Optimum in one objective for a given value in the other. This is callednon-dominated sorting. The resulting curve is referred to as Pareto Frontand it defines the optimum trade-off relationship between two objectives.

When the multi-objective run option is selected, the weighting forcompeting objectives does not need to be defined a priori. The study willreturn a set of all optimal designs that lie on the Pareto front. Theoptimization algorithm being used is the MO-SHERPA search algorithm byRed Cedar Technology.

When the multi-objective run option is selected, two additional run optionsare exposed:

1. Set Archive Size: This is the desired number of non-dominatingdesigns in your Pareto front or trade-off curve. A larger archive sizetypically produces better resolved trade-off curves, but only if thenumber of evaluation is increased as well. As a general rule, the optimal

archive size can be calculated as: Number of evaluations / 1002. Stop on Pareto Convergence?: Checking this option forces the

optimization run to stop as soon as the Pareto front is converged. If thePareto front does not converge, Optimate will carry out the number ofevaluations as specified in the Assembly Tab.

The variables used in the multi-objective run option must be defined usingthe ‘Minimum, Maximum, Resolution/Increment’ method.

Running the multi-objective run option requires theSTAR-CCM+/Optimate+ product and related licensing features.

Design of Experiments Mode

The Design of Experiments mode can be used for local exploration arounda particular design. A user will supply variable values using the ‘Minimum,Maximum, Resolution/Increment’ method and Optimate will use Design ofExperiments to create a response surface and study sensitivities of designfactors and factor interaction.

When the ‘Design of Experiments’ run mode is selected, three ‘Run

Options’ are exposed:

Sensitivity and Screening

1. 2 Level Full Factorial: A full factorial DoE studies the various factorsand all possible combinations of the factors at a specified number oflevels. From such a study insight can be gained into the sensitivity ofeach factor and every combination of factors to the design responses. A2 level full factorial study examines all the factors at two levels, ‘low’


10/40


and ‘high’. The number of runs required for a 2 level full factorial studyis 2n, where ‘n’ is the number of DoE factors.

2. 3 Level Full Factorial: A 3 level full factorial DoE is in conceptuallysimilar to a 2 level full factorial, with the main difference being that allfactors and combinations of factors are evaluated at three levels, ‘low’,

‘mid’ and ‘high’. The number of runs required for a 3 level full factorialstudy is 3n, where ‘n’ is the number of DoE factors.

Response Surface Modeling

1. Latin Hypercube: The Latin Hypercube sampling option is an efficientmethod to generate a response surface for the design space. Thisgenerated response surface can be used for higher level DoE studytypes like 2 or 3 level full factorial studies since running these studies ona response surface is computationally inexpensive. The minimumnumber of evaluations to fit a quadratic surface is (n+1)(n+2)/2, where

‘n’ is the number of DoE factors. It is recommended that the userevaluates at least 2-4 more evaluations than the minimum, up to amaximum of two times the minimum.

2. Use Existing Designs: The ‘Use Existing Designs’ option allows theuser to create a response surface that fits a design set specified by theuser. The designs are to be specified through a .csv file which can beexported through HEEDS Post. To export a set of designs from HEEDSPost, open up the design table and select ‘Save Plot Data’.

Running in Design of Experiments mode requires either theSTAR-CCM+/enabling Optimate or STAR-CCM+/enabling Optimate+

products and related licensing features.

Stochastic Analysis

A Stochastic Analysis study is used to determine whether a particulardesign is affected by minor variations in selected input values due toinstallation or manufacturing tolerances. The user specifies a probabilitydistribution which is applied to the inputs and the distribution of theoutputs can lead to insights about the robustness of the design. The user canalso specify constraints on design responses to obtain a prediction of failure

rate.

The variable values using in Stochastic Analysis mode are defined using the‘Value, Distribution’ mode where the user can specify either a Gaussian oruniform probability distribution.

Running in Stochastic Analysis mode requires either theSTAR-CCM+/enabling Optimate or STAR-CCM+/enabling Optimate+products and related licensing features.


11/40


Variables

Optimate allows users to identify which variables to create from an existingsimulation file. These variables can be either geometry modifications orboundary conditions. For this release, the support variables can be found

below.

Design Parameters

CAD models that have been modified and/or created in 3D-CAD and havedesign parameters defined can be modified using Optimate. Changingdesign parameters and pushing the modified geometry through themeshing pipeline will require Optimate to remesh the geometry. Usersshould be aware of this for memory considerations. Changing a designparameter such that the geometry becomes invalid will result in a failure for

the analysis. Variables can be created from the following design parameters:• Scalar quantities

• Translation components

Scalar quantities include distances, radii, extrusion lengths, and taperangles.

For translation variables, Optimate will attempt to also translate acoordinate system with the same name as the current design parameter.This feature is useful if a rotation needs to be performed after the translation

is done. It is important to create the translate variable(s) first before anyrotation variables.

Design Parameters that result from CAD-Client geometry import are alsolisted here. Supported CAD-Clients are STAR-NX, STAR-Works,STAR-Creo, STAR-ProE, STAR-Inventor and STAR-CAT.

Part Swapping

Parts can be variables if they have been created from an imported CADmodel. Only parts that have been imported directly into the parts tree willpopulate the parts for swapping drop down menu. Users will be able toidentify a list of CAD files to be used to replace the current part. User mustsupply at least two CAD files. Swapping a part that causes a mesh operationto return an invalid result will cause that specific analysis to fail.

With a part swapping variable, it is necessary to provide the execution CADdirectory.


12/40


If a NASTRAN file (*.nas) is selected, the simulation preferred length unit isselected as the import unit.

Motions

Motion variables are created from defined motions in the simulation file. Ifa user is using reference frames for boundary conditions the variables willnot be created. Users must create a motion and use the automaticallycreated reference frame as the boundary condition for the region. Variablescan be created from the following motion types:

• Rotation rate

• Translational velocity

Region Physics Values

The following region physics values that have their method set to‘Constant’ will have variables available:

• Volumetric heat source

Boundary Physics Values

The following boundary physics values that have their method set to‘Constant’ will have variables available:

• Velocity magnitude

• Mass flow rate

• Static and total temperature

• Static and total pressure

• Mach number

• Flow angles

• Mass fractions

• Wall roughness

• Turbulence scalars

• Thermal scalars

Flow Angles

Variations of inlet flow angles will attempt to modify a local Cartesiancoordinate system named ‘wind’. Users must create this coordinate system


13/40


in the original simulation file and align it so that flow with zero pitch angle,zero roll angle and zero yaw angle is aligned along the positive X axis.

Pitch, yaw and roll are defined as rotations about the Y,Z and X axisrespectively. All reports that should remain relative to the wind coordinatesystem should reference the ‘wind’ coordinate system.

Base Size

Mesh dependency studies can be performed by creating variables from thebase size in a mesh continua or automated mesh operation.

Field Functions

Variables can be created from user field functions in a simulation file. The

field function must be a scalar field function and its definition must be onlynumeric.

Examples of allowable definitions:

• 10

• -1.312

Field functions with invalid definitions will not appear in the field functionvariable drop down menu.

For use in Optimate, please ensure that the presentation name and thefunction name for the field function are the same.

Interface and Capabili ties Description

Optimate is split into five tabs: run mode, variables, outputs, assembly andrun. The tabs are arranged in order of how users should setup cases, startingwith the variables tab and ending with the run tab.

Run Mode Tab

This is where a user picks the run mode for the analysis. Users can selectfrom the following modes:

• Design Sweeps

• Optimization Using SHERPA


14/40


• Design of Experiments

• Stochastic Analysis

Depending on the ‘Run Mode’ selected, additional ‘Run Options’ areexposed to the user. A description of each ‘Run Option’ is given under each

‘Run Modes’ section.

In order to change the run mode after variables or outputs have beencreated, the variables and outputs will be cleared. The user will promptedbefore this action is completed.

Variables Tab

This is where a user identifies what variables in the simulation file shouldbe varied during the analyses. By choosing the applicable variable from a

drop-down menu and pressing the ‘Add’ button, it will be added to the listof variables to be modified. Once a variable is already added into the study,it will appear grayed out within the drop-down list.

Definit ion Mode

The next step is to define the values that will be used for that variable. Userscan select from the following modes:

• Minimum, Maximum, N

• Minimum, Maximum, Resolution/Increment

• List

• CSV File Column

• Value, Distribution

• Geometry Files

The exact modes that are visible will depend on the selected run mode andselected variable type.

Minimum, Maximum, N

Users will specify a minimum value, maximum value, and number ofincrements. For example, if a user specifies a minimum of two, a maximumof ten and five increments, a run will be completed for the values of two,four, six, eight, and ten.

When running in Optimization mode, this definition method must be used.The optimization algorithm will use the minimum and maximum value asbounds for the variable and select values between the two values.


15/40


Minimum, Maximum, Resolution/Increment

Users will specify a minimum value and maximum value. This mode isused for optimization and Design of Experiment modes where the searchalgorithms will be selecting the exact values to use between the provided

bounds. Users can also control discretization of the variable by specifyingthe resolution or increment value of the variable.

List

Users will supply a comma separated list of values to use. Optimate will runa case for each value in the list. This is useful if the values are not evenlyspaced.

CSV File Column

Users will choose a column from an imported CSV file. This file wasimported in the run mode tab. Once imported a user can choose a columnto supply values for a given variable.

This option is only available in Design Sweeps mode and cannot be used forpart swapping variables.

Value, Distribution

Users will define a distribution type and values for each variable. Duringrun time, input values will be chosen to fit the specified probably

distribution.

There are two distribution types available:

• Uniform distribution: The ‘Value’ field for the uniform distribution isthe mean value for the variable. The ‘Maximum Variation’ field is themaximum variable of the variable from the mean in either direction. Forexample, a ‘Value’ of 10 and a ‘Maximum Variation’ of 5 gives us avariable that is uniformly distributed for 5 to 15.

• Gaussian distribution: The ‘Value’ field for Gaussian distribution is themean value for the variable. The ‘Standard Deviation’ field is normal

standard deviation of the variable from the mean value.This option is only available in Stochastic Analysis mode.

Geometry Files

For variables created for part swapping users can specify geometry files toswap with the current part.


16/40


Removal of Variables

Variables can be removed by selecting it and right-clicking and selecting‘Delete’ or selecting the ‘Delete’ button.

Outputs Tab

This is where a user defines what outputs should be recorded during theanalysis.

Reports Recording

Reports from the simulation file can be recorded at the end of each analysisby Optimate. Reports can be added individually using the ‘Add’ button orall at once using the ‘Add All’ button.

The values used for the reports will always be in the units specified in thereport properties in the simulation file.

Recording Modes

Once a report has been added to the list of recorded reports, changing itsrun mode will change how the Optimate solver treats the value exportedfrom STAR-CCM+. The recording mode for each recorded report can be setto the following:

• Output

• Objective

• Constraint

Output

For this recording mode, the Optimate solver will only record the value ofthe report.

Objective

For this recording mode, the Optimate solver will use this report value to judge how this design is performing relative to previous designs. For eachobjective the user sets a goal, normalization and linear weight value. Thegoal can be set to ‘Minimize’ or ‘Maximize’. The normalization is importantif there are multiple objectives and it should be set such that all objectivesare the same order of magnitude. The ‘Use Baseline’ check-box can be usedto automatically set the normalization values for each variable by using thebaseline run. The linear weight is important if there are multiple objective


17/40


and determines how the objectives will be combined to determine theperformance of each design.

Constraint

For this recording mode, the Optimate solver will use this report value todetermine if this design is feasible or infeasible. If a particular set of inputscreates an infeasible design, the Optimate solver will avoid this part of thedesign space in subsequent analysis. For each constraint the user sets thetype and limit. The type can be set to ‘Less Than’ or ‘Greater Than’ and thelimit is set to the value which cannot be exceeded or below. For example, ifa user created a constraint based on a drag report, set the type to ‘Less Than’and the limit to 300, any analysis with a converged value higher than 300would be considered infeasible.

Import from RSM

If a response surface is being used as the source of the study, the check-boxfor ‘Import from RSM’ should be selected. This will open up a dialog toallow the user to select the response surface associated with that output.

Plots and Scenes Recording

Users can also define which plots and scenes should be saved at the end ofeach STAR-CCM+ run. Plots and scenes can be added individually usingthe ‘Add’ button or all at once using the ‘Add All’ button. The directory towhich the images are placed will be defined in the assembly tab.

Requirements

For all analysis at least one report must be recorded as either an output,objective or constraint. For cases run in Optimization mode, there must beat least one objective and for cases run in Pareto Optimization mode theremust be at least two objectives. It is recommended that objectives be definedfor Design Sweeps mode as the Optimate solver can sort the resultsaccording to the performance of the analyses.

Assembly TabThis tab is used to define how the STAR-CCM+ jobs will be run.

Simultaneous Jobs

This number defines how many jobs will be executed at once. This numbershould be as small as practical when running in Optimization mode. The


18/40


Optimate optimization algorithm (SHERPA) works best when it can learnas many times as possible. If you are running 100 cases in total in blocks oftwenty-five at a time, SHERPA can only learn three times. If you arerunning those same 100 cases in blocks of two, SHERPA can learn forty-ninetimes and can perform much better.

When a response surface is the source for a 2 level or 3 level full factorialDoE study, the number of simultaneous jobs is fixed to 1.

Cores per STAR-CCM+ Job

This defines how many cores each STAR-CCM+ job will be run on.

Macro Insertion Point

Allows the user to identify the desired insertion point for custom macros

into the StarDriver.java macro. The Insert Macro STAR-CCM+ Run Optionmust be selected to enable this portion of the Assembly Tab.

Before Meshing

Updates the Macros To Be Inserted list to display macros selected to beinserted immediately before the execute meshing pipeline command isexecuted in StarDriver.java.

Af ter Mesh ing

Updates the Macros To Be Inserted list to display macros selected to beinserted after the simulation mesh has been generated but prior to runningthe solver.

Af ter Running

Updates the Macros To Be Inserted list to display macros selected to beinserted immediately after the solver has been completed and before anyresults (reports, scenes, and plots) are returned to the Optimate solver.

Macros To Be Inserted

This list displays user selected macros to insert into the StarDriver.java fileat the location specified by the Macro Insertion Point selection. Users are tobrowse to the location of the desired macros and insert them into the desiredlist. The order that they are displayed in the list represents the order thatthey will be played in the specified insertion point. The same macro cannotbe played more than once at a given insertion point, but may be playedagain at a different insertion point. It is a requirement that any macro to beinserted meet all the requirements necessary to play a macro directly in


19/40


STAR-CCM+. For this reason it is recommended that even if the user iswriting their own macro they record a shell of it in STAR-CCM+ and modifythis file to reflect the full set of instructions. It is also recommended that theuser ensure their macro will execute manually in STAR-CCM+.

Remove Macro

This button removes the selected macro in the currently displayed MacrosTo Be Inserted list.

STAR-CCM+ Run Options

The following options will determine how STAR-CCM+ jobs are submitted,executed and saved.

Re-mesh Required

This will be checked if any variables were created from a design parameteror for part swapping.

Remove Invalid Cells

When selected STAR-CCM+ will execute the remove invalid cells commandon each individual job submitted. This is advisable if it is determined thatthe mesh settings in the base sim file might occasionally generate invalidmeshes. This is more likely for projects where widely varying geometriesare being generated and when the surface wrapping is being used on

complex geometry.

Convert to 2D

When selected the project will convert each submitted job into a 2Dproblem. All of the same restrictions for running 2D cases in STAR-CCM+apply when running Optimate analyses in 2D. The mesh must have a facealigned with the X-Y plane. The physics continua, interfaces, and reportswill automatically be updated to the appropriate forms for 2D simulations.Any scene selected in the output tab will automatically be updated such thatthe displayer parts are the newly created 2D regions.

Save all Simulation Files

When this option is activated the save command will be added toStarDriver.java macro which is executed for each simulation in the analysis.The result is that any star_0/Design/star/ (where N is the designnumber) directories retained by Optimate will contain the completed simfile and any other simulations file (e.g. *.trk) for that particular simulation.Note that if the simulation has the auto save batch runs activated in the


20/40


File>Auto Save menu then a sim file will be retained even if this option isdeactivated. It is advisable to check this setting (activated as default inSTAR-CCM+) before starting the project.

Clear Solution

Checking this box will clear the current solution in STAR-CCM+ beforerunning each case. By leaving this box unchecked STAR-CCM+ will use theexisting solution as a starting point which can significantly reduce theiterations required to reach a converged solution.

Insert Macro

Checking this box will activate the macro insertion portion of the AssemblyTab allowing the user to insert custom recorded or written macros into theStarDriver.java macro used to execute each STAR-CCM+ simulation.

Use Windows Queue

This allows Optimate to submit the jobs using a Windows Scheduler thatcan be configured in Tools > Configure Microsoft Cluster.

Use Linux Queue

This allows Optimate to submit the jobs using a generic queuing system thatcan be configured in Tools > Configure Linux Queue.

Optimate Save Option

Last Best Design

This option is only available when the Run Mode is set to eitherOptimization using Sherpa or Pareto Optimization using MO-SHERPA.When selected this option instructs the Optimate solver to remove alldesign directories with the exception of that identified as the best designbased on the specified objectives.

Save All Best

This option is only available when the Run Mode is set to eitherOptimization using Sherpa or Pareto Optimization using MO-SHERPA.When selected this option instructs the Optimate solver to remove alldesign directories with the exception of those that were identified as thebest design during the history of the project run. As an example the first runof an Optimization project will always be the first best design identified,subsequently as the Optimate solver identifies improved designs it will no


21/40


longer be the best design. With this option turned on however the directoryfor the first design will be retained because it was identified at one point asthe best design.

Al l Designs

When selected this option instructs Optimate to retain all design directories.

None

When selected this option instructs Optimate to remove all designdirectories after the outputs of a completed simulation (report values, plots,scenes) has been extracted.

Number of STAR-CCM+ Runs

The number of runs is determined by the number of variables and howmany values will be used for each variable in Design Sweeps mode. InOptimization mode, the value is set by the user based on how many casesthere is time to run. For a Pareto optimization problem at least forty casesmust be run. For 2 Level Full Factorial or 3 Level Full Factorial runs, thenumber of runs is determined by the algorithm and automaticallypopulated.

Check Frequency

This number determines how often Optimate checks each STAR-CCM+ job

to see if it has finished. By default it will check every 360 seconds but thisshould be modified according to the expected run times.

Maximum Run Time

This number determines how long Optimate will wait for one job to becompleted before submitting the next one. By default it will wait 360,000seconds before submitting the next job. This should be modified to be onlyslightly longer than the job should take to run, but it is important to keepqueue times and possible solver slowdowns in mind.

Tokens Required

Multiplying the number of simultaneous jobs by the number of cores per jobwill determine how many Power Tokens will be required to run. Please beaware that if using a cluster, this number will not reflect the correct amountof tokens unless you change the cores per STAR-CCM+ job to reflect thecommand provided in the queue configuration window.


22/40


Licensing Options

During run time, Optimate jobs will use with an Optimate or Optimate+license as well as the necessary licenses for starting STAR-CCM+ jobs. Inthis release, existing STAR-CCM+ license features can be used in additionto Power Tokens and the options below allow users to control how licenseswill be checked out.

Use Power Tokens

This is the default licensing scheme for Optimate. Optimate will check outPower Tokens for each STAR-CCM+ job based on the number of cores each job will be run on.

Use Serial and HPCs

This will allow Optimate to check out STAR-CCM+ session licenses andHPC licenses for each STAR-CCM+ run.

Use Power Sessions

This will allow Optimate to check out a Power Session for eachSTAR-CCM+ run.

Use Power on Demand

This will allow Optimate to check out a Power Session from the CD-adapcoFlexLM server. Users will be prompted for a Power-on-Demand key. Thelicense server is set to [email protected]. However, this can bechanged manually by modifying the ‘Process1.in’ file after building theproject.

Study Directory

This should be set to the directory where the project files are to be written.The project will run in this directory as well. If the case is to be run on aremote cluster, just this directory needs to be copied over.

The directory can be set by browsing the local file system or manually if therun directory is not currently mounted. Relative paths are acceptable whenmanually setting this directory.

CAD Directory

This only needs to be modified if a variable is created for a part swap. Bydefault, the directory is set assuming that the CAD files exist in the same


23/40


directory as the original simulation file. If this is not the case, the directoryneeds to be changed.


Image Directory

This should be set to the directory where the plot and scene images shouldbe saved. By default it will place all of the images in the same directory asthe original simulation file. It is recommended that a new directory iscreated for all of the images.


Macro Directory

This only needs to be modified if a macro has been selected for insertion intoStarDriver.java. And represents the location where STAR-CCM+ will go tofind all macros.


Build Study

Pressing the ‘Build Study’ button will write all the files necessary to executethe Optimate solver for the job defined in the previous three tabs. It will alsomodify and save the simulation file to allow the use of the Power Tokenlicensing scheme.

All of the files will be written to the same directory as the originalsimulation file. If running the job on a cluster, all of the written files must becopied to the cluster file system.

Run Tab

The run tab is used once the project has been built to start local jobs, kill local jobs, post-process, view the message file and run the baseline analysis.


24/40


Open HEEDS Post

Once a local job has completed, pressing the ‘Post Process’ button willlaunch HEEDS POST to post-process the results.

HEEDS POST can also be launched outside of Optimate to view the results.

Run

The run button gets activated once the study has been built. The run buttonitself has three options.

Run

The ‘Run’ will being the design exploration study by starting the Optimatesolver on the local machine.

Run Baseline

The ‘Run Baseline’ option runs the baseline design by itself. This can beused to ensure the robustness of the starting simulation.

CAD Robustness

This feature can be used to check the robustness of the CAD regeneration.Optimate will sample the design space using a Latin Hypercube samplingtechnique. Once a CAD Robustness is run/running, it can be post processed

by clicking on the ‘Open HEEDS Post’ button. In HEEDS Post, an objectivecalled ‘CAD Robustness Report’ is found. Any design with a value of 0 forthis report means that the design was unable to regenerate the CADcorrectly.

Stop

The stop button can be used to stop the Optimate study. It is important tonote that this does not kill the actual STAR-CCM+ jobs that have alreadybeen launched.

Pause/Resume

The pause button can be used to pause the Optimate study. The resumebutton continues the job from the paused state.


25/40


Share Design

This option allows the user to insert their own ‘design’ to the study. Adesign can be inserted into the study at any time during the run. This allowsthe user to study the current set of results and make a ‘best guess’ at a gooddesign. Optimate will then evaluate this design and use the results for therest of the run. The ‘Share Designs’ button opens up a panel that allows theuser to set values for each of the design parameters. This design will be runafter the set of current evaluations is complete.

Print Message File

Pressing the ‘Print Message File’ button will print the contents of theOptimate solver message file (Agent_Group_1.mes) to the output window.This file contains information about the Optimate job and can be useful fordebugging jobs that fail to start.

File Menu

The file menu includes the following options:

Save

This will overwrite the open .optm project file with the current project.

Save As

This option saves the Optimate project in a .optm file with a specified nameand location.

Exit

This will close down the Optimate interface, however the license that wasused to start Optimate will not be released until the server is shutdown.

Tools Menu

The tools menu can be used to control the external programs that Optimateis calling and to configure cluster setups.

Set Optimate Solver

This is used to set the Optimate solver executable for local jobs. Users willbe prompted to set this the first time Optimate is started and it can bemodified if needed.


26/40


Set HEEDS Post

This is used to set the HEEDS POST executable for launching HEEDS POSTfrom Optimate. Users will be prompted to set this the first time Optimate isstarted and it can be modified if needed.

Configure Microsoft Queue

This will bring up a window to setup the commands to run on a Microsoftcluster. The values should be modified to reflect the configuration that usersplan on running on.

Queue Submission Command

This is the system command to put a job in the queue. In almost all cases,this is going the be the default value of ‘ job submit’

Job Name Specifier

This is the command that is used to identify the name for each submitted job. This is the command line argument that allows the users to identify thename for each submitted job. In almost all cases, this is going the be thedefault value of ‘ /jobname:’.

Job Name Prefix

This is the prefix of each STAR-CCM+ job that is launched. The full name of

the job will be this prefix, appended by the evaluation numbercorresponding to that job.

STAR-CCM+ Execution Command

This is either the STAR-CCM+ command or the batch script used to launchSTAR-CCM+ on the cluster. It is important to provide the shared path of theexecutable for the full installation of STAR-CCM+.

Full Command

Shows the user a preview of the submission command that gets run.

Remote Execution

This check box toggles the remote execution run option. If remote executionis selected, a drop down box with the available remote profiles is available.More details on the remote execution option can be found under the‘Remote Execution’ section.


27/40


Configure Linux Queue

This will bring up a window to setup the commands to run on a genericqueueing system. The defaults reflect the commands to run on a Linuxcluster running OpenPBS. The values should be modified to reflect theconfiguration that users plan on running on. Two methods are nowavailable

Use Generic Scheduler

This method requires the following information

Job Submit

This is the command that is used to submit each job on the cluster. Thedefault value is setup for a cluster running OpenPBS where each job issubmitted on one node running four cores per node.

Please note that modifying the number of nodes per job and cores per nodewill not affect the number of Power Tokens displayed in the assembly tab.However, it will affect the number of Power Tokens required to run.

Job Name Specifier

This is the command that is used to identify the name for each submitted job. The default value is setup for a cluster running OpenPBS.

Command to Execute STAR-CCM+

This is the command that is given for each submitted job. By default each job will be started by executing the contents of the shell script‘./ccmprun.csh’. This shell script needs to be created by the user for aspecific machine. Requirements for the contents of the shell script can befound here.

Direct Parallel Execution

This method requires the following information:

Command to submit job to cluster

This is the exact command that a user would enter into the command line tostart a STAR-CCM+ simulation minus any files associated with thesubmission. Typically this will be the command to submit to a job scheduler.As an example a user might directly launch STAR-CCM+ via the commandline which could include

starccm+ -np 3 -batch StarDriver.java


28/40


followed by the simulation file. The above command would be entered intothe Command to submit job to cluster text box. Alternatively a user mightuse a scheduling tool and a script to submit a job. In this case everything butthe script file itself is included in the Command to submit job to cluster textbox. As an example using OpenPBS the user would include

qsub -l nodes=1:ppn=8

in the Command to submit job to cluster text box.

Run Script

This is the name of any file needed in addition to the command given theCommand to submit job to cluster text box. For the first example above thisbox would contain

.sim

with the appropriate simulation file name. For the second example it wouldcontain the run script name. The file specified here is copied from the projectdirectory to the directory created by Optimate to launch the individualdesign variant. The complete command executed by Optimate from thisdirectory is the combined command from both this box and the Commandto submit job to cluster text box.

Remote Execution

This check box toggles the remote execution run option. If remote executionis selected, a drop down box with the available remote profiles is available.

More details on the remote execution option can be found under the‘Remote Execution’ section.

Manage Remote Profiles

This panel allows the user to manage remote profiles that can be used in theremote execution run mode. For more details on how remote executionworks, please refer to the ‘Remote Profiles’ section of the documentation. Aremote profile contains information about the remote machine on whichevaluations can be run on. The list on the left side of the panel allows theuser to add or remove distinct remote profiles, so that different remote

machines can be used easily. The following data is needed to create a remoteprofile:

• Remote Host Type: Select the operating system environment for theremote machine

• Profile Name: The name to store the remote profile as in Optimate

• Remote Host Name: The name of the remote host. Include the domainif it is needed to connect from your local machine


29/40


• Remote User Name: The user name needed to log in to the remotemachine. A password free ssh must also be set up to this user accounton the remote machine

• Shared Drive: Tick this option if your local workstation shares the samedrive with your remote machine. i.e., both local and remote machines

can access the same files.• SSH Command: The command used to ‘ssh’ from the local machine to

the remote machine

• SCP Command: The command used to ‘scp’ (copy files) from the localmachine to the remote machine

Options

The ‘Options’ option opens up the ‘Options’ pane where the followingsettings can be specified:

Optimate Options

• Always On Top: Checking this option will tell the Optimate frame tosite in front of all other windows. This can be useful because Optimatewill fall to the back if the mouse is moved over a plot or scene inSTAR-CCM+ and when a local job is started. Note, that this optionshould not be selected when browsing to files and directories as theOptimate frame will remain on top of the File chooser window. Thisoption will be remembered when Optimate is started in the future.

• Use External Optimizer: Checking this option will choose the Use

External Optimizer run mode. All current variables will be cleared andthe user can pick the new variables and outputs for the study. The runmode tab is grayed out since that is selected on the external optimizerside.

• Hide Messages: By default, messages related to incorrect inputs andexecution errors will create pop-up menus that the user must close. Ifthis box is checked, the messages will instead be printed to theSTAR-CCM+ output window. This option will be remembered whenOptimate is started in the future.

• Power Session Core: By default, the core STAR-CCM+ license for the

design exploration study is a serial license (ccmpsuite). This optiongives Optimate permission to use a power session in the event that aserial license cannot be found.

CAD Robustness Study Options

• Sampling Intensity: This slider controls the number of samples that arerun for a CAD Robustness study. The higher the sampling intensity, thegreater the number of samples picked throughout the design space.


30/40


• Concurrent Runs: Controls the number of CAD Robustness evaluationsrun in parallel.

STAR-CCM+ Command Line Options

The user can specify any additional command line arguments for launchingeach STAR-CCM+ evaluation (eg. -dp for double precision). By default,Optimate picks power tokens before selecting HPC’s for each additionalCPU within an evaluation. To modify licensing behavior to prefer HPC’sover power tokens, the ‘-doe-prefer-hpcdomains’ flag should be used.

Help Menu

Optimate User Guide

This user guide is opened up through this menu item.

Tutorials

The documentation for all the Optimate tutorials is found under thissub-menu.

Running Jobs

Optimate can setup cases to run locally on the same machine that is settingup the job or on a cluster.

STAR-CCM+ is called with the following command on Windows:

starccm+.exe

or on Linux:

starccm+

In order for the above commands to work, the path environment variablemust be set to launch the correct version of STAR-CCM+. The full path can

be inserted into the ‘Process1.in’ file if it is not possible to change the path.

Running the Baseline Model

The baseline model can be run either directly from the run tab using the‘Run Baseline Model’ button or the command can be copied and pasted toa command prompt. This is useful if the model needs to be run using PowerTokens as the necessary command line flags are shown.


31/40


Local Jobs from Optimate

Local jobs can be start through Optimate using the ‘Start Local Job’ buttonin the run tab.

Optimate must be open to start a local job. If the project is being built in thesame session, this is straightforward. If the project has already been built inanother session, users will need to load the original simulation file again,start Optimate, navigate to the run tab, and press the ‘Start Local Job’button. The project will not need to be built again.

If the previous Optimate job did not exit correctly, users will be promptedto delete the lock file. The extension of the ‘UserDesigns0_Initialize’ will bechanged from ‘.in_backup_at_0_evals’ to ‘.in’.

Local Jobs in Batch

Jobs can also be submitted in batch by executing the Optimate solver fromthe command line. Users will need to navigate to the directory that containsthe original simulation file and the project files.

If the previous Optimate job did not exit correctly, users will need to deletethe lock file named ‘star0.lock’ and also change the extension of the‘UserDesigns0_Initialize’ file back to ‘.in’.

Linux

On Linux machines, execute the following command:

PATH_TO_OPTIMATE/optimate/Ver2014.06/LX64/solver/Optimatei=Agent_Group_1.in overwrite skipEvalCheck

Substitute the path to reflect the local installation.

Windows

On Windows machines, execute the following command:

PATH_TO_Optimate/optimate\Ver2014.06\Win64\solver\Optimat

e.exe i=Agent_Group_1.in overwrite skipEvalCheck


Remote Execution

For large cases where the STAR-CCM+ evaluations need to be run on aremote workstation or cluster, the remote execution option is the preferred


32/40


method. The remote execution option runs Optimate on the localworkstation, and sends STAR-CCM+ data to and from the remoteenvironment. Functionally, this means that the user can set up andeffectively run Optimate locally, while the STAR-CCM+ jobs areautomatically run on a separate workstation or cluster.

Requirements for running a remote execution study

• The user needs to have password free SSH set up between the local andremote machines. For detailed instructions on how to set this up, pleasecontact your dedicated support engineer.

• For the duration of the study, the local machine cannot be restarted orshut down.

Creating a remote profi le

The user first needs to create a remote profile, which stores all theinformation about the remote machine. Remote profiles can be managed byclicking on ‘Tools -> Manage Remote Profiles’. Details about managingremote profiles can be found in the ‘Manage Remote Profiles’ section. Oncea remote profile is created, it is stored so that it can be used for futurestudies.

Placement of required scr ipts

When running in remote execution mode, all files need to exist on the localmachine first, so they can be transferred over to the remote machine as

necessary. Therefore, the script used to launch Optimate on the remoteworkstation also needs to be placed in local directory where the project isbuilt.

Generic Queue Cluster Jobs

To submit jobs on a cluster with a generic queuing system, all of the projectfiles must be copied to the user’s run directory on the cluster file system. TheOptimate solver must be installed on the cluster as well as the correctversion of STAR-CCM+.

When setting up a generic queue case, Optimate will create an additionalfile named ‘optimate.txt’. The file contains an ID flag that must be passed toSTAR-CCM+ to access the Power Token licensing scheme. This ID must beincorporated into the c-shell script that is used to call STAR-CCM+ that isidentified in the setup. For example, a variable is created as follows:

set UUID=‘cat optimate.txt‘


33/40


This variable is passed to STAR-CCM+ via the command line option:

-doeuuid $UUID

Optimate is also creating the batch script to run STAR-CCM+. The name ofthis file is ‘StarDriver.java’ and this also needs to be passed to STAR-CCM+

via the command line option:-batch StarDriver.java

By default, Optimate will submit a job that executes the followingcommand:

./ccmprun.csh

At a minimum, the called cshell script should contain:

#!/bin/tcsh

set UUID=‘cat optimate.txt‘

starccm+ -doeuuid $UUID -batch StarDriver.java -np 2test.sim >>& test.log

It is likely that this will need to be appended to include machine informationrelated to the specific cluster being used. It should also be noted that thecommand that executes STAR-CCM+ is back-grounded. This is necessaryfor the Optimate solver to function correctly.

Optimate requires the following environment variables need to be set:

PYTHONHOME=PATH_TO_Optimate/optimate/Ver2014.06/Python27HEEDS_ROOT=PATH_TO_Optimate/optimate/Ver2014.06/LX64/solv

erLD_LIBRARY_PATH=PATH_TO_Optimate/optimate/Ver2014.06/LX64;PATH_TO_Optimate/optimate/Ver2014.06/LX64/solverPATH=PATH:PATH_TO_Optimate/optimate/Ver2014.06/LX64

When submitting the job on the cluster directly (without remote execution),use the following command on the head node of the cluster:

PATH_TO_OPTIMATE/optimate/Ver2014.06/LX64/solver/Optimatei=Agent_Group_1.in overwrite skipEvalCheck


Microsoft Queue Cluster Jobs

To submit jobs on a cluster with a Microsoft queuing system, all of theproject files must be copied to the user’s run directory on the cluster filesystem.


34/40


Optimate requires the following environment variables to be set:

PYTHONHOME=PATH_TO_Optimate\optimate\Ver2014.06\Python27HEEDS_ROOT=PATH_TO_Optimate\optimate\Ver2014.06\Win64\solverLD_LIBRARY_PATH=PATH_TO_Optimate\optimate\Ver2014.06\Win64;PATH_TO_Optimate\optimate\Ver2014.06\Win64\solverPATH=PATH:PATH_TO_Optimate\optimate\Ver2014.06\LX64

When submitting the job on the cluster directly (without remote execution),use the following command on the head node of the cluster:

PATH_TO_OPTIMATE\optimate\Ver2014.06\Win64\solver\Optimate.exe i=Agent_Group_1.in overwrite skipEvalCheck


Resuming Jobs

If a job aborts for any reason and needs to be resumed, the job can be startedand will pick up from the last completed design using the followingcommand line:

PATH_TO_OPTIMATE/optimate/Ver2014.06/LX64/solver/Optimatei=Agent_Group_1.in useHistory skipEvalCheck

Note: this can only be done from the command prompt and not via theOptimate interface.

Extending Jobs

If a job completes but further designs are needed to achieve the desiredresults, the job can be continued. First, the number of jobs must be increasedin the ‘Agent_Group_1.in’ file. An example of the lines to be modified isshown below:

$Start Agent ID, End Agent ID, Number of Designs Evaluated

0, 0, 20

The number is set to the ‘Number of Designs Evaluated’ should be modifiedto the number of additional runs that are needed. In the followingmodification, 10 additional designs are requested.

0,0,10

Modify the end of the file to include an *EXTENDING command rightbefore the *END command as follows:

*EXTENDING


35/40


*END

The file is then saved and the following command is given to extend the job:

PATH_TO_OPTIMATE/optimate\Ver2014.06\Win64\solver\Optimate.exe i=Agent_Group_1.in

Note: this can only be done from the command prompt and not via theOptimate interface.

Post-Processing

Once a series of jobs have completed the results can be post-processingeither further in STAR-CCM+ or using HEEDS POST.

STAR-CCM+

If a user selected to save all simulation files, individual simulation files canbe found in the following directories:

star_0/DesignN/star/

Where N is the design ID for each job. Each simulation file will be appendedwith a three digit design ID so that they can all be copied into the samedirectory for archiving but still reference the ID for post-processing inHEEDS POST.

HEEDS POST

HEEDS POST can be started from Optimate or outside of Optimate.

• HEEDS POST can be accessed from within Optimate by clicking on the‘Post-Process’ button in the Run tab. This will automatically load thestudy that is running, or just finished running within Optimate.

• To import an existing study in HEEDS POST, select ‘File -> Open’ andthen select the *.optm file. If your study results do not get imported

automatically, click on the ‘Refresh Study Data’ button in the topribbon.

• If the study is moved to a new folder, the association needs to be reset inHEEDS Post. To re-associate the study folder, right click on the studyname in the tree and select the ‘Find Study Folder’ option. Thennavigate to the study folder and accept.


36/40


Please refer to the HEEDS POST documentation for more information. Thiscan be found in the installation directory of HEEDS POST.

File Descriptions

The file descriptions are given below to aid in debugging cases that are notexecuting as expected.

Built Projects

When an Optimate project is built, the following files can be found in thesame directory as the simulation file.

Agent_Group_1.in

This file contains information about the run mode and the number of runsto be completed.

Assembly.in

This file contains information about the run mode.

Definitions.in

This file contains information variables that will be changed at run time. Thename of the variable, the minimum value, the maximum value and thebaseline value can be found here.

M_{SIM FILE NAME}.in

The file tells Optimate how to modify the input file for each run such thatSTAR-CCM+ runs using the updated variable values.

Performance0.in

This file contains information about the outputs, objectives and constraintsfor each project and tells Optimate where it can find these values after eachSTAR-CCM+ job has completed.

{SIM FILE NAME}.in

This file contains the variable names and values that will be read bySTAR-CCM+ at run time. This file is copied to the design directory at run,modified with the new values by Optimate and the STAR-CCM+ batch


37/40


script will read this file and update the fields in STAR-CCM+ beforerunning the analysis.

{SIM FILE NAME}.out

This file is written by each STAR-CCM+ job at completion and contains thevalues of the outputs that will be read by Optimate. If the STAR-CCM+analysis does not complete successfully, this file will not be written andOptimate will mark the analysis as a failure.

Process1.in

This file contains the command to start each STAR-CCM+ analysis (eithervia a queuing system or directly), information about how often to check forcompletion and the named files to by copied into each design directory.

Representation0.in

This file contains information about the resolution of each variable.

StarDriver.java

This is the batch script that each STAR-CCM+ job will execute. It isresponsible to reading the input file, adjusting parameters in STAR-CCM+,remeshing if necessary, running the analysis and exporting the results.

UserDesigns0_Initialize.in

This file is only written for analysis run using Design Exploration mode. Itcontains the value of each variable to be used for each STAR-CCM+ job.

Running and Completed Projects

The following additional files can be found in the directory where areproject is running or has completed.

Agent_Group_1.mes

The file is the output from the Optimate process and contains informationabout when each STAR-CCM+ job is started and completed. If there are anyerrors parsing the other input files, a detailed message can be found here.

star0.gph star0.hst star0.res star0.rpt

These are the post-processing files that are loaded into HEEDS POST. If aproject is run on a computer that does not have HEEDS POST, these four


38/40


files and the ‘star0.hds’ file must be copied to the machine with HEEDSPOST.

star_0/

This directory is created at run time and contains all the design directories.

Debugging

Information regarding failed jobs can be found in the files written byOptimate and STAR-CCM+.

Message File

During an Optimate run, Optimate is always writing to the‘Agent_Group_1.mes’ file. This file is in the directory with the originalsimulation file. If there are any errors parsing the project files written byOptimate it will be documented here. These errors can include:

• Licensing error

• Check CDLMD_LICENSE_FILE variable

• Ensure license server is running

• Error executing STAR-CCM+

• Check command in ‘Process1.in’ file

STAR-CCM+ Log Files

During an Optimate run, Optimate is creating directories for eachSTAR-CCM+ job. The directory for each run can be found in the directorynamed:

star_0/DesignN/star/

Where N is the design ID of each job starting at one and ending with the

number of jobs to be run. If the ‘Save all Simulation Files’ box is checked,these folders will not be deleted and will persist after the run is complete. Ifthe box is unchecked, these directories will only persist during the run.

If any job fails it will be placed in a directory named:

star_0/DesignN-ERROR/star/


39/40


The above directories will contain all of the input files, outputs files, a logfile, and the simulation file for each run. If STAR-CCM+ fails, an errormessage will be in the ‘star.log ’ file. Errors can include:

• Error getting appropriate licenses

• Change number of simultaneous jobs in ‘Process1.in’ file

• Change number of core per STAR-CCM+ job in ‘Process1.in’ file

• Check CDLMD_LICENSE_FILE variable

• Ensure license server is running

• Error modifying 3D-CAD model

• Change values to avoid invalid geometry

• Error meshing

• Check mesh settings in original simulation file

• Floating point error• Review solver settings

• Review initial conditions from original simulation file

• Error importing CAD files

• Check directoryCAD variable in ‘StarDriver.java’ file

• Error exporting scenes

• Check directoryPOST variable in ‘StarDriver.java’ file

• Error saving simulation file

• Check for specific cause at end of log file

• Incompatible version error

• The path environmental variable needs to be modified such that thecorrect version of STAR-CCM+ is listed first in the path

HEEDS Post

If HEEDS Post fails to open or does not work as expected, the use can takea look at the HEEDS Post log file for further information. The log file is

called ‘HEEDSPost.log’ and is created in the user’s home directory.

Known Issues1. If a job fails due to a licensing failure, Optimate will continue to wait for

this job to complete. Optimate will wait until the maximum time isreached before submitting the next job.


40/40


2. When restarting a ‘Design Sweep’ study, the‘UserDesigns0_DesignSweep.in_backup_at_0_evals’ file needs to berenamed to ‘UserDesigns0_DesignSweep.in’. Not doing so will lead tothe design sweep variables not respecting the specific list of valuesspecified.

3. All of the licensing options cannot be selected at the same time.Specifically, power sessions and serial/HPC licenses cannot be selectedtogether. A combination of either one with power tokens is a validcombination (eg.: power sessions & tokens OR serial/HPC’s & tokensare valid). The currently invalid combination is planned to beimplemented in future releases.

4. Optimate Frame will fall behind STAR-CCM+ window when the mousehovers over an open STAR-CCM+ scene. The ‘Always On Top’ optionin the File menu prevents this from happening, but the Optimate Framewill now prevent file browsing, and message widows from Optimatefrom being on top of itself.

5. When choosing variables from a .csv file, each variable should beassigned by selecting the relevant column from the drop down box inthe Variables tab. Any automatic association created by Optimate ispurely coincidental and the association is not reflected for the actualstudy.

6. For every field function variable, please ensure that the function nameis the same as the presentation name for the field function.

optimate904ncfgj_userguide

Documents