Cookbook
Short, focused recipes for things researchers commonly want to do with LUIDA. Each recipe is one task, with the smallest working setup.
Each recipe answers one "I want to…" question. Recipes are short on purpose — they show the minimum you need to make the feature work, and link to the Tutorials, Concepts, and Reference sections for the depth behind each step.
If the recipe you want isn't here, check the Decision tree — it covers the common forks at a different angle.
Recipes
I want a button that advances the state when pressed
The simplest interaction: one button, one state transition. Plain CCK, no Customized Action.
I want to log reaction times
Time the gap between a stimulus appearing and a button press. Per-trial, downloadable as CSV.
I want different stimuli per condition
Show one thing for condition A, another for condition B. The if-toggle on a state-listening action does it.
I want to assign a unique avatar per participant
Use AssignAvatarToParticipant + a between-subjects variable to give each session a different VRM.
What's deliberately not here
- "I want to send data to an external EEG / MoCap rig" (OSC). The
SendViaOscaction is implemented (see Reference → SendViaOsc) but hasn't been validated end-to-end against real hardware as of this writing. We'd rather not publish a recipe we haven't seen work. If you're planning to use OSC for hardware integration, contact luida@cluster.mu so we can confirm the round-trip with you and turn that confirmation into this missing recipe.
How to read a recipe
Every recipe follows the same shape:
- Goal — one sentence.
- Smallest setup — the minimum Unity / Web Console state you need before the recipe applies.
- The recipe — numbered steps.
- Why this works — one or two paragraphs of context, linking to the deeper Concepts page.
- Variants — common adjustments (per-condition, per-participant, different timing).
- Where to go next — the full Tutorial or Reference page if you want the deep version.
If a recipe assumes a tutorial, it'll say so up top. Otherwise, treat each as standalone.