pyepl-users Mailing List for PyEPL

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Callitng Asll Male Virgins.www .ze44. com

How Pheroomnes Can Give You A Better sex Lfie.www .se57. net

Your Naughtty Wekeend 101 Guide For Hot sex www. ku17. net. Chhina coon man proves money doesn't grow on trees

The #1 Way to Excite a Woman - The Dirty Little Sercet of Driving a Woman Wiild With Desire www. ca35. net. Modern marriage nhad mortgages enter Chinese lexicon

Rediscover Senssuality With sexy Lingjerie www. pill84. net. Panbty Prank Bennches 6 Cheerleaders

Tanrta: What iss Tantra? www . shop28 . net

Hi,

Sorry for the clutter. From what I understood eegtrack only allows to send 
data. I will need send and receive data through the parport (linux) however, 
so I will just use pyParallel. 

Thanks.

Wolfgang

ps. We tried to order activewire boards. Nothing had arrived after one month. 
Nobody awnsered phone calls or emails. Luckily after a couple days we were at 
least able to reach someone to cancel. Hurray active wire inc!

Hi!

I am trying to start using sync-pulsing. However, somehow I cannot find any 
example code, and looking at help(EEGTrack) did not provide all necessary 
insights. I saw a mention of some ominous py300new program earlier  in the 
mailing list, however I can't find it. 

In general, is there space somewhere, where uses can commit there programs for 
other people to learn from it???

Thanks!

Wolfgang

Good question :)

I've not tried myself and we did not explicitly put in unicode support
that I know of, however, it may just work and, if not, I'm happy to
look into making it work.

One requirement would be that pygame support unicode.  Obviously,
python has some support for unicode, so give it a whirl...

Is it just that you want to present a unicode string on the screen?

Best,
Per

On Thu, Mar 6, 2008 at 10:13 AM, Yaroslav Halchenko
<de...@on...> wrote:
> Hi Guys,
>
>  Some lab members got problem with displaying unicode text within PyEPL
>  -- I didn't look into it myself but decided to ask first if anyone used
>  it with unicode and if it is supported/not-supported and what to do to
>  have it support unicode? ;-)
>
>  thanks in advance
>
>  --
>                                   .-.
>  =------------------------------   /v\  ----------------------------=
>  Keep in touch                    // \\     (yoh@|www.)onerussian.com
>  Yaroslav Halchenko              /(   )\               ICQ#: 60653192
>                    Linux User    ^^-^^    [175555]
>
>
>
>  _______________________________________________
>  Pkg-exppsy-maintainers mailing list
>  Pkg...@li...
>  http://lists.alioth.debian.org/mailman/listinfo/pkg-exppsy-maintainers
>

Hi Guys,

Some lab members got problem with displaying unicode text within PyEPL
-- I didn't look into it myself but decided to ask first if anyone used
it with unicode and if it is supported/not-supported and what to do to
have it support unicode? ;-)

thanks in advance

-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]

I've been using a button callback to raise an exception, which then takes me
to the Except portion of my code. For the most part, it seems to work like
magic. I can get it to go to the appropriate Except line and then follow
that code (such as print commands or the like). However, it chokes whenever
it needs input, such as a ButtonChooser for a Stim.present (i.e., it will
just hang on the stimulus presentation, waiting for an input despite
pounding the keyboard unless I set a max time). I've been trying everything
to figure it out - I've tried flushing the Tracks, finalizing and then
initializing the hardware/pyEPL before setting new Track names and then
setting the ButtonChooser. I've also tried jumping directly from the
callback function to the appropriate portion of the code - or to an imported
module.

Is it trying to pass the callback key and is just stuck on that, not
allowing me to use the keyboard input after that? Any ideas?

Below is a small program (with explanation below) that raises the problem
I've been encountering in more complicated script:

#!/usr/bin/python

from pyepl.locals import *
# other modules
import random
import time
import RandomArray
import os
import sys
import shutil
import copy
import pickle
import exceptions
import optparse

#import keyboard, etc. to allow jumpback exception
from pyepl.exputils import *
from pyepl.keyboard import *

#Default font
setDefaultFont(Font("Verdana.ttf"))

button2 = keyboard.Key("ESCAPE") & keyboard.Key("F2")
button3 = keyboard.Key("F12")

