> For the complete documentation index, see [llms.txt](https://campus-rover.gitbook.io/lab-notebook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://campus-rover.gitbook.io/lab-notebook/fiiva/bru.md).

# Brandeis Robotics Utility

## What it is

First of all, BRU is not a finished product, it is constantly under development. You should expect inconsistencies and incompleteness. You are invited to fix and improve it. BRU embodies a series of python scripts, bash shells, and conventions, to make it more convenient to operate robots in the Brandeis Robotics Lab. We have many different robots that are all similiar but a little different. BRU attempts to unify and organize things in a sane manner.

## What is the problem BRU solves?

While all our robots run ROS (so far, just ROS1) they are all a little different. They use different SBC (single board computers) and different controllers. They have different peripherals. Also students use the robots either from their own laptop but more commonly from a virtual machine in our cluster environment. ROS has very partoicular requirements about IP addresses and environment variables. All together this can become very confusing.


---

# 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://campus-rover.gitbook.io/lab-notebook/fiiva/bru.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.