guild run [OPTIONS] [[MODEL:]OPERATION] [FLAG=VAL...]
Run an operation.
By default Guild tries to run
OPERATION for the default model defined in the current project.
MODEL is specified, Guild uses it instead of the default model.
OPERATION may alternatively be a Python script. In this case any current project is ignored and the script is run directly. Options in the format
--NAME=VAL can be passed to the script using flags (see below).
[MODEL]:OPERATION may be omitted if
--proto is specified, in which case the operation used in
RUN is used.
FLAG values in the form
One or more batch files can be used to run multiple trials by specifying the file path as
For example, to run trials specified in a CSV file named
guild run [MODEL:]OPERATION @trials.csv
NOTE: At this time you must specify the operation with batch files - batch files only contain flag values and cannot be used to run different operations for the same command.
Batch files may be formatted as CSV, JSON, or YAML. Format is determined by the file extension.
Each entry in the file is used as a set of flags for a trial run.
CSV files must have a header row containing the flag names. Each subsequent row is a corresponding list of flag values that Guild uses for a generated trial.
JSON and YAML files must contain a top-level list of flag-to-value maps.
--print-trials to preview the trials run for the specified batch files.
A list of flag values may be specified using the syntax
[VAL1[,VAL2]...]. Lists containing white space must be quoted. When a list of values is provided, Guild generates a trial run for each value. When multiple flags have list values, Guild generates the cartesian product of all possible flag combinations.
Flag lists may be used to perform grid search operations.
For example, the following generates four runs for operation
train and flags
guild run train learning-rate[0.01,0.1] batch-size=[10,100]
You can preview the trials generated from flag lists using
--print-trials. You can save the generated trials to a batch file using
--save-trials. For more information, see PREVIEWING AND SAVING TRIALS below.
--optimizer is specified, flag lists may take on different meaning depending on the type of optimizer. For example, the
random optimizer randomly selects values from a flag list, rather than generate trials for each value. See OPTIMIZERS for more information.
A run may be optimized using
--optimizer. An optimizer runs up to
--max-trials runs using flag values and flag configuration.
For details on available optimizers and their behavior, refer to Optimizers Reference - Reference - Guild AI.
When using flag lists or optimizers, which generate trials, you can limit the number of trials with
--max-trials. By default, Guild limits the number of generated trials to 20.
Guild limits trials by randomly sampling the maximum number from the total list of generated files. You can specify the seed used for the random sample with
--random-seed. The random seed is guaranteed to generate consistent results when used on the same version of Python. When used across different versions of Python, the results may be inconsistent.
When flag lists (used for grid search) or an optimizer is used, you can preview the generated trials using
--print-trials. You can save the generated trials as a CSV batch file using
--proto is specified, Guild applies the operation, flags, and source code used in
RUN to the new operation. You may add or redefine flags in the new operation. You may use an alternative operation, in which case only the flag values and source code from
RUN are applied.
RUN must be a run ID or unique run ID prefix.
--restart is specified,
RUN is restarted using its operation and flags. Unlike
--proto, restart does not create a new run. You cannot change the operation, flags, source code, or run directory when restarting a run.
--stage to stage an operation to be run later. Use
--start with the staged run ID to start it.
--start is specified,
RUN is started using the same rules applied to
--restart (see above).
To run an operation outside of Guild’s run management facility, use
--stage-dir to specify an alternative run directory. These options are useful when developing or debugging an operation. Use
--stage-dir to prepare a run directory for an operation without running the operation itself. This is useful when you want to verify run directory layout or manually run an operation in a prepared directory.
NOTE: Runs started with
--run-dir are not visible to Guild and do not appear in run listings.
By default, operations have access to all available GPU devices. To limit the GPU devices available to a run, use
For example, to limit visible GPU devices to
guild run --gpus 0,1 ...
To disable all available GPUs, use
--no-gpus are used to construct the
CUDA_VISIBLE_DEVICES environment variable used for the run process. If
CUDA_VISIBLE_DEVICES is set, using either of these options redefines that environment variable for the run.
--optimizer to run the operation multiple times in attempt to optimize a result. Use
--maximize to indicate what should be optimized. Use
--max-runs to indicate the maximum number of runs the optimizer should generate.
--edit-flags to use an editor to review and modify flag values. Guild uses the editor defined in
EDITOR environment variables. If neither environment variable is defined, Guild uses an editor suitable for the current platform.
--debug-sourcecode to specify the location of project source code for debugging. Guild uses this path instead of the location of the copied soure code for the run. For example, when debugging project files, use this option to ensure that modules are loaded from the project location rather than the run directory.
--break to set breakpoints for Python based operations.
LOCATION may be specified as
[FILENAME:]LINE or as
FILENAME is not specified, the main module is assumed. Use the value
1 to break at the start of the main module (line 1).
Relative file names are resolved relative to the their location in the Python system path. You can omit the
If a line number does not correspond to a valid breakpoint, Guild attempts to set a breakpoint on the next valid breakpoint line in the applicable module.
||Set a label for the run.|
||Associate TAG with run. May be used multiple times.|
||Comment associated with the run.|
||Use an editor to type a comment.|
||Use an editor to review and modify flags.|
||Use alternative run directory DIR. Cannot be used with --stage.|
||Stage an operation.|
||Start a staged run or restart an existing run. Cannot be used with --proto or --run-dir.|
||Use the operation, flags and source code from RUN. Flags may be added or redefined in this operation. Cannot be used with --restart.|
||Use working source code when --restart or --proto is specified. Ignored otherwise.|
||Limit availabe GPUs to DEVICES, a comma separated list of device IDs. By default all GPUs are available. Cannot beused with --no-gpus.|
||Disable GPUs for run. Cannot be used with --gpu.|
||Label to use for batch runs. Ignored for non-batch runs.|
||Associate TAG with batch. Ignored for non-batch runs. May be used multiple times.|
||Comment associated with batch.|
||Use an editor to type a batch comment.|
||Optimize the run using the specified algorithm. See Optimizing Runs for more information.|
||Optimize the run using the default optimizer.|
||Column to minimize when running with an optimizer. See help for compare command for details specifying a column. May not be used with --maximize.|
||Column to maximize when running with an optimizer. See help for compare command for details specifying a column. May not be used with --minimize.|
||Flag for OPTIMIZER. May be used multiple times.|
||Maximum number of trials to run in batch operations. Default is optimizer specific. If optimizer is not specified, default is 20.|
||Random seed used when sampling trials or flag values.|
||Specify an alternative source code path for debugging. See Debug Source Code below for details.|
||For batch operations, stage trials without running them.|
||Run the operation remotely.|
||Do not prompt before running operation.|
||Accept all flag assignments, even for undefined or invalid values.|
||Continue even when a required resource is not resolved.|
||Stop operation after N minutes.|
||Stop batch operations when a trial exits with an error.|
||Run only if there is not an available matching run. A matching run is of the same operation with the same flag values that is not stopped due to an error.|
||Run operation in background.|
||Run operation in background, writing the background process ID to PIDFILE.|
||Don’t wait for a remote operation to complete. Ignored if run is local.|
||Saves generated trials to a CSV batch file. See BATCH FILES for more information.|
||Keep run even when configured with ‘delete-on-success’.|
||Keep batch run rather than delete it on success.|
||Include PATH as a dependency.|
||Set a breakpoint at the specified location for Python based operations. Set
||Enter the Python debugger at the point an error occurs for Python based operations.|
||Do not show output.|
||Show operation command and exit.|
||Show operation environment and exit.|
||Show generated trials and exit.|
||Show model help and exit.|
||Show operation help and exit.|
||Test output scalars on output. Use ‘-’ to read from standard intput.|
||Test source code selection.|
||Test flag configuration.|
||Show this message and exit.|
Guild AI version 0.8.2