Sean Robinson

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 77 total)
  • Author
    Posts
  • in reply to: SanBox app reset #2207
    Sean Robinson
    Participant

    There will be copies of configuration files with default values in the directories where you built the sandbox. Or in the tar.gz files downloaded to start the build process.

    If neither of these work, please give more details about which files you want to reset.

    in reply to: VRUI – “Unable to locate package” #2206
    Sean Robinson
    Participant

    …we are using PC Dr Oliver mentioned…

    I’m a bit confused. Do you have an “HP Victus” (as you mentioned above) or an “HP Pavillion” (Oliver’s new purchase)? If a Victus, is it a desktop computer or a laptop?

    in reply to: VRUI – “Unable to locate package” #2197
    Sean Robinson
    Participant

    Thank you for posting the links to your Linux Mate threads, they filled in many details.

    The short version: 19.3 & 20.1 can not see hard drive in this PC.

    I see several discussions about changing the hard drive interface in BIOS to fix the missing drive on Ubuntu, et al. The following thread has one of the more explicit fixes and explanations.

    https://ubuntu-mate.community/t/cant-see-nvme-m-2-drive-for-fresh-install/18463

    Missing 1 line of code?

    The cstddef header is included in iostream, which is included in FrameRateViewer.h. The include chain should bring in the size_t type. I built Vrui with g++ 11.2 (same version used in LM21) without that error.

    Another possible avenue with your local Linux Mint expert: use a fresh, clean LM21 and try to manually build Vrui, etc. The “Unable to locate package libdc1394-22-dev” is specific to using Build-Ubuntu.sh. Or edit Build-Ubuntu.sh to install libdc1394-25-dev instead.

    in reply to: VRUI – “Unable to locate package” #2185
    Sean Robinson
    Participant

    Is Artie your nickname?

    Artie the Artichoke is our school’s mascot.

    in reply to: VRUI – “Unable to locate package” #2183
    Sean Robinson
    Participant

    came close to success.

    Actually, the compiling errors ou posted in the Linux Mint forum hints that there are many incompatible changes between v19 and v21 that Vrui has not been updated to handle.

    Question: which version of 20 do you recommend?

    My initial recommendation for Linux Mint v20 was based solely on libdc1394-22-dev. But there may be other changes between v19 and v20 that would cause Vrui, Kinect, and SARndbox to not build.

    As the latest recommended version is v19.3, stick to that version for now.

    Also, from reading your post on the Linux Mint forum, the KeckCAVES Github page does not seem to be actively maintained. Your best bet for help is probably this forum.

    in reply to: VRUI – “Unable to locate package” #2181
    Sean Robinson
    Participant

    My recommendation is to use Linux Mint v19 or v20. By using v21, some of the software needed by Vrui has been upgraded. This could work, but Vrui has not been tested with the newer versions.

    To clarify, the Sourceforge address you shared is for the libdc1394 project. libdc1394-22-dev and libdc1394-25-dev are the Ubuntu packages made from the project code.

    Another clarification: MATE is a GUI environment running on the Linux Mint distribution. Mint uses Ubuntu as a source for additional software packages. Having these distinctions in mind may help when researching software.

    Wikipedia has good articles that can give you context for how these pieces (e.g. MATE, Mint, Ubuntu) mesh.

    in reply to: Sandbox doesn’t project correctly #2180
    Sean Robinson
    Participant

    Good work and congratulations!

    in reply to: Sandbox doesn’t project correctly #2173
    Sean Robinson
    Participant

    Make sure you are using -uhm with SARndbox to enable elevation color mapping.

    You can also use SARndbox -h to see which file the sandbox will use for colors. Find “Default elevation color map file name” in the help output and verify the file shown on that line is located at the given path and that the file is readable (i.e. proper permisisons).

    If the contour lines seem in the wrong places on the sand, then calibrate the sandbox, again, with CalibrateProjector.

    in reply to: Calibration Issues #2166
    Sean Robinson
    Participant

    Alguma dica?

    Random calibration ideas:

    • Use a CD or DVD as the target disc. A too big or too small disc will not work.
    • Add a stiff wire or small stick to hold the target disc.
    • Do not hold the disc itself, hold only the wire or stick. Leave a 2-3 cm gap between your fingers and the target disc edge.
    • Keep the disc at least 2-3 cm from any box or sand wall.
    • Keep the disc at least 2-3 cm above nearby sand.
    • The yellow or green projected circle may not align with the target disc. This is not a problem.
    • When the projected disc is green (no matter where projected), press the capture key.
    • Clean the Kinect lenses with a soft cloth.
    • The Kinect-to-sand distance should be close to 1 meter.

    The list above contains generic advice, pictures from your calibration process might help find something else.

    in reply to: Calibration Issues #2165
    Sean Robinson
    Participant

    Can you link to pictures of your sandbox during calibration?

    For the second part, this is probably related to the Base Plane Equation measured in Step 8. If you change the fourth number (near -100.0) to a few centimeters less negative, it will raise the “sea level”.

    in reply to: Locate AR Sandbox in San Diego County #2163
    Sean Robinson
    Participant
    in reply to: Calibration Issues #2161
    Sean Robinson
    Participant

    @carmemmaluf,

    If the CD never turns green the tie point capture will not work. It should turn green before you press the “1” key.

    Make sure the CD is isolated from other things (e.g. sand, box wall, a hand). The calibration software looks for a circle.

    in reply to: Calibration Issues #2158
    Sean Robinson
    Participant

    I have a few questions to better understand what to are doing and seeing.

    I’ll assume you are “calibrating Kinect” with RawKinectViewer. Which field in the output says “-nan”? Do you have a value for “Camera-space plane equation”?

    I’ll assume you are using CalibrateProjector when the second problem appears. After the “warning window” appears, do you press a second, different key? When you try to capture the first tie point (by centering the target on the crosshairs and pressing “1”), does your terminal window show “Capturing 60 tie point frames…”?

    in reply to: bindings for 1/2 and mouse 1/2 #2153
    Sean Robinson
    Participant

    AFAICT, “Mouse” is the name of the standard keyboard/mouse input device adapter. So, the “1” and “2” in the bindings line refer to the keys which would produce the numerals “1” and “2” in a text editor.

    What is the path of the file that contains your config?

    Please also post that config file’s full contents.

    in reply to: USB JOYSTICK DON’T WORK! #2152
    Sean Robinson
    Participant

    Thanks Sean for your help, i solved that problem

    Did my answer solve the problem? Or did you need to change something else?

    I tried to replace mouse with USBEncoder but i don’t know witch number or letter are the button.

    You will need to know the keyboard key(s) assigned to the button(s). With the cursor in a text editor, what letter or number appears when you press the USB button(s)? Can you assign a specific key with the button’s software?

    If you have two buttons set up with the letters “p” (piove) and “a” (asciuga), I believe you will need to change the line bindings ((Mouse, 1, 2)) to bindings ((USBEncoder, p, a)).

    bindings ((Mouse, p, a)) works for me, on a normal USB keyboard, to flood and drain.

Viewing 15 posts - 46 through 60 (of 77 total)