The simulation job
The execution of the simulation by the simulator is referred to as the simulation job. The simulation job is an encapsulation of a single execution of a reservoir simulator. There is a one-to-one correspondence between a simulation case and a job. That is, a simulation case can only have one job running at a time. Once the job finishes, a new simulation job can be created and run for the simulation case.
The simulation job runs locally, using the version of the selected simulator installed on your machine to complete the job. Unless explicitly canceled, the job continues until completion, or until failure if an error is encountered, even if the application is closed. When the job successfully finishes, and if it was not a scheduled start, it signals the application to load the results (plot, map and output report). If a job does not execute successfully, you can review the Simulation log for details.
The simulation job can be started either from the Case Explorer pane or from the Running Simulations form of the simulator you are using. As the simulation job runs, it advances through a number of stages. The active stage of the simulation job is reported in various places: the simulation case tree, the simulation log and the Job Explorer, which can be accessed via the Panes menu in the upper-right corner of the application. The various job stages that are normally seen during a simulation run are:
Queued Communication to the simulator established. Job is created on indicated queue. Simulation case is validated and deck is built.
Starting Simulation case data is submitted to the simulator and Input files moved to job cache.
Running Simulator begins running.
Pushing Output Simulator finished. Output files are being moved from job cache to working directory.
Finished Indicates that the application can load results.
The following stages are encountered only when an issue with the simulation arises or it is manually paused:
Idle Illegal state. Indicates problem with the simulator.
Paused Simulation job was paused by user.
Failed Job failed for some reason. Generally caused by user stopping the job.