> For the complete documentation index, see [llms.txt](https://manymanys.gitbook.io/mm1-lab-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manymanys.gitbook.io/mm1-lab-manual/method/apparatus.md).
# Apparatus
#### Barrier
An opaque barrier can be used to block the subject’s view of—and access to—the stimuli (or other test subjects) before the start of each trial and between trials. To minimize neophobic responses, the barrier should consist of a familiar object and be present during acclimation and shaping phases (see Procedure section below). The choice of color, size, and material for the barrier can vary across species. Examples of barriers include curtains, boards, and sheets. Alternatively, small subjects can be covered with an opaque container. If the use of a barrier is not possible, the stimuli can be removed out of sight of the subject by the experimenter between trials. The dimensions of the barrier are determined by each lab/team/site based on species- and site-specific characteristics.
#### Surface
The stimuli are placed on a flat uniform surface (e.g., floor, table, mat, wall) and positioned at an equal distance from the subject’s starting point, with the distance from the stimuli being scaled to body size. The surface should allow sufficient visual discrimination of the experimental setup (e.g., stimuli).
{% hint style="info" %}
Figure 1. Example of experimental setup for location cue condition. The subject is tested in a familiar space, with trials taking place on a flat uniform surface. The stimuli consist of two Lego® brick objects that differ in shape and color, but are both half the size of the subject. Stimuli are placed equidistance (approximately two-body length) from the subject, one on the left (S+) and the other on the right (S−). Image credit: Ben Whittaker.
{% endhint %}
---
# 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://manymanys.gitbook.io/mm1-lab-manual/method/apparatus.md?ask=&goal=
```
`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.