Job Progress Window

This dockable window displays details of the progress of a job.

Examples of job types include simulation, TSD update and mesh generation, and for InfoWorks network only, alert generation and manifest run.

The window toolbar contains a set of tools for controlling the initialisation and execution of that job. By default, the Job Progress Window will cycle automatically through the currently submitted jobs. See the Job Control Window topic for details of how this cycling is controlled.

Tip: This window is shared by both the Job Control window and the Server Job Control window. This means that, for example, the status of manual and automatic simulation jobs currently being run can be viewed on the Job Progress window.

To open the window, select Job Progress window from the Window menu.

Job Progress window toolbar

The following commands are available from the toolbar:

Toolbar icon Function

Stop initialising

Stop finding initial steady state of a network and start simulating.

Continue

Only enabled when the current job is paused.

Resume the execution of the job.

Only available for simulation jobs

Pause

Pause the job.

Only available for simulation jobs.

Step

Only enabled when the current job is paused.

Carry out the next time step in the job.

Only available for simulation jobs

Change Duration

Only enabled when the current job is paused.

Displays the Change Duration dialog.

Allows the maximum duration of the current job to be changed.

Only available for simulation jobs

Stop

Stop job and save results (status will be Completed).

Only available for simulation jobs

Cancel

Stop job without saving results (status will be Failed).

Job Progress window description

The following information regarding the current simulation is displayed in the Job Progress Window:

Simulation The simulation currently being processed.

Run

The title of the run being processed.

Network

The network for which the simulation is being run.

Activity Progress messages displaying current activity, loading networks, initialising etc.
Total(s)

Inflow and outflow profiles during the simulation.

Duration

The total period in minutes to be covered by the run.

Elapsed

The amount of time that has elapsed so far during the simulation.

Rainfall

The rainfall intensity at the elapsed time.

Surcharged

The number of pipes that were surcharged at the elapsed time.

Flooded

The number of nodes that were flooded at the elapsed time.

Timestep(s)

The timestep (in seconds) being used in the calculation at the elapsed time. If a stable solution cannot be found, the timestep will be halved and the calculation will be performed again. This process is repeated until either a stable solution has been found or the timestep has been halved a specified number of times. The timestep is restored to its original value for the next stage in the simulation.

Iterations

The number of iterations performed so far for the current timestep.

Link fail H

The last link where a stable solution could not be found for the level calculation. The failure of a link at a particular time is not a problem providing that the simulation as a whole does not fail. The link will be displayed here until the simulation is complete or another failure has occurred.

Link fail Q

The last link where a stable solution could not be found for the flow calculation.

Node fail

The last node where a stable solution could not be found.

Inflow

The inflow value at the elapsed time.

Outflow

The outflow value at the elapsed time.

Minimum 2D timestep

For each element in a 2D zone, the timestep required in order to achieve stability is calculated using a Courant-Friedrichs-Lewy condition.

Each zone is assigned the minimum calculated timestep of all of its elements.

The Minimum 2D timestep is the minimum timestep of all the 2D zones in the network.

2D Zone ID

The 2D zone for which the Minimum 2D timestep was calculated.

Useful for checking which areas are responsible for limiting the speed of the run.

Element ID

The 2D zone element for which the Minimum 2D timestep was calculated.

Useful for checking which areas are responsible for limiting the speed of the run.

Wet area

The total area of all the elements in a 2D zone whose depth is above the depth tolerance.

Inundated area

The total area of all the elements in a 2D zone whose depth is above the inundation threshold.

Max wet area

The total area of all the elements in a 2D zone whose depth has been above the depth tolerance at some point during the simulation.

Max inundated area

The total area of all the elements in a 2D zone whose depth has been above the inundation threshold at some point during the simulation.

2D volume

The total water volume for all the elements in a 2D zone.

2D volume error

The total of volume errors accumulated during a simulation for all the elements in a 2D zone.

2D rainfall

Average rainfall falling onto 2D elements during the last run time step. i.e. total rainfall volume divided by the area of all the elements in the 2D zone.

2D average inflow

Average inflow into a 2D zone during the last time step.

2D average outflow

Average outflow from a 2D zone elements during the last time step.

WQ step

Shows which Water Quality solver is being used. The possible values are:

  • node
  • link
  • erosion
  • source
WQ iteration

The number of iterations performed so far for the current timestep (Water Quality).

WQ node fail

The last node where a stable solution could not be found (Water Quality).

WQ change

Change in concentration during initialisation period (Water Quality).

WQ solving

The name of the sediment fraction or determinant the solver is currently working on.

GPU status

A suitable GPU card can be used to improve performance of 2D simulations.

Note: When using a GPU card for carrying out 2D calculations, it is recommended that the latest available NVIDIA driver for the GPU card is installed.

The GPU status indicates whether the GPU is being used or not. Possible values are:

  • Not in use
  • Active