Showing:

Annotations
Attributes
Diagrams
Facets
Identity Constraints
Instances
Model
Properties
Source
Used by

Table of Contents

Group by:

http://med.kuleuven.be/exporl/apex/4.1.2/experiment

Resource hierarchy:

Main schema procedure-document.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Schema to be used to validate a document containing only procedures
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema procedure.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema xmlgeneratingplugin.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Element apex:procedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType
Type apex:procedureType
Properties
content complex
Model
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:element name="procedure" type="apex:procedureType"/>
[ top ]
Element apex:adaptiveProcedure / parameters
Namespace No namespace
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType procedure-document.tmp#adaptiveProcedureParametersType_nUp procedure-document.tmp#adaptiveProcedureParametersType_nDown procedure-document.tmp#adaptiveProcedureParametersType_adapt_parameter procedure-document.tmp#adaptiveProcedureParametersType_start_value procedure-document.tmp#adaptiveProcedureParametersType_stop_after_type procedure-document.tmp#adaptiveProcedureParametersType_stop_after procedure-document.tmp#adaptiveProcedureParametersType_min_value procedure-document.tmp#adaptiveProcedureParametersType_max_value procedure-document.tmp#adaptiveProcedureParametersType_larger_is_easier procedure-document.tmp#adaptiveProcedureParametersType_repeat_first_until_correct procedure-document.tmp#adaptiveProcedureParametersType_stepsizes procedure-document.tmp#adaptiveProcedureParametersType
Type apex:adaptiveProcedureParametersType
Type hierarchy
Properties
content complex
Model
Children adapt_parameter, corrector, defaultstandard, input_during_stimulus, intervals, larger_is_easier, max_value, min_value, nDown, nUp, order, pause_between_stimuli, presentations, repeat_first_until_correct, skip, start_value, stepsizes, stop_after, stop_after_type, time_before_first_trial, uniquestandard
Instance
 
<parameters>
  <presentations>{1,1}</presentations>
  <skip>{0,1}</skip>
  <order>{1,1}</order>
  <defaultstandard>{0,1}</defaultstandard>
  <uniquestandard>{0,1}</uniquestandard>
  <intervals count="" select="">{0,1}</intervals>
  <corrector>{0,1}</corrector>
  <pause_between_stimuli>{0,1}</pause_between_stimuli>
  <time_before_first_trial>{0,1}</time_before_first_trial>
  <input_during_stimulus>{0,1}</input_during_stimulus>
  <nUp>{1,1}</nUp>
  <nDown>{1,1}</nDown>
  <adapt_parameter>{1,unbounded}</adapt_parameter>
  <start_value>{1,1}</start_value>
  <stop_after_type>{1,1}</stop_after_type>
  <stop_after>{1,1}</stop_after>
  <min_value>{0,1}</min_value>
  <max_value>{0,1}</max_value>
  <larger_is_easier>{1,1}</larger_is_easier>
  <repeat_first_until_correct>{0,1}</repeat_first_until_correct>
  <stepsizes>{1,1}</stepsizes>
</parameters>
Source
 
<xs:element name="parameters" type="apex:adaptiveProcedureParametersType"/>
[ top ]
Element apex:procedureParametersType / presentations
Namespace No namespace
Annotations
 
Number of times every trial will be
presented.
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
default 1
Source
 
<xs:element name="presentations" type="xs:positiveInteger" default="1">
  <xs:annotation>
    <xs:documentation>Number of times every trial will be presented.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / skip
Namespace No namespace
Annotations
 
Number of trials that will be presented before the actual
presentations start. Eg if skip=2 and presentations=3 then first 2 trials
will be presented and then 3*#trials. If the order is sequential, the
skipped trials will be the first skip trials from the trial list, repeated
if necessary. If the order is random, the skipped trials will be picked from
the trial list without replacement, repeating this procedure if necessary
(if skip>nTrials). Trials that are to be skipped in the results analysis are
marked with the skip tag in the results file. Warning: this has not been
thorougly checked for other procedures than constant.
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="skip" type="xs:integer" default="0" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Number of trials that will be presented before the actual presentations start. Eg if skip=2 and presentations=3 then first 2 trials will be presented and then 3*#trials. If the order is sequential, the skipped trials will be the first skip trials from the trial list, repeated if necessary. If the order is random, the skipped trials will be picked from the trial list without replacement, repeating this procedure if necessary (if skip>nTrials). Trials that are to be skipped in the results analysis are marked with the skip tag in the results file. Warning: this has not been thorougly checked for other procedures than constant.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / order
Namespace No namespace
Annotations
 
The order in which to present the trials.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration random 
Random is realized by creating a list of trials
    before the experiment starts and shuffling this
list
enumeration sequential 
Trials are presented in order of appearance in the
experiment file
Source
 
<xs:element name="order">
  <xs:annotation>
    <xs:documentation>The order in which to present the trials.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="random">
        <xs:annotation>
          <xs:documentation>Random is realized by creating a list of trials before the experiment starts and shuffling this list</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="sequential">
        <xs:annotation>
          <xs:documentation>Trials are presented in order of appearance in the experiment file</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:procedureParametersType / defaultstandard
Namespace No namespace
Annotations
 
The default standard: only relevant if choices>1 This standard
    will be used if no standard is defined in a certain
trial.
Diagram
Diagram
Type xs:Name
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="defaultstandard" minOccurs="0" maxOccurs="1" type="xs:Name">
  <xs:annotation>
    <xs:documentation>The default standard: only relevant if choices>1 This standard will be used if no standard is defined in a certain trial.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / uniquestandard
Namespace No namespace
Annotations
 
If uniquestandard is true and multiple standards are defined
per trial, Apex will try to present another standard in each interval of the
trial.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
maxOccurs 1
default false
Source
 
<xs:element name="uniquestandard" minOccurs="0" maxOccurs="1" default="false" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>If uniquestandard is true and multiple standards are defined per trial, Apex will try to present another standard in each interval of the trial.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / intervals
Namespace No namespace
Annotations
 
Associate intervals with screen elements. Only useful if count>1, otherwise
you can use a corrector.
Diagram
Diagram procedure-document.tmp#procedureParametersType_procedureParametersType_intervals_count procedure-document.tmp#procedureParametersType_procedureParametersType_intervals_select procedure-document.tmp#procedureParametersType_procedureParametersType_intervals_interval
Properties
content complex
minOccurs 0
Model
Children interval
Instance
 
<intervals count="" select="">
  <interval element="" number="">{2,unbounded}</interval>
</intervals>
Attributes
QName Type Use Annotation
count apex:intervalsCountType required 
Number of intervals
select apex:selectChoicesType optional 
If select is defined, the stimulus will only
be presented in the intervals enumerated in the select
attribute. e.g.: if select="2,3", the stimulus will never
occur in interval 1, but only in 2 and 3
Source
 
<xs:element name="intervals" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Associate intervals with screen elements. Only useful if count>1, otherwise you can use a corrector.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="interval" maxOccurs="unbounded" minOccurs="2">
        <xs:complexType>
          <xs:attribute name="number" type="xs:positiveInteger" use="required">
            <xs:annotation>
              <xs:documentation>Time slot of the stimulus</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="element" type="xs:string" use="required">
            <xs:annotation>
              <xs:documentation>Name of the screen element corresponding to the time slot</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="count" type="apex:intervalsCountType" use="required">
      <xs:annotation>
        <xs:documentation>Number of intervals</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="select" type="apex:selectChoicesType">
      <xs:annotation>
        <xs:documentation>If select is defined, the stimulus will only be presented in the intervals enumerated in the select attribute. e.g.: if select="2,3", the stimulus will never occur in interval 1, but only in 2 and 3</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:procedureParametersType / intervals / interval
Namespace No namespace
Diagram
Diagram procedure-document.tmp#procedureParametersType_procedureParametersType_intervals_procedureParametersType_procedureParametersType_intervals_interval_number procedure-document.tmp#procedureParametersType_procedureParametersType_intervals_procedureParametersType_procedureParametersType_intervals_interval_element
Properties
content complex
minOccurs 2
maxOccurs unbounded
Attributes
QName Type Use Annotation
element xs:string required 
Name of the screen element
corresponding to the time
slot
number xs:positiveInteger required 
Time slot of the
stimulus
Source
 
