The first step in using the D0 software is to define the release in which you will work. At present D0 is making weekly releases with names of the form t01.xx.00 where xx is a number which increments each week. For the purpose of the following example, I will use xx = 07.
If you want a current release you are usually best off with the one from the preceeding week. The current week's build will dissappear and reappear on a nightly basis. On the D0 machines, releases are deleted after a few weeks.
There are also well-tested and long-lasting production releases (pmc* for Monte Carlo, psim* for d0sim, preco* for reco). These are stable but often badly out of date.
On d0mino, you must first specify that you want to make use of the n32 (new 32-bit) libraries. Use the following command:
> setup n32
On any machine, you can specify the release and set up the run II software with the command
> setup D0RunII t01.07.00Subsitute the desired release name for t01.07.00 on this line.
If you want to use an optimized (one for which compiler optimiztion has been enabled), you must add a qualifier. For example:
> setup D0RunII t01.05.00-maxopt -O SRT_QUAL=maxopt
This will define the run II release and many associated products such as KCC, python, paw and root. You should not set these up separately either before or after the run II setup because you may cause conflicts.
If the command setup is not found then you need to set up setup. Ask someone for help or poke around in the login files of advanced users. This should not be neccessary on D0 machines.
You can set up a new release by issuing another setup command but this often does not work. It is best to log in again and start from scratch.