Millisecond Forums

Awesome -- glad to hear that!

> I don't know how you find these things [...]

I can neither confirm nor deny that my methods involve a healthy portion of black magic. No animals were harmed in the process. :)

That worked Dave!  I don't know how you find these things but you are truly an Inquisit guru.  I owe you one big time.

Okay, here's what I've got so far. Using the image files you provided:

(1) I am *not* able to reproduce the issue with the script version you initially provided (attached here: https://www.millisecond.com/forums/FindPost15727.aspx ).
(2) I am able to reproduce the issue using the script included in the ZIP archive (attached here: https://www.millisecond.com/forums/FindPost15745.aspx ).
(3) As far as I can tell, the issue is *not* caused by either <trial initialselect> or <trial reselecttrial>. It is <trial patchtrial>'s setup.
(3a) In the latest script version (under #2 above), you insert a <clock> element into <trial patchtrial>'s frames

/ontrialbegin = [if (...)
{trial.patchtrial.insertstimulusframe(clock.choose, 1); ...}
...

while you already have that <clock> in the trial's regular /stimulusframes attribute:

/stimulusframes = [1 = choose]

This is what causes the crash for me. You can provoke the same behavior by foregoing insertstimulusframe() and simply doing

/stimulusframes = [1 = choose, choose]

(3b) With that said, removing the redundant clock insertion-logic from the /ontrialbegin attributes resolves the issue for me. The script then runs as expected. A file with those modifications is attached to this response and I'd be interested to learn how that script behaves on your system.

Thanks for providing the files. I'll get back to you ASAP, but I suspect this is going to take a while to figure out...

Here is the zipped files.  Thanks a lot for looking into this Dave.  It is a very weird issue.

Interesting. Can you put those files in a ZIP archive and attach the archive to this thread. I'll see if I can reproduce the issue / narrow it down then.

The <text> script you provided works... I guess something is off with my pictures or picture elements.

Thanks a ton for all the help Dave.  I'll keep you posted.

I'm not sure either. At any rate, I am unfortunately unable to reproduce the behavior you're experiencing using the script you attached. The only change I made to that script is switching the <picture> elements to <text> elements because I don't have your image files. I'm attaching that script as a reference. I don't see any obvious mistakes in the script and -- more importantly -- there is no reason why the added insertstimulusframe() logic should cause the script to disregard input. A couple of suggestion for moving on:
(1) Try rebooting your machine and see if the issue persists. Perhaps some system library crashed silently in the background or the like.
(2) Try if the attached <text>-only version exhibits the same issue for you.
(3) Try running the script via your web license if possible. The resulting data file might offer additional clues in case the issue also occurs when the script is run via the web on your machine.

Let me know what you find.

I can't look at the output file since my trial version has run out and we have only purchased a web license version.  That is odd that you are able to progress to the next trial without issue though... Not sure what could be different between our two setups.