Millisecond Forums

+x

 

Dave - 9/9/2022

+x

 

AKrishna - 9/9/2022

Speculation here, but maybe it has something to do with how the files are named when they are downloaded at the start of the experiment? My stimulus sets were long and shared large portions of their names. It would be very weird regardless, and I'm not sure why the problem didn't occur on the same computer with your scripts (especially the second one).

If it's a client-side thing, well... there isn't much that can be done if I can't reproduce it consistently. I'm under pressure to run the experiment, so I will probably just do it with the shorter filenames and hope there's no crashes, but if desired, I can recreate and upload an older version of the same experiment so we can try to reproduce it. Might be a few days before I have time, though.

> Speculation here, but maybe it has something to do with how the files are named when they are downloaded at the start of the experiment?

I don't see how that could be the case; to be sure, Windows used to have some weird constraints on maximum local path length, but these are a thing of the past and, in any event, the 2nd test script I posted should have triggered the error if that were the problem.

> I can recreate and upload an older version of the same experiment so we can try to reproduce it. Might be a few days before I have time, though.

I'll be happy to take a look if you want to go for this. It would, however, be important to have the exact script (and associated files) that originally produced the error, not a recreation. If that script had some really subtle mistake in it, the recreation might not have it.

+x

 

AKrishna - 9/9/2022

+x

 

Dave - 9/9/2022

+x

 

AKrishna - 9/9/2022

Speculation here, but maybe it has something to do with how the files are named when they are downloaded at the start of the experiment? My stimulus sets were long and shared large portions of their names. It would be very weird regardless, and I'm not sure why the problem didn't occur on the same computer with your scripts (especially the second one).

If it's a client-side thing, well... there isn't much that can be done if I can't reproduce it consistently. I'm under pressure to run the experiment, so I will probably just do it with the shorter filenames and hope there's no crashes, but if desired, I can recreate and upload an older version of the same experiment so we can try to reproduce it. Might be a few days before I have time, though.

> Speculation here, but maybe it has something to do with how the files are named when they are downloaded at the start of the experiment?

I don't see how that could be the case; to be sure, Windows used to have some weird constraints on maximum local path length, but these are a thing of the past and, in any event, the 2nd test script I posted should have triggered the error if that were the problem.

> I can recreate and upload an older version of the same experiment so we can try to reproduce it. Might be a few days before I have time, though.

I'll be happy to take a look if you want to go for this. It would, however, be important to have the exact script (and associated files) that originally produced the error, not a recreation. If that script had some really subtle mistake in it, the recreation might not have it.

Agreed. Unfortunately, I actually overwrote the old script files and renamed the original video files in my haste to figure out a solution to the problem. I'll tell you what - when I have some time (hopefully next week), I'll try and see whether I can reconstruct the file from older versions and see whether I can get the same error on my workstation. If so, I'll let you know. If not, it'll have to remain an unsolved mystery, I guess.