Problem withMediaLab V2014.1.105 and Inquisit 4.0.4 (case 13195)

[densonlab]

Hi there,

I am using Medialab 2014.1.105 and when trying to pull up and Inquisit 4.0.4 script the program is requesting participant ID and condition details, which it used to get automatically from the medialab file (older version of medialab). Does anyone know how I might get around this so participants are not shown this screen and the information is generated automatically again?

Any help would be greatly appreciated.

Thanks!




Tags

[jason_reed]

Would you mind uploading any MediaLab and Inquisit files that you are using so that I may take a look at them?

[densonlab]

Hi jason_reed,

I have attached a simplified medialab file and the inquisit file that I am attempting to run in it. Any help you could provide would be much appreciated!

Thanks,

densonlab

[jason_reed]

You can do this by using an executable item in place of the Inquisit item in the .que file. Specifically, we have to take advantage of both Medialab's and Inquisit's use of command lines and MediaLab's feature of allowing for the substitution of previous variables into subsequent items.

If you open the attached .que file, you will see that the second item is an executable item. If you open that item to take a look at its details, you will also see the following in its File Name field:


"C:\Program Files\Millisecond Software\Inquisit 4\Inquisit.exe" "C:\MediaLab\FogBugz\case13195\Emotion Regulation IAT.exp" -s <subject> -g <condition>


These arguments come from a webpage from the Inquisit website (http://www.millisecond.com/support/d...ommandline.htm) that details how to run Inquisit from a command prompt. The pathway between the first set of quotation marks is the location of Inquisit.exe file, and the pathway between the second set of quotation marks is the location of the script file to run. To pass the subject ID and condition number entered at the start of running a MediaLab file we add some substitute variable values by typing <subject> after the -s and <condition> after the -g (see http://www.empirisoft.com/medialab/h...textlabels.htm for more information about the substitute feature).


If the Inquisit file has more than one groupid that you want to trigger with a similar number in the MediaLab condition field, all that needs to be done is to open an .exp file in MediaLab and create a new line for each condition number. All lines will refer to the same .que file with the exectuable item for the Inquisit file, just like the attached .exp file.

[psychDarwin]

Hello - I am having the same problem trying to run an Inquisit 4 file in Medlialab 2014. I get the "Please Wait" message and then MediaLab asks me to click 'Continue'. After I do, MediaLab proceeds to the next step of the questionnaire file without ever running the Inquisit experiment. I tried making the update to the path environment variable and pasting in the path extensions as was mentioned in the thread about passing the subject and condition to Inquisit. Neither worked (I'm not even to the point where I can pass subject ID or condition yet, I'm just trying to get the Inquisit file to run).

Questionnaire file and Inquisit file are attached. Any help would be much appreciated.

FYI - The thread would not allow me to upload the newest formal of the Inquisit file (*.iqx). I had to save the file in the legacy (*.exp) format in order to attach it.

BeanFest.queBeanFest - Full Feedback.exp

[jason_reed]

In your .que file, use an Executable item type instead of the Inquisit session item type and see what happens.

[bibi]

I just wanted to let everyone know that I got inquisit 4 to work but unfortunately it won't work when you specify the entire inquisit file path location as you did in your example (e.g. my documents etc...). In addition the two quotations marks need to have a space between them.

I found that the easiest way to copy and paste it would be to actually open the questionnaire and paste it in the file name section instead of using the shortcut.

This is the command which worked for me for an inquisit file labeled cyberball inclusion. Also, remember to make the item type executable rather than an inquisit type.

"C:\Program Files\Millisecond Software\Inquisit 4\Inquisit.exe" "Cyberball inclusion.iqx" -s <subject> -g <condition>

I really hope you can eventually fix this issue so that we can just run it as an inquisit session rather than an executable file with paths as it will make it so much easier.

[jason_reed]

Thanks for the information, bibi! We appreciate it any time that someone can share with us the details about their use of MediaLab and what worked with their situation.

We will make sure to add your suggestions to a list of features to consider for future versions of MediaLab.