Gabriele Cosmo
79 lines
3.3 KiB
Plaintext
79 lines
3.3 KiB
Plaintext
|
|
=========================================================
|
|
Geant4 - an Object-Oriented Toolkit for Simulation in HEP
|
|
=========================================================
|
|
|
|
ExampleP02
|
|
----------
|
|
|
|
General description
|
|
-------------------
|
|
|
|
This example shows how to store in a binary file and how to
|
|
read back the geometry tree using the 'reflection' technique for
|
|
persistency provided by the Reflex tool also included in ROOT. The
|
|
Reflex tool allows to create a dictionary for the geometry classes,
|
|
making then possible to save the entire tree in a .root file.
|
|
|
|
The provided makefile produces the executable: 'exampleP02'. In order
|
|
to run it one has to specify the argument, either 'write' or
|
|
'read'. In the first case the geometry is instaciated in the standard
|
|
way and then saved into the root file (geo.root). In the second case,
|
|
the geometry is read from geo.root file.
|
|
|
|
|
|
Building and running the example
|
|
--------------------------------
|
|
|
|
Before buidling and/or running the example you need to set the
|
|
following environment variables:
|
|
|
|
ROOTSYS - ROOT installation directory, it is required to run ROOT
|
|
|
|
GCCXMLPATH - gccxml binary directory, it is needed by ROOT for the
|
|
dictionary generation
|
|
LD_LIBRARY_PATH - to include the ROOT library path and the path to
|
|
the dictionary library, i.e., for tcsh UNIX shell:
|
|
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:$ROOTSYS/lib:
|
|
$G4WORKDIR/tmp/$G4SYSTEM/exampleP01
|
|
|
|
The present version of the example requires that Geant4 headers are
|
|
installed in a single directory referenced by G4INCLUDE, as the standard
|
|
Geant4 installation procedure allows to do.
|
|
|
|
Once those variables are set (together with the standard Geant4 setup)
|
|
the example can be build by issueing the 'make' command. The final
|
|
executable file can be found in the usual directory:
|
|
|
|
$G4WORKDIR/bin/$G4SYSTEM/
|
|
|
|
|
|
Remark on dictionary generation
|
|
-------------------------------
|
|
|
|
The dictionary is generated by ${ROOTSYS}/bin/genreflex
|
|
tool. The header file including headers for all the classes we want to
|
|
generate the dictionary for should be given as argument. Additionally,
|
|
a so called selection file (xml) should be provided (with -s flag) to
|
|
the genreflex tool (see the GNUmakefile). The role of this file is to
|
|
specify which classes we want to generate the dictionary for. The
|
|
selection file for our dictionary is in xml/ directory. Please refer
|
|
to genreflex manual for more details concerning the usage of that
|
|
tool.
|
|
|
|
Concerning generating dictionary for the Geant4 objects, there are
|
|
also two technical remarks that need to be made here. The gccxml tool
|
|
(version 0.6.0_patch1) requires all the templated classes to be
|
|
explicitely used somewhere in the included header files in order for
|
|
the generation of the dictionary to be possible. For those templated
|
|
classes for which it is not the case, the problem can be very easily
|
|
solved by instaciating them in the headerfile which is given to
|
|
genreflex (see includes/Classes.h) as argument.
|
|
The second remark is that there is an unfortunate clash of names as
|
|
far as G4String class is concerned. The header of G4String class
|
|
defines __G4String which happens to be the name of a variable used
|
|
within the generated dictionary code. The solution for that is to do
|
|
#undef __G4String in include/Classes.h file.
|
|
|
|
|