OSWeb error

Comments

• JelleStudentRug

  July 2020

  p.s. using chrome version 83.0.4103.116, I got the error code from the console (f12)
• JelleStudentRug

  July 2020 edited July 2020

  I'm sorry if I'm spamming my own thread, I just can't seem to find an edit option for comments / posts.

  I should add that the error I get from my console is twofold; I thought it was only one error being presented twice, but upon closer inspection, it also says it cannot load the content for 'js.map':

  DevTools failed to load SourceMap: Could not load content for file:///C:/Users/Jelle/AppData/Local/Temp/vendors~osweb.1.3.8.bundle.js.map: System error: net::ERR_FILE_NOT_FOUND

  DevTools failed to load SourceMap: Could not load content for file:///C:/Users/Jelle/AppData/Local/Temp/vendors~osweb.1.3.8.bundle.css.map: System error: net::ERR_FILE_NOT_FOUND

  
  

  I also have this error in the console that opens when I open the experiment file:

  C:\Program Files (x86)\OpenSesame>python.exe Lib\site-packages\opensesame.py "C:\Users\Jelle\Desktop\DISNEG\OS\preferenceTask3.osexp"

  [2020-07-23 11:10:11,586:OpenScienceFramework:889:WARNING] Could not connect to cogsci.nl to get OSF settings: Error transferring http://cogsci.nl/dschreij/osfsettings.json - server replied: Not Found

  [2020-07-23 11:10:11,586:OpenScienceFramework:890:WARNING] Using cached OSF settings instead

  
  

  Could this in any way be what is causing the issue with OSWeb?

  I have also attached my (new) experiment file. It has many audio recordings (maybe that could be an issue too? The error starts when the loop with the second recording starts), and participants need to choose which pronunciation they prefer when presented with two recordings of the same sentence, but pronounced differently each time.

  preferenceTask3.osexp

  Many thanks!

  Best

  Jelle
• Daniel

  July 2020

  Hi @Jelle,

  The source map errors are harmless and are probably not the reason your experiment is not working. As a sidenote, I ran your experiment and also experience problems if I run it in OpenSesame (as in, I only see the arrow on the second instruction screen, and not the text).

  As for the freeze in osweb, it doesn't appear to be a problem with your experiment (even though its structure is quite intricate). It just doesn't want to continue after the IN_loop. I added a console.log() after the click to see if it was registered and it is, but somehow it doesn't continue. I can't really easily see what causes this and will need to find some time to look into this further.

  The osf warning is also likely not the reason your experiment is not working, but we should look into that I think @sebastiaan? I haven't seen this error before, but that's where the updated credentials for OSF can be found.

  Best

  
• JelleStudentRug

  July 2020 edited July 2020

  Dear Daniel,

  Thanks for your reply! I've attached another version of the experiment that does work offline, but also not on OSWeb. I hope this helps.

  PT v1.0.osexp

  
  

  (I did shorten the audio files in the training and experimental loop to only play for 1 second for the purpose of going through all of them quickly)

  And I get a new error when I close down opensesame:

  

  

  
  

  Best

  Jelle
• JelleStudentRug

  July 2020 edited July 2020

  Dear Daniel & Sebastiaan,

  
  

  I found the issue when reading a different thread! I had multiple linked loggers in the overall experiment_sequence, because I was using loops that could potentially loop multiple times, when participants would want to re-read the experiment information, correct typos or other reasons. Then it would make sense to have a logger only after the loop in the experiment sequence, because I am not interested in how many times the loop was run, but only in the final output (which would've made the analysis more easy, since you can automate it in R when each dataset has the same number of rows; now it'll take some manual labour). But those were linked copies of the same logger item, which apparently is an issue for now with OSWeb. I've put the loggers in the loop objects, and now, the experiment runs nicely in the browser.

  
  

  Many thanks!

  Best

  Jelle
• Daniel

  July 2020

  Ah yes, the referenced/linked item are an issue that is hard to quickly solve due to the way that osweb is currently built up. I hope you have managed to work around this now...