From z-Tree to oTree
summary
Compares the legacy z-Tree experiment platform with oTree, an open-source rewrite implemented in Python and Django, focusing on a four-client Prisoner’s Dilemma demo. Explains that z-Tree is easy to set up but single-threaded, slow, and hard to automate large test suites (e.g., 36 screens), whereas oTree supports multithreading, programmable bots, automated testing and integration with standard web servers at the cost of more complex setup, occasional beta instability, and developer effort for migration.
AI-written summary · about
chapters (11)
- 0:00z-Tree and oTree intro
- 3:15z-Tree structure
- 5:44Prisoner's Dilemma demo
- 7:12oTree architecture
- 8:59oTree demo and interface
- 12:05Switching to oTree
- 15:20oTree acceptance
- 16:27oTree for surveys
- 17:10oTree setup
- 19:40oTree demos and bots
- 20:45Summary and Q&A
related talks
28mBetter Routing Through Trees
26mZiggurat
39mTree-sitter - a new parsing system for programming tools
51mTo Deploy or Not-to-Deploy - decide using TTA's Trend & Failure Analysis
15mAsTree: An Audio Subscription Architecture Enabling Massive-Scale Multi-Party...
49mWhat CRDTs, distributed editing and the speed of light means to your writer friends
20mArboretum and Arbility: Improving Web Accessibility Through a Shared Browsing Architecture
28mTrees and UX: Designing Customer Journeys for a Green Impact