Shane T Mueller

Thanks for reporting this. I've confirmed that this present in pebl 2.4. This is caused by an improper use of a deprecated parameter in the final report generation, but otherwise data should be intact and shouldn't impact anything reporting the summary error rate. I'll fix it in the github, but if you want to fix it, just delete the line 192 in gonogo.pbl or comment it out with a # FilePrint(gSumFileOut, "Use mouse: " + gParams.usemouse) You can find the gonogo file in My Documents\pebl-exp.2.4\my_studies\STUDYNAME\gonogo\...

Hi, this is the old launcher and no longer is supported. I'm not sure exactly how you ran it, so maybe I had something in the standalone package misconfigured. There should be a pebl-launcher.exe in the bin/ directory that allows you to run the new launcher, but I'll need to check out how to access it.

I think the pursuit rotor instructions are very limited and progress as soon as you hit a key. You might edit the file and after the MakeWindow() line add a MessageBox("instructions here", gWin). This will add a new instructions page and you can add whatever text you want. I am nearing release of PEBL 2.2, and have files staged for release at https://sourceforge.net/projects/pebl/files/pebl/2.2/ You may have better luck with these, although there have been a massive amount of changes, updates, and...

I don't know what the anticipation test is, so I don't think so. I'm about to release a new release in the next month and I'm removing the nag screen on the launcher--we will have a comprehensive on-line system which will be a better way of supporting PEBL development. Email me at my mtu.edu account if you'd like the current password.

What is the syntax error? Did it give a line number? I'm not seeing an error like that when I run it. I've added a beep stimulus that gets played when the 'x' appears. Note that you will need to edit the instructions to specify that they need to hit the 'x' key, although you can change the parameters to use another key using the edit parameters dialog. I guess if they are blind, you don't need to change the instructions on-screen, you just need to show them which key to press. You can update the...

updating nback data coding instructions.

I haven't looked at this task for a decade, so let me try to decipher it from looking at the code: subnum,time,posX,posY,userdeltaX,userdeltaY,timeDelta,targetDeltaX,targetDeltaY,deviation,mouseD1,mouseD2 6,1,3446,0.705094,0.799724,0,0,0,0.705094,0.799724,1.06617,0,0 6,1,3460,1.40433,1.61463,0,0,14,0.699234,0.814906,2.1399,0,0 6,1,3474,2.09821,2.44424,0,0,14,0.693877,0.829608,3.2213,0,0 6,1,3488,2.78767,3.28686,0,0,14,0.689461,0.842619,4.30982,0,0 6,1,3502,3.47358,4.1408,0,0,14,0.685912,0.853945,5.40481,0,0...

You might want to consider something like the continuous performance task (PCPT) modeled after conner's CPT; or another go/no-go task like TOVA or the oddball task. The tempo of those tasks is a lot faster (1/sec or so instead of 1/minute). You get more data, and it is probably a better measure of general sustained attention and vigilance decrement than PVT which is really designed to catch people literally falling asleep after sleep deprivation.