#Allow users to skip to the Final tests
class CustomException(Exception): pass

def endJump(option, opt_str, value, parser):
        raise CustomException()

parser = optparse.OptionParser()
parser.add_option("--endJump Callback", action="callback", callback=endJump)

def runme(exp):
        vt.clear("black")
        stim = Text("This is a test - hit 'S'!")
        bc = ButtonChooser(Key("S"))
        vt.clear("black")

        #present the question
        (ts, b, rt) = stim.present(clk=clk, duration=3000, bc=bc)

        #decide which input files to use
        if b==Key("S"):
            flashStimulus(Text("You chose S"), 1500, clk=clk)
        else:
            print "better luck next time"

if __name__ == "__main__":
    #start PyEPL, parse command line options, and do subject housekeeping
    exp = Experiment()
    exp.parseArgs()
    exp.setup()

    #allow users to break out of the experiment with escape-F1 (the default
key combo)
    exp.setBreak()

    #allow users to jump to the final tests
    button2.addCallback(endJump, None, None)
    button3.addCallback(endJump, None, None)

    #get the subject configuration
    config = exp.getConfig()

    #Create a VideoTrack object for interfacing with monitor, and a KeyTrack
object for interfacing with keyboar
    vt = VideoTrack("video")
    kt = KeyTrack("key")
    log = LogTrack("session")
    audio = AudioTrack("audio")

    # create a PresentationClock to handle timing
    clk = PresentationClock()

    global state
    exp.saveState(None, sessionNum=0, trialNum=0, subsession=0, day=1)
    # get the state
    state = exp.restoreState()

    try:
            #run the subject
            runme(exp)

    except CustomException:
            print "Take me to End!"
            vt.clear("black")
            stim = Text("This is a test - hit 'N'!")
            bc = ButtonChooser(Key("N"))
            vt.clear("black")

            #present the question
            (ts, b, rt) = stim.present(clk=clk, duration=3000, bc=bc)

            #decide which input files to use
            if b==Key("N"):
                    flashStimulus(Text("You chose N"), 1500, clk=clk)
            else:
                    print "oh well..."

Basically, I added assigned two buttons (ESCAPE+F2 and F12 alone) that are
attached to a callback to the "endJump" function, which raises an exception
that takes you from what the program is trying to run (runme function) to
the code at the very bottom beginning with "print "Take me to End!". I've
moved this except function all around -- to another defined function
above/to an imported module, but that doesn't seem to help any.

So I run the experiment, when the first question pops up, I hit F12 as if
someone came into the hospital room and I have to jump to an abbreviated
version of the experiment in order to finish in time. It does jump down to
the "print 'Take me to End!" command, and even presents the stim on the
screen "...hit 'N'!). However, it won't register my button press --
eventually it times out, and prints "oh well".

I've tried naming the buttonchooser other things, but that doesn't seem to
work... I've also tried re-creating audio/video/key tracks, no luck there
either. Though if I leave in a second audio track, I get an OS-X built in
audio error (I assume it just can't handle the multiple streams).

Am I doing something obviously wrong?

Thanks,

Justin Hulbert

You're welcome, but Per handled this :)

Thanks again for the packaging.

Aaron

On May 9, 2007, at 11:15 PM, Yaroslav Halchenko wrote:

> Thank you Aaron for the satisfying my feature request ;) It works  
> for me
> just fine on the test examples.
>
> For Debian/Ubuntu users:
> 1.0.29 got uploaded to unstable Debian. If there is any particular
> necessity to have it built for some other release of Debian or  
> Ubuntu --
> let me know.
>
> Best
> Yarik

I've had the exact same issue with the ATI Technologies Inc Radeon
Mobility M6 LY card. I tried hard to fix it, even different xservers,
but always got the same error message. I think it is an issue with the
card not being able to handle some OpenGL instruction that pyepl
relies on. So, I'm sorry to say, but you probably won't be able to run
pyepl with this video card.

