Odd spike behaviour

Hello Jared

Could you attach your modified Lua script to this thread (I’ve enabled upload of .lua files) and we will see if we can figure out why you get an error on line 62.

While Otii is making a recording it creates temporary files in your document folder. On Windows that would be My Documents/otii/.openproject. You will find a number of binary .dat files and a .json file which is the project description. If these files have recent modified times then your data is still being saved. You can try to recover these files to extract your data. Start by making a copy of .openproject folder so you can restore it if needed. After you have made a copy you can forcefully terminate Otii. Next time you start it it will try to recover the project. When recovered you can right click on the recording and export the data as csv if you want to import it into matlab.
If this fails you can try reading the .dat file. It is a long sequence of doubles with your actual data. It is not time coded so the sample rate indicated in the json file determines the timestamp of each sample.
The output in the ScriptView window is unfortunately never saved anywhere by the application so if you can’t access it from the UI it’s unfortunately gone.

There might be two reasons why the UI is not responding. I’m not exactly sure about your project setup but if you have graphs visible there’s a lot of samples in them after 40 hours. We know this will affect performance and we are investigating how to improve in this area. What we however suspect is that the ScriptView is not optimal at having a very large output, and I suspect that you have more than 20000 lines in there. This was something we were not aware of previously but when running some tests with large data in the ScriptView we noticed a major slowdown.

We would recommend that you do this kind of operations with otiicli instead as it then will not draw any UI. It should be no problem to run for several days. You might want to pipe the output to a file so you get all the history (so your terminal’s buffer doesn’t limit you). Or write to a file directly from the Lua script.

Best Regards
Christer Fletcher