Proposal of CHIPS melting in Geant4 hadronic

1. Proposal of CHIPS melting in Geant4 hadronic M. Kosov (ITEP/VNIIA)

2. Introduction • Historically, the CHIPSPhysics package was placed to hadronic/models, whilst at present it includes cross-sections and processes, which should be in proper place in the Geant4 hadronic. • Fortunately, CHIPSdoes not depend on any class of the G4Hadr administration, so temporary it can be moved to any position in the Geant4/hadronic directory/dependency hierarchy. • After that it can be split in parts and distributed through the management, cross_sections, models, and processes sub-directories of Geant4 hadronic: Three Steps Proposal. M.Kosov, CHIPS melting in G4Hadr

3. hadronic processes models cross_sections management chips chiral_inv_phase_space body cross_sections fragmentation processes calcul test nucleus utiles empty empty interface Geant4/tests Step One: the emptynucleus and utiles directories are deleted, the test is moved to geant4/tests directory as test79, the interface stays put, the rest is moved to the new hadronic/chips directory (tmp). This works on my PC. test79 = test M.Kosov, CHIPS melting in G4Hadr

4. hadronic processes models cross_sections management chips chiral_inv_phase_space body cross_sections fragmentation processes calcul interface Step Two: the chiral_inv_phase_space/interface directory is made for G4Hadr interfaces to CHIPS, so it depends on all the G4Hadr administration and can’t be moved on the Step One. It depends on CHIPS too, but as the temporary chips directory is made on the very bottom of hadronic the interface directory depends on CHIPS too as well as the hadronicmanagement, cross_sections, models, processes directories. On the Step Two the classes of interface are distributed over the management, cross_sections, models and disappear in the old directory together with the chiral_inv_phase_space directory itself. Geant4/tests test79 M.Kosov, CHIPS melting in G4Hadr

5. hadronic processes models cross_sections management chips chips chips chips_calcul chips chips body cross_sections fragmentation calcul processes Step Three: if the cross_sections depends on management (?), models depends on both of them, and processes depends on all three of them, then the following trivial moves should be done: chips/body → management/chips, chips/cross_sections → cross_sections/chips, chips/fragmentation → models/chips, chips/calcul → models/calcul_chips (not in the public releases), chips/processes → processes/chips. As a result, the temporarychips directory disappears and CHIPS is melted in Geant4 hadronic. tests test79 M.Kosov, CHIPS melting in G4Hadr

6. hadronic processes models cross_sections management chips chips chips_calcul chips chips Final state: As a result of this CHIPS movement, not only the CHIPS dependencies are preserved, but all G4Hadr classes can use CHIPS classes directly or through the distributed interfaces to CHIPS, which can be still supported by me or by any other person (e. g. Witek). The cross-section interfaces to CHIPS elastic and inelastic XS, which as a result becomes in cross_sections, can be used by any G4Hadr process or in Physics Lists in parallel with the cloned CHIPS cross-section classes. Except for the interface directory, distribution of which over the rest of hadronic sub-directories (Step Two) demands further discussion, the rest of the CHIPS sub-directories are moved as is, so the change in the GNUmakefile and source.cmake files are trivial on each Step. tests test79 M.Kosov, CHIPS melting in G4Hadr

7. A few comments about CHIPS PDG • The CHIPS C++ Physics Package inherits from FORTRAN DINREG (Deep Inelastic Reaction Event Generator). • The first CHIPS C++ Manual was published in 2000 in KEK (including the G4QPDGCode) before CERN G4 contracts. • In this Manual the first proposal of the PDG codes for isotopes was made & realized in a 9LZZZNNN form. • Tthe PDG particle code is an integer constant, and if it is wrong, it’s a bug. The PDG code is not the float mass value. • In CHIPS the hadronic PDG code is used to extract the G4QuarkContent. It’s not just a number, it defines quarks. • In 2007 the CHIPS proposal for the isotope PDG code was discussed by the PDG community and after a world wide discussion it was adopted in a form 10LZZZAAAI. • Conversion of CHIPS to this code was planned as a future work. At present the code is converted on the process level. M.Kosov, CHIPS melting in G4Hadr

8. Conclusion • The CHIPSmelting in Geant4/hadronicdoes not break any dependency and does not prevent any cloning from CHIPS. • After the Witold’s cloning, it has become much easier. • Step One can be done in the 9.6-beta release (proper time). • Step Two demands additional discussion in the hadronic group to find proper places for G4Hadr interfaces to CHIPS. • Step Three is trivial & can be done together with Step Two. • As a result two administrations can coexist in G4/hadronic: the G4Hadr, made by H.-P. Wellisch, and the CHIPS, made by me, which is much simpler, as it is using only the basic interface classes of Geant4. The new structure of the dependencies/directories lets any G4Hadr class to use any necessaryCHIPS classes and reduces the cloning needs. • The Step One is the very minimum. It’s working fine on my PC & I can improve CHIPS only in this layout of directories. • As soon as G4 makes Step One, we can converge back. M.Kosov, CHIPS melting in G4Hadr