> Date: Tue, 3 Apr 2007 01:14:32 -0400
> From: Yaroslav Halchenko <li...@on...>
> Subject: [Pyepl-users] OpenGL pukes on me
> To: pye...@li...
> Message-ID: <200...@wa...>
> Content-Type: text/plain; charset=us-ascii
>
> Dear PyEPLers,
>
> Before I dig into troubleshooting of my crappy video card (ATI
> Technologies Inc Radeon Mobility M6 LY) I thought to ask you first since
> may be you will give me a quick hint. Testing the pyepl experiment on my
> laptop I got:
>
> $> ./blank.py --config config_gen.py --sconfig config_exp1-hands_feet.py -s subj01_01
> libGL warning: 3D driver claims to not support visual 0x4b
> Traceback (most recent call last):
>   File "./blank.py", line 19, in ?
>     video = VideoTrack("video")
>   File "/usr/lib/python2.4/site-packages/pyepl/display.py", line 1049, in __init__
>     textlog.LogTrack.__init__(self, basename, archive, autoStart)
>   File "/usr/lib/python2.4/site-packages/pyepl/textlog.py", line 41, in __init__
>     self.startService()
>   File "/usr/lib/python2.4/site-packages/pyepl/display.py", line 1085, in startService
>     hardware.startVideo()
>   File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/__init__.py", line 220, in startVideo
>     LowImage(os.path.join(pyepldir, "resources", "splash.png")).scale(x + 1, y + 1).show(0, 0)
>   File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/image.py", line 344, in __init__
>     self.gl_texture = OGLSprite(self.surf)
>   File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/image.py", line 201, in __init__
>     glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, w2, h2, 0, GL_RGBA, GL_UNSIGNED_BYTE, rgba)
> OpenGL.GL.GLerror: [Errno 1281] invalid value
> Exception exceptions.AttributeError: <exceptions.AttributeError instance at 0xb60ea90c> in <bound method OGLSprite.__del__ of <pyepl.hardware.graphics.image.OGLSprite instance at 0xb608f52c>> ignored
>
>
> Any ideas on how to fight it would be really appreciated since I thought to run
> the experiment on the beast tomorrow...
>
> --
>                                   .-.
> =------------------------------   /v\  ----------------------------=
> Keep in touch                    // \\     (yoh@|www.)onerussian.com
> Yaroslav Halchenko              /(   )\               ICQ#: 60653192
>                    Linux User    ^^-^^    [175555]

Thank you Aaron for the satisfying my feature request ;) It works for me
just fine on the test examples.

For Debian/Ubuntu users:
1.0.29 got uploaded to unstable Debian. If there is any particular
necessity to have it built for some other release of Debian or Ubuntu --
let me know.

Best
Yarik

On Thu, 03 May 2007, Aaron Geller wrote:

> For pyepl through version 1.0.28, it is, in fact, the case that  
> timing error must be compensated for manually.

> As of pyepl version 1.0.29, however, the PresentationClock  
> constructor takes a parameter called correctAccumulatedErrors.  This  
> defaults to False, but if you set this to True, the clock will now  
> automatically correct for timing errors any time delay() or jitter()  
> is called.

> I can't account for the occasional > 1s lags, however.

> Best,
> Aaron
-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]

For pyepl through version 1.0.28, it is, in fact, the case that  
timing error must be compensated for manually.

As of pyepl version 1.0.29, however, the PresentationClock  
constructor takes a parameter called correctAccumulatedErrors.  This  
defaults to False, but if you set this to True, the clock will now  
automatically correct for timing errors any time delay() or jitter()  
is called.

I can't account for the occasional > 1s lags, however.

Best,
Aaron

On Apr 5, 2007, at 11:22 PM, Yaroslav Halchenko wrote:

