> For the complete documentation index, see [llms.txt](https://2025.istvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://2025.istvs.org/conference/technical-tour.md).

# Technical Tour

ISTVS 2025 | October 6-9, 2025 | Lebanon, New Hampshire, USA

{% hint style="success" %}
Technical tour will be held ***outside, rain or shine,*** please make sure to wear appropriate attire. Average New England temperatures during October range from 30°F / -1°C to 60°F / 15°C.
{% endhint %}

### Date & Time

* Wednesday, October 8
* 0700 - 1730

### About

The technical tour will include two separate events about 1.5 miles apart. Participants will be bussed from the Hilton Garden Inn to and from the tour sites. The attendees will be split into two groups with the first group attending Team O’Neil Rally School Tarmac events and the second group attending the autonomy demonstrations at nearby Ridge Runner Promotions. The teams will meet back at Team O’Neil for lunch before switching areas for the afternoon session. The day will start with pickup at the hotel at 0700 for an 0800 start of the demonstrations and will return to the hotel around 1730 that evening.

### [Team O’Neil Rally Demonstrations](https://2025.istvs.org/conference/technical-tour/team-oneil-rally-demonstrations.md)

***

### [Autonomy Demonstrations](https://2025.istvs.org/conference/technical-tour/autonomy-demonstration.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://2025.istvs.org/conference/technical-tour.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
