Forum Replies Created

Viewing 15 posts - 316 through 330 (of 522 total)
  • Author
    Posts
  • in reply to: Warsaw University try on ARSandbox #102024
    Oliver Kreylos
    Keymaster

    Cool idea!

    Unfortunately, the stepping problem you are seeing is something some Kinects do. It’s a flaw of the device hardware itself, and it cannot be fixed via calibration. If you have access to another Kinect camera, please try that one to see if it works better.

    What makes the problem worse in your case is the long distance between the Kinect and the surface you are scanning (looks to be about 2 meters?). That’s outside the Kinect’s accurate scanning range; the ideal resolution of its elevation measurements at that distance will be > 1 centimeter, and noise will be on the order of several centimeters.

    in reply to: Minor software update #102023
    Oliver Kreylos
    Keymaster

    If you created a control pipe Foo.fifo via

    $ mkfifo Foo.fifo

    and then ran SARndbox with the additional -cp Foo.fifo command line argument,

    and created a color map file Bar.cpt, then you can

    $ echo "colorMap Bar.cpt" > Foo.fifo

    to immediately load the color map in Bar.cpt while the AR Sandbox is running.

    in reply to: installing to different location #101929
    Oliver Kreylos
    Keymaster

    They do (I just tried both), but if you did the original install based on Vrui in a different location than the one at the top of their respective makefiles, you have to do
    make VRUI_MAKEDIR=<Vrui dir>/share/make clean

    in reply to: installing to different location #101925
    Oliver Kreylos
    Keymaster

    I just downloaded a new tarball of Vrui-3.1-004 into my ~/src directory, unpacked it, and ran this from a terminal:

    cd /home/user/src/Vrui-3.1-004
    make INSTALLDIR=/home/user/Foo
    make INSTALLDIR=/home/user/Foo install

    which installed into /home/user/Foo. I then built Vrui’s example programs:

    cd ExamplePrograms
    make VRUI_MAKEDIR=/home/user/Foo/share/Vrui-3.1/make INSTALLDIR=/home/user/Foo
    make VRUI_MAKEDIR=/home/user/Foo/share/Vrui-3.1/make INSTALLDIR=/home/user/Foo install

    which worked as well, and the example programs work and find their configuration files. I didn’t try SARndbox, but it would work as well.

    Did you run make from a directory in which you had run make before, using a different installation directory? To do that, you first need to run make clean, so that all sources get rebuilt with the new installation directory.

    Oliver Kreylos
    Keymaster

    The important distinction between graphics cards for the AR Sandbox is the number of floating-point operations per second (flops), which is more or less proportional to the product of number of CUDA cores / stream processors and clock frequency, but memory bandwidth and core efficiency enter it as well. Flops ratings can be found on the Wikipedia entries for most GPUs, and on GPU benchmark sites. For comparison, our recommended Nvidia GeForce 970 GTX delivers around 3.5 teraflops.

    Memory size is not important, as the AR Sandbox in default configuration uses much less than 1 GB of VRAM.

    in reply to: updated pic 8020 mast #101910
    Oliver Kreylos
    Keymaster

    None. You can edit the BoxLayout.txt file with new values whenever you need to, and CalibrateProjector overwrites the ProjectorMatrix.dat file every time it exits.

    Your post should be ignored during calibration, as it will be considered background.

    in reply to: Can we fixed the function of each key #101909
    Oliver Kreylos
    Keymaster

    Yes. First, start the application and set up key and button functions to your liking. Then open the main menu, go to “Vrui System,” to “Devices,” and then select “Save Input Graph…”. Click on the “OK” button in the file selection box that comes up. You can change the file name in the selection box by first pressing F1 to enter text mode, then edit the name as usual, then press F1 again to go back to tool mode.

    This will save the current tool bindings and settings to a file with a .inputgraph extension.

    The next time you run the application, pass loadInputGraph <input graph file name> on the command line, where <input graph file name> is the name of the file that was created when you saved the graph.

    in reply to: Set level of both Water and Rain #101904
    Oliver Kreylos
    Keymaster

    You can set the range of rain elevations via the -rer <min rain elevation> <max rain elevation> command line parameter to SARndbox. The elevation values are in centimeters relative to your configured base plane.

    I don’t know what you mean by setting the water level.

    I don’t know how to search the forum from inside, but you can try google with the site:lakeviz.org search modifier. For example, googling site:lakeviz.org usb button returns all posts which discuss using USB buttons.

    in reply to: Dynamically adjust the contour datum ? #101826
    Oliver Kreylos
    Keymaster

    Might be due to HTML formatting. On the command line, check that you’re using a greater-than sign (>) to direct output from the echo command to the pipe.

    SARndbox should print an error message to its console when it doesn’t understand a request on the pipe. Do you get anything?

    Lastly, you cannot print from a pipe, or open a pipe with a text editor. It’s a one-way communication pathway, in this case into the SARndbox program.

    in reply to: Dynamically adjust the contour datum ? #101819
    Oliver Kreylos
    Keymaster

    There is currently no code to change the contour line offset in the code. There is the ability to change color maps on-the-fly that maphew pointed out.

    That feature might work better for your purpose, but will require some work. To show the effects of water level changes, you could create a series of color maps that are identical in the high-elevation parts, but cut from dry land color to blue at different elevations (and the granularity of those changes is entirely up to you). By dynamically switching between those, you can raise or lower the apparent water level. The nice thing is that the changes won’t affect dry parts of the surface at all, so it will look much nicer. If you offset contour lines, or change the base elevation plane, everything will change, which might bury the changes you want to show.

    Changing the base plane would be a pretty simple feature to put in, though.

    in reply to: Per-pixel depth correction #101815
    Oliver Kreylos
    Keymaster

    The Kinect v1 has a set minimum scanning distance, and when you’re getting close to that distance, you will see points appearing or disappearing randomly, due to measurement errors. But once you move more than a few centimeters below the minimum distance, you should get a solid black depth image.

    in reply to: Rain bounding box #101814
    Oliver Kreylos
    Keymaster

    The water simulation’s bounding box is set when you measure the 3D corner positions of your sandbox during calibration. You can either re-do that step and put your new values into BoxLayout.txt, or move the corner points outwards manually by editing BoxLayout.txt. Don’t overdo it though; if the simulation bounding box extends beyond the edges of your sand surface as captured by the Kinect, you will get drastically reduced simulation performance.

    in reply to: BoxLayout File #101790
    Oliver Kreylos
    Keymaster

    BoxLayout.txt already exists, in /etc/SARndbox-<version> inside the SARndbox source code directory. You can edit that file, or copy your new file into that directory.

    in reply to: Calibration Problem! #101779
    Oliver Kreylos
    Keymaster

    When you create the “Capture” tool, you assign two buttons to it — the first one you press to bring up the tool selection menu, the second one you press when the tool creation dialog box pops up.

    To capture a tie point, press the first button you assigned, not the second one.

    in reply to: Complete Installation Instructions #101769
    Oliver Kreylos
    Keymaster

    Did you cd into the SARndbox directory before trying to run ./bin/CalibrateProjector? It should go like this:

    $ cd ~/src/SARndbox-1.6
    $ ./bin/CalibrateProjector -s 1024 768

    If that still doesn’t work, do

    $ ls ~/src/SARndbox-1.6

    and check that the d, o, and bin directories exist. If not, run

    $ make

    If you run into further problems, please start a new thread in the main forum. This thread is becoming hard to manage.

Viewing 15 posts - 316 through 330 (of 522 total)