Millisecond Forums

inquisit crashing

https://forums.millisecond.com/Topic19434.aspx

By nc - 7/27/2016

Hello,

I'm attempting to use inquisit with my ACER ONE laptop. It has Windows 10 installed and can be configured to be a touchscreen.

The program crashes when I attempt to run it and use my computer as a touchscreen. I've tried setting the input device both to mouse and touchscreen, and the same issue occurs. The experiment works fine if I set the input device to mouse and only use the mouse on it. Do you have any advice?
By Dave - 7/27/2016

I have no spontaneous idea, but here are a couple of things to try / check:

(1) Is the Inquisit version you've installed up to date? When in doubt, download the latest one from https://www.millisecond.com/download and install it.

(2) Is the touchscreen driver on the system up to date? Here, too, when in doubt, obtain the latest driver from the manufacturer and install it.

(3) What happens when you set /inputdevice to keyboard and try to use the touchscreen?

(4) What does the technical log say (Select "Tools -> View Log File..." in Inquisit Lab to access the log)?
By nc - 7/27/2016

Hi Dave,

I can't really set it to keyboard without altering the validresponse on almost every trial (it was set to a click on specific areas of the screen).

Here's what it says in the log though:

2016-07-28T10:51:16.611   InquisitLab   5.0.4.0   3732   32bit   Release   CompileDate='Jul 5 2016'   CompileTime='16:50:48'   Initializing...

2016-07-28T10:51:16.627   InquisitLab   5.0.4.0   3732   System Platform='Windows NT 10.0; Win32; Touch'   MemAvail=581844   MemTotal=2034620   CPUSpeed=1333   TimerResolution=0.0007680001966080503   IPAddress=XXXXXXXXXXXXXXX    MacAddress=XXXXXXX
By Dave - 7/28/2016

Okay, thanks. Is that all that's contained in the log?

And: Do you get the same result when trying to run some other script (i.e., not yours) on your Acer and try to use the touchscreen? Any of the scripts available in the library should work as test cases, as for testing /inputdevice=keyboard, you could use one of the IAT scripts.

I'm trying to get a sense of whether the issue is confined to a particular script / combination of settings, or if it's more general (e.g. an issue with this specific Acer model).

Thanks!
By nc - 7/28/2016

Hi Dave,

I just tried the IAT Touchscreen and the same issue happened. It ran through more of the script before it crashed, but it had the same crash.
By nc - 7/28/2016

Hi Dave,

Another question - am I correct in assuming I'd need to purchase inquisit web (not inquisit lab) to do this on an iPad (given my issues with displaying this on the ACER)? I am not interested in doing data collection online, but I don't currently see how else I would get the script to run on an ipad.
By Dave - 7/28/2016

Thanks for taking the time to test. Regarding "It ran through more of the script before it crashed, but it had the same crash.", could you tell me _when_ approximately the script crashed on your device? E.g. after the instructions, after X trials, after the 1st block?

As for running scripts on iOS devices (iPad, iPhone), yes, that's only possible using Inquisit Web for the time being. An Inquisit Lab version for iPads is not available currently.

Thanks.
By nc - 7/28/2016

It got through the instructions being able to take the touchscreen input and crashed during the first trial
By Dave - 7/28/2016

Thanks, that's an interesting piece of information to have. Instructions in the IAT are presented using regular <trial> elements, i.e. in the same way the actual trials (where you categorize the words, etc.) work. So, touch input seems to work in principle. The only obvious difference between <trial instructions> (which works for you / takes touch input), and the other <trial> elements would be that the latter have several response options ("E" and "I"), whereas the instructions trial only has / needs one (the "Spacebar").

Here's a quick test script to check whether the crash is related to the number of available response options. Trials in the 1st block will only allow one response option. Trials in the 2nd block will allow two. If the theory holds, the 1st block should work for you, while you would experience crashing in the 2nd block. It would be great if you could try to run this on your Acer and let me know how it behaves. Thanks!

<expt>
/ blocks = [1=first; 2=second]
</expt>
e
<block first>
/ trials = [1-10 = noreplace(press_e,press_i)]
</block>

<block second>
/ trials = [1-10 = noreplace(press_e_or_i)]
</block>

<trial press_e>
/ stimulusframes = [1=e_text]
/ validresponse = ("E")
</trial>

<trial press_i>
/ stimulusframes = [1=i_text]
/ validresponse = ("I")
</trial>

<trial press_e_or_i>
/ stimulusframes = [1=e_or_i_text]
/ validresponse = ("E", "I")
</trial>

<text e_text>
/ items = ("Press E")
</text>

<text i_text>
/ items = ("Press I")
</text>

<text e_or_i_text>
/ items = ("Press E or I")
</text>
By nc - 7/28/2016

Hi Dave,

So I tried the short script you sent, and it worked just fine. I even added trials with 4 response options and that also worked fine.

But I re-tried the IAT TouchScreen and confirmed that it crashed as soon as I tried to give a response on the first trial.
By nc - 7/28/2016

Another piece of information that might be useful: I just tried my own experiment and tried to touch the screen during trials that don't require any input (i.e., have a timeout instead), and the same crash occurred. Basically, whenever I touch the screen, it crashes.
By nc - 7/28/2016

Here's more from the crash log:

2016-07-28T18:00:53.798   InquisitLab   5.0.4.0   3732   Script='C:/Users/XXXX/Desktop/Experiment/InGroupOutGroupExperiment.iqx'   GroupID=1   SubjectID=1   Graphics=Direct2D   ColorDepth=32   ScreenWidth=1280   ScreenHeight=800   RefreshRate=60   VidoeSync=DXGIWaitForVBlankMode

