search

lochhh / e-Babylab

Apache License 2.0
2 stars 4 forks source link

quesiton: cannot download data #5

Open piekomk opened 3 weeks ago

piekomk commented 3 weeks ago

Dear Developer, Thank you for developing such wonderful software. I am a researcher in infant studies and have recently started organizing a research group. Our members are interested in conducting surveys and both moderated and unmoderated experiments with infants and their caregivers in Japan. Since we are from different universities, we launched a server using a commercial VPS service and have just installed your e-babylab software. It works smoothly, except that we cannot download experiment data. When we try to do so, the browser displays an 'Internal server error (500)' message. We have read the troubleshooting guide you provided and made sure that the 'webcam' directory is placed in the same directory as 'ipl'. However, we still encounter the same error message. Can we resolve this issue? We would greatly appreciate any advice or suggestions you could offer. We understand that you are busy, and we truly appreciate your time and assistance in resolving this issue.

our environment: Ubuntu 22.04.4 LTS

piekomk commented 2 weeks ago

Hi,

I wanted to follow up on the issue I reported earlier about not being able to download experiment data. After digging a bit, I found that changing a line in ./ipl/experiments/reporter.py fixed the problem. Specifically: writer.save() needed to be changed to: writer.close()

After this modification, I was able to download the experiment data without any Internal Server Errors. I'm not entirely sure if this is the best solution, but it's working for us now. I thought it might be helpful to share this in case others encounter a similar issue.

Thanks again for developing this great tool. It's really making a difference in our research.

lochhh commented 1 week ago

Hi @piekomk thank you very much for raising and suggesting a fix for this issue! You're absolutely right about the need to change writer.save() to writer.close() as the former is indeed deprecated. I will push the fix next week when I'm back from vacation. Thank you once again.