<xs:element name="interval" maxOccurs="unbounded" minOccurs="2">
  <xs:complexType>
    <xs:attribute name="number" type="xs:positiveInteger" use="required">
      <xs:annotation>
        <xs:documentation>Time slot of the stimulus</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="element" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>Name of the screen element corresponding to the time slot</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:procedureParametersType / corrector
Namespace No namespace
Annotations
 
Describes the corrector to be used. The corrector compares
the user input and the correct answer for a certain trail. Real
correctors are derived from apex:correctorType
Diagram
Diagram procedure-document.tmp#correctorType
Type apex:correctorType
Properties
content complex
minOccurs 0
Model
Source
 
<xs:element name="corrector" type="apex:correctorType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Describes the corrector to be used. The corrector compares the user input and the correct answer for a certain trail. Real correctors are derived from apex:correctorType</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / pause_between_stimuli
Namespace No namespace
Annotations
 
If specified, a pause of n milliseconds will be introduced
between successive stimulus/standard presentations
Diagram
Diagram
Type xs:nonNegativeInteger
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="pause_between_stimuli" minOccurs="0" type="xs:nonNegativeInteger" default="0">
  <xs:annotation>
    <xs:documentation>If specified, a pause of n milliseconds will be introduced between successive stimulus/standard presentations</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / time_before_first_trial
Namespace No namespace
Annotations
 
If specified, apex will wait for the given number of seconds
before starting the first stimulus of the first trial when the procedure is
started.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="time_before_first_trial" minOccurs="0" type="xs:double" default="0">
  <xs:annotation>
    <xs:documentation>If specified, apex will wait for the given number of seconds before starting the first stimulus of the first trial when the procedure is started.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:procedureParametersType / input_during_stimulus
Namespace No namespace
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="input_during_stimulus" type="xs:boolean" minOccurs="0" default="false"/>
[ top ]
Element apex:adaptiveProcedureParametersType / nUp
Namespace No namespace
Annotations
 
Number of times the user has to give a wrong answer before the parameter is adapted
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
Source
 
<xs:element name="nUp" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Number of times the user has to give a wrong answer before the parameter is adapted</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / nDown
Namespace No namespace
Annotations
 
Number of times the user has to give a correct answer before the parameter is adapted
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
Source
 
<xs:element name="nDown" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Number of times the user has to give a correct answer before the parameter is adapted</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / adapt_parameter
Namespace No namespace
Annotations
 
Parameter to be adapted. Can be a fixed or variable parameter. If more than one parameter is specified, all parameters will be set to the same value. Only the first parameter given can be a fixed parameter.
Fixed parameters are properties of stimuli, so when a fixed parameter is specified, the adaptive procedure will select the stimulus that has the most appropriate fixed parameter.
Diagram
Diagram
Type xs:IDREF
Properties
content simple
minOccurs 1
maxOccurs unbounded
Source
 
<xs:element name="adapt_parameter" type="xs:IDREF" minOccurs="1" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Parameter to be adapted. Can be a fixed or variable parameter. If more than one parameter is specified, all parameters will be set to the same value. Only the first parameter given can be a fixed parameter. Fixed parameters are properties of stimuli, so when a fixed parameter is specified, the adaptive procedure will select the stimulus that has the most appropriate fixed parameter.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / start_value
Namespace No namespace
Annotations
 
Start value of the parameter
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="start_value" type="xs:string">
  <xs:annotation>
    <xs:documentation>Start value of the parameter</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / stop_after_type
Namespace No namespace
Annotations
 
Criterion to be used to stop the procedure. The
    procedure will be stopped after stop_after instances of this
event.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration reversals 
Total number of reversals in the
staircase
enumeration trials 
Total number of trials to be
presented
enumeration presentations 
Corresponding to the above presentations
tag. Warning: the number of presentations as specified
in the presentations element will be used! Every
stimulus will be played the number of times specified in
the presentations element.
Source
 
<xs:element name="stop_after_type">
  <xs:annotation>
    <xs:documentation>Criterion to be used to stop the procedure. The procedure will be stopped after stop_after instances of this event.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="reversals">
        <xs:annotation>
          <xs:documentation>Total number of reversals in the staircase</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="trials">
        <xs:annotation>
          <xs:documentation>Total number of trials to be presented</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="presentations">
        <xs:annotation>
          <xs:documentation>Corresponding to the above presentations tag. Warning: the number of presentations as specified in the presentations element will be used! Every stimulus will be played the number of times specified in the presentations element.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <!-- stop after the parameters above are used -->
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / stop_after
Namespace No namespace
Annotations
 
The procedure ends after stop_after events of type
stop_after_type
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
Source
 
<xs:element name="stop_after" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>The procedure ends after stop_after events of type stop_after_type</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / min_value
Namespace No namespace
Annotations
 
Minimal value of the parameter. If the procedure tries
to go below this value, the parameter is saturated and saturation is
reported on screen and in the results file.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
Source
 
<xs:element name="min_value" type="xs:double" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Minimal value of the parameter. If the procedure tries to go below this value, the parameter is saturated and saturation is reported on screen and in the results file.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / max_value
Namespace No namespace
Annotations
 
Maximal value of the parameter. If the procedure tries
to go above this value, the parameter is saturated and saturation is
reported on screen and in the results file.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
Source
 
<xs:element name="max_value" type="xs:double" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximal value of the parameter. If the procedure tries to go above this value, the parameter is saturated and saturation is reported on screen and in the results file.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / larger_is_easier
Namespace No namespace
Annotations
 
Larger values of the parameter are easier than smaller
values
Diagram
Diagram
Type xs:boolean
Properties
content simple
default true
Source
 
<xs:element name="larger_is_easier" type="xs:boolean" default="true">
  <xs:annotation>
    <xs:documentation>Larger values of the parameter are easier than smaller values</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / repeat_first_until_correct
Namespace No namespace
Annotations
 
Repeat the first trial untill the answer is
correct.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="repeat_first_until_correct" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Repeat the first trial untill the answer is correct.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / stepsizes
Namespace No namespace
Annotations
 
Defines the stepsizes to be used to adapt the
parameter
Diagram
Diagram procedure-document.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_change_after procedure-document.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_stepsize
Properties
content complex
Model
Children change_after, stepsize
Instance
 
<stepsizes>
  <change_after>{0,1}</change_after>
  <stepsize begin="" direction="" size="">{1,unbounded}</stepsize>
</stepsizes>
Identity constraints
QName Type Refer Selector Field(s)
uniqueBeginStepsize unique stepsize @begin; @direction
Source
 
<xs:element name="stepsizes">
  <xs:annotation>
    <xs:documentation>Defines the stepsizes to be used to adapt the parameter</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="change_after" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Change the stepsize after a certain number of trials or a certain number of reversals</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="trials"/>
            <xs:enumeration value="reversals"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="stepsize" maxOccurs="unbounded" minOccurs="1">
        <xs:annotation>
          <xs:documentation>The procedure uses a step of size "size" after "begin" events of type "change_after" have occured</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:attribute name="begin" type="xs:nonNegativeInteger" use="required"/>
          <xs:attribute name="size" type="xs:double" use="required"/>
          <xs:attribute name="direction" type="apex:direction" use="optional">
            <xs:annotation>
              <xs:documentation>If this attribute is specified, this stepsize will only be used then adapting in the up/down direction. When specifying direction for a certain begin value, it needs to be specified for both up and down.</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
  <xs:unique name="uniqueBeginStepsize">
    <xs:selector xpath="stepsize"/>
    <xs:field xpath="@begin"/>
    <xs:field xpath="@direction"/>
  </xs:unique>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / stepsizes / change_after
Namespace No namespace
Annotations
 
Change the stepsize after a certain number
    of trials or a certain number of
reversals
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration trials
enumeration reversals
Source
 
<xs:element name="change_after" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Change the stepsize after a certain number of trials or a certain number of reversals</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="trials"/>
      <xs:enumeration value="reversals"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:adaptiveProcedureParametersType / stepsizes / stepsize
Namespace No namespace
Annotations
 
The procedure uses a step of size "size"
after "begin" events of type "change_after" have occured
Diagram
Diagram procedure-document.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_stepsize_begin procedure-document.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_stepsize_size procedure-document.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_stepsize_direction
Properties
content complex
minOccurs 1
maxOccurs unbounded
Attributes
QName Type Use Annotation
begin xs:nonNegativeInteger required
direction apex:direction optional 
If this attribute is specified, this stepsize will only be used then adapting in the up/down direction.
When specifying direction for a certain begin value, it needs to be specified for both up and down.
size xs:double required
Source
 
