Geant4 Tools#

Configuration File: geant4_tools.json Tool Type: Local Tools Count: 1

This page contains all tools defined in the geant4_tools.json configuration file.

Available Tools#

geant4_depth_dose_simulation (Type: Geant4DepthDoseTool)#

Monte Carlo depth-dose simulation with GEANT4: fire a particle beam into a slab of one NIST mater…

geant4_depth_dose_simulation tool specification

Tool Information:

  • Name: geant4_depth_dose_simulation

  • Type: Geant4DepthDoseTool

  • Description: Monte Carlo depth-dose simulation with GEANT4: fire a particle beam into a slab of one NIST material and get the energy deposited in each depth bin, plus the peak depth (the Bragg peak for ions). Use it for range and shielding questions — how deep a 150 MeV proton beam deposits its dose in water, how much of a gamma beam a lead slab absorbs, how an ion’s range changes with energy or tissue. One fixed application is compiled against the local GEANT4 on first use; nothing but the numbers below can vary, so no geometry or macro is accepted. Requires a local GEANT4 installation with its physics data (geant4-config on PATH, or GEANT4_CONFIG set); a 200-event proton run takes about a second.

Parameters:

  • particle ([‘string’, ‘null’]) (optional) Beam particle (default ‘proton’).

  • energy_mev ([‘number’, ‘null’]) (optional) Kinetic energy of each primary particle in MeV, from 0.001 to 100000 (default 150).

  • material ([‘string’, ‘null’]) (optional) Target material, a NIST name GEANT4 builds itself (default ‘G4_WATER’).

  • thickness_cm ([‘number’, ‘null’]) (optional) Depth of the target along the beam in cm, from 0.01 to 500 (default 20). Make it larger than the expected range, or the beam leaves the target before stopping.

  • bins ([‘integer’, ‘null’]) (optional) Number of equal depth bins to score, from 1 to 2000 (default 100). thickness_cm / bins is the depth resolution.

  • events ([‘integer’, ‘null’]) (optional) Primary particles to simulate, from 1 to 200000 (default 200). More events mean a smoother curve and a longer run.

  • timeout_seconds ([‘integer’, ‘null’]) (optional) Give up after this many seconds, from 1 to 1800 (default 600).

Example Usage:

query = {
    "name": "geant4_depth_dose_simulation",
    "arguments": {
    }
}
result = tu.run(query)