Millisecond Forums

About the only thing I can think of would be something like this:

<trial rest>
/ ontrialbegin = [if(expressions.offdurations_trial_mean >= 0){
    item.ontargettimes.appenditem(expressions.timeOnTarget_trial)
    } else {
        item.ontargettimes.appenditem("-1000")
    }
]
/ stimulusframes = [1 = clearscreen, BetweenTest]
/ timeout = parameters.restTime
/ branch = [
    trial.startRotate;
]
/ recorddata = false
</trial>

<trial rest1>
/ ontrialbegin = [if(expressions.offdurations_trial_mean >= 0){
    item.ontargettimes.appenditem(expressions.timeOnTarget_trial)
    } else {
        item.ontargettimes.appenditem("-1000")
    }
]
/ stimulusframes = [1 = clearscreen, BetweenTest1]
/ timeout = 5000
/ branch = [
    trial.startRotate;
]
/ recorddata = false
</trial>

<trial prequestion>
/ ontrialbegin = [if(expressions.offdurations_trial_mean >= 0){
    item.ontargettimes.appenditem(expressions.timeOnTarget_trial)
    } else {
        item.ontargettimes.appenditem("-1000")
    }
]
/ stimulusframes = [1 = clearscreen, BetweenTest2]
/ validresponse = (lbuttondown)
/ recorddata = false
/ branch = [
    trial.end
]
</trial>

That should result in the value -1 being displayed for "no movement" trials instead of the value "nan" (not a number). That, in turn, should lead to the high-score -- longest time on target for trials when there was movement -- being reported accurately as well.

Oh perfect, thank you so much! One last question (not a huge deal but I figured I'd check): on the feedback page if someone has 'nan' for any of the trials, in the section where it says their high score, nan is reported as the high score. Is there any way around this? To only list actual numbers for the high score?

Copy and paste error on my part is responsible for that, sorry. The expression in my previous reply was missing a crucial "{":

/ offdurations_trial_mean = if (list.offDurations_trial.itemcount>0 && list.targetDistances_trial.itemcount>0) {
                            list.offDurations_trial.mean
                        } else if (list.targetDistances_trial.itemcount == 0) {
                            "nan"
                        } else {
                            0
                        }

Hm, this returned a bunch of errors (see photo), and kept calculating perfect scores as zero (see data file).

Thanks for the data file. Since the non-movement in trials 1-3 as well as trials 7-8 appears to be correctly detected / reflected by list.targetDistances_trial.itemcount, it shoud be possible to factor that in to the expression calculating the per-trial off-target duration:

<expressions>
...
/ offdurations_trial_mean = if (list.offDurations_trial.itemcount>0 && list.targetDistances_trial.itemcount>0) {
                            list.offDurations_trial.mean
                        } else if (list.targetDistances_trial.itemcount == 0) {
                            "nan"
                        } else
                            0   
                        }
/ sum_offDurations_trial = expressions.offdurations_trial_mean * list.offDurations_trial.itemcount
...
</expressions>

Here's the data file. In trials 1-3 I didn't move my mouse at all. In trials 4-6 I did move it, and got a perfect score on trial 5. In trials 7 and 8, I didn't move my mouse again.

Thanks for the computer key. Please paste the following key

A44ABAABA2356644

into the "REGISTRATION KEY:" field and then click the "Get Registration Key" button. This should reset the trial period.

Great, thanks so much. The computer key is BE4B400A3A0B4A0E.

Hmm, that's not what I'm seeing. I'm getting very low values (both on-screen as well as in the data file) depending on where exactly I positioned the mouse within the circle during the start trial. But maybe something is throwing things off on my system because it's virtually impossible for me to not move the mouse at all.

If you direct message me your trial installation's computer key, I can give you a special registration key that will reset the trial period -- you can then record data again (for another 30 days), and maybe some of your data file(s) will tell me what's going on.

I'm working with the trial version so it doesn't record the data when I test this out, but if you run the attached script you can see for yourself in the feedback pages between each trial it'll say 2 if you don't move your mouse at all (each trial is 2 seconds long). FYI--the instructions may not match the correct times, I shortened the trial and rest times for testing purposes.