<xs:element name="stepsize" maxOccurs="unbounded" minOccurs="1">
  <xs:annotation>
    <xs:documentation>The procedure uses a step of size "size" after "begin" events of type "change_after" have occured</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:attribute name="begin" type="xs:nonNegativeInteger" use="required"/>
    <xs:attribute name="size" type="xs:double" use="required"/>
    <xs:attribute name="direction" type="apex:direction" use="optional">
      <xs:annotation>
        <xs:documentation>If this attribute is specified, this stepsize will only be used then adapting in the up/down direction. When specifying direction for a certain begin value, it needs to be specified for both up and down.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:adaptiveProcedure / trials
Namespace No namespace
Annotations
 
Trials are selected according to the sequence
parameter. A trial can contain multiple stimuli. If the parameter to
be adapted is fixed, a stimulus is selected from this list according
to the target value of the parameter of the procedure. If more than
one stimulus has the same fixed parameter value, a random stimulus
is selected out of this subset. If no exact match for the fixed
parameter is found, the closest match is used. If the parameter to
be adapted is variable, the value of the parameter is set right
before stimulus output.
Diagram
Diagram procedure-document.tmp#trialsType_trial procedure-document.tmp#trialsType_plugintrials procedure-document.tmp#trialsType
Type apex:trialsType
Properties
content complex
Model
Children plugintrials, trial
Instance
 
<trials>
  <trial id="">{0,unbounded}</trial>
  <plugintrials>{0,unbounded}</plugintrials>
</trials>
Source
 
<xs:element name="trials" type="apex:trialsType">
  <xs:annotation>
    <xs:documentation>Trials are selected according to the sequence parameter. A trial can contain multiple stimuli. If the parameter to be adapted is fixed, a stimulus is selected from this list according to the target value of the parameter of the procedure. If more than one stimulus has the same fixed parameter value, a random stimulus is selected out of this subset. If no exact match for the fixed parameter is found, the closest match is used. If the parameter to be adapted is variable, the value of the parameter is set right before stimulus output.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialsType / trial
Namespace No namespace
Diagram
Diagram procedure-document.tmp#trialType_id procedure-document.tmp#trialType_answer procedure-document.tmp#trialType_answer_element procedure-document.tmp#trialType_screen procedure-document.tmp#trialType_stimulus procedure-document.tmp#trialType_standard procedure-document.tmp#trialType
Type apex:trialType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children answer, answer_element, screen, standard, stimulus
Instance
 
<trial id="">
  <answer>{0,1}</answer>
  <answer_element>{0,1}</answer_element>
  <screen id="">{1,1}</screen>
  <stimulus id="">{0,unbounded}</stimulus>
  <standard id="">{0,unbounded}</standard>
</trial>
Attributes
QName Type Use
id xs:ID required
Identity constraints
QName Type Refer Selector Field(s)
trialKey key apex:trial @apex:id
stimulusRef keyref apex:trialKey apex:stimulus apex:stimuli/apex:stimulus/apex:id
Source
 
<xs:element name="trial" type="apex:trialType" minOccurs="0" maxOccurs="unbounded">
  <xs:key name="trialKey">
    <xs:selector xpath="apex:trial">
    </xs:selector>
    <xs:field xpath="@apex:id">
    </xs:field>
  </xs:key>
  <xs:keyref refer="apex:trialKey" name="stimulusRef">
    <xs:selector xpath="apex:stimulus">
    </xs:selector>
    <xs:field xpath="apex:stimuli/apex:stimulus/apex:id">
    </xs:field>
  </xs:keyref>
</xs:element>
[ top ]
Element apex:trialType / answer
Namespace No namespace
Annotations
 
The correct answer for this trial. Can be the name of a screen
element, a string, a number or mixed xml data.
Diagram
Diagram procedure-document.tmp#trialType_trialType_answer_key procedure-document.tmp#trialType_trialType_answer_skey
Properties
content complex
minOccurs 0
mixed true
Model
Children key, skey
Instance
 
<answer>
  <key>{0,unbounded}</key>
  <skey>{0,unbounded}</skey>
</answer>
Source
 
<xs:element name="answer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The correct answer for this trial. Can be the name of a screen element, a string, a number or mixed xml data.</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="true">
    <xs:choice maxOccurs="unbounded" minOccurs="0">
      <xs:element name="key" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Keyword, to be used by the corrector</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="skey" type="xs:string" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Part of a split keyword, to be used by the corrector.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:trialType / answer / key
Namespace No namespace
Annotations
 
Keyword, to be used by the
corrector
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
 
<xs:element name="key" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Keyword, to be used by the corrector</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialType / answer / skey
Namespace No namespace
Annotations
 
Part of a split keyword, to be used by the
corrector.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
 
<xs:element name="skey" type="xs:string" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Part of a split keyword, to be used by the corrector.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialType / answer_element
Namespace No namespace
Annotations
 
Screen element that contains the user input to be used by the
corrector.
Diagram
Diagram
Type xs:IDREF
Properties
content simple
minOccurs 0
Source
 
<xs:element name="answer_element" type="xs:IDREF" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Screen element that contains the user input to be used by the corrector.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialType / screen
Namespace No namespace
Annotations
 
Screen to be shown
Diagram
Diagram procedure-document.tmp#screenRefType_id procedure-document.tmp#screenRefType
Type apex:screenRefType
Properties
content complex
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:element name="screen" type="apex:screenRefType">
  <xs:annotation>
    <xs:documentation>Screen to be shown</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialType / stimulus
Namespace No namespace
Annotations
 
One or more stimuli. An adaptive procedure using a fixed
parameter will select one of these stimuli. Other procedures select a random
stimulus if more than one is present. Notice that it is not guaranteed that
all stimuli will be presented an equal number of times, in the case a random
stimulus is selected here.
Diagram
Diagram procedure-document.tmp#stimulusRefType_id procedure-document.tmp#stimulusRefType
Type apex:stimulusRefType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:element name="stimulus" type="apex:stimulusRefType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>One or more stimuli. An adaptive procedure using a fixed parameter will select one of these stimuli. Other procedures select a random stimulus if more than one is present. Notice that it is not guaranteed that all stimuli will be presented an equal number of times, in the case a random stimulus is selected here.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialType / standard
Namespace No namespace
Annotations
 
The standard to be used when procedure/choices>1. The standard
will be presented on every time-slot except for one when the stimulus is
presented. If more than one standard is defined, a random standard will be
selected for each presentation. If e.g. 3 standards are defined and
choices=4, a possible sequence would be standard1 stimulus1 standard2
standard1
Diagram
Diagram procedure-document.tmp#stimulusRefType_id procedure-document.tmp#stimulusRefType
Type apex:stimulusRefType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:element name="standard" type="apex:stimulusRefType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>The standard to be used when procedure/choices>1. The standard will be presented on every time-slot except for one when the stimulus is presented. If more than one standard is defined, a random standard will be selected for each presentation. If e.g. 3 standards are defined and choices=4, a possible sequence would be standard1 stimulus1 standard2 standard1</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trialsType / plugintrials
Namespace No namespace
Diagram
Diagram procedure-document.tmp#xmlGeneratingPluginType_script procedure-document.tmp#xmlGeneratingPluginType_parameter procedure-document.tmp#xmlGeneratingPluginType procedure-document.tmp#pluginTrialType
Type apex:pluginTrialType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children parameter, script
Instance
 
<plugintrials>
  <script source="">{0,1}</script>
  <parameter name="">{0,unbounded}</parameter>
</plugintrials>
Source
 
<xs:element name="plugintrials" type="apex:pluginTrialType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:xmlGeneratingPluginType / script
Namespace No namespace
Diagram
Diagram procedure-document.tmp#xmlGeneratingPluginType_xmlGeneratingPluginType_script_source
Type extension of xs:string
Properties
content complex
minOccurs 0
Attributes
QName Type Use
source restriction of xs:string required
Source
 
<xs:element name="script" minOccurs="0">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="source" use="required">
          <xs:simpleType>
            <xs:annotation>
              <xs:documentation>If inline, the ECMAScript function must be defined inside this element, if file, the filename must be given</xs:documentation>
            </xs:annotation>
            <xs:restriction base="xs:string">
              <xs:enumeration value="inline"/>
              <xs:enumeration value="file"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:xmlGeneratingPluginType / parameter
