Welcome Guest, you are in: <root>Elements • Login

Page History: Reporter Element

Compare Page Revisions

35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 Current 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0

« Older Revision - Back to Page History - Newer Revision »

Page Revision: 2013/06/10 05:49

The Reporter element offers a simple and flexible way to control data collection in EventIDE experiments.

Table of Contents [Hide/Show] Description Snapshots Practical Use     Using Reporter for collecting trial data into a multi-line table     Using Reporter for collecting data into a record list Element's internal actions aligned with epochs of the parent event Notes Properties     Generic Properties

Description ¶

EventIDE has an core mechanism for data collection, which is called Data Report. The mechanism is very flexible, because you can always code what data will be written and when it will be done in the course of an experiment. To remove a need to write such data collection code in standard scenarios, the Reporter element is introduced. The element provides a visual designer, where you can select a list of global variables and Proxy Variables for recording. With the Reporter's designer you can define the variable order, value formats and preview the expected results. At runtime, the Reporter element automatically makes a snapshot of the selected variables, builds a text block with collected variables' values (either in a line or columns) and records the block into the Data Report. This operation is done either on onset or on offset the parent event, which helps to implement repeated data drops, when the parent event is included in a trial loop. Multiple Reporter elements can be used elsewhere in an experiment, when different blocks of the data have to be recorded separately. The element can also create a header line containing names of the selected variables. The header is automatically placed at the top of the data report, before actual data collection starts.

Snapshots ¶

Snapshot 1

Snapshot 2

Practical Use ¶

Using Reporter for collecting trial data into a multi-line table ¶

1. Check a logic of your experiment to choose variables whose values you want to collect in each trial.
2. Add the Reporter element to the event, in which you want to collect data. Typically, it is the last event in a trial loop.
3. Set the Recording Point property of Reporter. You can define there when data will be collected, either on onset or offset of the parent event. The default option is the event
   offset, because you may need to calculate a trial outcome, after onset of the last trial event but before trial data is recorded.
4. Open the Reporter designer by clicking on the corresponding property.
5. Using a drop-down list on the left-top of the designer, select and add all variables whose values you want to record in each trial:
   {|
   |
   

   Dropdown selection of variables
   

   
   |}
6. In the Layout Option panel set the layout of variables to "in rows" and choose a character that will be used a column separator.
7. Check the report preview at the bottom of the designer
8. Close the designer and run an experiment for several trial loops.
9. Open or export the resulting data report, and check how trial data is recorded. You should see data organized in a table, for example:
   

   
   
   Participant Code;Block Number;Trial Number;Target Position;Target Color;Target Shape;SOA Duration;Trial Result;Trial RT;
   
   Participant 01;1;1;180;Blue;1;100;True;881;
   
   Participant 01;1;2;180;Yellow;2;400;True;564;
   
   Participant 01;1;3;180;Blue;2;300;False;0;
   
   Participant 01;1;4;0;Blue;2;600;True;867;
   
   Participant 01;1;5;180;Red;2;200;True;760;
   
   

   
   

Using Reporter for collecting data into a record list ¶

1. Repeat steps 1-5 from the previous technique except for selection of the parent event. The record list is usually added once per run, at the start of the experiment.
2. Set the layout of variables to "in columns" in the Layout Option panel of Reporter's designer. If you do not want variables' names to be included in a record list, uncheck the 'Append variables's headers' option.
3. Set the layout of variables to "in columns" in the Layout Option panel of Reporter's designer. If you do not want variables' names to be included in a record list, uncheck the 'Append variables's headers' option. Otherwise, select a character that will separate variable's name and value in each row.
4. Check the report preview at the bottom of the designer
5. Close the designer and run an experiment for several trial loops.
6. Open or export the resulting data report, and check how trial data is recorded. You should see data organized in a list, for example:
   

    
   
   Participant Code;Participant 01;
   
   Condition; AA05;
   
   Key Map; 01; 
   
   

   
   

Element's internal actions aligned with epochs of the parent event ¶

Epoche	Actions
After onset	if the Recording Point property is 'On Onset', Reporter saves selected variables into a data report
Before offset	if the Recording Point property is 'On Offset', Reporter saves selected variables into a data report

Notes ¶

• You can use multiple Reporter elements elsewhere in an experiment, but be aware of the order, in which they save their own data into a data report.
• There is no need to use Reporter, when you need to save a list of global experiment variables at the top of a data report, you can used the startup info variables instead.
• While using the Reporter element, you still can write any data into a data report directly, via code snippets.
  

Properties ¶

Generic Properties ¶

Name	Description	Attributes	Value Type	Proxy Reflex
Category Name
Recording Point	Defines a time point in the parent event, when the element records selected variables into Data Report

+=== Properties inherited from clElement === Inherited properties of clElement

Name	Description	Constraints	Value Type	Upon Change
Control
Is Enabled	If set to false the element is completely omitted when the experiment is run.	Design Time..	Boolean
Title	Title of the element.	Design Time..	String