DirectRT stops running stimuli during test

[jarvis24]

Nothing obviously wrong as far as I can see. If you run through a trial session with ROantb+ and give the same response on each trial (e.g., always 203, always 205, or always 208), will it always quit at the same spot?

[jarvis24]

[edited from support email]

I actually think I found the problem and would just like confirmation. Our variable in position 158 is generally where the survey abruptly cuts off. However I just noticed that the skip is incorrectly programmed to skip to a preceding variable for all but two of the possible response categories. Would this cause the experiment to end? It is currently programmed to skip to 'everdrunk' which occurred at position 118 instead of rmeligion at position 161.

Yes, a backwards jump or skip would cause it to end because DirectRT simply skips trials until it finds the one it's looking for. If it is never found (in the forward direction), the session would end.

[bls62]

We haven't gone through a file using only one response, yet. We do, however, believe that the crash has to do with too fast of a response time. It seems to be crashing on swifter responses, which seem to be within 200 miliseconds or less from the word stimuli. Has this been a problem in the past for anyone?

[bls62]

The software doesn't seem to consistently crash dependent on which button (203, 205, 208) is pressed, but it does seem more consistent that it crashes when response time is quicker (about 200 miliseconds or less).