Setting up a new uDST production
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 [auxiliary_scripts.html#make_production_area.sh make_production_area.sh] shell script in the general/script subdirectory. When executed, this script expects that the following environment variables exist:
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 [udstd_files.html#fill.conf 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 [udstd_files.html#fill.conf fill.conf] file from the previous production and modify the fields so that it is useful for the new production. | |||||||||
| (5) | - |
Make a new [udstd_files.html#disk.conf disk.conf] file for the production and store it in the /config subdirectory in the production area. | |||||||||
| (6) | - |
Make a new [udstd_files.html#udst.conf 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. |