hi chris,
in the process of setting up an awake behaving lab here, i am going to try to convince everyone to start using monkeyworks.
not sure if that will be a good things or a bad thing for you 
a few of things i was wondering about:
1 I know there was talk of interfacing with eyelink directly through ethernet cable, instead of using our usual Analog to Digital I/O. How far along is that project? I remember both Nicole and John Maunsell were interested in it for the eyelink 1000.
2 What is the latest in terms of the A to D I/O. I know that what we use only works at 32bits, and that no more drivers have been written for it. Any idea as to which direction we are heading in terms of that type of communication.
3 finally, for random dot kinematograms, i know that the Stefan Treue lab was developing some stuff. Any idea how far along that stuff is?
best
najib
Hi Najib,
Good to hear from you! I hope all is well in NY.
1 I know there was talk of interfacing with eyelink directly through ethernet cable, instead of using our usual Analog to Digital I/O. How far along is that project? I remember both Nicole and John Maunsell were interested in it for the eyelink 1000.
Philipp Schwedhelm developed an MWorks plugin for the EyeLink 1000, and I believe it’s actively in use in Stefan’s lab. Philipp has kindly provided a downloadable package for MWorks 0.4.5, so you can try it out if you like.
Working with Philipp to get the plugin included in the standard MWorks distribution has been on my to-do list for a while, but I haven’t gotten to it yet.
2 What is the latest in terms of the A to D I/O. I know that what we use only works at 32bits, and that no more drivers have been written for it. Any idea as to which direction we are heading in terms of that type of communication.
The folks at HEKA recently released 64-bit drivers for the ITC-18. The current MWorks nightly includes a 64-bit version of the ITC plugin, meaning you can (finally!) run MWServer in 64-bit mode when using an ITC-18.
As for other I/O devices, several labs have developed plugins for the hardware they’re using. However, I don’t have much current information on exactly which devices are supported or what the development status of the plugins is. Are there any devices you’re particularly interested in?
3 finally, for random dot kinematograms, i know that the Stefan Treue lab was developing some stuff. Any idea how far along that stuff is?
I believe the folks in Stefan’s lab are making extensive use of their custom random dot generator(s). Ralf Brockhausen (rrode at gwdg dot de) would be the person to ask.
Cheers,
Chris
Hi Chris,
Thank you so much for your detailed response.
I am in the process of setting up mworks on my experimental machine, and I
have to tell you that it has come a long way since I arrived at MIT five
years ago
Regarding the Eyelink 1000 plugin, I downloaded it, but I am not sure where
it belongs.
My guess is that it belongs in the core plugins, but i am not positive.
Also, the current readme files and documentation doesn’t have much in it.
I was wondering if you can get me in touch with Philip to get an example
file, or some instructions on setting it up.
Best
Najib
Hi Najib,
Regarding the Eyelink 1000 plugin, I downloaded it, but I am not sure where it belongs. My guess is that it belongs in the core plugins, but i am not positive.
That’s correct. If you place the .bundle package in /Library/Application Support/MWorks/Plugins/Core, then MWServer should see it.
Also, the current readme files and documentation doesn’t have much in it. I was wondering if you can get me in touch with Philip to get an example file, or some instructions on setting it up.
Sure. I’ll cc you on an email to him.
Chris