Input and Output Files

To run SNOMAN you require the following input data files:-

Command File

As part of the initialisation SNOMAN reads commands from the standard input. Further commands can be stored in files and SNOMAN instructed to read them by typing:-

@command_file

PEGS File

e.g. PEGS4_10.DAT (which holds the cross-section information for EGS4, mess with it at your peril and only if you understand what you are doing).

Titles File

All the control input to SNOMAN is through the titles banks discussed in section C.3. These may come either directly from the database, see section 3.8 or from titles files. During initialization banks from these sources are loaded as required. If the database is installed only a minimal set of titles files are required.

If the standard installation procedure has been followed, you will find a complete set of data file (.dat and .cmd) on the directory:-

...snoman/n_nn/prod

IMPORTANT:-

Only take copies of those files you want to modify; when SNOMAN is asked to load a titles file it automatically searches the following directories for any command and data files:-

1. If looking for the titles file sdb_table.dat try $CDSERV
2. current directory
3. the mcprod dir
4. the prod dir
5. the code dir

So set the default directory to some private directory where you want SNOMAN to write its output.

SNOMAN produces the following output files:-

• RSEED.DAT which is the file to which the event number and starting seed are written at the beginning of each event in case of a crash.

• HBOOKSM.NTP which contains the SNOMAN histograms.

• SNOMAN.LOG or SNOMAN_LOG.nnnnnn which is a log file containing a complete record of the job. To help you find your way around this rather long file, it is divided into 6 sections:-
  • Initialisation Phase. Part I (Core SU Initialisation)
  • Initialisation Phase. Part 2 (Reading Commands & Titles)
  • Initialisation Phase. Part 3 (Context Setting)
  • Initialisation Phase. Part 4 (Active SU Initialisation)
  • Execution Phase.
  • Termination Phase.

  At the end of the job you will find information telling you:-

  • How much of the ZEBRA memories were used.

  • How many ZTELL IDs were reported. These are conditions that were reported to ZEBRA. Some are errors, but IDs greater than 800 are just vetos e.g. insufficient light to trigger. More information on ZTELL IDs can be found in the Error Handling section of the Programmer's Manual.

  • The CPU time used.