Pylink Import Error

[chris2307]

Hi all,

I am using Vizard 5 32 bit and have attempted to import pylink in to my project file as follows:

sys.path.append("C:\WayfindingResearchCentre/pylink/pylink23")
print sys.path

I get this error:

ImportError: DLL load failed: The specified module could not be found.

In Vizard 4 42 bit, the pylink module is loaded in fine.

Does anyone know why this breaks in Vizard 5?

Thanks

[chris2307]

Sorry, I definitely copied the above code incorrectly. It should read:

sys.path.append("C:\WayfindingResearchCentre/pylink/pylink23")
import pylink

[farshizzo]

What version of pylink is installed in that directory? I installed the latest version of pylink through the Tools > Package Manager interface. After it installed I ran the following:

import pylink

And it imported successfully. Can you try installing the latest version?

[chris2307]

Okay,

So I guess it may have been installed incorrectly. The people who previously worked with pylink in Vizard 4 did not install it via the package manager but directly linked their project to the pylink directory (as I have tried to do above).

Installing pylink in the Vizard 5 beta means I can now import pylink. However, the previous code breaks and I now see this error.

Traceback (most recent call last):
  File "<string>", line 11, in <module>
  File "C:\Users\Operator\Desktop\Application\src\functions\EyeTracker.py", line 194, in <module>
    beginExperiment()
  File "C:\Users\Operator\Desktop\Application\src\functions\EyeTracker.py", line 138, in beginExperiment
    _setupConnection(False)
  File "C:\Users\Operator\Desktop\Application\src\functions\EyeTracker.py", line 20, in _setupConnection
    eyelinktracker = pylink.EyeLink()     # Real connection
AttributeError: 'module' object has no attribute 'EyeLink'

The code at which it fails at is:

	if dummy == True:
		eyelinktracker = pylink.EyeLink(None) # open dummy connection
	else:
		eyelinktracker = pylink.EyeLink()     # Real connection

I'm getting frustrated now because I feel like I am missing something really obvious here...

[farshizzo]

I'm thinking the pylink module you are using is different than the official one that is hosted on the Python Package Index. Do you know where the previous module came from?

[chris2307]

The previous module came from the SR Research thread which contained links to the different platform specific pylink. I downloaded win32.

https://www.sr-support.com/showthread.php?14-Pylink

When importing manually, it works for Vizard4 but not at all for Vizard5. I have eliminated the possibility that it could be looking elsewhere by specifying the exact file path also.

I would prefer to install pylink using the package manager as this seems like the "proper" way to do things. FYI - When I did this, I downloaded Pylink 0.3.2 through the package manager interface. I saw no other versions available.

[farshizzo]

The pylink that is listed on the Python Package Index is completely unrelated to the pylink library provided by SR Research. I was able to get the pylink library provided by SR Research to work using the following steps:

1. Download pylink_win32.zip from https://www.sr-support.com/showthread.php?14-Pylink
2. Extract the zip file to your local computer
3. Copy the entire pylink27 subfolder to the Vizard/bin/lib/site-packages folder
4. Rename the pylink27 folder to pylink
5. Now you can call import pylink from any Vizard script

I ran the above steps with Vizard 5 32-bit and it worked fine.

Note, as of the time of this post, SR Research does not seem to provide a 64-bit version of the pylink library for Windows, so this will not work with 64-bit versions of Vizard.

[chris2307]

Thank you for this.

I was completely unaware that there were two completely unrelated pylink librarys!

I will give this a go tomorrow when I am back in the office. Many thanks

[chris2307]

Just to confirm - This has worked so many thanks for your help.

I find it bizarre as I had attempted to manually link to all the sub-folders in pylink at one point or another! Must have been missing something rather obvious :/

Anyway, thank you for the help.