Task Manager | Summary and Preferences

The Task Manager (accessed from the HYPERSIM Ribbon) enables visualization of network tasks to be simulated in several cores, and processing of manual task programming on processors.

Below. the Task Manager window with input fields.

Preferences

Preferences contain editable parameters which have an impact on task mapping.

Preference	Description	Python API preference name
Time Step	Simulation time step defined by the user	`simulation.calculationStep`
Performance factor	The performance factor is used to calculate the execution time step based on the user-defined time step. Execution time step = performance factor * simulation time step.	`simulation.performance`
Processor load level	Set the maximum processor load considered during task mapping (value between 0 and 1).	`simulation.procLoadLevel`
Processor reservation mode	Optimization for multi-user usage. Dynamic CPU reservation can enhance performance 1 → Dynamic 2 → Dynamic and Static 3 → Static	`simulation.taskMappingMode`

Additionally, to improve performance, simply uncheck the 'Legacy Task Mapper' option and enable the new automatic task mapper, which is built on the Scotch library.

Preference	Description	Python API preference name
Use legacy task mapper	Not recommended: If selected, the task manager will use the legacy task mapper. Note: The legacy task mapper is automatically activated if the `mapping.useBeta` preference is set to false.	`mapping.useBeta`
Mapping strategy	Select task mapping strategy: load balancing (Balance) or minimizing communications (Quality).	`mapping.strategy`
Processor imbalance ratio	Load balancing target for the task mapper. The value ranges from 0 to 1, with 1 representing perfect balance.	`mapping.procImbalanceRatio`
Requested # of processors	The number of processors specified by the user for the task mapper. If set to the default value of 0, an optimized number will be automatically determined. If the number of processors requested by the user exceeds the available hardware, then all physical cores will be reserved by the task mapper.	`mapping.requestedProcs`