This release is a pre-release and may not be stable for production use.
REACHER — Operant Experiment Control Server
Hardware control, session coordination, and live data capture for Arduino-driven rodent operant behavior experiments.
Written by: Joshua Boquiren
Overview
REACHER runs rodent operant conditioning experiments end to end — it drives the Arduino-based behavioral chamber, records every event as it happens, and exports the session ready for analysis. Paradigms ship as firmware for fixed ratio, progressive ratio, variable interval, omission, and Pavlovian conditioning, each exposing the hardware a self-administration rig actually uses: levers, cue lights and speakers, syringe pumps, lick circuits, and optogenetic laser control. Reinforcement ratios, timing parameters, session limits, and per-board pin assignments are set from the interface, so a rig is reconfigured between subjects without editing or recompiling firmware.
Every lever press, infusion, lick, and cue is timestamped against the trial clock and streamed live to the browser while the session runs, alongside microscope frame timestamps for aligning behavior with calcium imaging. A single host coordinates several chambers at once — each with its own serial port, paradigm, and output file — and hosts on the same network can be paired so one browser drives an entire rig room. Firmware for any paradigm is flashed onto a board directly from the interface, with no separate Arduino toolchain on the experimenter's machine.
Getting Started
pip install reacher2p # from PyPI
pip install reacher2p-3.4.0b2-py3-none-any.whl # from a release wheel
Host setup — installation, pairing, and systemd services — is documented in docs/setup-guide.md; see CONTRIBUTING.md and RELEASING.md for development and release process.
Architecture & Dependencies
| Component | Language | Framework / Libraries |
|---|---|---|
| REST & WebSocket API | Python 3.10+ | FastAPI, Uvicorn, websockets |
| Serial kernel | Python 3.10+ | pyserial |
| Session manager | Python 3.10+ | Python standard library (threading, asyncio) |
| Discovery & pairing | Python 3.10+ | zeroconf, httpx |
| Terminal monitor | Python 3.10+ | Rich, httpx |
| Firmware uploader | Python 3.10+ | avrdude |
| Arduino firmware | C++ (Arduino) | REACHERDevices, arduino-cli (AVR core) |
License
This project is released into the public domain under the Unlicense. See LICENSE for details.
Contact
Joshua Boquiren — thejoshbq@proton.me
1 maintainer
Release files for reacher2p 3.4.0b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| reacher2p-3.4.0b2.tar.gz | 767.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| reacher2p-3.4.0b2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / reacher2p-3.4.0b2.tar.gz
| Download URL | reacher2p-3.4.0b2.tar.gz |
|---|---|
| Size | 767.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
034f87de7180fb77f80de979dcd6656973ca6dfc916f54f16f1c613835d51164
|
|
BLAKE2b-256 checksum How to use checksums |
b2d03a3d648db0ab233e006b74f8469899a5b83839da9f5fdcde2300d71f69ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency logRelease files / reacher2p-3.4.0b2-py3-none-any.whl
| Download URL | reacher2p-3.4.0b2-py3-none-any.whl |
|---|---|
| Size | 678.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
01a070854770bbce159b6c1b291c8e54038eb1ec16a3ab3466b3a271f4c11e2a
|
|
BLAKE2b-256 checksum How to use checksums |
a5cc96dd9e564ab259367fbd4414a2e8954e8d3a12e85bb3bb4579d21546a348
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 24, 2026.
Transparency log
