Standard reports

Below is a description of all the report types included in the reporting module. We have tried to define reports that summarize the most commonly-needed information across different types of infant and toddler testing procedures. Sometimes, running multiple reports may best suit your needs. You may also find that none of these capture a measure that you need. If so, we are happy to help you better understand the formatting of log files so that you can create a custom report function - either to run within the reporting module, or as a separate script.

Common elements to all report types

Report info

All report types open with basic information about their generation via the reporting module and the log file(s) included. In this opening section, one row is output per log file included in the report. Each line includes:

1. Subject ID

2. Date and time of experiment session

3. Date and time when report was generated

4. BITTSy version used to run the experiment session

5. Reporting module version used to generate the report

6. File path of the log file included in the report

Reporting/formatting conventions

In all report types, all time measurements are reported in milliseconds.

When a report is generated from multiple logs, an additional column is added on the far left for subject number. The report begins with averages across subjects (when applicable for that report type) and then the individual summaries by subject.

See this page on using report files for more information about how reports are formatted.

Header Information

This report type contains information from the header section of the log file(s) being analyzed. It includes:

1. Subject ID

2. Subject date of birth

3. Experimenter name

4. Date and time of experiment session

5. Name and filepath of the protocol file run during the session

6. Any comments entered by the experimenter prior to the study session

Listing of media

This report type can be used to simply list which stimuli were presented on which trials, and to what location. It includes:

1. Phase in which the stimulus occurred

2. Trial in which the stimulus occurred

3. Stimulus type (audio/video/image)

4. Tag name of the stimulus. This is always a static tag name, even if the action statement that played it used a dynamic tag.

5. Side that the stimulus was presented to

The test phase in this example is actually 18 trials long - some examples are cut off for space!

Overall looking information

This report type generates some general attention measures across phases of the experiment. It includes:

1. Phase being reported

2. Average looking time per trial within the phase

3. Total looking time to all stimuli within the phase (this does not double-count attention toward two stimulus types that are active in the same location at the same time)

4. Average time from a stimulus becoming active to the participant orienting to that stimulus. Note that this is across all stimulus types (audio/video/image/lights), and includes all stimuli that were active during trials.

Overall looking time by trial

This report breaks down some of the same attention measures from the overall looking information report above by trial. Even reported per trial, it is "overall looking" because all looks to a single stimulus are totaled together. It contains:

1. Phase being reported

2. Trial number within the phase

3. Tag name of active stimulus (light_blink or light_on for lights)

4. Group name that the tag was selected from, if applicable

5. Side that the active stimulus was presented on

6. Time from when the stimulus started to when the experimenter first indicated the participant was looking in that direction. This time is reported as zero for cases in which 1) the participant was already looking in a direction when a stimulus started on that side, or 2) when the stimulus presentation begins simultaneously with the participant's look being recorded in that direction (as is the case for trial audio in HPP).

7. Total time the stimulus was active (this includes time outside the trial, if the stimulus started earlier or continued after - as seen in the HPP example below, where the side lights serve as attention-getters before a trial begins)

8. Total time the participant spent looking toward the active stimulus within that trial.

Number of looks per trial

This report includes the same information as Overall Looking Time by Trial above, with an additional column containing number of looks toward that stimulus within the trial. Looks whose total length are shorter than the COMPLETELOOK threshold are not counted as a separate look, but are combined with another look in that direction. Looks that are in-progress when a trial stimulus becomes active (the participant is already looking in the direction where the stimulus appears) are counted within the number of looks for that trial.

With a SINGLELOOKAWAY 2000 end condition for audio trials, we would expect total playing time to be the total looking time plus 2000 if there were only one look - but now we can see there were multiple looks for all these trials.

Individual looks by trial

This report gives a more detailed view of the participant's looking behavior within trials, allowing you to see the lengths of individual looks. It contains:

1. Phase the look occurred in

2. Stimulus that was active in the direction the look was recorded in (looks in directions where no stimuli were active are not reported)

3. Group that the stimulus was selected from, if applicable

4. Trial number the look occurred in (looks that occur outside a trial are not reported)

5. Length of the look in milliseconds

For this HPP log, we would normally uncheck reporting the lights to remove the redundant looks, since audio and lights always co-occur

Summary across sides

This report breaks down the time that the participant spent looking toward media (audio/video/images) in different locations, ignoring what the particular stimuli were. Having a strong bias to look to one side over another, in a study in which stimulus type and presentation location is randomized, is sometimes a reason to exclude a participant: it is unclear whether their preference for the stimuli on that side was due to the features of those particular stimuli, or simply because it was more comfortable to maintain attention to that side based on how they were positioned. This report contains:

1. The phase being reported

2. How many tags were presented to a given location within that phase

3. Total time participant spent looking toward tags in that location

4. Average time spent looking toward a tag in that location as a single look

