Titles Banks and Files

The fundamental interface between the user and SNOMAN is the titles bank. It is these banks that contain all the information that SNOMAN reads to tell it what to do and what the detector looks like. For a complete description of all titles banks see:-

Companion/Titles Banks

Most of these banks are in the database see section 3.8, but they can also be stored in a number of titles files. The companion tells you in which file each bank is to be found.

To take a concrete example, look at the JOB bank, which can be found in the titles file JOB_CONTROL.DAT. You could control SNOMAN by editing this file. For instance, to run 200 events rather than 100 you could change the 100 to 200 on the line that controls the number of events. However it is NOT a good idea to start changing standard files, it is far better to create a new file, say MY_TITLES.DAT and copy any titles banks you want to it. Now you can change them in any way you want and then run SNOMAN and give the commands:-

titles my_titles
@run

This tells SNOMAN to read the file MY_TITLES.DAT (.DAT is the default extension for titles files) and then read the command file RUN (.CMD is the default extension for command files) which tells SNOMAN to read all the other titles files it needs and to start execution. If SNOMAN finds 2 versions of some titles banks it resolves the ambiguity in favour of the first, so the golden rule is:

Make sure your titles banks come first.

You are free to organise you private versions of titles banks into titles files in anyway you please, either grouping them together or putting each in a separate file. If you find the number of commands you have to type is starting to become tedious then you can put them all into a file, say MY_COMMANDS.CMD, including the @run, and then run SNOMAN simply by typing:-

@MY_COMMANDS