Logger breaks experiment

Comments

• lvanderlinden

  November 2020 edited November 2020

  Hi @Candice,

  I can reproduce the issue, but to be honest I don't understand what causes it. However, I do think the issue will disappear when you clean up the block/trial structure of your experiment and only use (linked copies of a) logger(s) at identical levels of your experiment. (Regardless of the logger issue, I think the experiment can benefit from a bit of restructuring.)

  For example, you could remove the information loop and use Run-if statements to either show more information about the person or not. In that case, you should use feedback items rather than sketchpads to display the additional info. Just let us know if you need help implementing this.

  Hopefully this will make the logger issue go away.

  
  

  Cheers,

  
  

  Lotje

  Did you like my answer? Feel free to
• Candice

  November 2020

  Hi Lotje,

  Thank you very much for your response!

  I sent you a simplified version of the experiment. I need participants to either skip the loop (if the participant pressed D immediately) or repeat the loop as many times as the participant provides an "enter" response, each of which needs to be followed by the two options again and needs to provide information chosen at random from a list. The problem with the run-if statements is that I need to allow up to 10 consecutive information requests, so that the main loop becomes quite long. I also need to randomize what kind of information they get, which I'm not sure I could do with feedback screens and run if statements (in a different experiment I tried to modify this kind of information using script screens, but it didn't work). Also, the reason why I need the loggers at both levels is that I need to know both how many times they gave an "enter" (information seeking) response and what their final decision was. Can you think of a different structure that would still allow that?

  I'm sorry, but I don't understand what you mean about the loggers. I believe they are all linked, are they not?

  Thanks again for your help!!

  Cheers,

  Candice
• lvanderlinden

  November 2020 edited November 2020

  Hi @Candice

  
  

  It appears that issues using linked copies (of logger items but also other items) are known to exist in OSWeb. It has to do with OpenSesame's prepare-run strategy.

  
  

  As a work-around, you could wrap a loop item around the linked copy of your logger like so:

  

  
  

  
  

  Hope this helps!

  
  

  Cheers,

  
  

  Lotje

  Did you like my answer? Feel free to
• Candice

  November 2020

  Hi Lotje,

  That seems to work!!! Thank you so much!!!

  Cheers,

  Candice
• lvanderlinden

  November 2020 edited November 2020

  Hi @Candice ,

  
  

  Great to hear and sorry for the inconvenience. OSWeb is still work in progress. :)

  
  

  Cheers,

  
  

  Lotje

  Did you like my answer? Feel free to