| Author |
 Topic  |
|
|
debra.cooper
Starting Member
USA
4 Posts |
 Posted - Mar 14 2007 : 3:54:25 PM
|
| I ran a subject yesterday using CIGAL and instructed the subject only the left two buttons were supposed to be pressed. After each run, the button responses were combinations of presses from buttons 1, 2, 4, 6, 16, and 18. I tested the subject's button presses and only the first two buttons flashed whenever she pressed them. I was wondering what the button reponses 4, 6, 16, and 18 are referring to. |
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - Mar 14 2007 : 4:04:36 PM
|
Each button box generates its own response values for each button. The pattern you describe suggests that this was a binary-coded box that sends 1,2,4,8, or 16 for each button, but for some reason you are getting combinations 6 and 18. Which button box were you using and on which scanner? This pattern almost makes sense, but not if you were using the normal joystick box.
If you could send me CIGAL's "pdigm" output file for a problem run I could probably figure out what was happening.
Jim
|
 |
|
|
felder
BIAC
17 Posts |
Posted - Oct 04 2007 : 12:13:27 PM
|
I had a similar issue yesterday at the 4T. The participant was using the 4-button box (with joystick on top), and was instructed to press only two buttons.
During the 4th run cigal indicated:
Button 2 - pressed 21x
Button 4 - pressed 140x
Button 16- pressed 40x
Button 18- pressed 4x
Button 20- pressed 34x
And during the 5th run:
Button 2 - pressed 8x
Button 4 - pressed 36x
Button 16- pressed 212x
Button 18- pressed 23x
Button 20- pressed 170x
The .out files are not exactly consistent with what cigal indicates.
Any ideas? |
|
|
|
jim.voyvodic
BIAC Faculty
138 Posts |
Posted - Oct 04 2007 : 4:26:40 PM
|
The variable results appear to be because the button box is sending spurious 16 codes at a fairly high rate. The 1 and 2 buttons are coded as 2 and 4, so presumably those values make sense. The 16's are button 4 signals coming in on their own, while the 18's and 20's are button 4 signals coming while button 2 or 4 is pressed (the values simply add).
So, there is apparently a hardware problem (an unstable button or wire) causing the funny code values. We'll get somebody to look into that.
For the scans you already have you should be able to filter all the 16 transition signals out of our behavioral data using the response log data stored in CIGAL's 'pdigm' output file. If you need help on that please come see me.
Jim |
|
|
| |
Topic |
|
|
|
button responses with cigal
