Monitoring Status

The Status tab allows you to monitor the progress of your job and get information about your cluster in real-time.

status-gantt-chart.png

Access the Status tab by clicking on its icon (highlighted in red here).

Job Status

As your job runs, it will go through five stages to successful completion shown: Queued, Validating Input, Starting Cluster, Running Job and Stopping Cluster. If there is an error during any of these job states, then a red "X" appears in place of the green check mark icon. Please contact us if you encounter an error during one of these job states as described.

Job Logs

More detail is given in the job log. An example of a typical log output is provided here:

basic-job-logs.png

For a job consisting of multiple runs (e.g. Design of Experiment or Optimization), you will see when individual runs are started:

doe-job-logs.png

Cluster Status

cluster-status.png

The Cluster Status section gives you up-to-date information on the cluster that your job is running. If your job doesn't run properly, or is taking an especially long time, then this section includes monitors that may help diagnose potential issues. For example, if your Avg Free Memory was especially low, then it might indicate that the cluster did not have access to enough memory to meet the simulation's requirements. If you are running on more than one node, then you will see the status of each node on separate lines.

Live Tailing

live-tailing-run.png

Live Tailing allows you to monitor the progress of your simulation in real- time and ensure the solution develops appropriately by following updates made to runtime files by the solver.

Select one of your cases from the list under the Active Runs table and click on any file associated with that case in the adjacent column to view the most recent lines of that selected file. While the list of Runs shown will vary as simulations start and stop, the list of files shown should be refreshed manually using the refresh button to access the latest file contents. The live tailing feature is limited to files of 800kB or smaller.

Downloading files during runtime

If you place your mouse cursour in the Live Tailing window at runtime, you will see a number of options in the top right hand corner of the liver tailing window, as show below. The Download button on the left allows you to download this single file, as it is at the point in time when you issue this instruction. If you wish to download all the files for a Run during its execution, follow the instructions given for Snapshots. The remaining buttons allow you to refresh the content of the file, expand the window to full-screen, and change the number of lines to be viewed.

live-tailing-settings.png

Stopping an Individual Run or Complete Job

If you decide you want to stop an individual run in-progress, then click on the X next to the run number in the Runs column of the Active Runs table.

stop-individual-run.png

When you stop an individual job in this way, you will see a dialog window, as shown below. If you choose Stop, your files for this run will be uploaded in the state that they were in when the Stop command was issued. This allows you to use them as input files for subsequent jobs.

stop-run-popup.png

If the run you have chosen to stop has already completed its workflow, you may see the dialog shown below. In this case, it is safe to go ahead and click Stop on this dialog. Your files for this run will be uploaded.

already-stopped-popup.png

When you wish to stop an entire job rather than an individual run you can use the Stop button which is shown below. Your files for completed, and partially completed Runs within the job will be uploaded for you. Runs which have not yet started will not be launched.

stop-job-button.png

If you use this Stop button to end your entire job, you will be presented with the following dialog.

stop-job-popup.png

Interrupting the job in this way and shutting down the cluster is recorded in the job status output log as User requested... as illustrated here.

stopping-job-status.png