By grit.herzmann - 11/4/2024
Hello,
I have a problem with the Millisecond Gambling Task provided at https://www.millisecond.com/download/library/millisecondgamblingtask The task does not operate as described. Looking at the experiment, the problem occurs when participants place the bets they want to gamble. The description states that bets automatically increase every 5 seconds until participants click with the mouse on a bet (e.g., 3rd bet) or the bets max out (i.e., the 5th bet). The experiment runs such that a mouse click on the bet does not lock in the bet but instead increases it to the next option. The bet only locks in at the maximal bet.
I looked into the program code (but I am new to inquisit) and tried to identify the problem. It seems that multiple trials that are programmed don’t work appropriately. The following trials all don’t do what they should: trial.bed_red, trial.bed_blue, trial.bet. All of these trials have the branch programming that if the bedbox is clicked with the mouse, they should move on to trial.wait, if the bedbox is not clicked the first to move on to trial.bet, and if the bedbox is not clicked trial.bet automatically increased the bets up to 5 times until it automatically moves to trial.wait. According to this programming, the clicking of the bedbox does not accurately move on to the trail.wait. Instead, clicking the bedbox restarts the trial.bet because the next bet appears without waiting the 5 seconds.
I have tried with trial and error to correct the error, but I have been unsuccessful. Help is very much appreciated.
Thank you!
Grit
|
By Dave - 11/4/2024
+xHello, I have a problem with the Millisecond Gambling Task provided at https://www.millisecond.com/download/library/millisecondgamblingtask The task does not operate as described. Looking at the experiment, the problem occurs when participants place the bets they want to gamble. The description states that bets automatically increase every 5 seconds until participants click with the mouse on a bet (e.g., 3rd bet) or the bets max out (i.e., the 5th bet). The experiment runs such that a mouse click on the bet does not lock in the bet but instead increases it to the next option. The bet only locks in at the maximal bet. I looked into the program code (but I am new to inquisit) and tried to identify the problem. It seems that multiple trials that are programmed don’t work appropriately. The following trials all don’t do what they should: trial.bed_red, trial.bed_blue, trial.bet. All of these trials have the branch programming that if the bedbox is clicked with the mouse, they should move on to trial.wait, if the bedbox is not clicked the first to move on to trial.bet, and if the bedbox is not clicked trial.bet automatically increased the bets up to 5 times until it automatically moves to trial.wait. According to this programming, the clicking of the bedbox does not accurately move on to the trail.wait. Instead, clicking the bedbox restarts the trial.bet because the next bet appears without waiting the 5 seconds. I have tried with trial and error to correct the error, but I have been unsuccessful. Help is very much appreciated. Thank you! Grit
It's a mistake in the Inquisit 7 version of the script. Inquisit 7 iqjs scripts are case-sensitive in all respects. The clickable object at issue is called "betBox", and that is what the response property returns as well. Some of the logic relying on the response property, however, wrongly expects "betbox" as the response.
We'll have fixed versions up in the library in due course, but in the meantime you can easily fix this yourself with a simple search and replace.
Search for: "betbox"
Replace with: "betBox"
|
|