5. Average time spent looking toward a tag in that location per trial that had active stimuli in that location

6. Percent of time participant spent looking toward that location out of total looking to all active stimulus locations within that phase

In the example below, media was presented LEFT and RIGHT, but not to any other sides. The information above is listed for each side, and the order in which sides are reported is alphabetical by side name. Percentage looking to the different locations (#6 in the list above) is always placed after all individual sides are listed; columns here are also alphabetical by side name.

In this protocol, presentation locations were psuedorandomized and not necessarily equal per phase. We can check for a side bias, and also whether our presentation locations happened to be relatively unbalanced

In calculating the percent time looking to different locations, BITTSy will include all locations that had active media during trials in that phase. It does not account for how many trials occurred on each side, or what stimulus types were present. You may wish to recalculate percentages using the other information in this report, to correct for unbalanced numbers of trials or to exclude a presentation location that had fundamentally different stimuli in your study (e.g. center training/reinforcement trials interspersed in a study where left/right trials tested learning of the training stimuli.)

Summary across groups and tags

This report gives looking time information for particular tags (across all times the tag was presented) and groups of tags. It includes:

1. Phase the group/tag was presented in. Groups/tags that are presented in multiple phases have their looking time averaged only within each phase rather than across phases.

2. Group name (or names, comma-separated, if a tag was selected from multiple groups in the course of a single phase)

3. Tag name (or (average) to report average looking time across all tag members of that group that were presented in the phase)

4. Looking time per trial of the phase in which the group/tag was presented

The example above comes from a protocol similar in structure to this HPP example, in which participants hear 6 audio files repeated across 3 blocks of trials. In between trials, audio attention-getter clips (in the group ags) are played to help orient the child toward the blinking side lights - these end as trials start, and thus do not appear in any trials or accumulate any looking time. In this report, we can see from the testblock1, testblock2, and testblock3 averages (our three blocks of trials, in chronological order) that looking time was greater toward the start of the experiment. Our main items of interest in this HPP study are the average looking times for the name and foil audio files presented in the test phase.

Detailed looking

This report generates a row for every 50 milliseconds during each of your experiment's trials, and reports what was happening at that time by filling in time between events in the detailed log file. This can be used to generate a time-course of looking behavior in any live-coded experiment. Keep in mind that it is a rough time-course! This granularity of 50ms was chosen as conservative estimate of keyboard input delay. However, inaccuracies due to experimenter reaction times still exist, and we generally recommend offline coding of looking behavior for studies such as preferential looking paradigm that typically require more fine-grained analyses of looking time.

This report contains:

1. Current phase

2. Trial in which the time was reached (timepoints outside of trial start/stop flags are not reported)

3. Current time, as expressed from the start of the experiment (when the experimenter clicked Run Protocol)

4. Current time, as expressed from the start of the current trial (times that coincide with trial start/stop events are reported as Trial Start and Trial Stop)

5. Most recent key pressed by experimenter at the current timepoint

6. Stimuli that were active at the current timepoint, comma-separated

7. Sides that the active stimuli were present on, comma-separated and corresponding in order to their respective stimulus/tag in the ActiveStimuli column

Key assignments are not included in log files, so to know which stimulus a participant was looking at based on the most recent experimenter keypress, you would need to match keys with the sides to which they were assigned in your protocol file. Then, some simple conditional formulas in Excel can help you generate a column of tag names that were attended to across timepoints in the study.

Habituation

This report is designed especially for studies that have a habituation phase using CRITERIONMET. It has three sections, in addition to the standard header.

1. Habituation settings, consisting of:

   1. Window size

   2. Window overlap

   3. Criterion reduction

   4. Basis chosen (LONGEST or FIRST)

   5. Window type (SLIDING or FIXED)

   6. Basis minimum time

2. Information on the habituation phase (identified as the one containing the CRITERIONMET condition - it can be named as you wish)

   1. Whether or not habituation criteria were met

   2. How many trials before the participant reached habituation (n/a if they did not habituate)

3. Trial and looking time information across phases

   1. Current phase

   2. Trial number within the current phase

   3. Active trial stimulus tag

   4. Group the tag was selected from, if applicable

   5. Side the tag was presented on

   6. Time from when the stimulus started to when the experimenter first indicated the participant was looking in that direction. This time is reported as zero for cases in which 1) the participant was already looking in a direction when a stimulus started on that side, or 2) when the stimulus presentation begins simultaneously with the participant's look being recorded in that direction

   7. Total time the stimulus was active (this includes time outside the trial, if the stimulus started earlier or continued after)

   8. Total time the participant spent looking toward the active stimulus within that trial.

The example report above comes from a run of this example protocol of habituation to a category.

All event info

This report simply outputs the detailed log file(s) that were loaded into the reporting module into a CSV, with the date, time, and event separated into columns. This can then be analyzed with a custom script or macro, if desired.