Start Cavepainting manually in the Cave: Difference between revisions

From VrlWiki
Jump to navigation Jump to search
Jadrian Miles (talk | contribs)
No edit summary
Jadrian Miles (talk | contribs)
No edit summary
Line 20: Line 20:
### Once all the red "Timing" and "Stereo" lights along the right turn green, you can hit "Quit"
### Once all the red "Timing" and "Stereo" lights along the right turn green, you can hit "Quit"
# Make sure that <tt>grexecd</tt> is running on the Windows machine in the corner to the right of the Cave and that there are no error messages or other weird things going on there.
# Make sure that <tt>grexecd</tt> is running on the Windows machine in the corner to the right of the Cave and that there are no error messages or other weird things going on there.
# Run your personalized Cavepainting script on <tt>wallconsole</tt>.  These steps should be equivalent to just pressing the corresponding button on the [http://wallconsole/kiosk/index.cgi?mode=cs137fall08 kiosk webpage].
# Run Cavepainting on <tt>wallconsole</tt>.  You have three options, listed in increasing order of hassle and debuggability:
## <code>ssh -Y cavedemo@wallconsole</code>
## Press the button on the [http://wallconsole/kiosk/index.cgi?mode=cs137fall08 kiosk webpage] corresponding to your project.
## <code>$G/bin/cave.cscluster.<some other junk that includes your username></code>
## Run your personalized Cavepainting script directly:
### <code>ssh -Y cavedemo@wallconsole</code>
### <code>$G/bin/cave.cscluster.<some other junk that includes your username></code>
## Run the commands typically included in such a script manually:
### <code>ssh -Y cavedemo@wallconsole</code>
### <code>$G/bin/cave_display_cscluster</code>
### <code>ssh -Y demo@cs-nodes</code>
### <code>setenv GROOT /ccvdisk2/dollar-g-cs137; source $GROOT/tools/gfxtools-startup-csh</code>
### <code>$G/bin/cavepainting-cave -c SaveBasePath=$G/data/cavepaintings/<user> -c LoadBasePath=$G/data/cavepaintings/<user> -c UserDataDir=$G/data/cavepaintings/<user></code>
# You should now see activity in a new terminal window on the Windows machine, then a big grey window on the Windows machine, and then Cavepainting should start in the Cave.
# You should now see activity in a new terminal window on the Windows machine, then a big grey window on the Windows machine, and then Cavepainting should start in the Cave.
# If there are problems with the display, check out [[Troubleshoot Cavepainting|HOWTO Troubleshoot Cavepainting]]. Be sure to also follow the [[Cavepainting user's guide]], and especially to shut down properly by using the ESC key on the Windows machine.
# If there are problems with the display, check out [[Troubleshoot Cavepainting|HOWTO Troubleshoot Cavepainting]].
# Be sure to follow the [[Cavepainting user's guide]], and especially to shut down properly by using the ESC key on the Windows machine.


[[Category:HOWTO]]
[[Category:HOWTO]]

Revision as of 11:18, 16 September 2008

Cavepainting in the Cave involves coordination among a bunch of different machines. This article shows you HOWTO get everything running by issuing commands from the command line.

  1. Turn on tracking (VRPN) on serial
    1. ssh cavedemo@serial
    2. cd /share/gfx/bin
      Note that you don't want to go to $G!
    3. ./vrpn_start.current
    4. Leave this program running and open up a new terminal to do the following steps.
  2. Set up the displays on cs-nodes
    1. ssh -Y cs-nodes
    2. cd /vol/projects/cave-powerwall
    3. ./setup_cave.sh
    4. ./myframelock.sh
      • Note that this script might whine. Give it a long time to throw up errors; it eventually shows.
      • If it stalls after displaying "cs-front", hit ctrl-C and see if it continues through the other machines and works.
      • If it is taking especially long, hit ctrl-C a few times until you return to the prompt and try again. I'm not sure why this program is so nondeterministic.
    5. In the Nvidia config GUI program that pops up:
      1. Go to "Frame Lock" in the left-hand pane
      2. Make sure that cs-front has the "server" box checked and all others are "client"
      3. Hit the "Enable Frame Lock" button in the lower-right
      4. Once all the red "Timing" and "Stereo" lights along the right turn green, you can hit "Quit"
  3. Make sure that grexecd is running on the Windows machine in the corner to the right of the Cave and that there are no error messages or other weird things going on there.
  4. Run Cavepainting on wallconsole. You have three options, listed in increasing order of hassle and debuggability:
    1. Press the button on the kiosk webpage corresponding to your project.
    2. Run your personalized Cavepainting script directly:
      1. ssh -Y cavedemo@wallconsole
      2. $G/bin/cave.cscluster.<some other junk that includes your username>
    3. Run the commands typically included in such a script manually:
      1. ssh -Y cavedemo@wallconsole
      2. $G/bin/cave_display_cscluster
      3. ssh -Y demo@cs-nodes
      4. setenv GROOT /ccvdisk2/dollar-g-cs137; source $GROOT/tools/gfxtools-startup-csh
      5. $G/bin/cavepainting-cave -c SaveBasePath=$G/data/cavepaintings/<user> -c LoadBasePath=$G/data/cavepaintings/<user> -c UserDataDir=$G/data/cavepaintings/<user>
  5. You should now see activity in a new terminal window on the Windows machine, then a big grey window on the Windows machine, and then Cavepainting should start in the Cave.
  6. If there are problems with the display, check out HOWTO Troubleshoot Cavepainting.
  7. Be sure to follow the Cavepainting user's guide, and especially to shut down properly by using the ESC key on the Windows machine.