> Dear PyEPL People,
>
> I might be doing smth wrong, so please don't kick me hard ;-)  
> please advise on
> how can I avoid accumulating the lag -- should my program adjust  
> presentation
> of each flashStimulus for that "manually"?
>
> I have a very simple block design, where stimuli is presented using
> following loop:
> ,------------------------------------------------------------------
> | for block in stimuli_blocks:
> |         log.logMessage('BLOCK_START of %s'%block[0])
> |         flashStimulus(Text(block[0]), block[1], clk=mypc)
> |         log.logMessage('BLOCK_END of %s'%block[0])
> |         flashStimulus(Text("+"), config.rest_duration, clk=mypc)
> `---
>
> block[1] and config.rest_duration are set to be 8000. After I  
> collect the
> data, and convert timestamps into a convenient form using following  
> conversion:
>
> ,---
> | retime = re.compile('^(?P<timestamp>[0-9]{13})(?P<rest>\s.*$)')
> | prev_timestamp = 0
> | for l in sys.stdin.readlines():
> |     res = retime.search(l)
> |     if res:
> |         timestamp_sec = float(res.groupdict()['timestamp'])/1000.0
> |         timestamp = datetime.datetime.fromtimestamp(timestamp_sec)
> |         print '%s (d=%f) %s'%(timestamp.isoformat(' '),  
> timestamp_sec  - prev_timestamp, l.strip())
> |         prev_timestamp = timestamp_sec
> |     else:
> |         print l,
> `---
>
> I get following:
>
> ,--------------------------------------------------------------------- 
> ------------------------------
> | 2007-04-05 00:35:20.491000 (d=8.051000) 1175747720491   0        
> BLOCK_START of Imagery Both Feet
> | 2007-04-05 00:35:28.514000 (d=8.023000) 1175747728514   0        
> BLOCK_END of Imagery Both Feet
> | 2007-04-05 00:35:36.569000 (d=8.055000) 1175747736569   0        
> BLOCK_START of Overt Left Hand
> | 2007-04-05 00:35:44.584000 (d=8.015000) 1175747744584   0        
> BLOCK_END of Overt Left Hand
> | 2007-04-05 00:35:52.597000 (d=8.013000) 1175747752597   0        
> BLOCK_START of Imagery Tongue
> | 2007-04-05 00:36:00.615000 (d=8.018000) 1175747760615   0        
> BLOCK_END of Imagery Tongue
> | 2007-04-05 00:36:08.670000 (d=8.055000) 1175747768670   0        
> BLOCK_START of Overt Right Hand
> | 2007-04-05 00:36:16.687000 (d=8.017000) 1175747776687   0        
> BLOCK_END of Overt Right Hand
> | 2007-04-05 00:36:25.808000 (d=9.121000) 1175747785808   0        
> BLOCK_START of Imagery Both Feet
> | 2007-04-05 00:36:34.021000 (d=8.213000) 1175747794021   0        
> BLOCK_END of Imagery Both Feet
> | 2007-04-05 00:36:42.035000 (d=8.014000) 1175747802035   0        
> BLOCK_START of Overt Tongue
> | 2007-04-05 00:36:50.091000 (d=8.056000) 1175747810091   0        
> BLOCK_END of Overt Tongue
> | 2007-04-05 00:36:58.103000 (d=8.012000) 1175747818103   0        
> BLOCK_START of Overt Tongue
> | 2007-04-05 00:37:06.124000 (d=8.021000) 1175747826124   0        
> BLOCK_END of Overt Tongue
> | ..............
> | 2007-04-05 00:55:59.049000 (d=8.064000) 1175748959049   0        
> BLOCK_START of Imagery Left Hand
> | 2007-04-05 00:56:07.112000 (d=8.063000) 1175748967112   0        
> BLOCK_END of Imagery Left Hand
> | 2007-04-05 00:56:15.174000 (d=8.062000) 1175748975174   0        
> BLOCK_START of Imagery Tongue
> | 2007-04-05 00:56:25.395000 (d=10.221000) 1175748985395  0        
> BLOCK_END of Imagery Tongue
> | 2007-04-05 00:56:33.503000 (d=8.108000) 1175748993503   0        
> BLOCK_START of Imagery Tongue
> | 2007-04-05 00:56:41.524000 (d=8.021000) 1175749001524   0        
> BLOCK_END of Imagery Tongue
> | 2007-04-05 00:56:49.539000 (d=8.015000) 1175749009539   0        
> BLOCK_START of Imagery Right Hand
> `---
> As you can see
>
> 1. I slowly accumulate the time lag due to difference in .05 sec on
> each flashStimulus (or may be logMessage?)
>
> 2. some times presentation gets delayed as much as by 1 sec. (the  
> laptop
> I am running it on is an Ok laptop, so I am not expecting that much  
> of the
> delay)
>
> Do I have to monitor time stamps manually and adjust the duration  
> of each
> following flashStimulus to  do not accumulate the drag?? I thought  
> that clk= is
> there for exactly this reason. I was running pyepl 1.0.26-1 (Debian  
> etch)

Dear PyEPL Users,

PyEPL v. 1.0.29 is now posted to http://pyepl.sf.net.  Here is the  
changelog:

1. Fixed environment.pyx so it compiles with latest pyrexc.
2. Added automatic time-lag correction in PresentationClock
3. Fixed recursion error in pollEvents.
4. Implemented linux version of setSignal for sync-pulsing.

Happy coding,
The PyEPL Team

Dear PyEPL People,

I might be doing smth wrong, so please don't kick me hard ;-) please advise on
how can I avoid accumulating the lag -- should my program adjust presentation
of each flashStimulus for that "manually"?

I have a very simple block design, where stimuli is presented using
following loop:
,------------------------------------------------------------------
| for block in stimuli_blocks:
|         log.logMessage('BLOCK_START of %s'%block[0])
|         flashStimulus(Text(block[0]), block[1], clk=mypc)
|         log.logMessage('BLOCK_END of %s'%block[0])
|         flashStimulus(Text("+"), config.rest_duration, clk=mypc)
`---

