HFSS15: Testing Your Scheduler Integration

One way to test these functions is to run the analysis for an ANSYS EM product in batch mode. When running in batch mode, a batch log file is created in the same directory as the project file. The batch log file has the same base name is the project file, with an extension of ".log". For example, if the project file is TestProject123.hfss, then the batch file is TestProject123.log. The batch log file contains useful information about the analysis run.

See the product specific help for details on running the product in batch mode, and for the command line options to use for distributed analysis.

• Testing IsProductLaunchedInYourEnvironment

• Testing GetSchedulerDisplayName and GetThisJobID

• Testing GetTempDirectory

• Testing GetMachineListAvailableForDistribution

• Testing LaunchProcess

• Testing GetUseRsmForEngineLaunch