Sequence not working in browser but working with quick run

Comments

• lvanderlinden

  March 2021

  Hi @janhoruk ,

  
  

  One thing that comes to mind is that you defined 'allowed responses' in the keyboard_response item, and that the value of a certain response is named differently locally than it is in the browser. For example, if you set the allowed response to "SPACE" whereas the browser names the same keypress "space", the experiment freezes (at least when the timeout is set to "infinite") because the allowed response will never be pressed.

  
  

  Could this be what is causing the issue?

  
  

  If not, feel free to upload your experiment here so that we can have a closer look.

  
  

  Cheers,

  
  

  Lotje

  Did you like my answer? Feel free to
• janhoruk

  March 2021 edited March 2021

  Hi, @lvanderlinden

  This is exactly it, I believe! I just deleted the keyboard_response item and kept the "allowed responses" in the sketchpad items.

  Do you by any chance know, is it a better practice to have the keyboard_item or is it ok to just change the script in each sketchpad as the logger still logs every key response?

  Thank you!! <3
• lvanderlinden

  March 2021

  Hi @janhoruk ,

  
  

  Great to hear! :)

  Actually, it's better to set the duration of the sketchpad to 0 and append a keyboard_response item for response collection, because then all response variables are logged:

  
  

  • https://osdoc.cogsci.nl/3.3/manual/variables/#response-variables

  
  

  Otherwise, OpenSesame only waits for a key but doesn't log everything.

  
  

  So perhaps it's better to change your experiment accordingly.

  
  

  Best wishes,

  
  

  Lotje

  Did you like my answer? Feel free to
• janhoruk

  April 2021 edited April 2021

  Hi, @lvanderlinden (sorry to bother you again, will buy you a coffee when I get a job :))

  I was wondering: if I have 5 sketchpad in my sequence that serve as instructions, is it necessary to have a keyboard_response for every single sketchpad? I wanted to have only 1 keyboard_response at the end (that means after the last sketchpad inside the sequence), but noticed that only the sketchpad directly above the keyboard_response (the fifth one) actually has the limitations set in "Allowed responses" (I have it set to "SPACE", so the participant can read the next instruction on the next sketchpad, when they press the spacebar), whilst the other sketchpads run if I press any key, not only those in "Allowed responses".

  Now I have 5 sketchpads items and 5 keyboard_response items. But I have to press SPACE twice to move to the next sketchpad ... If I set the timeout to 0 instead of infinite, the limitation set in "Allowed responses" don't work anymore.

  Next, I tried to change the first keyboard_response 's "Event type" to "keyboard release" ... and now all the sketchpads move with only 1 spacebar press. It works, but I don't think this is the correct way.

  Next, I used your suggestion, I still have 5 sketchpads items and 5 keyboard_response items, but I set the sketchpads' duration to 0 and all 5 keyboard_response items have "infinite" and "keypress" options selected. I'm attaching this version of the file here:

  AfektivnenormeNEW_1.osexp

  
  
• janhoruk

  April 2021 edited April 2021

  Hi, @lvanderlinden

  Was wondering if you would consider this positioning of the sketchpads and keyboard responses a good practice or is there a better way?

  AfektivnenormeNEW_1.osexp

  Also, I'd like to ask, if you know the solutions for the these problems:

  1. Browser sets everything (or maybe just the text) inside sketchpads at 105 %, which makes it look blurry.
  2. Browser makes a scrollbar (because of added padding? margin?), which makes the content of the sketchpad seem to jump up and down.
• eduard

  April 2021

  Hi Jan,

  The positioning is fine, but of course it depends a it on what you want to accomplish. For example, in your trial loop, only the response to the last rating scale (affectiveValence3) will be logged, as you only have a logger behind that item. If you need to log the response to each rating scale, you need to add a logger after every keyboard_response, or have an inline_script after every keyboard response, in which you save the response variables with another variable name (to prevent the next keyboard_response item to overwrite the response). In this case a single logger is fine.

  Another thing that can be improved is the instructions part. You could remove all the keyboard response items, and just set the duration of the sketchpads to keypress

  Hope this helps,

  Eduard