Change Detection task

Jump to: navigation, search
Screen shot of PEBL's Change Detection task.


[edit] About

An implementation of the 'flicker' paradigm, but using

[edit] Notes

There are four conditions, each of which involves a different type of change.

  • 1 =movement (location)
  • 2 = present/absent
  • 3 =color
  • 4 =size

[edit] Options

   gTolerance <- 30           #How close you have to get to count as correct
   gUseBackground  <- 0  ##Whether to use a faked background with many circles
   gCircles <- 50  #Number of circles in field
                   ## 20 is pretty easy; 50 is a bigger challenge
   gRadMin <- 10   ## Minimum circle radius
   gRadMax <- 30   ## Maximum circle radius

   gXMin <- 100    ##left bound of field
   gXMax <- 700    ##right bound of field
   gYMin <- 100    ##top bound of field
   gYMax <- 500    ##Bottom bound of field
   gShowTime <- 400     ##How long to show field
   gScreenTime <- 100   ##how long to show screen
   condsize <- 5        ##Number of trials per condition

[edit] Data Output

Data output is saved in a .csv file:

  • x1,y1,r1,col1 specify the change object on first screen
  • x2,y2,r2,col2 specify change object on the second screen

For the output, each trial has two screens that differ by a single aspect (color, size, location). The xy position, radius, and color of that shape is specified by the x y r col columns. The cond specifies which one of these aspects changed.

[edit] References

[edit] See Also

PEBL Test Battery

Personal tools