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

Main Schema
Included Schemas
Elements
Complex Types
Simple Types
Element Groups
Attribute Groups

Resource hierarchy:

Main schema experiment.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Apex experiment file schema. Describes an entire APEX 4
experiment. An experiment consists of a series of trials.
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema datablocks.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema prefix.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 ]
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 screens.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema devices.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema filters.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema parameter.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema connections.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Included schema stimuli.xsd
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Properties
attribute form default unqualified
element form default unqualified
[ top ]
Element apex:apex
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#apex_version experiment.tmp#apex_description experiment.tmp#apex_procedure experiment.tmp#apex_screens experiment.tmp#apex_datablocks experiment.tmp#apex_devices experiment.tmp#apex_filters experiment.tmp#apex_stimuli experiment.tmp#apex_connections experiment.tmp#apex_randomgenerators experiment.tmp#apex_calibration experiment.tmp#apex_results experiment.tmp#apex_interactive experiment.tmp#apex_general
Properties
content complex
Model
Children calibration, connections, datablocks, description, devices, filters, general, interactive, procedure, randomgenerators, results, screens, stimuli
Instance
 
<apex:apex version="" xmlns:apex="http://med.kuleuven.be/exporl/apex/4.1.2/experiment">
  <description>{0,1}</description>
  <procedure id="">{1,1}</procedure>
  <screens>{1,1}</screens>
  <datablocks>{1,1}</datablocks>
  <devices>{1,1}</devices>
  <filters>{0,1}</filters>
  <stimuli>{1,1}</stimuli>
  <connections>{0,1}</connections>
  <randomgenerators>{0,1}</randomgenerators>
  <calibration profile="">{0,1}</calibration>
  <results>{0,1}</results>
  <interactive>{0,1}</interactive>
  <general>{0,1}</general>
</apex:apex>
Attributes
QName Type Use Annotation
version xs:positiveInteger optional 
Apex will only load experiment files with the correct version
attribute. Conversion scripts will be provided to convert to newer
versions.
Source
 
<xs:element name="apex">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="description" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Describes the entire experiment. Is reported in the results file.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="procedure" type="apex:procedureType">
        <xs:annotation>
          <xs:documentation>Describes the procedure to be used. The procedure controls the sequence of trials that will be presented. Real procedures are derived from apex:procedureType.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="screens" type="apex:screensType">
        <xs:annotation>
          <xs:documentation>Defines one or more screens to be used elsewhere. A screen is what is visible on the computer screen at a certain instant of time.</xs:documentation>
        </xs:annotation>
        <xs:key name="screensKey">
          <xs:selector xpath="apex:screen">
          </xs:selector>
          <xs:field xpath="@apex:id">
          </xs:field>
        </xs:key>
      </xs:element>
      <xs:element name="datablocks" type="apex:datablockstype">
        <xs:annotation>
          <xs:documentation>A datablock is the smallest unit of output data used in Apex. Every sound or other stimulus file to be used elsewhere, is to be defined in this section.</xs:documentation>
        </xs:annotation>
        <xs:key name="datablockKey">
          <xs:selector xpath="apex:datablock">
          </xs:selector>
          <xs:field xpath="@apex:id">
          </xs:field>
        </xs:key>
      </xs:element>
      <xs:element name="devices" type="apex:devicesType">
        <xs:annotation>
          <xs:documentation>All output devices to be used are enumerated in this section. Before the experiment can be started, Apex tries to open them. The experiment only starts if all devices can be opened. Devices are started in alphabetical order of their id, except if a master is specified. They are stopped in reverse alphabetical order. Thus if you want them to be started or stopped in a certain order, you can change their IDs.</xs:documentation>
        </xs:annotation>
        <xs:key name="devicesKey">
          <xs:selector xpath="apex:device">
          </xs:selector>
          <xs:field xpath="@apex:id">
          </xs:field>
        </xs:key>
      </xs:element>
      <xs:element name="filters" type="apex:filtersType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Filters can be placed anywhere in the output network. They can be real filters, ie blocks that process data, or generators, ie blocks that generate data without any input data.</xs:documentation>
        </xs:annotation>
        <xs:key name="filterKey">
          <xs:selector xpath="apex:filter">
          </xs:selector>
          <xs:field xpath="@apex:id">
          </xs:field>
        </xs:key>
      </xs:element>
      <xs:element name="stimuli" type="apex:stimuliType">
        <xs:annotation>
          <xs:documentation>A stimulus is the whole of datablocks (for any number of devices) and parameters (fixed and variable) that is presented to the user at a certain instant of time.</xs:documentation>
        </xs:annotation>
        <xs:key name="stimulusKey">
          <xs:selector xpath="apex:stimulus">
          </xs:selector>
          <xs:field xpath="@apex:id">
          </xs:field>
        </xs:key>
      </xs:element>
      <xs:element name="connections" minOccurs="0" type="apex:connectionsType">
        <xs:annotation>
          <xs:documentation>In this section, connections can be made between datablocks, filters and devices. "from" is only possible for datablocks and filters, "to" is only possible for filters that accept input (thus no generators) and devices. Connections can only be made between elements belonging to the same device. If no connections are specified, Apex tries to make a default network by connecting all channels from _ALL_ (== all datablocks) to all channels from the datablocks' device. Default connections are not made when filters are present.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="randomgenerators" minOccurs="0" type="apex:randomgeneratorsType">
        <xs:annotation>
          <xs:documentation>Randomgenerators generate random numbers according to a certain specification and can set any parameter defined elsewhere before stimulus output. All randomgenerators are asked to set their corresponding parameters right before a stimulus is output.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="calibration" minOccurs="0" maxOccurs="1" type="apex:calibrationType">
        <xs:annotation>
          <xs:documentation>In this optional section, parameters for the built in calibration mechanism are defined. Calibration is the process of ensuring a relation between a digital stimulus level (dB) and the actual audio output (dBSPL). Calibration parameters are stored in profiles that are persistent between sessions. Profiles are stored in the apex/config/calibration directory and can be edited by hand if required.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="results" minOccurs="0" type="apex:resultsType">
        <xs:annotation>
          <xs:documentation>Parameters related to the presentation/analysis of the result of this experiment are defined here.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="interactive" minOccurs="0" type="apex:interactiveType">
        <xs:annotation>
          <xs:documentation>For every entry in this section, the value of a certain element in this experiment file will be changed to the value set by the user in a GUI window.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="general" minOccurs="0" type="apex:generalType">
        <xs:annotation>
          <xs:documentation>Some general experiment parameters are defined here.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="version" use="optional" type="xs:positiveInteger">
      <xs:annotation>
        <xs:documentation>Apex will only load experiment files with the correct version attribute. Conversion scripts will be provided to convert to newer versions.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:apex / description
Namespace No namespace
Annotations
 
Describes the entire experiment. Is reported in the
results file.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="description" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Describes the entire experiment. Is reported in the results file.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / procedure
Namespace No namespace
Annotations
 
Describes the procedure to be used. The procedure controls
the sequence of trials that will be presented. Real procedures are
derived from apex:procedureType.
Diagram
Diagram experiment.tmp#procedureType_id experiment.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">
  <xs:annotation>
    <xs:documentation>Describes the procedure to be used. The procedure controls the sequence of trials that will be presented. Real procedures are derived from apex:procedureType.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / screens
Namespace No namespace
Annotations
 
Defines one or more screens to be used elsewhere. A screen
    is what is visible on the computer screen at a certain instant of
time.
Diagram
Diagram experiment.tmp#screensType_prefix experiment.tmp#screensType_general experiment.tmp#screensType_reinforcement experiment.tmp#screensType_style_apex experiment.tmp#screensType_style experiment.tmp#screensType_childmode experiment.tmp#screensType_defaultFont experiment.tmp#screensType_defaultFontsize experiment.tmp#screensType_screen experiment.tmp#screensType_pluginscreens experiment.tmp#screensType
Type apex:screensType
Properties
content complex
Model
Children childmode, defaultFont, defaultFontsize, general, pluginscreens, prefix, reinforcement, screen, style, style_apex
Instance
 
<screens>
  <prefix source="inline">{0,1}</prefix>
  <general>{0,1}</general>
  <reinforcement>{0,1}</reinforcement>
  <style_apex>{0,1}</style_apex>
  <style>{0,1}</style>
  <childmode>{0,1}</childmode>
  <defaultFont>{0,1}</defaultFont>
  <defaultFontsize>{0,1}</defaultFontsize>
  <screen description="" id="">{0,unbounded}</screen>
  <pluginscreens>{0,unbounded}</pluginscreens>
</screens>
Identity constraints
QName Type Refer Selector Field(s)
screensKey key apex:screen @apex:id
Source
 
<xs:element name="screens" type="apex:screensType">
  <xs:annotation>
    <xs:documentation>Defines one or more screens to be used elsewhere. A screen is what is visible on the computer screen at a certain instant of time.</xs:documentation>
  </xs:annotation>
  <xs:key name="screensKey">
    <xs:selector xpath="apex:screen">
    </xs:selector>
    <xs:field xpath="@apex:id">
    </xs:field>
  </xs:key>
</xs:element>
[ top ]
Element apex:screensType / prefix
Namespace No namespace
Annotations
 
Defines a prefix for the filenames of media
files used in the screens below. The prefix is concatenated
in the front of the filenames given below before trying to
open any file.
Diagram
Diagram experiment.tmp#prefixType_source experiment.tmp#prefixType
Type apex:prefixType
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Default Use
source restriction of xs:string inline optional
Source
 
<xs:element name="prefix" type="apex:prefixType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Defines a prefix for the filenames of media files used in the screens below. The prefix is concatenated in the front of the filenames given below before trying to open any file.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / general
Namespace No namespace
Annotations
 
Some general properties of the entire Apex
window are set in this section. They are applied for each
particular screen defined below.
Diagram
Diagram experiment.tmp#screenGeneralType_stopbutton experiment.tmp#screenGeneralType_repeatbutton experiment.tmp#screenGeneralType_statuspicture experiment.tmp#screenGeneralType_showpanel experiment.tmp#screenGeneralType_showmenu experiment.tmp#screenGeneralType_fullscreen experiment.tmp#screenGeneralType_intertrialscreen experiment.tmp#screenGeneralType
Type apex:screenGeneralType
Properties
content complex
minOccurs 0
Model
Children fullscreen, intertrialscreen, repeatbutton, showmenu, showpanel, statuspicture, stopbutton
Instance
 
<general>
  <stopbutton>{0,1}</stopbutton>
  <repeatbutton>{0,1}</repeatbutton>
  <statuspicture>{0,1}</statuspicture>
  <showpanel>{0,1}</showpanel>
  <showmenu>{0,1}</showmenu>
  <fullscreen>{0,1}</fullscreen>
  <intertrialscreen length="">{0,1}</intertrialscreen>
</general>
Source
 
<xs:element name="general" type="apex:screenGeneralType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Some general properties of the entire Apex window are set in this section. They are applied for each particular screen defined below.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / stopbutton
Namespace No namespace
Annotations
 
Show a red panic button that immediately stops all output when
clicked.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="stopbutton" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Show a red panic button that immediately stops all output when clicked.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / repeatbutton
Namespace No namespace
Annotations
 
Show a repeat button that will repeat the last stimulus.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="repeatbutton" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Show a repeat button that will repeat the last stimulus.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / statuspicture
Namespace No namespace
Annotations
 
Show a status picture that indicates whether the user should be listening or giving an answer
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="statuspicture" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Show a status picture that indicates whether the user should be listening or giving an answer</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / showpanel
Namespace No namespace
Annotations
 
Show the panel; in case of childmode: a movie if defined
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="showpanel" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Show the panel; in case of childmode: a movie if defined</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / showmenu
Namespace No namespace
Annotations
 
Determined whether the apex main menu (containing File, Calibration, etc.) is shown
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
 
<xs:element name="showmenu" type="xs:boolean" minOccurs="0" default="true">
  <xs:annotation>
    <xs:documentation>Determined whether the apex main menu (containing File, Calibration, etc.) is shown</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / fullscreen
Namespace No namespace
Annotations
 
If true, the main apex window will  be shown full-screen, without window title or taskbar or whatever
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="fullscreen" type="xs:boolean" minOccurs="0" default="false">
  <xs:annotation>
    <xs:documentation>If true, the main apex window will be shown full-screen, without window title or taskbar or whatever</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenGeneralType / intertrialscreen
Namespace No namespace
Annotations
 
A screen to show in between trials (after feedback that is)
Diagram
Diagram experiment.tmp#screenGeneralType_screenGeneralType_intertrialscreen_length
Type extension of xs:IDREF
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
length xs:positiveInteger optional 
The period to show the screen
Source
 
<xs:element name="intertrialscreen" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>A screen to show in between trials (after feedback that is)</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:IDREF">
        <xs:attribute name="length" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>The period to show the screen</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:screensType / reinforcement
Namespace No namespace
Annotations
 
Defines what kind of feedback about the
procedure and correctness of answers is shown to the user.
This is valid for the whole experiment.
Diagram
Diagram experiment.tmp#reinforcementType_progressbar experiment.tmp#reinforcementType_feedback experiment.tmp#reinforcementType_feedback_on experiment.tmp#reinforcementType_feedback_picture_positive experiment.tmp#reinforcementType_feedback_picture_negative experiment.tmp#reinforcementType_showcurrent experiment.tmp#reinforcementType_feedbackplugin experiment.tmp#reinforcementType
Type apex:reinforcementType
Properties
content complex
minOccurs 0
Model
Children feedback, feedback_on, feedback_picture_negative, feedback_picture_positive, feedbackplugin, progressbar, showcurrent
Instance
 
<reinforcement>
  <progressbar>{1,1}</progressbar>
  <feedback length="1000">{1,1}</feedback>
  <feedback_on>{0,1}</feedback_on>
  <feedback_picture_positive>{0,1}</feedback_picture_positive>
  <feedback_picture_negative>{0,1}</feedback_picture_negative>
  <showcurrent>{0,1}</showcurrent>
  <feedbackplugin name="">{0,unbounded}</feedbackplugin>
</reinforcement>
Source
 
<xs:element name="reinforcement" type="apex:reinforcementType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Defines what kind of feedback about the procedure and correctness of answers is shown to the user. This is valid for the whole experiment.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:reinforcementType / progressbar
Namespace No namespace
Annotations
 
Show a progress bar in the right hand panel, indicating the
experiment progress. Not functional for multiprocedure or
trainingprocedure.
Diagram
Diagram
Type xs:boolean
Properties
content simple
Source
 
<xs:element name="progressbar" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>Show a progress bar in the right hand panel, indicating the experiment progress. Not functional for multiprocedure or trainingprocedure.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:reinforcementType / feedback
Namespace No namespace
Annotations
 
Show visual feedback according to the correctness of the last
answer. Feedback is shown using an upward or downward pointing thumb in the
right hand panel.
Diagram
Diagram experiment.tmp#reinforcementType_reinforcementType_feedback_length
Type extension of xs:boolean
Properties
content complex
Attributes
QName Type Default Use Annotation
length xs:nonNegativeInteger 1000 optional 
Length of the feedback in ms. If feedback is false but a length is present, the specified time will be the time between two trials.
Source
 
<xs:element name="feedback">
  <xs:annotation>
    <xs:documentation>Show visual feedback according to the correctness of the last answer. Feedback is shown using an upward or downward pointing thumb in the right hand panel.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:boolean">
        <xs:attribute name="length" type="xs:nonNegativeInteger" default="1000">
          <xs:annotation>
            <xs:documentation>Length of the feedback in ms. If feedback is false but a length is present, the specified time will be the time between two trials.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:reinforcementType / feedback_on
Namespace No namespace
Annotations
 
If feedback is shown, it is shown as a picture in the panel, but a screen element can also be highlighted.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
default correct
Facets
enumeration none 
Do not highlight any screenelement
enumeration correct 
Highlight the correct screenelement
enumeration clicked 
Highlight the clicked screenelement (the subject answer)
Source
 
<xs:element name="feedback_on" minOccurs="0" default="correct">
  <xs:annotation>
    <xs:documentation>If feedback is shown, it is shown as a picture in the panel, but a screen element can also be highlighted.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="none">
        <xs:annotation>
          <xs:documentation>Do not highlight any screenelement</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="correct">
        <xs:annotation>
          <xs:documentation>Highlight the correct screenelement</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="clicked">
        <xs:annotation>
          <xs:documentation>Highlight the clicked screenelement (the subject answer)</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:reinforcementType / feedback_picture_positive
Namespace No namespace
Annotations
 
Picture to be shown in the panel on positive feedback.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="feedback_picture_positive" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Picture to be shown in the panel on positive feedback.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:reinforcementType / feedback_picture_negative
Namespace No namespace
Annotations
 
Picture to be shown in the panel on negateive feedback.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="feedback_picture_negative" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Picture to be shown in the panel on negateive feedback.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:reinforcementType / showcurrent
Namespace No namespace
Annotations
 
Show a border around the screen element corresponding to the
currently playing stimulus.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="showcurrent" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Show a border around the screen element corresponding to the currently playing stimulus.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:reinforcementType / feedbackplugin
Namespace No namespace
Annotations
Diagram
Diagram experiment.tmp#reinforcementType_reinforcementType_feedbackplugin_name experiment.tmp#reinforcementType_reinforcementType_feedbackplugin_parameter
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children parameter
Instance
 
<feedbackplugin name="">
  <parameter name="">{0,unbounded}</parameter>
</feedbackplugin>
Attributes
QName Type Use Annotation
name xs:string required 
Name of the plugin to be loaded
Source
 
<xs:element name="feedbackplugin" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>
    </xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" default="" minOccurs="0" maxOccurs="unbounded">
        <xs:annotation>
          <xs:documentation>Parameter to be passed to the plugin</xs:documentation>
        </xs:annotation>
        <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="name" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>Name of the plugin to be loaded</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:reinforcementType / feedbackplugin / parameter
Namespace No namespace
Annotations
 
Parameter to be passed to the plugin
Diagram
Diagram experiment.tmp#reinforcementType_reinforcementType_feedbackplugin_reinforcementType_reinforcementType_feedbackplugin_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:annotation>
    <xs:documentation>Parameter to be passed to the plugin</xs:documentation>
  </xs:annotation>
  <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:screensType / style_apex
Namespace No namespace
Annotations
 
Style that is to be applied to the whole of apex
Diagram
Diagram experiment.tmp#stylesheetType
Type apex:stylesheetType
Properties
content simple
minOccurs 0
Source
 
<xs:element name="style_apex" type="apex:stylesheetType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Style that is to be applied to the whole of apex</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / style
Namespace No namespace
Annotations
 
Style that is to be applied to all screens
Diagram
Diagram experiment.tmp#stylesheetType
Type apex:stylesheetType
Properties
content simple
minOccurs 0
Source
 
<xs:element name="style" type="apex:stylesheetType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Style that is to be applied to all screens</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / childmode
Namespace No namespace
Annotations
 
Defines the elements used in child mode.
Diagram
Diagram experiment.tmp#childmodeType_intro experiment.tmp#childmodeType_outro experiment.tmp#childmodeType_panel experiment.tmp#childmodeType
Type apex:childmodeType
Properties
content complex
minOccurs 0
Model
Children intro, outro, panel
Instance
 
<childmode>
  <intro length="">{0,1}</intro>
  <outro length="">{0,1}</outro>
  <panel>{0,1}</panel>
</childmode>
Source
 
<xs:element name="childmode" type="apex:childmodeType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Defines the elements used in child mode.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:childmodeType / intro
Namespace No namespace
Annotations
 
The screen to show as intro before the experiment starts
Diagram
Diagram experiment.tmp#childmodeType_childmodeType_intro_length
Type extension of xs:IDREF
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
length xs:nonNegativeInteger optional 
Length of the movie in ms, if not specified, the system will wait for the movie to end and then continue.
Source
 
<xs:element name="intro" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The screen to show as intro before the experiment starts</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:IDREF">
        <xs:attribute name="length" type="xs:nonNegativeInteger">
          <xs:annotation>
            <xs:documentation>Length of the movie in ms, if not specified, the system will wait for the movie to end and then continue.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:childmodeType / outro
Namespace No namespace
Annotations
 
The screen to show as outro after the experiment has finished
Diagram
Diagram experiment.tmp#childmodeType_childmodeType_outro_length
Type extension of xs:IDREF
Properties
content complex
minOccurs 0
maxOccurs 1
Attributes
QName Type Use Annotation
length xs:nonNegativeInteger optional 
Length of the movie in ms
Source
 
<xs:element name="outro" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The screen to show as outro after the experiment has finished</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:IDREF">
        <xs:attribute name="length" type="xs:nonNegativeInteger">
          <xs:annotation>
            <xs:documentation>Length of the movie in ms</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:childmodeType / panel
Namespace No namespace
Annotations
 
The panel reinforcement movie to use
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="panel" type="xs:anyURI" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The panel reinforcement movie to use</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / defaultFont
Namespace No namespace
Annotations
 
Name of the default font to be used for all
elements of every screen. Possible names: any font found by
QFontDialog
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="defaultFont" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Name of the default font to be used for all elements of every screen. Possible names: any font found by QFontDialog</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / defaultFontsize
Namespace No namespace
Annotations
 
Size of the default font to be used for all
elements of every screen. Unit: points as defined by the
system
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="defaultFontsize" type="xs:positiveInteger" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Size of the default font to be used for all elements of every screen. Unit: points as defined by the system</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / screen
Namespace No namespace
Annotations
 
Every single screen defines a screen with a
certain ID to be used elsewhere in the experiment
file.
Diagram
Diagram experiment.tmp#screenType_id experiment.tmp#screenType_description experiment.tmp#screenType_hLayout experiment.tmp#screenType_vLayout experiment.tmp#screenType_gridLayout experiment.tmp#screenType_twoPartLayout experiment.tmp#screenType_arcLayout experiment.tmp#screenType_buttongroup experiment.tmp#screenType_default_answer_element experiment.tmp#screenType
Type apex:screenType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children arcLayout, buttongroup, default_answer_element, gridLayout, hLayout, twoPartLayout, vLayout
Instance
 
<screen description="" id="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <twoPartLayout col="" direction="" id="" ratio="" row="" x="" y="">{0,1}</twoPartLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <buttongroup id="">{0,1}</buttongroup>
  <default_answer_element>{0,1}</default_answer_element>
</screen>
Attributes
QName Type Use Annotation
description xs:string optional 
Description of the screen - for your own reference
id xs:ID required
Source
 
<xs:element name="screen" type="apex:screenType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Every single screen defines a screen with a certain ID to be used elsewhere in the experiment file.</xs:documentation>
  </xs:annotation>
  <!--   As the following does not work, it it implemented per layout
                -->
  <!--xs:unique name="screenIDs">
                    <xs:selector xpath="./*[not(name()='buttongroup')]//*"></xs:selector>
                    <xs:field xpath="@id"></xs:field>
                    </xs:unique-->
</xs:element>
[ top ]
Element apex:screenType / hLayout
Namespace No namespace
Annotations
 
