> For the complete documentation index, see [llms.txt](https://gtae.gitbook.io/ifl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gtae.gitbook.io/ifl/training.md).

# Initiation and Training

## All IFL Users

All IFL users must complete the following tasks to gain access the IFL:

* #### Pre-initiation
  * Make sure you have well and truly read the Shared Spaces User Agreement.
  * Read the [scheduling calendar instructions](https://gtae.gitbook.io/ifl/calendar-and-teams) hosted on the IFL Gitbook Wiki.
  * Spend 10 minutes familiarizing yourself with the [IFL website (especially the "About the IFL" page)](https://ifl.ae.gatech.edu/) and the rest of the IFL Gitbook Wiki.
* #### In-person initiation
  * Work with the Lab Manager to arrange your in-person initiation.
  * During in-person initiation you'll undergo the following:
    * General overview of the space(s) and capabilities
    * Review of Shared Space User Agreement and shared space philosophy
    * Instructions on use of the external doors
    * Safety discussion (emphasis on Li-Po procedure)
    * Review of the research project including technical advice/support (time-permitting)

## Vicon Users

*Forewarning: The IFL does not provide Vicon markers!!!* See the [Setting up Vicon Tracker and your object](/ifl/vicon-integration/setting-up.md) page for more details on how to procure your own.

Strictly speaking, no training is required in order to use the Vicon system, therefore explicit Vicon training is not offered ***unless it's absolutely needed***. If you don't have a trained lab mate and you are comfortable attempting Vicon solo, here are some excellent resources that should get you 90% of the way there:

1. <mark style="background-color:yellow;">\[COMING SOON: IFL-SPECIFIC VIDEO ON VICON SETUP AND USAGE]</mark>
2. All of the 'Vicon Integration' pages on this Gitbook Wiki, starting with the [Quick Start Guide](https://gtae.gitbook.io/ifl/vicon-integration/quick-start-guide). Note that the Wiki is intended to supplement the Vicon Tracker User Guide, not replace it, and to provide space-specific information.
3. Watch the official Vicon Tracker 3 [tutorial videos](https://www.youtube.com/playlist?list=PLxtdgDam3USXPrhGA70ix8WT_nZBLK7qB). Note that, of the 14 videos on this playlist, only the following videos are absolutely necessary to watch: 1,2,7,10,11,12,13,14. But there is no downside to watching the entire playlist.
4. Thoroughly read the Vicon Tracker 3.7 user guide. You can access it online [here ](https://docs.vicon.com/display/Tracker37/Vicon+Tracker+User+Guide)(expand the "Vicon Tracker User Guide" drop down on the left hand side of the page) but it's clumsy to navigate so I recommend you download the PDF version [here](https://firebasestorage.googleapis.com/v0/b/gitbook-28427.appspot.com/o/assets%2F-MKc9az4fYzF9_wFvhka%2F-MXsJ9R9nNIHlk-TAAbG%2F-MXsKLvRgBxSwPfHJTzd%2FVicon%20Tracker%20User%20Guide.pdf?alt=media\&token=8088a7d1-e673-4593-91be-50c6f9f0583e).&#x20;

If you are still struggling, reach out to Lee Whitcher to arrange a Vicon primer.


---

# 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://gtae.gitbook.io/ifl/training.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.
