Paraview for VisCube

ParaView for VisCube

  1. Configuration Files
  2. Configure Server
  3. Configure VRPlugin
  4. Start Tracking

Configuration files (return to top)

Configuration files reside in the .config/ParaView directory located at the top level of your home directory (for Linux or Mac OS X). The .config/ParaView/servers.pvsc file contains server definitions used by ParaView.

<Servers>
  <Server name="console" configuration="" resource="cs://console:11111">
    <ManualStartup/>
  </Server>
</Servers>

Configure Server (return to top)

To set up ParaView for use with a cluster you’ll need to configure the server. Choose the Connect option from the File menu shown in Figure 1.

ParaView FIle menu

The Choose Server dialog box shown in Figure 2 will appear. You can add, edit, or delete configurations. You may also save or load server configuration files (with extension .pvsc). You can choose to create a server connection or you can load an existing server.pvsc file.

ParaView choose server dialog

Click on the Add Server button and then Configure New Server dialog box will appear. This will require that you start the pvserver(s) or pvdataserver(s) and pvrenderserver(s) manually.

Configure New Server dialog box

Edit the dialog to provide proper information for your cluster. The Name field can be anything you wish (it is recommended you give it a name so you know what it is for). The Server Type field should be Client/Server. The Host field should contain the hostname (i.e. console) or the associated IP address. The Port field should contain the network port to be used for your session.

Configure VRPlugin (return to top)

To enable head and wand tracking, you will need to add the VRPlugin to the client and servers. To do this, open the “Tools” menu and click “Manage Plugins…”. This will open the Plugin Manager window as shown in Figure 1.

Plugin Manager

Click on the “+” symbol next to VRPlugin for the local plugins (the right side). Enable the Auto Load checkbox. Click on the VRPlugin name (it should be highlighted). Then click the “Load Selected” button. Do the same for the remote plugins (the left side). When you are done, the details for both local and remote VRPlugin should look similar to Figure 2.

Plugin Manager - VRPlugin loaded

After this is done, click the “Close” button. You should see a new VR Panel as show in Figure 3 in the lower left of the information view. Go ahead and exit ParView so that the changes will be saved. Choose the “File” menu and click “Exit” or use the keyboard shortcut Ctrl+Q. You can launch ParaView again to continue.

VR Panel

Configure VRPlugin (return to top)

You can manually add the connections and interactions. The names can be changed, but the addresses and indexes should remain the same.

To add the connection for the head, click on the “Add…” button below the VR Connections list which will popup a window similar to that shown in Figure 4. Change the name and address. Then choose Tracker in the drop down, change the index to 0, and change the name of the tracker. Finally, click the “+” button to add the tracker definition. To finish editing click the “OK” button. Figure 5, 6, and 7 show the definitions for wand, joystick, and buttons respectively. Add each of the connections.

NOTE: Please note that the wand has 5 buttons, but the trigger is designated as index 5 and index 4 is omitted.

 

Add VR Connection-wand

 

Add VR Connection-joystick

 

Add VR Connection-buttons

You can manually configure the VR connections and interactions or load an existing state file containing this information. It is located at

/etc/paraview/pv4.0.1.vrpn.tracking.pvsm

on console machine.

 

Start Tracking (return to top)

To start tracking, simply click the “Start” button at the bottom of the VR Panel as shown in Figure 8. There have been issues using the “Stop” button which seems to cause ParaView to lock up. Should you have this issue, you will lose any work not already saved, and must use Ctrl+C in the terminal ParaView was started to exit.

VR Panel-start