DIAL release 1.20: Getting started

David Adams
13jun05

Setup

The first step toward using DIAL is to run a setup script that defines a few environmental variables and aliases. Ask the dial installer where these scripts are located. Here we assume they are at $DIALSETDIR. The set up is one of the following (depending on your shell):

  > . $DIALSETDIR/setup.sh
  > source $DIALSETDIR/setup.csh

This setup has a minimal effect on your environment and can safely be put in a user or system login file.

Here are some of the places these setup files may be found:

   BNL: DIALSETDIR=/usatlas/ada_sw/apps/dial/setup
  CERN: DIALSETDIR=/afs/cern.ch/user/d/dial/apps/dial/setup

Please note the that the BNL location has changed since release 1.1.0.

Command line interface

The easiest way to run any of the DIAL command-line tools is to open a DIAL shell, issue the command then exit back to the starting shell:

  > dial
  dial: Starting DIAL version 1.20 with configuration atlas.

  Welcome to DIAL
  dial-1.20> uidtest
  ID connection is 
    WsClientUniqueIdGenerator:http://adial01.usatlas.bnl.gov:20001:true
  Next Test ID is 124-12
  dial-1.20> exit
  exit
  Leaving DIAL

  >

The DIAL version and configuration may be explictly specified on the command line:

  > dial -v 1.20 -c atlas

A single command may be run directly:

  > dial uidest
  ID connection is 
    WsClientUniqueIdGenerator:http://adial01.usatlas.bnl.gov:20001:true
  Next Test ID is 124-12
  dial-1.20> exit

ROOT interface

Most common is to start a root session with the command dialroot. This will start a DIAL shell if it is not run inside a shell and and then start root. Inside root, one can easily define, submit and monitor a job and examine its results.

  > dialroot
  dialroot: Starting DIAL shell to run root.
  dial: Starting DIAL version 1.20 with configuration atlas.
  ...Many lines omitted...
  root[0]

If the flag -i is included on the command line, then any missing DIAL configuration, example or demo files will be copied into the local directory before root is started. These files must be present to load the DIAL dictionaries and access DIAL classes and services. This is a change from release 1.10 where the flag did not exist and the files were always copied if absent. Typical usage is to supply the flag only the first time dialroot is run in a directory.

From inside of root, one can browse the catalogs, extract objects (applications, tasks and and datasets), create new objects, define, submit and monitor jobs, and examine their results. Use the help() message to redisplay the list of useful commands that appears when your first start up dialroot.

As with the shell command, the ATLAS version and configuration may be explicitly specified on the command line. The usual root options may may also be provided.

If you are in a DIAL shell and do not wish to fetch the configuration or demo files, you may start root in the usual manner:

> root.exe

DIAL provides a rootlogon.C script to load dictionaries and define global variables. If you wish to provide you own startup commands, they may be placed in userlogon.C which is called from rootlogon.C if present.

dladams@bnl.gov