Namespace No namespace
Diagram
Diagram procedure-document.tmp#xmlGeneratingPluginType_xmlGeneratingPluginType_parameter_name
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
default
Attributes
QName Type Use
name xs:Name required
Source
 
<xs:element name="parameter" default="" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="name" type="xs:Name" use="required"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:constantProcedure / parameters
Namespace No namespace
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType procedure-document.tmp#constantProcedureParametersType
Type apex:constantProcedureParametersType
Type hierarchy
Properties
content complex
Model
Children corrector, defaultstandard, input_during_stimulus, intervals, order, pause_between_stimuli, presentations, skip, time_before_first_trial, uniquestandard
Instance
 
<parameters>
  <presentations>{1,1}</presentations>
  <skip>{0,1}</skip>
  <order>{1,1}</order>
  <defaultstandard>{0,1}</defaultstandard>
  <uniquestandard>{0,1}</uniquestandard>
  <intervals count="" select="">{0,1}</intervals>
  <corrector>{0,1}</corrector>
  <pause_between_stimuli>{0,1}</pause_between_stimuli>
  <time_before_first_trial>{0,1}</time_before_first_trial>
  <input_during_stimulus>{0,1}</input_during_stimulus>
</parameters>
Source
 
<xs:element name="parameters" type="apex:constantProcedureParametersType"/>
[ top ]
Element apex:constantProcedure / trials
Namespace No namespace
Annotations
 
If a trial contains more than one stimulus, a random
one will be selected.
Diagram
Diagram procedure-document.tmp#trialsType_trial procedure-document.tmp#trialsType_plugintrials procedure-document.tmp#trialsType
Type apex:trialsType
Properties
content complex
Model
Children plugintrials, trial
Instance
 
<trials>
  <trial id="">{0,unbounded}</trial>
  <plugintrials>{0,unbounded}</plugintrials>
</trials>
Source
 
<xs:element name="trials" type="apex:trialsType">
  <xs:annotation>
    <xs:documentation>If a trial contains more than one stimulus, a random one will be selected.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:trainingProcedure / parameters
Namespace No namespace
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType procedure-document.tmp#trainingProcedureParametersType
Type apex:trainingProcedureParametersType
Type hierarchy
Properties
content complex
Model
Children corrector, defaultstandard, input_during_stimulus, intervals, order, pause_between_stimuli, presentations, skip, time_before_first_trial, uniquestandard
Instance
 
<parameters>
  <presentations>{1,1}</presentations>
  <skip>{0,1}</skip>
  <order>{1,1}</order>
  <defaultstandard>{0,1}</defaultstandard>
  <uniquestandard>{0,1}</uniquestandard>
  <intervals count="" select="">{0,1}</intervals>
  <corrector>{0,1}</corrector>
  <pause_between_stimuli>{0,1}</pause_between_stimuli>
  <time_before_first_trial>{0,1}</time_before_first_trial>
  <input_during_stimulus>{0,1}</input_during_stimulus>
</parameters>
Source
 
<xs:element name="parameters" type="apex:trainingProcedureParametersType"/>
[ top ]
Element apex:trainingProcedure / trials
Namespace No namespace
Diagram
Diagram procedure-document.tmp#trialsType_trial procedure-document.tmp#trialsType_plugintrials procedure-document.tmp#trialsType
Type apex:trialsType
Properties
content complex
Model
Children plugintrials, trial
Instance
 
<trials>
  <trial id="">{0,unbounded}</trial>
  <plugintrials>{0,unbounded}</plugintrials>
</trials>
Source
 
<xs:element name="trials" type="apex:trialsType"/>
[ top ]
Element apex:multiProcedure / parameters
Namespace No namespace
Diagram
Diagram procedure-document.tmp#multiProcedureParametersType_order procedure-document.tmp#multiProcedureParametersType
Type apex:multiProcedureParametersType
Properties
content complex
Model
Children order
Instance
 
<parameters>
  <order>{1,1}</order>
</parameters>
Source
 
<xs:element name="parameters" type="apex:multiProcedureParametersType"/>
[ top ]
Element apex:multiProcedureParametersType / order
Namespace No namespace
Annotations
 
Order of interleaving the child procedures.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration random
enumeration sequential
enumeration onebyone 
Present the procedures one by one: only start the
next procedure if the previous one is finished
Source
 
<xs:element name="order">
  <xs:annotation>
    <xs:documentation>Order of interleaving the child procedures.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="random"/>
      <xs:enumeration value="sequential"/>
      <xs:enumeration value="onebyone">
        <xs:annotation>
          <xs:documentation>Present the procedures one by one: only start the next procedure if the previous one is finished</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:multiProcedure / procedure
Namespace No namespace
Annotations
 
All child procedures MUST have an
ID
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType
Type apex:procedureType
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:element name="procedure" type="apex:procedureType" minOccurs="1" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>All child procedures MUST have an ID</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:pluginProcedure / parameters
Namespace No namespace
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType procedure-document.tmp#pluginProcedureParametersType_script procedure-document.tmp#pluginProcedureParametersType_debugger procedure-document.tmp#pluginProcedureParametersType_adjust_parameter procedure-document.tmp#pluginProcedureParametersType_parameter procedure-document.tmp#pluginProcedureParametersType
Type apex:pluginProcedureParametersType
Type hierarchy
Properties
content complex
Model
Children adjust_parameter, corrector, debugger, defaultstandard, input_during_stimulus, intervals, order, parameter, pause_between_stimuli, presentations, script, skip, time_before_first_trial, uniquestandard
Instance
 
<parameters>
  <presentations>{1,1}</presentations>
  <skip>{0,1}</skip>
  <order>{1,1}</order>
  <defaultstandard>{0,1}</defaultstandard>
  <uniquestandard>{0,1}</uniquestandard>
  <intervals count="" select="">{0,1}</intervals>
  <corrector>{0,1}</corrector>
  <pause_between_stimuli>{0,1}</pause_between_stimuli>
  <time_before_first_trial>{0,1}</time_before_first_trial>
  <input_during_stimulus>{0,1}</input_during_stimulus>
  <script>{1,1}</script>
  <debugger>{0,1}</debugger>
  <adjust_parameter>{0,1}</adjust_parameter>
  <parameter name="">{0,unbounded}</parameter>
</parameters>
Source
 
<xs:element name="parameters" type="apex:pluginProcedureParametersType"/>
[ top ]
Element apex:pluginProcedureParametersType / script
Namespace No namespace
Annotations
 
Name of the script to be used as plugin procedure
TODO
Diagram
Diagram
Properties
minOccurs 1
Source
 
<xs:element name="script" minOccurs="1">
  <xs:annotation>
    <xs:documentation>Name of the script to be used as plugin procedure TODO</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:pluginProcedureParametersType / debugger
Namespace No namespace
Annotations
 
If true, a JavaScript debugger will be shown upon errors, or when the "debugger" statement is encountered in the script
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="debugger" minOccurs="0" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>If true, a JavaScript debugger will be shown upon errors, or when the "debugger" statement is encountered in the script</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:pluginProcedureParametersType / adjust_parameter
Namespace No namespace
Annotations
 
Parameter to be modified by the procedure
Diagram
Diagram
Type xs:IDREF
Properties
content simple
minOccurs 0
Source
 
<xs:element name="adjust_parameter" type="xs:IDREF" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Parameter to be modified by the procedure</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:pluginProcedureParametersType / parameter
Namespace No namespace
Diagram
Diagram procedure-document.tmp#pluginProcedureParametersType_pluginProcedureParametersType_parameter_name
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
name xs:Name required
Source
 
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="name" type="xs:Name" use="required"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:pluginProcedure / trials
Namespace No namespace
Diagram
Diagram procedure-document.tmp#trialsType_trial procedure-document.tmp#trialsType_plugintrials procedure-document.tmp#trialsType
Type apex:trialsType
Properties
content complex
Model
Children plugintrials, trial
Instance
 
<trials>
  <trial id="">{0,unbounded}</trial>
  <plugintrials>{0,unbounded}</plugintrials>
</trials>
Source
 
