Adding Luminosity data to SU database

Vn 1.0; 01-May-97, J.E.Conboy

The following proposal is for a simple ( quick ? ) method of storing luminosity data in the SU database. It is intended to enable the luminosity to be updated rapidly after new data is taken, or old data reRoped, and may not be adequate for final high statistics results.

Directory structure

Dirtectory names will be of the form 
            /SUOF/LUddXxxPpp
   eg       /SUOF/LUFDX07P02
where
dd
is a subdetector name {FD,SW,EE}
xx
is the experiment number {1:.. }
nn
is the pass ( ie reRope ) number
Each record in a subdirectory is identified by an array IPV giving a valid range of Expt, run and event number ( usual OPCAL convention )

The 'subdetector' MH could be used to store the TKMH cross section.

Data banks

The first 4 words of each data bank are defined as follows :-
  1. Ibit, the event type for which the luminosity is returned - { 1,2,3, 36,38,39, 50 } for { LUET,LUEM,LUCU, SWIA,SWIR,SWIL, WABB }
  2. Ebeam, the beam energy {0.:200.}
  3. Xsec, the cross section in nb
  4. DXsec, the systematic error on Xsec to be added ( in quadrature ) to the calculated statistical error.
Additional words may be used as required for each subdetector.

Access routine

Data may be retrieved by a call 
      CALL SULUDB( CSUBD, IBIT, EB, XS, DXS, IERR )
where
CSUBD*2
is the subdetector name
IBIT
is the event type for which the cross section is required. If zero, the nearest match in EB is found, and the actual event type is returned in IBIT
EB
is the required beam energy. If zero, get current energy from IUHEAD. On return, EB contains the energy for which the cross section has been calculated
XS
is the cross section from word 3 of the selected data bank
DXS
is the error from word 4
IERR
is returned as 0 if successful
The closest matching record for the requested value of Ebeam will be returned; the search may be restricted to a single event type if IBIT is non-zero on input.

The SUOF/LU.. subdirectories are searched in increasing order of pass number, starting with IPASS equal to the pass number of the data read ( as returned by SUPASS ). If no directory for pass .GE. current pass exists, the highest available pass is used. If the pass numbers are not uniform throughout a year ( eg 1996 ) , it may be necessary to insert the same Luminosity data in different ( pass ) subdirectories to be sure of using the correct luminosity.

Creating the data structure

A stand alone utility SULUUP to transform a TZ ( cards ) file into the appropriate SUDB subdirectories is available. The input data file ( for 1996 FD luminosity ) looks like this :- 
*PRINT
*--     Example data file for SULUUP ; 1996 FD Luminosity

*DO    LUUP   1  -iI  -n9
  "J. E. Conboy    "
  "SULU/FD Expt 7      "
*--   1   2   3   4   5

 
*--    p77-79  PASS 1-3 -------------------------------------*
 
*DO    LUHD  1  -iI  -n7 
     3  7 7000 1 7 7469 999999

*--    On peak Xsec from p77, p80 + p70 ( reRoped ) , Cf TKMH

*DO    FDCU  1  -i(1I3F) -n4
  3  45.55  12.459  0.125

*DO    FDCU  1  -i(1I3F) -n4
  3  82.50   3.904  0.08 

 
*--    p77-79  PASS 4,5 -------------------------------------*
 
*DO    LUHD  1  -iI  -n7
     5  7 7000 1 7 7469 999999

*DO    FDCU  1  -i(1I3F) -n4
  3  45.55  12.459  0.125

*DO    FDCU  1  -i(1I3F) -n4
  3  82.50   3.837  0.038

*DO    LUHD  1  -iI  -n7 
      5 7 7515 1 7 7999 999999

*DO    FDCU  1  -i(1I3F) -n4
  3  45.55  12.459  0.125

*DO    FDCU  1  -i(1I3F) -n4
  3  82.50   3.837  0.038

 
*--    p80-81  PASS 1-2 -------------------------------------*
 
*DO    LUHD  1  -iI  -n7 
     2  7 7515 1 7 7999 999999

*DO    FDCU  1  -i(1I3F) -n4
  3  45.55  12.459  0.125

*DO    FDCU  1  -i(1I3F) -n4
  3  82.50   3.837  0.038
NB:
  1. The bank LUUP contains OC logging information and must be present
  2. The banks LUHD contain pass number and the IPV arrays
  3. The first 2 characters of the data banks must correspond to a recognized luminosity subdetector. Each such bank is stored in the location defined by the previous LUHD bank
  4. Data from different subdetectors can not be stored after the same LUHD bank
  5. Updating different subdetectors with a single run of SULUUP may work, but is not supported.
jec@hep.ucl.ac.uk