We present the system for versioning two packages: the TAUOLA of tau lepton
decay and PHOTOS for radiative corrections in decays. The following features
can be chosen in automatic or semi-automatic way: (1) format of the common
block HEPEVT; (2) version of the physics input (for TAUOLA): as published, as
initialized by CLEO collaboration, as initialized by ALEPH collaboration (it is
suggested to use this version only with the help of the collaboration advice);
(3) type of application: stand-alone, universal interface through HEPEVT,
interface for KKMC Monte Carlo; (4) random number generators; (5) compiler
options.Comment: nine pages, late

Golonka, P.

Richter-Was, E.

Was, Z.

English

arXiv

We present the system for versioning two packages: the TAUOLA of tau lepton decay and PHOTOS for radiative corrections in decays. The following features can be chosen in automatic or semi-automatic way: (1) format of the common block HEPEVT; (2) version of the physics input (for TAUOLA): as published, as initialized by CLEO collaboration, as initialized by ALEPH collaboration (it is suggested to use this version only with the help of the collaboration advice); (3) type of application: stand-alone, universal interface through HEPEVT, interface for KKMC Monte Carlo; (4) random number generators; (5) compiler options.We present the system for versioning two packages: the TAUOLA of tau lepton decay and PHOTOS for radiative corrections in decays. The following features can be chosen in automatic or semi-automatic way: (1) format of the common block HEPEVT; (2) version of the physics input (for TAUOLA): as published, as initialized by CLEO collaboration, as initialized by ALEPH collaboration (it is suggested to use this version only with the help of the collaboration advice); (3) type of application: stand-alone, universal interface through HEPEVT, interface for KKMC Monte Carlo; (4) random number generators; (5) compiler options.We present the system for versioning two packages: the TAUOLA of tau lepton decay and PHOTOS for radiative corrections in decays. The following features can be chosen in automatic or semi-automatic way: (1) format of the common block HEPEVT; (2) version of the physics input (for TAUOLA): as published, as initialized by CLEO collaboration, as initialized by ALEPH collaboration (it is suggested to use this version only with the help of the collaboration advice); (3) type of application: stand-alone, universal interface through HEPEVT, interface for KKMC Monte Carlo; (4) random number generators; (5) compiler options.We present the system for versioning two packages: the TAUOLA of tau lepton decay and PHOTOS for radiative corrections in decays. The following features can be chosen in automatic or semi-automatic way: (1) format of the common block HEPEVT; (2) version of the physics input (for TAUOLA): as published, as initialized by CLEO collaboration, as initialized by ALEPH collaboration (it is suggested to use this version only with the help of the collaboration advice); (3) type of application: stand-alone, universal interface through HEPEVT, interface for KKMC Monte Carlo; (4) random number generators; (5) compiler options

CERN Document Server