<xs:element name="trials" type="apex:trialsType"/>
[ top ]
Element apex:variableParametersType / parameter
Namespace No namespace
Diagram
Diagram procedure-document.tmp#parameterType_type procedure-document.tmp#parameterType procedure-document.tmp#hasIdParameterType_id procedure-document.tmp#hasIdParameterType
Type apex:hasIdParameterType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
id xs:ID required
type xs:string required
Source
 
<xs:element name="parameter" type="apex:hasIdParameterType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:fixedParametersType / parameter
Namespace No namespace
Diagram
Diagram procedure-document.tmp#maybeIdParameterType_type procedure-document.tmp#maybeIdParameterType_id procedure-document.tmp#maybeIdParameterType
Type apex:maybeIdParameterType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
id xs:ID optional
type xs:string required
Source
 
<xs:element name="parameter" type="apex:maybeIdParameterType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Complex Type apex:procedureType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureType_id
Properties
abstract true
Used by
Model
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:complexType name="procedureType" abstract="true">
  <xs:sequence>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="optional">
    <xs:annotation>
      <xs:documentation>The ID is optional, except for child procedures of a multiprocedure. IDs are reported in the results file.</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
[ top ]
Complex Type apex:adaptiveProcedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Adaptive procedure according to Levitt (1978) Adapts a certain
parameter according to the correctness of the last answer.
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType procedure-document.tmp#adaptiveProcedure_parameters procedure-document.tmp#adaptiveProcedure_trials
Type extension of apex:procedureType
Type hierarchy
Model
Children parameters, trials
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:complexType name="adaptiveProcedure">
  <xs:annotation>
    <xs:documentation>Adaptive procedure according to Levitt (1978) Adapts a certain parameter according to the correctness of the last answer.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:procedureType">
      <xs:sequence>
        <xs:element name="parameters" type="apex:adaptiveProcedureParametersType"/>
        <xs:element name="trials" type="apex:trialsType">
          <xs:annotation>
            <xs:documentation>Trials are selected according to the sequence parameter. A trial can contain multiple stimuli. If the parameter to be adapted is fixed, a stimulus is selected from this list according to the target value of the parameter of the procedure. If more than one stimulus has the same fixed parameter value, a random stimulus is selected out of this subset. If no exact match for the fixed parameter is found, the closest match is used. If the parameter to be adapted is variable, the value of the parameter is set right before stimulus output.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:adaptiveProcedureParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType procedure-document.tmp#adaptiveProcedureParametersType_nUp procedure-document.tmp#adaptiveProcedureParametersType_nDown procedure-document.tmp#adaptiveProcedureParametersType_adapt_parameter procedure-document.tmp#adaptiveProcedureParametersType_start_value procedure-document.tmp#adaptiveProcedureParametersType_stop_after_type procedure-document.tmp#adaptiveProcedureParametersType_stop_after procedure-document.tmp#adaptiveProcedureParametersType_min_value procedure-document.tmp#adaptiveProcedureParametersType_max_value procedure-document.tmp#adaptiveProcedureParametersType_larger_is_easier procedure-document.tmp#adaptiveProcedureParametersType_repeat_first_until_correct procedure-document.tmp#adaptiveProcedureParametersType_stepsizes
Type extension of apex:procedureParametersType
Type hierarchy
Used by
Model
Children adapt_parameter, corrector, defaultstandard, input_during_stimulus, intervals, larger_is_easier, max_value, min_value, nDown, nUp, order, pause_between_stimuli, presentations, repeat_first_until_correct, skip, start_value, stepsizes, stop_after, stop_after_type, time_before_first_trial, uniquestandard
Source
 
<xs:complexType name="adaptiveProcedureParametersType">
  <xs:complexContent>
    <xs:extension base="apex:procedureParametersType">
      <xs:sequence>
        <xs:element name="nUp" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>Number of times the user has to give a wrong answer before the parameter is adapted</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="nDown" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>Number of times the user has to give a correct answer before the parameter is adapted</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="adapt_parameter" type="xs:IDREF" minOccurs="1" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>Parameter to be adapted. Can be a fixed or variable parameter. If more than one parameter is specified, all parameters will be set to the same value. Only the first parameter given can be a fixed parameter. Fixed parameters are properties of stimuli, so when a fixed parameter is specified, the adaptive procedure will select the stimulus that has the most appropriate fixed parameter.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="start_value" type="xs:string">
          <xs:annotation>
            <xs:documentation>Start value of the parameter</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="stop_after_type">
          <xs:annotation>
            <xs:documentation>Criterion to be used to stop the procedure. The procedure will be stopped after stop_after instances of this event.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="reversals">
                <xs:annotation>
                  <xs:documentation>Total number of reversals in the staircase</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="trials">
                <xs:annotation>
                  <xs:documentation>Total number of trials to be presented</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="presentations">
                <xs:annotation>
                  <xs:documentation>Corresponding to the above presentations tag. Warning: the number of presentations as specified in the presentations element will be used! Every stimulus will be played the number of times specified in the presentations element.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <!-- stop after the parameters above are used -->
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="stop_after" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>The procedure ends after stop_after events of type stop_after_type</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="min_value" type="xs:double" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Minimal value of the parameter. If the procedure tries to go below this value, the parameter is saturated and saturation is reported on screen and in the results file.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="max_value" type="xs:double" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Maximal value of the parameter. If the procedure tries to go above this value, the parameter is saturated and saturation is reported on screen and in the results file.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <!--xs:element name="rev_for_mean" type="xs:positiveInteger" minOccurs="0">
                        <xs:annotation>
                            <xs:documentation>Number of reversals to be taken for mean value.
                                Currently only used in xslt scripts to convert/analyse the resuls
                                file.</xs:documentation>
                        </xs:annotation>
                    </xs:element-->
        <xs:element name="larger_is_easier" type="xs:boolean" default="true">
          <xs:annotation>
            <xs:documentation>Larger values of the parameter are easier than smaller values</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="repeat_first_until_correct" type="xs:boolean" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Repeat the first trial untill the answer is correct.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="stepsizes">
          <xs:annotation>
            <xs:documentation>Defines the stepsizes to be used to adapt the parameter</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:sequence>
              <xs:element name="change_after" minOccurs="0">
                <xs:annotation>
                  <xs:documentation>Change the stepsize after a certain number of trials or a certain number of reversals</xs:documentation>
                </xs:annotation>
                <xs:simpleType>
                  <xs:restriction base="xs:string">
                    <xs:enumeration value="trials"/>
                    <xs:enumeration value="reversals"/>
                  </xs:restriction>
                </xs:simpleType>
              </xs:element>
              <xs:element name="stepsize" maxOccurs="unbounded" minOccurs="1">
                <xs:annotation>
                  <xs:documentation>The procedure uses a step of size "size" after "begin" events of type "change_after" have occured</xs:documentation>
                </xs:annotation>
                <xs:complexType>
                  <xs:attribute name="begin" type="xs:nonNegativeInteger" use="required"/>
                  <xs:attribute name="size" type="xs:double" use="required"/>
                  <xs:attribute name="direction" type="apex:direction" use="optional">
                    <xs:annotation>
                      <xs:documentation>If this attribute is specified, this stepsize will only be used then adapting in the up/down direction. When specifying direction for a certain begin value, it needs to be specified for both up and down.</xs:documentation>
                    </xs:annotation>
                  </xs:attribute>
                </xs:complexType>
              </xs:element>
            </xs:sequence>
          </xs:complexType>
          <xs:unique name="uniqueBeginStepsize">
            <xs:selector xpath="stepsize"/>
            <xs:field xpath="@begin"/>
            <xs:field xpath="@direction"/>
          </xs:unique>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:procedureParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus
Used by
Model
Children corrector, defaultstandard, input_during_stimulus, intervals, order, pause_between_stimuli, presentations, skip, time_before_first_trial, uniquestandard
Source
 
