> For the complete documentation index, see [llms.txt](https://docs.robbie.run/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.robbie.run/running-your-experiments-on-robbie/funding-group-environment-and-images.md).

# 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.robbie.run/running-your-experiments-on-robbie/funding-group-environment-and-images.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.