Try our new documentation site (beta).
Accessing Job Parameters
The Gurobi Optimizer provides a number of parameters that can be modified by the user. The job params command allows you to inspect the values of these parameters in a Compute Server job:
> grbcluster job params 58780a22 info : Found matching job is 58780a22-8acc-499e-b73c-da6f2df59669 ComputeServer=server1 TimeLimit=60
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 changed parameters of the last job submitted.
The following example illustrates how the grbcluster job params command can be used in practice. The first step is to start an optimization job on a Compute Server cluster with one modified parameter:
> gurobi_cl TimeLimit=120 glass4.mps
Once the job starts, you can use the grbcluster jobs command to retrieve the associated JOBID (or you can read it off from the output of gurobi_cl). For jobs that have been already processed, you would run the job recent command instead.
> grbcluster jobs JOBID ADDRESS STATUS #Q STIME USER PRIO API 7c51bf74 server1 RUNNING 2019-04-07 14:50:56 jones 0 gurobi_cl
Once you obtain the JOBID, the job params command shows the modified parameter settings for the job:
> grbcluster job params 7c51bf74 info : Found matching job is 7c51bf74-ba02-4239-875e-c8ea388f9427 ComputeServer=server1 TimeLimit=120
The full list of Gurobi parameters can be found in the Parameters section of the Gurobi Reference Manual.