<xs:complexType name="procedureParametersType">
  <xs:sequence>
    <xs:element name="presentations" type="xs:positiveInteger" default="1">
      <xs:annotation>
        <xs:documentation>Number of times every trial will be presented.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="skip" type="xs:integer" default="0" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Number of trials that will be presented before the actual presentations start. Eg if skip=2 and presentations=3 then first 2 trials will be presented and then 3*#trials. If the order is sequential, the skipped trials will be the first skip trials from the trial list, repeated if necessary. If the order is random, the skipped trials will be picked from the trial list without replacement, repeating this procedure if necessary (if skip>nTrials). Trials that are to be skipped in the results analysis are marked with the skip tag in the results file. Warning: this has not been thorougly checked for other procedures than constant.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="order">
      <xs:annotation>
        <xs:documentation>The order in which to present the trials.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="random">
            <xs:annotation>
              <xs:documentation>Random is realized by creating a list of trials before the experiment starts and shuffling this list</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="sequential">
            <xs:annotation>
              <xs:documentation>Trials are presented in order of appearance in the experiment file</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="defaultstandard" minOccurs="0" maxOccurs="1" type="xs:Name">
      <xs:annotation>
        <xs:documentation>The default standard: only relevant if choices>1 This standard will be used if no standard is defined in a certain trial.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="uniquestandard" minOccurs="0" maxOccurs="1" default="false" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>If uniquestandard is true and multiple standards are defined per trial, Apex will try to present another standard in each interval of the trial.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <!--xs:element name="choices" minOccurs="0" default="1">
                <xs:annotation>
                    <xs:documentation>Number of choices: choices stimuli are presented, one of which
                        is the stimulus. The others are the current standard (defined in the trial
                        or the default standard). To be combined with an "alternatives"
                    corrector.</xs:documentation>
                </xs:annotation>
                <xs:complexType>
                    <xs:simpleContent>
                        <xs:extension base="xs:positiveInteger">
                            <xs:attribute name="select" type="apex:selectChoicesType">
                                <xs:annotation>
                                    <xs:documentation>If select is defined, the stimulus will only
                                        be presented in the intervals enumerated in the select
                                        attribute. e.g.: if select="2,3", the stimulus will never
                                        occur in interval 1, but only in 2 and 3</xs:documentation>
                                </xs:annotation>
                            </xs:attribute>
                        </xs:extension>
                    </xs:simpleContent>
                </xs:complexType>
            </xs:element-->
    <xs:choice>
      <xs:element name="intervals" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Associate intervals with screen elements. Only useful if count>1, otherwise you can use a corrector.</xs:documentation>
        </xs:annotation>
        <xs:complexType>
          <xs:sequence>
            <xs:element name="interval" maxOccurs="unbounded" minOccurs="2">
              <xs:complexType>
                <xs:attribute name="number" type="xs:positiveInteger" use="required">
                  <xs:annotation>
                    <xs:documentation>Time slot of the stimulus</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
                <xs:attribute name="element" type="xs:string" use="required">
                  <xs:annotation>
                    <xs:documentation>Name of the screen element corresponding to the time slot</xs:documentation>
                  </xs:annotation>
                </xs:attribute>
              </xs:complexType>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="count" type="apex:intervalsCountType" use="required">
            <xs:annotation>
              <xs:documentation>Number of intervals</xs:documentation>
            </xs:annotation>
          </xs:attribute>
          <xs:attribute name="select" type="apex:selectChoicesType">
            <xs:annotation>
              <xs:documentation>If select is defined, the stimulus will only be presented in the intervals enumerated in the select attribute. e.g.: if select="2,3", the stimulus will never occur in interval 1, but only in 2 and 3</xs:documentation>
            </xs:annotation>
          </xs:attribute>
        </xs:complexType>
      </xs:element>
      <xs:element name="corrector" type="apex:correctorType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Describes the corrector to be used. The corrector compares the user input and the correct answer for a certain trail. Real correctors are derived from apex:correctorType</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
    <xs:element name="pause_between_stimuli" minOccurs="0" type="xs:nonNegativeInteger" default="0">
      <xs:annotation>
        <xs:documentation>If specified, a pause of n milliseconds will be introduced between successive stimulus/standard presentations</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="time_before_first_trial" minOccurs="0" type="xs:double" default="0">
      <xs:annotation>
        <xs:documentation>If specified, apex will wait for the given number of seconds before starting the first stimulus of the first trial when the procedure is started.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="input_during_stimulus" type="xs:boolean" minOccurs="0" default="false"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Simple Type apex:intervalsCountType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:positiveInteger
Facets
minInclusive 2
Used by
Source
 
<xs:simpleType name="intervalsCountType">
  <xs:restriction base="xs:positiveInteger">
    <xs:minInclusive value="2"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Simple Type apex:selectChoicesType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
pattern \d+(,\d+)*
Used by
Source
 
<xs:simpleType name="selectChoicesType">
  <xs:restriction base="xs:string">
    <xs:pattern value="\d+(,\d+)*"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:correctorType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Base type for all correctors
Diagram
Diagram
Properties
abstract true
Used by
Model
Source
 
<xs:complexType name="correctorType" abstract="true">
  <xs:annotation>
    <xs:documentation>Base type for all correctors</xs:documentation>
  </xs:annotation>
  <xs:sequence>
  </xs:sequence>
</xs:complexType>
[ top ]
Simple Type apex:direction
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration down
enumeration up
Used by
Source
 
<xs:simpleType name="direction">
  <xs:restriction base="xs:string">
    <xs:enumeration value="down"/>
    <xs:enumeration value="up"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:trialsType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#trialsType_trial procedure-document.tmp#trialsType_plugintrials
Used by
Model
Children plugintrials, trial
Source
 
<xs:complexType name="trialsType">
  <xs:sequence>
    <xs:element name="trial" type="apex:trialType" minOccurs="0" maxOccurs="unbounded">
      <xs:key name="trialKey">
        <xs:selector xpath="apex:trial">
        </xs:selector>
        <xs:field xpath="@apex:id">
        </xs:field>
      </xs:key>
      <xs:keyref refer="apex:trialKey" name="stimulusRef">
        <xs:selector xpath="apex:stimulus">
        </xs:selector>
        <xs:field xpath="apex:stimuli/apex:stimulus/apex:id">
        </xs:field>
      </xs:keyref>
    </xs:element>
    <xs:element name="plugintrials" type="apex:pluginTrialType" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:trialType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#trialType_id procedure-document.tmp#trialType_answer procedure-document.tmp#trialType_answer_element procedure-document.tmp#trialType_screen procedure-document.tmp#trialType_stimulus procedure-document.tmp#trialType_standard
Used by
Model
Children answer, answer_element, screen, standard, stimulus
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="trialType">
  <xs:sequence>
    <xs:element name="answer" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The correct answer for this trial. Can be the name of a screen element, a string, a number or mixed xml data.</xs:documentation>
      </xs:annotation>
      <xs:complexType mixed="true">
        <xs:choice maxOccurs="unbounded" minOccurs="0">
          <xs:element name="key" type="xs:string" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Keyword, to be used by the corrector</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="skey" type="xs:string" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Part of a split keyword, to be used by the corrector.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:choice>
      </xs:complexType>
    </xs:element>
    <xs:element name="answer_element" type="xs:IDREF" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Screen element that contains the user input to be used by the corrector.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="screen" type="apex:screenRefType">
      <xs:annotation>
        <xs:documentation>Screen to be shown</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="stimulus" type="apex:stimulusRefType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>One or more stimuli. An adaptive procedure using a fixed parameter will select one of these stimuli. Other procedures select a random stimulus if more than one is present. Notice that it is not guaranteed that all stimuli will be presented an equal number of times, in the case a random stimulus is selected here.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="standard" type="apex:stimulusRefType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>The standard to be used when procedure/choices>1. The standard will be presented on every time-slot except for one when the stimulus is presented. If more than one standard is defined, a random standard will be selected for each presentation. If e.g. 3 standards are defined and choices=4, a possible sequence would be standard1 stimulus1 standard2 standard1</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:screenRefType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#screenRefType_id
Used by
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:complexType name="screenRefType">
  <!--xs:attribute name="id" type="xs:IDREF" use="required"> </xs:attribute-->
  <xs:attribute name="id" type="xs:Name" use="required">
  </xs:attribute>
</xs:complexType>
[ top ]
Complex Type apex:stimulusRefType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#stimulusRefType_id
Used by
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:complexType name="stimulusRefType">
  <xs:attribute name="id" type="xs:Name" use="required">
  </xs:attribute>
</xs:complexType>
[ top ]
Complex Type apex:pluginTrialType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#xmlGeneratingPluginType_script procedure-document.tmp#xmlGeneratingPluginType_parameter procedure-document.tmp#xmlGeneratingPluginType
Type extension of apex:xmlGeneratingPluginType
Type hierarchy
Used by
Model
Children parameter, script
Source
 
