> For the complete documentation index, see [llms.txt](https://docs.axobug.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.axobug.com/responses.md).

# Reading a response

A practical guide to channel rates, movement drives and spike frames.

## Movement drives / 0–1

drive contains normalized values derived from neural channel rates. They are convenient controls for your scene, not probabilities of success or learned gameplay decisions.

| Field        | Use it for                                        |
| ------------ | ------------------------------------------------- |
| walk         | Forward pace or roaming speed                     |
| stop         | Slowing or stopping a character                   |
| backward     | Reverse movement                                  |
| escape       | Dodge distance, lift or an escape effect          |
| proboscis    | A feeding animation                               |
| wing         | Wing animation; also responds to escape activity  |
| turn / groom | Reserved in this decoder; both currently return 0 |

```javascript
const speed = brain.drive.walk * 80;
const dodge = brain.drive.escape * 160;
const glow = brain.drive.proboscis;

// Apply these values to your own objects and animation.
```

## Channel activity / Hz

channels contains average firing rates per neuron within named channel populations, over the simulated duration. Read channels.escape, for example, when you want the rate rather than the normalized drive. A quiet channel can legitimately return zero.

## The response at a glance

| Field                                      | Meaning                                                         |
| ------------------------------------------ | --------------------------------------------------------------- |
| id / model                                 | Unique run ID and model version                                 |
| stimulus / seed / intensity / duration\_ms | The settings used for this run                                  |
| neurons / connections                      | Model graph size                                                |
| stimulated\_neurons                        | Size of the selected input population                           |
| total\_spikes                              | Total spike events during the run                               |
| responding\_neurons                        | Number of neurons that fired at least once                      |
| compute\_ms                                | Server simulation compute time, excluding network travel        |
| channels / drive                           | Measured channel rates and normalized movement controls         |
| frames                                     | Display frames; full response only                              |
| top\_types                                 | Up to eight cell types with the most spikes; full response only |

## Animate with spike frames

Full responses include one display frame per 5 ms of simulated time. Each has t (simulation time in ms), spikes (atlas neuron indices), total (cumulative spike count) and channels (rates for that interval). A 100 ms experiment produces 20 frames.

{% hint style="info" %}
**Display frames are sampled**

spikes contains up to 3,000 unique neuron indices per frame. It is a visualization sample, not an exhaustive event log. Do not add the frame arrays to calculate total spikes; use total\_spikes.
{% endhint %}

Play frames locally at your chosen visual speed. Replaying a response does not request another experiment or make the model learn. Neural Observatory shows one way to map these frames into a particle scene.


---

# 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://docs.axobug.com/responses.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.