> 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/procedure/important-notes-on-testing.md).

# Important notes on testing

* Subjects should receive a minimum phase length of 11 trials per day (i.e., without interruption and using a consistent ITI).
* The ITI must be documented and kept consistent within each lab/team/site.
* While the experimental design includes three cue conditions (location, shape, and color), it may not be feasible for every testing site to administer all three due to logistical constraints (e.g., time, resources, testing capacity).
* Some species may be unable to complete all conditions because of perceptual limitations (e.g., restricted color vision), motor constraints, or other species-specific factors that could affect task performance.
* The core procedure is intended to be broadly applicable across a diverse range of captive or laboratory-tested taxa, though participation of sites testing semi-captive or wild subjects is also welcome when feasible (see [Wildlife Considerations](https://docs.google.com/document/d/1zxvtuttE8B2X0ItV682l0UqCZx9gaJ4LF7hbO4so8SY/edit?tab=t.1bolecl9p8vg) section).
* If a testing site encounters any of the above constraints, they should consult with the MM1 Leadership Team to discuss appropriate alternatives, including modified procedures, adjusted condition sets, or prioritization of conditions that best align with the species’ sensory and motor capabilities while preserving the comparative aims of the reversal learning experiment.


---

# 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/procedure/important-notes-on-testing.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.