arXiv:hep-ph/0009302v1  26 Sep 2000TPJU 10/2000The tauola-photos-F environmentfor versioning the TAUOLA and PHOTOS packages †P. Golonkaa,b, E. Richter-Wa¸sa,c,d and Z. Wa¸sa,eaInstitute of Nuclear Physics, ul. Kawiory 26a, 30-055 Cracow, Poland.bFaculty of Nuclear Physics and Techniques, Cracow, Poland.cDepartment of Computer Science, Jagellonian UniversitydCERN, PPE, CH-1211 Geneva 23, Switzerland.eCERN, Theory Division, CH-1211 Geneva 23, Switzerland.AbstractWe present the system for versioning two packages: the TAUOLA of τ leptondecay and PHOTOS for radiative corrections in decays. The following features canbe chosen in automatic or semi-automatic way: (1) format of the common blockHEPEVT; (2) version of the physics input (for TAUOLA): as published, as initialized byCLEO collaboration, as initialized by ALEPH collaboration (it is suggested to usethis version only with the help of the collaboration advice); (3) type of application:stand-alone, universal interface through HEPEVT, interface for KKMCMonte Carlo; (4)random number generators; (5) compiler options.† Work supported in part by Polish Government grants KBN 2P03B11819, the Maria Sk lodowska-Curie Joint Fund II PAA/DOE-97-316, and the Polish–French Collaboration within IN2P3 throughLAPP Annecy.Home page at http://wasm.home.cern.ch/wasm/TPJU 10/2000August 20001 IntroductionThe TAUOLA [1–3] and PHOTOS [4, 5] are the computing projects of rather long history.Written and maintained by the well defined authors, nonetheless migrated into widerange of applications where became ingredients of the complicated simulations chains.As a consequence a large number of different versions are presently in use. From thealgorithmic point of view, they often differ only in a few small details, but incorporatesubstantial amount of specific results from the distinct τ -lepton measurements. Oftenprogram versions differ because of the requirements of interfaces to other packages usedin the simulation chains (eg. format of the event record has to be adjusted).Present utility setup for constructing specific versions of TAUOLA and PHOTOS is pre-pared for the software librarians and advanced users interested in updating both packagesin the multipurpose environment. The idea was to create a repository which allows to in-clude and keep main options of TAUOLA developed for different purposes. At the same timerepository can provide the standard Fortran files which can be handled later in exactlythe same way as the published versions of the packages.Our present document is not aimed to be the manual of the PHOTOS and TAUOLApackages. It is assumed that the user is familiar with the programs themselves and theirdocumentation, refs. [1–3] and [4, 5].Motivations for versioning:1. PHOTOS: Versions of Fortran code are necessary because of the different versionsof the HEPEVT common block being in use in the HEP libraries (single/double pre-cisions, maximal number of entries).2. TAUOLA: Versions of Fortran code are motivated by: (A) different versions of ini-tialization of physics parameters; (B) interfaces with different Monte Carlo genera-tors for production of τ -lepton(s); and (C) different versions of the HEPEVT commonblock:• (A) Different physics initializations:(1) As published in [3];(2) As initialized by ALEPH collaboration [6] (it is suggested to use this versiononly with the help of the collaboration advice);(3) As initialized by CLEO collaboration [7] (see printout of this version fordetails);(4) Further coding of some individual decay modes.• (B) Different interfaces with MC generators:(1) Old demo program as in published version [3];(2) Interface to KKMC [8];(3) New universal interface using HEPEVT common block.• (C) Different versions of the HEPEVT common block.13. TAUOLA and PHOTOS: different versions of random number generators.4. TAUOLA and PHOTOS: makefiles with different compiler flags.The aim is to provide full backward compatibility at the level of Fortran source withthe various versions being at present in use. Standard tools are used in the discussedsetup: cpp the C-language pre-compiler: its if, elif and include commands, as wellas Unix logical links and cat command. It is expected that the user will use this setupto create her/his version of TAUOLA and PHOTOS libraries (subdirectories tauola/ andphotos/) and other subdirectories of the setup will be erased/stored separately.2 Organization of the directory treeOnce unpacked, the main directory TAUOLA is created.It contains README file and:subdirectories including Fortran pre-code1. photos-F/: Main directory containing PHOTOS pre-code with options.2. tauola-F/: Main directory containing TAUOLA pre-code with options.3. demo-factory: Directory for updating input in demo files. For specialized use only,see section 2.3.4. randg/: Directory containing random number generators which are kept separatelyfrom the rest of TAUOLA and PHOTOS source code. This should facilitate replacementwith the versions of random number generators favoured by the user. Randomnumber generators are kept in Fortran subroutines placed in files photos-random.hand tauola-random.h.5. include/: Directory containing the HEPEVT-xxx.h files for different versions of theHEPEVT common block. The logical link HEPEVT.h to the one actually used will beplaced in this directory later.subdirectories necessary to run demo and,to install packages on different platforms1. glibk/: Directory containing histograming package, used by demos only.2. jetset/: Directory containing JETSET MC package, used by demos only.3. platform/: Directory containing system-dependent versions of make.inc files forsupported platforms.24. make.inc: Logical link to the chosen make-xxxx.inc located in subdirectory platform/.The make-xxxx.inc files define machine-dependent flags for compilers etc. to beused by all makefiles.The following directories are createdonce the actions of the setup are completed:1. photos/: Standard directory with Fortran code of PHOTOS library and its demo.2. tauola/: Standard directory with Fortran code of TAUOLA library, its demos andexample outputs.(a) tauola/demo-standalone: Demo program for TAUOLA executed in a stan-dalone mode.(b) tauola/demo-jetset: Demo program for TAUOLA executed with universal in-terface to physics event generators based on the HEPEVT common block. In thisdemo HEPEVT is filled from JETSET74 [9] Monte Carlo generator.(c) tauola/demo-KK-face: Interface to KK Monte Carlo [8].2.1 Options for PHOTOS Monte CarloDifferent options of PHOTOS which can be created correspond solely to the differentversions of the HEPEVT common block. The possible options are:1. KK-all – for KK Monte Carlo2. 2kD-all – dimension 2000 double precision3. 4kD-all – dimension 4000 double precision4. 2kR-all – dimension 2000 single precision5. 10kD-all – dimension 10000 double precisionThe action of creating required version of the library is performed with the help ofcpp pre-compiler. It creates file photos.f from file photos.F. Once it is done, the logicallink to the required version of the HEPEVT common block is created. This link is used inconstruction of tauola library, see next section.2.2 Options for TAUOLA Monte CarloBasic options for physics initializations are: cpc; cleo; aleph. As results of the actionperformed by the package:1. tauola/ subdirectory is erased;32. Directory structure of tauola/ is rebuilt;• tauola/ directory is filled with the Fortran code, libraries and makefiles;• tauola/demo-xx are filled with the Fortran code of demos;The three possible versions of created tauola.f correspond to form-factors and branch-ing ratios defined respectively as in: (cpc) published version of TAUOLA; (aleph) asadopted by ALEPH collaboration, (cleo) as adopted by CLEO collaboration.Remarks:• The makefile files are prepared to run TAUOLA within environment of the distributionTAUOLA directory, however the templates for makefiles are compatible with these of theKK Monte Carlo. Thus if tauola directory is copied into respective place of the KKMCdistribution tree, and make makflag of KK/ffbench/ is executed, it overwrites makefilefile in tauola/. The new ones are produced from makefile.templ and match the KKMCstructure.• Additional parametrizations for form-factors, which can be useful in some applica-tions, are stored in the directory TAUOLA/tauola-F/suppl. They are not ready to use andsome cross checks, how they match the actual option of TAUOLA library, are mandatory.At present, code used in refs. [10] and [11] is stored there.2.3 How to change setting of TAUOLA input parametersIt is often necessary to change some of the TAUOLA input parameters like branching ratios,mass of the τ -lepton, etc. It is convenient to have it done once for all applications i.e.demo-KK-face, demo-jetset and demo-standalone. The purpose of the demo-factorydirectory is exactly that. Here one can create the .F files for the interfaces, by the setof paste commands embodied in the script klej, out of the blocks of the Fortran code.More precisely the following files can be recreated:• For demo-KK-face: ./prod/Tauface.F• For demo-jetset: ./prod/tauola photos ini.F• For demo-standalone: ./prod/taumain.FFor details of the intialization routines, which are semi-identical in the three cases, seerefs. [1–3]. This requires special care from the physics point of view. In many cases inputparameters are inter-related with the actual choice of form factors. The changes shouldbe thus performed consistently.How to proceed:1. Some of the routines in directory ./source have to be updated by hand first. Theyare stored in individual files. The ones which usually should not be modified arewrite protected.42. Later execution of the script klej will create the following files from the piecesstored in directory ./source simply by pasting them together:• ./prod/Tauface.F,• ./prod/tauola photos ini.F,• ./prod/taumain.F.Automatic check (diff) with the archive versions stored in directory ./back willalso be executed.3. Finally the following commands copy the files into appropriate places:(a) cp prod/Tauface.F ../tauola-F/tauface-KK-F/Tauface.F(b) cp prod/tauola photos ini.F ../tauola-F/jetset-F/tauola photos ini.F(c) cp prod/taumain.F ../tauola-F/standalone-F/taumain.F2.4 Random number generators• PHOTOS and TAUOLA have their own copies of the random number generators. Theyare contained in the include files placed in the directory randg.• The user who wants to implement her/his own generators, eg. compatible with theones used by the collaboration, should replace files:– ./photos-random.h,– ./tauola-random.hwith the files including the appropriate wrappers of his own random generators orempty files if the generators of the same name reside elsewhere.2.5 Compiler flags etcPlatform dependent parts of the makefiles are stored in directory platform/. At presentoptions for LINUX and AIX platforms are available only. But it is rather straightforwardto extend them to the new ones.3 Universal interface with HEPEVT common blockUniversal interface to different Monte Carlo generators is provided through event recordHEPEVT. As a demonstration example it is interfaced with JETSET generator, however itshould work in the same manner with PYTHIA, HERWIG or ISAJET generators.• τ -lepton should be forced to be stable in the event generator.5• Content of the HEPEVT common block is searched for all τ leptons and neutrinos.• It is checked if there are τ -flavour pairs (two τ -leptons or τ -lepton and τ -neutrino)originating from the same mother.• Decay of the τ -flavour pairs are performed with TAUOLA. In some cases spin corre-lations are included explicitly. This is the case of the decay of W - and Z-bosons:W → τν and Z → ττ and decays of scalar and pseudoscalar Higgses: H → ττ ,A→ ττ , H± → τν. At present it is treated in the incomplete manner only. Parallelor antiparallel spin configurations are generated, but for ττ pairs originating fromZ/γ each possibility is taken with 50 % chances.• Photon radiation in decay is performed with PHOTOS.Finally let us note that the calculation of the τ polarization created from the Z and/orvirtual γ (as function of the direction), represents rather non trivial extension. Dedicatedstudy of the production matrix elements of the host generator is necessary. Separatepaper [12] will be devoted to this point.4 How to use the package1. Start with make Clean from main directory to secure against mismatches.2. Check platform dependent makefiles.• Go to subdirectory platform/• Determine if make-xxx.inc file specific for your computer is present there: forLINUX it is make-linux.inc; for AIX it is make-aix.inc; for other you needto clone/write it.• Erase symbolic link make.inc existing in this directory and create a new onewhich points to the chosen make-xxx.inc:– rm make.inc– for LINUX: ln -s make-linux.inc make.inc– for AIX: ln -s make-aix.inc make.incAfterwards check whether link to the make.inc is present in the main directory.3. Settings of TAUOLA input parameters can be changed for all implemented applica-tions, see chapter 2.3 for details.4. PHOTOS and TAUOLA have their own private random generators. If you wish to replacethem, you should do it at this point, see chapter 2.4.5. Create required versions of photos/ and tauola/ directories. It is mandatory tocreate photos/ directory first, i.e. before creating tauola/.6• Go to directory photos-F• Type one of the following commands to choose the required version of HEPEVT:– make KK-all– make 2kD-all– make 4kD-all– make 2kR-all– make 10kD-all• Go to directory tauola-F:• Type one of the following commands to choose the required version of TAUOLAinitialization:– make cpc– make cleo– make aleph6. The required version of PHOTOS and TAUOLA will reside in newly (re)created directo-ries ./photos and ./tauola.7. Following demos can be invoked from that directories:• Demo for PHOTOS resides in ./photos/demo and can be invoked by commandmake followed by make run.• Demo for TAUOLA stand-alone resides in./tauola/demo-standalone and can be invoked by the command make fol-lowed by make run.• Demo for TAUOLA with JETSET being a host Monte Carlo resides in./tauola/jetset-demo and can be invoked by the command make followedby make run.• Interface to KKMC resides in ./tauola/KK-face/Tauface.f. It has to be movedto ./KK2f/Tauface.f of distribution directory of KKMC [8]. The rest of the./tauola directory should replace the original one of the KK Monte Carlodistribution.Finally, let us remark that most of the TAUOLA tree is not necessary and can be erasedat this point. Code and makefiles of directories ./tauola and ./photos are sufficient.To execute demo programs, either directories ./jetset and ./glibk need to be kept orreplaced by the appropriate links. The make.inc logical link pointing to make-xxxx.incfile in directory ./platform, defining appropriate compiler flags, need to be kept also.75 Summary and future possibilitiesWe have presented the system for creating required version of PHOTOS and TAUOLA packagesfrom their master versions. The master version are structured in relatively compact formwithout code duplications etc.This was the first step toward future attempts to develop packages without loss oftheir present physics content. Some experience, collected already in that direction, issummarized in [13]. We find the question of the language translation for the fixed programversion relatively easy. Contrary, the question of project continuity into further upgradesmotivated by the physics, needs to be think carefully over. Matching the programmingstyles of the e.g. OO C++ experts with the strategies of testing numerical correctnessof consecutive versions is a rather crucial issue which has to be addressed. Tools andmethods embodied in Fortran survive such translation with difficulty.Necessary strategy may thus require fluency at certain moment in the Fortran/OOlanguages and physics content of the project by the same person. Platform independenttools for mixing code in Fortran and OO languages might be of great help also.AcknowledgementsAuthors are grateful to ALEPH, CLEO, DELPHI and OPAL collaborations for pro-viding their appropriate versions of the whole or parts of TAUOLA initialization. Usefuldiscussions and suggestions from B. Bloch, S. Jadach, J. H. Ku¨hn and A. Weinstein arealso acknowledged. One of the authors (ZW) acknowledges warm hospitality of the ZurichETH L3 group at the final stage of the project completion.References[1] S. Jadach, J. H. Kuhn, and Z. Was, Comput. Phys. Commun. 64 (1990) 275.[2] M. Jezabek, Z. Was, S. Jadach, and J. H. Kuhn, Comput. Phys. Commun. 70 (1992)69.[3] S. Jadach, Z. Was, R. Decker, and J. H. Kuhn, Comput. Phys. Commun. 76 (1993)361–380.[4] E. Barberio, B. van Eijk, and Z. Was, Comput. Phys. Commun. 66 (1991) 115.[5] E. Barberio and Z. Was, Comput. Phys. Commun. 79 (1994) 291–308.[6] ALEPH Collaboration, B. Bloch, to contact send a mail toBrigitte.Bloch-Devaux@cern.ch.[7] CLEO Collaboration, A. Weinstein, seehttp://www.cithep.caltech.edu/˜ajw/korb doc.html#files.8[8] S. Jadach, Z. Wa¸s, and B. F. L. Ward, Comput. Phys. Commun. 130 (2000) 260; ;pto date source is available from http://home.cern.ch/jadach/.[9] T. Sjostrand and M. Bengtsson, Comput. Phys. Commun. 43 (1987) 367.[10] OPAL Collaboration, G. Abbiendi et al., Eur. Phys. J. C13 (2000) 197,hep-ex/9908013.[11] DELPHI Collaboration, P. Abreu et al., Phys. Lett. B426 (1998) 411–427.[12] Z. Was et al., unpublished.[13] P. Golonka, MSc thesis written under supervision of Z. Wa¸s; P. Golonka’s home pageis at http://lhotse.ifj.edu.pl/~piters.9

The tauola-photos_F environment for versioning the TAUOLA and PHOTOS packages

Abstract

Similar works

Full text

Available Versions

CERN Document Server