block[1] and config.rest_duration are set to be 8000. After I collect the
data, and convert timestamps into a convenient form using following conversion:

,---
| retime = re.compile('^(?P<timestamp>[0-9]{13})(?P<rest>\s.*$)')
| prev_timestamp = 0
| for l in sys.stdin.readlines():
|     res = retime.search(l)
|     if res:
|         timestamp_sec = float(res.groupdict()['timestamp'])/1000.0
|         timestamp = datetime.datetime.fromtimestamp(timestamp_sec)
|         print '%s (d=%f) %s'%(timestamp.isoformat(' '), timestamp_sec  - prev_timestamp, l.strip())
|         prev_timestamp = timestamp_sec
|     else:
|         print l,
`---

I get following:

,---------------------------------------------------------------------------------------------------
| 2007-04-05 00:35:20.491000 (d=8.051000) 1175747720491   0       BLOCK_START of Imagery Both Feet
| 2007-04-05 00:35:28.514000 (d=8.023000) 1175747728514   0       BLOCK_END of Imagery Both Feet
| 2007-04-05 00:35:36.569000 (d=8.055000) 1175747736569   0       BLOCK_START of Overt Left Hand
| 2007-04-05 00:35:44.584000 (d=8.015000) 1175747744584   0       BLOCK_END of Overt Left Hand
| 2007-04-05 00:35:52.597000 (d=8.013000) 1175747752597   0       BLOCK_START of Imagery Tongue
| 2007-04-05 00:36:00.615000 (d=8.018000) 1175747760615   0       BLOCK_END of Imagery Tongue
| 2007-04-05 00:36:08.670000 (d=8.055000) 1175747768670   0       BLOCK_START of Overt Right Hand
| 2007-04-05 00:36:16.687000 (d=8.017000) 1175747776687   0       BLOCK_END of Overt Right Hand
| 2007-04-05 00:36:25.808000 (d=9.121000) 1175747785808   0       BLOCK_START of Imagery Both Feet
| 2007-04-05 00:36:34.021000 (d=8.213000) 1175747794021   0       BLOCK_END of Imagery Both Feet
| 2007-04-05 00:36:42.035000 (d=8.014000) 1175747802035   0       BLOCK_START of Overt Tongue
| 2007-04-05 00:36:50.091000 (d=8.056000) 1175747810091   0       BLOCK_END of Overt Tongue
| 2007-04-05 00:36:58.103000 (d=8.012000) 1175747818103   0       BLOCK_START of Overt Tongue
| 2007-04-05 00:37:06.124000 (d=8.021000) 1175747826124   0       BLOCK_END of Overt Tongue
| ..............
| 2007-04-05 00:55:59.049000 (d=8.064000) 1175748959049   0       BLOCK_START of Imagery Left Hand
| 2007-04-05 00:56:07.112000 (d=8.063000) 1175748967112   0       BLOCK_END of Imagery Left Hand
| 2007-04-05 00:56:15.174000 (d=8.062000) 1175748975174   0       BLOCK_START of Imagery Tongue
| 2007-04-05 00:56:25.395000 (d=10.221000) 1175748985395  0       BLOCK_END of Imagery Tongue
| 2007-04-05 00:56:33.503000 (d=8.108000) 1175748993503   0       BLOCK_START of Imagery Tongue
| 2007-04-05 00:56:41.524000 (d=8.021000) 1175749001524   0       BLOCK_END of Imagery Tongue
| 2007-04-05 00:56:49.539000 (d=8.015000) 1175749009539   0       BLOCK_START of Imagery Right Hand
`---
As you can see

