Farmer's Guide to D0 Monte Carlo Production

Introduction and Contents

1. The Monte Carlo Production Collective
2. D0Geant Requests and How They're Handled
3. Communication Among the Farmers and Your WWW Status Page
4. File and Tape Handling: FATMEN
5. Software Details

Here's a link to the D0 Monte Carlo Production page.

1. The Monte Carlo Production Collective

Participation in the Collective is a service task. (Don't tell anyone, but it's a very easy service task which maximizes institutional recognition and minimizes actual work, just your style, eh?) As a service task it allows institutions to play a more direct role in a much wider set of analyses than usually possible.

2. D0Geant Requests and How They're Handled

1. Physicists performing analyses arrange to have their requests made by their physics group OCPB representative. The OCPB representative then use the WWW to fill out a request form. The URL of the DØGeant request form is
   http://www-hep.uta.edu/stephens/d0/geant_mcform.html
   The form is fully annotated.
   
2. The form is then mailed ot the Coordinator who copies it to a directory on the D0FS cluster:
   D0FS::USR$ROOT21:[D0GEANT.REQUEST.OCPB]
   If there is a backlog of requests, they are reviewed by the OCPB which sets priorities.
   
3. Given these priorities, the Coordinator then requests specific CPU farms to take on a given job. The farms then interact with the person who made the request to arrange the details of file/tape delivery.
   
4. To keep tabs on requests, there are four different directories on D0FS:
   D0FS::USR$ROOT21:[D0GEANT.REQUEST.ocpb/todo/inpr/done]
   each request has its own file, referenced by the "order number" (which is assigned when the request is made) and the nine character file descriptor. The files first appear in the OCPB directory, then in the TODO directory after OCPB review, then when a farm has accepted the request, the file is moved to the INPR directory during production, and finally it is put in the DONE area after production has completed. The D0FS directories can be accessed through the MC Production web page.
   

3. Communication Among the Farmers and Your WWW Status Page

Let me reiterate. The web status page is extremely important to both the Requestor and the Coordinator. The Coordinator needs to know when a job is finished so that s/he can shuffle the request form to the [...done] area on D0FS and so s/he will know that the given farm may be available for another production job.

It would also be nice to have a link from the D0 Monte Carlo Production page to a more formal farm page in addition to the status page.

4. File and Tape Handling: FATMEN

There's more information in D0Notes 1744 and 2403.

4.1 FATMEN: File Naming

1. GRP = three characters for the physics group:
   • MUB
   • NEW
   • QCD
   • TOP
   • WZX
2. EVENTTYPE = nine character Requestor assigned description of events;
3. SIMUL = five character description of event generator including version number, e.g. IS714 = isajet 7.14;
4. DETCSIM = Geant version and showering parameter, e.g. G315TS5 for D0GEANT version 3.15 and SHWG 5 or G314SS0 for version 3.14 and SHWG 0.
5. A = one alphanumeric descriptor the requestor can choose for organizational purposes - called the tape descriptor;
6. nn = two digit file number;
7. EXT = X_RAW01 ==> eXchange format, raw data output.

NEW_S200G300_IS714_A_01.ISA

NEW_S200G300_IS714_G314SS5_A_01.X_RAW01
               for Geant V3.14, 
                    SHWG 5, 
                               eXchange format, 
                                  RAW geant output.

TOP_TTLL170XS_HW057_A_20.ISA

This is pretty straightforward, but it gets quite a bit more involved when we start running D0RECO on the Monte Carlo output.

4.2 FATMEN: Tape Writing and Labeling

• UUCnnn - University of Maryland
• UUDnnn - University of Texas at Arlington
• UUEnnn - Florida State University
• UUFnnn - Northern Illinois University

4.3 FATMEN: RCP Catalog File creation

5. Software Details