Thanks for your reply.
Yes, I am saying that opening 2 files with the same name but different folders doesn’t allow them to be distinguished in Runner.
The best example that I have of an experiment that doesn’t compile its script but doesn’t raise an error is the ‘IAT.psyexp’ file attached. However, I don’t think it will behave in the same way on a different PC. On my PC, the program saves changes that I make to it (the save date and time are typically updated, although in one instance of the problem this was not occurring), but does not create a ‘_lastrun.py’ file and none of the changes show up when it runs. (Bizarrely, it continues to run even when removed from the folder that contains its last ‘_lastrun.py’ file and the various images and Excel conditions files that it requires. In this respect, the program runs as if it was still located in the old folder.) But when I copy the .psyexp file to a different PC and run it there, it creates a new ‘_lastrun.py’ file and throws an error because the files it requires are not present. (I can’t get any further on this other PC because it lacks a suitable graphics card for PsychoPy, but the program seems to behave normally up to this point). If it is any help, I can also attach a zipped folder containing the images and conditions files that the program normally requires, but I suspect you’ll just see a program working normally.
Although I don’t know what caused the program to start behaving this way in PsychoPy v2020.1.3 (i.e. what initially prevented the ‘_lastrun.py’ file from updating), I think Experiment Runner is somehow linked to the persistence of the problem, as the ‘solution’ to the problem is different on v2020.1.3 and v3.2.4. When I was using v3.2.4 and the program failed to generate a ‘_lastrun.py’ file or to show changes, I was able to identify the cause as an uncaught coding error and once the error was resolved the program started behaving normally again. Also, the program ceased to run if it was copied to a new folder without also copying its last ‘_lastrun.py’ file. In contrast, when using v2020.1.3, the cause was not a coding error because the program worked normally when re-named. And the program did not cease to run when put into a new folder without its last ‘_lastrun.py’ file. I don’t know how Experiment Runner works, but it looks as if something was helping the .psyexp program to keep track of where its ‘_lastrun.py’ file and various image and Excel files were located and making sure that it found the old ones no matter where it was moved to.
As I’ve said, the initial cause of the problem in v2020.1.3 is difficult to determine. In one case it started when I retrieved a program folder from the Windows recycle bin. On another occasion, it started after I had saved a change to the code, but reverting to the old code did not resolve the problem (as had been the case in v3.2.4) and the only solution was to rename the program. At other times, it has been impossible even to guess what might have triggered it because I did not discover the problem until I had been failing to understand for some time why debugging attempts were not working. I should admit that my PC is prone to crashing (it freezes and requires a forced reboot, on average once per day), but this has not corrupted programs or documents I’ve been writing in any other software.
IAT.psyexp (158.2 KB)