Funding Group, Environment, and Images

Robbie enables users to run their workloads on GPUs in minutes without complex setup and configuration. You sign up, purchase tokens, install the Robbie Python package, and start sending your jobs.

By default, Robbie will consume your Personal tokens and use your default hardware (Environment). In the case of NERC this is the “NERC Small GPU”.

For example:

`robbie run “python main.py” (without a job_config.yaml in your local directory)`

Before Robbie executes your run, it will display the funding source (Personal or Group), environment, and Image it plans to use – along with the Token consumption rate. You can choose to proceed or exit.

Robbie gives you several options when you need to customize the Group, Environment, and Image for your runs.

• Run robbie run with the –-i (interactive) option and choose the Group, Environment, and Image for your run.

• Build a customer configuration (job_config.yaml) using the robbie configure command.

• Using the Robbie portal, choose a funding source, environment and image then download the job_config.yaml to use for your runs.

• (Advanced) Pass –funding_group_id, --environment_id, or --image arguments to robbie run. Note: You must specify UUIDs from the –funding_group_id, --environment_id options. These are available in the Robbie portal.

Robbie treats Group, Environment, and Image precedence as follows:

• Default 🡪 job_config.yaml 🡪CLI Argument

This means that the default value will be used first. If the value is specified in the job_config.yaml, that will be used, and finally, if an argument is specified that will be used for the job.