cwj

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: New Software Installation Mechanism #2775
    cwj
    Participant

    @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.

    in reply to: New Software Installation Mechanism #2772
    cwj
    Participant

    I 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.

    in reply to: New Software Installation Mechanism #2762
    cwj
    Participant

    I 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 1 month, 2 weeks ago by cwj.
    in reply to: Sandbox Software Unstable – Constantly Freezing #2760
    cwj
    Participant

    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.

Viewing 4 posts - 1 through 4 (of 4 total)