TomArmstrong
About
- Username
- TomArmstrong
- Joined
- Visits
- 207
- Last Active
- Roles
- Member
Comments
-
Hi Sebastiaan, Thanks--that makes sense. The only caveat is that for the collaborating lab, it wasn't happening at calibration, but instead during image presentation, but I guess the experiment isn't doing anything 4 or 8 seconds into a 12-second i…
-
One more observation: something similar (perhaps?) happened in my lab today. OpenSesame froze up mid-calibration with the Gazepoint. It exited out to GUI window, which was frozen with icons at top greyed out; when RA clicked on OpenSesame icon in ta…
-
HI Sebastiaan, Thanks for reply! I'm looping in @Edwin. I have looked through the data files. For three instances (172, 203, 203a), the issue happens during the 12 s presentation of the image pairs (when eye movement data is being recorded). We are…
-
And if it is helpful, here are comments from IT person: 1. When the students were running the program, at certain points throughout the processor fan will speed up (to the point where you can hear it) indicating the processor is being used clo…
-
A few more details. The fan pretty consistently speeds up and becomes loud during the experiment. Also, when the issue happened again today, we got this message: Stopped: The experiment did not finish normally. - The experiment process was killed …
-
btw issue happens about 1/4 times we run participants
-
As a follow-up, I see that the messages are being written to the _log.txt file, not the .tsv file. (The _log.txt file is not outputted when Eye Tribe is the tracker type.) Is it possible to do custom logging to the .tsv with OpenGaze as tracker type…
-
Ahh, I get it. So far so good after 3 participants. I'll let you know if we get another IO error. Thanks again!
-
Thanks for the advice. I now have the images in a folder "__pool__" in the experiment folder. Just to make sure I follow: when you used the "__pool__" folder method, OpenSesame still copies the files to a temporary folder, as it …
-
Of course the day after I post, the IO error comes back! We just got it twice for one participant. First, it happened where it often does, in the last trial of the first block of trials. Then, upon trying to start the experiment from the place it cr…
-
Hi Sebastiaan and Edward, I fixed the file extension--from .JPG to .jpg--and there have been no IO errors for the last 19 participants! We used to get it ~1/5 participants, so I am pretty sure the problem is solved, but I will check back after we ru…
-
Thanks Sebastiaan! I will start there. We are using a PC with Windows 10.
-
https://forum.cogsci.nl/uploads/308/FUK0Z5KJ2AYV.osexp Hi Eduard, Here is the experiment (it's the actual experiment--not the test version with the inline script). The first screen allows you to start at different points in the experiment, depending…
-
I am deeply grateful for this software and for the countless hours of hard work that the developers put into it. However, I have lost dozens of paid participants to runtime errors involving Python repeatedly crashing, or IO errors involving supposed…
-
Hi Eduard, I tried out that code. I edited the example by inserting one of my files in as the filename: my_canvas = Canvas() # Determine the absolute path: path = exp.pool[u'Rock.jpg'] # Function interface my_canvas.image(path) # Element interface m…
-
Thanks Eduard! I will try that out. Here is the experiment. We got the error on a different PC, prior to upgrading to the faster PC we are using now. But I will try to test on a different machine in our lab. I'll let you know how the test with the s…
-
I just confirmed that the error is independent of the actual image: It happens for either of the two images (Rock.jpg and Poop.jpg).
-
Thanks for your reply. It seems to be independent of the actual image. Any thoughts on why it might happen in the last iteration of the loop? The 15 prior iterations involve presentation of the same two stimuli--poop.jpg and rock.jpg from the file …
-
Hi all, This inexplicable IO error has been happening with more regularity in another experiment. In this case, we can see the file in the file pool that supposedly is not available (it's a disgust experiment, hence the image name). Although I can…
-
I'll take any advice I can get :) Thanks Eduard. I can't reliably reproduce the error. It happens in two different experiments unpredictably at a low frequency. I wasn't even going to post about it because it's rare and odd, but it happened just en…
-
Thanks for the advice! I'll give it a shot.
-
Hi Sebastiaan, Thanks for the reply and pardon the delay. The surveys do not crash--I was just concerned that having a second experiment file open while running another might be the issue, but it does not appear to be related. I have implemented a…
-
I have an EyeLink 1000 plus, several Eye Tribes, and now a Gazepoint. Most of my research is on dwell time, so I don't find that I need the EyeLink---I bought it because at the time, it wasn't that much more than a 60 Hz system from ASL or SMI...th…
-
I was able to install lmxl from the debug window once I ran OpenSesame as an administrator. Now I'm all set! Thanks everyone for your help! Very cool to see how the Gazepoint calibration routine plays out in PyGaze/OpenSesame! :)
-
Thanks cesco! As you suspected, I did the GitHub download wrong. Now I am back to the 'No module named lxml.etree error'. So I just need to get the lxml library installed, which I will now try with your advice regarding the path...
-
Thanks Edwin! I'm looking forward to using the GP3 :) I think I'm almost there. I ran that code in the debug window in OpenSesame, and here is what happened: Collecting lxml Using cached https://files.pythonhosted.org/packages/d7/ce/e5aa3dd8f9b402…
-
Hi all, I am posting in this thread rather than creating a new one because I suspect it is a similar issue. In both Gazepoint 4.3 and the new 5.1 release, I encounter this error at the pygaze_init object (with opengaze selected as the tracker). I'm…
-
Also, after this happened, I asked the research assistant to close the OpenSesame file for the surveys that precede the experiment (window on the right) before running the experiment (window on the left). The error still occurs. One more thing: the …
-
Thanks for your help, Sebastiaan. We've been using the multiprocess runner. The OpenSesame experiment crashes, but the entire program doesn't--it goes back to the user interface screen with the error message. Also, it happens to us about 50% of the…
-
@sebastiaan Pardon the late reply! I don't know how exactly E-Prime deals with this, but in my experience, using the flag object to jump ahead never caused crashes.