<xs:complexType name="pluginTrialType">
  <xs:complexContent>
    <xs:extension base="apex:xmlGeneratingPluginType"/>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:xmlGeneratingPluginType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#xmlGeneratingPluginType_script procedure-document.tmp#xmlGeneratingPluginType_parameter
Used by
Complex Type apex:pluginTrialType
Model
Children parameter, script
Source
 
<xs:complexType name="xmlGeneratingPluginType">
  <xs:sequence>
    <xs:element name="script" minOccurs="0">
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:string">
            <xs:attribute name="source" use="required">
              <xs:simpleType>
                <xs:annotation>
                  <xs:documentation>If inline, the ECMAScript function must be defined inside this element, if file, the filename must be given</xs:documentation>
                </xs:annotation>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="inline"/>
                  <xs:enumeration value="file"/>
                </xs:restriction>
              </xs:simpleType>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="parameter" default="" minOccurs="0" maxOccurs="unbounded">
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:string">
            <xs:attribute name="name" type="xs:Name" use="required"/>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <!--xs:attribute name="id" type="xs:ID" use="required"/-->
</xs:complexType>
[ top ]
Complex Type apex:constantProcedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Every trial is presented a specified number of
times.
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType procedure-document.tmp#constantProcedure_parameters procedure-document.tmp#constantProcedure_trials
Type extension of apex:procedureType
Type hierarchy
Model
Children parameters, trials
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:complexType name="constantProcedure">
  <xs:annotation>
    <xs:documentation>Every trial is presented a specified number of times.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:procedureType">
      <xs:sequence>
        <xs:element name="parameters" type="apex:constantProcedureParametersType"/>
        <xs:element name="trials" type="apex:trialsType">
          <xs:annotation>
            <xs:documentation>If a trial contains more than one stimulus, a random one will be selected.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:constantProcedureParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType
Type extension of apex:procedureParametersType
Type hierarchy
Used by
Model
Children corrector, defaultstandard, input_during_stimulus, intervals, order, pause_between_stimuli, presentations, skip, time_before_first_trial, uniquestandard
Source
 
<xs:complexType name="constantProcedureParametersType">
  <xs:complexContent>
    <xs:extension base="apex:procedureParametersType">
      <xs:sequence>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:trainingProcedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
The training procedure is the reverse of the constant procedure: a
stimulus is presented AFTER the uses gives input. The trial to be presented is
determined according to the user input. If no corresponding trial is found, an error
dialog box is shown. This procedure is designed to be used as a drop-in instead of
the constant procedure to let subjects perform training before starting the actual
experiment.
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType procedure-document.tmp#trainingProcedure_parameters procedure-document.tmp#trainingProcedure_trials
Type extension of apex:procedureType
Type hierarchy
Model
Children parameters, trials
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:complexType name="trainingProcedure">
  <xs:annotation>
    <xs:documentation>The training procedure is the reverse of the constant procedure: a stimulus is presented AFTER the uses gives input. The trial to be presented is determined according to the user input. If no corresponding trial is found, an error dialog box is shown. This procedure is designed to be used as a drop-in instead of the constant procedure to let subjects perform training before starting the actual experiment.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:procedureType">
      <xs:sequence>
        <xs:element name="parameters" type="apex:trainingProcedureParametersType"/>
        <xs:element name="trials" type="apex:trialsType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:trainingProcedureParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType
Type extension of apex:procedureParametersType
Type hierarchy
Used by
Model
Children corrector, defaultstandard, input_during_stimulus, intervals, order, pause_between_stimuli, presentations, skip, time_before_first_trial, uniquestandard
Source
 
<xs:complexType name="trainingProcedureParametersType">
  <xs:complexContent>
    <xs:extension base="apex:procedureParametersType">
      <xs:sequence>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:multiProcedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
The multiprocedure contains several child procedures and selects
    between them. This procedure ends when all child procedures have
ended.
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType procedure-document.tmp#multiProcedure_parameters procedure-document.tmp#multiProcedure_procedure
Type extension of apex:procedureType
Type hierarchy
Model
Children parameters, procedure
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:complexType name="multiProcedure">
  <xs:annotation>
    <xs:documentation>The multiprocedure contains several child procedures and selects between them. This procedure ends when all child procedures have ended.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:procedureType">
      <xs:sequence>
        <xs:element name="parameters" type="apex:multiProcedureParametersType"/>
        <xs:element name="procedure" type="apex:procedureType" minOccurs="1" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>All child procedures MUST have an ID</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:multiProcedureParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#multiProcedureParametersType_order
Used by
Model
Children order
Source
 
<xs:complexType name="multiProcedureParametersType">
  <xs:sequence>
    <xs:element name="order">
      <xs:annotation>
        <xs:documentation>Order of interleaving the child procedures.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="random"/>
          <xs:enumeration value="sequential"/>
          <xs:enumeration value="onebyone">
            <xs:annotation>
              <xs:documentation>Present the procedures one by one: only start the next procedure if the previous one is finished</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:pluginProcedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
TODO
Diagram
Diagram procedure-document.tmp#procedureType_id procedure-document.tmp#procedureType procedure-document.tmp#pluginProcedure_parameters procedure-document.tmp#pluginProcedure_trials
Type extension of apex:procedureType
Type hierarchy
Model
Children parameters, trials
Attributes
QName Type Use Annotation
id xs:ID optional 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Source
 
<xs:complexType name="pluginProcedure">
  <xs:annotation>
    <xs:documentation>TODO</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:procedureType">
      <xs:sequence>
        <xs:element name="parameters" type="apex:pluginProcedureParametersType"/>
        <xs:element name="trials" type="apex:trialsType"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:pluginProcedureParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram procedure-document.tmp#procedureParametersType_presentations procedure-document.tmp#procedureParametersType_skip procedure-document.tmp#procedureParametersType_order procedure-document.tmp#procedureParametersType_defaultstandard procedure-document.tmp#procedureParametersType_uniquestandard procedure-document.tmp#procedureParametersType_intervals procedure-document.tmp#procedureParametersType_corrector procedure-document.tmp#procedureParametersType_pause_between_stimuli procedure-document.tmp#procedureParametersType_time_before_first_trial procedure-document.tmp#procedureParametersType_input_during_stimulus procedure-document.tmp#procedureParametersType procedure-document.tmp#pluginProcedureParametersType_script procedure-document.tmp#pluginProcedureParametersType_debugger procedure-document.tmp#pluginProcedureParametersType_adjust_parameter procedure-document.tmp#pluginProcedureParametersType_parameter
Type extension of apex:procedureParametersType
Type hierarchy
Used by
Model
Children adjust_parameter, corrector, debugger, defaultstandard, input_during_stimulus, intervals, order, parameter, pause_between_stimuli, presentations, script, skip, time_before_first_trial, uniquestandard
Source
 
<xs:complexType name="pluginProcedureParametersType">
  <xs:complexContent>
    <xs:extension base="apex:procedureParametersType">
      <xs:sequence>
        <xs:element name="script" minOccurs="1">
          <xs:annotation>
            <xs:documentation>Name of the script to be used as plugin procedure TODO</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="debugger" minOccurs="0" type="xs:boolean">
          <xs:annotation>
            <xs:documentation>If true, a JavaScript debugger will be shown upon errors, or when the "debugger" statement is encountered in the script</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="adjust_parameter" type="xs:IDREF" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Parameter to be modified by the procedure</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:string">
                <xs:attribute name="name" type="xs:Name" use="required"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:variableParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Parameters defined in this section will be set before the stimulus is
played
Diagram
Diagram procedure-document.tmp#variableParametersType_parameter
Model
Children parameter
Source
 
<xs:complexType name="variableParametersType">
  <xs:annotation>
    <xs:documentation>Parameters defined in this section will be set before the stimulus is played</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="parameter" type="apex:hasIdParameterType" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:hasIdParameterType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Parameter with obligated ID
Diagram
Diagram procedure-document.tmp#parameterType_type procedure-document.tmp#parameterType procedure-document.tmp#hasIdParameterType_id
Type extension of apex:parameterType
Type hierarchy
Used by
Attributes
QName Type Use
id xs:ID required
type xs:string required
Source
 
<xs:complexType name="hasIdParameterType">
  <xs:annotation>
    <xs:documentation>Parameter with obligated ID</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="apex:parameterType">
      <xs:attribute name="id" type="xs:ID" use="required"/>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:parameterType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
