Experiment builder notes: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 14: | Line 14: | ||
For context: | For context: | ||
* If | * 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. | ||
* there is the idea that a process with high priority[https://learn.microsoft.com/en-us/windows/win32/procthread/scheduling-priorities] set with will be scheduled on the CPU more easily | * why does it ask for admin rights? | ||
:: the better | : there is the idea that a process with high priority[https://learn.microsoft.com/en-us/windows/win32/procthread/scheduling-priorities] 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 log in with your department account managed by someone else, you are probably not an administrator | * 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. | : 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. | ||
--> | |||
* 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") | |||
Experiment Builder | : 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 - so if you deployed with the setting to ask for admin rights, you could alter that later without redeploying ((deleting the manifest file would apparently also work{{verify]]): | |||
Find the <tt>.manifest</tt> file alongside the experiment, edit the {{inlinecode|level}} part {{comment|(documented [https://learn.microsoft.com/en-us/previous-versions/bb756929(v=msdn.10)?redirectedfrom=MSDN here])}}: | |||
<requestedExecutionLevel level="requireAdministrator" uiAccess="False"> | <requestedExecutionLevel level="requireAdministrator" uiAccess="False"> | ||
You could either change that level= value to asInvoker | You could either change that level= value to asInvoker: | ||
<requestedExecutionLevel level="asInvoker" uiAccess="False"> | <requestedExecutionLevel level="asInvoker" uiAccess="False"> | ||
Revision as of 11:47, 1 July 2024
Notes related to setting up behavioural experiments and such.
|
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 - so if you deployed with the setting to ask for admin rights, you could alter that later without redeploying ((deleting the manifest file would apparently also work{{verify]]):
Find the .manifest file alongside the experiment, edit the level part {{{1}}}:
<requestedExecutionLevel level="requireAdministrator" uiAccess="False">
You could either change that level= value to asInvoker:
<requestedExecutionLevel level="asInvoker" uiAccess="False">
http://sr-research.jp/support/files/a2ab23fd3769ea34af5d83a3429be0e2.pdf