gibuu is hosted by Hepforge, IPPP Durham
GiBUU

TABLE OF CONTENTS


/PIL_FormInfo [ Modules ]

[ Top ] [ Modules ]

NAME

module PIL_FormInfo

PURPOSE

cf. module PIL_nLead

Provide some storage method for a integer valued information connected to a particle characterized by its unique particleNumber.

This is closely connected to the module PILIndex

The stored information is a flag connected with string fragmentation:

   EArr(2,...) + 10 * EArr(3,...) + 100 * nLead

(cf. GetJetSetVec.f)

EArr(1,...):

  • 0: hadron has not been processed
  • 1: everything should be ok (in principle)
  • 3: next to last hadron in fragmentation
  • 4: last hadron in fragmentation

EArr(2,...):

  • 1: problems with ProdTime 1 ; additive
  • 2: problems with ProdTime 2 ; additive
  • 4: problems with FormTime ; additive

Values can be tested by the intrinsic f77-function IAnd(...,1|2|4).

EArr(3,...):

  • 1: hadron from QQ-String
  • 2: hadron from QQ-String with internal Gluons
  • 3: hadron from pure gluonic GG-string
  • 4: hadron from Cluster-Decay -> 1 hadron
  • 5: hadron from Cluster-Decay -> 2 hadrons
  • 6: hadron from Doku-Line

EArr(4,...): number of the string

EArr(5,...): Rank of the particle, like it was calculated

EArr(6,...): rank as the minmal number of particles to the left or right (plus 1). (reverse ordering is considered)

NOTES

  • "PIL" stands for "PartInfoList"


PIL_FormInfo/FormationVals [ Types ]

[ Top ] [ PIL_FormInfo ] [ Types ]

NAME

type FormationVals

PURPOSE

a container of the information to be stored

SOURCE

  type FormationVals
     integer :: val
  end type FormationVals

PIL_FormInfo/IndexList [ Global module-variables ]

[ Top ] [ PIL_FormInfo ] [ Global module-variables ]

PURPOSE

The list, were the particle numbers are connected with the (physical) storage position

SOURCE

  type(tIndexList),save :: IndexList

PIL_FormInfo/ValueList [ Global module-variables ]

[ Top ] [ PIL_FormInfo ] [ Global module-variables ]

PURPOSE

The list, were the information is stored

SOURCE

  type(FormationVals),save,  allocatable :: ValueList(:)

PIL_FormInfo/PIL_FormInfo_DeAlloc [ Subroutines ]

[ Top ] [ PIL_FormInfo ] [ Subroutines ]

NAME

subroutine PIL_FormInfo_DeAlloc

PURPOSE

Deallocate the memory for this list and the corresponding index list.


PIL_FormInfo/PIL_FormInfo_ZERO [ Subroutines ]

[ Top ] [ PIL_FormInfo ] [ Subroutines ]

NAME

subroutine PIL_FormInfo_ZERO()

PURPOSE

Reset the list by setting the counter of stored information to 0. No allocation or deallocation of memory happens.


PIL_FormInfo/PIL_FormInfo_PUT [ Subroutines ]

[ Top ] [ PIL_FormInfo ] [ Subroutines ]

NAME

subroutine PIL_FormInfo_PUT(number,r)

PURPOSE

Store the information "r" connected with particle "number" in the list.

INPUTS

  • integer :: number -- the (unique) particle number
  • integer :: r -- the information to store

OUTPUT

none


PIL_FormInfo/PIL_FormInfo_GET [ Functions ]

[ Top ] [ PIL_FormInfo ] [ Functions ]

NAME

logical function PIL_FormInfo_GET(number,r)

PURPOSE

Get the stored information of particle "number"

INPUTS

  • integer, intent(IN) :: number -- the (unique) particle number

OUTPUT

  • integer, intent(OUT) :: r -- the stored information (or .false.)
  • the (logical) return value signals, whether inforation about this particle was found in the list or not.


PIL_FormInfo/PIL_FormInfo_Allocate [ Subroutines ]

[ Top ] [ PIL_FormInfo ] [ Subroutines ]

NAME

subroutine PIL_FormInfo_Allocate

PURPOSE

Do the allocation and reallocation of the value vector. The new size is taken from the size of the IndexList vectors.

NOTES

For security one should insert here checks, whether the memory allocations failed and stop execution in these cases.


PIL_FormInfo/PIL_FormInfo_Print [ Subroutines ]

[ Top ] [ PIL_FormInfo ] [ Subroutines ]

NAME

subroutine PIL_FormInfo_Print(file)

PURPOSE

Print the list to file