[suz]

Hi Jeremy,

Thanks so much for this, the relief is real 😉

–Susanne

[suz]

Thanks a lot! That worked, although I had to comment out both these lines, if that is helpful feedback.

   width: 40em !important; /* controls the witdth of the content area */
    margin-left: calc(50vw - 20em); /* aligns the content area's left edge with the vertical center of the page */

[suz]

Hi Jeremy,

Oops, sorry, I totally misread your answer – and I see it has already been addressed. Apologies! Still working on the code.

Best
Susanne

[suz]

Hi Jeremy,

I think what Juliana refers to is the following “reverse order logging”, which I also just detected in my maze experiment, and which only happens for Safari users:

1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,7,experiment.,1607021545338,T1,train,train,stroughnths.,0,yes,906,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,6,an,1607021545338,T1,train,train,da,0,yes,1020,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,5,for,1607021545338,T1,train,train,jud,1,yes,586,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,4,day,1607021545338,T1,train,train,zir,0,yes,540,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,3,good,1607021545338,T1,train,train,vyt,1,yes,547,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,2,a,1607021545338,T1,train,train,q,1,yes,601,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,1,is,1607021545338,T1,train,train,og,1,yes,602,
1607021943,176a19eda12ab8848370ad796cddd0da,PennController,3,0,training,NULL,Controller-Maze,Maze,0,Today,1607021545338,T1,train,train,x-x-x,0,yes,1103,

I also found it in DashedSentence experiments. Sure enough, the event time is the same, and the time to key press is probably also correct, but the order in the result file is reversed. which will obviously be a problem to calculate cumulative reading times past the critical region. I’m working on a quick fix in R and will post the code here upon success 🙂

Best,
Susanne

[suz]

Hi Jeremy,

Thanks a million, you are a life-saver, works a charm! Thanks for the many explanations also, makes it easy to understand and learn.

The new farm looks great! I might have a go over there. The old server doesn’t appear to be unstable, it behaves as expected; it is just slow in loading the experiment/code (updates from Github are quite fast, actually).

Best,
Susanne

[suz]

Hi Jeremy,

Nah, that’s all for now, and exactly what I needed for the intended primary purpose. Thanks!

—Susanne

[suz]

Hi Jeremy,

This is brilliant, thanks! So I gather that at failure it cannot re-use or re-loop through trainings.csv (judging from this topic I just found here)? That’s fine, I’ll just have 10 or so training items then, that should do the trick. (The progress bar is relative to the full number of possible items, so for early-finishers this will ‘jump’ a little, but that’s not a problem.)

Again, thanks a lot for your swift response, I’m getting the hang of things!

Best,
Susanne

[suz]

Hi Jeremy,

Awesome! Thanks a lot, much appreciated! I guess future novice mazers will appreciate this, too. I’m getting the hang of it, I have even managed to include a break after every n trials from forum posts.

–Susanne

[suz]

Hi Jeremy,

All working fine now. One minor thing I’ve noticed is that the feedback message for (wrong) choices in the maze task doesn’t show. Does it require a particular setting in the Template? I think it’s what is called “errorMessage” / “error_message” and “normalMessage” / “normal_message” in MazeSeparator.js. In the ibex task, the participants press a key to continue from the feedback to the next trial. In my experiment, there is currently a 750ms/500ms ISI (which I actually like because they don’t have to click anything). Although a brief flash of “oops!” for incorrect responses might also be an option, possibly as a reminder of participants to be attentive. Would an if-statement in the Template do that trick? I tried to add .failure(newText("oops!")) to no avail:

Template("training.csv", row =>
    newTrial("training",

        newController("Maze", {s: row.Sentence, a: row.Distractor})
            .print()
            .log()
            .wait()
            .failure(newText("oops!"))
            .remove()
        ,
        newTimer(500).start().wait()
    )
)

Thanks, it’s only minor. I’m quite happy!
–Susanne

[suz]

Hi Jeremy,

Ha, it just occurred me this very second that the sample.js file was the issue, thanks a lot! Yeah, I had already changed the maze.js code as suggested, it was working over at ibex already with the arrows.

Thanks again, major relief.

–Susanne

[suz]

Hi Jeremy,

Thanks, will do!

Best,
Susanne

[Author]

Posts