Particle Physics Data System

CS database - energy dependence of cross sections and multiplicities

This is a description of how to extract data compilations on integrated characteristics of particles collisions: cross sections for exclusive and inclusive reactions, mean charged and partial multiplicities of hadrons, produced in hadrons and leptons collisions with various targets.
  • 1. INTRODUCTION.
  • 2. DATA STRUCTURE.
  • 3. DESCRIPTION OF OUTPUT.
  • 4. DATA BASE USAGE.
  • 5. CONCLUSION
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
     

    1. INTRODUCTION.

    The database CS (Cross Sections) includes data on integral properties of particles collisions and is a development and update of the HERA(CERN) compilations [1]. One can find in the CS database the mostly complete set of formaly evaluated data on the topics:

    - total cross sections of exclusive and inclusive reactions (in full phase space, as a rule);
    - data on Re(T)/Im(T) for hadronic forward amplitudes;
    - cross section for GAMMA induced reactions;
    - cross sections for GAMMA GAMMA induced reactions;
    - SIG/E for neutrino induced reactions;
    - mean charged hadrons multiplicities;
    - partial hadron multiplicities.

    The collection of the CS data base and formal evaluation of data have been made in several stages: merging of 1987 HERA(CERN) compilations translated on PPDL (Particle Physics Data Language) with data from old UCRL and LBL compilations.

    In all cases the data were checked with original publications before loading to the CS database. Practically all experimental data points presented in CS data base are repeatedly checked by comparing stored data with data in the original publications.

    Where it was possible the preliminary data were marked with special mark that makes it easy to separate them from final results. Another special key marks the data obtained in not full phase space and/or model dependent data.

    The PPDL language and highly developed program tools give a possibility to establish a strong control of reaction description and, as a result, reduces an amount of wrong descriptors and, in many cases, rejects errors arosing from misprints in journals.

    CS data compilation now updated regularly by data from ReacData (RD) data base [3,5].


    | 2. DATA STRUCTURE. | 3. DESCRIPTION OF OUTPUT. | 4. DATA BASE USAGE. | 5. CONCLUSION |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
     

    2. CS DATA BASE STRUCTURE


    Basic unit of the CS data base under BDMS is a record - a set of data elements connected by hierarchical relations. Each record contains the data belonging to one reaction (RE), one observable (YN) and extracted from one publication (R). Record schema is as follows:

       Biblio     Reaction         Data       Experimental      Service
       graphy    Descriptors      Points       Conditions     Descriptors
      *==============================*=========*==================*======*
      | ||| |  | | | | | | | |    |  |         |   |  | | |     | |  | | |
      SC||| |  RE| | | | | | |   YN  |         |  KIN | |SIG    | |DEN | cr
        ||| |    | | | | | |MODE     |         |      | |       | |    |
        R|| |   REC| | | | |       point       |    CORR|      SB |   DCH
         || |      | | | | |      / | | \     sys       |         |
         D| |     BP'| | |MULT  btm | |  y   /   \    COND        |
          | |        | | |          | |  | csys   \            ___ds__
          TY|       TP'|brv      PLAB |  |      sys-err       /   |   \
            |          |              | ysis                DSA  DSR  dcc
            RR        FSP'          ECM
     
    Key data elements (DE) are in upper case, (') marks the virtual DE, which are created by the program from other data.
    The data elements fall into several categories, depending on the information they contain:
    2.1
    Bibliographic information: SC, D, TY, R, RR.
    2.2
    Reaction description: RE, REC, MULT, MODE, FSP, BP, TP, BRV.
    2.3
    Experimental data description: YN, POINT, BTM, PLAB, ECM, Y. These data elements contain the information about an observable, a value of observable and a values of kinematic variables.
    2.4
    Description of experimental conditions: SYS, CSYS, SYS-ERR, YSYS, COND, CORR. These data elements contains information about systematical errors, corrections and experimental conditions.
    2.5
    Comments to the data: KIN, SIG, CR.
    2.6
    Information on expert data evaluation: DS, DSA, DSR, DSC.
    2.7
    Service data elements: REC-ID, SB, DEN, DCH.

    | 1. INTRODUCTION. | 3. DESCRIPTION OF OUTPUT. | 4. DATA BASE USAGE. | 5. CONCLUSION |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    2.1 Bibliographic Information.

    SC - is short code.
    SC = < first author's first name > < two last digits of the year of publication> . For example: SC = ANTIPOV 88;
    D - is the publication year. For example: D = 1987;
    TY - is the publication type.
    According to the ideology of CS data base, it contains the data points from the journal publications as usual. We have restricted ourselves by this choice, keeping in mind that the journal publications have an additional quality check during the editorial reading. But it is possible to insert into the data base the "hot" data from other sources - preprints, conference proceedings and so on. Following types are allowed:
    JOUR - journal
    PRER - preprint
    CONF - conference
    THES - thesis
    R - is the reference of the publication.
    The format of R for articles from journals: R = < PPDL-abbreviation of journal> < volume> , < page> ;
    For example: R = PR D25, 2231;
    The format of R for preprints:
    R = < PPDL-abbreviation of institute> -< two last digits of the year of publication> -< preprint number> ;
    For example: R = JINR-E1-81-289;
    The format of R for conferences:
    R = < PPDL-abbreviation of conference> , < page> ;
    For example: R = ROCHESTER-60, P. 1128;
    RR - the reference for earlier results, preliminary with respect to those presented in the record. RR and R formats are identical exept for some deviations.

    | 2. DATA STRUCTURE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    2.2 The reaction description

    RE -
    is the reaction code.
    REC -
    is the reaction code without decay brackets. For reactions without resonance production REC is identical to RE.
    MULT -
    is the final state multiplicity of the reaction presented in REC. It is calculated by the applied program for all classes of reactions except for MISC and < XX> PS. For the classes INCL, INRP, SEMI, DSEM, and DSRP data element MULT contains the multiplicity of the detected final state.
    FSP -
    contains codes of particles in final state. The codes of particles produced in resonance decays are not included into FSP. PPDL codes for particles see in [4]. FSP is the virtual key, i.e. it is missing in the record listings, but it is possible to retrieve the record with the given value of FSP.
    Now we have additional possibility of searching with this data element. This means a search of particles with desired properties. Format of this search is:
    FSP < PROP(......);**
    where points represent the property. Sign '< ' indicates mode of operation for query procedures. Next properties are allowed:
    HADRON - no operation allowed
    LEPTON - no operation allowed
    MESON - no operation allowed
    NUCLEUS - no operation allowed
    HYPERON - no operation allowed
    BARYON -
    CHARGED -
    STRANGE -
    CHARMED -
    ISOMUL -
    BEAUTY -
    MASS -
    The meaning of every property is transparent. Every property can have operation (with exeption for first five properties), for example - CHARGED=-2, means particles with charge = -2. Allowed operations are :
    = -
    equal to,
    > -
    grater than,
    < -
    less than,
    < > -
    not equal to.
    Note, please, that the presence of every property in query string means that this property is at least not equal to zero (unless zero explicitly required).
    So, strings
    FIND FSP < PROP(CHARGED< > 0);** and
    FIND FSP < PROP(CHARGED);**
    are identical.
    You can use more than one property in single query. In this case, please, devide them with commas. All properties are considered to be connected by logical AND operation. Some examples of the PROP usage:
    FIND FSP < PROP(HYPERON);** - find all hyperons;
    FIND FSP < PROP(CHARGED< 0,HYPERON);** - find all negativelly charged hyperons;
    FIND FSP < PROP(CHARGED=1,MASS> 2.,MESON);** - find all mesons with mass grater than 2. GeV and charge = +1.
    Note, please ! In the case of ANY contradictions in query THE LAST value is used ! So in the query
    FIND FSP < PROP(CHARGED=1,CHARGED=0,MESON);** mesons WITH CHARGE=0 will be found.
    BP -
    is beam particle code, it is similar to FSP.
    TP -
    is target particle code, it is similar to FSP.
    BRV -
    product of all branchings for decays of final states particles specified in RE. Used to calculate cross sections from Y values with current PDG values for branchings.
    The necessary branching fractions are extracted from the data base (PP) containing particle properties. In records containing the flag SIG=SIG; recalculations not performed.
    The data-element Y contains the value of cross section times the branching ratios of all cascade decays in the final state as usual. The value of BRV then can be used straightforward to calculate the corrected value of the cross section. The user can obtain that corrected value in some modes of the DOCUMENT (as it will be explained later).
    Sometimes it is impossible to find this value in publication: authors give the value of YN corrected for branching. In that case the value SIG for data element SIG then appears.
    If the experiment was carried in such manner that all decay modes of resonance was detected, then the value of RE doesn't contain decay modes. In such a case RE and REC are identical. The information is presented in the same manner if the authors don't give the decay modes but the value of YN is already corrected for branching ratio. In this case the record contains flag SIG. | 2. DATA STRUCTURE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    2.3 Experimental data description

    YN -
    describes the value under consideration and their units as it is given in publication. For example: YN = SIG/E IN FB/GEV;
    POINT -
    is a node data element used to couple the data related to one value of BTM.
    BTM -
    describes the energy variables and their values for beam particle. BTM contains information directrly taken from publication.
    PLAB -
    is the beam momentum in laboratory system (GeV/c). It is presented in the form of a three-component vector: the mean value, left and right boundary of the momenta spectrum. Is calculated by system from BTM. For example: PLAB = 75.,74.,76.;
    ECM -
    is the C.M.S. energy (GeV). The format is equivalent to PLAB. Is calculated from BTM.
    Y -
    is the value of YN for reaction given in RE and for corresponding value of PLAB. It is represented in the form of three-component vector: the value of YN, positive and negative errors. For example: Y=22.,1.,2.;
    The last two components of Y usually specify the statistical error, the systematic error is given separately (see Description of experimental conditions:). But if there is a combined error in publication, consisting of statistic fluctuations and systematics shifts, then this error is specified in Y and the corresponding string appears in the CSYS data element (see Description of experimental conditions:).
    | 2. DATA STRUCTURE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    2.4 Description of experimental conditions

    SYS -
    is a node data element. It is designed to connect together the values and descriptions of the corresponding sources for the systematic errors belonging to all or to the majority of the experimental data points in the record (see the description of YSYS data element).
    SYS-ERR-
    is the value of systematic error expressed in percents. It is presented in the form of a two-component vector: a positive and a negative error.
    CSYS -
    is a comment describing the source of the error specified in SYS-ERR or YSYS.
    If Y contains errors that already include systematic deviations, SYS-ERR is empty and CSYS = INCLUDED. If the systematic error is not given in the publication CSYS = NOT GIVEN. If authors do not give the source of systematic error, but give the value of this error CSYS = UNKNOWN. If authors declare that the errors specified are purely statistical CSYS = STATISTICAL ONLY.
    YSYS -
    is a data element similar to SYS-ERR. It is presented in the case when for some point/points in the record the systematic errors differs from that specified in SYS-ERR. Therewith the value of systematic error common for the majority of the points in the record is stored in SYS-ERR.
    CORR -
    is the description of the corrections applied by authors during handling and analyzing data.
    COND -
    is the description of experimental conditions (incomplete geometry of the experimental set-up, cut-offs etc.) Including also the corrections not taken into account by the authors but considered to be important according to the opinion of the encoder.
    | 2. DATA STRUCTURE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    2.5 Comments to the data

    KIN -
    describes the unusual for CS data base data:
    KIN
    = FORW; - forward scattering,
    = BACK; - backward scattering,
    = UL; - upper limit on cross section,
    = LL; - lower limit,
    = PD; - preliminary data,
    = OM; - order of magnitude,
    = RDB; - data were taken from data base ReacData without second checking according to publication,
    = CALC; - points were calculated from the data presented in the given publication with the help of additional information.
    SIG -
    is used to mark records in which the cross section value has been corrected for branching. If the correction has been made by the authors of the publication SIG = SIG. If it has to be made by applied program SIG = CORR. If for some reasons the cross section value can not be corrected for branching this element is not included into the record.
    DS -
    (Data Status) - expert flag of "reliable" data. It has the form DS = < Expert code = latin initials > . All authors that have used these data in some analysis can be considered as experts. The value DS = -< Expert code> means that expert gives the negative judgement on these data (see DSC).
    DSA -
    first author's name. Is analogous to SC.
    DSR -
    reference to the publication with expert evaluation, in the format of R.
    DSC -
    < Data Status Comment> - comment to the data. Contains the description of transformations that must be made to convert the data presented to be a part of basal set of data, and/or expert judgements on the data.
    CR -
    is the comment for the record as a whole. It appears in the case when the above record structure does not make it possible to present the information from the publication appropriately. It also contains the necessary explanation to the record.
    | 2. DATA STRUCTURE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    2.7 Service data elements

    REC-ID -
    is a record number assigned by the system when stored.
    SB -
    code of responsibility of the encoder. For example: SB = ENCODED 31 JUN 1980 BY SIA;
    DEN -
    is encoding date.
    DCH -
    is last edition date.
    | 2. DATA STRUCTURE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
     

    3. DESCRIPTION OF OUTPUT

    To output the information stored in compilation a user can utilize both standard facilities of the BDMS (commands PRINT, DUMP, LIST) and those supplied by the applied programs (command DOCUMENT). Using the command DOCUMENT one can get several types of output specified by MODD,< number> command, which must be issued before DOCUMENT command.

    The output by

    MODD,1

    is a catalogue of the reactions available in the current set.

    A part of the listing relating to a single reaction has two lines: the first one specifies the parameter as follows: the reaction code, the masses of beam and target particles, the reaction threshold for the momentum in laboratory system and for the center of mass system energy (all in GeV) ,multiplicity in the final state and the data element YN. The second line specifies the number of points for a given reaction in the current set.

    MODD,2

    In addition to the above output contains also the lines describing the experimental points. These lines follow one describing the reaction. The experimental points are ordered according to the beam momentum.

    One line corresponds to one experimental point and contains the following information: the mean value, the right and left boundaries of momenta spectrum, the same parameters for the energy in c.m.s. (all in GeV), the YN value, the negative and positive errors, warning comment, systematical errors in percents, SC of the record and reference to the publication.

    The warning comment is the symbol "W". It appears in the next cases:

    -
    there are data elements COND or KIN in the record (exept for KIN = RDB; and KIN = CALC;);
    -
    the data element SIG is absent or equal SIG.

    In the case when KIN = RDB; or KIN = CALC; the warning comment equals "R" and "C" respectivelly. The output according MODD,2 is acceptable by the system ATLAS [8].

    MODD,3

    gives the fullest information about the record. As a kinematical variables PLAB and ECM are used. The value of YN is corrected for the current PDG branching ratio value from BRV.

    If authors have corrected the value of YN on branching and this fact is marked by encoder in the data element SIG, then the line

    CORRECTED BY AUTHORS
    appears in the output for given record.

    If for some reasons the correction haven't been made then the line

    UNCORRECTED
    appears in the record.

    The type of output according to MODD,4 is equivalent to the MODD,3 except the value of YN not corrected for current value of branching ratio. This mode is convenient in checking data.

    If SET that have been formed by the user contains the information belonging to one reaction only, it is strongly recommended to use outputs MODD,5 and MODD,6 instead of MODD,1 and MODD,2 respectively. They are complitely identical but are at least ten times faster.

    MODD,7

    Technical format of output to be used in the procedure CSBOOK. Equivalent to MODD,6 with additional outputted lines that describes the decay brackets of decaying particles.

    MODD,8

    Produces the output in the format of CERN-HERA compilations.If the particle(s) in final state have been observed in a particular decay mode(s) it will produce two lines for a single entry - one with corrected cross section and another with uncorrected.

    MODD,9

    Produces the output equivalent to one of ReacData data base in the MODD,2 grouped according to reactions.

    MODD,10

    Equivalent to MODD,9. Should be used if the set to be output contains the records with unique reaction. Is at least an order faster than MODD,9

    MODD,11

    Equivalent to MODD,2. Supresses the output of PLAB value and gives the overall systematic and individual errors as separate entries.

    MODD,12

    Equivalent to MODD,11. Should be used when the selected set contains the records with the same reaction.


    | 1. INTRODUCTION. | 2. DATA STRUCTURE. | 4. DATA BASE USAGE. | 5. CONCLUSION |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    4. DATA BASE USAGE

    An access to the data base CS in the VMS media is given by PPDS macro-command. A powerfull internal help on the BDMS system (commands: ?, ??, ?< command>) and on the data base itself (commands: HELPBASE, FDT, INDEX, GUIDE) give a possibility to become familiar with BDMS system and data base in a short time.

    Access to BDMS for interactive work with CS data base:
    PPDS CS
    System invites user to type BDMS commands:
    CS:READ:EXEC>
    Online help on BDMS commands of data retrieval and manipulation
    ? - list of BDMS commands;
    ?? - list of BDMS commands with short description;
    ?< command> - command description.
    Data base overview:
    HELPBASE - online handbook on data base, with key access to the sections;
    FDT - display the data base structure;
    INDEX,< KDE> - index of Key Data Elements;
    Retrieval and list of the data:
    The retrieval condition on the data, for example, on cross section for the reaction PI- P --> N PI+ PI- must be as follows:
    FIND RE=PI- P --> N PI+ PI-; AND YN=SIG;**
    System then creates a current SET of the data. It is useful to use commands INDEX/SET,< params> and LIST,< params> to investigate the content of the set.
    LIST - list of the current set on the screen;
    Output of the data into external files:
    PRINT - output of the current SET into file CS.PRN in the format of LIST command;
    DUMP - output of the current SET into fide CS.DUM in the format that is acceptable by BDMS;
    DOCUMENT - output of the current SET into file CS.DOC in the format set previously by the command MODD.
    The main mode of output is MODD,2. With the command :
    MODD,2 DOCU
    all data from the current SET will be presented as compilation ordered by reactions and momentum.
    There is a possibility to produce a well-to-see compilation of tables and graphs with the help of CSBOOK system (all consultations available from data base manager).
    To finish work with BDMS type STOP.
    | 1. INTRODUCTION. | 2. DATA STRUCTURE. | 3. DESCRIPTION OF OUTPUT. | 5. CONCLUSION |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    5. Conclusion

    Describing compilation contains now about 21500 records, that corresponds to about 45000 experimental points. All records except for very little part were checked by COMPAS group (IHEP). All these record have data element SB.

    In the future we plan to maintain the data base with the help of PPDS's data bases DataGuide (DG) and ReacData (RD) with additional checking of the records against publications whenever it is possible.

    We plan also future development of the data base in some directions: rejection of errors in data presentation, construction of "the basal data sets" with the help of expert evaluations published elsewhere and stored in the data elements DS, DSA, DSR, DSC, new possibilities in data manipulation.

    All criticism on quality of data base, proposals on future development will be accepted with pleasure and used in our work.


    | 1. INTRODUCTION. | 2. DATA STRUCTURE. | 3. DESCRIPTION OF OUTPUT. | 4. DATA BASE USAGE. |
  • | go to CS database home page | go to CS advanced search page | Return to PPDS home page |