base type for all kinds of parameters
Diagram
Diagram procedure-document.tmp#parameterType_type
Type extension of xs:string
Used by
Attributes
QName Type Use
type xs:string required
Source
 
<xs:complexType name="parameterType">
  <xs:annotation>
    <xs:documentation>base type for all kinds of parameters</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="xs:string">
      <xs:attribute name="type" type="xs:string" use="required"/>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:fixedParametersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Fixed parameters are properties of a stimulus
Diagram
Diagram procedure-document.tmp#fixedParametersType_parameter
Model
Children parameter
Source
 
<xs:complexType name="fixedParametersType">
  <xs:annotation>
    <xs:documentation>Fixed parameters are properties of a stimulus</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="parameter" type="apex:maybeIdParameterType" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:maybeIdParameterType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Parameter with optional ID
Diagram
Diagram procedure-document.tmp#maybeIdParameterType_type procedure-document.tmp#maybeIdParameterType_id
Type extension of xs:string
Used by
Attributes
QName Type Use
id xs:ID optional
type xs:string required
Source
 
<xs:complexType name="maybeIdParameterType">
  <xs:annotation>
    <xs:documentation>Parameter with optional ID</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="xs:string">
      <xs:attribute name="type" type="xs:string" use="required"/>
      <xs:attribute name="id" type="xs:ID" use="optional"/>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:genericParameterType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Parameter with parameter name, value, and optional
ID
Diagram
Diagram procedure-document.tmp#genericParameterType_name procedure-document.tmp#genericParameterType_value procedure-document.tmp#genericParameterType_id
Type extension of xs:string
Attributes
QName Type Use
id xs:ID optional
name xs:string required
value xs:string required
Source
 
<xs:complexType name="genericParameterType">
  <xs:annotation>
    <xs:documentation>Parameter with parameter name, value, and optional ID</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="xs:string">
      <xs:attribute name="name" type="xs:string" use="required"/>
      <xs:attribute name="value" type="xs:string" use="required"/>
      <xs:attribute name="id" type="xs:ID" use="optional"/>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:isequal
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Corrector that checks whether the inputs are exactly equal. Useful for
checking buttongroups or exact string matching.
Diagram
Diagram procedure-document.tmp#correctorType
Type extension of apex:correctorType
Type hierarchy
Model
Source
 
<xs:complexType name="isequal">
  <xs:annotation>
    <xs:documentation>Corrector that checks whether the inputs are exactly equal. Useful for checking buttongroups or exact string matching.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:correctorType"/>
  </xs:complexContent>
</xs:complexType>
[ top ]
Attribute apex:procedureType / @id
Namespace No namespace
Annotations
 
The ID is optional, except for child procedures of a
multiprocedure. IDs are reported in the results file.
Type xs:ID
Properties
use optional
Used by
Complex Type apex:procedureType
Source
 
<xs:attribute name="id" type="xs:ID" use="optional">
  <xs:annotation>
    <xs:documentation>The ID is optional, except for child procedures of a multiprocedure. IDs are reported in the results file.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:procedureParametersType / intervals / interval / @number
Namespace No namespace
Annotations
 
Time slot of the
stimulus
Type xs:positiveInteger
Properties
use required
Used by
Source
 
<xs:attribute name="number" type="xs:positiveInteger" use="required">
  <xs:annotation>
    <xs:documentation>Time slot of the stimulus</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:procedureParametersType / intervals / interval / @element
Namespace No namespace
Annotations
 
Name of the screen element
corresponding to the time
slot
Type xs:string
Properties
use required
Used by
Source
 
<xs:attribute name="element" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>Name of the screen element corresponding to the time slot</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:procedureParametersType / intervals / @count
Namespace No namespace
Annotations
 
Number of intervals
Type apex:intervalsCountType
Properties
use required
Facets
minInclusive 2
Used by
Source
 
<xs:attribute name="count" type="apex:intervalsCountType" use="required">
  <xs:annotation>
    <xs:documentation>Number of intervals</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:procedureParametersType / intervals / @select
Namespace No namespace
Annotations
 
If select is defined, the stimulus will only
be presented in the intervals enumerated in the select
attribute. e.g.: if select="2,3", the stimulus will never
occur in interval 1, but only in 2 and 3
Type apex:selectChoicesType
Properties
content simple
Facets
pattern \d+(,\d+)*
Used by
Source
 
<xs:attribute name="select" type="apex:selectChoicesType">
  <xs:annotation>
    <xs:documentation>If select is defined, the stimulus will only be presented in the intervals enumerated in the select attribute. e.g.: if select="2,3", the stimulus will never occur in interval 1, but only in 2 and 3</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:adaptiveProcedureParametersType / stepsizes / stepsize / @begin
Namespace No namespace
Type xs:nonNegativeInteger
Properties
use required
Used by
Source
 
<xs:attribute name="begin" type="xs:nonNegativeInteger" use="required"/>
[ top ]
Attribute apex:adaptiveProcedureParametersType / stepsizes / stepsize / @size
Namespace No namespace
Type xs:double
Properties
use required
Used by
Source
 
<xs:attribute name="size" type="xs:double" use="required"/>
[ top ]
Attribute apex:adaptiveProcedureParametersType / stepsizes / stepsize / @direction
Namespace No namespace
Annotations
 
If this attribute is specified, this stepsize will only be used then adapting in the up/down direction.
When specifying direction for a certain begin value, it needs to be specified for both up and down.
Type apex:direction
Properties
use optional
Facets
enumeration down
enumeration up
Used by
Source
 
<xs:attribute name="direction" type="apex:direction" use="optional">
  <xs:annotation>
    <xs:documentation>If this attribute is specified, this stepsize will only be used then adapting in the up/down direction. When specifying direction for a certain begin value, it needs to be specified for both up and down.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:screenRefType / @id
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Complex Type apex:screenRefType
Source
 
<xs:attribute name="id" type="xs:Name" use="required">
</xs:attribute>
[ top ]
Attribute apex:stimulusRefType / @id
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Complex Type apex:stimulusRefType
Source
 
<xs:attribute name="id" type="xs:Name" use="required">
</xs:attribute>
[ top ]
Attribute apex:trialType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:trialType
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:xmlGeneratingPluginType / script / @source
Namespace No namespace
Type restriction of xs:string
Properties
use required
Facets
enumeration inline
enumeration file
Used by
Source
 
<xs:attribute name="source" use="required">
  <xs:simpleType>
    <xs:annotation>
      <xs:documentation>If inline, the ECMAScript function must be defined inside this element, if file, the filename must be given</xs:documentation>
    </xs:annotation>
    <xs:restriction base="xs:string">
      <xs:enumeration value="inline"/>
      <xs:enumeration value="file"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:xmlGeneratingPluginType / parameter / @name
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Source
 
<xs:attribute name="name" type="xs:Name" use="required"/>
[ top ]
Attribute apex:pluginProcedureParametersType / parameter / @name
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Source
 
<xs:attribute name="name" type="xs:Name" use="required"/>
[ top ]
Attribute apex:parameterType / @type
Namespace No namespace
Type xs:string
Properties
use required
Used by
Complex Type apex:parameterType
Source
 
<xs:attribute name="type" type="xs:string" use="required"/>
[ top ]
Attribute apex:hasIdParameterType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:maybeIdParameterType / @type
Namespace No namespace
Type xs:string
Properties
use required
Used by
Source
 
<xs:attribute name="type" type="xs:string" use="required"/>
[ top ]
Attribute apex:maybeIdParameterType / @id
Namespace No namespace
Type xs:ID
Properties
use optional
Used by
Source
 
<xs:attribute name="id" type="xs:ID" use="optional"/>
[ top ]
Attribute apex:genericParameterType / @name
Namespace No namespace
Type xs:string
Properties
use required
Used by
Source
 
<xs:attribute name="name" type="xs:string" use="required"/>
[ top ]
Attribute apex:genericParameterType / @value
Namespace No namespace
Type xs:string
Properties
use required
Used by
Source
 
<xs:attribute name="value" type="xs:string" use="required"/>
[ top ]
Attribute apex:genericParameterType / @id
Namespace No namespace
Type xs:ID
Properties
use optional
Used by
Source
 
<xs:attribute name="id" type="xs:ID" use="optional"/>
[ top ]
XML Schema documentation generated by ® XML Editor.