The version that has been integrated into SPENVIS allows the user to execute GRAS remotely without the need to install Geant4 and the GRAS code on his/her local computer. However, users preferring a local version of this tool can download the source code from the ESA/GRAS website.
The latest version of GRAS installed in SPENVIS is v3.1 compiled with geant4-09-05-patch-02.
Users can go to any particular input page and enter their settings. Note that some input is obligatory. After they have provided their data on a particular input page, they can press the button and return to the main model page. Once they are satisfied with all their input, they can press on the button to generate the macro file. Pressing the button will start the calculation and bring up the results page.
Since the model uses a Monte-Carlo simulation-based code, execution time can be very long. In order to guarantee consistency between the different models available in the SPENVIS system, the user project is 'blocked' while running the GRAS simulation. Nevertheless, navigation remains possible. The excution is limited to ten minutes of CPU-time on the simulation server. If the GRAS run exceeds this limit, the simulation will be terminated and intermediate results returned to the user.
There are two execution modes available for the SPENVIS GRAS implementation: GDMLMULASSIS. For the MULASSIS execution mode the user is referred to the MULASSIS help page since the input pages are the same. However, note that some of the input for the two models might differ (e.g. different analysis types available for MULASSIS and GRAS).
The following sections describe the user input for the GDML execution mode.
This information is recorded in a separated macro file (GPS macro file) that is executed inside the GRAS main macro.
The user can locate the source anywhere inside the GDML geometry by selecting a particular GDML volume (see later) and providing the Cartesian coordinates with respect to the centre of that volume. For a point or a disk source, the user can also specify where the source is pointing to by selecting another volume and providing again the Cartesian coordinates with respect to the centre of that volume. Note that the two reference volumes can coincide. When the source is assumed to be a disk or a sphere, an additional input for the source radius is required. The Cartesian coordinates and the source radius can be defined in terms of [mm], [cm] or [m].
The default geometry source is a point source located inside the volume “world” at x=0, y=0 and z=100 [mm] pointing at the centre of “world”. For a mission based environment and a GDML execution mode, a spherical source is recommended. However, it is the responsibility of the user to position correctly the source with respect to the GDML geometry.
Finally, it is possible to produce a graphical representation of the chosen geometry. This can be generated in two formats, i.e. PostScript or VRML, with or without the visualisation of the particle tracks. Note that no particle tracks would be represented in the graphics file if more than hundred primary particles are requested for the simulation.
The user can select only one analysis type at a time.
In addition, a common analysis module is automatically inserted by GRAS (no user action is required) and its results are output at the end of the simulation.
For fluence and NIEL, users can select a number of volume interfaces for the analysis. Then, a count is registered only when the particle crosses the selected boundary in the direction specified by the user (i.e. the order of the volume names). For TID, dose equivalent and equivalent dose the user can specify the number and the name of the volumes where the particular analysis will be performed.
The results are recorded as:
The Linear Energy Transfer (LET) analysis module computes the LET spectrum at user a selected volume boundary. The LET is obtained by computing the value of dE/dx for user specified particle type and energy in a given material. The output units are MeV/cm. In SEU analyses the LET spectrum can be used to obtain an estimate of the SEU rate (e.g. by integrating the LET spectrum above a given threshold).
The general principles in Geant4 regarding secondary particle production cuts are the following:
Volumes that require different cuts from the global ones shall be grouped into regions and each region can be given its own cuts. Again, region cuts-in-range can be defined as a single cut for gamma, electron and positron productions, or different cuts for each type of the three particles. In addition the user can group the GDML geometry volumes into different regions and apply different cuts to each region.
Note that the default is no region cuts-in-range and the default values for the global cuts-in-range length is 1 µm.
More recently, a new Geant4 physics list QBBC has been created dedicated for space applications, radiation biology and radiation protection. It includes combinations of BIC, BIC-Ion, BERT, CHIPS, QGSP and FTFP models and has higher precision than the others for many hadron-ion and ion-ion interactions in a wide energy range [Ivantchenko et al., 2012].
Based on the user’s selection for the incident particle, SPENVIS automatically selects the appropriate physics scenario. For pure EM interactions (e.g. incident gamma or electron) the Geant4 Option 3 (emstandard_opt3) is used. This standard EM physics list is optimised for medical and space applications. Otherwise, the physics list QBBC is used to simulate additional hadronic interactions. Finally, note that for geantinos no physics scenario is required.
The normalisation factor for the SPENVIS implementation of GRAS is calculated using the following formula:
where n1 and n2 are calculated by the SPENVIS Geant4 “source particles tool” and recorded in the generated macro file (NORM_FACTOR_SPECTRUM and NORM_FACTOR_ANGULAR aliases in the GPS macro file). Note that the normalisation factor is calculated in terms of particles per cm -2.
When the GDML mode is selected the user can also specify the geometry of the source. For a disk-like or a spherical source the area of its surface has to be taken into consideration when calculating the normalisation factor. In the SPENVIS implementation this is computed automatically by GRAS using the following macro command: /gras/analysis/setSourceSurfaceType AUTO
For the 1D simulations (MULASSIS mode) and when the geometry refers to a spherical shell the normalisation factor requires an additional term in order to take into consideration the integration over the surface of the source sphere. In other words, one needs to divide the above formula by a factor of 4πR2.
Finally, GRAS can distinguish (internally) between normalising with respect to external flux or current by using the /gras/analysis/setSourceFluenceType macro command and selecting either FLUX or CURRENT respectively. However, the outputs of the Geant4 Monte-Carlo simulations are in general inherently normalised to unit incident current e.g. as in the case of MULASSIS. Therefore, for both GDML and MULASSIS modes the SPENVIS GRAS v3.1 results are normalised to a current going through the primary surface i.e. the CURRENT option is used.
The log file spenvis_gras.g4log records the output from GRAS to stdout and stderr. The output file spenvis_gras.csv containing tabulated results (fluence, NIEL, TID, dose equivalent or equivalent dose) for the selected analysis. The graphics files spenvis_gras.wrl and spenvis_gras.eps show the 3D geometry or the shield cross section.
spenvis_gras.g4log
spenvis_gras.csv
spenvis_gras.wrl
spenvis_gras.eps
spenvis_gras31.g4log
spenvis_gras31.g4mac
spenvis_gras31.csv
spenvis_gras31_aida.root
spenvis_gras31.wrl
spenvis_gras31.eps
spenvis_gras31_aida.ps