wandb launch

Launch or queue a W&B Job. See https://wandb.me/launch

Usage

wandb launch [OPTIONS]

Options

Option	Description
--uri, -u	Local path or git repo uri to launch. If provided this command will create a job from the specified uri.
--job, -j	Name of the job to launch. If passed in, launch does not require a uri.
--entry-point, -E	Entry point within project. [default: main]. If the entry point is not found, attempts to run the project file with the specified name as a script, using ‘python’ to run .py files and the default shell (specified by environment variable $SHELL) to run .sh files. If passed in, will override the entrypoint value passed in using a config file.
--git-version, -g	Version of the project to run, as a Git commit reference for Git projects.
--build-context	Path to the build context within the source code. Defaults to the root of the source code. Compatible only with -u.
--job-name, -J	Name for the job created if the -u,—uri flag is passed in.
--name	Name of the run under which to launch the run. If not specified, a random run name will be used to launch run. If passed in, will override the name passed in using a config file.
--entity, -e	Name of the target entity which the new run will be sent to. Defaults to using the entity set by local wandb/settings folder. If passed in, will override the entity value passed in using a config file.
--project, -p	Name of the target project which the new run will be sent to. Defaults to using the project name given by the source uri or for github runs, the git repo name. If passed in, will override the project value passed in using a config file.
--resource, -r	Execution resource to use for run. Supported values: ‘local-process’, ‘local-container’, ‘kubernetes’, ‘sagemaker’, ‘gcp-vertex’. This is now a required parameter if pushing to a queue with no resource configuration. If passed in, will override the resource value passed in using a config file.
--docker-image, -d	Specific docker image you’d like to use. In the form name:tag. If passed in, will override the docker image value passed in using a config file.
--base-image, -B	Docker image to run job code in. Incompatible with —docker-image.
--config, -c	Path to JSON file (must end in ‘.json’) or JSON string which will be passed as a launch config. Dictation how the launched run will be configured.
--set-var, -v	Set template variable values for queues with allow listing enabled, as key-value pairs e.g. --set-var key1=value1 --set-var key2=value2
--queue, -q	Name of run queue to push to. If none, launches single run directly. If supplied without an argument (--queue), defaults to queue ‘default’. Else, if name supplied, specified run queue must exist under the project and entity supplied.
--async	Flag to run the job asynchronously. Defaults to false, i.e. unless —async is set, wandb launch will wait for the job to finish. This option is incompatible with —queue; asynchronous options when running with an agent should be set on wandb launch-agent. (default: False)
--resource-args, -R	Path to JSON file (must end in ‘.json’) or JSON string which will be passed as resource args to the compute resource. The exact content which should be provided is different for each execution backend. See documentation for layout of this file.
--build, -b	Flag to build an associated job and push to queue as an image job. (default: False)
--repository, -rg	Name of a remote repository. Will be used to push a built image to.
--project-queue, -pq	Name of the project containing the queue to push to. If none, defaults to entity level queues.
--dockerfile, -D	Path to the Dockerfile used to build the job, relative to the job’s root
--priority, -P	When —queue is passed, set the priority of the job. Launch jobs with higher priority are served first. The order, from highest to lowest priority, is: critical, high, medium, low