Documentation

Next: Accessing Job Parameters Up: Job Commands Previous: Listing Jobs

Accessing Job Logs

Gurobi Optimizer log output from a previous or currently running job can be retrieved by using the job log command. For example:

> grbcluster job log 58780a22
info  : Found matching job is 58780a22-8acc-499e-b73c-da6f2df59669
  Flow cover: 20
  Zero half: 4

Explored 54868 nodes (381866 simplex iterations) in 4.27 seconds
Thread count was 4 (of 4 available processors)

Solution count 4: 30 31 32 33

Optimal solution found (tolerance 1.00e-04)
Best objective 3.000000000000e+01, best bound 3.000000000000e+01, gap 0.0000%

The argument to this command is the JOBID for the job of interest (which can be retrieved using the jobs command). You can use the full ID or the short ID. If you don't specify a JOBID, the command will display the log for the last job submitted.

The job log command accepts the following arguments:

Usage:
  grbcluster job log <JOBID> [flags]

Flags can be set using --flag=value or the short form -f=value if defined.
A boolean flag can be enabled using --flag or the short form -f if defined.

Flags:
  -b, --begin        Display log from the beginning
  -f, --continuous   Display log continuously until job completion
  -h, --help         help for log
  -n, --lines int    Display only the last n lines (default 10)

For example, to get the entire log, from the beginning of the job, use the -b (or --begin) flag.

> grbcluster job log 58780a22 -b

You can get a continuous feed of the log for a running optimization job with the -f (or --follow) flag.

---

Next: Accessing Job Parameters Up: Job Commands Previous: Listing Jobs