1. I slowly accumulate the time lag due to difference in .05 sec on
each flashStimulus (or may be logMessage?)

2. some times presentation gets delayed as much as by 1 sec. (the laptop
I am running it on is an Ok laptop, so I am not expecting that much of the
delay)

Do I have to monitor time stamps manually and adjust the duration of each
following flashStimulus to  do not accumulate the drag?? I thought that clk= is
there for exactly this reason. I was running pyepl 1.0.26-1 (Debian etch)

-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]

I have now clue what those errors mean, but in my own quest to run an
experiment on a laptop with an ATi card, I discovered ENVY. This is a
script that will install the best proprietery driver for your NVidia or
ATi card. For me, it worked...

Good luck!

Yaroslav Halchenko schreef:
> Dear PyEPLers,
>
> Before I dig into troubleshooting of my crappy video card (ATI
> Technologies Inc Radeon Mobility M6 LY) I thought to ask you first since
> may be you will give me a quick hint. Testing the pyepl experiment on my
> laptop I got:
>
> $> ./blank.py --config config_gen.py --sconfig config_exp1-hands_feet.py -s subj01_01
> libGL warning: 3D driver claims to not support visual 0x4b
> Traceback (most recent call last):
>   File "./blank.py", line 19, in ?
>     video = VideoTrack("video")
>   File "/usr/lib/python2.4/site-packages/pyepl/display.py", line 1049, in __init__
>     textlog.LogTrack.__init__(self, basename, archive, autoStart)
>   File "/usr/lib/python2.4/site-packages/pyepl/textlog.py", line 41, in __init__
>     self.startService()
>   File "/usr/lib/python2.4/site-packages/pyepl/display.py", line 1085, in startService
>     hardware.startVideo()
>   File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/__init__.py", line 220, in startVideo
>     LowImage(os.path.join(pyepldir, "resources", "splash.png")).scale(x + 1, y + 1).show(0, 0)
>   File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/image.py", line 344, in __init__
>     self.gl_texture = OGLSprite(self.surf)
>   File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/image.py", line 201, in __init__
>     glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, w2, h2, 0, GL_RGBA, GL_UNSIGNED_BYTE, rgba)
> OpenGL.GL.GLerror: [Errno 1281] invalid value
> Exception exceptions.AttributeError: <exceptions.AttributeError instance at 0xb60ea90c> in <bound method OGLSprite.__del__ of <pyepl.hardware.graphics.image.OGLSprite instance at 0xb608f52c>> ignored
>
>
> Any ideas on how to fight it would be really appreciated since I thought to run
> the experiment on the beast tomorrow...
>
>   

Dear PyEPLers,

Before I dig into troubleshooting of my crappy video card (ATI
Technologies Inc Radeon Mobility M6 LY) I thought to ask you first since
may be you will give me a quick hint. Testing the pyepl experiment on my
laptop I got:

$> ./blank.py --config config_gen.py --sconfig config_exp1-hands_feet.py -s subj01_01
libGL warning: 3D driver claims to not support visual 0x4b
Traceback (most recent call last):
  File "./blank.py", line 19, in ?
    video = VideoTrack("video")
  File "/usr/lib/python2.4/site-packages/pyepl/display.py", line 1049, in __init__
    textlog.LogTrack.__init__(self, basename, archive, autoStart)
  File "/usr/lib/python2.4/site-packages/pyepl/textlog.py", line 41, in __init__
    self.startService()
  File "/usr/lib/python2.4/site-packages/pyepl/display.py", line 1085, in startService
    hardware.startVideo()
  File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/__init__.py", line 220, in startVideo
    LowImage(os.path.join(pyepldir, "resources", "splash.png")).scale(x + 1, y + 1).show(0, 0)
  File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/image.py", line 344, in __init__
    self.gl_texture = OGLSprite(self.surf)
  File "/usr/lib/python2.4/site-packages/pyepl/hardware/graphics/image.py", line 201, in __init__
    glTexImage2D(GL_TEXTURE_2D, 0, GL_RGBA, w2, h2, 0, GL_RGBA, GL_UNSIGNED_BYTE, rgba)
