Problem with script in Inquisit Web


Author
Message
satchmo496
satchmo496
Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)
Group: Forum Members
Posts: 35, Visits: 77
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 104K
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

satchmo496
satchmo496
Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)
Group: Forum Members
Posts: 35, Visits: 77
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Wonderful, thank you so much!
satchmo496
satchmo496
Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)
Group: Forum Members
Posts: 35, Visits: 77
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Sorry Dave, but one followup. Is it enough to simply add this element to the script or do I have to specify that this element be run before any other blocks/trial in the script? Thanks again!
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 104K
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Sorry Dave, but one followup. Is it enough to simply add this element to the script or do I have to specify that this element be run before any other blocks/trial in the script? Thanks again!

It's enough to simply add it to the script. The <picture> element need not be actually used anywhere during the procedure.

satchmo496
satchmo496
Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)
Group: Forum Members
Posts: 35, Visits: 77
Dave - 11/15/2019
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Sorry Dave, but one followup. Is it enough to simply add this element to the script or do I have to specify that this element be run before any other blocks/trial in the script? Thanks again!

It's enough to simply add it to the script. The <picture> element need not be actually used anywhere during the procedure.

Thanks!
satchmo496
satchmo496
Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)
Group: Forum Members
Posts: 35, Visits: 77
Dave - 11/15/2019
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Sorry Dave, but one followup. Is it enough to simply add this element to the script or do I have to specify that this element be run before any other blocks/trial in the script? Thanks again!

It's enough to simply add it to the script. The <picture> element need not be actually used anywhere during the procedure.

Unfortunately I'm still running into a problem. The script now seems to be loading all of the pictures correctly, but the presentation of the picture/profile combinations in the initial block of trials is now functioning incorrectly. In this initial block, each of 64 picture/profile combinations is supposed to be presented for 1000 ms. This is what happens when i run the script using Inquisit lab. But, when i run it on Inquisit Web, the script does eventually present all 64 combinations, but it also starts by presenting a bunch of blank screens, then moves to presenting one or two picture/profile screens interspersed with blank screens, then moves to a solid run of picture/profile combinations (I realize that the particular order here may be random, but the general problem of not presenting all 64 combinations one after another for 1000 ms each remains!). Here's a link to the script (which now has the picture preload element from above).

Thanks again for your help with this!
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 104K
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Sorry Dave, but one followup. Is it enough to simply add this element to the script or do I have to specify that this element be run before any other blocks/trial in the script? Thanks again!

It's enough to simply add it to the script. The <picture> element need not be actually used anywhere during the procedure.

Unfortunately I'm still running into a problem. The script now seems to be loading all of the pictures correctly, but the presentation of the picture/profile combinations in the initial block of trials is now functioning incorrectly. In this initial block, each of 64 picture/profile combinations is supposed to be presented for 1000 ms. This is what happens when i run the script using Inquisit lab. But, when i run it on Inquisit Web, the script does eventually present all 64 combinations, but it also starts by presenting a bunch of blank screens, then moves to presenting one or two picture/profile screens interspersed with blank screens, then moves to a solid run of picture/profile combinations (I realize that the particular order here may be random, but the general problem of not presenting all 64 combinations one after another for 1000 ms each remains!). Here's a link to the script (which now has the picture preload element from above).

Thanks again for your help with this!

I've uploaded and tested the script you linked here: https://mili2nd.co/fopb

"the presentation of the picture/profile combinations in the initial block of trials is now functioning incorrectly. In this initial block, each of 64 picture/profile combinations is supposed to be presented for 1000 ms. This is what happens when i run the script using Inquisit lab. But, when i run it on Inquisit Web, the script does eventually present all 64 combinations, but it also starts by presenting a bunch of blank screens, then moves to presenting one or two picture/profile screens interspersed with blank screens, then moves to a solid run of picture/profile combinations"

I'm not seeing any of those issues.

satchmo496
satchmo496
Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)Expert (1.2K reputation)
Group: Forum Members
Posts: 35, Visits: 77
Dave - 11/15/2019
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Dave - 11/15/2019
satchmo496 - 11/15/2019
Hi!
I have a script that runs fine on my desktop version of Inquisit, but doesn't correctly display certain stimuli on Inquisit web. Specifically, in the task, participant should see each of 64 screens for a few seconds in an initial block of trials. All of the screens are correctly displayed on the desktop version of Inquisit, but some are not displayed on the web version. I've linked to a zipped folder with the inquisit file and stimuli. I appreciate any ideas you have. As is usually the case, I imagine I've just missed something simple that more expert eyes will see right away!

The way you've coded the script, you assign images to empty <item> elements at runtime per a bunch of <counter> elements. That's not a problem on your computer, where all the files are already present on your disk. It is a problem on the web, because Inquisit can't know what image files it has to download.

Add a <picture> element to the script that has *all* the image files as its items. I.e.

