[carlap]

Thanks for the explanation. I can’t do the calculation the way you did it since I am interested in calculating from the exposure timeout until the key press. So… Am I correct that if I want that, I have to add 300ms to the interval between the timeout timer and the key press? I think I see how I can also do the back calculation for the others too.

Thanks!

[carlap]

Nevermind, I fixed it!

 newAudio ("Level_Up", "chipquest.mp3")
    .play()
     .wait(2000)
    ,
    getAudio("Level_Up")
    .remove
    ,
    newKey(" ")
    .wait()

[carlap]

Hi Jeremy!

Thanks. Issue 1 is all good.
Issue 2, was with multiple jpg files and with loading the file both from git and manually, but it appears to have been resolved just by waiting, so maybe it was a problem with my local chrome cache or something. Thanks!

[carlap]

So, apparently I just put: randomize (“practica_spanish”) in the sequence section and it works…

But, while I have your attention, I have my resource files loaded in Github and when I change a file in git and then sync it to my experiment, the new version of the file is not getting pulled. Even if I manually try to load the new file directly into PCIbex (using the add resource button) the file appears to load, but the old version is still in my resources. So, I can’t seem to change or update the files. I even tried deleting my experiment then reloading the entire thing from git and it’s still loading the old version of the file, which no longer exist in my git repository… Thoughts? Thanks!

[carlap]

Works like a charm! Thanks!

[carlap]

That works great! You rock! Thanks!

[carlap]

Hi. Thanks for the quick response. I´m sorry if it isn´t clear. What I would like is for the subject to be able to respond both during and after the 300ms, while the text is on the screen and also during the 5 seconds waiting time after it has been removed. But, I need a response during the 300ms to cancel the second waiting time. That is a response during the 300ms is captured and then the program just moves on to the next trial. A response after the 300ms sould have the same effect, captured and move on. Thanks!

[carlap]

I have a similar issue. I want to keep track of correct answers and I tried to integrate the information above but without success. I am not using a scale, I am using the arrow keys. My code to track the keys is:

newKey(“pressOnArrow”, “ArrowLeft”, “ArrowRight”) .callback( getTimer(“timeout”).stop() ).log(“all”) , newTimer(“timeout”, 5000).start().log().wait() , getKey(“pressOnArrow”) .disable() .test.pressed().success( newText(“Good job”).print() ) .failure( newText(“Too slow”).print() ))

Obviously that is not my original coding (thanks for the earlier help). Now, I want to track if the ArrowLeft or ArrowRight is the correct answer and store it in a variable to display at the end of a section of trials. I tried integrating:
.test.selected(row.Correct)
.success( getVar(“Acc”).set(v=>v+1) )

But it does not seem to work. I do not need to keep track of wrong answwers. Any thoughts? Thanks!

[carlap]

Thanks! That was the solution!

[Author]

Posts