HFSS15: Job outcome

Job status: The exit code of job doesn’t indicate success or failure correctly. The error messages from multiple log files needs to be combined to determine the reason for failure. In many situations, the reason for a failure is apparent only after re-running the job after turning ON the 'debug logging'

In some LINUX scenarios, the analysis appears to finish successfully with valid results, except that the exit code is ‘134’. In this case, although the exit is abnormal, the failed exit code can be ignored

Load Balancing: For models with 'unbalanced variations table' (i.e. variations that take considerably different amount of time to solve are clustered in few regions of table), job will take longer time to solve than a Regular DSO as the job's overall completion time is determined by the slowest solving region.

Workaround: rearrange the rows in the parametric table so that each region takes a similar time to solve

GM Specifics: the model used for ‘Report-based extractor’ jobs is NOT compatible with the ‘ANSYS-extractor-for-GM’ jobs. A valid model for ANSYS-extractor-for-GM cannot contain any of: reports, overlay plots, optimetrics calculations.