<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://tsgdoc.socsci.ru.nl/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=H.voogd</id>
	<title>TSG Doc - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="http://tsgdoc.socsci.ru.nl/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=H.voogd"/>
	<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php/Special:Contributions/H.voogd"/>
	<updated>2026-05-10T08:10:23Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.4</generator>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5895</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5895"/>
		<updated>2025-02-13T09:09:26Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Template:Infobox_tsg/doc&amp;diff=5882</id>
		<title>Template:Infobox tsg/doc</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Template:Infobox_tsg/doc&amp;diff=5882"/>
		<updated>2025-02-10T09:41:57Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{documentation subpage}}&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&amp;lt;pre style=&amp;quot;overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
{{Infobox tsg&lt;br /&gt;
| child          = &lt;br /&gt;
| name           = &lt;br /&gt;
| title          = &lt;br /&gt;
| image          = &lt;br /&gt;
| image size     = &lt;br /&gt;
| image alt      = &lt;br /&gt;
| caption        = &amp;lt;!-- Image name is enough --&amp;gt;&lt;br /&gt;
| location       =&lt;br /&gt;
| header1        = &lt;br /&gt;
| label1         = &lt;br /&gt;
| data1          = &lt;br /&gt;
| manuals        = &amp;lt;!-- List of links --&amp;gt;&lt;br /&gt;
| downloads      = &amp;lt;!-- List of links --&amp;gt;&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
{{Clear}}&lt;br /&gt;
&lt;br /&gt;
== Example ==&lt;br /&gt;
{{Infobox tsg&lt;br /&gt;
| name           = Physical Place Holder&lt;br /&gt;
| image          = placeholder.png&lt;br /&gt;
| caption        = The device in action&lt;br /&gt;
| downloads      = {{bulleted list&lt;br /&gt;
      | [[Main Page|Installer]]&lt;br /&gt;
      | [[Main Page|Drivers]]&lt;br /&gt;
  }}&lt;br /&gt;
| manuals        = {{bulleted list&lt;br /&gt;
      | [[Main Page|Quick Start Guide]]&lt;br /&gt;
      | [[Main Page|Reference Guide]]&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;pre style=&amp;quot;overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
{{Infobox tsg&lt;br /&gt;
| name           = Physical Place Holder&lt;br /&gt;
| image          = placeholder.png&lt;br /&gt;
| caption        = The device in action&lt;br /&gt;
| downloads      = {{bulleted list&lt;br /&gt;
      | [[Main Page|Installer]]&lt;br /&gt;
      | [[Main Page|Drivers]]&lt;br /&gt;
  }}&lt;br /&gt;
| manuals        = {{bulleted list&lt;br /&gt;
      | [[Main Page|Quick Start Guide]]&lt;br /&gt;
      | [[Main Page|Reference Guide]]&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
=== Embedded === &lt;br /&gt;
{{Infobox&lt;br /&gt;
| title = Embedded Example&lt;br /&gt;
| label1 = label1&lt;br /&gt;
|  data1 = data1&lt;br /&gt;
| label2 = label2&lt;br /&gt;
|  data2 = data2&lt;br /&gt;
|  data3 =&lt;br /&gt;
 {{Infobox tsg&lt;br /&gt;
  | child = yes&lt;br /&gt;
  | downloads = *[[Main Page|Link]]&lt;br /&gt;
 }}&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;pre style=&amp;quot;overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
{{Infobox&lt;br /&gt;
| title = Embedded Example&lt;br /&gt;
| label1 = label1&lt;br /&gt;
|  data1 = data1&lt;br /&gt;
| label2 = label2&lt;br /&gt;
|  data2 = data2&lt;br /&gt;
|  data3 =&lt;br /&gt;
 {{Infobox tsg&lt;br /&gt;
  | child = yes&lt;br /&gt;
  | downloads = *[[Main Page|Link]]&lt;br /&gt;
 }}&lt;br /&gt;
}}&lt;br /&gt;
&amp;lt;/p&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Parameters ==&lt;br /&gt;
All parameters are optional.&lt;br /&gt;
&lt;br /&gt;
; child&lt;br /&gt;
: Whether the infobox is placed embedded in an other infobox. The infobox will be styled accordingly. If embedded, the name/title will not be displayed. For technical reasons, anything for this parameter has the same effect, be it &amp;quot;yes&amp;quot;, &amp;quot;no&amp;quot; or anything else. To nullify the effect of this parameter, you need to omit it.&lt;br /&gt;
; name&lt;br /&gt;
: Name of the infobox. Can affect the title of the infobox but its primary use is to help retrieve release data from outside the article. In such cases, if you want to edit the title at the top of the infobox, use the {{para|title}} parameter instead.&lt;br /&gt;
::'''Attention:''' Please do not include a wikilink, hyperlink or image in this parameter. This parameter should be composed of pure text.&lt;br /&gt;
; title&lt;br /&gt;
: Name of the software product as displayed above the infobox. When not specified, contents of {{para|name}} parameter will be displayed instead.&lt;br /&gt;
:'''Important note:''' Please do not include an image in this field.&lt;br /&gt;
; bodystyle&lt;br /&gt;
: CSS styling for the infobox as a whole. Don't touch unless you know what you're doing.&lt;br /&gt;
; image&lt;br /&gt;
: Code for an image to be displayed at the top of the infobox. You may specify a full image syntax or just a file name, with or without namespace prefix. In other words, the following examples are all acceptable:&lt;br /&gt;
::placeholder.png&lt;br /&gt;
::File:placeholder.png&lt;br /&gt;
::Image:placeholder.png&lt;br /&gt;
::&amp;lt;nowiki&amp;gt;[[File:placeholder.png|64px]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
::&amp;lt;nowiki&amp;gt;[[Image:placeholder.png|64px]]&amp;lt;/nowiki&amp;gt;&lt;br /&gt;
; image size&lt;br /&gt;
: Size of the image. Defaults to 300px.&lt;br /&gt;
; image alt&lt;br /&gt;
: Alternative text of the image; very important.&lt;br /&gt;
; caption&lt;br /&gt;
: Caption of the image that appears below it.&lt;br /&gt;
; location&lt;br /&gt;
: Room number.&lt;br /&gt;
; header1&lt;br /&gt;
: Some space left to possibly include other information before the resource links, or for a custom resource header.&lt;br /&gt;
; label1&lt;br /&gt;
: Some space left to possibly include other information before the resource links.&lt;br /&gt;
; data1&lt;br /&gt;
: Some space left to possibly include other information before the resource links.&lt;br /&gt;
; downloads&lt;br /&gt;
: Designed to take a list of (download) links using something like {{tl|bulleted list}}.&lt;br /&gt;
; manuals&lt;br /&gt;
: Designed to take a list of links (to manuals) using something like {{tl|bulleted list}}.&lt;br /&gt;
&lt;br /&gt;
&amp;lt;includeonly&amp;gt;&lt;br /&gt;
&amp;lt;!-- ADD CATEGORIES BELOW THIS LINE --&amp;gt;&lt;br /&gt;
&amp;lt;!-- ADD INTERWIKIS BELOW THIS LINE --&amp;gt;&lt;br /&gt;
&amp;lt;/includeonly&amp;gt;&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5881</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5881"/>
		<updated>2025-02-10T09:31:54Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5880</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5880"/>
		<updated>2025-02-10T09:29:51Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5879</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5879"/>
		<updated>2025-02-10T09:18:27Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5878</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5878"/>
		<updated>2025-02-10T09:12:11Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
     }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5877</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5877"/>
		<updated>2025-02-10T09:11:26Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        |  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        |  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        |  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        |  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        |  []&lt;br /&gt;
        |  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
     }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5876</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5876"/>
		<updated>2025-02-10T09:08:55Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5875</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5875"/>
		<updated>2025-02-10T09:02:24Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5874</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5874"/>
		<updated>2025-02-10T09:01:06Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Course Template]]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5873</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5873"/>
		<updated>2025-02-10T09:00:46Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5872</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5872"/>
		<updated>2025-02-10T08:59:48Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [Media:TemplatePsychopy2019.zip|Template  Course template]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5871</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5871"/>
		<updated>2025-02-10T08:59:03Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Template]  Course template]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5870</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5870"/>
		<updated>2025-02-05T14:10:49Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.10.11 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv. And is available in the Windows Start Menu.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5869</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5869"/>
		<updated>2025-02-05T13:49:28Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when you are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.10.11.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=38 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.8.10.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=310 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.10 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5868</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5868"/>
		<updated>2025-02-05T13:47:08Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate. TSG does not support Psychopy Builder. Neither does TSG make any projects in Psychopy Builder. TSG can provide some labsupport when yoou are using the Builder. TSG does support Psychopy Coder and TSG uses Psychopy elements to create experiments. There are sample experiments to download from the infobox on this page.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5867</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5867"/>
		<updated>2025-02-05T13:44:42Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5866</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5866"/>
		<updated>2025-02-05T13:38:20Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5865</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5865"/>
		<updated>2025-02-05T13:37:46Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        |* [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        |* []&lt;br /&gt;
        |*  [Branches:]&lt;br /&gt;
        |*  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        |*  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        |*  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        |*  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        |*  []&lt;br /&gt;
        |*  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
     }}&lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5864</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5864"/>
		<updated>2025-02-05T13:36:17Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install  installation files for Psychopy2024.2.4] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5863</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5863"/>
		<updated>2025-02-05T13:35:43Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
        *  []&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install] &lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.10.11 64 bits installed. Psychopy recommends Python 3.10.11 or 3.8.10 TSG recommends Python 3.10.11&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.2.4install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5862</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5862"/>
		<updated>2025-02-05T13:32:25Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * []&lt;br /&gt;
        *  [Branches:]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound?ref_type=heads    basic example with text and picture and sound]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-microphone?ref_type=heads    basic example with text and picture and microphone]&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text-sound-microphone?ref_type=heads    basic example with text and picture and sound and microphone]&lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.1.0install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5861</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5861"/>
		<updated>2025-02-05T13:30:23Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/tsg/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * &lt;br /&gt;
        *  Branches:&lt;br /&gt;
        *  [https://gitlab.socsci.ru.nl/tsg/psychopytemplate/-/tree/basic-picture-text?ref_type=heads    basic example with text and picture]&lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.1.0install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5834</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5834"/>
		<updated>2024-08-20T13:16:21Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/utilities/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/utilities/psychopytemplate/-/blob/main/runexperiment.py?ref_type=heads  MainCode for Template / Working Example]&lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl/tsg/psychopy2024.1.0install&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Pylink is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Studio ===&lt;br /&gt;
Check this link to connect to Tobii Studio:&lt;br /&gt;
https://gitlab.socsci.ru.nl/h.voogd/tobiiclearviewtriggerapipython3&lt;br /&gt;
the tobii-research package is installed on our lab computers.&lt;br /&gt;
&lt;br /&gt;
=== For Tobii Pro Lab ===&lt;br /&gt;
Tobii-research is installed on our lab computers. Titta (https://github.com/marcus-nystrom/Titta) is not working on a two-computer-system.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5833</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5833"/>
		<updated>2024-08-20T13:03:50Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = &lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/utilities/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/utilities/psychopytemplate/-/blob/main/runexperiment.py?ref_type=heads  MainCode for Template / Working Example]&lt;br /&gt;
   &lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Eyelink users should follow the regular instructions above. Additionally, in the installer folder from our Gitlab, find the pylink version you need, rename it to '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5832</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5832"/>
		<updated>2024-08-20T13:01:47Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        * [[https://gitlab.socsci.ru.nl/utilities/psychopytemplate  Template / Working Example]&lt;br /&gt;
        * [https://gitlab.socsci.ru.nl/utilities/psychopytemplate/-/blob/main/runexperiment.py?ref_type=heads  MainCode for Template / Working Example]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Eyelink users should follow the regular instructions above. Additionally, in the installer folder from our Gitlab, find the pylink version you need, rename it to '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5831</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5831"/>
		<updated>2024-08-20T13:00:31Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[https://gitlab.socsci.ru.nl/utilities/psychopytemplate  Template / Working Example]&lt;br /&gt;
        | [https://gitlab.socsci.ru.nl/utilities/psychopytemplate/-/blob/main/runexperiment.py?ref_type=heads  MainCode for Template / Working Example]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Eyelink users should follow the regular instructions above. Additionally, in the installer folder from our Gitlab, find the pylink version you need, rename it to '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5830</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5830"/>
		<updated>2024-08-20T12:58:48Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [https://gitlab.socsci.ru.nl/utilities/psychopytemplate  Template / Working Example]&lt;br /&gt;
        | [https://gitlab.socsci.ru.nl/utilities/psychopytemplate/-/blob/main/runexperiment.py?ref_type=heads  MainCode for Template / Working Example]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Eyelink users should follow the regular instructions above. Additionally, in the installer folder from our Gitlab, find the pylink version you need, rename it to '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5829</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5829"/>
		<updated>2024-08-20T12:56:30Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [https://gitlab.socsci.ru.nl/utilities/psychopytemplate  Template / Working Example]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Eyelink users should follow the regular instructions above. Additionally, in the installer folder from our Gitlab, find the pylink version you need, rename it to '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Python&amp;diff=5812</id>
		<title>Python</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Python&amp;diff=5812"/>
		<updated>2024-04-23T14:42:30Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox software&lt;br /&gt;
| name                   = Python&lt;br /&gt;
| logo                   = Python-logo-generic.svg&lt;br /&gt;
| logo size              = 180px&lt;br /&gt;
| logo alt               = Python(tm)&lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = 3.7.9 64-bits&lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| website                = [http://www.python.org python.org]&lt;br /&gt;
| resources              = {{Infobox tsg&lt;br /&gt;
  | child = yes&lt;br /&gt;
  | header2 = Workshop&lt;br /&gt;
  | data2 = {{bulleted list&lt;br /&gt;
      | [[Workshop: Python for behavioural scientists|Python for behavioural scientists]]&lt;br /&gt;
  }}&lt;br /&gt;
 }}  &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[wikipedia:Python_(programming_language)|Python]] is a general-purpose, high-level programming language. It is also a [[wikipedia:Python_%28genus%29|type of snake]] and a [[wikipedia:Python_%28Efteling%29|rollercoaster]], but one is arguably more relevant to your research than the others. &amp;lt;br/&amp;gt;&lt;br /&gt;
On the lab computers, there is support for Spyder, PyCharm and [[Psychopy]]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Table of Contents will be generated here --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Psychopy==&lt;br /&gt;
{{see |Psychopy}}&lt;br /&gt;
&lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our lab computers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
===Example: TestArgs.py===&lt;br /&gt;
Execute the following script within the commandline (CMD): &amp;lt;code style=&amp;quot;background-color:#000; color:#fff; padding:1px 3px;&amp;quot;&amp;gt;python testArgs.py a.&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
You should see the following result:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;python&amp;quot; overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
number of argument:  2&lt;br /&gt;
 argv[0]: ./testArgs.py&lt;br /&gt;
 argv[1]: a&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Psychopy]]&lt;br /&gt;
*[[Workshop: Python for social scientists]]&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 ==References==&lt;br /&gt;
&amp;lt;references /&amp;gt; --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==External Links== &lt;br /&gt;
*{{Official website|http://www.python.org}}&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Python&amp;diff=5811</id>
		<title>Python</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Python&amp;diff=5811"/>
		<updated>2024-04-23T14:42:04Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox software&lt;br /&gt;
| name                   = Python&lt;br /&gt;
| logo                   = Python-logo-generic.svg&lt;br /&gt;
| logo size              = 180px&lt;br /&gt;
| logo alt               = Python(tm)&lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = 3.7.9 64-bits&lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| website                = [http://www.python.org python.org]&lt;br /&gt;
| resources              = {{Infobox tsg&lt;br /&gt;
  | child = yes&lt;br /&gt;
  | header2 = Workshop&lt;br /&gt;
  | data2 = {{bulleted list&lt;br /&gt;
      | [[Workshop: Python for behavioural scientists|Python for behavioural scientists]]&lt;br /&gt;
  }}&lt;br /&gt;
 }}  &lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[wikipedia:Python_(programming_language)|Python]] is a general-purpose, high-level programming language. It is also a [[wikipedia:Python_%28genus%29|type of snake]] and a [[wikipedia:Python_%28Efteling%29|rollercoaster]], but one is arguably more relevant to your research than the others. &amp;lt;br/&amp;gt;&lt;br /&gt;
On the lab computers, there is support for Spyder, PyCharm and [[Psychopy]]. &lt;br /&gt;
&lt;br /&gt;
&amp;lt;!-- Table of Contents will be generated here --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Upgrade from 2.7 to 3.7==&lt;br /&gt;
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on our [[System Image]]. Standard is now: Python 3.7 64-bits.&lt;br /&gt;
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')&lt;br /&gt;
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html&lt;br /&gt;
&lt;br /&gt;
For our previous documentation for Python 2.7, see [[Python/Legacy]]&lt;br /&gt;
&lt;br /&gt;
==Psychopy==&lt;br /&gt;
{{see |Psychopy}}&lt;br /&gt;
&lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our lab computers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
== Usage ==&lt;br /&gt;
&lt;br /&gt;
===Example: TestArgs.py===&lt;br /&gt;
Execute the following script within the commandline (CMD): &amp;lt;code style=&amp;quot;background-color:#000; color:#fff; padding:1px 3px;&amp;quot;&amp;gt;python testArgs.py a.&amp;lt;/code&amp;gt;&amp;lt;br/&amp;gt;&lt;br /&gt;
You should see the following result:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight lang=&amp;quot;python&amp;quot; overflow:auto;&amp;quot;&amp;gt;&lt;br /&gt;
number of argument:  2&lt;br /&gt;
 argv[0]: ./testArgs.py&lt;br /&gt;
 argv[1]: a&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==See Also==&lt;br /&gt;
*[[Psychopy]]&lt;br /&gt;
*[[Workshop: Python for social scientists]]&lt;br /&gt;
&amp;lt;!--&lt;br /&gt;
 ==References==&lt;br /&gt;
&amp;lt;references /&amp;gt; --&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==External Links== &lt;br /&gt;
*{{Official website|http://www.python.org}}&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5810</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5810"/>
		<updated>2024-04-23T14:40:37Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[Media:TemplatePsychopy2019.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
==Installation==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.8.10 64 bits installed. Psychopy recommends Python 3.8.10.&lt;br /&gt;
&lt;br /&gt;
Check our gitlab server https://gitlab.socsci.ru.nl&lt;br /&gt;
&lt;br /&gt;
=== For Pavlovia users ===&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
===Lab computer versioning===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A default version of Psychopy has been installed in the root of the Python3.8.10 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop. One in a while, the default version is upgraded to a newer version. The older version is then still available in a virtualenv.&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
=== For SR-Research Eyelink users ===&lt;br /&gt;
Eyelink users should follow the regular instructions above. Additionally, in the installer folder from our Gitlab, find the pylink version you need, rename it to '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
=== For SMI RED 500 and SMI HiSpeed Tower users ===&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
==Usage==&lt;br /&gt;
===VirtualEnv===&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
=== Spyder ===&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from a virtualenv, type '''workon &amp;lt;name of the virtualenv&amp;gt;''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
=== PyCharm ===&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
=== Batch files ===&lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5582</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5582"/>
		<updated>2023-01-09T12:32:11Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a '''tutorial video''' on how to '''setup Eyelink with a participant''': [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
From the SR-Research support forum, about '''placement of monitor, camera and participant''':&lt;br /&gt;
&lt;br /&gt;
''Ideally, the Desktop mount should be placed between 50-70 cm from the participant's eyes and be centrally aligned with the Display monitor from the participant's perspective. When using a wide screen monitor it will need to be sufficiently far away from the participant that it fits within the trackable range of the system. As a rule of thumb it will need to be at a distance at least 1.75 times its width (so a 40 cm wide monitor would need to be at least 70 cm away). As widescreen monitors are typically around 50 cm wide, they will need to be placed at least 90 cm away. This means that, in order for the camera to be placed correctly (50-70 cm from the participant's eyes) it will need to be brought forward from the monitor 20-30 cm.''&lt;br /&gt;
&lt;br /&gt;
''The top of the EyeLink camera and illuminator should also be as high as possible in the participant's field of view without obstructing any part of the display.''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The original image is from the sr-research support forum. It is found [https://www.sr-support.com/showthread.php?tid=206 here (sign in needed).]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
https://www.fh-joanneum.at/en/projekt/visionspace-wahrnehmungslabor/&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[https://www.fh-joanneum.at/en/projekt/visionspace-wahrnehmungslabor/ Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5456</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5456"/>
		<updated>2022-08-09T10:22:32Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a '''tutorial video''' on how to '''setup Eyelink with a participant''': [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
From the SR-Research support forum, about '''placement of monitor, camera and participant''':&lt;br /&gt;
&lt;br /&gt;
''Ideally, the Desktop mount should be placed between 50-70 cm from the participant's eyes and be centrally aligned with the Display monitor from the participant's perspective. When using a wide screen monitor it will need to be sufficiently far away from the participant that it fits within the trackable range of the system. As a rule of thumb it will need to be at a distance at least 1.75 times its width (so a 40 cm wide monitor would need to be at least 70 cm away). As widescreen monitors are typically around 50 cm wide, they will need to be placed at least 90 cm away. This means that, in order for the camera to be placed correctly (50-70 cm from the participant's eyes) it will need to be brought forward from the monitor 20-30 cm.''&lt;br /&gt;
&lt;br /&gt;
''The top of the EyeLink camera and illuminator should also be as high as possible in the participant's field of view without obstructing any part of the display.''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The original image is from the sr-research support forum. It is found [https://www.sr-support.com/showthread.php?tid=206 here (sign in needed).]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5455</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5455"/>
		<updated>2022-08-09T10:21:38Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a '''tutorial video''' on how to '''setup Eyelink with a participant''': [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
From the SR-Research support forum:&lt;br /&gt;
&lt;br /&gt;
''Ideally, the Desktop mount should be placed between 50-70 cm from the participant's eyes and be centrally aligned with the Display monitor from the participant's perspective. When using a wide screen monitor it will need to be sufficiently far away from the participant that it fits within the trackable range of the system. As a rule of thumb it will need to be at a distance at least 1.75 times its width (so a 40 cm wide monitor would need to be at least 70 cm away). As widescreen monitors are typically around 50 cm wide, they will need to be placed at least 90 cm away. This means that, in order for the camera to be placed correctly (50-70 cm from the participant's eyes) it will need to be brought forward from the monitor 20-30 cm.''&lt;br /&gt;
&lt;br /&gt;
''The top of the EyeLink camera and illuminator should also be as high as possible in the participant's field of view without obstructing any part of the display.''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The original image is from the sr-research support forum. It is found [https://www.sr-support.com/showthread.php?tid=206 here (sign in needed).]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5454</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5454"/>
		<updated>2022-08-09T08:10:27Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The original image is from the sr-research support forum. It is found [https://www.sr-support.com/showthread.php?tid=206 here (sign in needed).]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5453</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5453"/>
		<updated>2022-08-09T08:04:45Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The original image is from the sr-research support forum. It is found [here (sign in needed) [[https://www.sr-support.com/showthread.php?tid=206&amp;lt;nowiki&amp;gt;]]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5452</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5452"/>
		<updated>2022-08-09T08:03:22Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
The original image is from the sr-research support forum. It is found [here (sign in needed) [[https://www.sr-support.com/showthread.php?tid=206&amp;lt;nowiki&amp;gt;]]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5451</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5451"/>
		<updated>2022-08-09T08:02:42Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
|}&lt;br /&gt;
The original image is from the sr-research support forum. It is found [here (sign in needed) [[https://www.sr-support.com/showthread.php?tid=206&amp;lt;nowiki&amp;gt;]]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5450</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5450"/>
		<updated>2022-08-09T08:01:56Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
The original image is from the sr-research support forum. It is found [here (sign in needed) [[https://www.sr-support.com/showthread.php?tid=206&amp;lt;nowiki&amp;gt;]]&amp;lt;/nowiki&amp;gt;]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5449</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5449"/>
		<updated>2022-08-09T07:59:23Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5448</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5448"/>
		<updated>2022-08-09T07:54:46Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
[[File:EyelinkParticipantSetup.jpg|none|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5447</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5447"/>
		<updated>2022-08-09T07:54:09Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000 and Eyelink 1000 Plus&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
Monitor, camera and participant positioning should resemble this:&lt;br /&gt;
&lt;br /&gt;
[[File:EyelinkParticipantSetup.jpg|frame|FAQ: What is the ideal configuration EyeLink 1000 / EyeLink 1000 Plus Desktop mount? Original is here on the sr-support forum (need to sign-in): https://www.sr-support.com/showthread.php?tid=206]]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=File:EyelinkParticipantSetup.jpg&amp;diff=5446</id>
		<title>File:EyelinkParticipantSetup.jpg</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=File:EyelinkParticipantSetup.jpg&amp;diff=5446"/>
		<updated>2022-08-09T07:50:47Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: Image is copied from the sr-research support forum:

https://www.sr-support.com/showthread.php?tid=206&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Summary ==&lt;br /&gt;
Image is copied from the sr-research support forum:&lt;br /&gt;
&lt;br /&gt;
https://www.sr-support.com/showthread.php?tid=206&lt;br /&gt;
== Licensing ==&lt;br /&gt;
{{Unknown_copyright}}&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5445</id>
		<title>Eyetracker</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Eyetracker&amp;diff=5445"/>
		<updated>2022-08-09T07:38:55Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: /* EyeLink 1000 */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== SR Research ==&lt;br /&gt;
&lt;br /&gt;
[[image:SR_logo.jpg | right |150px]]&lt;br /&gt;
[[File:eyelink.jpg|thumb|200px|SR Research EyeLink II]]&lt;br /&gt;
&lt;br /&gt;
=== EyeLink II ===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The EyeLink II system consists of three miniature cameras mounted on a padded headband. Two eye cameras allow binocular eye tracking or selection of the subject’s dominant eye. &lt;br /&gt;
&lt;br /&gt;
An optical head-tracking camera integrated into the headband allows accurate tracking of the subject’s point of gaze without the need for a bite bar.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|EyeLink II &lt;br /&gt;
|-&lt;br /&gt;
| 500 Hz binocular eye monitoring&lt;br /&gt;
|-&lt;br /&gt;
| 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Access eye position data with 3.0 msec delay&lt;br /&gt;
|-&lt;br /&gt;
| 0.01º RMS resolution&lt;br /&gt;
|-&lt;br /&gt;
| High quality computer based or scene camera eye tracking&lt;br /&gt;
|-&lt;br /&gt;
| Fast and simple participant setup, calibration, and validation&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== EyeLink 1000 ===&lt;br /&gt;
[[image:Eyelink1000.jpg | right |150px]]&lt;br /&gt;
http://www.sr-research.com/eyelink1000.html&lt;br /&gt;
&lt;br /&gt;
The core of the EyeLink 1000 eye tracker consists of a custom designed high-speed camera connected to a dedicated Host computer. Running on a real-time operating system, the Host software provides extremely fast eye sample access with incredibly low inter-sample variability, accessed via a set of programming interfaces for multiple operating systems and programming languages&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
! Eyelink 1000&lt;br /&gt;
|-&lt;br /&gt;
| Sampling Rate || Head Supported: 2000 Hz Monocular / 1000 Hz Binocular &lt;br /&gt;
Remote / Head Free: 500 Hz Monocular&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy || Head Supported: 0.25º -0.5º average accuracy&lt;br /&gt;
Remote / Head Free: 0.5º average accuracy&lt;br /&gt;
|-&lt;br /&gt;
| Real-time Data Access || Head Supported: 1.4 msec (SD &amp;lt; 0.4 msec) @ 2000 Hz&lt;br /&gt;
Remote / Head Free: 3 msec (SD &amp;lt; 1.2 msec) @ 500 Hz&lt;br /&gt;
|-&lt;br /&gt;
| Participant Setup || Very simple and easy. Typically less than 2-5 minutes&lt;br /&gt;
|-&lt;br /&gt;
| Resolution || Head Supported: 0.01º RMS, micro-saccade resolution of 0.05º&lt;br /&gt;
Remote / Head Free:0.05º RMS, saccade resolution of 0.25&lt;br /&gt;
|}&lt;br /&gt;
Full specifications: http://www.sr-research.com/pdf/techspec.pdf&amp;lt;br /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
[[Eyelink_1000_calibration | Matlab calibration example]]&lt;br /&gt;
&lt;br /&gt;
[[Eyelink1000plussetup|Eyelink 1000 plus setup]]&lt;br /&gt;
&lt;br /&gt;
Here is a tutorial video on how to setup Eyelink with a participant: [https://www.youtube.com/watch?v=O3z8I5y_l5E&amp;amp;list=PLOdF-B36TwspxRQeam0u5Yd29wOjUWcel&amp;amp;index=7 Eyelink setup and calibration tutorial video.]&lt;br /&gt;
&lt;br /&gt;
== Tobii ==&lt;br /&gt;
&lt;br /&gt;
[[File:tobii_logo.jpg | right]]&lt;br /&gt;
[[File:Tobii.jpg|thumb|200px|Tobii T60]]&lt;br /&gt;
[[File:TX300.png|thumb|250px|Tobii TX300]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Tobii T60/T120===&lt;br /&gt;
&lt;br /&gt;
The Tobii T60 and T120 Eye Trackers are integrated into a 17&amp;quot; TFT monitor. They are ideal for all forms of eye tracking studies using screen based stimuli.&lt;br /&gt;
&lt;br /&gt;
There is a Tobii setup in the babylab, which is in a fixed lab setup.&lt;br /&gt;
&lt;br /&gt;
There are also two mobile Tobii setups. Please contact [mailto:g.lange@psych.ru.nl Gero Lange] for booking requests. Please keep in mind that these mobile setups are booked _without_ a room. If you plan to use these eyetrackers, make sure to also book a room that can be locked. You can use it in a cubicle, as long as you make sure that the eyetracker is stored in a locked room at the end of the day.&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T60 Eye Tracker&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii T120 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 || 0.5&lt;br /&gt;
|-&lt;br /&gt;
| Drift (degrees) || &amp;lt; 0.3 || &amp;lt; 0.3&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 44 * 22 * 30 || 30 * 22 * 30&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60 || 120&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes&lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 17 || 17&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1280 * 1024 || 1280 * 1024&lt;br /&gt;
|-&lt;br /&gt;
| Bright/Dark Pupil Tracking || Both - automatic optimization || Both - automatic optimization&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded || Embedded&lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in || Built-in&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers|| Built-in Speakers&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;The Tobii T120 Eye Tracker can also run in T60 mode with full head movement box&lt;br /&gt;
&lt;br /&gt;
Presentation plugin, including documentation on how to install and how to use it:&lt;br /&gt;
&lt;br /&gt;
http://www.visionspace.at/index.php?id=3&amp;amp;L=1&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:Tobii TX 300.pdf|How to use a Tobii TX 300 eyetracker]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Getting_a_Tobii_Eye_Tracker_to_Work.pdf|Getting Started Guide]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:TobiiEyetrackerExtension_1_1.zip|Tobii Eyetrackers Extension for use with Presentation (including samples and documentation) (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[http://www.visionspace.at/index.php?id=3&amp;amp;L=1 Neurobs Presentation plugin &amp;amp; documentation]&lt;br /&gt;
&lt;br /&gt;
'''Lab setup'''&lt;br /&gt;
&lt;br /&gt;
http://tsgdoc.socsci.ru.nl/index.php?title=Tobii_Eye_Tracker&lt;br /&gt;
&lt;br /&gt;
===Tobii TX300===&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Specifications'''&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot; &lt;br /&gt;
|-&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;|&lt;br /&gt;
! scope=&amp;quot;col&amp;quot; style=&amp;quot;width:200px;&amp;quot;| Tobii TX300 Eye Tracker&amp;lt;sup&amp;gt;1&amp;lt;/sup&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| Precision(degrees) || &amp;lt; 0.1&lt;br /&gt;
|-&lt;br /&gt;
| Accuracy (degrees) || 0.5 (Monocular), 0.4 (Binocular)&lt;br /&gt;
|-&lt;br /&gt;
| Freedom of Head Movement (cm) || 37 * 17 (at 65 cm distance)&lt;br /&gt;
|-&lt;br /&gt;
| Data Rate (Hz) || 60Hz, 120Hz or 300Hz&lt;br /&gt;
|-&lt;br /&gt;
| Binocular Tracking || style=&amp;quot;background-color:#9F9;&amp;quot; | Yes &lt;br /&gt;
|-&lt;br /&gt;
| Display Size (inch) || 23&lt;br /&gt;
|-&lt;br /&gt;
| Display Resolution (px) || 1920 * 1080 (max 60Hz)&lt;br /&gt;
|-&lt;br /&gt;
| Tracking method || Dark Pupil Tracking&lt;br /&gt;
|-&lt;br /&gt;
| Eye Tracking Server || Embedded &lt;br /&gt;
|-&lt;br /&gt;
| User Camera || Built-in (640x480@30fps)&lt;br /&gt;
|-&lt;br /&gt;
| Audio || Built-in Speakers (3W)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== SensoMotoric Instruments (SMI) ==&lt;br /&gt;
[[image:SMI_logo.jpg |right]]&lt;br /&gt;
[[File:IViewXRED.jpg|thumb|200px|SMI RED500]]&lt;br /&gt;
[[file:eyeviewx.jpg |thumb|200px|SMI iView X]]&lt;br /&gt;
&lt;br /&gt;
=== SMI RED500 ===&lt;br /&gt;
&lt;br /&gt;
[[SMI RED 500 Eye Tracker (DCC)|How to connect SMI RED 500 eyetracker (Scheme)]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
*[[Media:IView_X_SDK_Manual.pdf|IView User Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation. &lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;br /&gt;
&lt;br /&gt;
=== iView X ===&lt;br /&gt;
&lt;br /&gt;
'''Downloads'''&lt;br /&gt;
&lt;br /&gt;
*[[Media:IViewX.pdf | iView X Manual]]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Eye-tracking_Presentation_iview.zip | Presentation Extension (zip)]]&lt;br /&gt;
*[[Media:SMI-Eyetracker-Example.zip|Example Presentation Script (zip, new script since 2018-06-05)]] An example script that connects and communicates with the IViewX program. It shows two pictures side by side. Data can be analysed using BeGaze. There are a lot of explanations in the files. The comments will help understanding how to use an SMI eyetracker in Presentation.&lt;br /&gt;
Source code: [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-Example.sce SMI-Eyetracker-Example.sce ], [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleINFO.pcl SMI-Eyetracker-ExampleINFO.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExamplePCL.pcl SMI-Eyetracker-ExamplePCL.pcl] [https://gitlab.socsci.ru.nl/h.voogd/SMI-Eyetracking-Example/blob/master/SMI-Eyetracker-ExampleSUBS.pcl SMI-Eyetracker-ExampleSUBS.pcl]&lt;br /&gt;
&lt;br /&gt;
*[[Media:Python.zip|Python Script (zip)]]&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5298</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5298"/>
		<updated>2021-03-02T08:45:09Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[Media:TemplatePsychopy2013.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/~wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade ==&lt;br /&gt;
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on the PCs in the labs. Standard is now: Python 3.7 64-bits.&lt;br /&gt;
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')&lt;br /&gt;
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html&lt;br /&gt;
&lt;br /&gt;
Psychopy 2020.2.10 has been installed in the root of the Python3.7 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop.&lt;br /&gt;
There is also a Psychopy 2020.2.10 installed on Python3.6 32-bits. This version has its own icon on the desktop and should be used when you are using a TOBII Eyetracker.&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation for Tobii users ==&lt;br /&gt;
Since Tobii does not support 64-bits and does not support Python higher than version 3.6.8, there is a 32 bits Python version 3.6.8 installed. If you want to use a Tobii Eyetracker and want to install Python and Psychopy yourself, download Python here: [https://www.python.org/ftp/python/3.6.8/python-3.6.8-webinstall.exe Python3.6.8 (Windows)] or here: [https://www.python.org/downloads/release/python-368/ List of downloads for Python3.6.8. Please choose a 32-bit version.] Run the installer, choose to add python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.6.8 PsychoPyDependenciesPython3.6.8.txt]. Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''python -m pip install --upgrade pip''' to upgrade the pip installer. Then type:&lt;br /&gt;
'''pip install -r PsychoPyDependenciesPython3.6.8.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.6.8.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' in our labs, the 64-bits Python and 64-bits Psychopy are installed as default. The 32-bits Python 3.6.8 and 32-bits Psychopy are installed in a separate ''virtualenv''. If you want to use Python3.6.8 from the command prompt, you first have to type:&lt;br /&gt;
'''workon Python36'''&lt;br /&gt;
After that, everything should work from Python3.6.8, including the 32-bits packages. &lt;br /&gt;
&lt;br /&gt;
== Installation for other users ==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.7.6 64 bits installed. You can download it here: [https://www.python.org/ftp/python/3.7.6/python-3.7.6-amd64-webinstall.exe Python3.7.6 64 bits (Windows)] or choose here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.7-64-bits PsychopyRequirements3.7.txt].Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''python -m pip install --upgrade pip''' to upgrade the pip installer. Then type:&lt;br /&gt;
'''pip install -r PsychopyRequirements3.7.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.7.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
== Addition for SR-Research Eyelink users ==&lt;br /&gt;
Eyelink users should follow the instructions above: 'Installation for other users'. Additionally, download the SR-Research Python package from here: [https://gitlab.socsci.ru.nl/h.voogd/PyLink3.7-64bit pylinkForPython-3.7.5-x64-Win]. Unzip it, find the folder called: '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
== Addition for SMI RED 500 and SMI HiSpeed Tower users ==&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== VirtualEnv ==&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
In our labs, we have th evirtualenvs:&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python36''' that contains Python 3.6.8 32-bits, Psychopy and the tobii_research package.&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python37''' that contains Python 3.7 64-bits, Psychopy and the pylink package (for use with the Eyelink eyetracker).&amp;lt;br&amp;gt;&lt;br /&gt;
and some more virtualenvs that contain packages that would otherwise interfere with Psychopy.&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
== Git, Pavlovia ==&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
== Spyder ==&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python 3.7.6 64-bits environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from the Python36 virtualenv, type '''workon python36''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
== PyCharm ==&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
== Batch files == &lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''call workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;br /&gt;
&lt;br /&gt;
== Summary for Tobii users (and others that need 32 bits Psychopy) ==&lt;br /&gt;
Since Tobii does not support 64 bits systems and does not support Python with a version higher than 3.6, the labcomputer has a special virtualenv that is called '''Python36'''. This virtualenv contains everything that Psychopy needs to install, and it contains the '''tobii-research''' package. It also contains the packages that are needed to use the '''cv.dll''' library. &amp;lt;br&amp;gt;&lt;br /&gt;
To start your script you can: &amp;lt;br&amp;gt;&lt;br /&gt;
- start Psychopy using the icon on the desktop that uses the 32-bit version. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Psychopy''' to start the 32 bit Psychopy version.&amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Spyder3''' to start the Spyder IDE.&amp;lt;br&amp;gt;&lt;br /&gt;
- choose the ''Python 3.6 (Python36)'' python interpreter in PyCharm. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window type '''workon Python36''', then type '''python &amp;lt;myscript.py&amp;gt;''' to start your script. Or make a batch file that does this.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5296</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5296"/>
		<updated>2021-02-19T09:16:45Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[Media:TemplatePsychopy2013.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/~wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade ==&lt;br /&gt;
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on the PCs in the labs. Standard is now: Python 3.7 64-bits.&lt;br /&gt;
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')&lt;br /&gt;
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html&lt;br /&gt;
&lt;br /&gt;
Psychopy 2020.2.10 has been installed in the root of the Python3.7 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop.&lt;br /&gt;
There is also a Psychopy 2020.2.10 installed on Python3.6 32-bits. This version has its own icon on the desktop and should be used when you are using a TOBII Eyetracker.&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation for Tobii users ==&lt;br /&gt;
Since Tobii does not support 64-bits and does not support Python higher than version 3.6.8, there is a 32 bits Python version 3.6.8 installed. If you want to use a Tobii Eyetracker and want to install Python and Psychopy yourself, download Python here: [https://www.python.org/ftp/python/3.6.8/python-3.6.8-webinstall.exe Python3.6.8 (Windows)] or here: [https://www.python.org/downloads/release/python-368/ List of downloads for Python3.6.8. Please choose a 32-bit version.] Run the installer, choose to add python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.6.8 PsychoPyDependenciesPython3.6.8.txt]. Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''python -m pip install --upgrade pip''' to upgrade the pip installer. Then type:&lt;br /&gt;
'''pip install -r PsychoPyDependenciesPython3.6.8.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.6.8.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' in our labs, the 64-bits Python and 64-bits Psychopy are installed as default. The 32-bits Python 3.6.8 and 32-bits Psychopy are installed in a separate ''virtualenv''. If you want to use Python3.6.8 from the command prompt, you first have to type:&lt;br /&gt;
'''workon Python36'''&lt;br /&gt;
After that, everything should work from Python3.6.8, including the 32-bits packages. &lt;br /&gt;
&lt;br /&gt;
== Installation for other users ==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.7.6 64 bits installed. You can download it here: [https://www.python.org/ftp/python/3.7.6/python-3.7.6-amd64-webinstall.exe Python3.7.6 64 bits (Windows)] or choose here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.7-64-bits PsychopyRequirements3.7.txt].Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''python -m pip install --upgrade pip''' to upgrade the pip installer. Then type:&lt;br /&gt;
'''pip install -r PsychopyRequirements3.7.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.7.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
== Addition for SR-Research Eyelink users ==&lt;br /&gt;
Eyelink users should follow the instructions above: 'Installation for other users'. Additionally, download the SR-Research Python package from here: [https://gitlab.socsci.ru.nl/h.voogd/PyLink3.7-64bit pylinkForPython-3.7.5-x64-Win]. Unzip it, find the folder called: '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
== Addition for SMI RED 500 and SMI HiSpeed Tower users ==&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== VirtualEnv ==&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
In our labs, we have th evirtualenvs:&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python36''' that contains Python 3.6.8 32-bits, Psychopy and the tobii_research package.&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python37''' that contains Python 3.7 64-bits, Psychopy and the pylink package (for use with the Eyelink eyetracker).&amp;lt;br&amp;gt;&lt;br /&gt;
and some more virtualenvs that contain packages that would otherwise interfere with Psychopy.&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
== Git, Pavlovia ==&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
== Spyder ==&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python 3.7.6 64-bits environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from the Python36 virtualenv, type '''workon python36''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
== PyCharm ==&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
== Batch files == &lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;br /&gt;
&lt;br /&gt;
== Summary for Tobii users (and others that need 32 bits Psychopy) ==&lt;br /&gt;
Since Tobii does not support 64 bits systems and does not support Python with a version higher than 3.6, the labcomputer has a special virtualenv that is called '''Python36'''. This virtualenv contains everything that Psychopy needs to install, and it contains the '''tobii-research''' package. It also contains the packages that are needed to use the '''cv.dll''' library. &amp;lt;br&amp;gt;&lt;br /&gt;
To start your script you can: &amp;lt;br&amp;gt;&lt;br /&gt;
- start Psychopy using the icon on the desktop that uses the 32-bit version. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Psychopy''' to start the 32 bit Psychopy version.&amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Spyder3''' to start the Spyder IDE.&amp;lt;br&amp;gt;&lt;br /&gt;
- choose the ''Python 3.6 (Python36)'' python interpreter in PyCharm. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window type '''workon Python36''', then type '''python &amp;lt;myscript.py&amp;gt;''' to start your script. Or make a batch file that does this.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5295</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5295"/>
		<updated>2021-02-18T15:04:44Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: Corrected link to 64-bit Python installer&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[Media:TemplatePsychopy2013.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/~wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade ==&lt;br /&gt;
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on the PCs in the labs. Standard is now: Python 3.7 64-bits.&lt;br /&gt;
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')&lt;br /&gt;
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html&lt;br /&gt;
&lt;br /&gt;
Psychopy 2020.2.10 has been installed in the root of the Python3.7 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop.&lt;br /&gt;
There is also a Psychopy 2020.2.10 installed on Python3.6 32-bits. This version has its own icon on the desktop and should be used when you are using a TOBII Eyetracker.&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation for Tobii users ==&lt;br /&gt;
Since Tobii does not support 64-bits and does not support Python higher than version 3.6.8, there is a 32 bits Python version 3.6.8 installed. If you want to use a Tobii Eyetracker and want to install Python and Psychopy yourself, download Python here: [https://www.python.org/ftp/python/3.6.8/python-3.6.8-webinstall.exe Python3.6.8 (Windows)] or here: [https://www.python.org/downloads/release/python-368/ List of downloads for Python3.6.8. Please choose a 32-bit version.] Run the installer, choose to add python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.6.8 PsychoPyDependenciesPython3.6.8.txt]. Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''pip install -r PsychoPyDependenciesPython3.6.8.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.6.8.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' in our labs, the 64-bits Python and 64-bits Psychopy are installed as default. The 32-bits Python 3.6.8 and 32-bits Psychopy are installed in a separate ''virtualenv''. If you want to use Python3.6.8 from the command prompt, you first have to type:&lt;br /&gt;
'''workon Python36'''&lt;br /&gt;
After that, everything should work from Python3.6.8, including the 32-bits packages. &lt;br /&gt;
&lt;br /&gt;
== Installation for other users ==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.7.6 64 bits installed. You can download it here: [https://www.python.org/ftp/python/3.7.6/python-3.7.6-amd64-webinstall.exe Python3.7.6 64 bits (Windows)] or choose here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.7-64-bits PsychopyRequirements3.7.txt].Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''pip install -r PsychopyRequirements3.7.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.7.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
== Addition for SR-Research Eyelink users ==&lt;br /&gt;
Eyelink users should follow the instructions above: 'Installation for other users'. Additionally, download the SR-Research Python package from here: [https://gitlab.socsci.ru.nl/h.voogd/PyLink3.7-64bit pylinkForPython-3.7.5-x64-Win]. Unzip it, find the folder called: '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
== Addition for SMI RED 500 and SMI HiSpeed Tower users ==&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== VirtualEnv ==&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
In our labs, we have th evirtualenvs:&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python36''' that contains Python 3.6.8 32-bits, Psychopy and the tobii_research package.&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python37''' that contains Python 3.7 64-bits, Psychopy and the pylink package (for use with the Eyelink eyetracker).&amp;lt;br&amp;gt;&lt;br /&gt;
and some more virtualenvs that contain packages that would otherwise interfere with Psychopy.&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
== Git, Pavlovia ==&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
== Spyder ==&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python 3.7.6 64-bits environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from the Python36 virtualenv, type '''workon python36''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
== PyCharm ==&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
== Batch files == &lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;br /&gt;
&lt;br /&gt;
== Summary for Tobii users (and others that need 32 bits Psychopy) ==&lt;br /&gt;
Since Tobii does not support 64 bits systems and does not support Python with a version higher than 3.6, the labcomputer has a special virtualenv that is called '''Python36'''. This virtualenv contains everything that Psychopy needs to install, and it contains the '''tobii-research''' package. It also contains the packages that are needed to use the '''cv.dll''' library. &amp;lt;br&amp;gt;&lt;br /&gt;
To start your script you can: &amp;lt;br&amp;gt;&lt;br /&gt;
- start Psychopy using the icon on the desktop that uses the 32-bit version. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Psychopy''' to start the 32 bit Psychopy version.&amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Spyder3''' to start the Spyder IDE.&amp;lt;br&amp;gt;&lt;br /&gt;
- choose the ''Python 3.6 (Python36)'' python interpreter in PyCharm. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window type '''workon Python36''', then type '''python &amp;lt;myscript.py&amp;gt;''' to start your script. Or make a batch file that does this.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5294</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5294"/>
		<updated>2021-02-16T08:42:34Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: Fixed pip install command line&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[Media:TemplatePsychopy2013.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/~wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade ==&lt;br /&gt;
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on the PCs in the labs. Standard is now: Python 3.7 64-bits.&lt;br /&gt;
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')&lt;br /&gt;
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html&lt;br /&gt;
&lt;br /&gt;
Psychopy 2020.2.10 has been installed in the root of the Python3.7 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop.&lt;br /&gt;
There is also a Psychopy 2020.2.10 installed on Python3.6 32-bits. This version has its own icon on the desktop and should be used when you are using a TOBII Eyetracker.&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation for Tobii users ==&lt;br /&gt;
Since Tobii does not support 64-bits and does not support Python higher than version 3.6.8, there is a 32 bits Python version 3.6.8 installed. If you want to use a Tobii Eyetracker and want to install Python and Psychopy yourself, download Python here: [https://www.python.org/ftp/python/3.6.8/python-3.6.8-webinstall.exe Python3.6.8 (Windows)] or here: [https://www.python.org/downloads/release/python-368/ List of downloads for Python3.6.8. Please choose a 32-bit version.] Run the installer, choose to add python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.6.8 PsychoPyDependenciesPython3.6.8.txt]. Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''pip install -r PsychoPyDependenciesPython3.6.8.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.6.8.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' in our labs, the 64-bits Python and 64-bits Psychopy are installed as default. The 32-bits Python 3.6.8 and 32-bits Psychopy are installed in a separate ''virtualenv''. If you want to use Python3.6.8 from the command prompt, you first have to type:&lt;br /&gt;
'''workon Python36'''&lt;br /&gt;
After that, everything should work from Python3.6.8, including the 32-bits packages. &lt;br /&gt;
&lt;br /&gt;
== Installation for other users ==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.7.6 64 bits installed. You can download it here: [https://www.python.org/ftp/python/3.7.6/python-3.7.6-webinstall.exe Python3.7.6 64 bits (Windows)] or choose here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.7-64-bits PsychopyRequirements3.7.txt].Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''pip install -r PsychopyRequirements3.7.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.7.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
== Addition for SR-Research Eyelink users ==&lt;br /&gt;
Eyelink users should follow the instructions above: 'Installation for other users'. Additionally, download the SR-Research Python package from here: [https://gitlab.socsci.ru.nl/h.voogd/PyLink3.7-64bit pylinkForPython-3.7.5-x64-Win]. Unzip it, find the folder called: '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
== Addition for SMI RED 500 and SMI HiSpeed Tower users ==&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== VirtualEnv ==&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
In our labs, we have th evirtualenvs:&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python36''' that contains Python 3.6.8 32-bits, Psychopy and the tobii_research package.&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python37''' that contains Python 3.7 64-bits, Psychopy and the pylink package (for use with the Eyelink eyetracker).&amp;lt;br&amp;gt;&lt;br /&gt;
and some more virtualenvs that contain packages that would otherwise interfere with Psychopy.&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
== Git, Pavlovia ==&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
== Spyder ==&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python 3.7.6 64-bits environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from the Python36 virtualenv, type '''workon python36''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
== PyCharm ==&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
== Batch files == &lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;br /&gt;
&lt;br /&gt;
== Summary for Tobii users (and others that need 32 bits Psychopy) ==&lt;br /&gt;
Since Tobii does not support 64 bits systems and does not support Python with a version higher than 3.6, the labcomputer has a special virtualenv that is called '''Python36'''. This virtualenv contains everything that Psychopy needs to install, and it contains the '''tobii-research''' package. It also contains the packages that are needed to use the '''cv.dll''' library. &amp;lt;br&amp;gt;&lt;br /&gt;
To start your script you can: &amp;lt;br&amp;gt;&lt;br /&gt;
- start Psychopy using the icon on the desktop that uses the 32-bit version. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Psychopy''' to start the 32 bit Psychopy version.&amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Spyder3''' to start the Spyder IDE.&amp;lt;br&amp;gt;&lt;br /&gt;
- choose the ''Python 3.6 (Python36)'' python interpreter in PyCharm. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window type '''workon Python36''', then type '''python &amp;lt;myscript.py&amp;gt;''' to start your script. Or make a batch file that does this.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
	<entry>
		<id>http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5291</id>
		<title>Psychopy</title>
		<link rel="alternate" type="text/html" href="http://tsgdoc.socsci.ru.nl/index.php?title=Psychopy&amp;diff=5291"/>
		<updated>2021-02-11T16:14:42Z</updated>

		<summary type="html">&lt;p&gt;H.voogd: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;br /&gt;
{{Infobox software&lt;br /&gt;
| name                   = Psychopy&lt;br /&gt;
| logo                   = Psychopy Logo.png&lt;br /&gt;
| logo size              = 250px&lt;br /&gt;
| screenshot             = &lt;br /&gt;
| caption                = &lt;br /&gt;
| developer              = &lt;br /&gt;
| released               = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| discontinued           = &lt;br /&gt;
| latest release version = &lt;br /&gt;
| latest release date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| latest preview version = &lt;br /&gt;
| latest preview date    = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| installed version      = &lt;br /&gt;
| installed version date = &amp;lt;!-- {{Start date and age|YYYY|MM|DD|df=yes}} --&amp;gt;&lt;br /&gt;
| status                 = Active&lt;br /&gt;
| programming language   = Python&lt;br /&gt;
| operating system       = &lt;br /&gt;
| platform               = &lt;br /&gt;
| size                   = &lt;br /&gt;
| language               = &lt;br /&gt;
| genre                  = &lt;br /&gt;
| license                = &lt;br /&gt;
| website                = &lt;br /&gt;
| resources              = &lt;br /&gt;
  {{Infobox tsg&lt;br /&gt;
    | child              = yes&lt;br /&gt;
    | downloads          = {{bulleted list&lt;br /&gt;
        | [[Media:TemplatePsychopy2013.zip|Template]]&lt;br /&gt;
    }}&lt;br /&gt;
    | manuals            = {{bulleted list&lt;br /&gt;
        | [https://www.socsci.ru.nl/~wilberth/psychopy/index.html Course]&lt;br /&gt;
    }}&lt;br /&gt;
  }}&lt;br /&gt;
}}&lt;br /&gt;
PsychoPy is an alternative to Presentation, e-Prime and Inquisit. It is a Python library and application that allows presentation of stimuli and collection of data for a wide range of neuroscience, psychology and psychophysics experiments. When used on DCC computers PsychoPy is guaranteed to be millisecond accurate.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Upgrade ==&lt;br /&gt;
Since Python version 2.7 has reached end of life since January first 2020, this version is no longer installed on the PCs in the labs. Standard is now: Python 3.7 64-bits.&lt;br /&gt;
If you still have scripts written in Python2, the scripts should be upgraded to Python 3. Most changes are probably the print statements. Print statements should always have parentheses: print('some text')&lt;br /&gt;
Key differences between Python 2 and Python 3 are here: https://sebastianraschka.com/Articles/2014_python_2_3_key_diff.html&lt;br /&gt;
&lt;br /&gt;
Psychopy 2020.2.10 has been installed in the root of the Python3.7 64-bit version. This is also the default version when 'psychopy' is typed from the command prompt. It is also the default that opens when a .py file is double-clicked. It also can be started by clicking the appropriate icon on the desktop.&lt;br /&gt;
There is also a Psychopy 2020.2.10 installed on Python3.6 32-bits. This version has its own icon on the desktop and should be used when you are using a TOBII Eyetracker.&lt;br /&gt;
 &lt;br /&gt;
When your script fails to load in Psychopy, because you need packages that are not installed on our labcomputers, please contact TSG.&lt;br /&gt;
&lt;br /&gt;
On the labcomputer, there is support for Spyder, PyCharm and Psychopy. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Installation for Tobii users ==&lt;br /&gt;
Since Tobii does not support 64-bits and does not support Python higher than version 3.6.8, there is a 32 bits Python version 3.6.8 installed. If you want to use a Tobii Eyetracker and want to install Python and Psychopy yourself, download Python here: [https://www.python.org/ftp/python/3.6.8/python-3.6.8-webinstall.exe Python3.6.8 (Windows)] or here: [https://www.python.org/downloads/release/python-368/ List of downloads for Python3.6.8. Please choose a 32-bit version.] Run the installer, choose to add python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.6.8 PsychoPyDependenciesPython3.6.8.txt]. Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''pip install -r PsychoPyDependenciesPython3.6.8.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.6.8.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
'''Note:''' in our labs, the 64-bits Python and 64-bits Psychopy are installed as default. The 32-bits Python 3.6.8 and 32-bits Psychopy are installed in a separate ''virtualenv''. If you want to use Python3.6.8 from the command prompt, you first have to type:&lt;br /&gt;
'''workon Python36'''&lt;br /&gt;
After that, everything should work from Python3.6.8, including the 32-bits packages. &lt;br /&gt;
&lt;br /&gt;
== Installation for other users ==&lt;br /&gt;
We recommend to use a modern 64-bit version of Python. In our labs, we currently have Python 3.7.6 64 bits installed. You can download it here: [https://www.python.org/ftp/python/3.7.6/python-3.7.6-webinstall.exe Python3.7.6 64 bits (Windows)] or choose here: [https://www.python.org/downloads/release/python-376/ Please choose a 64 bit version.]. Run the installer and make sure to add Python to the file path (it's an option in the installer).&lt;br /&gt;
&lt;br /&gt;
Download from here: [https://gitlab.socsci.ru.nl/h.voogd/psychopy-installation-on-python-3.7-64-bits PsychopyRequirements3.7.txt].Open a command prompt (with administrator rights), go to the folder where the downloaded file is and type:&lt;br /&gt;
'''pip install -r PsychoPyDependenciesPython3.7.txt'''&lt;br /&gt;
&lt;br /&gt;
This should install everything you need for a basic Psychopy installation. Since packages are updated once in a while, this PsychoPyDependenciesPython3.7.txt might get outdated at some time. Please let us know.&lt;br /&gt;
&lt;br /&gt;
== Addition for SR-Research Eyelink users ==&lt;br /&gt;
Eyelink users should follow the instructions above: 'Installation for other users'. Additionally, download the SR-Research Python package from here: [https://gitlab.socsci.ru.nl/h.voogd/PyLink3.7-64bit pylinkForPython-3.7.5-x64-Win]. Unzip it, find the folder called: '''pylink''' and copy it to your Pythons '''lib/site-packages''' folder.&lt;br /&gt;
&lt;br /&gt;
== Addition for SMI RED 500 and SMI HiSpeed Tower users ==&lt;br /&gt;
Include this file into your project: [https://gitlab.socsci.ru.nl/h.voogd/iviewxudp iViewXudp]. This should work on both 64-bit and 32-bit Python 3 versions.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== VirtualEnv ==&lt;br /&gt;
Some of the packages that are installed in the steps above, make it possible to make use of VirtualEnvs. A virtual environment is a Python environment such that the Python interpreter, libraries and scripts installed into it are isolated from those installed in other virtual environments, and (by default) any libraries installed in a “system” Python, i.e., one which is installed as part of your operating system.&lt;br /&gt;
&lt;br /&gt;
If you want to use virtualenvs on your on computer, In ''System| Advanced system settings | Environment variables'', make a new system variable with name '''WORKON_HOME''' and value ''C:\Users\Public\Envs\''.&lt;br /&gt;
And make a new system variable with name: '''PROJECT_HOME''' and value ''C:\Users\Public\Projects''. Your virtualenvs will now be stored in ''C:\Users\Public\Projects'' and projects in ''C:\Users\Public\Projects''. These are also the places where virtualenvs and projects are stored on the labcomputer.&lt;br /&gt;
&lt;br /&gt;
Open a command window with administrator rights and type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon'''  to see a list of existing virtualenvs.&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenvname&amp;gt;''', where &amp;lt;virtualenvname&amp;gt; is the name of the virtualenv you want to use.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.7.6.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=36 &amp;lt;virtualenvname&amp;gt;''' to create a new and empty virtualenv that uses the installed Python3.6.8.&amp;lt;br&amp;gt;&lt;br /&gt;
'''mkvirtualenv -p=37 --system-site-packages &amp;lt;virtualenvname&amp;gt;''' to create a new virtualenv that uses the installed Python3.7 and its site-packages.&amp;lt;br&amp;gt;&lt;br /&gt;
'''rmvirtualenv &amp;lt;virtualenvname&amp;gt;''' to remove the virtualenv with name &amp;lt;virtualenvname&amp;gt;.&amp;lt;br&amp;gt;&lt;br /&gt;
'''deactivate''' to return to the defaults.&lt;br /&gt;
&amp;lt;br&amp;gt;&lt;br /&gt;
In our labs, we have th evirtualenvs:&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python36''' that contains Python 3.6.8 32-bits, Psychopy and the tobii_research package.&amp;lt;br&amp;gt;&lt;br /&gt;
'''Python37''' that contains Python 3.7 64-bits, Psychopy and the pylink package (for use with the Eyelink eyetracker).&amp;lt;br&amp;gt;&lt;br /&gt;
and some more virtualenvs that contain packages that would otherwise interfere with Psychopy.&lt;br /&gt;
&lt;br /&gt;
If you need a package that is not installed on our labcomputer, contact TSG, so that we can decide to add it to our standard installation, or to install it in a separate virtualenv. Do '''not''' use ''pip install'' and install anything in an existing virtualenv. Unless it is your own virtualenv. This might interfere with existing packages and might mess up other peoples projects. Instead, make your own virtualenv and install it there (use '''mkvirtualenv''' to create it, use '''workon''' to activate it, then use '''pip''' to install packages into your own virtualenv). Also, make a backup of your virtualenv, since when the labimage is updated, the newly created virtualenvs will be gone.&lt;br /&gt;
&lt;br /&gt;
== Git, Pavlovia ==&lt;br /&gt;
If you want to upload experiments to Pavlovia, you will need to install [https://github.com/git-for-windows/git/releases/download/v2.17.1.windows.1/Git-2.17.1-64-bit.exe Git-2.17.1-64-bit.exe] using these instructions: [https://gitlab.socsci.ru.nl/h.voogd/git-2.17.1.2-64-bit.exe/-/raw/master/GitInstall.docx GitInstall.docx]. Then, in&lt;br /&gt;
''System| Advanced system settings | Environment variables'', add the folder where ''git-daemon.exe'' is, to the PATH variable. Usually, that folder is named: 'C:\Program Files\Git\mingw64\libexec\git-core'.&lt;br /&gt;
&lt;br /&gt;
== Spyder ==&lt;br /&gt;
Spyder (Scientific Python Development Environment) is an IDE for Python. It can be run from a command prompt. If you want to use Spyder in the default Python 3.7.6 64-bits environment, you can just type '''Spyder''' from the command prompt. If you want to use Spyder from the Python36 virtualenv, type '''workon python36''' and then type '''Spyder3'''. If you have created your own virtualenv, make sure that Spyder is installed.&lt;br /&gt;
&lt;br /&gt;
== PyCharm ==&lt;br /&gt;
PyCharm is installed on our labcomputers. It is a Python IDE. In the lowerright corner, it will display its current Python environment. By clicking on that name, you can change the interpreter and choose from the existing virtualenvs that PyCharm knows. Or you can add your own virtualenv. &amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
[[File:PycharmInterpreters.png|thumb|none|PycharmInterpreters]]&lt;br /&gt;
&lt;br /&gt;
== Batch files == &lt;br /&gt;
If you are working from a virtualenv, other than the default, and you don't want to open a command window, type '''workon &amp;lt;virtualenv&amp;gt;''' and type '''python &amp;lt;myscript.py&amp;gt;''' every time, you might want to make a batch file. Create a text file, type:&amp;lt;br&amp;gt;&lt;br /&gt;
'''workon &amp;lt;virtualenv&amp;gt;'''&amp;lt;br&amp;gt;&lt;br /&gt;
'''python &amp;lt;myscript.py&amp;gt;'''&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;&lt;br /&gt;
Save the file into the folder where your script is, but change the extension from ''.txt'' to ''.bat'', for example, save the file as ''startmyscript.bat''.&lt;br /&gt;
&lt;br /&gt;
== Summary for Tobii users (and others that need 32 bits Psychopy) ==&lt;br /&gt;
Since Tobii does not support 64 bits systems and does not support Python with a version higher than 3.6, the labcomputer has a special virtualenv that is called '''Python36'''. This virtualenv contains everything that Psychopy needs to install, and it contains the '''tobii-research''' package. It also contains the packages that are needed to use the '''cv.dll''' library. &amp;lt;br&amp;gt;&lt;br /&gt;
To start your script you can: &amp;lt;br&amp;gt;&lt;br /&gt;
- start Psychopy using the icon on the desktop that uses the 32-bit version. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Psychopy''' to start the 32 bit Psychopy version.&amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window, type '''workon Python36''', then type '''Spyder3''' to start the Spyder IDE.&amp;lt;br&amp;gt;&lt;br /&gt;
- choose the ''Python 3.6 (Python36)'' python interpreter in PyCharm. &amp;lt;br&amp;gt;&lt;br /&gt;
- from a command window type '''workon Python36''', then type '''python &amp;lt;myscript.py&amp;gt;''' to start your script. Or make a batch file that does this.&lt;/div&gt;</summary>
		<author><name>H.voogd</name></author>
	</entry>
</feed>