attentionNetworkTest [iCub modules]

The attentionNetworkTest module generates a sequence of images that implement the Attention Network Test (ANT) developed by Michael Posner and his coworkers (see Fan et al. More...

The attentionNetworkTest module generates a sequence of images that implement the Attention Network Test (ANT) developed by Michael Posner and his coworkers (see Fan et al.

2002, below).

J. Fan, B. D. McCandliss, T. Sommer, A. Raz, and M. I. Posner (2002). Testing the Efficiency and Independence of Attentional Networks, Journal of Cognitive Neuroscience, 14:3, 340 – 347.

The current version has some restrictions:

• The module doesn't provide a facility for interaction with a participant and, specifically, for signalling when the orientation of the target is recognized. Consequently, the current sequence displays the target and flanker image for the full allowed reaction time. ANT should only present this image until the participant responds after which a post-target fixation image is shown.
• There are 48 distinct trials (4 cue conditions x 2 target lcoations x 2 target directions x 3 flanker conditions). ANT presents these trials in random order, with two repetitions (96 trials in total). However, currently, the modules presents the 48 trials in a fixed order and it repeats this set of trial continuously. The pattern of presentation cycles though each variable as follows:
  1. for each cue condition
  2. for each location
  3. for each direction
  4. vary flanker condition

Dependencies

YARP.

Parameters

Command Line Parameters

The following key-value pairs can be specified as command-line parameters by prefixing -- to the key (e.g. --from file.ini. The value part can be changed to suit your needs; the default values are shown below.

• from attentionNetworkTest.ini
  specifies the configuration file

• context attentionNetworkTest/conf
  specifies the sub-path from $ICUB_ROOT/icub/app to the configuration file

• name attentionNetworkTest
  specifies the name of the module (used to form the stem of module port names)

• robot icub
  specifies the name of the robot (used to form the root of robot port names)

Configuration File Parameters

The following key-value pairs can be specified as parameters in the configuration file (they can also be specified as command-line parameters if you so wish). The value part can be changed to suit your needs; the default values are shown below.

• ANTimageOutPort /ANTimage:o
  specifies the image output port

• d1 1600
  specifies the duration in milliseconds of the fixation image

• d2 100
  specifies the duration in milliseconds of the cue image

• d3 400
  specifies the duration in milliseconds of the fixation image

• d4 1700
  specifies the duration in milliseconds of the target image

• d5 0
  specifies the duration in milliseconds of the fixation image (4000 - d1 - d2 - d3 - d4); note that d3 is maximum reaction time RT

• database ANTdatabase
  specifies the directory name in which the database of images will be stored

• path ~/iCub/app/attentionNetworkTest
  specifies the path the to directory in which the database of images will be stored

The database parameter specifies the name of the directory in which the database of images is stored. This directory must be created before running the module.

The path parameter specifies the full path to the database directory. This is where the where the database of image files is stored.

For example, if the configuration file attentionNetworkTest.ini is located in C:/iCub/app/attentionNetworkTest/conf and the database is C:/iCub/app/attentionNetworkTest/ANTdatabase then

• attentionNetworkTest module must be invoked with --context attentionNetworkTest/conf
• attentionNetworkTest.ini must contain "path C:/iCub/app/attentionNetworkTest"
• the directory C:/iCub/app/attentionNetworkTest/ANTdatabase must exist.

The database must comprise the following ANT images

• ANT00 fixation
• ANT01 cue centre
• ANT02 cue top and bottom
• ANT03 cue top
• ANT04 cue bottom
• ANT05 target neutral top right
• ANT06 target neutral bottom right
• ANT07 target neutral top left
• ANT08 target neutral bottom left
• ANT09 target congurent top right
• ANT10 target congurent bottom right
• ANT11 target congurent top left
• ANT12 target congurent bottom left
• ANT13 target incongurent top right
• ANT14 target incongurent bottom right
• ANT15 target incongurent top left
• ANT16 target incongurent bottom left

Ports Accessed

None

Ports Created

Input ports

None

Output ports

• /attentionNetworkTest/ANTimage:o

The functional specification only names the ports to be used to communicate with the module but doesn't say anything about the data transmitted on the ports. This is defined by the following code.

I/O Port Types & Naming

• BufferedPort<ImageOf<PixelRgb> > ANTimageOutPort;

Input Data Files

ANTdatabase (see above)

Output Data Files

None

Configuration Files

attentionNetworkTest.ini (see above)

Tested OS

Linux and Windows

Example Instantiation of the Module

attentionNetworkTest --context attentionNetworkTest/conf --from attentionNetworkTest.ini

Author:

David Vernon

Copyright (C) 2009 RobotCub Consortium

CopyPolicy: Released under the terms of the GNU GPL v2.0.

This file can be edited at src/attentionNetworkTest/include/iCub/attentionNetworkTestModule.h