Forum Replies Created
-
AuthorPosts
-
cwjParticipant
Thank you @okreylos for the insight and confirmation that this is a hardware issue. I definitely came to that conclusion after all the troubleshooting, so that will be the next step for my situation.
I don’t have plans to make any changes (i.e. replacing Kinect) to our sandbox deployment right now, but if I ever do I will come back here to provide any updates.
cwjParticipantI did manage to put together a basic script that will auto-start and restart the program every 30 minutes, which seems to be effective for mitigating the issue. If it is freezing every 5 minutes for you, you may want to change the timeout (in seconds) to something shorter. Adding the “-evr” flag to change the evaporation rate also helped lessen the freezing. Also check that the directory matches where your program is stored. This is definitely a band-aid fix, though, and I would love to see a proper solution implemented.
I recommend scheduling a cronjob for an automatic restart each day, since brute-forcing it this way could cause memory issues if you do it for too long. You’ll need to set the account to auto-login on startup if not already, and then add this script as a startup program (through the system settings menu).
#!/bin/bash while true; do # Kill running instance kill -9 $(pgrep -f "SARndbox -uhm -fpv -evr -0.03") # Wait for previous instance to terminate sleep 7 # Change directory cd /opt/SARndbox-2.12 #Run program with 30 minute timeout timeout 1800 SARndbox -uhm -fpv -evr -0.03 done
cwjParticipant@gcsciencemill Unfortunately I don’t have an answer for that, the program continues to work like it did before despite the error occurring each time. I tried manually creating the .dat file it was looking for but that made it non-functional, so I am just leaving it be.
cwjParticipantI am also experiencing this same error, but I don’t know why it started suddenly. I was not having the issue when I pulled the installation files last month. The sandbox also still seems to function properly despite the error, in my case.
cwjParticipantI still received the same error that mkaszuba (above) did when pulling the packages (no such file or directory) and when trying to run the program (intrinsic calibration.dat not found). Is there a process for resolving this issue, or does it not have a significant impact on the operation of the program?
- This reply was modified 2 months, 3 weeks ago by cwj.
cwjParticipantJust as a brief update, the ‘ran out of time by’ error originally was repeated and were small numbers like 4.286, but now it only appears once before the program freezes and the number is significantly larger, something like 42000.
I have not seen the USB error in a while, but I am wondering if the program is timing out because the Kinect is failing? The rest of the computer seems to be running fine when the program is frozen. It has been running v2.6 of SARndbox for years now, so it would be strange to be attributed to a configuration issue.
I also found the new installation instructions on this forum and used the PullPackage tool to install the newer version of SARndbox (upgraded from 2.8 to 2.12) but unfortunately this did not resolve the issue at all.
-
AuthorPosts