Web Console
Researcher-facing UI for registering experiments, building questionnaires, uploading avatars, and downloading data.
These pages are not yet fully reviewed. The LUIDA team is continuing to review and improve them. If you find anything wrong on these pages, or have questions that aren't resolved by reading them, please ask or report to the LUIDA team.
The Web Console at luida.cluster.mu is the researcher-facing side of LUIDA. While the Unity template is where you build the experiment, the Web Console is where you register it — its title, consent form, world ID, session caps, allowed platforms, avatar mode — and where the data eventually lands. Every experiment has exactly one row in the Web Console's database, and that row is the record of how the experiment was configured.
This section of the docs walks through every page of the console, in roughly the order you'll touch them on a new study.
Where to start
If you've never used the Web Console:
Researcher onboarding
Sign up at luida.cluster.mu, get your account approved off the waitlist, and reach the Experiments list. ~1 hour of waiting once you email the LUIDA team.
Creating an experiment
Register your first study — basic info, world bindings, session limits, consent form. Pick up the eID you'll paste into Unity.
Configuring an experiment
Platform & avatar settings
allowedPlatforms (VR, Windows, Mac, Android, iOS) and participantAvatarMode (HIDE, DEFAULT, UNRESTRICTED). Which device types can join, and what avatar participants render with.
Sessions & balancing
maxSessionCount, excluded sessions, excluded participants. Cap data collection, drop unusable runs, balance between-subjects conditions.
Building questionnaires
Five question types, IPQ/SSQ templates, drag-to-reorder, and how qID gets assigned for binding from Unity.
Uploading avatars
VRM upload, thumbnail generation, special avatar names. The (mostly deprecated) per-experiment avatar set.
After data starts flowing
Downloading data
Three tabs — questionnaire answers, participant info, custom logs. Export as CSV, JSON, or ZIP.
Settings & account
Language toggle, profile display, account deletion. Short page.
How the Web Console fits into the larger picture
The console is one of LUIDA's four components — alongside the Unity template, the Recruitment World, and the Cluster instance itself.
- You write to the console: experiment registration, questionnaire content, avatars, exclusions.
- The Unity template reads from the console: during a session, the Unity-side
callExternalmachinery fetches questionnaires (byqID), validates participants, persists between-subjects assignments, and uploads custom-data records. - The console writes back to you: CSV/JSON exports on the download tabs.
For a deep dive into the wire-level dispatch types your Unity scenes use to talk to the console, see Reference → Web Console API.
Related
- About LUIDA — the four components and how they fit together.
- Concepts → Conditions, sessions, participants — the session-start handshake that the console orchestrates.
- Concepts → Questionnaires — the qID binding model that connects the console's question editor to Unity states.
- Concepts → Data collection — the four data streams that the console receives.