<BeadlTrialProtocol> element

The <BeadlTrialProtocol> element describes and implements all properties of the trial-based behavior protocol.

...
<BeadlTrialProtocol name="ExampleTask" startState="StartState" numberOfTrials="123">
  <BeadlArguments>
    ...
  </BeadlArguments>
  <HardwareSettings>
    ...
  </HardwareSettings>
  <BeadlEvents>
    ...
  </BeadlEvents>
  <BeadlActions>
    ...
  </BeadlActions>
  <BeadlStates>
    ...
  </BeadlStates>
  <BeadlStateTransitions>
    ...
  </BeadlStateTransitions>
<BeadlTrialProtocol />
...

Attributes

• name: defines the name of the protocol. The name of the protocol will be used during the code generation process for creating needed files and folders and thus should not contain any whitespace characters.
• startState: defines the starting point of the trial structure. The content must refer to one state listed later in the description.
• numberOfTrials: defines how many trials a session should last. The content of this attribute can either be a number (must be quoted) or the string literal INF to indicate that the session will not be terminated based on the number of performed trials.

Child Elements

• <BeadlArguments> element: Container for <BeadlArgument> elements
• <HardwareSettings> element: Definitions of the used behavioral control environment and definitions of the used resources via <ConnectionMapping> elements
• <BeadlEvents> element: Container for the definition of events (either <HardwareEvent> elements or <VirtualEvent> elements to be sensed for transitioning between states.
• <BeadlActions> element: Container for the definition of actions (either <HardwareActions> elements or <VirtualActions> elements to be executed when entering a state.
• <BeadlStates> element: Container for the definition of the <BeadlState> elements that define the structure of the behavioral task.
• <BeadlTransitions> element: Container for the definition of <BeadlTransition> elements that define the possible paths within the behavioral task.