Account setup for CMSIM

I added these lines to my .cshrc file:

  setenv CMS_PATH  /usr/cmsim/cern
  source $CMS_PATH/setup/cshrc
  source $CMS_PATH/setup/group_env_CMS.csh
  setenv SCRATCH /export/home/scratch
  echo Using $SCRATCH for the scratch area
  setenv CVSCOSRC  $CERN_ROOT/src
  setenv LIB       $CERN_ROOT/lib
  setenv DOC       $CERN_ROOT/doc
  setenv LOG       $CERN_ROOT/log
  setenv CERNLIB   $CERN/pro/lib
  setenv CERNBIN   $CERN/pro/bin
  set path= ($path  /usr/cmsim/bin $CERN/../cvs/v1_9/bin $CERN_ROOT/bin 
             $CERN_ROOT/mgr)

Important additional notes:

1. Make sure you have the software appropriate for your platform!
2. Some of the commands used by GEANT are very similar to those used by PAW. Thus, in your .pawlogon.kumac you must write out the full command. i.e. instead of alias/create you must use kuip/alias/create. To be safe, use the full command for everything. See the PAW manual or type
   PAW> usage <function-name>
   for the full command name.
3. CMSIM has some fairly general options set. One of them is the name of the input file to be used for commands. It expects a file named fort.4. It is best to make a symbolic link between the file you actually want to use and fort.4 to reduce the chance of overwriting a wanted file. To make a symbolic link, type
   % ln -s file.ttl fort.4
   where file is the name of file you wish to use.
4. Each keyword in the title file (actually only some, but many) give an ntuple: KINE, RHIT, HITS, TRIG, DIGI, VERT, HEAD, etc. Note that some of these are not usable by mere mortals and must be run through some code to make them consumable. See the DØ web pages for full details. We are working on providing a much more complete list of what each keyword does, what ntuples are filled, etc.
5. The title files (.ttl) have information about what to use for the detector setup, such as cmsp0.ttl or cmsv112.ttl. The first is a file that is for a test beam and the second is the current version of the full blown detector.
6. We have some sample .ttl files that you can use. These are for two test beam chambers, p0 and p1. After you set up all the software, you can find the ones being used in the directory $CMS_BIN.
7. When opening a .rz file inside PAW you have to use 0 as the record length.
8. Some of the ntuples cannot be easily interpreted by humans and need to be run through some FORTRAN code first. For example, digi.f examines the ntuples 400 and 900 and makes histograms. To plot these histograms, use digi.kumac. To load the ntuples into memory, you have to print out one of the ntuples (any) before you can run the COMIS routine. Type
   PAW > ntuple/print n
   where n is the number of your favorite ntuple. To use digi.f, you must open the .rz file within PAW (see note 4!) and then type
   PAW > call digi.f(0)
   where the 0 indicates the starting event. Next,
   PAW > cd //pawc
   And finally list, plot and print the histograms as you desire.
9. When using the CFIL keyword to specify input or output files, you must have a trailing space:
   cfile 'Det1' 'name '