Section5

Section 5: Setting up a new production

This document contains instructions for setting up a new uDST production. The production manager should do:

(1)	-	create the uDST production directory structure by executing the make_production_area.sh shell script in the general/script subdirectory. When executed, this script expects that the following environment variables exist: UDST_ROOT : the uDST root directory, e.g. for setting up the 97b4 production, this variable was set to: /data01/opa/udstprod/udst_97b4 UDST_VERSION : the uDST version, e.g. for setting up the 97b4 production, this variable was set to 97b4 DATA_YEAR : the data year, e.g. for setting up the 97b4 production, this variable was set to 1997 As this script execute, it produces output describing each directory, file, or symlink which it creates. For this reason, it is a good idea to catch this output in a file for later checking.
(2)	-	Install and compile the source code for the production. At present, the production expects that the udst_source_code directory tree exists and contains the executable codes used in the production.
(3)	-	Check that the various ASCII input files in the production are available.
(4)	-	Make a new fill.conf file for the production and store it in the config subdirectory in the production area. To avoid inavertently renumbering the fills, it is best to copy the fill.conf file from the previous production and modify the fields so that it is useful for the new production.
(5)	-	Make a new disk.conf file for the production and store it in the config subdirectory in the production area.
(6)	-	Make a new udst.conf file for the production and store it in the bin subdirectory in the production area. Usually, it is best to take a version of this file from a previous production and modify it for the new production because it is typically only necessary to update "compath" entry.