Experiment builder notes

Notes related to setting up behavioural experiments and such. Experiment design Hardware and timing Experiment building - on timing · on online experiments · on counterbalancing E-Prime notes · PsychoPy notes · Experiment builder notes · Gorilla notes · PsychToolbox notes · OpenSesame notes · DMDX notes

SR Research builds eye trackers, and has their own experimentation environment called Experiment Builder.

It's not the only way to use their eye trackers, but unless you have specific needs it may be the easiest.

Admin rights and manifest

✎ This article/section is a stub — some half-sorted notes, not necessarily checked, not necessarily correct. Feel free to ignore, or tell me about it.

AFAICT

For context:

• If running the experiment asks for admin rights, and you are not, it will pop up some sort of "please log in as admin", and will refuse to run if you do not.

• why does it ask for admin rights?

there is the idea that a process with high priority[1] set with will be scheduled on the CPU more easily

this doesn't make timing better

...but it can avoid it getting worse when there is another program loading the CPU

you can argue that

admin rights to do that is a band-aid and the better fix is to not have programs like that running

it can't hurt, and it can help, particularly in situations where you cannot guarantee that yourself (e.g. PC is managed by your department)

• in a few cases, you might not be able to access specific hardware without admin rights

you can tell by your experiment not functioning at all

won't apply to the eye tracker itself, and should be rare in general

• if you cannot get admin rights anyway (e.g. you are a regular user on a PC managed by someone else)

then you can disable the request for admin rights before deploying.

(it's in Edit → Preferences → Build/Deploy (near the bottom) → "Deploy Without Administrative Rights")

what this does is record whether or not

in newer versions of Experiment Builder (2.3) the manifest is embedded in the compiled experiment, so the only option is to set it before deploying

in older versions this went to the manifeset file, which was separate - and you could edit that file after deploying if you wanted:

This was recorded in the .manifest), specifically the level part (documented here):

<requestedExecutionLevel level="requireAdministrator" uiAccess="False">

You could either change that level= value to asInvoker:

<requestedExecutionLevel level="asInvoker" uiAccess="False">

It would apparently also work to just delete the manifest file(verify).

http://sr-research.jp/support/files/a2ab23fd3769ea34af5d83a3429be0e2.pdf

https://www.hse.ru/mirror/pubs/share/560338913.pdf