2016-07-28T18:00:53.798   InquisitLab   5.0.4.0   3732   Script='C:/Users/XXXXX/Desktop/Experiment/InGroupOutGroupExperiment.iqx'   GroupID=1   SubjectID=1   Graphics   isTablet=1   isScrollable=0   hasResponseView=0

2016-07-28T18:00:54.516   InquisitLab   5.0.4.0   3732   Script='C:/Users/Nadia/Desktop/Experiment/InGroupOutGroupExperiment.iqx'   GroupID=1   SubjectID=1   Script starting...

2016-07-28T18:00:54.700   InquisitLab   5.0.4.0   3732   Script='C:/Users/Nadia/Desktop/Experiment/InGroupOutGroupExperiment.iqx'   GroupID=1   SubjectID=1   Opened DataFile='C:/Users/XXXX/Desktop/Experiment/InGroupOutGroupExperiment_raw.iqdat'. Found FileSize=2057 bytes.

2016-07-28T18:00:54.700   InquisitLab   5.0.4.0   3732   Script='C:/Users/XXXX/Desktop/Experiment/InGroupOutGroupExperiment.iqx'   GroupID=1   SubjectID=1   Closed DataFile='C:/Users/XXXX/Desktop/Experiment/InGroupOutGroupExperiment_raw.iqdat'. Final FileSize=2057 bytes.

2016-07-28T18:03:20.656   InquisitLab   5.0.4.0   3732   32bit   Release   CompileDate='Jul 5 2016'   CompileTime='16:50:48'   Initializing...

2016-07-28T18:03:20.673   InquisitLab   5.0.4.0   3732   System Platform='Windows NT 10.0; Win32; Touch'   MemAvail=269536   MemTotal=2034620   CPUSpeed=1333   TimerResolution=0.0007680001966080503   IPAddress=XXXXX2   MacAddress=XXXX
By Dave - 7/28/2016

That's extremely weird. Just to clarify for me:

The test script in my previous response works for you, i.e., accepts touch input & doesn't crash, but for some reasons the other scripts do not. Correct?
By nc - 7/28/2016

Correct
By nc - 7/28/2016

Also, for what it's worth - I did just run it on my iPad by mirroring my computer screen onto the iPad and it worked using either mouse or touchscreen input. So, I'm inclined to believe that this may be specific to the ACER or Windows touchscreens
By Dave - 7/28/2016

Thanks for the confirmation and the additional (very useful!) observations. Given that I'm not aware of similar reports involving other WIndows touch devices / touch screens (so far, that is), I'm inclined to think this *may* be specific to the Acer / its specific configuration. I'm not sure how to narrow this down further at the moment, but I'll log a bug report and update this thread if I can think of anything else. One thing I mentioned earlier was trying to check if there's an updated driver for the Acer's touchscreen available. Have you checked if Acer has provided any driver updates for your device on their site?
By nc - 7/28/2016

Hi Dave,
Sure - I'm doing a complete factory reset on the ACER and downloading all the latest drivers and software now. I'll give you an update to let you know how it behaves after that.
By nc - 7/28/2016

Sorry- it still hast he same issue after a full factory reset and downloading all of the latest drivers.
By Dave - 7/28/2016

Thanks for trying the driver update angle and reporting back. I'm out of ideas right now, but we'll investigate, see if we can reproduce this somehow and ultimately figure out where exactly the problem stems from.

Thanks again for sharing your helpful observations and test results.
By dalarub - 5/28/2017

Dave - Friday, July 29, 2016
Thanks for trying the driver update angle and reporting back. I'm out of ideas right now, but we'll investigate, see if we can reproduce this somehow and ultimately figure out where exactly the problem stems from.

Thanks again for sharing your helpful observations and test results.

  Hi Dave,
I have the same problem in an Acer Iconia W4 tablet   with a Windows 8.1. As soon as I run the script on Inquisit 5 and I touched the screen it crashed. I have tried with Inquisit 4 and it works Ok, but I only have licenses available for Inquisit 5. I would appreciate any help.

Best
By Dave - 5/29/2017

dalarub - Monday, May 29, 2017
Dave - Friday, July 29, 2016
Thanks for trying the driver update angle and reporting back. I'm out of ideas right now, but we'll investigate, see if we can reproduce this somehow and ultimately figure out where exactly the problem stems from.

Thanks again for sharing your helpful observations and test results.

  Hi Dave,
I have the same problem in an Acer Iconia W4 tablet   with a Windows 8.1. As soon as I run the script on Inquisit 5 and I touched the screen it crashed. I have tried with Inquisit 4 and it works Ok, but I only have licenses available for Inquisit 5. I would appreciate any help.

Best

A couple of questions:
1) "As soon as I run the script on Inquisit 5 ..."
Which script?
2) Since this thread deals with a now very much outdated Inquisit 5 version, which version are you seeing this under? If it's not up to date, please update and report if the issue persists.
By dalarub - 5/29/2017

Hi Dave,
On every script that I have try from the Inquisit Library and with the last version of Inquisit 5.
Thanks for your quickly attention.
David
By Dave - 5/29/2017

dalarub - Monday, May 29, 2017
Hi Dave, On every script that I have try from the Inquisit Library and with the last version of Inquisit 5.Thanks for your quickly attention.David

Can you post or attach the crash information from the system's software log? Thanks.

Here's one way to find those entries: https://www.digitalmastersmag.com/magazine/tip-of-the-day-how-to-find-crash-logs-on-windows-8/