Experiment builder notes
Notes related to setting up behavioural experiments and such.
|
SR Research builds a specific eye tracker, and has their own experimentation environment
https://www.sr-research.com/experiment-builder/
Admin rights and manifest
AFAICT
For context:
- If Experiment Builder 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.
- there is the idea that a process with high priority[1] set with will be scheduled on the CPU more easily - which doesn't mean timing magically gets much better, but timing doesn't get get worse when there is another insistent program running
- the better solution is not to have another program like that, because this isn't even a real fix, just a band-aid. That said, it can't hurt and it can help.
- also there is potentially some hardware / syscalls that security says only admins are allowed to do, in which case the experiment would not even function without admin access. This should be rare and won't apply to the eye tracker itself.
- If you log in with your department account managed by someone else, you are probably not an administrator
- whereas if the PC is set up to automatically log in (or there's a specific account everyone knows), this is probably is an admin account and this section is not relevant.
Experiment Builder defaults to ask for admin rights.
If you don't have admin rights, and don't think you need them, 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")
In newer versions of Experiment Builder (2.3) the manifest is embedded, so the only option is to set it before deploying.
With previous versions of Experiment Builder you could do this later, because this demand was recorded in a separate file (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