- This topic has 1 reply, 1 voice, and was last updated 2 months ago by
.
-
Posts
-
Hello,
I am working with a AR Sandbox installation that was set up a few years ago. It has been working great, but about a month ago it began experiencing issues with freezing. The map would still be displayed, but the topography would no longer update when changes were made to the sand. It can be resolved by stopping and restarting the program, but I am looking for a permanent solution to this issue.
The most notable recurring issues from the program logs are:
1. Repeated messages of “Ran out of time by x.xx” with the X’s being varying numbers
2. Sometimes it reports:
terminate thrown after an instance of 'std.runtime_error'
what (): USB:: Device: :writecontrol: Device has been disconnected
Aborted (core dumped)I noted that the “ran out of time” errors occurred when making it rain, and sometimes made it freeze if too much water was added. I modified the evaporation rate and that made it seem more stable in the short-term. However, it very consistently freezes after running for a while, usually within a few hours.
Is the Kinect camera failing or is there some sort of performance bottleneck on the computer? It is running 360 Kinect, Ubuntu 18.04 LTS, 8GB memory, Intel i7-4770, and a GTX 970. The 970 is slightly underpowered compared to the officially recommended GTX 1060, but I’m not sure if this is the only explanation for the issues.
Initially, it was running SARndbox 2.6 but it has been updated to SARndbox 2.8 and re-calibrated, although the issues remain the same. I confirmed that the graphics drivers are installed properly as well.
Any thoughts or ideas on what could be going wrong here? Any help is appreciated.
Just 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.
- You must be logged in to reply to this topic.