OpenGL.GL.GLerror: [Errno 1281] invalid value
Exception exceptions.AttributeError: <exceptions.AttributeError instance at 0xb60ea90c> in <bound method OGLSprite.__del__ of <pyepl.hardware.graphics.image.OGLSprite instance at 0xb608f52c>> ignored

Any ideas on how to fight it would be really appreciated since I thought to run
the experiment on the beast tomorrow...

-- 
                                  .-.
=------------------------------   /v\  ----------------------------=
Keep in touch                    // \\     (yoh@|www.)onerussian.com
Yaroslav Halchenko              /(   )\               ICQ#: 60653192
                   Linux User    ^^-^^    [175555]

Thanks Yarik
A slightly easier url (equivalent to the one below) is
http://www.psychopy.org

:-)

all the best
Jon

Yaroslav Halchenko wrote:
> Hi Jon,
>
> Thank you for your reply!
> Indeed, psychopy seems like a good candidate to be packaged for Debian
> ;-) I will have a look at it in details in few days and let you know
> if Debian package for it becomes available for anyone willing to test.
>
> As for PyEPL -- I am forwarding this reply to pyepl-users mailing list,
> which can be more fruitful for any discussion about two products and the
> possible interaction between them.
>
> Dear PyEPL authors and users. Michael ran across another nice,
> python-based project for stimuli delivery
> http://www.psychology.nottingham.ac.uk/staff/jwp/psychopy/home.php/Main/HomePage
> and below you could find my buzz email to its mailing list and a kind
> reply from its author ;-) I think that both projects might benefit one
> way or another from each other.
>
> Best regards
> Yarik
>   

-- 
Jon Peirce
Nottingham University
+44 (0)115 8467176 (tel)
+44 (0)115 9515324 (fax)

http://www.peirce.org.uk/

This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.

Hi Jon,

Thank you for your reply!
Indeed, psychopy seems like a good candidate to be packaged for Debian
;-) I will have a look at it in details in few days and let you know
if Debian package for it becomes available for anyone willing to test.

As for PyEPL -- I am forwarding this reply to pyepl-users mailing list,
which can be more fruitful for any discussion about two products and the
possible interaction between them.

Dear PyEPL authors and users. Michael ran across another nice,
python-based project for stimuli delivery
http://www.psychology.nottingham.ac.uk/staff/jwp/psychopy/home.php/Main/HomePage
and below you could find my buzz email to its mailing list and a kind
reply from its author ;-) I think that both projects might benefit one
way or another from each other.

Best regards
Yarik

On Thu, 29 Mar 2007, Jon Peirce wrote:

> I'd never heard of PyEPL, but looking at it I'd say the main difference is that PsychoPy is started off as a package for drawing vision-science 
> stimuli and using things like spatial frequency and envelopes and masks etc. It can do other things like text, sounds and photographic images, but 
> gratings and vision science stimuli are it's special forte.

> Also handles monitor calibration (physical dimensions and gamma correction) so that you can specify your stimuli in degrees of visual angle rather 
> than number of pixels or percent of the screen etc.

> Just recently I also started packaging my own IDE to make it easier for users to run scripts (they often got confused about how to actually start 
> their experiment).

> I guess my gut reaction is that PsychoPy sits inbetween VisionEgg and PyEPL - a bit more simple than the former, a bit more sophisticated than the 
> latter. But i really haven't looked long at PyEPL. I'd be interested in chatting more about this stuff though. Either in the form of sharing code 
> (both ways) or helping you to modify PsychoPy if you found it worthy of inclusion in your package(s). Especially the linux aspect is of interest 
> because I don't have access to a linux box and can't test it there without others' help.

> thanks for getting in touch. All the best,
> Jon

> Yaroslav Halchenko wrote:
> >Hi,

