Run II SUSY/Higgs Workshop: Local Tools

The common tools are on the project disk, /prj_root/733/higgs2_1 on the challenge machines. To use any of the code below, you should first do

cd /prj_root/733/higgs2_1 source setup.csh newgrp higgs2_write
This defines a set of logical names needed by makefiles when linking executables. Members of the higgs working group should put your analysis-specific code in your directory in /prj_root/733/higgs2_1/analysis. If you do not have a directory there, please send mail to John Hobbs. Other groups should see their contact people for any common information

Higgs Decays

-- See the program HDECAY referenced on the Fermilab working group page (above). A local version of the program has been set up in d0chb:/prj_root/703/new_2/run2/higgs/hdecay. For more information on the local version, contact Anna Goussiou.

Event generator

- A version of Pythia 6.03 has been linked. Instructions and the executable are available in d0chb:/prj_root/733/higgs2_1/pythia. This version is similar to the standard DØ version except that

It is version 6.03
In addition to producing Zebra output, STDHEP output suitable for reading into the analysis skeleton, shw or mcfast is also written.
Instead of reading the .rcp files, the run is controlled by two text files, pythia.run and pythia.cards. The first contains parameters related to the number of events and diagnostic output. The second contains standard pythia cards. If you have .rcp files, you can convert them to a .run and .cards file by running the program convert.py found in the pythia/RUN_FILES directory. By using this format, the same control files can run both PYTHIA and SHW (below).

This executable was linked by John Hobbs.

SHW, a Fast Smearing Monte Carlo

The program SHW has been developed for use by the working groups. A DØ standard set up exists in /prj_root/733/higgs2_1/shw. More instructions can be found in this directory. Brief instructions are provided below. To use this for analysis, do the following:

Copy GNUmakefile from the source directory into your own directory
Make your own analysis code in user_analysis.f. See the example in the source directory.
Do 'gmake exe' in your own directory. This builds an STDHEP reading version, a pythia-generating version and an isajet version of SHW.
Reading STDHEP files
1. Make a soft link to the input data (for shw_file), via 'ln -sf the_data_file_true_name my_pythia_file.shw'
2. Run shw by typing 'shw_file'
Generating Pythia within SHW
1. Make soft links to the input .run and .cards files (above) via 'ln -sf the_run_file_true_name shw_pythia.run' and 'ln -sf the_cards_file_true_name shw_pythia.cards'
2. Run shw by typing 'shw_pythia'
Generating Isajet within SHW
1. Make soft links to the input .run and .cards files (above) via 'ln -sf the_run_file_true_name shw_isajet.run' and 'ln -sf the_cards_file_true_name shw_isajet.cards'
2. Run shw by typing 'shw_pythia'

The d0 pjets routines (below) are called parton_jets and particle_jets and the jet flavor tagging routine is called jet_flavor.

Simple Analysis skeleton

- Pythia analysis skeletons for both the stdhep and zebra formats are in d0chb:/prj_root/733/higgs2_1/skeleton. See the file 000-README.TXT for instructions.

Run II Trigger Simulator

- See the Upgrade trigger web page for information regarding the run II trigger simulator

Fast Monte Carlo

- McFast is the suggested fast Monte Carlo for tagging studies. Maria Roco has provided directions for its use.

Geant-based Simulation

TBA, John Womersley

Utilities

Utility routines are in /prj_root/733/higgs2_1/utility and compiled into the library libutils.a in the same directory. The default makefiles include this library in the link command.

PJETS The parton-level (pjcone) and particle-level(Pjpart) zebra PJETS routines have been converted to run on STDHEP format. The names are PARTON_JETS and PARTICLE_JETS respectively. The default settings veto only neutrinos and muons from the jets. The list of veto particles can be modified while your code runs using routines in the file is_vetoed.for in the skeleton directory. The same routines are included in generator_jets.f in the shw directory. The packaging was modified for inclusion in standard shw.
PJET flavor The flavor of a PJET found with the above code can be determined by using the integer function JET_FLAVOR(ipjet).
B tagging routine Maria has provided a b-tag function based on her studies of higgs and ttbar events. It provides the b-jet, c-jet and light flavor tag probabilities for the vertex tagging algorithm she uses. The call is:
```
     tprob = tagprob(jetpt,jeteta,jetphi,true_flavor,tag_flavor)
```
See the routine /prj_root/733/higgs2_1/utility/tagprob.f.

Storing large files

Our project disk space is critically small. Please consider this when running jobs. If the MC generation is fast, consider running the pythia+SHW or pythia+user_code versions and store no intermediate output. For slow data sets which produce significant output, the output should be stored on fmss and the local disk used sparingly. The following are instructions for using fmss from Eric Flattum. Date: Wed, 1 Jul 1998 9:09:09 -0500 (CDT) From: Eric Flattum FNAL To: hobbs CC: FLATTUM@D0PHY1 Subject: RE: Using FMSS? Hi, If there is space, the following are most of the commands I use. The commands should be fairly transparent to a unix person. d0chb> setup d0chb> fmss help d0chb> fmss ls mss:e740/susy/ - simple dir of a directory d0chb> fmss activity - tells you what's happening with the system d0chb> fmss cp disk:./my_file.dst mss:e740/susy/my_file.dst - how to copy a file to mss, and you need to say 'disk'. It's not some type of 'logical' d0chb> fmss cp mss:e740/susy/my_file.dst disk:./my_file.dst - how to copy a file from mss That's about all I ever needed. Eric

John Hobbs

Last modified: Tue Jun 9 17:05:02 CDT 1998