| 1 |
|
|---|
| 2 | =========================================================
|
|---|
| 3 | Geant4 - an Object-Oriented Toolkit for Simulation in HEP
|
|---|
| 4 | =========================================================
|
|---|
| 5 |
|
|---|
| 6 | ExampleP02
|
|---|
| 7 | ----------
|
|---|
| 8 |
|
|---|
| 9 | General description
|
|---|
| 10 | -------------------
|
|---|
| 11 |
|
|---|
| 12 | This example shows how to store in a binary file and how to
|
|---|
| 13 | read back the geometry tree using the 'reflection' technique for
|
|---|
| 14 | persistency provided by the Reflex tool also included in ROOT. The
|
|---|
| 15 | Reflex tool allows to create a dictionary for the geometry classes,
|
|---|
| 16 | making then possible to save the entire tree in a .root file.
|
|---|
| 17 |
|
|---|
| 18 | The provided makefile produces the executable: 'exampleP02'. In order
|
|---|
| 19 | to run it one has to specify the argument, either 'write' or
|
|---|
| 20 | 'read'. In the first case the geometry is instaciated in the standard
|
|---|
| 21 | way and then saved into the root file (geo.root). In the second case,
|
|---|
| 22 | the geometry is read from geo.root file.
|
|---|
| 23 |
|
|---|
| 24 |
|
|---|
| 25 | Building and running the example
|
|---|
| 26 | --------------------------------
|
|---|
| 27 |
|
|---|
| 28 | Before buidling and/or running the example you need to set the
|
|---|
| 29 | following environment variables:
|
|---|
| 30 |
|
|---|
| 31 | ROOTSYS - ROOT installation directory, it is required to run ROOT
|
|---|
| 32 |
|
|---|
| 33 | GCCXMLPATH - gccxml binary directory, it is needed by ROOT for the
|
|---|
| 34 | dictionary generation
|
|---|
| 35 | LD_LIBRARY_PATH - to include the ROOT library path and the path to
|
|---|
| 36 | the dictionary library, i.e., for tcsh UNIX shell:
|
|---|
| 37 | setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$ROOTSYS/lib:
|
|---|
| 38 | $G4WORKDIR/tmp/$G4SYSTEM/exampleP01
|
|---|
| 39 |
|
|---|
| 40 | The present version of the example requires that Geant4 headers are
|
|---|
| 41 | installed in a single directory referenced by G4INCLUDE, as the standard
|
|---|
| 42 | Geant4 installation procedure allows to do.
|
|---|
| 43 |
|
|---|
| 44 | Once those variables are set (together with the standard Geant4 setup)
|
|---|
| 45 | the example can be build by issueing the 'make' command. The final
|
|---|
| 46 | executable file can be found in the usual directory:
|
|---|
| 47 |
|
|---|
| 48 | $G4WORKDIR/bin/$G4SYSTEM/
|
|---|
| 49 |
|
|---|
| 50 |
|
|---|
| 51 | Remark on dictionary generation
|
|---|
| 52 | -------------------------------
|
|---|
| 53 |
|
|---|
| 54 | The dictionary is generated by ${ROOTSYS}/bin/genreflex
|
|---|
| 55 | tool. The header file including headers for all the classes we want to
|
|---|
| 56 | generate the dictionary for should be given as argument. Additionally,
|
|---|
| 57 | a so called selection file (xml) should be provided (with -s flag) to
|
|---|
| 58 | the genreflex tool (see the GNUmakefile). The role of this file is to
|
|---|
| 59 | specify which classes we want to generate the dictionary for. The
|
|---|
| 60 | selection file for our dictionary is in xml/ directory. Please refer
|
|---|
| 61 | to genreflex manual for more details concerning the usage of that
|
|---|
| 62 | tool.
|
|---|
| 63 |
|
|---|
| 64 | Concerning generating dictionary for the Geant4 objects, there are
|
|---|
| 65 | also two technical remarks that need to be made here. The gccxml tool
|
|---|
| 66 | (version 0.6.0_patch1) requires all the templated classes to be
|
|---|
| 67 | explicitely used somewhere in the included header files in order for
|
|---|
| 68 | the generation of the dictionary to be possible. For those templated
|
|---|
| 69 | classes for which it is not the case, the problem can be very easily
|
|---|
| 70 | solved by instaciating them in the headerfile which is given to
|
|---|
| 71 | genreflex (see includes/Classes.h) as argument.
|
|---|
| 72 | The second remark is that there is an unfortunate clash of names as
|
|---|
| 73 | far as G4String class is concerned. The header of G4String class
|
|---|
| 74 | defines __G4String which happens to be the name of a variable used
|
|---|
| 75 | within the generated dictionary code. The solution for that is to do
|
|---|
| 76 | #undef __G4String in include/Classes.h file.
|
|---|
| 77 |
|
|---|
| 78 |
|
|---|