When viewing an evaluator's details, the Properties tab displays detailed information about the evaluator.
Properties are grouped into the following categories: General, Compute Resources, Runtime Context, File Management, and Applications.
Most properties are read-only as they were set when the evaluator was configured. Some properties are configurable.
General
- Name
A user-friendly name to identify the evaluator.
- Username
The username of the account used to log in to the evaluator.
- Hostname
Name of the machine on which the evaluator is hosted, as seen by the network.
- Id
Unique ID that identifies the evaluator.
- Host Id
A 36-character alphanumeric string used to identify the host (also known as UUID).
- Platform
Operating system (Linux or Windows) of the machine on which the evaluator is hosted.
- Loop Interval [s]
The frequency in seconds at which the evaluator contacts Ansys HPC Job Manager looking for tasks to evaluate.
- Last Seen
Last time that this evaluator ran an evaluation.
- Task Manager Type
Task manager that is executing or submitting compute tasks.
- Project Assignment
Where projects are assigned.
- Assigned Projects
The projects to which the evaluator is assigned. While the default is All Active Projects, an evaluator can be assigned to specific projects.
- Version
The evaluator's build version. Click
to view build information.
Compute Resources
- Num Cores
Number of CPU cores that the evaluator has.
- Max Num Parallel Tasks
Maximum number of tasks that the evaluator can run in parallel.
- Memory
Total amount of memory (RAM) that the evaluator has.
- Disk Space
The amount of data that can be stored on the evaluator's drives.
Runtime Context
- Machines List
List of hosts on which applications can run.
File Management
- Working Directory
The directory to which temporary data is written when computations are performed.
- Local File Cache
Whether to store temporary data in a cache on the local system. When enabled, this can reduce network traffic and improve performance.
- Max Cache Size [MB]
The maximum amount of space in megabytes which the local file cache is allowed to consume.
- Task Directory Cleanup
If and when task working directories are cleaned up. Choices are:
Always. (default) A task's working directory is always cleaned up, regardless of the task's outcome.
On success. A task's working directory is only cleaned up if the task completes successfully.
Never. Task working directories are never cleaned up and remain in place until manually cleaned up.
Applications
This pane displays the Ansys applications that are available on the resource. By default, Ansys applications are automatically detected. For each application you can view the following properties:
- Name
Name of the solver application.
- Version
Version of the solver application.
- Installation Path
Path to the application's installation directory.
- Executable
Path to the application's executable file.
Note: On a Linux evaluator that is set to automatically detect the Ansys installation,
Ansys applications are not displayed in the Applications list if
the applications are installed in a location that cannot be automatically detected. On
Linux, Ansys applications are automatically detected if installed under
/ansys_inc or /user/ansys_inc folders or using
the AWP_ROOTXXX environment variables.
Administrators can manually add applications to the evaluator configuration if necessary. See Manually Adding Applications to an Evaluator's Configuration in the Ansys HPC Platform Services Deployment Guide.