<picture preload>
/ items = (
"Profile_Accept1.png",
"Profile_Accept2.png",
"Profile_Accept3.png",
"Profile_Accept4.png",
"Profile_Accept5.png",
"Profile_Accept6.png",
"Profile_Accept7.png",
"Profile_Accept8.png",
"Profile_Accept9.png",
"Profile_Accept10.png",
"Profile_Accept11.png",
"Profile_Accept12.png",
"Profile_Accept13.png",
"Profile_Accept14.png",
"Profile_Accept15.png",
"Profile_Accept16.png",
"Profile_Accept17.png",
"Profile_Accept18.png",
"Profile_Accept19.png",
"Profile_Accept20.png",
"Profile_Accept21.png",
"Profile_Accept22.png",
"Profile_Accept23.png",
"Profile_Accept24.png",
"Profile_Accept25.png",
"Profile_Accept26.png",
"Profile_Accept27.png",
"Profile_Accept28.png",
"Profile_Accept29.png",
"Profile_Accept30.png",
"Profile_Accept31.png",
"Profile_Accept32.png",
"Profile_Reject1.png",
"Profile_Reject2.png",
"Profile_Reject3.png",
"Profile_Reject4.png",
"Profile_Reject5.png",
"Profile_Reject6.png",
"Profile_Reject7.png",
"Profile_Reject8.png",
"Profile_Reject9.png",
"Profile_Reject10.png",
"Profile_Reject11.png",
"Profile_Reject12.png",
"Profile_Reject13.png",
"Profile_Reject14.png",
"Profile_Reject15.png",
"Profile_Reject16.png",
"Profile_Reject17.png",
"Profile_Reject18.png",
"Profile_Reject19.png",
"Profile_Reject20.png",
"Profile_Reject21.png",
"Profile_Reject22.png",
"Profile_Reject23.png",
"Profile_Reject24.png",
"Profile_Reject25.png",
"Profile_Reject26.png",
"Profile_Reject27.png",
"Profile_Reject28.png",
"Profile_Reject29.png",
"Profile_Reject30.png",
"Profile_Reject31.png",
"Profile_Reject32.png",
"B1S.BMP",
"B2S.BMP",
"B3S.BMP",
"B4S.BMP",
"B5S.BMP",
"B6S.BMP",
"B7S.BMP",
"B8S.BMP",
"B9S.BMP",
"B10S.BMP",
"B11S.BMP",
"B12S.BMP",
"B13S.BMP",
"B14S.BMP",
"B15S.BMP",
"B16S.BMP",
"B17S.BMP",
"B18S.BMP",
"B19S.BMP",
"B20S.BMP",
"B21S.BMP",
"B22S.BMP",
"B23S.BMP",
"B24S.BMP",
"B25S.BMP",
"B26S.BMP",
"B27S.BMP",
"B28S.BMP",
"B29S.BMP",
"B30S.BMP",
"B31S.BMP",
"B32S.BMP",
"W1S.BMP",
"W2S.BMP",
"W3S.BMP",
"W4S.BMP",
"W5S.BMP",
"W6S.BMP",
"W7S.BMP",
"W8S.BMP",
"W9S.BMP",
"W10S.BMP",
"W11S.BMP",
"W12S.BMP",
"W13S.BMP",
"W14S.BMP",
"W15S.BMP",
"W16S.BMP",
"W17S.BMP",
"W18S.BMP",
"W19S.BMP",
"W20S.BMP",
"W21S.BMP",
"W22S.BMP",
"W23S.BMP",
"W24S.BMP",
"W25S.BMP",
"W26S.BMP",
"W27S.BMP",
"W28S.BMP",
"W29S.BMP",
"W30S.BMP",
"W31S.BMP",
"W32S.BMP")
</picture>

The presence of that <picture> element will cause Inquisit to download all the image files to the client system prior to starting the experiment.

Sorry Dave, but one followup. Is it enough to simply add this element to the script or do I have to specify that this element be run before any other blocks/trial in the script? Thanks again!

It's enough to simply add it to the script. The <picture> element need not be actually used anywhere during the procedure.

Unfortunately I'm still running into a problem. The script now seems to be loading all of the pictures correctly, but the presentation of the picture/profile combinations in the initial block of trials is now functioning incorrectly. In this initial block, each of 64 picture/profile combinations is supposed to be presented for 1000 ms. This is what happens when i run the script using Inquisit lab. But, when i run it on Inquisit Web, the script does eventually present all 64 combinations, but it also starts by presenting a bunch of blank screens, then moves to presenting one or two picture/profile screens interspersed with blank screens, then moves to a solid run of picture/profile combinations (I realize that the particular order here may be random, but the general problem of not presenting all 64 combinations one after another for 1000 ms each remains!). Here's a link to the script (which now has the picture preload element from above).

Thanks again for your help with this!

I've uploaded and tested the script you linked here: https://mili2nd.co/fopb

"the presentation of the picture/profile combinations in the initial block of trials is now functioning incorrectly. In this initial block, each of 64 picture/profile combinations is supposed to be presented for 1000 ms. This is what happens when i run the script using Inquisit lab. But, when i run it on Inquisit Web, the script does eventually present all 64 combinations, but it also starts by presenting a bunch of blank screens, then moves to presenting one or two picture/profile screens interspersed with blank screens, then moves to a solid run of picture/profile combinations"

I'm not seeing any of those issues.

Sorry to bother with this. It seems to have been a problem with the batch script rather than this script. I made some changes to the batch and now everything is working properly. Thank you again for your help!
Dave
Dave
Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)Supreme Being (1M reputation)
Group: Administrators
Posts: 13K, Visits: 104K
satchmo496 - 11/15/2019

Sorry to bother with this. It seems to have been a problem with the batch script rather than this script. I made some changes to the batch and now everything is working properly. Thank you again for your help!

Great -- thanks for letting me know!

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Explore
Messages
Mentions
Search