• 易迪拓培训,专注于微波、射频、天线设计工程师的培养
首页 > HFSS > HFSS help > HPC Task Properties

HFSS15: HPC Task Properties

录入:edatop.com     点击:

In general, each job consists of one or more tasks. For Ansoft batch analyses run as Windows HPC jobs, the job contains one task to control the analysis. This task is equivalent to the ANSYS EM Desktop GUI, which controls the analysis when running in interactive mode. The properties of this task must be set correctly for analysis to be successful.

Some of the main task properties are:

• Task Name - text string that may be used to identify or describe the task

• Working Directory - Working directory where the task is started

• Command Line - The command line executed to start the task

• Minimum and maximum number of computing resource units for the task (The unit type is the same is the job unit type.)

Of these properties, the Command Line is particularly important. We recommend using the Ansoft Submit HPC Job dialog to submit jobs because this dialog will assist you in creating a valid task Command Line. If you use one of the other methods, you must specify the complete command line for the Desktop task. See Setting the Command Line discussion below.

For Ansoft Jobs, all the compute resource requirements are specified at the job level. At the task level, the minimum and maximum computing resource units should be set to one if the resource unit is 'Node'. For any other resource unit, set the minimum/maximum resources units to the amount of multi-processing per distributed engine, i.e. "Number of Processors, Distributed". The Desktop task will start additional tasks and child process, if needed, to complete the analysis.

Setting the Command Line

The examples in this section use the HFSS product. The command lines for other products are similar.

The task executable should be specified as described in the Installation of Ansoft Tools examples. The project file should be the last argument in the command line, and it should be specified as described in the Ansoft Project File and Project Directory examples. The other command line arguments should be selected to start the analysis as a batch job.

For Ansoft Jobs, all the compute resource requirements are specified at the job level. At the task level, the minimum and maximum computing resource units should be set to one, if the resource unit is 'Node'. For any other resource unit, set the minimum/maximum resources units to the amount of multi-processing per distributed engine i.e. "Number of Processors, Distributed". The Desktop task will start additional tasks and child process, if needed, to complete the analysis.

Example Command Lines:

Command Line that analyzes an HFSS project serially:

"C:Program Files (x86)AnsysEMHFSS15.0hfss.exe" -ng -local

-batchsolve \shared_driveprojsOptimTee12.hfss

Command Line that analyzes HFSS project serially and monitors analysis progress that is printed to

stdout/stderr: "C:Program Files (x86)AnsysEMHFSS15.0hfss.exe" -ng -monitor -local -batchsolve \shared_driveprojsOptimTee12.hfss

Command Line that uses four cores for multi-processing of analysis:

"C:Program Files (x86)AnsysEMHFSS15.0hfss.exe" -ng -monitor

-local -batchoptions

"'Hfss/Preferences/NumberOfProcessors'=4"

-batchsolve \shared_driveprojsOptimTee12.hfss

Command Line that runs four distributed engines, on compute units allocated by the HPC Scheduler:

"C:Program Files (x86)AnsysEMHFSS15.0hfss.exe" -ng

-monitor -distributed -machinelist num=4

-batchsolve \shared_driveprojsOptimTee12.hfss

Command Line that runs four distributed engines, with each engine using four cores for multi-processing:

"C:Program Files (x86)AnsysEMHFSS15.0hfss.exe" -ng -monitor

-distributed -machinelist num=4 -batchoptions

" 'Hfss/Preferences/NumberOfProcessorsDistributed'=4

'Hfss/Preferences/NumberOfProcessors'=4" -batchsolve

\shared_driveprojsOptimTee12.hfss

HFSS 学习培训课程套装,专家讲解,视频教学,帮助您全面系统地学习掌握HFSS

上一篇:Working with the History Tree
下一篇:Working with the Menu Bar

HFSS视频培训课程推荐详情>>
HFSS教程推荐

  网站地图