A Behavior records one behavioral assay actually performed, with
particular subjects, on a particular rig, during one Session. It is the
link between the standardized task description and the session in which it
happened, so it has no type of its own — the assay supplies that.
Assay, setup, and occurrence
-
Behavioral category and paradigm are
shared taxonomy: the broad domain and the standardized task.
-
Behavioral assay is your lab's implementation of that
task — the method as you run it.
-
Setup type and Setup describe the class
of apparatus and your concrete rig.
-
Behavior is one occurrence: this assay, on this setup,
with these subjects, in this session.
Create the Behavioral assay and the Setup first — a Behavior can only point at
ones that already exist and that you can use. Because the assay and setup are
reached through their groups while the Behavior belongs to the session's
projects, both have to be available to you in that context.
Behavior fields
-
Session
Required
Single selection
-
The session during which the behavior was run. The choices are
limited to sessions in projects where you can make changes, and
the session supplies this entry's permission context.
-
Subjects
Required
Multiple selections
-
Every subject that took part. The choices come from the
session's own subjects, so add a subject to the session first
if it is missing here. Select all participants rather than
creating one Behavior per animal, unless they genuinely ran
separately.
-
Setup
Required
Single selection
-
The physical rig the behavior ran on. Only setups you can
change are offered. Its setup type is shown beside the field so
you can check the rig suits the assay.
-
Behavioral assay
Required
Single selection
-
The lab method performed. Only assays you can change are
offered. This is what carries the task definition — the
Behavior itself stores no task parameters.
-
Order
Number
-
Where this behavior appears among the session's entries. Use it
when the sequence within the session matters; it does not imply
a start time.
-
Notes
Text · 500 characters
-
What was specific to this occurrence: deviations from the
assay, technical problems, or notable outcomes. Anything that
repeats every run belongs on the Behavioral assay instead.
Permissions
A Behavior inherits its access through the projects associated with its
Session. You need change access through at least one of those projects to add
or edit it. The subject, setup, and assay selectors are separately restricted
to entries you may use.
API access
Behaviors can be read and written through
/api/private/modules/behavior/. The corresponding public route
is read-only. A Behavior stores no structured detail of its own; its task
definition lives on the linked Behavioral assay.
Behavior documentation