DL Visualize v2.5 - Configuring Job Execution

Local Jobs

If the installation instructions have been followed and the DLV_DEF_CRYSTAL, DLV_DEF_GULP or DLV_DEF_EXCURV (DLV_CRYSTAL, DLV_GULP or DLV_EXCURV on Windows) variables have been correctly configured then the job configuration is already completed.

Unix issues

A user can override the default CRYSTAL (or GULP) path set with the DLV_DEF_CRYSTAL (DLV_DEF_GULP) variable. This will automatically happen if a CRYSTAL (or GULP) directory is in your PATH variable. It can also be be overriden for CRYSTAL (GULP or EXCURV) by setting the DLV_CRYSTAL (DLV_GULP or DLV_EXCURV) environment variable in the shell before you start DLV.

Remote Jobs via ssh

Jobs can only be run on remote systems running Unix. To configure the remote machine to submit CRYSTAL (98 or 03) or GULP jobs via ssh requires a configuration where ssh does not prompt for a password. (DL_EXCURV does not support batch mode execution and can only be run on the local machine.)

  1. Configure ssh to use public/private key authentication and start the ssh agent required for authentication. You should now be able to check that you can run remote commands without being prompted for a password
    ssh remote ls
  2. Copy the $DLV_ROOT/scripts directory to the remote machine, preserving the directory name e.g.
    ssh remote mkdir dlv
    scp -r $DLV_ROOT/scripts remote:dlv
    where remote is the name of the remote machine, and dlv represents a directory on the remote machine to copy the files to.
  3. Edit (create) the ssh environment file (~/.ssh/environment in OpenSSH). Set the DLV_ROOT environment to the dlv directory you copied the scripts to, and the DLV_CRYSTAL variable to the location of CRYSTAL (or GULP) on the remote machine (not needed if the executable is in your PATH). The format for this with OpenSSH (on the remote system) is variable=value pairs, one per line.

The same procecure can be used to submit jobs to a remote batch queue. If the remote system is behind a firewall then you will need to use ssh port tunneling, if it is permitted.

Windows issues

Job submission from Windows has only been tested with the PuTTY tools. The variable REMOTE_TOOLS in $DLV_ROOT\dlv.bat needs to have been correctly set to the location of the PuTTY bin directory.

Remote Jobs via rsh

Jobs can only be run on remote systems running Unix. To configure the remote machine to run CRYSTAL98 or CRYSTAL03 (or GULP) you must

  1. Check that the remote system is set up so rsh works. e.g. try
    rsh remote ls
    The usual things to check are that your shell startup file doesn't produce any output, and that your .rhosts file on the remote machine is correctly set to allow access.
  2. Copy the $DLV_ROOT/scripts directory to the remote machine, preserving the directory name e.g.
    rsh remote mkdir dlv
    rcp -r $DLV_ROOT/scripts remote:dlv
    where remote is the name of the remote machine, and dlv represents a directory on the remote machine to copy the files to.
  3. Edit your shell startup file on the remote machine (.cshrc for Csh users) and set the DLV_ROOT environment to the dlv directory you copied the scripts to, and the DLV_CRYSTAL variable to the location of CRYSTAL (or GULP) on the remote machine (not needed if the executable is in your PATH).

Windows issues

Job submission from Windows has only been tested with the Cygwin tools. The optional inetutils package provides the rsh/rcp commands required by the remote job submission routines. The variable REMOTE_TOOLS in $DLV_ROOT\dlv.bat needs to have been correctly set to the location of the Cygwin tools bin directory.