> >A friend of mine, Michael Hanke, emailed me from his vacation (probably
> >his vacation is somewhat filled with work and web browsing) that he
> >found a new cool project - PsychoPy.

> >It indeed sounds cool since both of us working on packaging
> >psychology relevant software for Debian Linux distribution:
> >http://alioth.debian.org/projects/pkg-exppsy/

> >As a part of the project we maintain package for PyEPL
> >http://pyepl.sourceforge.net/
> >which even became a part of coming etch release of Debian GNU/Linux.

> >You've mentioned on your page visionegg (which we packaged as well, but
> >not yet pushed to Debian) but not PyEPL. It would be really interesting
> >if you compare your project to PyEPL.

> >Please CC me since I am not on the list.
-- 
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student  Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW:     http://www.linkedin.com/in/yarik        

Sorry for the very basic question. I've been trying to make the switch from
PsyScript to PyEPL and it's taking me some time to get up to speed. After
working my way through the examples/documentation, I'm still having a bit of
trouble figuring out how to do what I assume are very basic procedures in
PyEPL/python. Rather than reinventing the wheel, I was hoping someone could
give me a leg-up with some advice, or perhaps some example code.

Basically, my lab uses a counterbalanced set of presentation orders (rather
than being randomized). So for any subject in a given counterbalancing
order, there is a separate input file, consisting of a number of columns.
For simplicity, let's say there are two columns: 1) a word pair to be
presented on the screen (e.g., shoe-table); 2) a code that specifies in what
color the pair should be presented.

How might I tell PyEPL to read in the input file and present the contents of
the first column (each pair) in turn, in the color specified by the
corresponding item in the second column?

Again, sorry for the extremely low-level question. I really appreciate any
help you might be able to provide.

Also, is there an accessible database of PyEPL experiments generated by the
community, aside from those example experiments already posted on the
website? 

Thanks again for providing a great (and one of the few) options for
experiment presentation on macs.

J 

If I am correct updateScreen returns the moment of updating the screen
which would allow you to calculate an RT on the fly.

timeOneScreen = videoTrack.updateScreen(presentationClock)

Hope this helps!

Wolfgang Pauli schreef:
> Hi,
>
> I am writing a simple experiment during which Images are presented at certain 
> parts of the screen. This part works fine with showProportional and 
> updateScreen. But I would like to calculate RTs on the fly. From the 
> documentation I figured (simple Stroop) that Image.present would do that for 
> me, but this method does not allow me to define the position where the image 
> should be presented on the screen. Any hints? Thanks!
>
> Wolfgang
>   
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Pyepl-users mailing list
> Pye...@li...
> https://lists.sourceforge.net/lists/listinfo/pyepl-users
>   

Hi,

I am writing a simple experiment during which Images are presented at certa=
in=20
parts of the screen. This part works fine with showProportional and=20
updateScreen. But I would like to calculate RTs on the fly. From the=20
documentation I figured (simple Stroop) that Image.present would do that fo=
r=20
me, but this method does not allow me to define the position where the imag=
e=20
should be presented on the screen. Any hints? Thanks!

Wolfgang

Hi,

	Supported inexpensive Mac interface cards seem to be few an far  
between (can anyone get a response from Activewire?, Delcom?).  While  
it is not inexpensive I encourage others to contact the makers of the  
PsyScope button box to develop a Python module as their next  
project.  They seem pretty keen on the idea from my brief discussions  
and that it would be much easier than a MatLab plug in.  And, it is a  
very good button box, especially for voice keys.

John Christie

2006	Jan	Feb	Mar (9)	Apr (5)	May (4)	Jun	Jul (2)	Aug (1)	Sep (1)	Oct (2)	Nov (3)	Dec (2)
2007	Jan (2)	Feb (3)	Mar (3)	Apr (3)	May (5)	Jun	Jul (1)	Aug	Sep	Oct	Nov	Dec
2008	Jan	Feb	Mar (2)	Apr	May	Jun	Jul	Aug (2)	Sep	Oct	Nov	Dec
2009	Jan	Feb	Mar	Apr	May	Jun (11)	Jul (20)	Aug	Sep	Oct	Nov	Dec

pyepl-users Mailing List for PyEPL

pyepl-users — General mailing list for PyEPL users.