Trial Protocol Designer

Design reinforcement schedules, build trial state machines, and export Bpod-compatible protocols for operant conditioning experiments.

Operant ConditioningState MachineClient-Side
Tool details, related tools, and citation

Try it out

Load example Trial Protocol Designer data to see the full workflow

Reinforcement Schedule

Reinforcement after a fixed number of responses

Timing Parameters

Schedule Results

Session Duration
10.0 min
600 seconds
Estimated Trials
100
FR5 schedule
Total Reward
1.00 mL
1000 µL
  • Plan operant conditioning sessions with accurate timing and reward volume estimates
  • Compare reinforcement schedules (FR, VR, FI, VI, DRL, PR) for your experimental design
  • Build and validate trial state machines before programming behavioral control hardware
  • Generate Bpod-compatible state tables and protocol JSON for Sanworks systems
  • Estimate progressive ratio breakpoints for motivation and addiction studies

Don't use for

  • For real-time behavioral control — this is a planning tool, not a runtime controller
  • For complex multi-agent or social behavior protocols requiring parallel state machines
  • As a substitute for pilot testing — actual timing depends on animal performance

Operant Conditioning Schedule Fundamentals

Reinforcement schedules control when and how frequently responses are rewarded, fundamentally shaping behavior patterns:

Ratio schedules (FR, VR) reinforce after a set number of responses. Fixed ratios produce post-reinforcement pauses; variable ratios produce steady high-rate responding.
Interval schedules (FI, VI) reinforce the first response after a time period. Fixed intervals produce scalloped response patterns; variable intervals produce moderate steady rates.
Progressive ratio escalates the response requirement each trial, measuring motivational breakpoints. The Richardson-Roberts formula (5×e^(0.2n)−5) is the standard escalation function.
DRL reinforces only when responses are spaced by a minimum delay, measuring impulse control and temporal discrimination.

Common Pitfalls in Protocol Design

Several factors can compromise behavioral data quality:

Session too long: Sessions beyond 60–90 min cause satiety and fatigue artifacts. Monitor lick rate and response latency for decline. • Reward volume mismatch: Total session reward must match the daily fluid/food restriction target. Too much causes satiety; too little causes motivational drift. • ITI too short: Brief ITIs cause behavioral carry-over between trials. Minimum 3–5s for operant, 10–30s for Pavlovian. • Missing timeout states: Omitting timeout penalties for incorrect responses reduces discrimination learning speed. • State machine dead-ends: States with no outgoing transitions will freeze the protocol. Always verify every state can exit. • Progressive ratio ceiling: Without a breakpoint criterion (typically 5 min no response), PR sessions can run indefinitely.

Frequently Asked Questions