Download GAMOS

13.1. USING PHASE SPACES
127
When you use a phase space as input you may use as number of
events the real number of events run in your job (which would equal
be to the number of particles in the phase space multiplied by the
number of times each particle is reused), or you may alternatively use
as number of events the original number of events that were used to
generate the phase space (see section on Scoring dose in phantom. To
use the first the first one you can invoke the standard Geant4 method
G4RunManager::GetRunManager()-¿GetNumberOfEvent(), to use the
second one, you may invoke the GAMOS method GmNumberOfEvent::GetNumberOfEvent().
13.1.4
Adding extra information to a phase space
The IAEA format allows the storing of two long integers and two floats
in the phase space file as extra information. In GAMOS we have extended this functionality by putting the 32+32 bits of the two integers in a continuous stream, that the user can divide in groups of
bits of the desired length to store several informations. The user can
even add more sets of 32 bits by changing the the following line at
source/RadioTherapy/include/iaeaRecord.hh :
#define NUM_EXTRA_LONG 2
and recompiling (cd MY GAMOS DIR/source/RadioTherapy; make).
To store some information in this format the user has to instantiate
one of the following user actions
• RTExtraInfoProviderCrossings: fills a bit if the track has crossed
the corresponding region before reaching the phase space
• RTExtraInfoProviderInteractions: fills a bit if the track has interacted in the corresponding region before reaching the phase space
• RTExtraInfoProviderOrigin: fills a bit if the track has been created
in the corresponding region before reaching the phase space
The user may select how many bits each information must occupy by
using the GAMOS parameter :
/gamos/setParam EXTRA INFO NAME:NBits NBITS
where EXTRA INFO NAME is the name of the extra information class
(see above). GAMOS will check that the index to be filled by a class is
not bigger than the number of bits reserved for it. And it will also check
that the total number of bits is not bigger than the available quantity
(32*NUM EXTRA LONG).
The order of declaration of the extra information user actions sets
the order of bits occupancy. At the end of the job each of these extra
information user actions fills a file explainning the information contained
in each bit. By default this file is called RTExtraInfoProvider.summ, but
the user may change the name of it with the parameter /gamos/setParam
RTExtraInfoProviderLong:FileName FILE NAME
An example of a file is the following one: