OptionComponent
Options can comprise multiple components. This table describes each component of an option.
-
option_id
id -
A reference to the primary key
idof the Option table.Range
idin the corresponding Stimulus table (same subject/session/activity). -
index
index -
A 1-based index differentiating each part and indicating the stacking order of them. An option component with a higher
indexis displayed on top of those with lower values, similar to CSS z-index property.Range
1-based indices
-
panel_id
string -
Identifier of the panel this option is displayed over.
-
x_screen
integer -
X coordinates of the option component relative to the left edge of the screen in pixels.
Range
pixels
-
y_screen
integer -
Y coordinates of the option component relative to the top edge of the screen in pixels.
Range
pixels
-
x_viewport
float -
X coordinates of the option component relative to the left edge of the screen expressed as a fraction of the screen width.
Range
0 to 1 (inclusive)
-
y_viewport
float -
Y coordinates of the option component relative to the top edge of the screen expressed as a fraction of the screen height.
Range
0 to 1 (inclusive)
-
description
string -
A human readable, compact description of the component.
-
symbol_name
string -
The name of the displayed symbol.
-
symbol_count
integer -
The number of symbols represented in this component.
-
symbol_layout
enum -
How the symbols are laid out.
Range
vertical: along the Y axis.horizontal: along the X axis.diagonal_top_leftdiagonal_top_rightsquareringcrosstwo_columns
-
color_name
string -
The human-readable name of the component color, e.g.,
red. -
color_hex
string -
The hexadecimal RGB color code of the component (e.g., #FF0000 for red) with optional alpha channel for transparency.
Range
#000000(00) to #FFFFFF(FF)
-
orientation
enum -
Indicates the symbol orientation.
Key
Where
In BDM, the preferred position is the center of the object. However, specific implementations of the tasks may use other locations such as the top-left corner. If this is the case, it should be explicitly stated in the codebook.
What
If none of the predefined layouts apply, leave this field empty or use a custom human-readable label. Make sure custom labels are clearly defined in the codebook.
To maintain clarity and consistency, BDM recommends using CSS-style naming conventions for colors (e.g., “lightgray”).
If none of the predefined orientations apply, leave this field empty or use a custom human-readable label. Make sure custom labels are clearly defined in the codebook.