Covise-installation

From Immersive Visualization Lab Wiki
Revision as of 16:53, 2 July 2009 by Jschulze (Talk | contribs)

Jump to: navigation, search

Contents

COVISE Installation Tips

These tips apply only to collaborators of IVL who intend to use the educational license of COVISE for non-profit purposes. Also, only the Linux version of COVISE is covered. There is a Windows version but when you decide to use it we can't give any support due to a lack of experience with it.

Installation of base system

  • Create an account for the COVISE installation, e.g., "covise".
  • In /etc/passwd set the default shell for this account to /bin/tcsh.
  • Download COVISE for your Linux distribution from the HLRS download page.
  • Follow the installation instructions on that web site.
  • Once installed, run "opencover" to see if it was successful. You should see a black window with the COVER menu.

Adding support to compile plugins

At this point you can only use COVISE's built-in plugins. In the following steps we're going to add the ability to compile custom plug-ins.

  • Copy your plugin source code to the machine COVISE is installed on.
  • Make sure the environment variable QT_HOME points to your Qt installation, with qmake under the bin directory. Example:
    setenv QT_HOME /home/covise/covise/extern_libs/qt4

Display and plugin configuration

At this point when you run opencover it comes up in a fixed size window on the node you run it on. In order to change the screen configuration and enable your plugins we are going to edit COVISE's configuration file. The configuration file is located at ~covise/covise/config.

  • Come up with a name for the configuration file. For instance, if your machine or tiled display wall has a name then use that. Let's assume the name is starcave.
  • Add a line to the .cshrc file in covise's home directory:
    setenv $COCONFIG starcave.xml
    .
  • Copy the default configuration file config.xml to starcave.xml
    cp config.xml starcave.xml
    .
  • To enable a custom plugin like MyPlugin add a line to the <Plugins> section:
    <MyPlugin value="on" />