> 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/counterbalancing.md).

# Counterbalancing

### Condition Counterbalancing and Reversal Count

Priority should be given to testing subjects in all three conditions, using appropriate counterbalancing across conditions (i.e., a third of subjects start with the location cue condition, another third with the shape condition, and the remaining third with the color condition). Subjects who reach the learning criterion for the first reversal (i.e., reversal 1) can either be tested in an interreversal phase—consisting of at least six reversals—or skip the interreversal phase and move on to the next condition. It is the responsibility of labs/teams/testing sites to decide whether to conduct or opt out of the interreversal phase.

### Side Counterbalancing

The side on which each stimulus is presented for each trial is pseudo-randomized such that each stimulus is on each side an equal number of times during the acquisition or reversal phase, but with no more than three trials in a row on the same side.&#x20;

Testing sites are responsible for appropriate pseudo-randomization of stimulus location.


---

# 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/counterbalancing.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.
