Problems with AAT - software problem?


Problems with AAT - software problem?

Author
Message
c.witteki
c.witteki
Associate Member
Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)

Group: Awaiting Activation
Posts: 15, Visits: 38
Hi again,

in a study I use the mouse AAT, however, it is not working in the intended way:
when participants are instructed to pull the mouse, the pictures remains on the screen although the response direction is correct. In contrast, when pictures are pushed (irrespective of instruction), the pictures disappear (importantly, the AAT is running on other computers, thus, the computers that are used seem to be the problem). As the computers are rather old, I was wondering whether the graphic card (AMD Radeon (TM) HD 8350) or the system (e.g., RAM (8 GB) or processor (Intel (R) Core (TM) i5-4590 CPU@ 3.30GHz) might be responsible. Are there any minimum requirements to run the mouse AAT?

Thanks in advance for your help,

best
Charlotte

Dave
Dave
Supreme Being
Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)

Group: Administrators
Posts: 7.7K, Visits: 32K
c.witteki - Monday, December 05, 2016
Hi again,

in a study I use the mouse AAT, however, it is not working in the intended way:
when participants are instructed to pull the mouse, the pictures remains on the screen although the response direction is correct. In contrast, when pictures are pushed (irrespective of instruction), the pictures disappear (importantly, the AAT is running on other computers, thus, the computers that are used seem to be the problem). As the computers are rather old, I was wondering whether the graphic card (AMD Radeon (TM) HD 8350) or the system (e.g., RAM (8 GB) or processor (Intel (R) Core (TM) i5-4590 CPU@ 3.30GHz) might be responsible. Are there any minimum requirements to run the mouse AAT?

Thanks in advance for your help,

best
Charlotte

It seems more likely that when you pull the mouse, the mouse coordinates never actually reach the border of the screen. Try the following:

Do a search & replace in the script and replace all instances of "display.height" with "display.canvasheight" (without the double-quotes).

c.witteki
c.witteki
Associate Member
Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)Associate Member (178 reputation)

Group: Awaiting Activation
Posts: 15, Visits: 38
Dave - Monday, December 05, 2016
c.witteki - Monday, December 05, 2016
Hi again,

in a study I use the mouse AAT, however, it is not working in the intended way:
when participants are instructed to pull the mouse, the pictures remains on the screen although the response direction is correct. In contrast, when pictures are pushed (irrespective of instruction), the pictures disappear (importantly, the AAT is running on other computers, thus, the computers that are used seem to be the problem). As the computers are rather old, I was wondering whether the graphic card (AMD Radeon (TM) HD 8350) or the system (e.g., RAM (8 GB) or processor (Intel (R) Core (TM) i5-4590 CPU@ 3.30GHz) might be responsible. Are there any minimum requirements to run the mouse AAT?

Thanks in advance for your help,

best
Charlotte

It seems more likely that when you pull the mouse, the mouse coordinates never actually reach the border of the screen. Try the following:

Do a search & replace in the script and replace all instances of "display.height" with "display.canvasheight" (without the double-quotes).

Hi Dave, thanks for your reply. I searched the script for "display.height", however, this command does not appear. There is one instance /Maxheight = display.canvasheight, but that´s it. Do you have any other ideas?
Thanks,
Charlotte

Dave
Dave
Supreme Being
Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)Supreme Being (198K reputation)

Group: Administrators
Posts: 7.7K, Visits: 32K
c.witteki - Tuesday, December 06, 2016
Dave - Monday, December 05, 2016
c.witteki - Monday, December 05, 2016
Hi again,

in a study I use the mouse AAT, however, it is not working in the intended way:
when participants are instructed to pull the mouse, the pictures remains on the screen although the response direction is correct. In contrast, when pictures are pushed (irrespective of instruction), the pictures disappear (importantly, the AAT is running on other computers, thus, the computers that are used seem to be the problem). As the computers are rather old, I was wondering whether the graphic card (AMD Radeon (TM) HD 8350) or the system (e.g., RAM (8 GB) or processor (Intel (R) Core (TM) i5-4590 CPU@ 3.30GHz) might be responsible. Are there any minimum requirements to run the mouse AAT?

Thanks in advance for your help,

best
Charlotte

It seems more likely that when you pull the mouse, the mouse coordinates never actually reach the border of the screen. Try the following:

Do a search & replace in the script and replace all instances of "display.height" with "display.canvasheight" (without the double-quotes).

Hi Dave, thanks for your reply. I searched the script for "display.height", however, this command does not appear. There is one instance /Maxheight = display.canvasheight, but that´s it. Do you have any other ideas?
Thanks,
Charlotte

Okay, thanks. We need to figure out what's happening on those systems then. For background: The script determines when a stimulus has been "fully zoomed in" based on the mouse coordinates:

<trial increase>
...

/branch = [if (trial.increase.responsey >= values.maxheight-1)
                {values.mouse_y = trial.increase.responsey; values.endtime = script.elapsedtime; values.finalresponse = "PULL"; trial.endincrease}]

...
</trial>

My theory still is that this just never happens because -- for some reason -- the mouse never reaches the required coordinates for the above conditiont to fire:

trial.increase.responsey >= values.maxheight-1

There are a couple of things you can do:
- For a quick fix, you can try relaxing the condition by say doing something like

trial.increase.responsey >= values.maxheight-6

- To really figure out what happens, you would have to modify the script and log the actual mouse coordinates (change the /recorddata attributes in the various increase / decrease trials to 'true', log the respective responsey and mousey properties to the data file, log display.height and display.canvasheight). Those would show which coordinates the mouse is actually able to reach on those systems. See e.g. this thread for a similar problem: https://www.millisecond.com/forums/FindPost17073.aspx
- As for what prevents the mouse from working properly on those systems, there are a couple of possibilities: You may have some piece of software installed that messes with the mouse / remaps its coordinates. If the systems have multiple monitors with different sizes attached, that can also mess things up.

Let me know what you find regarding the mouse coordinates and we'll take it from there.

GO


Reading This Topic


Login
Existing Account
Email Address:


Password:


Social Logins

Select a Forum....






Millisecond Forums


Search