Horizontal layout: places elements next to each
other
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#hScreenLayoutType_width experiment.tmp#gridElementAttributes experiment.tmp#hScreenLayoutType
Type apex:hScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<hLayout col="" id="" row="" width="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</hLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Identity constraints
QName Type Refer Selector Field(s)
screenId_hLayout unique ./* @id
Source
 
<xs:element name="hLayout" type="apex:hScreenLayoutType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Horizontal layout: places elements next to each other</xs:documentation>
  </xs:annotation>
  <xs:unique name="screenId_hLayout">
    <xs:selector xpath="./*"/>
    <xs:field xpath="@id"/>
  </xs:unique>
</xs:element>
[ top ]
Element apex:layoutElementGroup / hLayout
Namespace No namespace
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#hScreenLayoutType_width experiment.tmp#gridElementAttributes experiment.tmp#hScreenLayoutType
Type apex:hScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<hLayout col="" id="" row="" width="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</hLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="hLayout" type="apex:hScreenLayoutType" minOccurs="0"/>
[ top ]
Element apex:screenElementGroup / button
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenButtonType_text experiment.tmp#screenButtonType
Type apex:screenButtonType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, text, width
Instance
 
<button col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <text>{1,1}</text>
</button>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="button" type="apex:screenButtonType" minOccurs="0"/>
[ top ]
Element apex:screenElementType / style
Namespace No namespace
Diagram
Diagram experiment.tmp#stylesheetType
Type apex:stylesheetType
Properties
content simple
minOccurs 0
Source
 
<xs:element name="style" type="apex:stylesheetType" minOccurs="0"/>
[ top ]
Element apex:screenElementType / width
Namespace No namespace
Annotations
 
TODO: units?
Diagram
Diagram
Type xs:nonNegativeInteger
Properties
content simple
minOccurs 0
Source
 
<xs:element name="width" type="xs:nonNegativeInteger" minOccurs="0">
  <xs:annotation>
    <xs:documentation>TODO: units?</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementType / height
Namespace No namespace
Diagram
Diagram
Type xs:nonNegativeInteger
Properties
content simple
minOccurs 0
Source
 
<xs:element name="height" type="xs:nonNegativeInteger" minOccurs="0"/>
[ top ]
Element apex:screenElementType / shortcut
Namespace No namespace
Diagram
Diagram experiment.tmp#shortcutBaseType experiment.tmp#shortcutType_action experiment.tmp#shortcutType_modifier experiment.tmp#shortcutType_hex experiment.tmp#shortcutType
Type apex:shortcutType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Default Use Annotation
action restriction of xs:string click optional
hex xs:boolean optional 
If true, parses the shortcut as a hexadecimal number. See the
Key enum in qtnamespace.h for known values
modifier restriction of xs:string optional 
Dead key to be used together with the
shortcut
Source
 
<xs:element name="shortcut" type="apex:shortcutType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:screenElementType / font
Namespace No namespace
Annotations
 
TODO: how is the font specified?
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="font" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>TODO: how is the font specified?</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementType / fontsize
Namespace No namespace
Annotations
 
Text font size, in points as defined by the system
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="fontsize" type="xs:positiveInteger" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Text font size, in points as defined by the system</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementType / bgcolor
Namespace No namespace
Diagram
Diagram experiment.tmp#colorType
Type apex:colorType
Properties
content simple
minOccurs 0
Source
 
<xs:element name="bgcolor" type="apex:colorType" minOccurs="0"/>
[ top ]
Element apex:screenElementType / fgcolor
Namespace No namespace
Diagram
Diagram experiment.tmp#colorType
Type apex:colorType
Properties
content simple
minOccurs 0
Source
 
<xs:element name="fgcolor" type="apex:colorType" minOccurs="0"/>
[ top ]
Element apex:screenElementType / floating
Namespace No namespace
Annotations
 
Put the element in it's own window instead of embedding it in the current layout
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="floating" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Put the element in it's own window instead of embedding it in the current layout</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementType / disabled
Namespace No namespace
Annotations
 
If set to true, the element will always be disabled (can be used to "guide the eye")
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="disabled" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If set to true, the element will always be disabled (can be used to "guide the eye")</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenButtonType / text
Namespace No namespace
Annotations
 
Text to be printed on the button
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="text" type="xs:string">
  <xs:annotation>
    <xs:documentation>Text to be printed on the button</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / label
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenLabelType_text experiment.tmp#screenLabelType
Type apex:screenLabelType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, text, width
Instance
 
<label col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <text>{1,1}</text>
</label>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="label" type="apex:screenLabelType" minOccurs="0"/>
[ top ]
Element apex:screenLabelType / text
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="text" type="xs:string"/>
[ top ]
Element apex:screenElementGroup / answerlabel
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenAnswerLabelType
Type apex:screenAnswerLabelType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, width
Instance
 
<answerlabel col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
</answerlabel>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="answerlabel" type="apex:screenAnswerLabelType" minOccurs="0"/>
[ top ]
Element apex:screenElementGroup / parameterlabel
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenParameterLabelType_parameter experiment.tmp#screenParameterLabelType
Type apex:screenParameterLabelType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, parameter, shortcut, style, width
Instance
 
<parameterlabel col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <parameter expression="" name="">{1,1}</parameter>
</parameterlabel>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="parameterlabel" type="apex:screenParameterLabelType" minOccurs="0"/>
[ top ]
Element apex:screenParameterLabelType / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#showparameterType_name experiment.tmp#showparameterType_expression experiment.tmp#showparameterType
Type apex:showparameterType
Properties
content complex
minOccurs 1
maxOccurs 1
Attributes
QName Type Use Annotation
expression apex:mathexpression optional 
Expression to be evaluated. Expressions must
be in the format a*x+b, where x is the parameter value and a
and b are floats
name optional 
Parameter name to show in the
list
Source
 
<xs:element name="parameter" type="apex:showparameterType" minOccurs="1" maxOccurs="1"/>
[ top ]
Element apex:screenElementGroup / textEdit
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenTextEditType_text experiment.tmp#screenTextEditType_inputmask experiment.tmp#screenTextEditType
Type apex:screenTextEditType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, inputmask, shortcut, style, text, width
Instance
 
<textEdit col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <text>{0,1}</text>
  <inputmask>{0,1}</inputmask>
</textEdit>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="textEdit" type="apex:screenTextEditType" minOccurs="0"/>
[ top ]
Element apex:screenTextEditType / text
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="text" type="xs:string" minOccurs="0" maxOccurs="1"/>
[ top ]
Element apex:screenTextEditType / inputmask
Namespace No namespace
Annotations
 
Input mask to restrict what can be typed in the textbox.
Defined in the Qt documentation. If inputmask=="numbers", only numeric input
will be allowed. If inputmask starts with a / (slash), the remainder will be 
used as a regular expression for QRegExpValidator.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="inputmask" type="xs:string" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Input mask to restrict what can be typed in the textbox. Defined in the Qt documentation. If inputmask=="numbers", only numeric input will be allowed. If inputmask starts with a / (slash), the remainder will be used as a regular expression for QRegExpValidator.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / picture
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenPictureType_file experiment.tmp#screenPictureType_feedback experiment.tmp#screenPictureType
Type apex:screenPictureType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, feedback, fgcolor, file, floating, font, fontsize, height, shortcut, style, width
Instance
 
<picture col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <file id="">{1,1}</file>
  <feedback>{0,1}</feedback>
</picture>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="picture" type="apex:screenPictureType" minOccurs="0"/>
[ top ]
Element apex:screenPictureType / file
Namespace No namespace
Annotations
 
Filename of the picture. The format can be any of: PNG, BMP,
XBM, XPM, JPEG, MNG, GIF, PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or
P6). If path is relative, it will be prefixed with the prefix given
above.
Diagram
Diagram experiment.tmp#screenPictureType_screenPictureType_file_id
Type extension of xs:string
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="file">
  <xs:annotation>
    <xs:documentation>Filename of the picture. The format can be any of: PNG, BMP, XBM, XPM, JPEG, MNG, GIF, PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6). If path is relative, it will be prefixed with the prefix given above.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="id" type="xs:ID"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:screenPictureType / feedback
Namespace No namespace
Annotations
 
If used, overrides the normal feedback (using coloured borders) by drawing a different picture on screen.
Diagram
Diagram experiment.tmp#feedbackPathsType_highlight experiment.tmp#feedbackPathsType_positive experiment.tmp#feedbackPathsType_negative experiment.tmp#feedbackPathsType_disabled experiment.tmp#feedbackPathsType
Type apex:feedbackPathsType
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children disabled, highlight, negative, positive
Instance
 
<feedback>
  <highlight>{0,1}</highlight>
  <positive>{0,1}</positive>
  <negative>{0,1}</negative>
  <disabled>{0,1}</disabled>
</feedback>
Source
 
<xs:element name="feedback" type="apex:feedbackPathsType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>If used, overrides the normal feedback (using coloured borders) by drawing a different picture on screen.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:feedbackPathsType / highlight
Namespace No namespace
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
Source
 
<xs:element name="highlight" type="xs:anyURI" minOccurs="0"/>
[ top ]
Element apex:feedbackPathsType / positive
Namespace No namespace
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
Source
 
<xs:element name="positive" type="xs:anyURI" minOccurs="0"/>
[ top ]
Element apex:feedbackPathsType / negative
Namespace No namespace
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
Source
 
<xs:element name="negative" type="xs:anyURI" minOccurs="0"/>
[ top ]
Element apex:feedbackPathsType / disabled
Namespace No namespace
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
Source
 
<xs:element name="disabled" type="xs:anyURI" minOccurs="0"/>
[ top ]
Element apex:screenElementGroup / flash
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenFlashType_file experiment.tmp#screenFlashType_feedback experiment.tmp#screenFlashType
Type apex:screenFlashType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, feedback, fgcolor, file, floating, font, fontsize, height, shortcut, style, width
Instance
 
<flash col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <file>{1,1}</file>
  <feedback>{0,1}</feedback>
</flash>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="flash" type="apex:screenFlashType" minOccurs="0"/>
[ top ]
Element apex:screenFlashType / file
Namespace No namespace
Annotations
 
Flash movie to be put on the screen.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="file" type="xs:string">
  <xs:annotation>
    <xs:documentation>Flash movie to be put on the screen.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenFlashType / feedback
Namespace No namespace
Annotations
 
If used, overrides the normal feedback (using coloured borders) by putting a different movie on screen.
Diagram
Diagram experiment.tmp#feedbackPathsType_highlight experiment.tmp#feedbackPathsType_positive experiment.tmp#feedbackPathsType_negative experiment.tmp#feedbackPathsType_disabled experiment.tmp#feedbackPathsType
Type apex:feedbackPathsType
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children disabled, highlight, negative, positive
Instance
 
<feedback>
  <highlight>{0,1}</highlight>
  <positive>{0,1}</positive>
  <negative>{0,1}</negative>
  <disabled>{0,1}</disabled>
</feedback>
Source
 
<xs:element name="feedback" type="apex:feedbackPathsType" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>If used, overrides the normal feedback (using coloured borders) by putting a different movie on screen.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / parameterlist
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenParameterlistType_parameter experiment.tmp#screenParameterlistType
Type apex:screenParameterlistType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, parameter, shortcut, style, width
Instance
 
<parameterlist col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <parameter expression="" name="">{1,unbounded}</parameter>
</parameterlist>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="parameterlist" type="apex:screenParameterlistType" minOccurs="0"/>
[ top ]
Element apex:screenParameterlistType / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#showparameterType_name experiment.tmp#showparameterType_expression experiment.tmp#showparameterType
Type apex:showparameterType
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
expression apex:mathexpression optional 
Expression to be evaluated. Expressions must
be in the format a*x+b, where x is the parameter value and a
and b are floats
name optional 
Parameter name to show in the
list
Source
 
<xs:element name="parameter" type="apex:showparameterType" maxOccurs="unbounded"/>
[ top ]
Element apex:screenElementGroup / picturelabel
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenPictureLabelType_file experiment.tmp#screenPictureLabelType_disabledfile experiment.tmp#screenPictureLabelType
Type apex:screenPictureLabelType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, disabledfile, fgcolor, file, floating, font, fontsize, height, shortcut, style, width
Instance
 
<picturelabel col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <file>{1,1}</file>
  <disabledfile>{0,1}</disabledfile>
</picturelabel>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="picturelabel" type="apex:screenPictureLabelType" minOccurs="0"/>
[ top ]
Element apex:screenPictureLabelType / file
Namespace No namespace
Annotations
 
Filename of the picture. The format can be any of: PNG, BMP,
XBM, XPM, JPEG, MNG, GIF, PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or
P6). If path is relative, it will be prefixed with the prefix given
above.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
Source
 
<xs:element name="file" type="xs:anyURI">
  <xs:annotation>
    <xs:documentation>Filename of the picture. The format can be any of: PNG, BMP, XBM, XPM, JPEG, MNG, GIF, PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6). If path is relative, it will be prefixed with the prefix given above.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenPictureLabelType / disabledfile
Namespace No namespace
Annotations
 
Picture to be used if the element is disabled
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="disabledfile" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Picture to be used if the element is disabled</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / spinBox
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenSpinBoxType_value experiment.tmp#screenSpinBoxType_min experiment.tmp#screenSpinBoxType_max experiment.tmp#screenSpinBoxType_step experiment.tmp#screenSpinBoxType_parameter experiment.tmp#screenSpinBoxType_reset experiment.tmp#screenSpinBoxType
Type apex:screenSpinBoxType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, max, min, parameter, reset, shortcut, step, style, value, width
Instance
 
<spinBox col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <value>{0,1}</value>
  <min>{0,1}</min>
  <max>{0,1}</max>
  <step>{0,1}</step>
  <parameter>{0,1}</parameter>
  <reset>{0,1}</reset>
</spinBox>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="spinBox" type="apex:screenSpinBoxType" minOccurs="0"/>
[ top ]
Element apex:screenSpinBoxType / value
Namespace No namespace
Annotations
 
Default value
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="value" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Default value</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSpinBoxType / min
Namespace No namespace
Annotations
 
Minimum value
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="min" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Minimum value</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSpinBoxType / max
Namespace No namespace
Annotations
 
Maximum value
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="max" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximum value</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSpinBoxType / step
Namespace No namespace
Annotations
 
Stepsize
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="step" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Stepsize</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSpinBoxType / parameter
Namespace No namespace
Annotations
 
Parameter to be set to the value of the spinbox. This parameter will be set the NEXT trial.
Diagram
Diagram
Type xs:IDREF
Properties
content simple
minOccurs 0
Source
 
<xs:element name="parameter" type="xs:IDREF" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Parameter to be set to the value of the spinbox. This parameter will be set the NEXT trial.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSpinBoxType / reset
Namespace No namespace
Annotations
 
Reset the value for every new trial
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="reset" type="xs:boolean" default="false" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Reset the value for every new trial</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / checkBox
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenCheckBoxType_text experiment.tmp#screenCheckBoxType_isChecked experiment.tmp#screenCheckBoxType
Type apex:screenCheckBoxType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, isChecked, shortcut, style, text, width
Instance
 
<checkBox col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <text>{1,1}</text>
  <isChecked>{0,1}</isChecked>
</checkBox>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="checkBox" type="apex:screenCheckBoxType" minOccurs="0"/>
[ top ]
Element apex:screenCheckBoxType / text
Namespace No namespace
Annotations
 
Text to be printed right to the checkbox
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="text" type="xs:string">
  <xs:annotation>
    <xs:documentation>Text to be printed right to the checkbox</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenCheckBoxType / isChecked
Namespace No namespace
Annotations
 
Determines whether checkbox is checked by default
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="isChecked" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Determines whether checkbox is checked by default</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / slider
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenSliderType_orientation experiment.tmp#screenSliderType_min experiment.tmp#screenSliderType_max experiment.tmp#screenSliderType_value experiment.tmp#screenSliderType_tickinterval experiment.tmp#screenSliderType_stepsize experiment.tmp#screenSliderType_pagesize experiment.tmp#screenSliderType
Type apex:screenSliderType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, max, min, orientation, pagesize, shortcut, stepsize, style, tickinterval, value, width
Instance
 
<slider col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <orientation>{0,1}</orientation>
  <min>{0,1}</min>
  <max>{0,1}</max>
  <value>{0,1}</value>
  <tickinterval>{0,1}</tickinterval>
  <stepsize>{0,1}</stepsize>
  <pagesize>{0,1}</pagesize>
</slider>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="slider" type="apex:screenSliderType" minOccurs="0"/>
[ top ]
Element apex:screenSliderType / orientation
Namespace No namespace
Annotations
 
Orientation of slider
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration horizontal
enumeration vertical
Source
 
<xs:element name="orientation" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Orientation of slider</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="horizontal"/>
      <xs:enumeration value="vertical"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:screenSliderType / min
Namespace No namespace
Annotations
 
Minimum value of slider
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="min" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Minimum value of slider</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSliderType / max
Namespace No namespace
Annotations
 
Maximum value of slider
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="max" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximum value of slider</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSliderType / value
Namespace No namespace
Annotations
 
Default value of slider
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="value" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Default value of slider</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSliderType / tickinterval
Namespace No namespace
Annotations
 
Interval between slider ticks
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="tickinterval" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Interval between slider ticks</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSliderType / stepsize
Namespace No namespace
Annotations
 
Step size on single arrow key press
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="stepsize" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Step size on single arrow key press</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenSliderType / pagesize
Namespace No namespace
Annotations
 
Step size of pageUp pageDown key press
Diagram
Diagram
Type xs:integer
Properties
content simple
minOccurs 0
Source
 
<xs:element name="pagesize" type="xs:integer" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Step size of pageUp pageDown key press</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / matrix
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenMatrixType_autocontinue experiment.tmp#screenMatrixType_element experiment.tmp#screenMatrixType
Type apex:screenMatrixType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children autocontinue, bgcolor, disabled, element, fgcolor, floating, font, fontsize, height, shortcut, style, width
Instance
 
<matrix col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <autocontinue>{0,1}</autocontinue>
  <element col="" row="">{1,unbounded}</element>
</matrix>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="matrix" type="apex:screenMatrixType" minOccurs="0"/>
[ top ]
Element apex:screenMatrixType / autocontinue
Namespace No namespace
Annotations
 
Automatically end the trial when all columns are completed
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
 
<xs:element name="autocontinue" type="xs:boolean" default="true" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Automatically end the trial when all columns are completed</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenMatrixType / element
Namespace No namespace
Diagram
Diagram experiment.tmp#screenMatrixType_screenMatrixType_element_row experiment.tmp#screenMatrixType_screenMatrixType_element_col experiment.tmp#screenMatrixType_screenMatrixType_element_name experiment.tmp#screenMatrixType_screenMatrixType_element_text
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children name, text
Instance
 
<element col="" row="">
  <name>{1,1}</name>
  <text>{0,1}</text>
</element>
Attributes
QName Type Use Annotation
col xs:positiveInteger required 
Column in the matrix
row xs:positiveInteger required 
Row in the matrix
Source
 
<xs:element name="element" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="name" type="xs:string">
        <xs:annotation>
          <xs:documentation>Name of the element. Will be reported in the results. Will also be used as text if no text is given.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="text" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Text to be shown on the button</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="row" type="xs:positiveInteger" use="required">
      <xs:annotation>
        <xs:documentation>Row in the matrix</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="col" type="xs:positiveInteger" use="required">
      <xs:annotation>
        <xs:documentation>Column in the matrix</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:screenMatrixType / element / name
Namespace No namespace
Annotations
 
Name of the element. Will be reported in the results. Will also be used as text if no text is given.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="name" type="xs:string">
  <xs:annotation>
    <xs:documentation>Name of the element. Will be reported in the results. Will also be used as text if no text is given.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenMatrixType / element / text
Namespace No namespace
Annotations
 
Text to be shown on the button
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="text" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Text to be shown on the button</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / html
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenHtmlType_page experiment.tmp#screenHtmlType
Type apex:screenHtmlType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, page, shortcut, style, width
Instance
 
<html col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
  <page>{1,1}</page>
</html>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="html" type="apex:screenHtmlType" minOccurs="0"/>
[ top ]
Element apex:screenHtmlType / page
Namespace No namespace
Annotations
 
Filename of the HTML document.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
Source
 
<xs:element name="page" type="xs:anyURI">
  <xs:annotation>
    <xs:documentation>Filename of the HTML document.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screenElementGroup / numericKeypad
Namespace No namespace
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenNumericKeypadType
Type apex:screenNumericKeypadType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, width
Instance
 
<numericKeypad col="" id="" row="" x="" y="">
  <style>{0,1}</style>
  <width>{0,1}</width>
  <height>{0,1}</height>
  <shortcut action="click" hex="" modifier="">{0,unbounded}</shortcut>
  <font>{0,1}</font>
  <fontsize>{0,1}</fontsize>
  <bgcolor>{0,1}</bgcolor>
  <fgcolor>{0,1}</fgcolor>
  <floating>{0,1}</floating>
  <disabled>{0,1}</disabled>
</numericKeypad>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="numericKeypad" type="apex:screenNumericKeypadType" minOccurs="0"/>
[ top ]
Element apex:layoutElementGroup / vLayout
Namespace No namespace
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#vScreenLayoutType_height experiment.tmp#gridElementAttributes experiment.tmp#vScreenLayoutType
Type apex:vScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<vLayout col="" height="" id="" row="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</vLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
height xs:int required
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="vLayout" type="apex:vScreenLayoutType" minOccurs="0"/>
[ top ]
Element apex:layoutElementGroup / gridLayout
Namespace No namespace
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#gridScreenLayoutType_width experiment.tmp#gridScreenLayoutType_height experiment.tmp#gridScreenLayoutType_columnstretch experiment.tmp#gridScreenLayoutType_rowstretch experiment.tmp#gridElementAttributes experiment.tmp#gridScreenLayoutType
Type apex:gridScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</gridLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
columnstretch apex:stretchregexp optional 
Stretch factor for the columns: a list of integers separated by comma's. If specified, there should be as much 
integers as columns. The width of the columns will be proportional to the numbers. E.g. if width=2 and columnstretch="1,2", the 
second column will be twice as wide as the first. columnstretch="2,4" would have the same effect.
height xs:int required
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
rowstretch apex:stretchregexp optional 
Stretch factor for the rows: a list of integers separated by comma's. If specified, there should be as much 
integers as rows. The width of the rows will be proportional to the numbers. E.g. if height=3 and rowstretch="1,2,1", the 
second row will be twice as wide as the first and thirs. rowstretch="2,4,2" would have the same effect.
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="gridLayout" type="apex:gridScreenLayoutType" minOccurs="0"/>
[ top ]
Element apex:layoutElementGroup / arcLayout
Namespace No namespace
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#arcScreenLayoutType_width experiment.tmp#gridElementAttributes experiment.tmp#arcScreenLayoutType_type experiment.tmp#arcScreenLayoutType
Type apex:arcScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<arcLayout col="" id="" row="" type="" width="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</arcLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
type restriction of xs:string required 
TODO
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:element name="arcLayout" type="apex:arcScreenLayoutType" minOccurs="0"/>
[ top ]
Element apex:screenType / vLayout
Namespace No namespace
Annotations
 
Vertical layout: places elements above each
other
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#vScreenLayoutType_height experiment.tmp#gridElementAttributes experiment.tmp#vScreenLayoutType
Type apex:vScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<vLayout col="" height="" id="" row="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</vLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
height xs:int required
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Identity constraints
QName Type Refer Selector Field(s)
screenId_vLayout unique ./* @id
Source
 
<xs:element name="vLayout" type="apex:vScreenLayoutType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Vertical layout: places elements above each other</xs:documentation>
  </xs:annotation>
  <xs:unique name="screenId_vLayout">
    <xs:selector xpath="./*"/>
    <xs:field xpath="@id"/>
  </xs:unique>
</xs:element>
[ top ]
Element apex:screenType / gridLayout
Namespace No namespace
Annotations
 
Gridlayout: places elements in an (irregular)
grid.
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#gridScreenLayoutType_width experiment.tmp#gridScreenLayoutType_height experiment.tmp#gridScreenLayoutType_columnstretch experiment.tmp#gridScreenLayoutType_rowstretch experiment.tmp#gridElementAttributes experiment.tmp#gridScreenLayoutType
Type apex:gridScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</gridLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
columnstretch apex:stretchregexp optional 
Stretch factor for the columns: a list of integers separated by comma's. If specified, there should be as much 
integers as columns. The width of the columns will be proportional to the numbers. E.g. if width=2 and columnstretch="1,2", the 
second column will be twice as wide as the first. columnstretch="2,4" would have the same effect.
height xs:int required
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
rowstretch apex:stretchregexp optional 
Stretch factor for the rows: a list of integers separated by comma's. If specified, there should be as much 
integers as rows. The width of the rows will be proportional to the numbers. E.g. if height=3 and rowstretch="1,2,1", the 
second row will be twice as wide as the first and thirs. rowstretch="2,4,2" would have the same effect.
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Identity constraints
QName Type Refer Selector Field(s)
screenId_gridLayout unique ./* @id
Source
 
<xs:element name="gridLayout" type="apex:gridScreenLayoutType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Gridlayout: places elements in an (irregular) grid.</xs:documentation>
  </xs:annotation>
  <xs:unique name="screenId_gridLayout">
    <xs:selector xpath="./*"/>
    <xs:field xpath="@id"/>
  </xs:unique>
</xs:element>
[ top ]
Element apex:screenType / twoPartLayout
Namespace No namespace
Annotations
 
Layout with a small upper part and larger lower part
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#twoPartLayoutType_ratio experiment.tmp#twoPartLayoutType_direction experiment.tmp#gridElementAttributes experiment.tmp#twoPartLayoutType
Type apex:twoPartLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<twoPartLayout col="" direction="" id="" ratio="" row="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</twoPartLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
direction apex:horivertType required
id xs:Name optional
ratio xs:float required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Identity constraints
QName Type Refer Selector Field(s)
screenId_twoPartLayout unique ./* @id
Source
 
<xs:element name="twoPartLayout" type="apex:twoPartLayoutType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Layout with a small upper part and larger lower part</xs:documentation>
  </xs:annotation>
  <xs:unique name="screenId_twoPartLayout">
    <xs:selector xpath="./*"/>
    <xs:field xpath="@id"/>
  </xs:unique>
</xs:element>
[ top ]
Element apex:screenType / arcLayout
Namespace No namespace
Annotations
 
Arc layout: places elements in a semi-circle. Useful for
localization experiments.
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#arcScreenLayoutType_width experiment.tmp#gridElementAttributes experiment.tmp#arcScreenLayoutType_type experiment.tmp#arcScreenLayoutType
Type apex:arcScreenLayoutType
Type hierarchy
Properties
content complex
minOccurs 0
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Instance
 
<arcLayout col="" id="" row="" type="" width="" x="" y="">
  <hLayout col="" id="" row="" width="" x="" y="">{0,1}</hLayout>
  <vLayout col="" height="" id="" row="" x="" y="">{0,1}</vLayout>
  <gridLayout col="" columnstretch="" height="" id="" row="" rowstretch="" width="" x="" y="">{0,1}</gridLayout>
  <arcLayout col="" id="" row="" type="" width="" x="" y="">{0,1}</arcLayout>
  <button col="" id="" row="" x="" y="">{0,1}</button>
  <label col="" id="" row="" x="" y="">{0,1}</label>
  <answerlabel col="" id="" row="" x="" y="">{0,1}</answerlabel>
  <parameterlabel col="" id="" row="" x="" y="">{0,1}</parameterlabel>
  <textEdit col="" id="" row="" x="" y="">{0,1}</textEdit>
  <picture col="" id="" row="" x="" y="">{0,1}</picture>
  <flash col="" id="" row="" x="" y="">{0,1}</flash>
  <parameterlist col="" id="" row="" x="" y="">{0,1}</parameterlist>
  <picturelabel col="" id="" row="" x="" y="">{0,1}</picturelabel>
  <spinBox col="" id="" row="" x="" y="">{0,1}</spinBox>
  <checkBox col="" id="" row="" x="" y="">{0,1}</checkBox>
  <slider col="" id="" row="" x="" y="">{0,1}</slider>
  <matrix col="" id="" row="" x="" y="">{0,1}</matrix>
  <html col="" id="" row="" x="" y="">{0,1}</html>
  <numericKeypad col="" id="" row="" x="" y="">{0,1}</numericKeypad>
</arcLayout>
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
type restriction of xs:string required 
TODO
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Identity constraints
QName Type Refer Selector Field(s)
screenId_arcLayout unique ./* @id
Source
 
<xs:element name="arcLayout" type="apex:arcScreenLayoutType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Arc layout: places elements in a semi-circle. Useful for localization experiments.</xs:documentation>
  </xs:annotation>
  <xs:unique name="screenId_arcLayout">
    <xs:selector xpath="./*"/>
    <xs:field xpath="@id"/>
  </xs:unique>
</xs:element>
[ top ]
Element apex:screenType / buttongroup
Namespace No namespace
Diagram
Diagram experiment.tmp#screenIdAttribute experiment.tmp#buttonGroupType_button experiment.tmp#buttonGroupType
Type apex:buttonGroupType
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children button
Instance
 
<buttongroup id="">
  <button id="">{1,unbounded}</button>
</buttongroup>
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:element name="buttongroup" type="apex:buttonGroupType" minOccurs="0" maxOccurs="1"/>
[ top ]
Element apex:buttonGroupType / button
Namespace No namespace
Diagram
Diagram experiment.tmp#buttonGroupType_buttonGroupType_button_id
Properties
content complex
minOccurs 1
maxOccurs unbounded
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:element name="button" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <!--xs:attribute name="id" type="xs:IDREF" use="required"/-->
    <xs:attribute name="id" type="xs:Name" use="required"/>
    <!-- FIXME -->
  </xs:complexType>
</xs:element>
[ top ]
Element apex:screenType / default_answer_element
Namespace No namespace
Annotations
 
Default element for getting the user input to send to the
corrector.
Diagram
Diagram
Type xs:Name
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="default_answer_element" type="xs:Name" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Default element for getting the user input to send to the corrector.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:screensType / pluginscreens
Namespace No namespace
Diagram
Diagram experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType experiment.tmp#pluginScreenType
Type apex:pluginScreenType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children parameter, script
Instance
 
<pluginscreens>
  <script source="">{0,1}</script>
  <parameter name="">{0,unbounded}</parameter>
</pluginscreens>
Source
 
<xs:element name="pluginscreens" type="apex:pluginScreenType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:xmlGeneratingPluginType / script
Namespace No namespace
Diagram
Diagram experiment.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 experiment.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:apex / datablocks
Namespace No namespace
Annotations
 
A datablock is the smallest unit of output data used in
Apex. Every sound or other stimulus file to be used elsewhere, is to be
defined in this section.
Diagram
Diagram experiment.tmp#datablockstype_prefix experiment.tmp#datablockstype_datablock experiment.tmp#datablockstype_plugindatablocks experiment.tmp#datablockstype
Type apex:datablockstype
Properties
content complex
Model
Children datablock, plugindatablocks, prefix
Instance
 
<datablocks>
  <prefix source="inline">{0,1}</prefix>
  <datablock id="">{0,unbounded}</datablock>
  <plugindatablocks>{0,unbounded}</plugindatablocks>
</datablocks>
Identity constraints
QName Type Refer Selector Field(s)
datablockKey key apex:datablock @apex:id
Source
 
<xs:element name="datablocks" type="apex:datablockstype">
  <xs:annotation>
    <xs:documentation>A datablock is the smallest unit of output data used in Apex. Every sound or other stimulus file to be used elsewhere, is to be defined in this section.</xs:documentation>
  </xs:annotation>
  <xs:key name="datablockKey">
    <xs:selector xpath="apex:datablock">
    </xs:selector>
    <xs:field xpath="@apex:id">
    </xs:field>
  </xs:key>
</xs:element>
[ top ]
Element apex:datablockstype / prefix
Namespace No namespace
Annotations
 
The prefix for every filename used below.
    Only used if a filename is a relative path. This prefix
    is relative to the path of this experiment
file.
Diagram
Diagram experiment.tmp#prefixType_source experiment.tmp#prefixType
Type apex:prefixType
Properties
content complex
minOccurs 0
Attributes
QName Type Default Use
source restriction of xs:string inline optional
Source
 
<xs:element name="prefix" type="apex:prefixType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The prefix for every filename used below. Only used if a filename is a relative path. This prefix is relative to the path of this experiment file.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablockstype / datablock
Namespace No namespace
Diagram
Diagram experiment.tmp#datablockType_id experiment.tmp#datablockType_device experiment.tmp#datablockType_description experiment.tmp#datablockType_file experiment.tmp#datablockType_data experiment.tmp#datablockType_channels experiment.tmp#datablockType_loop experiment.tmp#datablockType
Type apex:datablockType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children channels, data, description, device, file, loop
Instance
 
<datablock id="">
  <device>{0,1}</device>
  <description>{0,1}</description>
  <file>{1,1}</file>
  <data>{1,1}</data>
  <channels>{0,1}</channels>
  <loop>{0,1}</loop>
</datablock>
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:element name="datablock" type="apex:datablockType" maxOccurs="unbounded" minOccurs="0">
</xs:element>
[ top ]
Element apex:datablockType / device
Namespace No namespace
Annotations
 
The device used to play the datablock. If
no device is specified, and there is only one device in
the experiment file, it will be used. Otherwise an error
message will be shown.
Diagram
Diagram
Type extension of xs:IDREF
Properties
content complex
minOccurs 0
Source
 
<xs:element name="device" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The device used to play the datablock. If no device is specified, and there is only one device in the experiment file, it will be used. Otherwise an error message will be shown.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:IDREF">
        <!--xs:attribute name="channel1" type="xs:nonNegativeInteger" default="0" use="optional"/>
                                <xs:attribute name="channel2" type="xs:nonNegativeInteger" default="1" use="optional"/-->
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:datablockType / description
Namespace No namespace
Annotations
 
Text description, for your own
reference
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="description" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Text description, for your own reference</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablockType / file
Namespace No namespace
Annotations
 
Filename of the corresponding
    datafile. If it is a relative path, it will be
    prefixed with the prefix defined
above.
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="file" type="xs:string">
  <xs:annotation>
    <xs:documentation>Filename of the corresponding datafile. If it is a relative path, it will be prefixed with the prefix defined above.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablockType / data
Namespace No namespace
Annotations
 
Direct data. If the data consists of
    XML code, it can be included directly inside this
    tag. Currently only works with L34 CI
stimuli
Diagram
Diagram
Properties
content complex
mixed true
Model
ANY element from ANY namespace
Source
 
<xs:element name="data">
  <xs:annotation>
    <xs:documentation>Direct data. If the data consists of XML code, it can be included directly inside this tag. Currently only works with L34 CI stimuli</xs:documentation>
  </xs:annotation>
  <xs:complexType mixed="true">
    <xs:sequence minOccurs="0">
      <xs:any processContents="skip"/>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:datablockType / channels
Namespace No namespace
Annotations
 
Number of channels: defaults to the number
    of channels in a wav-file or to 1 in all other
cases.
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
Source
 
<xs:element name="channels" type="xs:positiveInteger" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Number of channels: defaults to the number of channels in a wav-file or to 1 in all other cases.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablockType / loop
Namespace No namespace
Annotations
 
Number of times the datablock should be
looped
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="loop" type="xs:positiveInteger" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Number of times the datablock should be looped</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablockstype / plugindatablocks
Namespace No namespace
Diagram
Diagram experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType experiment.tmp#pluginDatablocksType
Type apex:pluginDatablocksType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children parameter, script
Instance
 
<plugindatablocks>
  <script source="">{0,1}</script>
  <parameter name="">{0,unbounded}</parameter>
</plugindatablocks>
Source
 
<xs:element name="plugindatablocks" type="apex:pluginDatablocksType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:apex / devices
Namespace No namespace
Annotations
 
All output devices to be used are enumerated in this
    section. Before the experiment can be started, Apex tries to open them.
    The experiment only starts if all devices can be
opened.
Devices are started in alphabetical order of their id, except if a
    master is specified. They are 
    stopped in reverse alphabetical order. Thus if you want them 
    to be started or stopped in a certain order, you can change their
    IDs.
Diagram
Diagram experiment.tmp#devicesType_master experiment.tmp#devicesType_device experiment.tmp#devicesType
Type apex:devicesType
Properties
content complex
Model
Children device, master
Instance
 
<devices>
  <master>{0,1}</master>
  <device id="">{0,unbounded}</device>
</devices>
Identity constraints
QName Type Refer Selector Field(s)
devicesKey key apex:device @apex:id
Source
 
<xs:element name="devices" type="apex:devicesType">
  <xs:annotation>
    <xs:documentation>All output devices to be used are enumerated in this section. Before the experiment can be started, Apex tries to open them. The experiment only starts if all devices can be opened. Devices are started in alphabetical order of their id, except if a master is specified. They are stopped in reverse alphabetical order. Thus if you want them to be started or stopped in a certain order, you can change their IDs.</xs:documentation>
  </xs:annotation>
  <xs:key name="devicesKey">
    <xs:selector xpath="apex:device">
    </xs:selector>
    <xs:field xpath="@apex:id">
    </xs:field>
  </xs:key>
</xs:element>
[ top ]
Element apex:devicesType / master
Namespace No namespace
Annotations
 
The master device is that last one to be
started after all stimuli are loaded for all devices. This
feature can be used when using triggers to synchronize
devices.
Diagram
Diagram
Type xs:IDREF
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="master" type="xs:IDREF" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>The master device is that last one to be started after all stimuli are loaded for all devices. This feature can be used when using triggers to synchronize devices.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:devicesType / device
Namespace No namespace
Annotations
 
All real devices derive from this
base.
Diagram
Diagram experiment.tmp#deviceType_id experiment.tmp#deviceType
Type apex:deviceType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:element name="device" type="apex:deviceType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>All real devices derive from this base.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / filters
Namespace No namespace
Annotations
 
Filters can be placed anywhere in the output network. They
can be real filters, ie blocks that process data, or generators, ie
blocks that generate data without any input data.
Diagram
Diagram experiment.tmp#filtersType_filter experiment.tmp#filtersType
Type apex:filtersType
Properties
content complex
minOccurs 0
Model
Children filter
Instance
 
<filters>
  <filter id="">{0,unbounded}</filter>
</filters>
Identity constraints
QName Type Refer Selector Field(s)
filterKey key apex:filter @apex:id
Source
 
<xs:element name="filters" type="apex:filtersType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Filters can be placed anywhere in the output network. They can be real filters, ie blocks that process data, or generators, ie blocks that generate data without any input data.</xs:documentation>
  </xs:annotation>
  <xs:key name="filterKey">
    <xs:selector xpath="apex:filter">
    </xs:selector>
    <xs:field xpath="@apex:id">
    </xs:field>
  </xs:key>
</xs:element>
[ top ]
Element apex:filtersType / filter
Namespace No namespace
Annotations
 
Every filter/generator derives from this base
type. All filters to be used are defined
here.
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType
Type apex:filterType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children channels, continuous, device
Instance
 
<filter id="">
  <device>{1,1}</device>
  <channels>{1,1}</channels>
  <continuous>{0,1}</continuous>
</filter>
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:element name="filter" minOccurs="0" maxOccurs="unbounded" type="apex:filterType">
  <xs:annotation>
    <xs:documentation>Every filter/generator derives from this base type. All filters to be used are defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:filterType / device
Namespace No namespace
Annotations
 
ID of the device to which this filter belongs. The mode of the
filter (online or offline) is determined by the device.
Diagram
Diagram
Type xs:IDREF
Properties
content simple
Source
 
<xs:element name="device" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>ID of the device to which this filter belongs. The mode of the filter (online or offline) is determined by the device.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:filterType / channels
Namespace No namespace
Annotations
 
Number of channels
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
Source
 
<xs:element name="channels" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Number of channels</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:filterType / continuous
Namespace No namespace
Annotations
 
If continuous==true, the filter/generator keeps on running
between trials (ie while the user is entering input). Only makes sense for
generators.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="continuous" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If continuous==true, the filter/generator keeps on running between trials (ie while the user is entering input). Only makes sense for generators.</xs:documentation>
    <!-- FIXME: move to generator -->
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / stimuli
Namespace No namespace
Annotations
 
A stimulus is the whole of datablocks (for any number of
devices) and parameters (fixed and variable) that is presented to the
user at a certain instant of time.
Diagram
Diagram experiment.tmp#stimuliType_fixed_parameters experiment.tmp#stimuliType_stimulus experiment.tmp#stimuliType_pluginstimuli experiment.tmp#stimuliType
Type apex:stimuliType
Properties
content complex
Model
Children fixed_parameters, pluginstimuli, stimulus
Instance
 
<stimuli>
  <fixed_parameters>{0,1}</fixed_parameters>
  <stimulus id="">{0,unbounded}</stimulus>
  <pluginstimuli>{0,unbounded}</pluginstimuli>
</stimuli>
Identity constraints
QName Type Refer Selector Field(s)
stimulusKey key apex:stimulus @apex:id
Source
 
<xs:element name="stimuli" type="apex:stimuliType">
  <xs:annotation>
    <xs:documentation>A stimulus is the whole of datablocks (for any number of devices) and parameters (fixed and variable) that is presented to the user at a certain instant of time.</xs:documentation>
  </xs:annotation>
  <xs:key name="stimulusKey">
    <xs:selector xpath="apex:stimulus">
    </xs:selector>
    <xs:field xpath="@apex:id">
    </xs:field>
  </xs:key>
</xs:element>
[ top ]
Element apex:stimuliType / fixed_parameters
Namespace No namespace
Annotations
 
Fixed parameters describe fixed properties of
every stimulus. They can be used by procedures to select a
certain stimulus, they can be presented on the screen or can
be used for the users own reference. They have no influence
whatever on the actual sound/stimulation that is sent to the
device when a particular stimulus is to be output. Every
fixed stimulus that is used in any stimulus should be
defined here. All fixed parameters defined here, should be
present in all stimuli.
Diagram
Diagram experiment.tmp#stimuliType_stimuliType_fixed_parameters_parameter
Properties
content complex
minOccurs 0
Model
Children parameter
Instance
 
<fixed_parameters>
  <parameter id="" useforresults="false">{0,unbounded}</parameter>
</fixed_parameters>
Source
 
<xs:element name="fixed_parameters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Fixed parameters describe fixed properties of every stimulus. They can be used by procedures to select a certain stimulus, they can be presented on the screen or can be used for the users own reference. They have no influence whatever on the actual sound/stimulation that is sent to the device when a particular stimulus is to be output. Every fixed stimulus that is used in any stimulus should be defined here. All fixed parameters defined here, should be present in all stimuli.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
        <xs:complexType>
          <xs:attribute name="id" type="xs:ID" use="required"/>
          <xs:attribute name="useforresults" type="xs:boolean" use="optional" default="false"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:stimuliType / fixed_parameters / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#stimuliType_stimuliType_fixed_parameters_stimuliType_stimuliType_fixed_parameters_parameter_id experiment.tmp#stimuliType_stimuliType_fixed_parameters_stimuliType_stimuliType_fixed_parameters_parameter_useforresults
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Default Use
id xs:ID required
useforresults xs:boolean false optional
Source
 
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:attribute name="id" type="xs:ID" use="required"/>
    <xs:attribute name="useforresults" type="xs:boolean" use="optional" default="false"/>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:stimuliType / stimulus
Namespace No namespace
Diagram
Diagram experiment.tmp#stimulusType_id experiment.tmp#stimulusType_description experiment.tmp#stimulusType_datablocks experiment.tmp#stimulusType_variableParameters experiment.tmp#stimulusType_fixedParameters experiment.tmp#stimulusType
Type apex:stimulusType
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children datablocks, description, fixedParameters, variableParameters
Instance
 
<stimulus id="">
  <description>{0,1}</description>
  <datablocks>{1,1}</datablocks>
  <variableParameters>{0,1}</variableParameters>
  <fixedParameters>{0,1}</fixedParameters>
</stimulus>
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:element name="stimulus" type="apex:stimulusType" maxOccurs="unbounded" minOccurs="0"/>
[ top ]
Element apex:stimulusType / description
Namespace No namespace
Annotations
 
Text description, for your own reference
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="description" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Text description, for your own reference</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:stimulusType / datablocks
Namespace No namespace
Annotations
 
Combination of datablocks to be output
Diagram
Diagram experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_datablock experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_sequential experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_simultaneous experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType
Type apex:datablocksType
Properties
content complex
Model
Children datablock, sequential, simultaneous
Instance
 
<datablocks>
  <datablock id="">{1,1}</datablock>
  <sequential>{1,1}</sequential>
  <simultaneous>{1,1}</simultaneous>
</datablocks>
Source
 
<xs:element name="datablocks" type="apex:datablocksType">
  <xs:annotation>
    <xs:documentation>Combination of datablocks to be output</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablocksType / datablock
Namespace No namespace
Diagram
Diagram experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_datablock_id
Properties
content complex
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:element name="datablock">
  <xs:complexType>
    <xs:attribute name="id" type="xs:Name" use="required">
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:datablocksType / sequential
Namespace No namespace
Annotations
 
Present all child datablocks or child combinations of
datablocks sequentially. The result is guaranteed gap-less when using a
single device for all children.
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous experiment.tmp#datablockGroup experiment.tmp#datablocksSequentialType
Type apex:datablocksSequentialType
Properties
content complex
Model
(datablock{0,1} | sequential{0,1} | simultaneous{0,1})
Children datablock, sequential, simultaneous
Instance
 
<sequential>
  <datablock id="">{0,1}</datablock>
  <sequential>{0,1}</sequential>
  <simultaneous>{0,1}</simultaneous>
</sequential>
Source
 
<xs:element name="sequential" type="apex:datablocksSequentialType">
  <xs:annotation>
    <xs:documentation>Present all child datablocks or child combinations of datablocks sequentially. The result is guaranteed gap-less when using a single device for all children.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:datablockGroup / datablock
Namespace No namespace
Diagram
Diagram experiment.tmp#datablockRefType_id experiment.tmp#datablockRefType
Type apex:datablockRefType
Properties
content complex
minOccurs 0
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:element name="datablock" type="apex:datablockRefType" minOccurs="0"/>
[ top ]
Element apex:datablockGroup / sequential
Namespace No namespace
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous experiment.tmp#datablockGroup experiment.tmp#datablocksSequentialType
Type apex:datablocksSequentialType
Properties
content complex
minOccurs 0
Model
Children datablock, sequential, simultaneous
Instance
 
<sequential>
  <datablock id="">{0,1}</datablock>
  <sequential>{0,1}</sequential>
  <simultaneous>{0,1}</simultaneous>
</sequential>
Source
 
<xs:element name="sequential" type="apex:datablocksSequentialType" minOccurs="0"/>
[ top ]
Element apex:datablockGroup / simultaneous
Namespace No namespace
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous experiment.tmp#datablockGroup experiment.tmp#datablocksSimultaneouslType
Type apex:datablocksSimultaneouslType
Properties
content complex
minOccurs 0
Model
Children datablock, sequential, simultaneous
Instance
 
<simultaneous>
  <datablock id="">{0,1}</datablock>
  <sequential>{0,1}</sequential>
  <simultaneous>{0,1}</simultaneous>
</simultaneous>
Source
 
<xs:element name="simultaneous" type="apex:datablocksSimultaneouslType" minOccurs="0"/>
[ top ]
Element apex:datablocksType / simultaneous
Namespace No namespace
Annotations
 
Present all child datablocks or child combinations of
datablocks simultaneously. The total length of this block is the length of
the longest child block. Zero's or null stimulation will be added to shorter
children if necessary (this is not guaranteed!).
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous experiment.tmp#datablockGroup experiment.tmp#datablocksSimultaneouslType
Type apex:datablocksSimultaneouslType
Properties
content complex
Model
(datablock{0,1} | sequential{0,1} | simultaneous{0,1})
Children datablock, sequential, simultaneous
Instance
 
<simultaneous>
  <datablock id="">{0,1}</datablock>
  <sequential>{0,1}</sequential>
  <simultaneous>{0,1}</simultaneous>
</simultaneous>
Source
 
<xs:element name="simultaneous" type="apex:datablocksSimultaneouslType">
  <xs:annotation>
    <xs:documentation>Present all child datablocks or child combinations of datablocks simultaneously. The total length of this block is the length of the longest child block. Zero's or null stimulation will be added to shorter children if necessary (this is not guaranteed!).</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:stimulusType / variableParameters
Namespace No namespace
Annotations
 
These parameters will be set just before the stimulus is
output
Diagram
Diagram experiment.tmp#stimulusType_stimulusType_variableParameters_parameter
Properties
content complex
minOccurs 0
Model
Children parameter
Instance
 
<variableParameters>
  <parameter id="">{0,unbounded}</parameter>
</variableParameters>
Source
 
<xs:element name="variableParameters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>These parameters will be set just before the stimulus is output</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="id" type="xs:IDREF" use="required">
              </xs:attribute>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:stimulusType / variableParameters / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#stimulusType_stimulusType_variableParameters_stimulusType_stimulusType_variableParameters_parameter_id
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="id" type="xs:IDREF" use="required">
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:stimulusType / fixedParameters
Namespace No namespace
Annotations
 
Fixed parameters are properties of a stimulus that can be
displayed or used to select a stimulus from a list based on a certain
criterion.
Diagram
Diagram experiment.tmp#stimulusType_stimulusType_fixedParameters_parameter
Properties
content complex
minOccurs 0
Model
Children parameter
Instance
 
<fixedParameters>
  <parameter id="">{0,unbounded}</parameter>
</fixedParameters>
Source
 
<xs:element name="fixedParameters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Fixed parameters are properties of a stimulus that can be displayed or used to select a stimulus from a list based on a certain criterion.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
        <xs:complexType mixed="true">
          <xs:choice maxOccurs="unbounded" minOccurs="0">
            <xs:element name="b" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="i" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
            <xs:element name="u" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
          </xs:choice>
          <xs:attribute name="id" type="xs:IDREF" use="required"/>
        </xs:complexType>
        <!--xs:simpleContent>
                                <xs:extension base="xs:string">
                                <xs:attribute name="id" type="xs:IDREF" use="required"/>
                                </xs:extension>
                                </xs:simpleContent-->
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:stimulusType / fixedParameters / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#stimulusType_stimulusType_fixedParameters_stimulusType_stimulusType_fixedParameters_parameter_id experiment.tmp#stimulusType_stimulusType_fixedParameters_stimulusType_stimulusType_fixedParameters_parameter_b experiment.tmp#stimulusType_stimulusType_fixedParameters_stimulusType_stimulusType_fixedParameters_parameter_i experiment.tmp#stimulusType_stimulusType_fixedParameters_stimulusType_stimulusType_fixedParameters_parameter_u
Properties
content complex
minOccurs 0
maxOccurs unbounded
mixed true
Model
b* | i* | u*
Children b, i, u
Instance
 
<parameter id="">
  <b>{0,unbounded}</b>
  <i>{0,unbounded}</i>
  <u>{0,unbounded}</u>
</parameter>
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType mixed="true">
    <xs:choice maxOccurs="unbounded" minOccurs="0">
      <xs:element name="b" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="i" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
      <xs:element name="u" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
    </xs:choice>
    <xs:attribute name="id" type="xs:IDREF" use="required"/>
  </xs:complexType>
  <!--xs:simpleContent>
                                <xs:extension base="xs:string">
                                <xs:attribute name="id" type="xs:IDREF" use="required"/>
                                </xs:extension>
                                </xs:simpleContent-->
</xs:element>
[ top ]
Element apex:stimulusType / fixedParameters / parameter / b
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
 
<xs:element name="b" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:stimulusType / fixedParameters / parameter / i
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
 
<xs:element name="i" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:stimulusType / fixedParameters / parameter / u
Namespace No namespace
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
maxOccurs unbounded
Source
 
<xs:element name="u" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:stimuliType / pluginstimuli
Namespace No namespace
Diagram
Diagram experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType experiment.tmp#pluginStimuliType
Type apex:pluginStimuliType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children parameter, script
Instance
 
<pluginstimuli>
  <script source="">{0,1}</script>
  <parameter name="">{0,unbounded}</parameter>
</pluginstimuli>
Source
 
<xs:element name="pluginstimuli" type="apex:pluginStimuliType" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:apex / connections
Namespace No namespace
Annotations
 
In this section, connections can be made between
datablocks, filters and devices. "from" is only possible for datablocks
and filters, "to" is only possible for filters that accept input (thus
no generators) and devices. Connections can only be made between
elements belonging to the same device. If no connections are specified,
Apex tries to make a default network by connecting all channels from
_ALL_ (== all datablocks) to all channels from the datablocks' device.
Default connections are not made when filters are present.
Diagram
Diagram experiment.tmp#connectionsType_connection experiment.tmp#connectionsType
Type apex:connectionsType
Properties
content complex
minOccurs 0
Model
Children connection
Instance
 
<connections>
  <connection>{0,unbounded}</connection>
</connections>
Source
 
<xs:element name="connections" minOccurs="0" type="apex:connectionsType">
  <xs:annotation>
    <xs:documentation>In this section, connections can be made between datablocks, filters and devices. "from" is only possible for datablocks and filters, "to" is only possible for filters that accept input (thus no generators) and devices. Connections can only be made between elements belonging to the same device. If no connections are specified, Apex tries to make a default network by connecting all channels from _ALL_ (== all datablocks) to all channels from the datablocks' device. Default connections are not made when filters are present.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:connectionsType / connection
Namespace No namespace
Diagram
Diagram experiment.tmp#connectionsType_connectionsType_connection_from experiment.tmp#connectionsType_connectionsType_connection_to
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children from, to
Instance
 
<connection>
  <from id="">{1,1}</from>
  <to id="">{1,1}</to>
</connection>
Source
 
<xs:element name="connection" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="from" type="apex:connectFromType">
        <xs:annotation>
          <xs:documentation>The channel of the filter/datablock where the connection is started from.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="to" type="apex:connectToType">
        <xs:annotation>
          <xs:documentation>The channel of the device/filter where the connection ends.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:connectionsType / connection / from
Namespace No namespace
Annotations
 
The channel of the
filter/datablock where the connection is started
from.
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#connectFromType_id experiment.tmp#connectFromType_channel experiment.tmp#connectFromType
Type apex:connectFromType
Properties
content complex
Model
Children channel, id
Instance
 
<from id="">
  <id mode="name">{1,1}</id>
  <channel id="">{1,1}</channel>
</from>
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="from" type="apex:connectFromType">
  <xs:annotation>
    <xs:documentation>The channel of the filter/datablock where the connection is started from.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:connectFromType / id
Namespace No namespace
Diagram
Diagram experiment.tmp#idOrAll experiment.tmp#connectFromType_connectFromType_id_mode
Type extension of apex:idOrAll
Type hierarchy
Properties
content complex
Attributes
QName Type Default Use Annotation
mode restriction of xs:string name optional 
Method of matching the given id.
Source
 
<xs:element name="id">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="apex:idOrAll">
        <xs:attribute name="mode" default="name">
          <xs:annotation>
            <xs:documentation>Method of matching the given id.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="name">
                <xs:annotation>
                  <xs:documentation>Exactly match the given ID</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="regexp">
                <xs:annotation>
                  <xs:documentation>Use regular expression to match an ID</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="wildcard">
                <xs:annotation>
                  <xs:documentation>Use wildcards (*,?,[]) to match an ID</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:connectFromType / channel
Namespace No namespace
Annotations
 
The channel to be used. Channels are zero based, ie the first
channel is 0, the second 1, etc. This parameter can have an ID for later
referral.
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:unsignedInt
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="channel">
  <xs:annotation>
    <xs:documentation>The channel to be used. Channels are zero based, ie the first channel is 0, the second 1, etc. This parameter can have an ID for later referral.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:unsignedInt">
        <xs:attributeGroup ref="apex:filterParam">
        </xs:attributeGroup>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:connectionsType / connection / to
Namespace No namespace
Annotations
 
The channel of the device/filter
where the connection ends.
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#connectToType_id experiment.tmp#connectToType_channel experiment.tmp#connectToType
Type apex:connectToType
Properties
content complex
Model
Children channel, id
Instance
 
<to id="">
  <id>{1,1}</id>
  <channel id="">{1,1}</channel>
</to>
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="to" type="apex:connectToType">
  <xs:annotation>
    <xs:documentation>The channel of the device/filter where the connection ends.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:connectToType / id
Namespace No namespace
Diagram
Diagram
Type xs:IDREF
Properties
content simple
Source
 
<xs:element name="id" type="xs:IDREF">
</xs:element>
[ top ]
Element apex:connectToType / channel
Namespace No namespace
Annotations
 
The channel to be used. Channels are zero based, ie the first
channel is 0, the second 1, etc. This parameter can have an ID for later
referral. 
Channel -1 means mute.
Diagram
Diagram experiment.tmp#unsignedPlus-1 experiment.tmp#filterParam
Type extension of apex:unsignedPlus-1
Type hierarchy
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="channel">
  <xs:annotation>
    <xs:documentation>The channel to be used. Channels are zero based, ie the first channel is 0, the second 1, etc. This parameter can have an ID for later referral. Channel -1 means mute.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="apex:unsignedPlus-1">
        <xs:attributeGroup ref="apex:filterParam">
        </xs:attributeGroup>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:apex / randomgenerators
Namespace No namespace
Annotations
 
Randomgenerators generate random numbers according to a
    certain specification and can set any parameter defined elsewhere before
    stimulus output. All randomgenerators are asked to set their
    corresponding parameters right before a stimulus is
output.
Diagram
Diagram experiment.tmp#randomgeneratorsType_randomgenerator experiment.tmp#randomgeneratorsType
Type apex:randomgeneratorsType
Properties
content complex
minOccurs 0
Model
Children randomgenerator
Instance
 
<randomgenerators>
  <randomgenerator id="">{0,unbounded}</randomgenerator>
</randomgenerators>
Source
 
<xs:element name="randomgenerators" minOccurs="0" type="apex:randomgeneratorsType">
  <xs:annotation>
    <xs:documentation>Randomgenerators generate random numbers according to a certain specification and can set any parameter defined elsewhere before stimulus output. All randomgenerators are asked to set their corresponding parameters right before a stimulus is output.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:randomgeneratorsType / randomgenerator
Namespace No namespace
Diagram
Diagram experiment.tmp#randomgenerator_id experiment.tmp#randomgenerator_min experiment.tmp#randomgenerator_max experiment.tmp#randomgenerator_type experiment.tmp#randomgenerator_parameter experiment.tmp#randomgenerator
Type apex:randomgenerator
Properties
content complex
minOccurs 0
maxOccurs unbounded
Model
Children max, min, parameter, type
Instance
 
<randomgenerator id="">
  <min>{1,1}</min>
  <max>{1,1}</max>
  <type>{1,1}</type>
  <parameter>{1,1}</parameter>
</randomgenerator>
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:element name="randomgenerator" type="apex:randomgenerator" minOccurs="0" maxOccurs="unbounded"/>
[ top ]
Element apex:randomgenerator / min
Namespace No namespace
Annotations
 
Minimum value of the random numbers (inclusive)
Diagram
Diagram
Type xs:double
Properties
content simple
Source
 
<xs:element name="min" type="xs:double">
  <xs:annotation>
    <xs:documentation>Minimum value of the random numbers (inclusive)</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:randomgenerator / max
Namespace No namespace
Annotations
 
Maximum value of the random numbers (exclusive)
Diagram
Diagram
Type xs:double
Properties
content simple
Source
 
<xs:element name="max" type="xs:double">
  <xs:annotation>
    <xs:documentation>Maximum value of the random numbers (exclusive)</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:randomgenerator / type
Namespace No namespace
Annotations
 
Data type
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration double 
Fractional number
enumeration int 
Whole number
Source
 
<xs:element name="type">
  <xs:annotation>
    <xs:documentation>Data type</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="double">
        <xs:annotation>
          <xs:documentation>Fractional number</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="int">
        <xs:annotation>
          <xs:documentation>Whole number</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:randomgenerator / parameter
Namespace No namespace
Annotations
 
Parameter to be set to the random value
Diagram
Diagram
Type xs:IDREF
Properties
content simple
Source
 
<xs:element name="parameter" type="xs:IDREF">
  <xs:annotation>
    <xs:documentation>Parameter to be set to the random value</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / calibration
Namespace No namespace
Annotations
 
In this optional section, parameters for the built in
    calibration mechanism are defined. Calibration is the process of
    ensuring a relation between a digital stimulus level (dB) and the actual
    audio output (dBSPL). Calibration parameters are stored in profiles that
    are persistent between sessions. Profiles are stored in the
    apex/config/calibration directory and can be edited by hand if
required.
Diagram
Diagram experiment.tmp#calibrationType_profile experiment.tmp#calibrationType_soundlevelmeter experiment.tmp#calibrationType_stimuli experiment.tmp#calibrationType_parameters experiment.tmp#calibrationType
Type apex:calibrationType
Properties
content complex
minOccurs 0
maxOccurs 1
Model
Children parameters, soundlevelmeter, stimuli
Instance
 
<calibration profile="">
  <soundlevelmeter>{0,1}</soundlevelmeter>
  <stimuli>{1,1}</stimuli>
  <parameters>{1,1}</parameters>
</calibration>
Attributes
QName Type Use
profile xs:Name required
Source
 
<xs:element name="calibration" minOccurs="0" maxOccurs="1" type="apex:calibrationType">
  <xs:annotation>
    <xs:documentation>In this optional section, parameters for the built in calibration mechanism are defined. Calibration is the process of ensuring a relation between a digital stimulus level (dB) and the actual audio output (dBSPL). Calibration parameters are stored in profiles that are persistent between sessions. Profiles are stored in the apex/config/calibration directory and can be edited by hand if required.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter
Namespace No namespace
Annotations
 
Information necessary for automatic calibration using an interface to a sound level meter.
Diagram
Diagram experiment.tmp#calibrationType_calibrationType_soundlevelmeter_plugin experiment.tmp#calibrationType_calibrationType_soundlevelmeter_transducer experiment.tmp#calibrationType_calibrationType_soundlevelmeter_frequency_weighting experiment.tmp#calibrationType_calibrationType_soundlevelmeter_time_weighting experiment.tmp#calibrationType_calibrationType_soundlevelmeter_type experiment.tmp#calibrationType_calibrationType_soundlevelmeter_percentile experiment.tmp#calibrationType_calibrationType_soundlevelmeter_time experiment.tmp#calibrationType_calibrationType_soundlevelmeter_accuracy experiment.tmp#calibrationType_calibrationType_soundlevelmeter_maxiterations
Properties
content complex
minOccurs 0
Model
Children accuracy, frequency_weighting, maxiterations, percentile, plugin, time, time_weighting, transducer, type
Instance
 
<soundlevelmeter>
  <plugin>{1,1}</plugin>
  <transducer>{0,1}</transducer>
  <frequency_weighting>{1,1}</frequency_weighting>
  <time_weighting>{1,1}</time_weighting>
  <type>{1,1}</type>
  <percentile>{0,1}</percentile>
  <time>{0,1}</time>
  <accuracy>{0,1}</accuracy>
  <maxiterations>{0,1}</maxiterations>
</soundlevelmeter>
Source
 
<xs:element name="soundlevelmeter" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Information necessary for automatic calibration using an interface to a sound level meter.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="plugin" type="xs:anyURI">
        <xs:annotation>
          <xs:documentation>Filename of the souind level meter plugin to be used</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="transducer" type="xs:string" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Name of the transducer (microphone, ...) to be used by the SLM. Will only be set if your SLM supports it.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="frequency_weighting" default="Z">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Z">
              <xs:annotation>
                <xs:documentation>No weighting: SPL</xs:documentation>
              </xs:annotation>
            </xs:enumeration>
            <xs:enumeration value="A"/>
            <xs:enumeration value="C"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="time_weighting" default="S">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="S"/>
            <xs:enumeration value="F"/>
            <xs:enumeration value="I"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="type" default="RMS">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="RMS"/>
            <xs:enumeration value="peak"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:element>
      <xs:element name="percentile" type="xs:double" minOccurs="0" default="0">
        <xs:annotation>
          <xs:documentation>Percentile of statistics on measurement. If 0 an instantaneous measurement will be made.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="time" type="xs:double" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Measurement time in seconds. If percentile is defined, time should be >0</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="accuracy" type="xs:double" minOccurs="0" default="0.5">
        <xs:annotation>
          <xs:documentation>Automatic calibration is repeated until the measured value is within the accuracy defined here of the target value</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="maxiterations" type="xs:positiveInteger" default="3" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Maximal number of iterations that can be done to reach the requested accuracy. If the requested accuracy is not reached after this number of iterations, the calibration fails</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / plugin
Namespace No namespace
Annotations
 
Filename of the souind level meter plugin to be used
Diagram
Diagram
Type xs:anyURI
Properties
content simple
Source
 
<xs:element name="plugin" type="xs:anyURI">
  <xs:annotation>
    <xs:documentation>Filename of the souind level meter plugin to be used</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / transducer
Namespace No namespace
Annotations
 
Name of the transducer (microphone, ...) to be used by the SLM. Will only be set if your SLM supports it.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="transducer" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Name of the transducer (microphone, ...) to be used by the SLM. Will only be set if your SLM supports it.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / frequency_weighting
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
default Z
Facets
enumeration Z 
No weighting: SPL
enumeration A
enumeration C
Source
 
<xs:element name="frequency_weighting" default="Z">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Z">
        <xs:annotation>
          <xs:documentation>No weighting: SPL</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="A"/>
      <xs:enumeration value="C"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / time_weighting
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
default S
Facets
enumeration S
enumeration F
enumeration I
Source
 
<xs:element name="time_weighting" default="S">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="S"/>
      <xs:enumeration value="F"/>
      <xs:enumeration value="I"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / type
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
default RMS
Facets
enumeration RMS
enumeration peak
Source
 
<xs:element name="type" default="RMS">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="RMS"/>
      <xs:enumeration value="peak"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / percentile
Namespace No namespace
Annotations
 
Percentile of statistics on measurement. If 0 an instantaneous measurement will be made.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="percentile" type="xs:double" minOccurs="0" default="0">
  <xs:annotation>
    <xs:documentation>Percentile of statistics on measurement. If 0 an instantaneous measurement will be made.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / time
Namespace No namespace
Annotations
 
Measurement time in seconds. If percentile is defined, time should be >0
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
Source
 
<xs:element name="time" type="xs:double" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Measurement time in seconds. If percentile is defined, time should be >0</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / accuracy
Namespace No namespace
Annotations
 
Automatic calibration is repeated until the measured value is within the accuracy defined here of the target value
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 0.5
Source
 
<xs:element name="accuracy" type="xs:double" minOccurs="0" default="0.5">
  <xs:annotation>
    <xs:documentation>Automatic calibration is repeated until the measured value is within the accuracy defined here of the target value</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / soundlevelmeter / maxiterations
Namespace No namespace
Annotations
 
Maximal number of iterations that can be done to reach the requested accuracy. If the requested accuracy is not reached after this number of iterations, the calibration fails
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
default 3
Source
 
<xs:element name="maxiterations" type="xs:positiveInteger" default="3" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximal number of iterations that can be done to reach the requested accuracy. If the requested accuracy is not reached after this number of iterations, the calibration fails</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / stimuli
Namespace No namespace
Annotations
 
Stimuli that are used for calibration. These can be, and in
    some cases should be stimuli that are used in the actual
experiment.
Diagram
Diagram experiment.tmp#calibrationType_calibrationType_stimuli_stimulus
Properties
content complex
Model
Children stimulus
Instance
 
<stimuli>
  <stimulus id="">{1,unbounded}</stimulus>
</stimuli>
Source
 
<xs:element name="stimuli">
  <xs:annotation>
    <xs:documentation>Stimuli that are used for calibration. These can be, and in some cases should be stimuli that are used in the actual experiment.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="stimulus" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:attribute name="id" type="xs:IDREF" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:calibrationType / stimuli / stimulus
Namespace No namespace
Diagram
Diagram experiment.tmp#calibrationType_calibrationType_stimuli_calibrationType_calibrationType_stimuli_stimulus_id
Properties
content complex
minOccurs 1
maxOccurs unbounded
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:element name="stimulus" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:attribute name="id" type="xs:IDREF" use="required"/>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:calibrationType / parameters
Namespace No namespace
Annotations
 
Parameters that are used to calibrate the system. Generally
    some output gain parameters of the last stage (eg the wavdevice) are
used.
Diagram
Diagram experiment.tmp#calibrationType_calibrationType_parameters_parameter
Properties
content complex
Model
Children parameter
Instance
 
<parameters>
  <parameter id="">{1,unbounded}</parameter>
</parameters>
Source
 
<xs:element name="parameters">
  <xs:annotation>
    <xs:documentation>Parameters that are used to calibrate the system. Generally some output gain parameters of the last stage (eg the wavdevice) are used.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" minOccurs="1" maxOccurs="unbounded">
        <xs:complexType>
          <xs:sequence>
            <xs:element name="targetamplitude" type="xs:double">
              <xs:annotation>
                <xs:documentation>Target acoustical measurement of the stimuli defined above during the experiment. Generally in dBSPL.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="calibrationamplitude" type="xs:double" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Value to calibrate at. Generally in dBSPL and higher than targetamplitude. Can be changed during calibration.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="mute" type="xs:double" default="-150">
              <xs:annotation>
                <xs:documentation>Value to be used for the other parameters while calibrating this parameter. Has no effect on the actual calibration. Useful for eg muting the other channel of a headphone.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="min" type="xs:double" default="-50" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Minimum parameter value that can be set by the calibrator.</xs:documentation>
              </xs:annotation>
            </xs:element>
            <xs:element name="max" type="xs:double" default="10" minOccurs="0">
              <xs:annotation>
                <xs:documentation>Maximum parameter value that can be set by the calibrator.</xs:documentation>
              </xs:annotation>
            </xs:element>
          </xs:sequence>
          <xs:attribute name="id" type="xs:IDREF" use="required"/>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:calibrationType / parameters / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#calibrationType_calibrationType_parameters_calibrationType_calibrationType_parameters_parameter_id experiment.tmp#calibrationType_calibrationType_parameters_calibrationType_calibrationType_parameters_parameter_targetamplitude experiment.tmp#calibrationType_calibrationType_parameters_calibrationType_calibrationType_parameters_parameter_calibrationamplitude experiment.tmp#calibrationType_calibrationType_parameters_calibrationType_calibrationType_parameters_parameter_mute experiment.tmp#calibrationType_calibrationType_parameters_calibrationType_calibrationType_parameters_parameter_min experiment.tmp#calibrationType_calibrationType_parameters_calibrationType_calibrationType_parameters_parameter_max
Properties
content complex
minOccurs 1
maxOccurs unbounded
Model
Children calibrationamplitude, max, min, mute, targetamplitude
Instance
 
<parameter id="">
  <targetamplitude>{1,1}</targetamplitude>
  <calibrationamplitude>{0,1}</calibrationamplitude>
  <mute>{1,1}</mute>
  <min>{0,1}</min>
  <max>{0,1}</max>
</parameter>
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:element name="parameter" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:sequence>
      <xs:element name="targetamplitude" type="xs:double">
        <xs:annotation>
          <xs:documentation>Target acoustical measurement of the stimuli defined above during the experiment. Generally in dBSPL.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="calibrationamplitude" type="xs:double" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Value to calibrate at. Generally in dBSPL and higher than targetamplitude. Can be changed during calibration.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="mute" type="xs:double" default="-150">
        <xs:annotation>
          <xs:documentation>Value to be used for the other parameters while calibrating this parameter. Has no effect on the actual calibration. Useful for eg muting the other channel of a headphone.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="min" type="xs:double" default="-50" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Minimum parameter value that can be set by the calibrator.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="max" type="xs:double" default="10" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Maximum parameter value that can be set by the calibrator.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:sequence>
    <xs:attribute name="id" type="xs:IDREF" use="required"/>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:calibrationType / parameters / parameter / targetamplitude
Namespace No namespace
Annotations
 
Target acoustical measurement of the
    stimuli defined above during the experiment. Generally in
dBSPL.
Diagram
Diagram
Type xs:double
Properties
content simple
Source
 
<xs:element name="targetamplitude" type="xs:double">
  <xs:annotation>
    <xs:documentation>Target acoustical measurement of the stimuli defined above during the experiment. Generally in dBSPL.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / parameters / parameter / calibrationamplitude
Namespace No namespace
Annotations
 
Value to calibrate at. Generally in
dBSPL and higher than targetamplitude. Can be changed during calibration.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
Source
 
<xs:element name="calibrationamplitude" type="xs:double" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Value to calibrate at. Generally in dBSPL and higher than targetamplitude. Can be changed during calibration.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / parameters / parameter / mute
Namespace No namespace
Annotations
 
Value to be used for the other
    parameters while calibrating this parameter. Has no
    effect on the actual calibration. Useful for eg
    muting the other channel of a
headphone.
Diagram
Diagram
Type xs:double
Properties
content simple
default -150
Source
 
<xs:element name="mute" type="xs:double" default="-150">
  <xs:annotation>
    <xs:documentation>Value to be used for the other parameters while calibrating this parameter. Has no effect on the actual calibration. Useful for eg muting the other channel of a headphone.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / parameters / parameter / min
Namespace No namespace
Annotations
 
Minimum parameter value that can be set by the calibrator.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default -50
Source
 
<xs:element name="min" type="xs:double" default="-50" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Minimum parameter value that can be set by the calibrator.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:calibrationType / parameters / parameter / max
Namespace No namespace
Annotations
 
Maximum parameter value that can be set by the calibrator.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 10
Source
 
<xs:element name="max" type="xs:double" default="10" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Maximum parameter value that can be set by the calibrator.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / results
Namespace No namespace
Annotations
 
Parameters related to the presentation/analysis of the
result of this experiment are defined here.
Diagram
Diagram experiment.tmp#resultsType_page experiment.tmp#resultsType_resultparameters experiment.tmp#resultsType_resultscript experiment.tmp#resultsType_showduringexperiment experiment.tmp#resultsType_showafterexperiment experiment.tmp#resultsType_confirmshowresults experiment.tmp#resultsType_matlabscript experiment.tmp#resultsType_subject experiment.tmp#resultsType
Type apex:resultsType
Properties
content complex
minOccurs 0
Model
Children confirmshowresults, matlabscript, page, resultparameters, resultscript, showafterexperiment, showduringexperiment, subject
Instance
 
<results>
  <page>{1,1}</page>
  <resultparameters>{0,1}</resultparameters>
  <resultscript>{0,1}</resultscript>
  <showduringexperiment>{0,1}</showduringexperiment>
  <showafterexperiment>{0,1}</showafterexperiment>
  <confirmshowresults>{0,1}</confirmshowresults>
  <matlabscript>{0,1}</matlabscript>
  <subject>{0,1}</subject>
</results>
Source
 
<xs:element name="results" minOccurs="0" type="apex:resultsType">
  <xs:annotation>
    <xs:documentation>Parameters related to the presentation/analysis of the result of this experiment are defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / page
Namespace No namespace
Annotations
 
URL of the HTML page to be shown in the results window. The page should have the appropriate javascript methods embedded.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 1
default apexresults.html
Source
 
<xs:element name="page" type="xs:anyURI" minOccurs="1" default="apexresults.html">
  <xs:annotation>
    <xs:documentation>URL of the HTML page to be shown in the results window. The page should have the appropriate javascript methods embedded.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / resultparameters
Namespace No namespace
Annotations
 
Parameters to be passed to the results page. Each parameter will be set in hash params.
Diagram
Diagram experiment.tmp#resultsType_resultsType_resultparameters_parameter
Properties
content complex
minOccurs 0
Model
Children parameter
Instance
 
<resultparameters>
  <parameter name="">{0,unbounded}</parameter>
</resultparameters>
Source
 
<xs:element name="resultparameters" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Parameters to be passed to the results page. Each parameter will be set in hash params.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:sequence>
      <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
        <xs:complexType>
          <xs:simpleContent>
            <xs:extension base="xs:string">
              <xs:attribute name="name" type="xs:string"/>
            </xs:extension>
          </xs:simpleContent>
        </xs:complexType>
      </xs:element>
    </xs:sequence>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:resultsType / resultparameters / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#resultsType_resultsType_resultparameters_resultsType_resultsType_resultparameters_parameter_name
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
name xs:string optional
Source
 
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attribute name="name" type="xs:string"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:resultsType / resultscript
Namespace No namespace
Annotations
 
Javascript, which will be executed after loading the results page, in the context of the results page.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
default
Source
 
<xs:element name="resultscript" type="xs:string" minOccurs="0" default="">
  <xs:annotation>
    <xs:documentation>Javascript, which will be executed after loading the results page, in the context of the results page.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / showduringexperiment
Namespace No namespace
Annotations
 
If true, an extra window will be created which will show
the results of the current experiment while the experiment is being executed.
Javascript embedded in the page will be executed upon each new trial.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
 
<xs:element name="showduringexperiment" type="xs:boolean" minOccurs="0" default="true">
  <xs:annotation>
    <xs:documentation>If true, an extra window will be created which will show the results of the current experiment while the experiment is being executed. Javascript embedded in the page will be executed upon each new trial.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / showafterexperiment
Namespace No namespace
Annotations
 
If true a new window will be opened and the results will be shown when the experiment is finished.
Confirmation might still be needed (see 'confirmshowresults').
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="showafterexperiment" type="xs:boolean" minOccurs="0" default="false">
  <xs:annotation>
    <xs:documentation>If true a new window will be opened and the results will be shown when the experiment is finished. Confirmation might still be needed (see 'confirmshowresults').</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / confirmshowresults
Namespace No namespace
Annotations
 
If true a dialog will ask for confirmation whether results should be shown.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
 
<xs:element name="confirmshowresults" type="xs:boolean" minOccurs="0" default="true">
  <xs:annotation>
    <xs:documentation>If true a dialog will ask for confirmation whether results should be shown.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / matlabscript
Namespace No namespace
Annotations
 
Matlab script to be used for processing results. Will be added as an XML processing tag to the results file
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="matlabscript" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Matlab script to be used for processing results. Will be added as an XML processing tag to the results file</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:resultsType / subject
Namespace No namespace
Annotations
 
Name of the test subject. Will be appended to the suggested results file name. Is typically modified at
the beginning of an experiment using an interactive entry.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="subject" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Name of the test subject. Will be appended to the suggested results file name. Is typically modified at the beginning of an experiment using an interactive entry.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:apex / interactive
Namespace No namespace
Annotations
 
For every entry in this section, the value of a certain
element in this experiment file will be changed to the value set by the
user in a GUI window.
Diagram
Diagram experiment.tmp#interactiveType_entry experiment.tmp#interactiveType
Type apex:interactiveType
Properties
content complex
minOccurs 0
Model
Children entry
Instance
 
<interactive>
  <entry constraint="" default="" description="" expression="" type="">{1,unbounded}</entry>
</interactive>
Source
 
<xs:element name="interactive" minOccurs="0" type="apex:interactiveType">
  <xs:annotation>
    <xs:documentation>For every entry in this section, the value of a certain element in this experiment file will be changed to the value set by the user in a GUI window.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:interactiveType / entry
Namespace No namespace
Diagram
Diagram experiment.tmp#interactiveType_interactiveType_entry_expression experiment.tmp#interactiveType_interactiveType_entry_type experiment.tmp#interactiveType_interactiveType_entry_description experiment.tmp#interactiveType_interactiveType_entry_default experiment.tmp#interactiveType_interactiveType_entry_constraint
Properties
content complex
maxOccurs unbounded
Attributes
QName Type Use Annotation
constraint xs:string optional 
Regex against which the value
should match.
default xs:string required 
Default value for the
replacement.
description xs:string required 
Description of this entry, will be
shown to the user.
expression xs:string optional 
XPath expression defining the element
to be modified. The user will be alerted if the
expression yields no results. If the expression
yields more than one result, every element found
will be modified. The modification takes place
before validation, so the resulting document will
not be used unless valid. Modifications will be
reported in the results file.
If expression is not present, the user input will be saved to the results file, but
nothing will be modified.
type restriction of xs:string required 
Data type of the element to be
modified. It impacts the dialog box presented to the
user and prevents input of data of the wrong data
type.
Source
 
<xs:element name="entry" maxOccurs="unbounded">
  <xs:complexType>
    <xs:attribute name="expression" type="xs:string" use="optional">
      <xs:annotation>
        <xs:documentation>XPath expression defining the element to be modified. The user will be alerted if the expression yields no results. If the expression yields more than one result, every element found will be modified. The modification takes place before validation, so the resulting document will not be used unless valid. Modifications will be reported in the results file. If expression is not present, the user input will be saved to the results file, but nothing will be modified.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="type" use="required">
      <xs:annotation>
        <xs:documentation>Data type of the element to be modified. It impacts the dialog box presented to the user and prevents input of data of the wrong data type.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="int">
            <xs:annotation>
              <xs:documentation>An integer number</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="double">
            <xs:annotation>
              <xs:documentation>A number</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="string">
            <xs:annotation>
              <xs:documentation>Some text</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="bool">
            <xs:annotation>
              <xs:documentation>Boolean value "true" or "false"</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="combo">
            <xs:annotation>
              <xs:documentation>Value from list. The list of options should be specified in default, separated by |</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="description" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>Description of this entry, will be shown to the user.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="default" type="xs:string" use="required">
      <xs:annotation>
        <xs:documentation>Default value for the replacement.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
    <xs:attribute name="constraint" type="xs:string">
      <xs:annotation>
        <xs:documentation>Regex against which the value should match.</xs:documentation>
      </xs:annotation>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:apex / general
Namespace No namespace
Annotations
 
Some general experiment parameters are defined
here.
Diagram
Diagram experiment.tmp#generalType_exitafter experiment.tmp#generalType_autosave experiment.tmp#generalType_waitforstart experiment.tmp#generalType_allowskip experiment.tmp#generalType_runoutputtest experiment.tmp#generalType_outputtestinput experiment.tmp#generalType_scriptlibrary experiment.tmp#generalType_scriptparameters experiment.tmp#generalType
Type apex:generalType
Properties
content complex
minOccurs 0
Model
Children allowskip, autosave, exitafter, outputtestinput, runoutputtest, scriptlibrary, scriptparameters, waitforstart
Instance
 
<general>
  <exitafter>{0,1}</exitafter>
  <autosave>{0,1}</autosave>
  <waitforstart>{0,1}</waitforstart>
  <allowskip>{0,1}</allowskip>
  <runoutputtest>{0,1}</runoutputtest>
  <outputtestinput>{0,1}</outputtestinput>
  <scriptlibrary>{0,1}</scriptlibrary>
  <scriptparameters>{0,1}</scriptparameters>
</general>
Source
 
<xs:element name="general" minOccurs="0" type="apex:generalType">
  <xs:annotation>
    <xs:documentation>Some general experiment parameters are defined here.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / exitafter
Namespace No namespace
Annotations
 
Exit immediately after the experiment was
finished. The "save results" dialog box is always
shown.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="exitafter" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Exit immediately after the experiment was finished. The "save results" dialog box is always shown.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / autosave
Namespace No namespace
Annotations
 
If defined, apex will automatically select a filename and 
only present the user with a messagebox asking wheter to save the results yes or no
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="autosave" type="xs:boolean" minOccurs="0" default="false">
  <xs:annotation>
    <xs:documentation>If defined, apex will automatically select a filename and only present the user with a messagebox asking wheter to save the results yes or no</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / waitforstart
Namespace No namespace
Annotations
 
If true, the next trial is only presented after clicking the Start button,
selecting Start from the Experiment menu or pressing F5.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
Source
 
<xs:element name="waitforstart" type="xs:boolean" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If true, the next trial is only presented after clicking the Start button, selecting Start from the Experiment menu or pressing F5.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / allowskip
Namespace No namespace
Annotations
 
If true, the F7 key can be used to skip anything that takes a certain
amount of time, eg intro/outro/iti
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default true
Source
 
<xs:element name="allowskip" type="xs:boolean" minOccurs="0" default="true">
  <xs:annotation>
    <xs:documentation>If true, the F7 key can be used to skip anything that takes a certain amount of time, eg intro/outro/iti</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / runoutputtest
Namespace No namespace
Annotations
 
Run test to compare output with input files. Only works for WavDevice, and
the apex executable must be compiled with WRITEWAVOUTPUT defined.
If set, the data send to the soundcard is also written to a file, and afterwards
compared with the input. This allows to check if the entire processing/buffering works properly.
If the input below is not specified, the test assumes all available datablocks were played
sequential. Filters and connections are not taken into account. (eg if two datablocks are defined,
the test just checks if the output is identical to the two wavefiles played right after each other).
To allow testing filter/loop/connections functionality, create a wavefile that mimics all the processing,
and specify the path below, and the test will use it to compare against the output.
See the example tests for more info.
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="runoutputtest" type="xs:boolean" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Run test to compare output with input files. Only works for WavDevice, and the apex executable must be compiled with WRITEWAVOUTPUT defined. If set, the data send to the soundcard is also written to a file, and afterwards compared with the input. This allows to check if the entire processing/buffering works properly. If the input below is not specified, the test assumes all available datablocks were played sequential. Filters and connections are not taken into account. (eg if two datablocks are defined, the test just checks if the output is identical to the two wavefiles played right after each other). To allow testing filter/loop/connections functionality, create a wavefile that mimics all the processing, and specify the path below, and the test will use it to compare against the output. See the example tests for more info.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / outputtestinput
Namespace No namespace
Annotations
 
Optional: path to a file to compare the output with.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
maxOccurs 1
Source
 
<xs:element name="outputtestinput" type="xs:anyURI" minOccurs="0" maxOccurs="1">
  <xs:annotation>
    <xs:documentation>Optional: path to a file to compare the output with.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / scriptlibrary
Namespace No namespace
Annotations
 
Library of ECMAScript functions. Functions defined in this library can be used from any other script for the experiment.
Diagram
Diagram
Type xs:anyURI
Properties
content simple
minOccurs 0
Source
 
<xs:element name="scriptlibrary" type="xs:anyURI" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Library of ECMAScript functions. Functions defined in this library can be used from any other script for the experiment.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generalType / scriptparameters
Namespace No namespace
Diagram
Diagram experiment.tmp#generalType_generalType_scriptparameters_parameter
Properties
content complex
minOccurs 0
Model
Children parameter
Instance
 
<scriptparameters>
  <parameter name="">{1,unbounded}</parameter>
</scriptparameters>
Source
 
<xs:element name="scriptparameters" minOccurs="0">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>Scriptparameters will be made available to all modules that use ECMAScript, such as plugin datablocks, stimuli, trials and procedures.</xs:documentation>
    </xs:annotation>
    <xs:sequence>
      <xs:element name="parameter" default="" minOccurs="1" 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:complexType>
</xs:element>
[ top ]
Element apex:generalType / scriptparameters / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#generalType_generalType_scriptparameters_generalType_generalType_scriptparameters_parameter_name
Type extension of xs:string
Properties
content complex
minOccurs 1
maxOccurs unbounded
default
Attributes
QName Type Use
name xs:Name required
Source
 
<xs:element name="parameter" default="" minOccurs="1" 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:calibstimType / parameter
Namespace No namespace
Annotations
 
Parameter to be calibrated using this stimulus.
Diagram
Diagram experiment.tmp#calibstimType_calibstimType_parameter_targetloudness
Type extension of xs:IDREF
Properties
content complex
minOccurs 1
maxOccurs unbounded
Attributes
QName Type Use Annotation
targetloudness xs:double required 
Target loudness value for calibration of this
parameter using this stimulus. Mostly in dBSPL. The aim of
the calibration is that this stimulus is presented at this
loudness in dBSPL to the subject.
Source
 
<xs:element name="parameter" minOccurs="1" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Parameter to be calibrated using this stimulus.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:IDREF">
        <xs:attribute name="targetloudness" type="xs:double" use="required">
          <xs:annotation>
            <xs:documentation>Target loudness value for calibration of this parameter using this stimulus. Mostly in dBSPL. The aim of the calibration is that this stimulus is presented at this loudness in dBSPL to the subject.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:adaptiveProcedure / parameters
Namespace No namespace
Diagram
Diagram experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.tmp#procedureParametersType experiment.tmp#adaptiveProcedureParametersType_nUp experiment.tmp#adaptiveProcedureParametersType_nDown experiment.tmp#adaptiveProcedureParametersType_adapt_parameter experiment.tmp#adaptiveProcedureParametersType_start_value experiment.tmp#adaptiveProcedureParametersType_stop_after_type experiment.tmp#adaptiveProcedureParametersType_stop_after experiment.tmp#adaptiveProcedureParametersType_min_value experiment.tmp#adaptiveProcedureParametersType_max_value experiment.tmp#adaptiveProcedureParametersType_larger_is_easier experiment.tmp#adaptiveProcedureParametersType_repeat_first_until_correct experiment.tmp#adaptiveProcedureParametersType_stepsizes experiment.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 experiment.tmp#procedureParametersType_procedureParametersType_intervals_count experiment.tmp#procedureParametersType_procedureParametersType_intervals_select experiment.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 experiment.tmp#procedureParametersType_procedureParametersType_intervals_procedureParametersType_procedureParametersType_intervals_interval_number experiment.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 experiment.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 experiment.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_change_after experiment.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 experiment.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_stepsize_begin experiment.tmp#adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_adaptiveProcedureParametersType_adaptiveProcedureParametersType_stepsizes_stepsize_size experiment.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 experiment.tmp#trialsType_trial experiment.tmp#trialsType_plugintrials experiment.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 experiment.tmp#trialType_id experiment.tmp#trialType_answer experiment.tmp#trialType_answer_element experiment.tmp#trialType_screen experiment.tmp#trialType_stimulus experiment.tmp#trialType_standard experiment.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 experiment.tmp#trialType_trialType_answer_key experiment.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 experiment.tmp#screenRefType_id experiment.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 experiment.tmp#stimulusRefType_id experiment.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 experiment.tmp#stimulusRefType_id experiment.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 experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType experiment.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:constantProcedure / parameters
Namespace No namespace
Diagram
Diagram experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.tmp#procedureParametersType experiment.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 experiment.tmp#trialsType_trial experiment.tmp#trialsType_plugintrials experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.tmp#procedureParametersType experiment.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 experiment.tmp#trialsType_trial experiment.tmp#trialsType_plugintrials experiment.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 experiment.tmp#multiProcedureParametersType_order experiment.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 experiment.tmp#procedureType_id experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.tmp#procedureParametersType experiment.tmp#pluginProcedureParametersType_script experiment.tmp#pluginProcedureParametersType_debugger experiment.tmp#pluginProcedureParametersType_adjust_parameter experiment.tmp#pluginProcedureParametersType_parameter experiment.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 experiment.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 experiment.tmp#trialsType_trial experiment.tmp#trialsType_plugintrials experiment.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 experiment.tmp#parameterType_type experiment.tmp#parameterType experiment.tmp#hasIdParameterType_id experiment.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 experiment.tmp#maybeIdParameterType_type experiment.tmp#maybeIdParameterType_id experiment.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 ]
Element apex:wavDeviceType / driver
Namespace No namespace
Annotations
 
Driver architecture to be used for sound
output
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
Facets
enumeration dummy 
Dummy soundcard
enumeration portaudio 
Portaudio is a cross-platform audio
framework
enumeration qtaudio 
Qt Multimedia framework
enumeration asio 
ASIO is a proprietary windows/mac-only audio
framework by Steinberg. Use it if low latency/more then
2 channels is required.
enumeration coreaudio 
CoreAudio is MacOsX' audio framework.
enumeration jack 
Jack is a cross-platform audio
framework. A jack connection will be made to the "drivername" specified in the main config file.
Source
 
<xs:element name="driver" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Driver architecture to be used for sound output</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="dummy">
        <xs:annotation>
          <xs:documentation>Dummy soundcard</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="portaudio">
        <xs:annotation>
          <xs:documentation>Portaudio is a cross-platform audio framework</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="qtaudio">
        <xs:annotation>
          <xs:documentation>Qt Multimedia framework</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="asio">
        <xs:annotation>
          <xs:documentation>ASIO is a proprietary windows/mac-only audio framework by Steinberg. Use it if low latency/more then 2 channels is required.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="coreaudio">
        <xs:annotation>
          <xs:documentation>CoreAudio is MacOsX' audio framework.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="jack">
        <xs:annotation>
          <xs:documentation>Jack is a cross-platform audio framework. A jack connection will be made to the "drivername" specified in the main config file.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:wavDeviceType / card
Namespace No namespace
Annotations
 
Name of the soundcard to be used. Cards are defined in
the main config file. Every soundcard in the system can be
enumerated in the main configfile. Use the ID defined there.
Otherwise the "default" card can be used.
Diagram
Diagram
Type xs:string
Properties
content simple
minOccurs 0
Source
 
<xs:element name="card" type="xs:string" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Name of the soundcard to be used. Cards are defined in the main config file. Every soundcard in the system can be enumerated in the main configfile. Use the ID defined there. Otherwise the "default" card can be used.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:wavDeviceType / channels
Namespace No namespace
Annotations
 
Number of output channels to be used. This is
restricted by the selected driver, with a maximum of 2 for
portaudio.
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
Source
 
<xs:element name="channels" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Number of output channels to be used. This is restricted by the selected driver, with a maximum of 2 for portaudio.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:wavDeviceType / gain
Namespace No namespace
Annotations
 
Final gain of the device, implemented with a software
mixer.
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#gainparam experiment.tmp#channelGainType_channel experiment.tmp#channelGainType
Type apex:channelGainType
Type hierarchy
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use Annotation
channel xs:nonNegativeInteger optional 
Used to specify a single channel to apply gain to,
instead of applying it to all channels at once.
For example, for an amplifier having two channels, these are set independently by using <gain id="ch0" channel="0">-3.00</gain>
<gain id="ch1" channel="1">-6.00</gain> Channels are zero based, ie the first channel is 0, the
second 1 and so on.
id xs:ID optional
Source
 
<xs:element name="gain" type="apex:channelGainType" minOccurs="0" maxOccurs="unbounded">
  <xs:annotation>
    <xs:documentation>Final gain of the device, implemented with a software mixer.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:wavDeviceType / samplerate
Namespace No namespace
Annotations
 
Sample rate of the device. Warning: not all sample
rates are supported by all devices and some drivers automatically
convert to other sample rates. Check your sound card
documentation.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration 16000
enumeration 44100
enumeration 96000
enumeration 32000
enumeration 48000
enumeration 8000
enumeration 22050
enumeration 72000
Source
 
<xs:element name="samplerate">
  <xs:annotation>
    <xs:documentation>Sample rate of the device. Warning: not all sample rates are supported by all devices and some drivers automatically convert to other sample rates. Check your sound card documentation.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="16000"/>
      <xs:enumeration value="44100"/>
      <xs:enumeration value="96000"/>
      <xs:enumeration value="32000"/>
      <xs:enumeration value="48000"/>
      <xs:enumeration value="8000"/>
      <xs:enumeration value="22050"/>
      <xs:enumeration value="72000"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:wavDeviceType / buffersize
Namespace No namespace
Annotations
 
Applies to the soundcard buffer size, not the internal apex buffer size.
Larger sizes are
more efficient, smaller sizes have smaller latencies.
Some notes: for asio, latency is always ( 2 * buffersize + overhead ) / samplerate.
The overhead is very small, eg 16 samples for an Rme Multiface.
Portaudio however always uses a number of internal buffers, mostly 4. Hence, actual latency
is ( 2 * 4 * buffersize + overhead ) / samplerate.
For asio/jack: must be set to the system buffer size.
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
Source
 
<xs:element name="buffersize" minOccurs="0" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Applies to the soundcard buffer size, not the internal apex buffer size. Larger sizes are more efficient, smaller sizes have smaller latencies. Some notes: for asio, latency is always ( 2 * buffersize + overhead ) / samplerate. The overhead is very small, eg 16 samples for an Rme Multiface. Portaudio however always uses a number of internal buffers, mostly 4. Hence, actual latency is ( 2 * 4 * buffersize + overhead ) / samplerate. For asio/jack: must be set to the system buffer size.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:wavDeviceType / blocksize
Namespace No namespace
Annotations
 
Applies to the block size that is used in the internal apex audio streams (for filters etc.).
Larger sizes are more efficient, smaller sizes have smaller latencies. If not defined, the soundcard buffersize will be used.
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
Source
 
<xs:element name="blocksize" minOccurs="0" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Applies to the block size that is used in the internal apex audio streams (for filters etc.). Larger sizes are more efficient, smaller sizes have smaller latencies. If not defined, the soundcard buffersize will be used.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:wavDeviceType / buffersize_apex
Namespace No namespace
Annotations
 
Size of internal apex sound buffer in seconds. This buffer ensures that no buffer
underruns occur. The default value is 1s. If continuous filters are used, the system will need
this amount of seconds before the next stimulus can be output.
Note that the value in seconds is rounded down to the nearest multiple of 8192 samples
(the buffersize used to fill the buffer):
so using 1 second here, with a samplerate of 44100, the actual amount of time will be
40960 samples / 44100 samples/sec = 0.9 seconds.
    If a buffersize smaller than 16384 samples is specified, a buffer of 16384 samples
    will be used.
Diagram
Diagram
Type restriction of xs:decimal
Properties
content simple
minOccurs 0
Facets
maxInclusive 60
minExclusive 0
Source
 
<xs:element name="buffersize_apex" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Size of internal apex sound buffer in seconds. This buffer ensures that no buffer underruns occur. The default value is 1s. If continuous filters are used, the system will need this amount of seconds before the next stimulus can be output. Note that the value in seconds is rounded down to the nearest multiple of 8192 samples (the buffersize used to fill the buffer): so using 1 second here, with a samplerate of 44100, the actual amount of time will be 40960 samples / 44100 samples/sec = 0.9 seconds. If a buffersize smaller than 16384 samples is specified, a buffer of 16384 samples will be used.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:decimal">
      <xs:minExclusive value="0"/>
      <xs:maxInclusive value="60"/>
    </xs:restriction>
  </xs:simpleType>
  <!--xs:simpleType>
                        <xs:restriction base="xs:string">
                          <xs:enumeration value="0.5"/>
                          <xs:enumeration value="1"/>
                          <xs:enumeration value="1.5"/>
                          <xs:enumeration value="2"/>
                          <xs:enumeration value="3"/>
                          <xs:enumeration value="4"/>
                          <xs:enumeration value="5"/>
                          <xs:enumeration value="10"/>
                        </xs:restriction>
                      </xs:simpleType-->
</xs:element>
[ top ]
Element apex:wavDeviceType / padzero
Namespace No namespace
Annotations
 
If smaller than 16: add padzero*8196 samples to the end of each stream. If larger than 16: add padzero samples to the end of each stream. 
This avoids dropping of the last N frames on some soundcards (notoriously LynxOne and FirefaceUC)
Diagram
Diagram
Type xs:nonNegativeInteger
Properties
content simple
minOccurs 0
Source
 
<xs:element name="padzero" type="xs:nonNegativeInteger" minOccurs="0">
  <xs:annotation>
    <xs:documentation>If smaller than 16: add padzero*8196 samples to the end of each stream. If larger than 16: add padzero samples to the end of each stream. This avoids dropping of the last N frames on some soundcards (notoriously LynxOne and FirefaceUC)</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:wavDeviceType / cisim
Namespace No namespace
Annotations
 
Parameters for automatic CI
simulation
Diagram
Diagram experiment.tmp#cisimType_number_electrodes experiment.tmp#cisimType_pulserate experiment.tmp#cisimType_noiseband experiment.tmp#cisimType
Type apex:cisimType
Properties
content complex
minOccurs 0
Model
Children noiseband, number_electrodes, pulserate
Instance
 
<cisim>
  <number_electrodes>{1,1}</number_electrodes>
  <pulserate>{1,1}</pulserate>
  <noiseband electrode="">{1,unbounded}</noiseband>
</cisim>
Source
 
<xs:element name="cisim" type="apex:cisimType" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Parameters for automatic CI simulation</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:cisimType / number_electrodes
Namespace No namespace
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
Source
 
<xs:element name="number_electrodes" type="xs:positiveInteger"/>
[ top ]
Element apex:cisimType / pulserate
Namespace No namespace
Diagram
Diagram
Type xs:integer
Properties
content simple
Source
 
<xs:element name="pulserate" type="xs:integer"/>
[ top ]
Element apex:cisimType / noiseband
Namespace No namespace
Diagram
Diagram experiment.tmp#cisimType_cisimType_noiseband_electrode
Type extension of xs:IDREF
Properties
content complex
minOccurs 1
maxOccurs unbounded
Attributes
QName Type Use
electrode xs:positiveInteger optional
Source
 
<xs:element name="noiseband" minOccurs="1" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:IDREF">
        <xs:attribute name="electrode" type="xs:positiveInteger"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:pluginController / plugin
Namespace No namespace
Diagram
Diagram
Type xs:anyURI
Properties
content simple
Source
 
<xs:element name="plugin" type="xs:anyURI"/>
[ top ]
Element apex:pluginController / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#pluginController_pluginController_parameter_name experiment.tmp#pluginController_pluginController_parameter_channel
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
Attributes
QName Type Use
channel xs:nonNegativeInteger optional
id xs:ID optional
name xs:Name required
Source
 
<xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attributeGroup ref="apex:filterParam"/>
        <xs:attribute name="name" type="xs:Name" use="required"/>
        <xs:attribute name="channel" type="xs:nonNegativeInteger" use="optional"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:CohDeviceType / device
Namespace No namespace
Annotations
 
Device identifier. For NIC 2, this identifier consists of three parts: the device type (e.g. l34) , the implant type (e.g. cic3, cic4) and the device number (e.g. 1, ordered according to the assigned COM port, device 0 is a simulated device).
Diagram
Diagram
Type xs:string
Properties
content simple
Source
 
<xs:element name="device" type="xs:string">
  <xs:annotation>
    <xs:documentation>Device identifier. For NIC 2, this identifier consists of three parts: the device type (e.g. l34) , the implant type (e.g. cic3, cic4) and the device number (e.g. 1, ordered according to the assigned COM port, device 0 is a simulated device).</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:CohDeviceType / trigger
Namespace No namespace
Annotations
 
Generate or use a trigger from the audio port.
Currently the trigger button status is not checked (nicv2 doesn't
allow this yet)
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration in
enumeration out
enumeration none
Source
 
<xs:element name="trigger">
  <xs:annotation>
    <xs:documentation>Generate or use a trigger from the audio port. Currently the trigger button status is not checked (nicv2 doesn't allow this yet)</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="in"/>
      <xs:enumeration value="out"/>
      <xs:enumeration value="none"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:CohDeviceType / powerup_count
Namespace No namespace
Annotations
 
Number of powerup pulses to send.
No powerup pulses will be sent if this is set
to 0.
Diagram
Diagram
Type xs:nonNegativeInteger
Properties
content simple
minOccurs 0
default 4000
Source
 
<xs:element name="powerup_count" minOccurs="0" default="4000" type="xs:nonNegativeInteger">
  <xs:annotation>
    <xs:documentation>Number of powerup pulses to send. No powerup pulses will be sent if this is set to 0.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:CohDeviceType / volume
Namespace No namespace
Diagram
Diagram experiment.tmp#volumeParam experiment.tmp#filterParam
Type extension of apex:volumeParam
Type hierarchy
Properties
content complex
minOccurs 0
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="volume" minOccurs="0">
  <xs:complexType>
    <xs:annotation>
      <xs:documentation>Volume parameter for Cochlear device. The current level (in clinical units) is calculated according the following formula: round(t + (c-t) * volume/100 * mag) Where: t=treshold level c=comfort level volume=current value of volume parameter mag=magnitude [0,1]</xs:documentation>
    </xs:annotation>
    <xs:simpleContent>
      <xs:extension base="apex:volumeParam">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:CohDeviceType / defaultmap
Namespace No namespace
Annotations
 
Defines the default subject map to be
used
Diagram
Diagram experiment.tmp#CohDeviceType_CohDeviceType_defaultmap_inline experiment.tmp#CohDeviceType_CohDeviceType_defaultmap_from_r126
Properties
content complex
Model
Children from_r126, inline
Instance
 
<defaultmap>
  <inline id="">{1,1}</inline>
  <from_r126>{1,1}</from_r126>
</defaultmap>
Source
 
<xs:element name="defaultmap">
  <xs:annotation>
    <xs:documentation>Defines the default subject map to be used</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:choice>
      <xs:element name="inline" type="apex:CohMap">
        <xs:annotation>
          <xs:documentation>The map is defined below</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="from_r126">
        <xs:annotation>
          <xs:documentation>The user can select the map from the R126 wizard. R126 is the clinical fitting software.</xs:documentation>
        </xs:annotation>
      </xs:element>
    </xs:choice>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:CohDeviceType / defaultmap / inline
Namespace No namespace
Annotations
 
The map is defined
below
Diagram
Diagram experiment.tmp#CohMap_id experiment.tmp#CohMap_number_electrodes experiment.tmp#CohMap_mode experiment.tmp#CohMap_pulsewidth experiment.tmp#CohMap_pulsegap experiment.tmp#CohMap_period experiment.tmp#CohMap_trigger experiment.tmp#CohMap_channel experiment.tmp#CohMap
Type apex:CohMap
Properties
content complex
Model
Children channel, mode, number_electrodes, period, pulsegap, pulsewidth, trigger
Instance
 
<inline id="">
  <number_electrodes>{1,1}</number_electrodes>
  <mode>{1,1}</mode>
  <pulsewidth>{1,1}</pulsewidth>
  <pulsegap>{1,1}</pulsegap>
  <period>{1,1}</period>
  <trigger>{0,1}</trigger>
  <channel comfort="" electrode="" number="" threshold="">{1,22}</channel>
</inline>
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="inline" type="apex:CohMap">
  <xs:annotation>
    <xs:documentation>The map is defined below</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:CohMap / number_electrodes
Namespace No namespace
Diagram
Diagram
Type restriction of xs:positiveInteger
Properties
content simple
Facets
maxInclusive 22
Source
 
<xs:element name="number_electrodes">
  <xs:simpleType>
    <xs:restriction base="xs:positiveInteger">
      <xs:maxInclusive value="22"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:CohMap / mode
Namespace No namespace
Annotations
 
Stimulation mode; bipolar modes use a lower, reverse
bipolar modes a higher reference electrode.
Diagram
Diagram experiment.tmp#CohModeEnum
Type apex:CohModeEnum
Properties
content simple
Facets
enumeration MP1+2
enumeration MP1
enumeration MP2
enumeration BP
enumeration BP+1
enumeration BP+2
enumeration BP+3
enumeration BP+4
enumeration BP+5
enumeration BP+6
enumeration BP+7
enumeration BP+8
enumeration BP+9
enumeration BP+10
enumeration RBP
enumeration RBP+1
enumeration RBP+2
enumeration RBP+3
enumeration RBP+4
enumeration RBP+5
enumeration RBP+6
enumeration RBP+7
enumeration RBP+8
enumeration RBP+9
enumeration RBP+10
Source
 
<xs:element name="mode" type="apex:CohModeEnum">
  <xs:annotation>
    <xs:documentation>Stimulation mode; bipolar modes use a lower, reverse bipolar modes a higher reference electrode.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:CohMap / pulsewidth
Namespace No namespace
Annotations
 
When using a Freedom processor, the maximum phasewidth is 429.8us
When using an L34 processor, the maximum phasewidth is 434.4us
Diagram
Diagram
Type restriction of xs:double
Properties
content simple
Facets
maxInclusive 434.4
minInclusive 25
Source
 
<xs:element name="pulsewidth">
  <xs:annotation>
    <xs:documentation>When using a Freedom processor, the maximum phasewidth is 429.8us When using an L34 processor, the maximum phasewidth is 434.4us</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:double">
      <xs:minInclusive value="25"/>
      <xs:maxInclusive value="434.4"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:CohMap / pulsegap
Namespace No namespace
Annotations
 
When using a Freedom processor, the maximum phase gap is 57us
When using an L34 processor, the maximum phase gap is 58us
When using a cic3 implant, the minimum phase gap is 8us
When using a cic4 implant, the minimum phase gap is 7us
Diagram
Diagram
Type restriction of xs:double
Properties
content simple
Facets
maxInclusive 58
minInclusive 7
Source
 
<xs:element name="pulsegap">
  <xs:annotation>
    <xs:documentation>When using a Freedom processor, the maximum phase gap is 57us When using an L34 processor, the maximum phase gap is 58us When using a cic3 implant, the minimum phase gap is 8us When using a cic4 implant, the minimum phase gap is 7us</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:double">
      <xs:minInclusive value="7"/>
      <xs:maxInclusive value="58"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:CohMap / period
Namespace No namespace
Annotations
 
When using a Freedom processor, the maximum period is 13078us
When using an L34 processor, the maximum period is 13107us
When using a cic3 implant, the minimum period is 70us
When using a cic4 implant, the minimum period is 64.6us
Diagram
Diagram
Type restriction of xs:double
Properties
content simple
Facets
maxInclusive 13107
minInclusive 64.6
Source
 
<xs:element name="period">
  <xs:annotation>
    <xs:documentation>When using a Freedom processor, the maximum period is 13078us When using an L34 processor, the maximum period is 13107us When using a cic3 implant, the minimum period is 70us When using a cic4 implant, the minimum period is 64.6us</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:double">
      <xs:minInclusive value="64.6"/>
      <xs:maxInclusive value="13107"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:CohMap / trigger
Namespace No namespace
Annotations
 
"all" will result in all pulses having triggers.
 "none" will result in no pulses having triggers.
"first" will result in the first pulses that needs mapping to have a trigger,
 the ones afterward will have no trigger.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
default none
Facets
enumeration all
enumeration none
enumeration first
Source
 
<xs:element name="trigger" minOccurs="0" default="none">
  <xs:annotation>
    <xs:documentation>"all" will result in all pulses having triggers. "none" will result in no pulses having triggers. "first" will result in the first pulses that needs mapping to have a trigger, the ones afterward will have no trigger.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="all"/>
      <xs:enumeration value="none"/>
      <xs:enumeration value="first"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:CohMap / channel
Namespace No namespace
Diagram
Diagram experiment.tmp#CohMap_CohMap_channel_number experiment.tmp#CohMap_CohMap_channel_electrode experiment.tmp#CohMap_CohMap_channel_threshold experiment.tmp#CohMap_CohMap_channel_comfort
Properties
content complex
minOccurs 1
maxOccurs 22
Attributes
QName Type Use
comfort restriction of xs:nonNegativeInteger required
electrode restriction of xs:positiveInteger required
number restriction of xs:positiveInteger required
threshold restriction of xs:nonNegativeInteger required
Source
 
<xs:element name="channel" minOccurs="1" maxOccurs="22">
  <xs:complexType>
    <xs:attribute name="number" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:positiveInteger">
          <xs:maxInclusive value="22"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="electrode" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:positiveInteger">
          <xs:maxInclusive value="22"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="threshold" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:nonNegativeInteger">
          <xs:maxInclusive value="255"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
    <xs:attribute name="comfort" use="required">
      <xs:simpleType>
        <xs:restriction base="xs:nonNegativeInteger">
          <xs:maxInclusive value="255"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:attribute>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:CohDeviceType / defaultmap / from_r126
Namespace No namespace
Annotations
 
The user can select the map from the R126
    wizard. R126 is the clinical fitting
software.
Diagram
Diagram
Source
 
<xs:element name="from_r126">
  <xs:annotation>
    <xs:documentation>The user can select the map from the R126 wizard. R126 is the clinical fitting software.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generator / type
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
Facets
enumeration noise 
White noise (this is NOT gaussian
noise)
enumeration sinus 
Sinus with peak amplitude = total
gain
enumeration singlepulse 
Single pulse with peak amplitude = total
gain. The polarity is set using the "polarity"
parameter.
Source
 
<xs:element name="type">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="noise">
        <xs:annotation>
          <xs:documentation>White noise (this is NOT gaussian noise)</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <!--xs:enumeration value="square">
                                    <xs:annotation>
                                    <xs:documentation>Square wave with peak amplitude = total
                                    gain</xs:documentation>
                                    </xs:annotation>
                                    </xs:enumeration-->
      <xs:enumeration value="sinus">
        <xs:annotation>
          <xs:documentation>Sinus with peak amplitude = total gain</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <!--xs:enumeration value="triangle">
                                    <xs:annotation>
                                    <xs:documentation>Triangle with peak amplitude = total
                                    gain</xs:documentation>
                                    </xs:annotation>
                                    </xs:enumeration-->
      <xs:enumeration value="singlepulse">
        <xs:annotation>
          <xs:documentation>Single pulse with peak amplitude = total gain. The polarity is set using the "polarity" parameter.</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:generator / basegain
Namespace No namespace
Annotations
 
The total gain is basegain+gain. Basegain is useful
for amplitude normalization between different
blocks
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="basegain" type="xs:double" default="0" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The total gain is basegain+gain. Basegain is useful for amplitude normalization between different blocks</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generator / invertgain
Namespace No namespace
Annotations
 
Inverts the gain of the block (but not the basegain).
Invertgain is useful for the attenuation of noise depending on an 
SNR
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="invertgain" type="xs:boolean" default="false" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Inverts the gain of the block (but not the basegain). Invertgain is useful for the attenuation of noise depending on an SNR</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generator / gain
Namespace No namespace
Annotations
 
The total gain is basegain+gain. Gain is a parameter
that can be changed by other modules
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#gainparam
Type apex:gainparam
Properties
content complex
default 0
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="gain" default="0" type="apex:gainparam">
  <xs:annotation>
    <xs:documentation>The total gain is basegain+gain. Gain is a parameter that can be changed by other modules</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generator / frequency
Namespace No namespace
Annotations
 
Frequency: only makes sense for sinus, square and
triangle
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:nonNegativeInteger
Properties
content complex
default 1000
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="frequency" default="1000">
  <xs:annotation>
    <xs:documentation>Frequency: only makes sense for sinus, square and triangle</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:nonNegativeInteger">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:generator / phase
Namespace No namespace
Annotations
 
Phase (rad): only makes sense for sinus, square and
triangle
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:double
Properties
content complex
default 0
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="phase" default="0">
  <xs:annotation>
    <xs:documentation>Phase (rad): only makes sense for sinus, square and triangle</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:double">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:generator / pulsewidth
Namespace No namespace
Annotations
 
Pulse width in samples. Currently only used for single pulse generator
Diagram
Diagram
Type xs:positiveInteger
Properties
content simple
minOccurs 0
default 1
Source
 
<xs:element name="pulsewidth" default="1" type="xs:positiveInteger" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Pulse width in samples. Currently only used for single pulse generator</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:generator / polarity
Namespace No namespace
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
minOccurs 0
default positive
Facets
enumeration positive
enumeration negative
Source
 
<xs:element name="polarity" minOccurs="0" default="positive">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="positive"/>
      <xs:enumeration value="negative"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:amplifier / basegain
Namespace No namespace
Annotations
 
The total gain is basegain+gain. Basegain is useful
for amplitude normalization between different
blocks
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#gainparam
Type apex:gainparam
Properties
content complex
minOccurs 0
default 0
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="basegain" type="apex:gainparam" default="0" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The total gain is basegain+gain. Basegain is useful for amplitude normalization between different blocks</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:amplifier / invertgain
Namespace No namespace
Annotations
 
Inverts the gain of the block (but not the basegain).
Invertgain is useful for the attenuation of noise depending on an 
SNR
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="invertgain" type="xs:boolean" default="false" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Inverts the gain of the block (but not the basegain). Invertgain is useful for the attenuation of noise depending on an SNR</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:amplifier / gain
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#gainparam experiment.tmp#channelGainType_channel experiment.tmp#channelGainType
Type apex:channelGainType
Type hierarchy
Properties
content complex
minOccurs 1
maxOccurs unbounded
Attributes
QName Type Use Annotation
channel xs:nonNegativeInteger optional 
Used to specify a single channel to apply gain to,
instead of applying it to all channels at once.
For example, for an amplifier having two channels, these are set independently by using <gain id="ch0" channel="0">-3.00</gain>
<gain id="ch1" channel="1">-6.00</gain> Channels are zero based, ie the first channel is 0, the
second 1 and so on.
id xs:ID optional
Source
 
<xs:element name="gain" minOccurs="1" maxOccurs="unbounded" type="apex:channelGainType">
</xs:element>
[ top ]
Element apex:fader / length
Namespace No namespace
Annotations
 
Fade length in mSec.
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:double
Properties
content complex
default 0
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="length" default="0">
  <xs:annotation>
    <xs:documentation>Fade length in mSec.</xs:documentation>
  </xs:annotation>
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:double">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:fader / type
Namespace No namespace
Annotations
 
Fader type: linear or cosine shaped.
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
default cosine
Facets
enumeration linear
enumeration cosine
Source
 
<xs:element name="type" default="cosine">
  <xs:annotation>
    <xs:documentation>Fader type: linear or cosine shaped.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="linear"/>
      <xs:enumeration value="cosine"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:fader / direction
Namespace No namespace
Annotations
 
Fader direction: fadein (beginning of stimulus) or
fadeout(end of stimulus)
Diagram
Diagram
Type restriction of xs:string
Properties
content simple
default in
Facets
enumeration in
enumeration out
Source
 
<xs:element name="direction" default="in">
  <xs:annotation>
    <xs:documentation>Fader direction: fadein (beginning of stimulus) or fadeout(end of stimulus)</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="in"/>
      <xs:enumeration value="out"/>
    </xs:restriction>
  </xs:simpleType>
</xs:element>
[ top ]
Element apex:dataloop / datablock
Namespace No namespace
Diagram
Diagram
Type xs:IDREF
Properties
content simple
Source
 
<xs:element name="datablock" type="xs:IDREF"/>
[ top ]
Element apex:dataloop / basegain
Namespace No namespace
Annotations
 
The total gain is basegain+gain. Basegain is useful
for amplitude normalization between different
blocks
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="basegain" type="xs:double" default="0" minOccurs="0">
  <xs:annotation>
    <xs:documentation>The total gain is basegain+gain. Basegain is useful for amplitude normalization between different blocks</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:dataloop / invertgain
Namespace No namespace
Annotations
 
Inverts the gain of the block (but not the basegain).
Invertgain is useful for the attenuation of noise depending on an 
SNR
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="invertgain" type="xs:boolean" default="false" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Inverts the gain of the block (but not the basegain). Invertgain is useful for the attenuation of noise depending on an SNR</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:dataloop / gain
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#gainparam
Type apex:gainparam
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="gain" type="apex:gainparam"/>
[ top ]
Element apex:dataloop / randomjump
Namespace No namespace
Annotations
 
Jump to a random place in the datablock upon
start. Only functional if randomjump=false
Diagram
Diagram
Type xs:boolean
Properties
content simple
minOccurs 0
default false
Source
 
<xs:element name="randomjump" type="xs:boolean" default="false" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Jump to a random place in the datablock upon start. Only functional if randomjump=false</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:dataloop / jump
Namespace No namespace
Annotations
 
Jump to a fixed place in the datablock when the 
generator is started. The place is specified in seconds. Take care that 
you do not jump further than the length of the wave file.
Diagram
Diagram
Type xs:double
Properties
content simple
minOccurs 0
default 0
Source
 
<xs:element name="jump" type="xs:double" default="0" minOccurs="0">
  <xs:annotation>
    <xs:documentation>Jump to a fixed place in the datablock when the generator is started. The place is specified in seconds. Take care that you do not jump further than the length of the wave file.</xs:documentation>
  </xs:annotation>
</xs:element>
[ top ]
Element apex:hrtffiltersum / anglespeech
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:integer
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="anglespeech">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:integer">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:hrtffiltersum / anglenoise
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:integer
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="anglenoise">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:integer">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:hrtffiltersum / snr
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:integer
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="snr">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:integer">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:hrtffiltersum / speechfile
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:integer
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="speechfile">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:integer">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:hrtffiltersum / noisefile
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:integer
Properties
content complex
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:element name="noisefile">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:integer">
        <xs:attributeGroup ref="apex:filterParam"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Element apex:pluginfilter / plugin
Namespace No namespace
Diagram
Diagram
Type xs:anyURI
Properties
content simple
Source
 
<xs:element name="plugin" type="xs:anyURI"/>
[ top ]
Element apex:pluginfilter / parameter
Namespace No namespace
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#pluginfilter_pluginfilter_parameter_name experiment.tmp#pluginfilter_pluginfilter_parameter_channel
Type extension of xs:string
Properties
content complex
minOccurs 0
maxOccurs unbounded
default
Attributes
QName Type Use
channel xs:nonNegativeInteger optional
id xs:ID optional
name xs:Name required
Source
 
<xs:element name="parameter" default="" minOccurs="0" maxOccurs="unbounded">
  <xs:complexType>
    <xs:simpleContent>
      <xs:extension base="xs:string">
        <xs:attributeGroup ref="apex:filterParam"/>
        <xs:attribute name="name" type="xs:Name" use="required"/>
        <xs:attribute name="channel" type="xs:nonNegativeInteger" use="optional"/>
      </xs:extension>
    </xs:simpleContent>
  </xs:complexType>
</xs:element>
[ top ]
Complex Type apex:procedureType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.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:screensType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#screensType_prefix experiment.tmp#screensType_general experiment.tmp#screensType_reinforcement experiment.tmp#screensType_style_apex experiment.tmp#screensType_style experiment.tmp#screensType_childmode experiment.tmp#screensType_defaultFont experiment.tmp#screensType_defaultFontsize experiment.tmp#screensType_screen experiment.tmp#screensType_pluginscreens
Used by
Model
Children childmode, defaultFont, defaultFontsize, general, pluginscreens, prefix, reinforcement, screen, style, style_apex
Source
 
<xs:complexType name="screensType">
  <xs:sequence>
    <xs:element name="prefix" type="apex:prefixType" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Defines a prefix for the filenames of media files used in the screens below. The prefix is concatenated in the front of the filenames given below before trying to open any file.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="general" type="apex:screenGeneralType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Some general properties of the entire Apex window are set in this section. They are applied for each particular screen defined below.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="reinforcement" type="apex:reinforcementType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Defines what kind of feedback about the procedure and correctness of answers is shown to the user. This is valid for the whole experiment.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="style_apex" type="apex:stylesheetType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Style that is to be applied to the whole of apex</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="style" type="apex:stylesheetType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Style that is to be applied to all screens</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="childmode" type="apex:childmodeType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Defines the elements used in child mode.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="defaultFont" type="xs:string" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Name of the default font to be used for all elements of every screen. Possible names: any font found by QFontDialog</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="defaultFontsize" type="xs:positiveInteger" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Size of the default font to be used for all elements of every screen. Unit: points as defined by the system</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="screen" type="apex:screenType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Every single screen defines a screen with a certain ID to be used elsewhere in the experiment file.</xs:documentation>
      </xs:annotation>
      <!--   As the following does not work, it it implemented per layout
                -->
      <!--xs:unique name="screenIDs">
                    <xs:selector xpath="./*[not(name()='buttongroup')]//*"></xs:selector>
                    <xs:field xpath="@id"></xs:field>
                    </xs:unique-->
    </xs:element>
    <xs:element name="pluginscreens" type="apex:pluginScreenType" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:prefixType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
A prefix can be specified inline (ie: here) or by specifying the ID of a prefix in the main configfile. 
Example:
Absolute:     c:/program files/bla
Relative:     ../stimuli
Diagram
Diagram experiment.tmp#prefixType_source
Type extension of xs:string
Used by
Attributes
QName Type Default Use
source restriction of xs:string inline optional
Source
 
<xs:complexType name="prefixType">
  <xs:annotation>
    <xs:documentation>A prefix can be specified inline (ie: here) or by specifying the ID of a prefix in the main configfile. Example: Absolute: c:/program files/bla Relative: ../stimuli</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="xs:string">
      <xs:attribute name="source" default="inline">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="inline">
              <xs:annotation>
                <xs:documentation>The prefix will be specified in this element</xs:documentation>
              </xs:annotation>
            </xs:enumeration>
            <xs:enumeration value="apexconfig">
              <xs:annotation>
                <xs:documentation>The prefix will be loaded from the apexconfig.xml file</xs:documentation>
              </xs:annotation>
            </xs:enumeration>
          </xs:restriction>
        </xs:simpleType>
      </xs:attribute>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:screenGeneralType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#screenGeneralType_stopbutton experiment.tmp#screenGeneralType_repeatbutton experiment.tmp#screenGeneralType_statuspicture experiment.tmp#screenGeneralType_showpanel experiment.tmp#screenGeneralType_showmenu experiment.tmp#screenGeneralType_fullscreen experiment.tmp#screenGeneralType_intertrialscreen
Used by
Model
Children fullscreen, intertrialscreen, repeatbutton, showmenu, showpanel, statuspicture, stopbutton
Source
 
<xs:complexType name="screenGeneralType">
  <xs:sequence>
    <xs:element name="stopbutton" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Show a red panic button that immediately stops all output when clicked.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="repeatbutton" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Show a repeat button that will repeat the last stimulus.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="statuspicture" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Show a status picture that indicates whether the user should be listening or giving an answer</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="showpanel" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Show the panel; in case of childmode: a movie if defined</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="showmenu" type="xs:boolean" minOccurs="0" default="true">
      <xs:annotation>
        <xs:documentation>Determined whether the apex main menu (containing File, Calibration, etc.) is shown</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="fullscreen" type="xs:boolean" minOccurs="0" default="false">
      <xs:annotation>
        <xs:documentation>If true, the main apex window will be shown full-screen, without window title or taskbar or whatever</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="intertrialscreen" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>A screen to show in between trials (after feedback that is)</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:IDREF">
            <xs:attribute name="length" type="xs:positiveInteger">
              <xs:annotation>
                <xs:documentation>The period to show the screen</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:reinforcementType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#reinforcementType_progressbar experiment.tmp#reinforcementType_feedback experiment.tmp#reinforcementType_feedback_on experiment.tmp#reinforcementType_feedback_picture_positive experiment.tmp#reinforcementType_feedback_picture_negative experiment.tmp#reinforcementType_showcurrent experiment.tmp#reinforcementType_feedbackplugin
Used by
Model
Children feedback, feedback_on, feedback_picture_negative, feedback_picture_positive, feedbackplugin, progressbar, showcurrent
Source
 
<xs:complexType name="reinforcementType">
  <xs:sequence>
    <xs:element name="progressbar" type="xs:boolean">
      <xs:annotation>
        <xs:documentation>Show a progress bar in the right hand panel, indicating the experiment progress. Not functional for multiprocedure or trainingprocedure.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="feedback">
      <xs:annotation>
        <xs:documentation>Show visual feedback according to the correctness of the last answer. Feedback is shown using an upward or downward pointing thumb in the right hand panel.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:boolean">
            <xs:attribute name="length" type="xs:nonNegativeInteger" default="1000">
              <xs:annotation>
                <xs:documentation>Length of the feedback in ms. If feedback is false but a length is present, the specified time will be the time between two trials.</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="feedback_on" minOccurs="0" default="correct">
      <xs:annotation>
        <xs:documentation>If feedback is shown, it is shown as a picture in the panel, but a screen element can also be highlighted.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="none">
            <xs:annotation>
              <xs:documentation>Do not highlight any screenelement</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="correct">
            <xs:annotation>
              <xs:documentation>Highlight the correct screenelement</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="clicked">
            <xs:annotation>
              <xs:documentation>Highlight the clicked screenelement (the subject answer)</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="feedback_picture_positive" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Picture to be shown in the panel on positive feedback.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="feedback_picture_negative" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Picture to be shown in the panel on negateive feedback.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="showcurrent" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Show a border around the screen element corresponding to the currently playing stimulus.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="feedbackplugin" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>
        </xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="parameter" default="" minOccurs="0" maxOccurs="unbounded">
            <xs:annotation>
              <xs:documentation>Parameter to be passed to the plugin</xs:documentation>
            </xs:annotation>
            <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="name" type="xs:string" use="required">
          <xs:annotation>
            <xs:documentation>Name of the plugin to be loaded</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Simple Type apex:stylesheetType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Any stylesheet supoprted by Qt (google for "qt style sheet")
Warning: if you request changed not supported by the native style engine, we switch to the 
Qt style engine, possibly resulting in other changes in layout.
Diagram
Diagram
Type xs:string
Used by
Source
 
<xs:simpleType name="stylesheetType">
  <xs:annotation>
    <xs:documentation>Any stylesheet supoprted by Qt (google for "qt style sheet") Warning: if you request changed not supported by the native style engine, we switch to the Qt style engine, possibly resulting in other changes in layout.</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string"/>
</xs:simpleType>
[ top ]
Complex Type apex:childmodeType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#childmodeType_intro experiment.tmp#childmodeType_outro experiment.tmp#childmodeType_panel
Used by
Model
Children intro, outro, panel
Source
 
<xs:complexType name="childmodeType">
  <xs:sequence>
    <xs:element name="intro" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The screen to show as intro before the experiment starts</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:IDREF">
            <xs:attribute name="length" type="xs:nonNegativeInteger">
              <xs:annotation>
                <xs:documentation>Length of the movie in ms, if not specified, the system will wait for the movie to end and then continue.</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="outro" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The screen to show as outro after the experiment has finished</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:IDREF">
            <xs:attribute name="length" type="xs:nonNegativeInteger">
              <xs:annotation>
                <xs:documentation>Length of the movie in ms</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="panel" type="xs:anyURI" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The panel reinforcement movie to use</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:screenType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#screenType_id experiment.tmp#screenType_description experiment.tmp#screenType_hLayout experiment.tmp#screenType_vLayout experiment.tmp#screenType_gridLayout experiment.tmp#screenType_twoPartLayout experiment.tmp#screenType_arcLayout experiment.tmp#screenType_buttongroup experiment.tmp#screenType_default_answer_element
Used by
Model
Children arcLayout, buttongroup, default_answer_element, gridLayout, hLayout, twoPartLayout, vLayout
Attributes
QName Type Use Annotation
description xs:string optional 
Description of the screen - for your own reference
id xs:ID required
Source
 
<xs:complexType name="screenType">
  <xs:sequence>
    <xs:choice maxOccurs="1">
      <xs:element name="hLayout" type="apex:hScreenLayoutType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Horizontal layout: places elements next to each other</xs:documentation>
        </xs:annotation>
        <xs:unique name="screenId_hLayout">
          <xs:selector xpath="./*"/>
          <xs:field xpath="@id"/>
        </xs:unique>
      </xs:element>
      <xs:element name="vLayout" type="apex:vScreenLayoutType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Vertical layout: places elements above each other</xs:documentation>
        </xs:annotation>
        <xs:unique name="screenId_vLayout">
          <xs:selector xpath="./*"/>
          <xs:field xpath="@id"/>
        </xs:unique>
      </xs:element>
      <xs:element name="gridLayout" type="apex:gridScreenLayoutType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Gridlayout: places elements in an (irregular) grid.</xs:documentation>
        </xs:annotation>
        <xs:unique name="screenId_gridLayout">
          <xs:selector xpath="./*"/>
          <xs:field xpath="@id"/>
        </xs:unique>
      </xs:element>
      <xs:element name="twoPartLayout" type="apex:twoPartLayoutType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Layout with a small upper part and larger lower part</xs:documentation>
        </xs:annotation>
        <xs:unique name="screenId_twoPartLayout">
          <xs:selector xpath="./*"/>
          <xs:field xpath="@id"/>
        </xs:unique>
      </xs:element>
      <xs:element name="arcLayout" type="apex:arcScreenLayoutType" minOccurs="0">
        <xs:annotation>
          <xs:documentation>Arc layout: places elements in a semi-circle. Useful for localization experiments.</xs:documentation>
        </xs:annotation>
        <xs:unique name="screenId_arcLayout">
          <xs:selector xpath="./*"/>
          <xs:field xpath="@id"/>
        </xs:unique>
      </xs:element>
    </xs:choice>
    <xs:element name="buttongroup" type="apex:buttonGroupType" minOccurs="0" maxOccurs="1"/>
    <xs:element name="default_answer_element" type="xs:Name" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Default element for getting the user input to send to the corrector.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
  <xs:attribute name="description" type="xs:string" use="optional">
    <xs:annotation>
      <xs:documentation>Description of the screen - for your own reference</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:complexType>
[ top ]
Complex Type apex:hScreenLayoutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Horizontal layout: places elements next to each
other
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#hScreenLayoutType_width experiment.tmp#gridElementAttributes
Type extension of apex:screenLayoutType
Type hierarchy
Used by
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="hScreenLayoutType">
  <xs:annotation>
    <xs:documentation>Horizontal layout: places elements next to each other</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenLayoutType">
      <xs:attribute name="width" type="xs:int" use="required">
      </xs:attribute>
      <!--xs:attribute name="id" type="xs:Name" use="optional"></xs:attribute-->
      <xs:attributeGroup ref="apex:gridElementAttributes"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenLayoutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Base type for all layout types
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup
Properties
abstract true
Used by
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Attributes
QName Type Use
id xs:Name optional
Source
 
<xs:complexType name="screenLayoutType" abstract="true">
  <xs:annotation>
    <xs:documentation>Base type for all layout types</xs:documentation>
  </xs:annotation>
  <xs:choice maxOccurs="unbounded">
    <xs:group ref="apex:layoutElementGroup">
    </xs:group>
    <xs:group ref="apex:screenElementGroup">
    </xs:group>
  </xs:choice>
  <xs:attribute name="id" type="xs:Name" use="optional"/>
</xs:complexType>
[ top ]
Complex Type apex:screenButtonType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Button element. Can be clicked. If button is clicked, the subject is
assumed to have responded to the trial.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenButtonType_text
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, text, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenButtonType">
  <xs:annotation>
    <xs:documentation>Button element. Can be clicked. If button is clicked, the subject is assumed to have responded to the trial.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="text" type="xs:string">
          <xs:annotation>
            <xs:documentation>Text to be printed on the button</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenElementType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Base element for all screen elements
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled
Properties
abstract true
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenElementType" abstract="true">
  <xs:annotation>
    <xs:documentation>Base element for all screen elements</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="style" type="apex:stylesheetType" minOccurs="0"/>
    <xs:element name="width" type="xs:nonNegativeInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>TODO: units?</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="height" type="xs:nonNegativeInteger" minOccurs="0"/>
    <xs:element name="shortcut" type="apex:shortcutType" minOccurs="0" maxOccurs="unbounded"/>
    <xs:element name="font" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>TODO: how is the font specified?</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="fontsize" type="xs:positiveInteger" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Text font size, in points as defined by the system</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="bgcolor" type="apex:colorType" minOccurs="0"/>
    <xs:element name="fgcolor" type="apex:colorType" minOccurs="0"/>
    <xs:element name="floating" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Put the element in it's own window instead of embedding it in the current layout</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="disabled" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If set to true, the element will always be disabled (can be used to "guide the eye")</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="apex:gridElementAttributes"/>
  <xs:attributeGroup ref="apex:screenIdAttribute"/>
</xs:complexType>
[ top ]
Complex Type apex:shortcutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Defines a keyboard key combination to be used as a shortcut
Diagram
Diagram experiment.tmp#shortcutBaseType experiment.tmp#shortcutType_action experiment.tmp#shortcutType_modifier experiment.tmp#shortcutType_hex
Type extension of apex:shortcutBaseType
Type hierarchy
Used by
Attributes
QName Type Default Use Annotation
action restriction of xs:string click optional
hex xs:boolean optional 
If true, parses the shortcut as a hexadecimal number. See the
Key enum in qtnamespace.h for known values
modifier restriction of xs:string optional 
Dead key to be used together with the
shortcut
Source
 
<xs:complexType name="shortcutType">
  <xs:annotation>
    <xs:documentation>Defines a keyboard key combination to be used as a shortcut</xs:documentation>
  </xs:annotation>
  <xs:simpleContent>
    <xs:extension base="apex:shortcutBaseType">
      <xs:attribute name="action" use="optional" default="click">
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="click">
              <xs:annotation>
                <xs:documentation>Has the same effect as clicking the widget</xs:documentation>
              </xs:annotation>
            </xs:enumeration>
            <xs:enumeration value="up">
              <xs:annotation>
                <xs:documentation>Has the same effect as clicking the up-button</xs:documentation>
              </xs:annotation>
            </xs:enumeration>
            <xs:enumeration value="down">
              <xs:annotation>
                <xs:documentation>Has the same effect as clicking the up-button</xs:documentation>
              </xs:annotation>
            </xs:enumeration>
          </xs:restriction>
        </xs:simpleType>
      </xs:attribute>
      <xs:attribute name="modifier">
        <xs:annotation>
          <xs:documentation>Dead key to be used together with the shortcut</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="Ctrl"/>
            <xs:enumeration value="Alt"/>
            <xs:enumeration value="Shift"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:attribute>
      <xs:attribute name="hex" type="xs:boolean">
        <xs:annotation>
          <xs:documentation>If true, parses the shortcut as a hexadecimal number. See the Key enum in qtnamespace.h for known values</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Simple Type apex:shortcutBaseType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#shortcutHex experiment.tmp#shortcutEnum experiment.tmp#shortcutRegExp
Type union of(apex:shortcutHex, apex:shortcutEnum, apex:shortcutRegExp)
Used by
Complex Type apex:shortcutType
Source
 
<xs:simpleType name="shortcutBaseType">
  <xs:union memberTypes="apex:shortcutHex apex:shortcutEnum apex:shortcutRegExp">
  </xs:union>
</xs:simpleType>
[ top ]
Simple Type apex:colorType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Define a color as accepted by Qt colorstring, can be:
* #RGB (each of R, G, and B is a single hex digit)
* #RRGGBB
* #RRRGGGBBB
* #RRRRGGGGBBBB
* a color name http://www.w3.org/TR/SVG/types.html#ColorKeywords
* transparent
Diagram
Diagram
Type xs:string
Used by
Source
 
<xs:simpleType name="colorType">
  <xs:annotation>
    <xs:documentation>Define a color as accepted by Qt colorstring, can be: * #RGB (each of R, G, and B is a single hex digit) * #RRGGBB * #RRRGGGBBB * #RRRRGGGGBBBB * a color name http://www.w3.org/TR/SVG/types.html#ColorKeywords * transparent</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string"/>
</xs:simpleType>
[ top ]
Complex Type apex:screenLabelType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Label element: simple text on the screen. Cannot be used for user input.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenLabelType_text
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, text, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenLabelType">
  <xs:annotation>
    <xs:documentation>Label element: simple text on the screen. Cannot be used for user input.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="text" type="xs:string"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenAnswerLabelType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Label containing the correct answer for the current
trial.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenAnswerLabelType">
  <xs:annotation>
    <xs:documentation>Label containing the correct answer for the current trial.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <!--xs:element name="fontsize" type="xs:positiveInteger" minOccurs="0" maxOccurs="1"/-->
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
  <!--xs:attributeGroup ref="apex:gridElementAttributes"/>
        <xs:attributeGroup ref="apex:idAttribute"/-->
</xs:complexType>
[ top ]
Complex Type apex:screenParameterLabelType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Label containing the value of a parameter.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenParameterLabelType_parameter
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, parameter, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenParameterLabelType">
  <xs:annotation>
    <xs:documentation>Label containing the value of a parameter.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <!--xs:element name="fontsize" type="xs:positiveInteger" minOccurs="0" maxOccurs="1"/-->
        <xs:element name="parameter" type="apex:showparameterType" minOccurs="1" maxOccurs="1"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
  <!--xs:attributeGroup ref="apex:gridElementAttributes"/>
            <xs:attributeGroup ref="apex:idAttribute"/-->
</xs:complexType>
[ top ]
Complex Type apex:showparameterType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#showparameterType_name experiment.tmp#showparameterType_expression
Type extension of xs:Name
Used by
Attributes
QName Type Use Annotation
expression apex:mathexpression optional 
Expression to be evaluated. Expressions must
be in the format a*x+b, where x is the parameter value and a
and b are floats
name optional 
Parameter name to show in the
list
Source
 
<xs:complexType name="showparameterType">
  <xs:simpleContent>
    <xs:extension base="xs:Name">
      <xs:attribute name="name">
        <xs:annotation>
          <xs:documentation>Parameter name to show in the list</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="expression" type="apex:mathexpression">
        <xs:annotation>
          <xs:documentation>Expression to be evaluated. Expressions must be in the format a*x+b, where x is the parameter value and a and b are floats</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Simple Type apex:mathexpression
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Simple math expression of the format a*x+b
Diagram
Diagram
Type restriction of xs:string
Facets
pattern (\-?\d*\.?\d*)\s*\*\s*x\s*([+-])\s*(\d+\.?\d*)
Used by
Source
 
<xs:simpleType name="mathexpression">
  <xs:annotation>
    <xs:documentation>Simple math expression of the format a*x+b</xs:documentation>
  </xs:annotation>
  <xs:restriction base="xs:string">
    <xs:pattern value="(\-?\d*\.?\d*)\s*\*\s*x\s*([+-])\s*(\d+\.?\d*)"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:screenTextEditType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Text box to be filled in by the user
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenTextEditType_text experiment.tmp#screenTextEditType_inputmask
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, inputmask, shortcut, style, text, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenTextEditType">
  <xs:annotation>
    <xs:documentation>Text box to be filled in by the user</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="text" type="xs:string" minOccurs="0" maxOccurs="1"/>
        <xs:element name="inputmask" type="xs:string" minOccurs="0" maxOccurs="1">
          <xs:annotation>
            <xs:documentation>Input mask to restrict what can be typed in the textbox. Defined in the Qt documentation. If inputmask=="numbers", only numeric input will be allowed. If inputmask starts with a / (slash), the remainder will be used as a regular expression for QRegExpValidator.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenPictureType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Picture to be put on the screen.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenPictureType_file experiment.tmp#screenPictureType_feedback
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, feedback, fgcolor, file, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenPictureType">
  <xs:annotation>
    <xs:documentation>Picture to be put on the screen.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="file">
          <xs:annotation>
            <xs:documentation>Filename of the picture. The format can be any of: PNG, BMP, XBM, XPM, JPEG, MNG, GIF, PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6). If path is relative, it will be prefixed with the prefix given above.</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:string">
                <xs:attribute name="id" type="xs:ID"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="feedback" type="apex:feedbackPathsType" minOccurs="0" maxOccurs="1">
          <xs:annotation>
            <xs:documentation>If used, overrides the normal feedback (using coloured borders) by drawing a different picture on screen.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:feedbackPathsType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
A screen element able to display different media depending on the state uses this to define the media.
The paths are absolute or relative, eventually prefixed by the prefix.
highlight = shown during stimulus play when 'showcurrent' is true.
positive = shown as positive feedback when feedback is true.
negative = shown as negative feedback when feedback is true.
Diagram
Diagram experiment.tmp#feedbackPathsType_highlight experiment.tmp#feedbackPathsType_positive experiment.tmp#feedbackPathsType_negative experiment.tmp#feedbackPathsType_disabled
Used by
Model
Children disabled, highlight, negative, positive
Source
 
<xs:complexType name="feedbackPathsType">
  <xs:annotation>
    <xs:documentation>A screen element able to display different media depending on the state uses this to define the media. The paths are absolute or relative, eventually prefixed by the prefix. highlight = shown during stimulus play when 'showcurrent' is true. positive = shown as positive feedback when feedback is true. negative = shown as negative feedback when feedback is true.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="highlight" type="xs:anyURI" minOccurs="0"/>
    <xs:element name="positive" type="xs:anyURI" minOccurs="0"/>
    <xs:element name="negative" type="xs:anyURI" minOccurs="0"/>
    <xs:element name="disabled" type="xs:anyURI" minOccurs="0"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:screenFlashType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenFlashType_file experiment.tmp#screenFlashType_feedback
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, feedback, fgcolor, file, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenFlashType">
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="file" type="xs:string">
          <xs:annotation>
            <xs:documentation>Flash movie to be put on the screen.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="feedback" type="apex:feedbackPathsType" minOccurs="0" maxOccurs="1">
          <xs:annotation>
            <xs:documentation>If used, overrides the normal feedback (using coloured borders) by putting a different movie on screen.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenParameterlistType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
A parameterlist shows the current value of several parameters (fixed
or variable)
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenParameterlistType_parameter
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, parameter, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenParameterlistType">
  <xs:annotation>
    <xs:documentation>A parameterlist shows the current value of several parameters (fixed or variable)</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="parameter" type="apex:showparameterType" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenPictureLabelType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Label element with a picture on it. Cannot be used for user input.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenPictureLabelType_file experiment.tmp#screenPictureLabelType_disabledfile
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, disabledfile, fgcolor, file, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenPictureLabelType">
  <xs:annotation>
    <xs:documentation>Label element with a picture on it. Cannot be used for user input.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="file" type="xs:anyURI">
          <xs:annotation>
            <xs:documentation>Filename of the picture. The format can be any of: PNG, BMP, XBM, XPM, JPEG, MNG, GIF, PBM (P1 or P4), PGM (P2 or P5), and PPM (P3 or P6). If path is relative, it will be prefixed with the prefix given above.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="disabledfile" type="xs:string" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Picture to be used if the element is disabled</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenSpinBoxType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Spin box. Can set a parameter.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenSpinBoxType_value experiment.tmp#screenSpinBoxType_min experiment.tmp#screenSpinBoxType_max experiment.tmp#screenSpinBoxType_step experiment.tmp#screenSpinBoxType_parameter experiment.tmp#screenSpinBoxType_reset
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, max, min, parameter, reset, shortcut, step, style, value, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenSpinBoxType">
  <xs:annotation>
    <xs:documentation>Spin box. Can set a parameter.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="value" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Default value</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="min" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Minimum value</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="max" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Maximum value</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="step" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Stepsize</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="parameter" type="xs:IDREF" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Parameter to be set to the value of the spinbox. This parameter will be set the NEXT trial.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="reset" type="xs:boolean" default="false" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Reset the value for every new trial</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenCheckBoxType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
CheckBox element. Can be checked. If checkbox is clicked, the subject is
assumed to have responded to the trial.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenCheckBoxType_text experiment.tmp#screenCheckBoxType_isChecked
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, isChecked, shortcut, style, text, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenCheckBoxType">
  <xs:annotation>
    <xs:documentation>CheckBox element. Can be checked. If checkbox is clicked, the subject is assumed to have responded to the trial.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="text" type="xs:string">
          <xs:annotation>
            <xs:documentation>Text to be printed right to the checkbox</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="isChecked" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Determines whether checkbox is checked by default</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenSliderType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Slider element.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenSliderType_orientation experiment.tmp#screenSliderType_min experiment.tmp#screenSliderType_max experiment.tmp#screenSliderType_value experiment.tmp#screenSliderType_tickinterval experiment.tmp#screenSliderType_stepsize experiment.tmp#screenSliderType_pagesize
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, max, min, orientation, pagesize, shortcut, stepsize, style, tickinterval, value, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenSliderType">
  <xs:annotation>
    <xs:documentation>Slider element.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="orientation" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Orientation of slider</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="horizontal"/>
              <xs:enumeration value="vertical"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="min" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Minimum value of slider</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="max" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Maximum value of slider</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="value" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Default value of slider</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="tickinterval" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Interval between slider ticks</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="stepsize" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Step size on single arrow key press</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="pagesize" type="xs:integer" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Step size of pageUp pageDown key press</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenMatrixType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Matrix of buttons of which one in each column can be selected.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenMatrixType_autocontinue experiment.tmp#screenMatrixType_element
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children autocontinue, bgcolor, disabled, element, fgcolor, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenMatrixType">
  <xs:annotation>
    <xs:documentation>Matrix of buttons of which one in each column can be selected.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="autocontinue" type="xs:boolean" default="true" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Automatically end the trial when all columns are completed</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="element" minOccurs="1" maxOccurs="unbounded">
          <xs:complexType>
            <xs:sequence>
              <xs:element name="name" type="xs:string">
                <xs:annotation>
                  <xs:documentation>Name of the element. Will be reported in the results. Will also be used as text if no text is given.</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="text" type="xs:string" minOccurs="0">
                <xs:annotation>
                  <xs:documentation>Text to be shown on the button</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:sequence>
            <xs:attribute name="row" type="xs:positiveInteger" use="required">
              <xs:annotation>
                <xs:documentation>Row in the matrix</xs:documentation>
              </xs:annotation>
            </xs:attribute>
            <xs:attribute name="col" type="xs:positiveInteger" use="required">
              <xs:annotation>
                <xs:documentation>Column in the matrix</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenHtmlType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Show HTML document
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType experiment.tmp#screenHtmlType_page
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, page, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenHtmlType">
  <xs:annotation>
    <xs:documentation>Show HTML document</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
      <xs:sequence>
        <xs:element name="page" type="xs:anyURI">
          <xs:annotation>
            <xs:documentation>Filename of the HTML document.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:screenNumericKeypadType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Numeric keypad input element.
Diagram
Diagram experiment.tmp#gridElementAttributes experiment.tmp#screenIdAttribute experiment.tmp#screenElementType_style experiment.tmp#screenElementType_width experiment.tmp#screenElementType_height experiment.tmp#screenElementType_shortcut experiment.tmp#screenElementType_font experiment.tmp#screenElementType_fontsize experiment.tmp#screenElementType_bgcolor experiment.tmp#screenElementType_fgcolor experiment.tmp#screenElementType_floating experiment.tmp#screenElementType_disabled experiment.tmp#screenElementType
Type extension of apex:screenElementType
Type hierarchy
Used by
Model
Children bgcolor, disabled, fgcolor, floating, font, fontsize, height, shortcut, style, width
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="screenNumericKeypadType">
  <xs:annotation>
    <xs:documentation>Numeric keypad input element.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenElementType">
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:vScreenLayoutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Vertical layout: places elements above each other
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#vScreenLayoutType_height experiment.tmp#gridElementAttributes
Type extension of apex:screenLayoutType
Type hierarchy
Used by
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
height xs:int required
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="vScreenLayoutType">
  <xs:annotation>
    <xs:documentation>Vertical layout: places elements above each other</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenLayoutType">
      <xs:attribute name="height" type="xs:int" use="required">
      </xs:attribute>
      <!--xs:attribute name="id" type="xs:Name" use="optional"> </xs:attribute-->
      <xs:attributeGroup ref="apex:gridElementAttributes"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:gridScreenLayoutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Gridlayout: places elements in an (irregular) grid.
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#gridScreenLayoutType_width experiment.tmp#gridScreenLayoutType_height experiment.tmp#gridScreenLayoutType_columnstretch experiment.tmp#gridScreenLayoutType_rowstretch experiment.tmp#gridElementAttributes
Type extension of apex:screenLayoutType
Type hierarchy
Used by
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
columnstretch apex:stretchregexp optional 
Stretch factor for the columns: a list of integers separated by comma's. If specified, there should be as much 
integers as columns. The width of the columns will be proportional to the numbers. E.g. if width=2 and columnstretch="1,2", the 
second column will be twice as wide as the first. columnstretch="2,4" would have the same effect.
height xs:int required
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
rowstretch apex:stretchregexp optional 
Stretch factor for the rows: a list of integers separated by comma's. If specified, there should be as much 
integers as rows. The width of the rows will be proportional to the numbers. E.g. if height=3 and rowstretch="1,2,1", the 
second row will be twice as wide as the first and thirs. rowstretch="2,4,2" would have the same effect.
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="gridScreenLayoutType">
  <xs:annotation>
    <xs:documentation>Gridlayout: places elements in an (irregular) grid.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenLayoutType">
      <xs:attribute name="width" type="xs:int" use="required">
      </xs:attribute>
      <xs:attribute name="height" type="xs:int" use="required">
      </xs:attribute>
      <xs:attribute name="columnstretch" type="apex:stretchregexp" use="optional">
        <xs:annotation>
          <xs:documentation>Stretch factor for the columns: a list of integers separated by comma's. If specified, there should be as much integers as columns. The width of the columns will be proportional to the numbers. E.g. if width=2 and columnstretch="1,2", the second column will be twice as wide as the first. columnstretch="2,4" would have the same effect.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <xs:attribute name="rowstretch" type="apex:stretchregexp" use="optional">
        <xs:annotation>
          <xs:documentation>Stretch factor for the rows: a list of integers separated by comma's. If specified, there should be as much integers as rows. The width of the rows will be proportional to the numbers. E.g. if height=3 and rowstretch="1,2,1", the second row will be twice as wide as the first and thirs. rowstretch="2,4,2" would have the same effect.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
      <!--xs:attribute name="id" type="xs:ID" use="optional"> </xs:attribute-->
      <xs:attributeGroup ref="apex:gridElementAttributes"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Simple Type apex:stretchregexp
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
pattern [0-9]+(,[0-9]+)*
Used by
Source
 
<xs:simpleType name="stretchregexp">
  <xs:restriction base="xs:string">
    <xs:pattern value="[0-9]+(,[0-9]+)*"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:arcScreenLayoutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Arc layout: places elements in a semi-circle. Useful for localization
experiments.
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#arcScreenLayoutType_width experiment.tmp#gridElementAttributes experiment.tmp#arcScreenLayoutType_type
Type extension of apex:screenLayoutType
Type hierarchy
Used by
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
id xs:Name optional
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
type restriction of xs:string required 
TODO
width xs:int required
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="arcScreenLayoutType">
  <xs:annotation>
    <xs:documentation>Arc layout: places elements in a semi-circle. Useful for localization experiments.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenLayoutType">
      <xs:attribute name="width" type="xs:int" use="required">
      </xs:attribute>
      <!--xs:attribute name="id" type="xs:ID" use="optional"> </xs:attribute-->
      <xs:attributeGroup ref="apex:gridElementAttributes"/>
      <xs:attribute name="type" use="required">
        <xs:annotation>
          <xs:documentation>TODO</xs:documentation>
        </xs:annotation>
        <xs:simpleType>
          <xs:restriction base="xs:string">
            <xs:enumeration value="upper"/>
            <xs:enumeration value="lower"/>
            <xs:enumeration value="left"/>
            <xs:enumeration value="right"/>
            <xs:enumeration value="full"/>
          </xs:restriction>
        </xs:simpleType>
      </xs:attribute>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:twoPartLayoutType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
TwoPartLayout: divides the screen in two parts with a proportion given by the ratio parameter.
The position of the child elements is determined by the y coördinate.
Diagram
Diagram experiment.tmp#screenLayoutType_id experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout experiment.tmp#layoutElementGroup experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad experiment.tmp#screenElementGroup experiment.tmp#screenLayoutType experiment.tmp#twoPartLayoutType_ratio experiment.tmp#twoPartLayoutType_direction experiment.tmp#gridElementAttributes
Type extension of apex:screenLayoutType
Type hierarchy
Used by
Model
Children answerlabel, arcLayout, button, checkBox, flash, gridLayout, hLayout, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit, vLayout
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
direction apex:horivertType required
id xs:Name optional
ratio xs:float required
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:complexType name="twoPartLayoutType">
  <xs:annotation>
    <xs:documentation>TwoPartLayout: divides the screen in two parts with a proportion given by the ratio parameter. The position of the child elements is determined by the y coördinate.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:screenLayoutType">
      <xs:attribute name="ratio" type="xs:float" use="required">
      </xs:attribute>
      <xs:attribute name="direction" type="apex:horivertType" use="required">
      </xs:attribute>
      <xs:attributeGroup ref="apex:gridElementAttributes"/>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Simple Type apex:horivertType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration horizontal
enumeration vertical
Used by
Source
 
<xs:simpleType name="horivertType">
  <xs:restriction base="xs:string">
    <xs:enumeration value="horizontal"/>
    <xs:enumeration value="vertical"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:buttonGroupType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Buttons can be grouped together using a buttongroup to form a single
answer element.
Diagram
Diagram experiment.tmp#screenIdAttribute experiment.tmp#buttonGroupType_button
Used by
Model
Children button
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:complexType name="buttonGroupType">
  <xs:annotation>
    <xs:documentation>Buttons can be grouped together using a buttongroup to form a single answer element.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="button" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <!--xs:attribute name="id" type="xs:IDREF" use="required"/-->
        <xs:attribute name="id" type="xs:Name" use="required"/>
        <!-- FIXME -->
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <!--xs:attribute name="id" type="xs:ID"/-->
  <xs:attributeGroup ref="apex:screenIdAttribute"/>
</xs:complexType>
[ top ]
Complex Type apex:pluginScreenType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType
Type extension of apex:xmlGeneratingPluginType
Type hierarchy
Used by
Model
Children parameter, script
Source
 
<xs:complexType name="pluginScreenType">
  <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 experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter
Used by
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:datablockstype
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#datablockstype_prefix experiment.tmp#datablockstype_datablock experiment.tmp#datablockstype_plugindatablocks
Used by
Model
Children datablock, plugindatablocks, prefix
Source
 
<xs:complexType name="datablockstype">
  <xs:sequence>
    <xs:element name="prefix" type="apex:prefixType" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The prefix for every filename used below. Only used if a filename is a relative path. This prefix is relative to the path of this experiment file.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="datablock" type="apex:datablockType" maxOccurs="unbounded" minOccurs="0">
    </xs:element>
    <xs:element name="plugindatablocks" type="apex:pluginDatablocksType" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:datablockType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#datablockType_id experiment.tmp#datablockType_device experiment.tmp#datablockType_description experiment.tmp#datablockType_file experiment.tmp#datablockType_data experiment.tmp#datablockType_channels experiment.tmp#datablockType_loop
Used by
Model
Children channels, data, description, device, file, loop
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="datablockType">
  <xs:sequence>
    <xs:element name="device" minOccurs="0">
      <xs:annotation>
        <xs:documentation>The device used to play the datablock. If no device is specified, and there is only one device in the experiment file, it will be used. Otherwise an error message will be shown.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:IDREF">
            <!--xs:attribute name="channel1" type="xs:nonNegativeInteger" default="0" use="optional"/>
                                <xs:attribute name="channel2" type="xs:nonNegativeInteger" default="1" use="optional"/-->
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="description" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Text description, for your own reference</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:choice>
      <xs:element name="file" type="xs:string">
        <xs:annotation>
          <xs:documentation>Filename of the corresponding datafile. If it is a relative path, it will be prefixed with the prefix defined above.</xs:documentation>
        </xs:annotation>
      </xs:element>
      <xs:element name="data">
        <xs:annotation>
          <xs:documentation>Direct data. If the data consists of XML code, it can be included directly inside this tag. Currently only works with L34 CI stimuli</xs:documentation>
        </xs:annotation>
        <xs:complexType mixed="true">
          <xs:sequence minOccurs="0">
            <xs:any processContents="skip"/>
          </xs:sequence>
        </xs:complexType>
      </xs:element>
    </xs:choice>
    <xs:element name="channels" type="xs:positiveInteger" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Number of channels: defaults to the number of channels in a wav-file or to 1 in all other cases.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="loop" type="xs:positiveInteger" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Number of times the datablock should be looped</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:pluginDatablocksType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType
Type extension of apex:xmlGeneratingPluginType
Type hierarchy
Used by
Model
Children parameter, script
Source
 
<xs:complexType name="pluginDatablocksType">
  <xs:complexContent>
    <xs:extension base="apex:xmlGeneratingPluginType"/>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:devicesType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#devicesType_master experiment.tmp#devicesType_device
Used by
Model
Children device, master
Source
 
<xs:complexType name="devicesType">
  <xs:sequence>
    <xs:element name="master" type="xs:IDREF" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>The master device is that last one to be started after all stimuli are loaded for all devices. This feature can be used when using triggers to synchronize devices.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="device" type="apex:deviceType" minOccurs="0" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>All real devices derive from this base.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:deviceType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Base type for all devices
Diagram
Diagram experiment.tmp#deviceType_id
Used by
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="deviceType">
  <xs:annotation>
    <xs:documentation>Base type for all devices</xs:documentation>
  </xs:annotation>
  <xs:attribute name="id" type="xs:ID" use="required"/>
  <!--xs:attribute name="mode" type="apex:deviceModesEnum" use="optional">
            <xs:annotation>
                <xs:documentation>Processing mode of this device. Impacts all associated
                filters.</xs:documentation>
            </xs:annotation>
        </xs:attribute-->
</xs:complexType>
[ top ]
Complex Type apex:filtersType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filtersType_filter
Used by
Model
Children filter
Source
 
<xs:complexType name="filtersType">
  <xs:sequence>
    <xs:element name="filter" minOccurs="0" maxOccurs="unbounded" type="apex:filterType">
      <xs:annotation>
        <xs:documentation>Every filter/generator derives from this base type. All filters to be used are defined here.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:filterType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Base type for all filters
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous
Used by
Model
Children channels, continuous, device
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="filterType">
  <xs:annotation>
    <xs:documentation>Base type for all filters</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="device" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>ID of the device to which this filter belongs. The mode of the filter (online or offline) is determined by the device.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="channels" type="xs:positiveInteger">
      <xs:annotation>
        <xs:documentation>Number of channels</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="continuous" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If continuous==true, the filter/generator keeps on running between trials (ie while the user is entering input). Only makes sense for generators.</xs:documentation>
        <!-- FIXME: move to generator -->
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:stimuliType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#stimuliType_fixed_parameters experiment.tmp#stimuliType_stimulus experiment.tmp#stimuliType_pluginstimuli
Used by
Model
Children fixed_parameters, pluginstimuli, stimulus
Source
 
<xs:complexType name="stimuliType">
  <xs:sequence>
    <xs:element name="fixed_parameters" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Fixed parameters describe fixed properties of every stimulus. They can be used by procedures to select a certain stimulus, they can be presented on the screen or can be used for the users own reference. They have no influence whatever on the actual sound/stimulation that is sent to the device when a particular stimulus is to be output. Every fixed stimulus that is used in any stimulus should be defined here. All fixed parameters defined here, should be present in all stimuli.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
            <xs:complexType>
              <xs:attribute name="id" type="xs:ID" use="required"/>
              <xs:attribute name="useforresults" type="xs:boolean" use="optional" default="false"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="stimulus" type="apex:stimulusType" maxOccurs="unbounded" minOccurs="0"/>
    <xs:element name="pluginstimuli" type="apex:pluginStimuliType" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:stimulusType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#stimulusType_id experiment.tmp#stimulusType_description experiment.tmp#stimulusType_datablocks experiment.tmp#stimulusType_variableParameters experiment.tmp#stimulusType_fixedParameters
Used by
Model
Children datablocks, description, fixedParameters, variableParameters
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="stimulusType">
  <xs:sequence>
    <xs:element name="description" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Text description, for your own reference</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="datablocks" type="apex:datablocksType">
      <xs:annotation>
        <xs:documentation>Combination of datablocks to be output</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="variableParameters" minOccurs="0">
      <xs:annotation>
        <xs:documentation>These parameters will be set just before the stimulus is output</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
            <xs:complexType>
              <xs:simpleContent>
                <xs:extension base="xs:string">
                  <xs:attribute name="id" type="xs:IDREF" use="required">
                  </xs:attribute>
                </xs:extension>
              </xs:simpleContent>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="fixedParameters" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Fixed parameters are properties of a stimulus that can be displayed or used to select a stimulus from a list based on a certain criterion.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
            <xs:complexType mixed="true">
              <xs:choice maxOccurs="unbounded" minOccurs="0">
                <xs:element name="b" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                <xs:element name="i" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
                <xs:element name="u" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>
              </xs:choice>
              <xs:attribute name="id" type="xs:IDREF" use="required"/>
            </xs:complexType>
            <!--xs:simpleContent>
                                <xs:extension base="xs:string">
                                <xs:attribute name="id" type="xs:IDREF" use="required"/>
                                </xs:extension>
                                </xs:simpleContent-->
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:datablocksType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Specifies how a number of datablocks are to be combined. Datablocks
can be sequential or simultaneous. All tags can be nested
infinitely.
Diagram
Diagram experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_datablock experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_sequential experiment.tmp#http___med.kuleuven.be_exporl_apex_4.1.2_experiment_datablocksType_simultaneous
Used by
Element apex:stimulusType/datablocks
Model
datablock | sequential | simultaneous
Children datablock, sequential, simultaneous
Source
 
<xs:complexType name="datablocksType">
  <xs:annotation>
    <xs:documentation>Specifies how a number of datablocks are to be combined. Datablocks can be sequential or simultaneous. All tags can be nested infinitely.</xs:documentation>
  </xs:annotation>
  <xs:choice minOccurs="0" maxOccurs="1">
    <xs:element name="datablock">
      <xs:complexType>
        <xs:attribute name="id" type="xs:Name" use="required">
        </xs:attribute>
      </xs:complexType>
    </xs:element>
    <xs:element name="sequential" type="apex:datablocksSequentialType">
      <xs:annotation>
        <xs:documentation>Present all child datablocks or child combinations of datablocks sequentially. The result is guaranteed gap-less when using a single device for all children.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="simultaneous" type="apex:datablocksSimultaneouslType">
      <xs:annotation>
        <xs:documentation>Present all child datablocks or child combinations of datablocks simultaneously. The total length of this block is the length of the longest child block. Zero's or null stimulation will be added to shorter children if necessary (this is not guaranteed!).</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:choice>
</xs:complexType>
[ top ]
Complex Type apex:datablocksSequentialType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous experiment.tmp#datablockGroup
Used by
Model
Children datablock, sequential, simultaneous
Source
 
<xs:complexType name="datablocksSequentialType">
  <xs:group ref="apex:datablockGroup"/>
</xs:complexType>
[ top ]
Complex Type apex:datablockRefType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#datablockRefType_id
Used by
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:complexType name="datablockRefType">
  <xs:attribute name="id" type="xs:IDREF" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:datablocksSimultaneouslType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous experiment.tmp#datablockGroup
Used by
Model
Children datablock, sequential, simultaneous
Source
 
<xs:complexType name="datablocksSimultaneouslType">
  <xs:group ref="apex:datablockGroup"/>
</xs:complexType>
[ top ]
Complex Type apex:pluginStimuliType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.tmp#xmlGeneratingPluginType
Type extension of apex:xmlGeneratingPluginType
Type hierarchy
Used by
Model
Children parameter, script
Source
 
<xs:complexType name="pluginStimuliType">
  <xs:complexContent>
    <xs:extension base="apex:xmlGeneratingPluginType"/>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:connectionsType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#connectionsType_connection
Used by
Model
Children connection
Source
 
<xs:complexType name="connectionsType">
  <xs:sequence>
    <xs:element name="connection" minOccurs="0" maxOccurs="unbounded">
      <xs:complexType>
        <xs:sequence>
          <xs:element name="from" type="apex:connectFromType">
            <xs:annotation>
              <xs:documentation>The channel of the filter/datablock where the connection is started from.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="to" type="apex:connectToType">
            <xs:annotation>
              <xs:documentation>The channel of the device/filter where the connection ends.</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <!--xs:attribute name="device" type="xs:IDREF" use="required"/-->
</xs:complexType>
[ top ]
Complex Type apex:connectFromType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#connectFromType_id experiment.tmp#connectFromType_channel
Used by
Model
Children channel, id
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:complexType name="connectFromType">
  <xs:sequence>
    <!--xs:element name="id" type="xs:IDREF"/-->
    <xs:element name="id">
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="apex:idOrAll">
            <xs:attribute name="mode" default="name">
              <xs:annotation>
                <xs:documentation>Method of matching the given id.</xs:documentation>
              </xs:annotation>
              <xs:simpleType>
                <xs:restriction base="xs:string">
                  <xs:enumeration value="name">
                    <xs:annotation>
                      <xs:documentation>Exactly match the given ID</xs:documentation>
                    </xs:annotation>
                  </xs:enumeration>
                  <xs:enumeration value="regexp">
                    <xs:annotation>
                      <xs:documentation>Use regular expression to match an ID</xs:documentation>
                    </xs:annotation>
                  </xs:enumeration>
                  <xs:enumeration value="wildcard">
                    <xs:annotation>
                      <xs:documentation>Use wildcards (*,?,[]) to match an ID</xs:documentation>
                    </xs:annotation>
                  </xs:enumeration>
                </xs:restriction>
              </xs:simpleType>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
    <xs:element name="channel">
      <xs:annotation>
        <xs:documentation>The channel to be used. Channels are zero based, ie the first channel is 0, the second 1, etc. This parameter can have an ID for later referral.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:unsignedInt">
            <xs:attributeGroup ref="apex:filterParam">
            </xs:attributeGroup>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="apex:filterParam"/>
</xs:complexType>
[ top ]
Simple Type apex:idOrAll
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#all
Type union of(apex:all, xs:IDREF, xs:string)
Used by
Source
 
<xs:simpleType name="idOrAll">
  <xs:union memberTypes="apex:all xs:IDREF xs:string">
    <xs:annotation>
      <xs:documentation>A connection can start from any ID defined elsewhere or from all datablocks. All datablocks can be specified using the _ALL_ in this element.</xs:documentation>
    </xs:annotation>
  </xs:union>
</xs:simpleType>
[ top ]
Complex Type apex:connectToType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#connectToType_id experiment.tmp#connectToType_channel
Used by
Model
Children channel, id
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:complexType name="connectToType">
  <xs:sequence>
    <!--xs:element name="id" type="xs:IDREF"/-->
    <xs:element name="id" type="xs:IDREF">
    </xs:element>
    <xs:element name="channel">
      <xs:annotation>
        <xs:documentation>The channel to be used. Channels are zero based, ie the first channel is 0, the second 1, etc. This parameter can have an ID for later referral. Channel -1 means mute.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="apex:unsignedPlus-1">
            <xs:attributeGroup ref="apex:filterParam">
            </xs:attributeGroup>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attributeGroup ref="apex:filterParam"/>
</xs:complexType>
[ top ]
Simple Type apex:unsignedPlus-1
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:int
Facets
minInclusive -1
Used by
Source
 
<xs:simpleType name="unsignedPlus-1">
  <xs:restriction base="xs:int">
    <xs:minInclusive value="-1"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:randomgeneratorsType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#randomgeneratorsType_randomgenerator
Used by
Model
Children randomgenerator
Source
 
<xs:complexType name="randomgeneratorsType">
  <xs:sequence>
    <xs:element name="randomgenerator" type="apex:randomgenerator" minOccurs="0" maxOccurs="unbounded"/>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:randomgenerator
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Base class for all randomgenerators
Diagram
Diagram experiment.tmp#randomgenerator_id experiment.tmp#randomgenerator_min experiment.tmp#randomgenerator_max experiment.tmp#randomgenerator_type experiment.tmp#randomgenerator_parameter
Properties
abstract true
Used by
Model
Children max, min, parameter, type
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="randomgenerator" abstract="true">
  <xs:annotation>
    <xs:documentation>Base class for all randomgenerators</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="min" type="xs:double">
      <xs:annotation>
        <xs:documentation>Minimum value of the random numbers (inclusive)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="max" type="xs:double">
      <xs:annotation>
        <xs:documentation>Maximum value of the random numbers (exclusive)</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="type">
      <xs:annotation>
        <xs:documentation>Data type</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="double">
            <xs:annotation>
              <xs:documentation>Fractional number</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
          <xs:enumeration value="int">
            <xs:annotation>
              <xs:documentation>Whole number</xs:documentation>
            </xs:annotation>
          </xs:enumeration>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="parameter" type="xs:IDREF">
      <xs:annotation>
        <xs:documentation>Parameter to be set to the random value</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:calibrationType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Calibration settings are stored in a calibration profile. Every
experiment file can have one profile. A profile contains certain parameter settings
that are supposed to impose a fixed relation between digital signal levels and
acoustical signal levels.
Diagram
Diagram experiment.tmp#calibrationType_profile experiment.tmp#calibrationType_soundlevelmeter experiment.tmp#calibrationType_stimuli experiment.tmp#calibrationType_parameters
Used by
Model
Children parameters, soundlevelmeter, stimuli
Attributes
QName Type Use
profile xs:Name required
Source
 
<xs:complexType name="calibrationType">
  <xs:annotation>
    <xs:documentation>Calibration settings are stored in a calibration profile. Every experiment file can have one profile. A profile contains certain parameter settings that are supposed to impose a fixed relation between digital signal levels and acoustical signal levels.</xs:documentation>
  </xs:annotation>
  <xs:sequence>
    <xs:element name="soundlevelmeter" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Information necessary for automatic calibration using an interface to a sound level meter.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="plugin" type="xs:anyURI">
            <xs:annotation>
              <xs:documentation>Filename of the souind level meter plugin to be used</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="transducer" type="xs:string" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Name of the transducer (microphone, ...) to be used by the SLM. Will only be set if your SLM supports it.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="frequency_weighting" default="Z">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="Z">
                  <xs:annotation>
                    <xs:documentation>No weighting: SPL</xs:documentation>
                  </xs:annotation>
                </xs:enumeration>
                <xs:enumeration value="A"/>
                <xs:enumeration value="C"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="time_weighting" default="S">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="S"/>
                <xs:enumeration value="F"/>
                <xs:enumeration value="I"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="type" default="RMS">
            <xs:simpleType>
              <xs:restriction base="xs:string">
                <xs:enumeration value="RMS"/>
                <xs:enumeration value="peak"/>
              </xs:restriction>
            </xs:simpleType>
          </xs:element>
          <xs:element name="percentile" type="xs:double" minOccurs="0" default="0">
            <xs:annotation>
              <xs:documentation>Percentile of statistics on measurement. If 0 an instantaneous measurement will be made.</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="time" type="xs:double" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Measurement time in seconds. If percentile is defined, time should be >0</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="accuracy" type="xs:double" minOccurs="0" default="0.5">
            <xs:annotation>
              <xs:documentation>Automatic calibration is repeated until the measured value is within the accuracy defined here of the target value</xs:documentation>
            </xs:annotation>
          </xs:element>
          <xs:element name="maxiterations" type="xs:positiveInteger" default="3" minOccurs="0">
            <xs:annotation>
              <xs:documentation>Maximal number of iterations that can be done to reach the requested accuracy. If the requested accuracy is not reached after this number of iterations, the calibration fails</xs:documentation>
            </xs:annotation>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="stimuli">
      <xs:annotation>
        <xs:documentation>Stimuli that are used for calibration. These can be, and in some cases should be stimuli that are used in the actual experiment.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="stimulus" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:attribute name="id" type="xs:IDREF" use="required"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="parameters">
      <xs:annotation>
        <xs:documentation>Parameters that are used to calibrate the system. Generally some output gain parameters of the last stage (eg the wavdevice) are used.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="parameter" minOccurs="1" maxOccurs="unbounded">
            <xs:complexType>
              <xs:sequence>
                <xs:element name="targetamplitude" type="xs:double">
                  <xs:annotation>
                    <xs:documentation>Target acoustical measurement of the stimuli defined above during the experiment. Generally in dBSPL.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="calibrationamplitude" type="xs:double" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Value to calibrate at. Generally in dBSPL and higher than targetamplitude. Can be changed during calibration.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="mute" type="xs:double" default="-150">
                  <xs:annotation>
                    <xs:documentation>Value to be used for the other parameters while calibrating this parameter. Has no effect on the actual calibration. Useful for eg muting the other channel of a headphone.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="min" type="xs:double" default="-50" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Minimum parameter value that can be set by the calibrator.</xs:documentation>
                  </xs:annotation>
                </xs:element>
                <xs:element name="max" type="xs:double" default="10" minOccurs="0">
                  <xs:annotation>
                    <xs:documentation>Maximum parameter value that can be set by the calibrator.</xs:documentation>
                  </xs:annotation>
                </xs:element>
              </xs:sequence>
              <xs:attribute name="id" type="xs:IDREF" use="required"/>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="profile" type="xs:Name" use="required"/>
</xs:complexType>
[ top ]
Complex Type apex:resultsType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#resultsType_page experiment.tmp#resultsType_resultparameters experiment.tmp#resultsType_resultscript experiment.tmp#resultsType_showduringexperiment experiment.tmp#resultsType_showafterexperiment experiment.tmp#resultsType_confirmshowresults experiment.tmp#resultsType_matlabscript experiment.tmp#resultsType_subject
Used by
Model
Children confirmshowresults, matlabscript, page, resultparameters, resultscript, showafterexperiment, showduringexperiment, subject
Source
 
<xs:complexType name="resultsType">
  <xs:sequence>
    <xs:element name="page" type="xs:anyURI" minOccurs="1" default="apexresults.html">
      <xs:annotation>
        <xs:documentation>URL of the HTML page to be shown in the results window. The page should have the appropriate javascript methods embedded.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="resultparameters" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Parameters to be passed to the results page. Each parameter will be set in hash params.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:sequence>
          <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
            <xs:complexType>
              <xs:simpleContent>
                <xs:extension base="xs:string">
                  <xs:attribute name="name" type="xs:string"/>
                </xs:extension>
              </xs:simpleContent>
            </xs:complexType>
          </xs:element>
        </xs:sequence>
      </xs:complexType>
    </xs:element>
    <xs:element name="resultscript" type="xs:string" minOccurs="0" default="">
      <xs:annotation>
        <xs:documentation>Javascript, which will be executed after loading the results page, in the context of the results page.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="showduringexperiment" type="xs:boolean" minOccurs="0" default="true">
      <xs:annotation>
        <xs:documentation>If true, an extra window will be created which will show the results of the current experiment while the experiment is being executed. Javascript embedded in the page will be executed upon each new trial.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="showafterexperiment" type="xs:boolean" minOccurs="0" default="false">
      <xs:annotation>
        <xs:documentation>If true a new window will be opened and the results will be shown when the experiment is finished. Confirmation might still be needed (see 'confirmshowresults').</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="confirmshowresults" type="xs:boolean" minOccurs="0" default="true">
      <xs:annotation>
        <xs:documentation>If true a dialog will ask for confirmation whether results should be shown.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="matlabscript" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Matlab script to be used for processing results. Will be added as an XML processing tag to the results file</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="subject" type="xs:string" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Name of the test subject. Will be appended to the suggested results file name. Is typically modified at the beginning of an experiment using an interactive entry.</xs:documentation>
      </xs:annotation>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:interactiveType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#interactiveType_entry
Used by
Model
Children entry
Source
 
<xs:complexType name="interactiveType">
  <xs:sequence>
    <xs:element name="entry" maxOccurs="unbounded">
      <xs:complexType>
        <xs:attribute name="expression" type="xs:string" use="optional">
          <xs:annotation>
            <xs:documentation>XPath expression defining the element to be modified. The user will be alerted if the expression yields no results. If the expression yields more than one result, every element found will be modified. The modification takes place before validation, so the resulting document will not be used unless valid. Modifications will be reported in the results file. If expression is not present, the user input will be saved to the results file, but nothing will be modified.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="type" use="required">
          <xs:annotation>
            <xs:documentation>Data type of the element to be modified. It impacts the dialog box presented to the user and prevents input of data of the wrong data type.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="int">
                <xs:annotation>
                  <xs:documentation>An integer number</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="double">
                <xs:annotation>
                  <xs:documentation>A number</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="string">
                <xs:annotation>
                  <xs:documentation>Some text</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="bool">
                <xs:annotation>
                  <xs:documentation>Boolean value "true" or "false"</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="combo">
                <xs:annotation>
                  <xs:documentation>Value from list. The list of options should be specified in default, separated by |</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
        <xs:attribute name="description" type="xs:string" use="required">
          <xs:annotation>
            <xs:documentation>Description of this entry, will be shown to the user.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="default" type="xs:string" use="required">
          <xs:annotation>
            <xs:documentation>Default value for the replacement.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
        <xs:attribute name="constraint" type="xs:string">
          <xs:annotation>
            <xs:documentation>Regex against which the value should match.</xs:documentation>
          </xs:annotation>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:generalType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#generalType_exitafter experiment.tmp#generalType_autosave experiment.tmp#generalType_waitforstart experiment.tmp#generalType_allowskip experiment.tmp#generalType_runoutputtest experiment.tmp#generalType_outputtestinput experiment.tmp#generalType_scriptlibrary experiment.tmp#generalType_scriptparameters
Used by
Model
Children allowskip, autosave, exitafter, outputtestinput, runoutputtest, scriptlibrary, scriptparameters, waitforstart
Source
 
<xs:complexType name="generalType">
  <xs:sequence>
    <xs:element name="exitafter" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Exit immediately after the experiment was finished. The "save results" dialog box is always shown.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="autosave" type="xs:boolean" minOccurs="0" default="false">
      <xs:annotation>
        <xs:documentation>If defined, apex will automatically select a filename and only present the user with a messagebox asking wheter to save the results yes or no</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="waitforstart" type="xs:boolean" minOccurs="0">
      <xs:annotation>
        <xs:documentation>If true, the next trial is only presented after clicking the Start button, selecting Start from the Experiment menu or pressing F5.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="allowskip" type="xs:boolean" minOccurs="0" default="true">
      <xs:annotation>
        <xs:documentation>If true, the F7 key can be used to skip anything that takes a certain amount of time, eg intro/outro/iti</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="runoutputtest" type="xs:boolean" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Run test to compare output with input files. Only works for WavDevice, and the apex executable must be compiled with WRITEWAVOUTPUT defined. If set, the data send to the soundcard is also written to a file, and afterwards compared with the input. This allows to check if the entire processing/buffering works properly. If the input below is not specified, the test assumes all available datablocks were played sequential. Filters and connections are not taken into account. (eg if two datablocks are defined, the test just checks if the output is identical to the two wavefiles played right after each other). To allow testing filter/loop/connections functionality, create a wavefile that mimics all the processing, and specify the path below, and the test will use it to compare against the output. See the example tests for more info.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="outputtestinput" type="xs:anyURI" minOccurs="0" maxOccurs="1">
      <xs:annotation>
        <xs:documentation>Optional: path to a file to compare the output with.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="scriptlibrary" type="xs:anyURI" minOccurs="0">
      <xs:annotation>
        <xs:documentation>Library of ECMAScript functions. Functions defined in this library can be used from any other script for the experiment.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="scriptparameters" minOccurs="0">
      <xs:complexType>
        <xs:annotation>
          <xs:documentation>Scriptparameters will be made available to all modules that use ECMAScript, such as plugin datablocks, stimuli, trials and procedures.</xs:documentation>
        </xs:annotation>
        <xs:sequence>
          <xs:element name="parameter" default="" minOccurs="1" 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:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:calibstimType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#calibstimType_id experiment.tmp#calibstimType_parameter
Model
Children parameter
Attributes
QName Type Use
id xs:IDREF required
Source
 
<xs:complexType name="calibstimType">
  <xs:sequence>
    <xs:element name="parameter" minOccurs="1" maxOccurs="unbounded">
      <xs:annotation>
        <xs:documentation>Parameter to be calibrated using this stimulus.</xs:documentation>
      </xs:annotation>
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:IDREF">
            <xs:attribute name="targetloudness" type="xs:double" use="required">
              <xs:annotation>
                <xs:documentation>Target loudness value for calibration of this parameter using this stimulus. Mostly in dBSPL. The aim of the calibration is that this stimulus is presented at this loudness in dBSPL to the subject.</xs:documentation>
              </xs:annotation>
            </xs:attribute>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:IDREF" use="required"/>
</xs:complexType>
[ top ]
Simple Type apex:nonEmptyString
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:token
Facets
minLength 1
Source
 
<xs:simpleType name="nonEmptyString">
  <xs:restriction base="xs:token">
    <xs:minLength value="1"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:uniform
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Uniform random generator
Diagram
Diagram experiment.tmp#randomgenerator_id experiment.tmp#randomgenerator_min experiment.tmp#randomgenerator_max experiment.tmp#randomgenerator_type experiment.tmp#randomgenerator_parameter experiment.tmp#randomgenerator
Type extension of apex:randomgenerator
Type hierarchy
Model
Children max, min, parameter, type
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="uniform">
  <xs:annotation>
    <xs:documentation>Uniform random generator</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:randomgenerator">
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:gaussian
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Gaussian random generator. NOT IMPLEMENTED
Diagram
Diagram experiment.tmp#randomgenerator_id experiment.tmp#randomgenerator_min experiment.tmp#randomgenerator_max experiment.tmp#randomgenerator_type experiment.tmp#randomgenerator_parameter experiment.tmp#randomgenerator
Type extension of apex:randomgenerator
Type hierarchy
Model
Children max, min, parameter, type
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="gaussian">
  <xs:annotation>
    <xs:documentation>Gaussian random generator. NOT IMPLEMENTED</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:randomgenerator">
    </xs:extension>
  </xs:complexContent>
</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 experiment.tmp#procedureType_id experiment.tmp#procedureType experiment.tmp#adaptiveProcedure_parameters experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.tmp#procedureParametersType experiment.tmp#adaptiveProcedureParametersType_nUp experiment.tmp#adaptiveProcedureParametersType_nDown experiment.tmp#adaptiveProcedureParametersType_adapt_parameter experiment.tmp#adaptiveProcedureParametersType_start_value experiment.tmp#adaptiveProcedureParametersType_stop_after_type experiment.tmp#adaptiveProcedureParametersType_stop_after experiment.tmp#adaptiveProcedureParametersType_min_value experiment.tmp#adaptiveProcedureParametersType_max_value experiment.tmp#adaptiveProcedureParametersType_larger_is_easier experiment.tmp#adaptiveProcedureParametersType_repeat_first_until_correct experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.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 experiment.tmp#trialsType_trial experiment.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 experiment.tmp#trialType_id experiment.tmp#trialType_answer experiment.tmp#trialType_answer_element experiment.tmp#trialType_screen experiment.tmp#trialType_stimulus experiment.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 experiment.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 experiment.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 experiment.tmp#xmlGeneratingPluginType_script experiment.tmp#xmlGeneratingPluginType_parameter experiment.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:constantProcedure
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Every trial is presented a specified number of
times.
Diagram
Diagram experiment.tmp#procedureType_id experiment.tmp#procedureType experiment.tmp#constantProcedure_parameters experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.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 experiment.tmp#procedureType_id experiment.tmp#procedureType experiment.tmp#trainingProcedure_parameters experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.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 experiment.tmp#procedureType_id experiment.tmp#procedureType experiment.tmp#multiProcedure_parameters experiment.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 experiment.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 experiment.tmp#procedureType_id experiment.tmp#procedureType experiment.tmp#pluginProcedure_parameters experiment.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 experiment.tmp#procedureParametersType_presentations experiment.tmp#procedureParametersType_skip experiment.tmp#procedureParametersType_order experiment.tmp#procedureParametersType_defaultstandard experiment.tmp#procedureParametersType_uniquestandard experiment.tmp#procedureParametersType_intervals experiment.tmp#procedureParametersType_corrector experiment.tmp#procedureParametersType_pause_between_stimuli experiment.tmp#procedureParametersType_time_before_first_trial experiment.tmp#procedureParametersType_input_during_stimulus experiment.tmp#procedureParametersType experiment.tmp#pluginProcedureParametersType_script experiment.tmp#pluginProcedureParametersType_debugger experiment.tmp#pluginProcedureParametersType_adjust_parameter experiment.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 experiment.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 experiment.tmp#parameterType_type experiment.tmp#parameterType experiment.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 experiment.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 experiment.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 experiment.tmp#maybeIdParameterType_type experiment.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 experiment.tmp#genericParameterType_name experiment.tmp#genericParameterType_value experiment.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 experiment.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 ]
Simple Type apex:shortcutHex
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:hexBinary
Facets
length 2
Source
 
<xs:simpleType name="shortcutHex">
  <xs:restriction base="xs:hexBinary">
    <xs:length value="2">
    </xs:length>
  </xs:restriction>
</xs:simpleType>
[ top ]
Simple Type apex:shortcutEnum
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration UpArrow
enumeration DownArrow
enumeration LeftArrow
enumeration RightArrow
enumeration Return
enumeration Space
enumeration Enter
Source
 
<xs:simpleType name="shortcutEnum">
  <xs:restriction base="xs:string">
    <xs:enumeration value="UpArrow"/>
    <xs:enumeration value="DownArrow"/>
    <xs:enumeration value="LeftArrow"/>
    <xs:enumeration value="RightArrow"/>
    <xs:enumeration value="Return"/>
    <xs:enumeration value="Space"/>
    <xs:enumeration value="Enter"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Simple Type apex:shortcutRegExp
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
length 1
pattern .
Source
 
<xs:simpleType name="shortcutRegExp">
  <xs:restriction base="xs:string">
    <!--xs:pattern value="Key_[A-Z0-9]"> </xs:pattern-->
    <xs:pattern value="."/>
    <!--Any Character is ok-->
    <xs:length value="1"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:idRefType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#idRefType_id
Attributes
QName Type Use
id xs:IDREF optional
Source
 
<xs:complexType name="idRefType">
  <xs:attribute name="id" type="xs:IDREF"/>
</xs:complexType>
[ top ]
Complex Type apex:wavDeviceType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#deviceType_id experiment.tmp#deviceType experiment.tmp#wavDeviceType_driver experiment.tmp#wavDeviceType_card experiment.tmp#wavDeviceType_channels experiment.tmp#wavDeviceType_gain experiment.tmp#wavDeviceType_samplerate experiment.tmp#wavDeviceType_buffersize experiment.tmp#wavDeviceType_blocksize experiment.tmp#wavDeviceType_buffersize_apex experiment.tmp#wavDeviceType_padzero experiment.tmp#wavDeviceType_cisim
Type extension of apex:deviceType
Type hierarchy
Model
Children blocksize, buffersize, buffersize_apex, card, channels, cisim, driver, gain, padzero, samplerate
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="wavDeviceType">
  <xs:complexContent>
    <xs:extension base="apex:deviceType">
      <xs:sequence>
        <xs:element name="driver" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Driver architecture to be used for sound output</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="dummy">
                <xs:annotation>
                  <xs:documentation>Dummy soundcard</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="portaudio">
                <xs:annotation>
                  <xs:documentation>Portaudio is a cross-platform audio framework</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="qtaudio">
                <xs:annotation>
                  <xs:documentation>Qt Multimedia framework</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="asio">
                <xs:annotation>
                  <xs:documentation>ASIO is a proprietary windows/mac-only audio framework by Steinberg. Use it if low latency/more then 2 channels is required.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="coreaudio">
                <xs:annotation>
                  <xs:documentation>CoreAudio is MacOsX' audio framework.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <xs:enumeration value="jack">
                <xs:annotation>
                  <xs:documentation>Jack is a cross-platform audio framework. A jack connection will be made to the "drivername" specified in the main config file.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="card" type="xs:string" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Name of the soundcard to be used. Cards are defined in the main config file. Every soundcard in the system can be enumerated in the main configfile. Use the ID defined there. Otherwise the "default" card can be used.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="channels" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>Number of output channels to be used. This is restricted by the selected driver, with a maximum of 2 for portaudio.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="gain" type="apex:channelGainType" minOccurs="0" maxOccurs="unbounded">
          <xs:annotation>
            <xs:documentation>Final gain of the device, implemented with a software mixer.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="samplerate">
          <xs:annotation>
            <xs:documentation>Sample rate of the device. Warning: not all sample rates are supported by all devices and some drivers automatically convert to other sample rates. Check your sound card documentation.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="16000"/>
              <xs:enumeration value="44100"/>
              <xs:enumeration value="96000"/>
              <xs:enumeration value="32000"/>
              <xs:enumeration value="48000"/>
              <xs:enumeration value="8000"/>
              <xs:enumeration value="22050"/>
              <xs:enumeration value="72000"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="buffersize" minOccurs="0" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>Applies to the soundcard buffer size, not the internal apex buffer size. Larger sizes are more efficient, smaller sizes have smaller latencies. Some notes: for asio, latency is always ( 2 * buffersize + overhead ) / samplerate. The overhead is very small, eg 16 samples for an Rme Multiface. Portaudio however always uses a number of internal buffers, mostly 4. Hence, actual latency is ( 2 * 4 * buffersize + overhead ) / samplerate. For asio/jack: must be set to the system buffer size.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="blocksize" minOccurs="0" type="xs:positiveInteger">
          <xs:annotation>
            <xs:documentation>Applies to the block size that is used in the internal apex audio streams (for filters etc.). Larger sizes are more efficient, smaller sizes have smaller latencies. If not defined, the soundcard buffersize will be used.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="buffersize_apex" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Size of internal apex sound buffer in seconds. This buffer ensures that no buffer underruns occur. The default value is 1s. If continuous filters are used, the system will need this amount of seconds before the next stimulus can be output. Note that the value in seconds is rounded down to the nearest multiple of 8192 samples (the buffersize used to fill the buffer): so using 1 second here, with a samplerate of 44100, the actual amount of time will be 40960 samples / 44100 samples/sec = 0.9 seconds. If a buffersize smaller than 16384 samples is specified, a buffer of 16384 samples will be used.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:decimal">
              <xs:minExclusive value="0"/>
              <xs:maxInclusive value="60"/>
            </xs:restriction>
          </xs:simpleType>
          <!--xs:simpleType>
                        <xs:restriction base="xs:string">
                          <xs:enumeration value="0.5"/>
                          <xs:enumeration value="1"/>
                          <xs:enumeration value="1.5"/>
                          <xs:enumeration value="2"/>
                          <xs:enumeration value="3"/>
                          <xs:enumeration value="4"/>
                          <xs:enumeration value="5"/>
                          <xs:enumeration value="10"/>
                        </xs:restriction>
                      </xs:simpleType-->
        </xs:element>
        <xs:element name="padzero" type="xs:nonNegativeInteger" minOccurs="0">
          <xs:annotation>
            <xs:documentation>If smaller than 16: add padzero*8196 samples to the end of each stream. If larger than 16: add padzero samples to the end of each stream. This avoids dropping of the last N frames on some soundcards (notoriously LynxOne and FirefaceUC)</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="cisim" type="apex:cisimType" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Parameters for automatic CI simulation</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:channelGainType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterParam experiment.tmp#gainparam experiment.tmp#channelGainType_channel
Type extension of apex:gainparam
Type hierarchy
Used by
Attributes
QName Type Use Annotation
channel xs:nonNegativeInteger optional 
Used to specify a single channel to apply gain to,
instead of applying it to all channels at once.
For example, for an amplifier having two channels, these are set independently by using <gain id="ch0" channel="0">-3.00</gain>
<gain id="ch1" channel="1">-6.00</gain> Channels are zero based, ie the first channel is 0, the
second 1 and so on.
id xs:ID optional
Source
 
<xs:complexType name="channelGainType">
  <xs:simpleContent>
    <xs:extension base="apex:gainparam">
      <xs:attribute name="channel" type="xs:nonNegativeInteger">
        <xs:annotation>
          <xs:documentation>Used to specify a single channel to apply gain to, instead of applying it to all channels at once. For example, for an amplifier having two channels, these are set independently by using
            <gain id="ch0" channel="0">-3.00</gain>
            <gain id="ch1" channel="1">-6.00</gain>Channels are zero based, ie the first channel is 0, the second 1 and so on.</xs:documentation>
        </xs:annotation>
      </xs:attribute>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:gainparam
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterParam
Type extension of xs:double
Used by
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:complexType name="gainparam">
  <xs:simpleContent>
    <xs:extension base="xs:double">
      <xs:attributeGroup ref="apex:filterParam"/>
    </xs:extension>
  </xs:simpleContent>
</xs:complexType>
[ top ]
Complex Type apex:cisimType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#cisimType_number_electrodes experiment.tmp#cisimType_pulserate experiment.tmp#cisimType_noiseband
Used by
Model
Children noiseband, number_electrodes, pulserate
Source
 
<xs:complexType name="cisimType">
  <xs:sequence>
    <xs:element name="number_electrodes" type="xs:positiveInteger"/>
    <xs:element name="pulserate" type="xs:integer"/>
    <xs:element name="noiseband" minOccurs="1" maxOccurs="unbounded">
      <xs:complexType>
        <xs:simpleContent>
          <xs:extension base="xs:IDREF">
            <xs:attribute name="electrode" type="xs:positiveInteger"/>
          </xs:extension>
        </xs:simpleContent>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
</xs:complexType>
[ top ]
Complex Type apex:dummyDeviceType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Dummy device that does nothing. Useful to temporarily suppress output
of a certain device. Allows anything as parameters.
Diagram
Diagram experiment.tmp#deviceType_id experiment.tmp#deviceType
Type extension of apex:deviceType
Type hierarchy
Model
ANY element from ANY namespace
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="dummyDeviceType">
  <xs:annotation>
    <xs:documentation>Dummy device that does nothing. Useful to temporarily suppress output of a certain device. Allows anything as parameters.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:deviceType">
      <xs:sequence>
        <xs:any processContents="skip" minOccurs="0" maxOccurs="unbounded"/>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:pluginController
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Plugin control device TODO
Diagram
Diagram experiment.tmp#deviceType_id experiment.tmp#deviceType experiment.tmp#pluginController_plugin experiment.tmp#pluginController_parameter
Type extension of apex:deviceType
Type hierarchy
Model
Children parameter, plugin
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="pluginController">
  <xs:annotation>
    <xs:documentation>Plugin control device TODO</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:deviceType">
      <xs:sequence>
        <xs:element name="plugin" type="xs:anyURI"/>
        <xs:element name="parameter" minOccurs="0" maxOccurs="unbounded">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:string">
                <xs:attributeGroup ref="apex:filterParam"/>
                <xs:attribute name="name" type="xs:Name" use="required"/>
                <xs:attribute name="channel" type="xs:nonNegativeInteger" use="optional"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:CohDeviceType
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Cochlear stimulation device
device
Diagram
Diagram experiment.tmp#deviceType_id experiment.tmp#deviceType experiment.tmp#CohDeviceType_device experiment.tmp#CohDeviceType_trigger experiment.tmp#CohDeviceType_powerup_count experiment.tmp#CohDeviceType_volume experiment.tmp#CohDeviceType_defaultmap
Type extension of apex:deviceType
Type hierarchy
Model
Children defaultmap, device, powerup_count, trigger, volume
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="CohDeviceType">
  <xs:annotation>
    <xs:documentation>Cochlear stimulation device device</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:deviceType">
      <xs:sequence>
        <xs:element name="device" type="xs:string">
          <xs:annotation>
            <xs:documentation>Device identifier. For NIC 2, this identifier consists of three parts: the device type (e.g. l34) , the implant type (e.g. cic3, cic4) and the device number (e.g. 1, ordered according to the assigned COM port, device 0 is a simulated device).</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="trigger">
          <xs:annotation>
            <xs:documentation>Generate or use a trigger from the audio port. Currently the trigger button status is not checked (nicv2 doesn't allow this yet)</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="in"/>
              <xs:enumeration value="out"/>
              <xs:enumeration value="none"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <!--xs:element name="volume" minOccurs="0">
                        <xs:simpleType>
                            <xs:restriction base="xs:double">
                                <xs:minInclusive value="0"/>
                                <xs:maxInclusive value="100"/>
                            </xs:restriction>
                        </xs:simpleType>
                    </xs:element -->
        <xs:element name="powerup_count" minOccurs="0" default="4000" type="xs:nonNegativeInteger">
          <xs:annotation>
            <xs:documentation>Number of powerup pulses to send. No powerup pulses will be sent if this is set to 0.</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="volume" minOccurs="0">
          <xs:complexType>
            <xs:annotation>
              <xs:documentation>Volume parameter for Cochlear device. The current level (in clinical units) is calculated according the following formula: round(t + (c-t) * volume/100 * mag) Where: t=treshold level c=comfort level volume=current value of volume parameter mag=magnitude [0,1]</xs:documentation>
            </xs:annotation>
            <xs:simpleContent>
              <xs:extension base="apex:volumeParam">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="defaultmap">
          <xs:annotation>
            <xs:documentation>Defines the default subject map to be used</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:choice>
              <xs:element name="inline" type="apex:CohMap">
                <xs:annotation>
                  <xs:documentation>The map is defined below</xs:documentation>
                </xs:annotation>
              </xs:element>
              <xs:element name="from_r126">
                <xs:annotation>
                  <xs:documentation>The user can select the map from the R126 wizard. R126 is the clinical fitting software.</xs:documentation>
                </xs:annotation>
              </xs:element>
            </xs:choice>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Simple Type apex:volumeParam
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:double
Facets
maxInclusive 100
minInclusive 0
Used by
Source
 
<xs:simpleType name="volumeParam">
  <xs:restriction base="xs:double">
    <xs:minInclusive value="0"/>
    <xs:maxInclusive value="100"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:CohMap
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#CohMap_id experiment.tmp#CohMap_number_electrodes experiment.tmp#CohMap_mode experiment.tmp#CohMap_pulsewidth experiment.tmp#CohMap_pulsegap experiment.tmp#CohMap_period experiment.tmp#CohMap_trigger experiment.tmp#CohMap_channel
Used by
Model
Children channel, mode, number_electrodes, period, pulsegap, pulsewidth, trigger
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:complexType name="CohMap">
  <xs:sequence>
    <xs:element name="number_electrodes">
      <xs:simpleType>
        <xs:restriction base="xs:positiveInteger">
          <xs:maxInclusive value="22"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="mode" type="apex:CohModeEnum">
      <xs:annotation>
        <xs:documentation>Stimulation mode; bipolar modes use a lower, reverse bipolar modes a higher reference electrode.</xs:documentation>
      </xs:annotation>
    </xs:element>
    <xs:element name="pulsewidth">
      <xs:annotation>
        <xs:documentation>When using a Freedom processor, the maximum phasewidth is 429.8us When using an L34 processor, the maximum phasewidth is 434.4us</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:double">
          <xs:minInclusive value="25"/>
          <xs:maxInclusive value="434.4"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="pulsegap">
      <xs:annotation>
        <xs:documentation>When using a Freedom processor, the maximum phase gap is 57us When using an L34 processor, the maximum phase gap is 58us When using a cic3 implant, the minimum phase gap is 8us When using a cic4 implant, the minimum phase gap is 7us</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:double">
          <xs:minInclusive value="7"/>
          <xs:maxInclusive value="58"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="period">
      <xs:annotation>
        <xs:documentation>When using a Freedom processor, the maximum period is 13078us When using an L34 processor, the maximum period is 13107us When using a cic3 implant, the minimum period is 70us When using a cic4 implant, the minimum period is 64.6us</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:double">
          <xs:minInclusive value="64.6"/>
          <xs:maxInclusive value="13107"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="trigger" minOccurs="0" default="none">
      <xs:annotation>
        <xs:documentation>"all" will result in all pulses having triggers. "none" will result in no pulses having triggers. "first" will result in the first pulses that needs mapping to have a trigger, the ones afterward will have no trigger.</xs:documentation>
      </xs:annotation>
      <xs:simpleType>
        <xs:restriction base="xs:string">
          <xs:enumeration value="all"/>
          <xs:enumeration value="none"/>
          <xs:enumeration value="first"/>
        </xs:restriction>
      </xs:simpleType>
    </xs:element>
    <xs:element name="channel" minOccurs="1" maxOccurs="22">
      <xs:complexType>
        <xs:attribute name="number" use="required">
          <xs:simpleType>
            <xs:restriction base="xs:positiveInteger">
              <xs:maxInclusive value="22"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
        <xs:attribute name="electrode" use="required">
          <xs:simpleType>
            <xs:restriction base="xs:positiveInteger">
              <xs:maxInclusive value="22"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
        <xs:attribute name="threshold" use="required">
          <xs:simpleType>
            <xs:restriction base="xs:nonNegativeInteger">
              <xs:maxInclusive value="255"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
        <xs:attribute name="comfort" use="required">
          <xs:simpleType>
            <xs:restriction base="xs:nonNegativeInteger">
              <xs:maxInclusive value="255"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:attribute>
      </xs:complexType>
    </xs:element>
  </xs:sequence>
  <xs:attribute name="id" type="xs:ID"/>
</xs:complexType>
[ top ]
Simple Type apex:CohModeEnum
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration MP1+2
enumeration MP1
enumeration MP2
enumeration BP
enumeration BP+1
enumeration BP+2
enumeration BP+3
enumeration BP+4
enumeration BP+5
enumeration BP+6
enumeration BP+7
enumeration BP+8
enumeration BP+9
enumeration BP+10
enumeration RBP
enumeration RBP+1
enumeration RBP+2
enumeration RBP+3
enumeration RBP+4
enumeration RBP+5
enumeration RBP+6
enumeration RBP+7
enumeration RBP+8
enumeration RBP+9
enumeration RBP+10
Used by
Source
 
<xs:simpleType name="CohModeEnum">
  <xs:restriction base="xs:string">
    <xs:enumeration value="MP1+2"/>
    <xs:enumeration value="MP1"/>
    <xs:enumeration value="MP2"/>
    <xs:enumeration value="BP"/>
    <xs:enumeration value="BP+1"/>
    <xs:enumeration value="BP+2"/>
    <xs:enumeration value="BP+3"/>
    <xs:enumeration value="BP+4"/>
    <xs:enumeration value="BP+5"/>
    <xs:enumeration value="BP+6"/>
    <xs:enumeration value="BP+7"/>
    <xs:enumeration value="BP+8"/>
    <xs:enumeration value="BP+9"/>
    <xs:enumeration value="BP+10"/>
    <xs:enumeration value="RBP"/>
    <xs:enumeration value="RBP+1"/>
    <xs:enumeration value="RBP+2"/>
    <xs:enumeration value="RBP+3"/>
    <xs:enumeration value="RBP+4"/>
    <xs:enumeration value="RBP+5"/>
    <xs:enumeration value="RBP+6"/>
    <xs:enumeration value="RBP+7"/>
    <xs:enumeration value="RBP+8"/>
    <xs:enumeration value="RBP+9"/>
    <xs:enumeration value="RBP+10"/>
  </xs:restriction>
</xs:simpleType>
[ top ]
Simple Type apex:deviceModesEnum
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration online 
All processing (mixing, filtering, ...) is done in real time
while sending output
Source
 
<xs:simpleType name="deviceModesEnum">
  <xs:restriction base="xs:string">
    <xs:enumeration value="online">
      <xs:annotation>
        <xs:documentation>All processing (mixing, filtering, ...) is done in real time while sending output</xs:documentation>
      </xs:annotation>
    </xs:enumeration>
    <!--xs:enumeration value="offline">
                <xs:annotation>
                    <xs:documentation>All processing is done beforehand and the resulting output
                        data is stored in memory. Not all devices support this
                    mode.</xs:documentation>
                </xs:annotation>
            </xs:enumeration-->
  </xs:restriction>
</xs:simpleType>
[ top ]
Complex Type apex:generator
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
A generator is a filter without any input.
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType experiment.tmp#generator_type experiment.tmp#generator_basegain experiment.tmp#generator_invertgain experiment.tmp#generator_gain experiment.tmp#generator_frequency experiment.tmp#generator_phase experiment.tmp#generator_pulsewidth experiment.tmp#generator_polarity
Type extension of apex:filterType
Type hierarchy
Model
Children basegain, channels, continuous, device, frequency, gain, invertgain, phase, polarity, pulsewidth, type
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="generator">
  <xs:annotation>
    <xs:documentation>A generator is a filter without any input.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:filterType">
      <xs:sequence>
        <xs:element name="type">
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="noise">
                <xs:annotation>
                  <xs:documentation>White noise (this is NOT gaussian noise)</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <!--xs:enumeration value="square">
                                    <xs:annotation>
                                    <xs:documentation>Square wave with peak amplitude = total
                                    gain</xs:documentation>
                                    </xs:annotation>
                                    </xs:enumeration-->
              <xs:enumeration value="sinus">
                <xs:annotation>
                  <xs:documentation>Sinus with peak amplitude = total gain</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
              <!--xs:enumeration value="triangle">
                                    <xs:annotation>
                                    <xs:documentation>Triangle with peak amplitude = total
                                    gain</xs:documentation>
                                    </xs:annotation>
                                    </xs:enumeration-->
              <xs:enumeration value="singlepulse">
                <xs:annotation>
                  <xs:documentation>Single pulse with peak amplitude = total gain. The polarity is set using the "polarity" parameter.</xs:documentation>
                </xs:annotation>
              </xs:enumeration>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="basegain" type="xs:double" default="0" minOccurs="0">
          <xs:annotation>
            <xs:documentation>The total gain is basegain+gain. Basegain is useful for amplitude normalization between different blocks</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="invertgain" type="xs:boolean" default="false" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Inverts the gain of the block (but not the basegain). Invertgain is useful for the attenuation of noise depending on an SNR</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="gain" default="0" type="apex:gainparam">
          <xs:annotation>
            <xs:documentation>The total gain is basegain+gain. Gain is a parameter that can be changed by other modules</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="frequency" default="1000">
          <xs:annotation>
            <xs:documentation>Frequency: only makes sense for sinus, square and triangle</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:nonNegativeInteger">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="phase" default="0">
          <xs:annotation>
            <xs:documentation>Phase (rad): only makes sense for sinus, square and triangle</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:double">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="pulsewidth" default="1" type="xs:positiveInteger" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Pulse width in samples. Currently only used for single pulse generator</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="polarity" minOccurs="0" default="positive">
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="positive"/>
              <xs:enumeration value="negative"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:amplifier
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType experiment.tmp#amplifier_basegain experiment.tmp#amplifier_invertgain experiment.tmp#amplifier_gain
Type extension of apex:filterType
Type hierarchy
Model
Children basegain, channels, continuous, device, gain, invertgain
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="amplifier">
  <xs:complexContent>
    <xs:extension base="apex:filterType">
      <xs:sequence>
        <xs:element name="basegain" type="apex:gainparam" default="0" minOccurs="0">
          <xs:annotation>
            <xs:documentation>The total gain is basegain+gain. Basegain is useful for amplitude normalization between different blocks</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="invertgain" type="xs:boolean" default="false" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Inverts the gain of the block (but not the basegain). Invertgain is useful for the attenuation of noise depending on an SNR</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="gain" minOccurs="1" maxOccurs="unbounded" type="apex:channelGainType">
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:fader
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType experiment.tmp#fader_length experiment.tmp#fader_type experiment.tmp#fader_direction
Type extension of apex:filterType
Type hierarchy
Model
Children channels, continuous, device, direction, length, type
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="fader">
  <xs:complexContent>
    <xs:extension base="apex:filterType">
      <xs:sequence>
        <xs:element name="length" default="0">
          <xs:annotation>
            <xs:documentation>Fade length in mSec.</xs:documentation>
          </xs:annotation>
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:double">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="type" default="cosine">
          <xs:annotation>
            <xs:documentation>Fader type: linear or cosine shaped.</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="linear"/>
              <xs:enumeration value="cosine"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
        <xs:element name="direction" default="in">
          <xs:annotation>
            <xs:documentation>Fader direction: fadein (beginning of stimulus) or fadeout(end of stimulus)</xs:documentation>
          </xs:annotation>
          <xs:simpleType>
            <xs:restriction base="xs:string">
              <xs:enumeration value="in"/>
              <xs:enumeration value="out"/>
            </xs:restriction>
          </xs:simpleType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:dataloop
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Loops a datablock forever.
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType experiment.tmp#dataloop_datablock experiment.tmp#dataloop_basegain experiment.tmp#dataloop_invertgain experiment.tmp#dataloop_gain experiment.tmp#dataloop_randomjump experiment.tmp#dataloop_jump
Type extension of apex:filterType
Type hierarchy
Model
Children basegain, channels, continuous, datablock, device, gain, invertgain, jump, randomjump
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="dataloop">
  <xs:annotation>
    <xs:documentation>Loops a datablock forever.</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:filterType">
      <xs:sequence>
        <xs:element name="datablock" type="xs:IDREF"/>
        <xs:element name="basegain" type="xs:double" default="0" minOccurs="0">
          <xs:annotation>
            <xs:documentation>The total gain is basegain+gain. Basegain is useful for amplitude normalization between different blocks</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="invertgain" type="xs:boolean" default="false" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Inverts the gain of the block (but not the basegain). Invertgain is useful for the attenuation of noise depending on an SNR</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="gain" type="apex:gainparam"/>
        <xs:element name="randomjump" type="xs:boolean" default="false" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Jump to a random place in the datablock upon start. Only functional if randomjump=false</xs:documentation>
          </xs:annotation>
        </xs:element>
        <xs:element name="jump" type="xs:double" default="0" minOccurs="0">
          <xs:annotation>
            <xs:documentation>Jump to a fixed place in the datablock when the generator is started. The place is specified in seconds. Take care that you do not jump further than the length of the wave file.</xs:documentation>
          </xs:annotation>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:hrtffiltersum
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType experiment.tmp#hrtffiltersum_anglespeech experiment.tmp#hrtffiltersum_anglenoise experiment.tmp#hrtffiltersum_snr experiment.tmp#hrtffiltersum_speechfile experiment.tmp#hrtffiltersum_noisefile
Type extension of apex:filterType
Type hierarchy
Model
Children anglenoise, anglespeech, channels, continuous, device, noisefile, snr, speechfile
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="hrtffiltersum">
  <xs:complexContent>
    <xs:extension base="apex:filterType">
      <xs:sequence>
        <xs:element name="anglespeech">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:integer">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="anglenoise">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:integer">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="snr">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:integer">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="speechfile">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:integer">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
        <xs:element name="noisefile">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:integer">
                <xs:attributeGroup ref="apex:filterParam"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Complex Type apex:pluginfilter
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Annotations
 
Filter implemented by a binary plugin
Diagram
Diagram experiment.tmp#filterType_id experiment.tmp#filterType_device experiment.tmp#filterType_channels experiment.tmp#filterType_continuous experiment.tmp#filterType experiment.tmp#pluginfilter_plugin experiment.tmp#pluginfilter_parameter
Type extension of apex:filterType
Type hierarchy
Model
Children channels, continuous, device, parameter, plugin
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:complexType name="pluginfilter">
  <xs:annotation>
    <xs:documentation>Filter implemented by a binary plugin</xs:documentation>
  </xs:annotation>
  <xs:complexContent>
    <xs:extension base="apex:filterType">
      <xs:sequence>
        <xs:element name="plugin" type="xs:anyURI"/>
        <xs:element name="parameter" default="" minOccurs="0" maxOccurs="unbounded">
          <xs:complexType>
            <xs:simpleContent>
              <xs:extension base="xs:string">
                <xs:attributeGroup ref="apex:filterParam"/>
                <xs:attribute name="name" type="xs:Name" use="required"/>
                <xs:attribute name="channel" type="xs:nonNegativeInteger" use="optional"/>
              </xs:extension>
            </xs:simpleContent>
          </xs:complexType>
        </xs:element>
      </xs:sequence>
    </xs:extension>
  </xs:complexContent>
</xs:complexType>
[ top ]
Simple Type apex:all
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram
Type restriction of xs:string
Facets
enumeration _ALL_
Source
 
<xs:simpleType name="all">
  <xs:restriction base="xs:string">
    <xs:enumeration value="_ALL_"/>
  </xs:restriction>
</xs:simpleType>
[ 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:prefixType / @source
Namespace No namespace
Type restriction of xs:string
Properties
default inline
Facets
enumeration inline 
The prefix will be specified in this element
enumeration apexconfig 
The prefix will be loaded from the apexconfig.xml file
Used by
Complex Type apex:prefixType
Source
 
<xs:attribute name="source" default="inline">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="inline">
        <xs:annotation>
          <xs:documentation>The prefix will be specified in this element</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="apexconfig">
        <xs:annotation>
          <xs:documentation>The prefix will be loaded from the apexconfig.xml file</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:screenGeneralType / intertrialscreen / @length
Namespace No namespace
Annotations
 
The period to show the screen
Type xs:positiveInteger
Properties
content simple
Used by
Source
 
<xs:attribute name="length" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>The period to show the screen</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:reinforcementType / feedback / @length
Namespace No namespace
Annotations
 
Length of the feedback in ms. If feedback is false but a length is present, the specified time will be the time between two trials.
Type xs:nonNegativeInteger
Properties
default 1000
Used by
Source
 
<xs:attribute name="length" type="xs:nonNegativeInteger" default="1000">
  <xs:annotation>
    <xs:documentation>Length of the feedback in ms. If feedback is false but a length is present, the specified time will be the time between two trials.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:reinforcementType / feedbackplugin / 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:reinforcementType / feedbackplugin / @name
Namespace No namespace
Annotations
 
Name of the plugin to be loaded
Type xs:string
Properties
use required
Used by
Source
 
<xs:attribute name="name" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>Name of the plugin to be loaded</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:childmodeType / intro / @length
Namespace No namespace
Annotations
 
Length of the movie in ms, if not specified, the system will wait for the movie to end and then continue.
Type xs:nonNegativeInteger
Properties
content simple
Used by
Source
 
<xs:attribute name="length" type="xs:nonNegativeInteger">
  <xs:annotation>
    <xs:documentation>Length of the movie in ms, if not specified, the system will wait for the movie to end and then continue.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:childmodeType / outro / @length
Namespace No namespace
Annotations
 
Length of the movie in ms
Type xs:nonNegativeInteger
Properties
content simple
Used by
Source
 
<xs:attribute name="length" type="xs:nonNegativeInteger">
  <xs:annotation>
    <xs:documentation>Length of the movie in ms</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:shortcutType / @action
Namespace No namespace
Type restriction of xs:string
Properties
use optional
default click
Facets
enumeration click 
Has the same effect as clicking the widget
enumeration up 
Has the same effect as clicking the up-button
enumeration down 
Has the same effect as clicking the up-button
Used by
Complex Type apex:shortcutType
Source
 
<xs:attribute name="action" use="optional" default="click">
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="click">
        <xs:annotation>
          <xs:documentation>Has the same effect as clicking the widget</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="up">
        <xs:annotation>
          <xs:documentation>Has the same effect as clicking the up-button</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="down">
        <xs:annotation>
          <xs:documentation>Has the same effect as clicking the up-button</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:shortcutType / @modifier
Namespace No namespace
Annotations
 
Dead key to be used together with the
shortcut
Type restriction of xs:string
Properties
content simple
Facets
enumeration Ctrl
enumeration Alt
enumeration Shift
Used by
Complex Type apex:shortcutType
Source
 
<xs:attribute name="modifier">
  <xs:annotation>
    <xs:documentation>Dead key to be used together with the shortcut</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="Ctrl"/>
      <xs:enumeration value="Alt"/>
      <xs:enumeration value="Shift"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:shortcutType / @hex
Namespace No namespace
Annotations
 
If true, parses the shortcut as a hexadecimal number. See the
Key enum in qtnamespace.h for known values
Type xs:boolean
Properties
content simple
Used by
Complex Type apex:shortcutType
Source
 
<xs:attribute name="hex" type="xs:boolean">
  <xs:annotation>
    <xs:documentation>If true, parses the shortcut as a hexadecimal number. See the Key enum in qtnamespace.h for known values</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:gridElementAttributes / @x
Namespace No namespace
Type xs:int
Properties
content simple
Used by
Attribute Group apex:gridElementAttributes
Source
 
<xs:attribute name="x" type="xs:int"/>
[ top ]
Attribute apex:gridElementAttributes / @y
Namespace No namespace
Type xs:positiveInteger
Properties
content simple
Used by
Attribute Group apex:gridElementAttributes
Source
 
<xs:attribute name="y" type="xs:positiveInteger"/>
[ top ]
Attribute apex:gridElementAttributes / @row
Namespace No namespace
Annotations
 
Row in the grid. Is the same as y, but should not be used together with y
Type xs:int
Properties
content simple
Used by
Attribute Group apex:gridElementAttributes
Source
 
<xs:attribute name="row" type="xs:int">
  <xs:annotation>
    <xs:documentation>Row in the grid. Is the same as y, but should not be used together with y</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:gridElementAttributes / @col
Namespace No namespace
Annotations
 
Column in the grid. Is the same as x, but should not be used together with x
Type xs:positiveInteger
Properties
content simple
Used by
Attribute Group apex:gridElementAttributes
Source
 
<xs:attribute name="col" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Column in the grid. Is the same as x, but should not be used together with x</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:screenIdAttribute / @id
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Attribute Group apex:screenIdAttribute
Source
 
<xs:attribute name="id" type="xs:Name" use="required">
</xs:attribute>
[ top ]
Attribute apex:showparameterType / @name
Namespace No namespace
Annotations
 
Parameter name to show in the
list
Used by
Complex Type apex:showparameterType
Source
 
<xs:attribute name="name">
  <xs:annotation>
    <xs:documentation>Parameter name to show in the list</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:showparameterType / @expression
Namespace No namespace
Annotations
 
Expression to be evaluated. Expressions must
be in the format a*x+b, where x is the parameter value and a
and b are floats
Type apex:mathexpression
Properties
content simple
Facets
pattern (\-?\d*\.?\d*)\s*\*\s*x\s*([+-])\s*(\d+\.?\d*)
Used by
Complex Type apex:showparameterType
Source
 
<xs:attribute name="expression" type="apex:mathexpression">
  <xs:annotation>
    <xs:documentation>Expression to be evaluated. Expressions must be in the format a*x+b, where x is the parameter value and a and b are floats</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:screenPictureType / file / @id
Namespace No namespace
Type xs:ID
Properties
content simple
Used by
Source
 
<xs:attribute name="id" type="xs:ID"/>
[ top ]
Attribute apex:screenMatrixType / element / @row
Namespace No namespace
Annotations
 
Row in the matrix
Type xs:positiveInteger
Properties
use required
Used by
Source
 
<xs:attribute name="row" type="xs:positiveInteger" use="required">
  <xs:annotation>
    <xs:documentation>Row in the matrix</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:screenMatrixType / element / @col
Namespace No namespace
Annotations
 
Column in the matrix
Type xs:positiveInteger
Properties
use required
Used by
Source
 
<xs:attribute name="col" type="xs:positiveInteger" use="required">
  <xs:annotation>
    <xs:documentation>Column in the matrix</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:hScreenLayoutType / @width
Namespace No namespace
Type xs:int
Properties
use required
Used by
Complex Type apex:hScreenLayoutType
Source
 
<xs:attribute name="width" type="xs:int" use="required">
</xs:attribute>
[ top ]
Attribute apex:screenLayoutType / @id
Namespace No namespace
Type xs:Name
Properties
use optional
Used by
Complex Type apex:screenLayoutType
Source
 
<xs:attribute name="id" type="xs:Name" use="optional"/>
[ top ]
Attribute apex:vScreenLayoutType / @height
Namespace No namespace
Type xs:int
Properties
use required
Used by
Complex Type apex:vScreenLayoutType
Source
 
<xs:attribute name="height" type="xs:int" use="required">
</xs:attribute>
[ top ]
Attribute apex:gridScreenLayoutType / @width
Namespace No namespace
Type xs:int
Properties
use required
Used by
Source
 
<xs:attribute name="width" type="xs:int" use="required">
</xs:attribute>
[ top ]
Attribute apex:gridScreenLayoutType / @height
Namespace No namespace
Type xs:int
Properties
use required
Used by
Source
 
<xs:attribute name="height" type="xs:int" use="required">
</xs:attribute>
[ top ]
Attribute apex:gridScreenLayoutType / @columnstretch
Namespace No namespace
Annotations
 
Stretch factor for the columns: a list of integers separated by comma's. If specified, there should be as much 
integers as columns. The width of the columns will be proportional to the numbers. E.g. if width=2 and columnstretch="1,2", the 
second column will be twice as wide as the first. columnstretch="2,4" would have the same effect.
Type apex:stretchregexp
Properties
use optional
Facets
pattern [0-9]+(,[0-9]+)*
Used by
Source
 
<xs:attribute name="columnstretch" type="apex:stretchregexp" use="optional">
  <xs:annotation>
    <xs:documentation>Stretch factor for the columns: a list of integers separated by comma's. If specified, there should be as much integers as columns. The width of the columns will be proportional to the numbers. E.g. if width=2 and columnstretch="1,2", the second column will be twice as wide as the first. columnstretch="2,4" would have the same effect.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:gridScreenLayoutType / @rowstretch
Namespace No namespace
Annotations
 
Stretch factor for the rows: a list of integers separated by comma's. If specified, there should be as much 
integers as rows. The width of the rows will be proportional to the numbers. E.g. if height=3 and rowstretch="1,2,1", the 
second row will be twice as wide as the first and thirs. rowstretch="2,4,2" would have the same effect.
Type apex:stretchregexp
Properties
use optional
Facets
pattern [0-9]+(,[0-9]+)*
Used by
Source
 
<xs:attribute name="rowstretch" type="apex:stretchregexp" use="optional">
  <xs:annotation>
    <xs:documentation>Stretch factor for the rows: a list of integers separated by comma's. If specified, there should be as much integers as rows. The width of the rows will be proportional to the numbers. E.g. if height=3 and rowstretch="1,2,1", the second row will be twice as wide as the first and thirs. rowstretch="2,4,2" would have the same effect.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:arcScreenLayoutType / @width
Namespace No namespace
Type xs:int
Properties
use required
Used by
Source
 
<xs:attribute name="width" type="xs:int" use="required">
</xs:attribute>
[ top ]
Attribute apex:arcScreenLayoutType / @type
Namespace No namespace
Annotations
 
TODO
Type restriction of xs:string
Properties
use required
Facets
enumeration upper
enumeration lower
enumeration left
enumeration right
enumeration full
Used by
Source
 
<xs:attribute name="type" use="required">
  <xs:annotation>
    <xs:documentation>TODO</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="upper"/>
      <xs:enumeration value="lower"/>
      <xs:enumeration value="left"/>
      <xs:enumeration value="right"/>
      <xs:enumeration value="full"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:twoPartLayoutType / @ratio
Namespace No namespace
Type xs:float
Properties
use required
Used by
Complex Type apex:twoPartLayoutType
Source
 
<xs:attribute name="ratio" type="xs:float" use="required">
</xs:attribute>
[ top ]
Attribute apex:twoPartLayoutType / @direction
Namespace No namespace
Type apex:horivertType
Properties
use required
Facets
enumeration horizontal
enumeration vertical
Used by
Complex Type apex:twoPartLayoutType
Source
 
<xs:attribute name="direction" type="apex:horivertType" use="required">
</xs:attribute>
[ top ]
Attribute apex:buttonGroupType / button / @id
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Source
 
<xs:attribute name="id" type="xs:Name" use="required"/>
[ top ]
Attribute apex:screenType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:screenType
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:screenType / @description
Namespace No namespace
Annotations
 
Description of the screen - for your own reference
Type xs:string
Properties
use optional
Used by
Complex Type apex:screenType
Source
 
<xs:attribute name="description" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>Description of the screen - for your own reference</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ 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:datablockType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:datablockType
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:deviceType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:deviceType
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:filterType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:filterType
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:stimuliType / fixed_parameters / parameter / @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:stimuliType / fixed_parameters / parameter / @useforresults
Namespace No namespace
Type xs:boolean
Properties
use optional
default false
Used by
Source
 
<xs:attribute name="useforresults" type="xs:boolean" use="optional" default="false"/>
[ top ]
Attribute apex:datablocksType / datablock / @id
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Element apex:datablocksType/datablock
Source
 
<xs:attribute name="id" type="xs:Name" use="required">
</xs:attribute>
[ top ]
Attribute apex:datablockRefType / @id
Namespace No namespace
Type xs:IDREF
Properties
use required
Used by
Complex Type apex:datablockRefType
Source
 
<xs:attribute name="id" type="xs:IDREF" use="required"/>
[ top ]
Attribute apex:stimulusType / variableParameters / parameter / @id
Namespace No namespace
Type xs:IDREF
Properties
use required
Used by
Source
 
<xs:attribute name="id" type="xs:IDREF" use="required">
</xs:attribute>
[ top ]
Attribute apex:stimulusType / fixedParameters / parameter / @id
Namespace No namespace
Type xs:IDREF
Properties
use required
Used by
Source
 
<xs:attribute name="id" type="xs:IDREF" use="required"/>
[ top ]
Attribute apex:stimulusType / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:stimulusType
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:connectFromType / id / @mode
Namespace No namespace
Annotations
 
Method of matching the given id.
Type restriction of xs:string
Properties
default name
Facets
enumeration name 
Exactly match the given ID
enumeration regexp 
Use regular expression to match an ID
enumeration wildcard 
Use wildcards (*,?,[]) to match an ID
Used by
Source
 
<xs:attribute name="mode" default="name">
  <xs:annotation>
    <xs:documentation>Method of matching the given id.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="name">
        <xs:annotation>
          <xs:documentation>Exactly match the given ID</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="regexp">
        <xs:annotation>
          <xs:documentation>Use regular expression to match an ID</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="wildcard">
        <xs:annotation>
          <xs:documentation>Use wildcards (*,?,[]) to match an ID</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:filterParam / @id
Namespace No namespace
Type xs:ID
Properties
content simple
Used by
Attribute Group apex:filterParam
Source
 
<xs:attribute name="id" type="xs:ID"/>
[ top ]
Attribute apex:randomgenerator / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Complex Type apex:randomgenerator
Source
 
<xs:attribute name="id" type="xs:ID" use="required"/>
[ top ]
Attribute apex:calibrationType / stimuli / stimulus / @id
Namespace No namespace
Type xs:IDREF
Properties
use required
Used by
Source
 
<xs:attribute name="id" type="xs:IDREF" use="required"/>
[ top ]
Attribute apex:calibrationType / parameters / parameter / @id
Namespace No namespace
Type xs:IDREF
Properties
use required
Used by
Source
 
<xs:attribute name="id" type="xs:IDREF" use="required"/>
[ top ]
Attribute apex:calibrationType / @profile
Namespace No namespace
Type xs:Name
Properties
use required
Used by
Complex Type apex:calibrationType
Source
 
<xs:attribute name="profile" type="xs:Name" use="required"/>
[ top ]
Attribute apex:resultsType / resultparameters / parameter / @name
Namespace No namespace
Type xs:string
Properties
content simple
Used by
Source
 
<xs:attribute name="name" type="xs:string"/>
[ top ]
Attribute apex:interactiveType / entry / @expression
Namespace No namespace
Annotations
 
XPath expression defining the element
to be modified. The user will be alerted if the
expression yields no results. If the expression
yields more than one result, every element found
will be modified. The modification takes place
before validation, so the resulting document will
not be used unless valid. Modifications will be
reported in the results file.
If expression is not present, the user input will be saved to the results file, but
nothing will be modified.
Type xs:string
Properties
use optional
Used by
Element apex:interactiveType/entry
Source
 
<xs:attribute name="expression" type="xs:string" use="optional">
  <xs:annotation>
    <xs:documentation>XPath expression defining the element to be modified. The user will be alerted if the expression yields no results. If the expression yields more than one result, every element found will be modified. The modification takes place before validation, so the resulting document will not be used unless valid. Modifications will be reported in the results file. If expression is not present, the user input will be saved to the results file, but nothing will be modified.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:interactiveType / entry / @type
Namespace No namespace
Annotations
 
Data type of the element to be
modified. It impacts the dialog box presented to the
user and prevents input of data of the wrong data
type.
Type restriction of xs:string
Properties
use required
Facets
enumeration int 
An integer
number
enumeration double 
A
number
enumeration string 
Some
text
enumeration bool 
Boolean value "true" or "false"
enumeration combo 
Value from list. The list of options should be specified in default, separated by |
Used by
Element apex:interactiveType/entry
Source
 
<xs:attribute name="type" use="required">
  <xs:annotation>
    <xs:documentation>Data type of the element to be modified. It impacts the dialog box presented to the user and prevents input of data of the wrong data type.</xs:documentation>
  </xs:annotation>
  <xs:simpleType>
    <xs:restriction base="xs:string">
      <xs:enumeration value="int">
        <xs:annotation>
          <xs:documentation>An integer number</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="double">
        <xs:annotation>
          <xs:documentation>A number</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="string">
        <xs:annotation>
          <xs:documentation>Some text</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="bool">
        <xs:annotation>
          <xs:documentation>Boolean value "true" or "false"</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
      <xs:enumeration value="combo">
        <xs:annotation>
          <xs:documentation>Value from list. The list of options should be specified in default, separated by |</xs:documentation>
        </xs:annotation>
      </xs:enumeration>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:interactiveType / entry / @description
Namespace No namespace
Annotations
 
Description of this entry, will be
shown to the user.
Type xs:string
Properties
use required
Used by
Element apex:interactiveType/entry
Source
 
<xs:attribute name="description" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>Description of this entry, will be shown to the user.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:interactiveType / entry / @default
Namespace No namespace
Annotations
 
Default value for the
replacement.
Type xs:string
Properties
use required
Used by
Element apex:interactiveType/entry
Source
 
<xs:attribute name="default" type="xs:string" use="required">
  <xs:annotation>
    <xs:documentation>Default value for the replacement.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:interactiveType / entry / @constraint
Namespace No namespace
Annotations
 
Regex against which the value
should match.
Type xs:string
Properties
content simple
Used by
Element apex:interactiveType/entry
Source
 
<xs:attribute name="constraint" type="xs:string">
  <xs:annotation>
    <xs:documentation>Regex against which the value should match.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:generalType / scriptparameters / 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:apex / @version
Namespace No namespace
Annotations
 
Apex will only load experiment files with the correct version
attribute. Conversion scripts will be provided to convert to newer
versions.
Type xs:positiveInteger
Properties
use optional
Used by
Element apex:apex
Source
 
<xs:attribute name="version" use="optional" type="xs:positiveInteger">
  <xs:annotation>
    <xs:documentation>Apex will only load experiment files with the correct version attribute. Conversion scripts will be provided to convert to newer versions.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:calibstimType / parameter / @targetloudness
Namespace No namespace
Annotations
 
Target loudness value for calibration of this
parameter using this stimulus. Mostly in dBSPL. The aim of
the calibration is that this stimulus is presented at this
loudness in dBSPL to the subject.
Type xs:double
Properties
use required
Used by
Source
 
<xs:attribute name="targetloudness" type="xs:double" use="required">
  <xs:annotation>
    <xs:documentation>Target loudness value for calibration of this parameter using this stimulus. Mostly in dBSPL. The aim of the calibration is that this stimulus is presented at this loudness in dBSPL to the subject.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:calibstimType / @id
Namespace No namespace
Type xs:IDREF
Properties
use required
Used by
Complex Type apex:calibstimType
Source
 
<xs:attribute name="id" type="xs:IDREF" use="required"/>
[ 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: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 ]
Attribute apex:idAttribute / @id
Namespace No namespace
Type xs:ID
Properties
use required
Used by
Attribute Group apex:idAttribute
Source
 
<xs:attribute name="id" type="xs:ID" use="required">
</xs:attribute>
[ top ]
Attribute apex:idRefType / @id
Namespace No namespace
Type xs:IDREF
Properties
content simple
Used by
Complex Type apex:idRefType
Source
 
<xs:attribute name="id" type="xs:IDREF"/>
[ top ]
Attribute apex:channelGainType / @channel
Namespace No namespace
Annotations
 
Used to specify a single channel to apply gain to,
instead of applying it to all channels at once.
For example, for an amplifier having two channels, these are set independently by using <gain id="ch0" channel="0">-3.00</gain>
<gain id="ch1" channel="1">-6.00</gain> Channels are zero based, ie the first channel is 0, the
second 1 and so on.
Type xs:nonNegativeInteger
Properties
content simple
Used by
Complex Type apex:channelGainType
Source
 
<xs:attribute name="channel" type="xs:nonNegativeInteger">
  <xs:annotation>
    <xs:documentation>Used to specify a single channel to apply gain to, instead of applying it to all channels at once. For example, for an amplifier having two channels, these are set independently by using
      <gain id="ch0" channel="0">-3.00</gain>
      <gain id="ch1" channel="1">-6.00</gain>Channels are zero based, ie the first channel is 0, the second 1 and so on.</xs:documentation>
  </xs:annotation>
</xs:attribute>
[ top ]
Attribute apex:cisimType / noiseband / @electrode
Namespace No namespace
Type xs:positiveInteger
Properties
content simple
Used by
Source
 
<xs:attribute name="electrode" type="xs:positiveInteger"/>
[ top ]
Attribute apex:pluginController / 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:pluginController / parameter / @channel
Namespace No namespace
Type xs:nonNegativeInteger
Properties
use optional
Used by
Source
 
<xs:attribute name="channel" type="xs:nonNegativeInteger" use="optional"/>
[ top ]
Attribute apex:CohMap / channel / @number
Namespace No namespace
Type restriction of xs:positiveInteger
Properties
use required
Facets
maxInclusive 22
Used by
Source
 
<xs:attribute name="number" use="required">
  <xs:simpleType>
    <xs:restriction base="xs:positiveInteger">
      <xs:maxInclusive value="22"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:CohMap / channel / @electrode
Namespace No namespace
Type restriction of xs:positiveInteger
Properties
use required
Facets
maxInclusive 22
Used by
Source
 
<xs:attribute name="electrode" use="required">
  <xs:simpleType>
    <xs:restriction base="xs:positiveInteger">
      <xs:maxInclusive value="22"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:CohMap / channel / @threshold
Namespace No namespace
Type restriction of xs:nonNegativeInteger
Properties
use required
Facets
maxInclusive 255
Used by
Source
 
<xs:attribute name="threshold" use="required">
  <xs:simpleType>
    <xs:restriction base="xs:nonNegativeInteger">
      <xs:maxInclusive value="255"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:CohMap / channel / @comfort
Namespace No namespace
Type restriction of xs:nonNegativeInteger
Properties
use required
Facets
maxInclusive 255
Used by
Source
 
<xs:attribute name="comfort" use="required">
  <xs:simpleType>
    <xs:restriction base="xs:nonNegativeInteger">
      <xs:maxInclusive value="255"/>
    </xs:restriction>
  </xs:simpleType>
</xs:attribute>
[ top ]
Attribute apex:CohMap / @id
Namespace No namespace
Type xs:ID
Properties
content simple
Used by
Complex Type apex:CohMap
Source
 
<xs:attribute name="id" type="xs:ID"/>
[ top ]
Attribute apex:pluginfilter / 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:pluginfilter / parameter / @channel
Namespace No namespace
Type xs:nonNegativeInteger
Properties
use optional
Used by
Source
 
<xs:attribute name="channel" type="xs:nonNegativeInteger" use="optional"/>
[ top ]
Element Group apex:layoutElementGroup
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#layoutElementGroup_hLayout experiment.tmp#layoutElementGroup_vLayout experiment.tmp#layoutElementGroup_gridLayout experiment.tmp#layoutElementGroup_arcLayout
Used by
Model
Children arcLayout, gridLayout, hLayout, vLayout
Source
 
<xs:group name="layoutElementGroup">
  <xs:sequence>
    <xs:choice maxOccurs="1">
      <xs:element name="hLayout" type="apex:hScreenLayoutType" minOccurs="0"/>
      <xs:element name="vLayout" type="apex:vScreenLayoutType" minOccurs="0"/>
      <xs:element name="gridLayout" type="apex:gridScreenLayoutType" minOccurs="0"/>
      <xs:element name="arcLayout" type="apex:arcScreenLayoutType" minOccurs="0"/>
    </xs:choice>
  </xs:sequence>
</xs:group>
[ top ]
Element Group apex:screenElementGroup
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#screenElementGroup_button experiment.tmp#screenElementGroup_label experiment.tmp#screenElementGroup_answerlabel experiment.tmp#screenElementGroup_parameterlabel experiment.tmp#screenElementGroup_textEdit experiment.tmp#screenElementGroup_picture experiment.tmp#screenElementGroup_flash experiment.tmp#screenElementGroup_parameterlist experiment.tmp#screenElementGroup_picturelabel experiment.tmp#screenElementGroup_spinBox experiment.tmp#screenElementGroup_checkBox experiment.tmp#screenElementGroup_slider experiment.tmp#screenElementGroup_matrix experiment.tmp#screenElementGroup_html experiment.tmp#screenElementGroup_numericKeypad
Used by
Model
Children answerlabel, button, checkBox, flash, html, label, matrix, numericKeypad, parameterlabel, parameterlist, picture, picturelabel, slider, spinBox, textEdit
Source
 
<xs:group name="screenElementGroup">
  <xs:sequence>
    <xs:choice maxOccurs="1">
      <xs:element name="button" type="apex:screenButtonType" minOccurs="0"/>
      <xs:element name="label" type="apex:screenLabelType" minOccurs="0"/>
      <xs:element name="answerlabel" type="apex:screenAnswerLabelType" minOccurs="0"/>
      <xs:element name="parameterlabel" type="apex:screenParameterLabelType" minOccurs="0"/>
      <xs:element name="textEdit" type="apex:screenTextEditType" minOccurs="0"/>
      <xs:element name="picture" type="apex:screenPictureType" minOccurs="0"/>
      <xs:element name="flash" type="apex:screenFlashType" minOccurs="0"/>
      <xs:element name="parameterlist" type="apex:screenParameterlistType" minOccurs="0"/>
      <xs:element name="picturelabel" type="apex:screenPictureLabelType" minOccurs="0"/>
      <xs:element name="spinBox" type="apex:screenSpinBoxType" minOccurs="0"/>
      <xs:element name="checkBox" type="apex:screenCheckBoxType" minOccurs="0"/>
      <xs:element name="slider" type="apex:screenSliderType" minOccurs="0"/>
      <xs:element name="matrix" type="apex:screenMatrixType" minOccurs="0"/>
      <xs:element name="html" type="apex:screenHtmlType" minOccurs="0"/>
      <xs:element name="numericKeypad" type="apex:screenNumericKeypadType" minOccurs="0"/>
    </xs:choice>
  </xs:sequence>
</xs:group>
[ top ]
Element Group apex:datablockGroup
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#datablockGroup_datablock experiment.tmp#datablockGroup_sequential experiment.tmp#datablockGroup_simultaneous
Used by
Model
Children datablock, sequential, simultaneous
Source
 
<xs:group name="datablockGroup">
  <xs:sequence>
    <xs:choice maxOccurs="unbounded" minOccurs="2">
      <xs:element name="datablock" type="apex:datablockRefType" minOccurs="0"/>
      <xs:element name="sequential" type="apex:datablocksSequentialType" minOccurs="0"/>
      <xs:element name="simultaneous" type="apex:datablocksSimultaneouslType" minOccurs="0"/>
    </xs:choice>
  </xs:sequence>
</xs:group>
[ top ]
Attribute Group apex:gridElementAttributes
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#gridElementAttributes_x experiment.tmp#gridElementAttributes_y experiment.tmp#gridElementAttributes_row experiment.tmp#gridElementAttributes_col
Used by
Attributes
QName Type Use Annotation
col xs:positiveInteger optional 
Column in the grid. Is the same as x, but should not be used together with x
row xs:int optional 
Row in the grid. Is the same as y, but should not be used together with y
x xs:int optional
y xs:positiveInteger optional
Source
 
<xs:attributeGroup name="gridElementAttributes">
  <xs:attribute name="x" type="xs:int"/>
  <xs:attribute name="y" type="xs:positiveInteger"/>
  <xs:attribute name="row" type="xs:int">
    <xs:annotation>
      <xs:documentation>Row in the grid. Is the same as y, but should not be used together with y</xs:documentation>
    </xs:annotation>
  </xs:attribute>
  <xs:attribute name="col" type="xs:positiveInteger">
    <xs:annotation>
      <xs:documentation>Column in the grid. Is the same as x, but should not be used together with x</xs:documentation>
    </xs:annotation>
  </xs:attribute>
</xs:attributeGroup>
[ top ]
Attribute Group apex:screenIdAttribute
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#screenIdAttribute_id
Used by
Attributes
QName Type Use
id xs:Name required
Source
 
<xs:attributeGroup name="screenIdAttribute">
  <xs:attribute name="id" type="xs:Name" use="required">
  </xs:attribute>
</xs:attributeGroup>
[ top ]
Attribute Group apex:filterParam
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#filterParam_id
Used by
Attributes
QName Type Use
id xs:ID optional
Source
 
<xs:attributeGroup name="filterParam">
  <xs:attribute name="id" type="xs:ID"/>
</xs:attributeGroup>
[ top ]
Attribute Group apex:idAttribute
Namespace http://med.kuleuven.be/exporl/apex/4.1.2/experiment
Diagram
Diagram experiment.tmp#idAttribute_id
Attributes
QName Type Use
id xs:ID required
Source
 
<xs:attributeGroup name="idAttribute">
  <xs:attribute name="id" type="xs:ID" use="required">
  </xs:attribute>
</xs:attributeGroup>
[ top ]
XML Schema documentation generated by ® XML Editor.