What Is an Experiment?
Each experiment in a quest has:| Field | Required? | Description |
|---|---|---|
| Name | ✅ Yes | Display name shown on the experiment card |
| Description | Optional | Short description shown below the name |
| Image URL | Optional | Thumbnail image for the experiment card |
| Code | ✅ Yes | HTML/JavaScript code (typically jsPsych) |
| Duration (minutes) | Optional | Estimated time shown to participants |
| Category | Optional | Category tag |
| Instructions | Optional | HTML instructions shown before the experiment |
Multi-Experiment Quests
A quest can have multiple experiments. When participants view the quest:- Experiments are displayed as horizontally scrollable cards with thumbnail, name, description, and duration
- The active experiment is highlighted
- Clicking a card selects that experiment
- Participants can complete experiments in sequence
- Experiments can have dependencies — locking them until prerequisites are completed
- Auto-trigger can automatically advance to the next experiment after completion
Data Flow
When a participant completes an experiment:- The jsPsych experiment calls
jatos.endStudy(data)to submit results - Data is captured by the NeuroFusion runner
- Saved locally first (for offline resilience on mobile)
- Synced to the server and stored in Azure Blob Storage
- Recorded as an
experiment_datadataset
Billing
Each experiment data submission is billed asquest_experiment to the quest’s organization. See the Pricing page for current costs.
Backward Compatibility
Older quests with a singleexperimentUrl string (the legacy format) continue to work. The system automatically treats them as a single-experiment quest.