Home

Geant4 User's Guide for Application Developers

1. Invoke the OGLSX driver Create a scene handler and a viewer for the OGLSX driver vis open OGLSX Create an empty scene and add detector components to it vis drawVolume Add trajectories to the current scene Note This command is not necessary in e g examples novice N03 since the C method DrawTrajectory is described in the event action vis scene add trajectories Set viewing parameters vis viewer reset vis viewer set viewpointThetaPhi 10 20 Visualize one it run beamOn 1 RHE HH HE AE FE FE HE FE FE FE HE EE AE FE FE AE FE FE FE FE EE FE AE FE FE HE FE FE FE HE FE FE E HE AE FE FE HE FE FE E FE E EE RE Visualization with the DAWNFILE driver FE EE FE E E FE AE FE FE AE FE FE FE E FE AE E FE AE FE FE FE FE FE FE E FE AE E FE AE FE FE AE FE FE FE AE FE AE FE FE AE FE FE AE FE FE E FE E E E EE Invoke the DAWNFILE driver Create a scene handler and a viewer for the DAWNFILE driver vis open DAWNFILE Create an empty scene and add detector components to it vis drawVolume Add trajectories to the current scene Note This command is not necessary in exampleN03 since the C method DrawTrajectory is described in the event action vis scene add trajectories Visualize plural events bird s eye view drawing style wireframe viewpoint theta phi 45 deg 45 deg Zoon Tractor m bs sereen Size
2. RayTracer has its own built in commands vis rayTracer Alternatively you can treat it as a normal vis system and use vis viewer commands e g vis open RayTracerX vis drawVolume vis viewer set viewpointThetaPhi 30 30 vis viewer refresh The view parameters are translated into the necessary RayTracer parameters RayTracer is compute intensive If you are unsure of a good viewing angle or zoom factor you might be advised to choose them with a faster renderer such as OpenGL and transfer the view parameters with vis viewer set all vis open OGLSXm or any of the OGL options Opens say viewer 0 vis drawVolume vis viewer zoom plus any vis viewer commands that get you the view you want vis open RayTracerX vis viewer set all viewer 0 vis viewer refresh 8 3 10 Visualization of detector geometry tree ASCIITREE is a visualization driver that is not actually graphical but that dumps the volume hierarchy as a simple text tree Each call to vis viewer flush or vis drawTree will dump the tree ASCII Tree has command to control its verbosity vis ASCIITree verbose The verbosity value controls the amount of information available e g physical volume name alone or also logical volume and solid names If the volume is sensitive and or has a readout geometry this may also be indicated Also the mass of the physical volume tree s can be printed but beware higher verbosity levels can
3. pRmin Inside radius pRmax Outside radius pRtor Swept radius of torus pSPhi Starting Phi angle in radians SPhi f DPhi lt 2PI SPhi gt 2PI pDPhi Delta angle of the segment in radians 63 Detector Definition and Response In addition the Geant4 Design Documentation shows in the Solids Class Diagram the complete list of CSG classes and the STEP documentation contains a detailed EXPRESS description of each CSG solid Specific CSG Solids Polycons Polycons PCON are implemented in Geant4 through the G4Polycon class G4Polycone const G4String amp pName G4double G4double G4int const G4double const G4double const G4double G4Polycone const G4String amp pName G4double G4double G4int const G4double const G4double UL SESW c phiTotal phiStart phirT tal numZPlanes zPlane rInner rOuter numRZ r z In the picture phiStart 1 4 Pi phiTotal 3 2 Pi numZPlanes 9 rIn ner 0 0 0 0 0 0 0 0 0 rOuter 0 10 10 5 p 5y AD gt 10 y 2y 2hr R 5 Tr Sp Aly 255 21r 297 3L 35 3 where phiStart Initial Phi starting angle phiTotal Total Phi angle numZPlanes Number of z planes numRZ Number of corners in r z space zPlane Position of z planes rInner Tangent distance to inner surface rOuter Tangent distance to outer surface r r coordinate of corners Z z coordinate of corners Pol
4. Auxiliary point visibility true Draw step point false Step point type circles Step point size 0 Step point fill style filled Step point colour yellow Step point visibility true Time slice interval 0 Points to note The context approach is intended to replace the configuration through the imode parameter The use of imode is depreciated and will be removed in Geant4 v9 0 Different visualisation drivers handle trajectory configuration in different ways so trajectories may not neces sarily get displayed as you have configured them 8 7 2 Trajectory Drawing Models A trajectory drawing model can override the default context according to the properties of a given trajectory The following models are supplied with the Geant4 distribution e G4TrajectoryGenericDrawer generic G4TrajectoryDrawByCharge drawByCharge G4TrajectoryDrawByParticleID drawByParticleID G4TrajectoryDrawByOriginVolume drawByOriginVolume G4TrajectoryDrawByAttribute drawByAttribute Both the context and model properties can be configured by the user The models are described briefly below followed by some example configuration commands G4TrajectoryGenericDrawer This model simply draws all trajectories in the same style with the properties provided by the context G4TrajectoryDrawByCharge This is the default model if no model is specified by the user this model will be constructed automatically The trajectory lines a
5. is messaged by the process manager whenever cross section tables should be prepared and rebuilt due to chang ing cut off values It is not mandatory if the process is not affected by cut off values virtual void StartTracking and virtual void EndTracking are messaged by the tracking manager at the beginning and end of tracking the current track Other base classes for processes Specialized processes may be derived from seven additional virtual base classes which are themselves derived from G4VProcess Three of these classes are used for simple processes 140 Tracking and Physics G4VRestProcess Processes using only the AtRestDoIt method example neutron capture G4VDiscreteProcess Processes using only the Post StepDoIt method example compton scattering hadron inelastic interaction The other four classes are provided for rather complex processes G4VContinuousDiscreteProcess Processes using both AlongStepDoIt and PostStepDoIt methods example transportation ionisation energy loss and delta ray G4VRestDiscreteProcess Processes using both AtRestDoIt and PostStepDoIt methods example positron annihilation decay both in flight and at rest G4VRestContinuousProcess Processes using both AtRestDoIt and AlongStepDoIt methods G4VRestContinuousDiscreteProcess Processes using AtRestDoIt AlongStepDoIt and PostStepDolt methods Particle change G4VParticleChange and its descendants
6. The biasing can be controlled either in compiled code or through interactive commands Extensive documentation can be found in Radioactive decay biasing example and Radioactive decay biasing Radioactive decay biasing examples are also distributed with the Geant4 distribution in examples extended ra dioactivedecay exrdm 3 7 2 1 3 Hadronic Leading Particle Biasing One hadronic leading particle biasing technigue is implemented in the G4HadLeadBias utility This method keeps only the most important part of the event as well as representative tracks of each given particle type So the track with the highest energy as well as one of each of Baryon pi0 mesons and leptons As usual appropriate weights are assigned to the particles Setting the SwitchLeadBiasOn environmental variable will activate this utility 3 7 2 1 4 Hadronic Cross Section Biasing Cross section biasing artificially enhances reduces the cross section of a process This may be useful for study ing thin layer interactions or thick layer shielding The built in hadronic cross section biasing applies to photon inelastic electron nuclear and positron nuclear processes The biasing is controlled through the BiasCrossSectionByFactor method in G4HadronicProcess as demonstrated below void MyPhysicsList ConstructProcess i G4ElectroNuclearReaction theElectroReaction new G4ElectroNuclearReaction G4ElectronNuclearProcess theElectronNuclearProcess theElectro
7. twistedangle Twisted angle endinnerrad Inner radius at endcap endouterrad Outer radius at endcap halfzlen Half z length dphi Phi angle of a segment Additional constructors are provided allowing the shape to be specified either as the number of segments in phi and the total angle for all segments or e a combination of the above constructors providing instead the inner and outer radii at z 0 with different z lengths along negative and positive z axis 4 1 2 2 Solids made by Boolean operations Simple solids can be combined using Boolean operations For example a cylinder and a half sphere can be com bined with the union Boolean operation Creating such a new Boolean solid requires Two solids 71 Detector Definition and Response A Boolean operation union intersection or subtraction Optionally a transformation for the second solid The solids used should be either CSG solids for examples a box a spherical shell or a tube or another Boolean solid the product of a previous Boolean operation An important purpose of Boolean solids is to allow the de scription of solids with peculiar shapes in a simple and intuitive way still allowing an efficient geometrical nav igation inside them The solids used can actually be of any type However in order to fully support the export of a Geant4 solid model via STEP to CAD systems we restrict the use of Boolean operations to this subset of solids
8. Mandatory method required and reason for this class virtual G4Material ComputeMaterial G4VPhysicalVolume currentVol const G4int no lev const G4VTouchable parentTouch private G4Material materiall material2 i The implementation of the method can utilise any information from a parent or other ancestor volume of its parameterised physical volume but typically it will use only the copy number G4Material SampleNestedParameterisation ComputeMaterial G4VPhysicalVolume currentVol const G4int no_lev const G4VTouchable parentTouchable G4Material material 0 Get the information about the parent volume G4int no parent parentTouchable gt GetReplicaNumber 83 Detector Definition and Response G4int no_total no_parent no_lev A simple checkerboard pattern of two materials if no_total 2 material materiall else material material2 Set the material to the current logical volume G4LogicalVolume currentLogVol currentVol gt GetLogicalVolume currentLogVol gt SetMaterial material return material Nested parameterisations are suitable for the case of regular voxel geometries in which a large number of equal volumes are required and their only difference is in their material By creating two or more levels of parame terised physical volumes it is possible to divide space while requiring only limited additional memory for very fine level optimisation This provid
9. 141 Tracking and Physics Photo electric effect class name G4PhotoElectricEffect e Muon pair production class name G4GammaConversionToMuons Electron positron processes Ionisation and delta ray production class name G4elonisation Bremsstrahlung class name G4eBremsstrahlung Positron annihilation into two gammas class name G4eplusAnnihilation e Positron annihilation into two muons class name G4AnnihiToMuPair Positron annihilation into hadrons class name G4eeToHadrons Muon processes Ionisation and delta ray production class name G4Mulonisation Bremsstrahlung class name G4MuBremsstrahlung e e e pair production class name G4MuPairProduction Hadron ion processes Ionisation class name G4hlonisation Ionisation for ions class name G4ionlonisation Ionisation for ions in low density media class name G4ionGaslonisation Ionisation for heavy exotic particles class name G4hhlonisation Ionisation for classical magnetic monopole class name G4mpllonisation Coulomb scattering processes A general process in the sense that the same process class is used to simulate the multiple scattering of the all charged particles class name G4MultipleScattering Specialised process for more fast simulation the multiple scattering of muons and hadrons class name G4hMultipleScattering Alternative process beta version for the multiple scattering of muons class name G4MuMultipleScattering Al
10. Fill the assembly by the plates as SecX caloX AL Ta SSC Y calorias Ta s E 2 0105 assemblyDetector AddPlacedVolume plateLV G4Transform3D Ta Ra Ta setr r emdiepx AM 2 eset esie 5 Ta setat 5 jp assemblyDetector AddPlacedVolume plateLV G4Transform3D Ta Ra Rae secX cado 1 Ta Set 0 escal oY AB a Se E RM assemblyDetector AddPlacedVolume plateLV G4Transform3D Ta Ra Ta setX caloX 4 Ta setY 1 caloY 4 Ta setZ 0 assemblyDetector AddPlacedVolume plateLV G4Transform3D Ta Ra Now instantiate the layers for unsigned int i 0 i lt layers i 1 Translation of the assembly inside the world G4ThreeVector Tm 0 0 i caloZ caloCaloOffset firstCaloPos assemblyDetector MakeImprint worldLV G4Transform3D Tm Rm The resulting detector will look as in Figure 4 3 below Ii 1 i jew are Figure 4 3 The geometry corresponding to the previous example code An example of usage of the G4AssemblyVolume class 90 Detector Definition and Response 4 1 7 Reflecting Hierarchies of Volumes Hierarchies of volumes based on CSG or specific solids can be reflected by means of the G4ReflectionFactory class and G4ReflectedSolid which implements a solid that has been shifted from its original reference frame to a new reflecte
11. where WorldExtent is the actual maximum extent of the world volume used for placing the whole geometry setup Such call to G4Geomet ryManager must be done before defining any geometrical component of the setup solid shape or volume and can be done only once The class G4Geomet ryTolerance is to be used for retrieving the actual values defined for tolerances surface Cartesian angular or radial respectively G4GeometryTolerance GetInstance GetSurfaceTolerance G4GeometryTolerance GetInstance GetAngularTolerance i G4GeometryTolerance GetInstance GetRadialTolerance 4 1 9 A Simple Geometry Editor GGE is the Geant4 Graphical Geometry Editor It is implemented in JAVA and is part of the Momo environment GGE aims to serve physicists who have a little knowledge of C and the Geant4 toolkit to construct his or her own detector geometry in a graphical manner GGE provides methods to 1 construct a detector geometry including G4Element G4Material G4Solids G4LogicalVolume G4PVPlacement etc view the detector geometry using existing visualization system like DAWN keep the detector object in a persistent way produce corresponding C codes after the norm of Geant4 toolkit make a Geant4 executable under adequate environment nb WN GGE is implemented with Java using Java Foundation Class Swing 1 0 2 In essence GGE is made a set of tables which contain all relevant parameters to cons
12. 53 Toolkit Fundamentals explicit G4WeightWindowStore const G4VPhysicalVolume amp worldvolume virtual G4WeightWindowStore virtual G4double GetLowerWeitgh const G4GeometryCell amp gCell G4double partEnergy const virtual G4bool IsKnown const G4GeometryCell amp gCell const virtual const G4VPhysicalVolume amp GetWorldVolume const void AddLowerWeights const G4GeometryCell amp gCell const std vector G4double amp lowerWeights void AddUpperEboundLowerWeightPairs const G4GeometryCell amp gCell const G4UpperEnergyToLowerWeightMap enWeMap void SetGeneralUpperEnergyBounds const std set lt G4double std less lt G4double gt gt amp enBounds private The user may choose equal energy bounds for all cells In this case a set of upper energy bounds must be given to the store using the method SetGeneralUpperEnergyBounds If a general set of energy bounds have been set AddLowerWeights can be used to add the cells Alternatively the user may chose different energy regions for different cells In this case the user must provide a mapping of upper energy bounds to lower weight bounds for every cell using the method AddUpperEbound LowerWeightPairs Weight window algorithms implementing the interface class G4VWeightWindowAlgorithm can be used to define a customized algorithm class G4VWeightWindowAlgorithm PUDLLET G4VWeightWindowAlgorithm virtual G4VWeightWindowAlgorithm virtual
13. Construct the run manager G4RunManager runManager new G4RunManager Activate command based scorer G4ScoringManager GetScoringManager 132 Detector Definition and Response 4 8 2 Defining a scoring mesh To define a scoring mesh the user has to specify the followings Shape and name of the 3D scoring mesh Currently box is the only available shape Size of the scoring mesh Mesh size must be specified as half width similar to the arguments of G4Box Number of bins for each axes Note that too hugh number causes immense memory consumption e Optionally position and rotation of the mesh If not specified the mesh is positioned at the center of the world volume without rotation For a scoring mesh the user can have arbitrary number of quantities to be scored for each cell of the mesh For each scoring quantity the use can set one filter Please note that score filter affects on the preceding scorer Names of scorers and filters must be unique for the mesh The user can define more than one scorers of same kind with different names and most likely with different filters Defining a scoring mesh and scores in thiat mesh should terminate with score close command The follow ing sample UI commands define a scoring mesh named boxMesh 1 size of which is 2 m 2 m 2 m and sliced into 30 cells along each axes For each cell energy deposition number of steps of gamma number of steps of electron and numb
14. Locates the volume containing the specified global point This involves a traverse of the hierarchy reguiring the computation of compound transformations testing replicated and parameterised volumes etc To improve ef ficiency this search may be performed relative to the last and this is the recommended way of calling the func tion A relative search may be used for the first call of the function which will result in the search defaulting to a search from the root node of the hierarchy Searches may also be performed using a G4TouchableHistory LocateGlobalPointAndUpdateTouchableHandle First search the geometrical hierarchy like the above method LocateGlobalPointAndSetup Then use the volume found and its navigation history to update the touchable ComputeStep Computes the distance to the next boundary intersected along the specified unit direction from a specified point The point must be have been located prior to calling ComputeStep When calling ComputeStep a proposed physics step is passed If it can be determined that the first inter section lies at or beyond that distance then kInfinity is returned In any case if the returned step is greater than the physics step the physics step must be taken SetGeometricallyLimitedStep Informs the navigator that the last computed step was taken in its entirety This enables entering exiting opti misation and should be called prior to calling LocateGlobalPointAndS
15. delete pA NICE delete pSubtracted If efficiency is an issue create the objects in the constructor delete them in the destructor and draw them in your Draw method Anyway an instance of your class needs to be registered with the vis manager e g G4VisManager visManager new G4VisExecutive visManager gt Initialize visManager gt SetUserAction new StandaloneVisAction G4VisExtent 5 m 5 m 5 m 5 m 5 m 5 m 2nd argument optional then activate by adding to a scene e g control verbose 2 vis verbose c vis open OGLSXm 237 Visualization vis scene create vis scene add userAction vis scene add userAction 10 10 10 10 10 10 m vis scene add axes 0 0 0 10 m vis scene add scale 10 m vis sceneHandler attach vis viewer refresh The extent can be added on registration or on the command line or neither if the extent of the scene is set by other components Your Draw method will be called whenever needed to refresh the screen or rebuild a graphics database for any chosen viewer The scene can be attached to any scene handler and your drawing will be shown 8 5 11 Standalone Visualization The above raises the possibility of using Geant4 as a standalone graphics package without invoking the run manager The following main program together with a user visualization action and a macro file will allow you to view your drawing interactively on any of the supported graphics systems in
16. 6 B E A B a a E z Z E LZ m HE Ec 1 LL Lit ate ane art THO Bee LT T4 mae aoe nee eee M Dx 5 Dy 10 Dz 20 Dx Half length X Dy Half length Y Dz Half length Z General Ellipsoid The general ellipsoid with possible cut in Z can be defined as follows 65 Detector Definition and Response G4Ellipsoid const G4String pName G4double G4double G4double G4double G4double pxSemiAxis pySemiAxis pzSemiAxis pzBottomCut 0 pzTopCut 0 L 17 E 49 E HAM HE 7 LT gt 1 142 A 20 HT Bei z EI EE EAN 0 2227 EE EU In the picture pxSemiAxis 10 pySemiAxis 20 pzSemiAxis 50 pzBot tomCut 10 pzTopCut 40 A general or triaxial ellipsoid is a quadratic surface which is given in Cartesian coordinates by 1 0 x pxSemiAxis 2 where y pySemiAxis 2 z pzSemiAxis 2 pxSemiAxis Semiaxis in X Semiaxis in Y pySemiAxis pzSemiAxis Semiaxis in Z lower cut plane level z pzBottomCut pzTopCut upper cut plane level z Cone with Elliptical Cross Section A cone with an elliptical cross section can be defined as follows G4EllipticalCone const G4String amp G4double G4double G4double G4double pName pxSemiAxis pySemiAxis zMax pzTopCut m fy it
17. MFDet gt RegisterPrimitive scorer7 Finally to measure the flux energy per unit velocity then G4PSTrackLength scorer8 new G4PSTrackLength psName SLWE V scorer8 gt Weighted true scorer8 gt MultiplykineticEnergy true scorer8 gt DivideByVelocity true MFDet gt RegisterPrimitive scorer8 4 5 Digitization 4 5 1 Digi A hit is created by a sensitive detector when a step goes through it Thus the sensitive detector is associated to the corresponding G4LogicalVolume object s On the other hand a digit is created using information of hits and or other digits by a digitizer module The digitizer module is not associated with any volume and you have to implicitly invoke the Digitize method of your concrete G4VDigitizerModule class Typical usages of digitizer module include simulate ADC and or TDC simulate readout scheme generate raw data 127 Detector Definition and Response simulate trigger logics simulate pile up G4VDigi G4VDigi is an abstract base class which represents a digit You have to inherit this base class and derive your own concrete digit class es The member data of your concrete digit class should be defined by yourself G4VDigi has two virtual methods Draw and Print G4TDigiCollection G4TDigiCollection is a template class for digits collections which is derived from the abstract base class G4VDigiCollection G4Event has a G4DCofThisEvent object which i
18. Optional You may decide to write zip files with events and geometry separated but linked This results in a smaller zip file as the geometry is only written once Use the command vis heprep appendGeometry false Optional To close the file remove the SceneHandler use 214 Visualization vis sceneHandler remove scene handler 0 Limitations Only one SceneHandler can exist at any time connected to a single Viewer Since the HepRep format is a model rather than a view this is not a real limitation In WIRED 4 you can create as many views SceneHan dlers as you like Further information WIRED4 Plugin to the JAS3 Analysis System FRED event display HepRep graphics format http www slac stanford edu perl heprep 8 3 6 DAWN The DAWN drivers are interfaces to Fukui Renderer DAWN which has been developed by Satoshi Tanaka Minato Kawaguti et al Fukui University It is a vectorized 3D PostScript processor and so well suited to prepare technical high quality outputs for presentation and or documentation It is also useful for precise debugging of detector geometry Remote visualization off line re visualization cut view and many other useful functions of detector simulation are supported A DAWN process is automatically invoked as a co process of Geant4 when visualization is performed and 3D data are passed with inter process communication via a file or the TCP IP socket When Geant4 Visualization is
19. gt messenger class ExNO3RunAction header file source file derived from G4VUserRunAction draw detector and tracks Interactivity SetCut process on off nteractivity change detector size material magnetic field 261 Examples ExN03EventAction header file source file derived from G4VUserEventAction store trajectories print end of event information energy deposited etc ExN03SteppingAction header file source file derived from G4VUserSteppingAction collect energy deposition etc 9 1 5 Example N04 Basic concepts e Simplified collider experiment geometry Full hits digits trigger Classes main source file e construction and deletion of ExN04RunManager construction and deletion of G UI session and VisManager construction and set of user classes ExN04DetectorConstruction header file source file derived from G4VUserDetectorConstruction e construction of ExN04MagneticField definitions of mixture and compound materials material dependent CutOff simplified collider geometry with Param Replica tracker muon parametrised calorimeter replica ExNO4TrackerParametrisation header file source file derived from G4VPVParametrisation parametrised sizes ExN04CalorimeterParametrisation header file source file derived from G4VPVParametrisation parametrized position rotation ExN04MagneticField header file source
20. Alternatively you can implement an empty RegisterGraphicsSystems function and register visualiza tion drivers you want directly in your main function See Example 8 3 Example 8 3 An alternative style for the main function ffe C source codes How to register a visualization driver directly in main function G4VisManager visManager new G4VisExecutive visManager gt RegisterGraphicsSystem new MyGraphicsSystem delete visManager Alix mea end of C Do not forget to delete the instantiated Visualization Manager by yourself Note that a graphics system for Geant4 Visualization may run as a different process In that case the destructor of G4VisManager might have to ter minate the graphics system and or close the connection We recommend that the instantiation initialization and deletion of the Visualization Manager be protected by C pre processor commands as in the novice examples The C pre processor macro G4VIS_USE is automatically 209 Visualization defined unless the environment variable G4VIS NONE is set This assumes that you are compiling your Geant4 executable with the standard version of GNUmakefile found in the config directory Example 8 4 shows an example of the main function available for Geant4 Visualization Example 8 4 An example of the main function available for Geant4 Visualization C source codes An example of main for visualization include G4VisExecut
21. G4LogicalVolume logVol pPhys gt GetLogicalVolume const G4VisAttributes pVA logVol gt GetVisAttributes if pVA attribs pVA G4Colour colour 1 0 0 attribs SetColour colour attribs SetForceSolid true ff Re visualization of a selected physical volume with red color pVVisManager gt Draw pPhys attribs trans a end of C codes 8 5 7 HepRep Attributes for Hits The HepRep file formats HepRepFile and HepRepXML attach various attributes to hits such that you can view these attributes label trajectories by these attributes or make visibility cuts based on these attributes Examples of adding HepRep attributes to hit classes can be found in examples extended analysis A01 and extended runAn dEvent REO1 For example in example REOI s class REO1CalorimeterHit cc available attributes will be Hit Type Track ID ZCell ID Phi Cell ID Energy Deposited Energy Deposited by Track Position Logical Volume You can add additional attributes of your choosing by modifying the relevant part of the hit class look for the methods GetAttDefs and CreateAttV alues 8 5 8 Visualization of text In Geant4 Visualization a text i e a character string is described by class G4Text inheriting G4VMarker as well as G4Square and G4Circle Therefore the way to visualize text is the same as for hits The corresponding drawing method of G4VVisManager is 1222 Drawing methods of G4Text
22. primary event generation via particle gun ExNO5RunAction header file source file derived from G4VUserRunAction draw detector activation deactivation of parameterisation ExN05EventAction header file source file derived from G4VUserEventAction print time information 9 1 7 Example N06 Basic concepts Interactivity build messenger classes Event Gun shoot charge particle at Cerenkov Radiator and Scintillator PIIM material mixture with optical and scintillation properties Geometry volumes filled with optical materials and possessing surface properties Physics define and initialize optical processes Tracking generate Cerenkov radiation collect energy deposition to produce scintillation Hits Digi PMT as detector Visualization geometry optical photon trajectories Classes main source file main for interactive mode and batch mode via macro file random number engine construction and deletion of G4RunManager construction and set of mandatory user classes hard coded beamOn ExNO6DetectorConstruction header file source file derived from G4VUserDetectorConstruction definitions of single materials and mixtures 265 Examples generate and add Material Properties Table to materials CSG and BREP solids e G4PVPlacement with rotation definition of surfaces generate and add Material Properties Table to surfaces visualizat
23. Dynamic creation by processes Category c Particle types in this category are are not created by default but will only be created by request from processes or directly by users Each shortlived particle corresponds to one object of a class derived from G4VshortLivedParticle and it will be created dynamically during the initialization phase 5 3 2 4 G4ParticleDefinition The G4ParticleDefinition class has read only properties to characterize individual particles such as name mass charge spin and so on These properties are set during initialization of each particle Methods to get these prop erties are listed in Table 5 2 G4String GetParticleName particle name G4double GetPDGMass mass G4double GetPDGWidth decay width G4double GetPDGCharge electric charge G4double GetPDGSpin spin G4double GetPDGMagneticMoment magnetic moment 0 not defined or no magnetic mo ment G4int GetPDGiParity parity O not defined G4int GetPDGiConjugation charge conjugation 0 not defined G4double GetPDGIsospin iso spin G4double GetPDGIsospin3 3 component of iso spin G4int GetPDGiGParity G parity 0 not defined G4String GetParticleType particle type G4String GetParticleSubType particle sub type G4int GetLeptonNumber lepton number G4int GetBaryonNumber baryon number G4int GetPDGEncoding part
24. Examples Dynamic geometry setups between runs Primitive scorer and filter Derived run class and run action Table 9 1 Table 9 2 and Table 9 3 display the item charts for the examples currently prepared in the novice level ExampleN01 ExampleN02 ExampleN03 comments minimal set for geantino fixed target tracker geome EM shower in calorimeter transportation try Run main for hard coded main for interactive main for interactive batch mode mode SetCut and Process On Off Event event generator selection event generator selection event generator selection particleGun particleGun particleGun e end of event simple analysis in UserEven tAction Tracking hard coded verbose level selecting secondaries select trajectories setting Geometry geometry definition CSG geometry definition in geometry definition in cludes Parametrised vol cludes replica ume uniform magnetic field uniform magnetic field Hits Digi tracker type hits calorimeter type hits PIIM minimal particle set EM particles set EM particles set e single element material e mixtures and compound mixtures and compound elements elements Physics transportation EM physics EM physics Vis e detector amp trajectory detector amp trajectory draw drawing ing tracker type hits drawing G UI GUI selection GUI selection Global Table 9 1 The item c
25. It is possible to use the enhanced trajectory drawing functionality in compiled code as well as from commands Multiple trajectory models can be instantiated configured and registered with G4VisManager Only one model may be current For example G4VisManager visManager new G4VisExecutive visManager gt Initialize G4TrajectoryDrawByParticleID model new G4TrajectoryDrawByParticleID G4TrajectoryDrawByParticleID model2 new G4TrajectoryDrawByParticleID test modeli gt SeEBe alte cyan model gt Set gamma green model gt Set e magenta model sec Eau MEO SP OS visManager gt RegisterModel model visManager gt RegisterModel model2 visManager gt SelectTrajectoryModel model Name 8 7 5 Drawing by time To draw by time you need to use a trajectory that records the track time at the beginning and end of each step To do this write a tracking action that sets G4RichTrajectory for example include G4UserTrackingAction hh class G4Track class MyTrackingAction public G4UserTrackingAction public virtual void PreUserTrackingAction const G4Track aTrack include G4RichTrajectory hh include G4TrackingManager hh include G4IdentityTrajectoryFilter hh include G4TransportationManager hh include G4PropagatorInField hh void MyTrackingAction PreUserTrackingAction const G4Track aTrack Require rich trajectory fpTrackingManager gt SetTrajectory new G4RichTraj
26. SetCutValue sets a cut value for a particle type for a region void SetCutValue G4double aCut const G4String amp pname const G4String amp rname Invoke SetCuts for specified particle for a region If the pointer to the region is NULL the default region is used In case of Retrieve flag is ON Cut values will be retrieved from files void SetParticleCuts G4double cut G4ParticleDefinition particle G4Region region 0 Invoke SetCuts for all particles in a region void SetCutsForRegion G4double aCut const G4String amp rname Following are utility methods are obsolete void ResetCuts EE AAA TAA AAA AA TATA AAA AA EAA public Get SetApplyCuts gets sets the flag for ApplyCuts void SetApplyCuts G4bool value const G4String amp name G4bool GetApplyCuts const G4String amp name const TDM AAA VVV TA MAGE ADD TEA AA TATA AAA AA AAA TAEDA ATA VV protected do BuildPhysicsTable for make the integral schema void BuildIntegralPhysicsTable GA4VProcess G4ParticleDefinition protected Retrieve PhysicsTable from files for proccess belongng the particle Normal BuildPhysics procedure of processes will be invoked if it fails in case of Process s RetrievePhysicsTable returns false virtual void RetrievePhysicsTable G4ParticleDefinition const G4String amp directory G4bool ascii false WEE AAA AEA AA EAE TA EAA TUQUE protected adds new ProcessManager to all particles in the Par
27. The corresponding UI command can be accessed in the UI subdirectory process eLoss The following types of SetMaxEnergyForMuons G4double SetDEDXBinning G4int SetDEDXBinningForCSDARange G4int SetLambdaBinning G4int SetStepFunction G4double G4double SetRandomStep G4bool SetApplyCuts G4bool SetBuildCSDARange G4bool SetVerbose G4int const G4String name all SetLambdaFactor G4double SetLinearLossLimit G4double ActivateDeexcitation G4bool val const G4Region r 0 SetMscStepLimitation G4MscStepLimitType val SetMscLateralDisplacement G4bool val SetSkin G4double SetMscRangeFactor G4double SetMscGeomFactor G4double SetLPMFlag G4bool SetBremsstrahlungTh G4double step limitation by multiple scattering are available G4EmCalculator is a class which provides access to cross sections and stopping powers This class can be used anywhere in the user code provided the physics list has already been initialised G4State_Idle G4EmCalculator has Get methods which can be applied to materials for which physics tables are already built and Compute methods which can be applied to any material defined in the application or existing in the Geant4 internal database fSimple step limitation used in g4 7 1 version used in QGSP_EMV Physics List fUseSafety default fUseDistanceToBoundary advance method of step limitation used in EM examples required parameter skin gt 0 should be used for setup without magnetic field
28. Unless the environment variable GAVIS NONE is set to 1 setting any of the above variables sets a C pre proces sor flag of the same name Also the C pre processor flag GAVIS BUILD is set see config G4VIS_BUILD gmk which incorparates the selected driver into the Geant4 libraries 8 2 2 How to Realize Visualization Drivers in an Exe cutable You can realize and use any of the visualization driver s you want in your Geant4 executable provided they are among the set installed beforehand into the Geant4 libraries A warning will appear if this is not the case In order to realize visualization drivers you must instantiate and initialize a subclass of GaVisManager that implements the pure virtual function RegisterGraphicsSystems This subclass must be compiled in the user s domain to force the loading of appropriate libraries in the right order The easiest way to do this is to use G4VisExecut ive a provided class with included implementation G4VisExecut ive is sensitive to the G4VIS USE variables mentioned below If you do wish to write your own subclass you may do so You will see how to do this by looking at G4VisExecutive icc A typical extract is RegisterGraphicsSystem new G4DAWNFILE ifdef G4VIS_USE_OPENGLX RegisterGraphicsSystem new G4OpenGLImmediateX RegisterGraphicsSystem new G4OpenGLStoredX fendif If you wish to use G4VisExecut ive but register an additional graphics system XXX say
29. a 207 20 g mole G4Element elPb new G4Element name Lead Symbol Pb z 82 a define an Element from isotopes by relative abundance G4Isotope U5 new G4Isotope name U235 iz 92 n 235 a 235 01 g mole G4Isotope U8 new G4Isotope name U238 iz 92 n 238 a 238 03 g mole G4Element elU new G4Element name enriched Uranium symbol U ncomponents 2 elU gt AddIsotope U5 abundance 90 perCent elU gt AddIsotope U8 abundance 10 perCent cout lt lt G4Isotope GetIsotopeTable lt lt endl cout lt lt G4Element GetElementTable lt lt endl define simple materials density 2 700 g cm3 a 26 98 g mole G4Material Al new G4Material name Aluminum z 13 a density 108 Detector Definition and Response density 1 390 g cm3 a 39 95 g mole vG4Material lAr new G4Material name liquidArgon z 18 a density density 8 960 g cm3 a 63 55 g mole G4Material Cu new G4Material name Copper r Za29 ay census define a material from elements case 1 chemical molecule density 1 000 g cm3 G4Material H20 new G4Material name Water density ncomponents 2 H20 gt AddElement elH natoms 2 H20 gt AddElement elO natoms 1 density 1 032 g cm3 G4Material Sci new G4Material name Scintillator density ncomponents 2 Sci gt AddElement elC natoms 9 Sci gt AddElement elH natoms 10 densit
30. getGlobalFastSimulationManager gt CloseFastSimulation This last call will cause the G4GlobalFastSimulationManager to build the flavour dependent ghost geometries This call must be done before the RunManager closes the geometry It is foreseen that the run manager in the future will invoke the CloseFastSimulation to synchronize properly with the closing of the geometry Visualization facilities are provided for ghosts geometries After the CloseFastSimulation invocation it is pos sible to ask for the drawing of ghosts in an interactive session The basic commands are vis draw Ghosts particle name which makes the drawing of the ghost geometry associated with the particle specified by name in the command line vis draw Ghosts which draws all the ghost geometries 5 2 6 8 Gflash Parameterization This section describes how to use the Gflash library Gflash is a concrete parameterization which is based on the equations and parameters of the original Gflash package from H1 hep ex 0001020 Grindhammer amp Peters see physics manual and uses the fast simulation facilities of GEANTA described above Briefly whenever a e e particle enters the calorimeter it is parameterized if it has a minimum energy and the shower is expected to be contained in the calorimeter or parameterization envelope If this is fulfilled the particle is killed as well as all secondaries and the energy is deposited according to the Gfl
31. mu particleName mu yt pmanager gt AddProcess new G4hMultipleScattering 1 1 1 pmanager gt AddProcess new G4Mulonisation cud xs pmanager gt AddProcess new G4MuBremsstrahlung m de ws 3B pmanager gt AddProcess new G4MuPairProduction ee d else if particleName alpha particleName He3 particleName GenericIon ions with charge gt 2 pmanager gt AddProcess new G4hMultipleScattering 1 1 1 pmanager gt AddProcess new G4ionIonisation 25 2B else if particle gt IsShortLived amp amp particle gt GetPDGCharge 0 0 amp amp particle GetParticleName chargedgeantino all others charged particles except geantino and short lived pmanager gt AddProcess new G4hMultipleScattering 1 1 1 pmanager AddProcess new G4hIonisation 2 2 B Novice and extended electromagnetic examples illustrating the use of electromagnetic processes are available as part of the Geant4 release Options are available for steering the standard electromagnetic processes These options may be invoked either by UI commands or by the interface class G4EmProcessOptions This class has the following public methods SetLossFluctuations G4bool e SetSubCutoff G4bool const G4Region r 0 SetIntegral G4bool e SetMinSubRange G4double SetMinEnergy G4double e SetMaxEnergy G4double e SetMaxEnergyForCSDARange G4double 143 Tracking and Physics
32. 111 9 293 Appendix 0 04074 6 0 242746 7 0 716514 G4_DIETHYL_ETHER 0 135978 6 0 648171 8 0 215851 G4 N N DIMETHYL FORMAMIDE 0 096523 6 0 492965 7 0 191625 8 0 218887 G4 DIMETHYL SULFOXIDE 0 077403 6 0 307467 8 0 204782 6 0 410348 G4 ETHANE 0 201115 6 0 798885 G4 ETHYL ALCOHOL 0 131269 6 0 521437 8 0 347294 G4 ETHYL CELLULOSE 0 090027 6 0 585182 8 0 324791 G4 ETHYLENE 0 143711 6 0 856289 G4 EYE LENS ICRP 0 099269 6 0 19371 7 0 05327 8 0 653751 G4 FERRIC OXIDE 8 0 300567 26 0 699433 G4 FERROBORIDE 5 0 162174 26 0 837826 G4 FERROUS OXIDE 8 0 222689 26 0 777311 G4 FERROUS SULFATE 1 0 108259 7 2416 05 8 0 878636 11 2 2e 05 16 0 012968 17 3 4e 05 26 5 4e 05 G4 FREON 12 6 0 099335 9 0 314247 177 0 586418 G4 FREON 12B2 6 0 057245 9 0 181096 35 0 761659 G4 FREON 13 6 0 114983 9 0 545621 I 0 339396 G4 FREON 13B1 6 0 080659 9 0 382749 35 0 536592 G4 FREON 13I1 6 0 061309 9 0 290924 53 0 647767 G4 GADOLINIUM OXYSULFIDE 8 0 084528 6 0 08469 64 0 830782 0 Tx 71378 60 9487 66 1014 98 00125324 45 7893 62 3 69 00117497 50 1 73 2 227 i15 261 7 248 024 76 12 143 8 284 595 126 5 210 8 293 44 493 294 Appendix G4_GALLIUM_ARSENIDE 31 0 482019 33 0 517981 G4_GEL_PHOTO_EMULSION 0 08118 6 0 41606 7 0 11124 8 0 38064 6 0 01088 G4_Pyrex_Glass 5 0 0400639 8 0 539561 1 0 0281909 3 0 011644
33. 4 1 8 5 Run time commands When running in verbose mode i e the default G4VERBOSE set while installing the Geant4 kernel libraries the navigator provides a few commands to control its behavior It is possible to select different verbosity levels up to 5 with the command geometry navigator verbose verbose level or to force the navigator to run in check mode geometry navigator check mode true false The latter will force more strict and less tolerant checks in step safety computation to verify the correctness of the solids response in the geometry By combining check mode with verbosity level 1 additional verbosity checks on the response from the solids can be activated 4 1 8 6 Setting Geometry Tolerance to be relative The tolerance value defining the accuracy of tracking on the surfaces is by default set to a reasonably small value of 10E 9 mm Such accuracy may be however redundant for use on simulation of detectors of big size or macroscopic dimensions Since release 9 0 it is possible to specify the surface tolerance to be relative to the extent of the world volume defined for containing the geometry setup The class G4Geomet ryManager can be used to activate the computation of the surface tolerance to be relative to the geometry setup which has been defined It can be done this way 97 Detector Definition and Response G4GeometryManager GetInstance gt SetWorldMaximumExtent WorldExtent
34. 989 6 HA ES 48 3 2949 86 8 539 3 468 3 136 4 292 Appendix 10 G4_CALCIUM_FLUORIDE 9 0 486659 20 0 513341 G4_CALCIUM_OXIDE 8 0 285299 20 0 714701 G4_CALCIUM_SULFATE 8 0 470095 6 0 235497 20 0 294408 G4_CALCIUM_TUNGSTATE 8 0 22227 20 0 139202 74 0 638528 G4 CARBON DIOXIDE CO_2 6 0 272916 8 0 727084 G4 CARBON TETRACHLORIDE 6 0 078083 7 0 921917 G4 CELLULOSE CELLOPHANE 0 062162 6 0 444462 8 0 493376 G4 CELLULOSE BUTYRATE 0 067125 6 0 545403 8 0 387472 G4 CELLULOSE NITRATE 0 029216 6 0 271296 7 0 121276 8 0 578212 G4 CERIC SULFATE d 0 107596 7 0 0008 8 0 874976 16 0 014627 58 0 002001 G4 CESIUM FLUORIDE 9 0 125069 55 0 874931 G4 CESIUM IODIDE 53 0 488451 55 0 511549 G4 CHLOROBENZENE 0 044772 6 0 640254 7 0 314974 G4 CHLOROFORM 0 008443 6 0 100613 7 0 890944 G4 CONCRETE 0 0 6 0 001 8 0 529107 1 0 016 2 0 002 3 0 033872 4 0 337021 9 0 013 20 0 044 26 0 014 G4 CYCLOHEXANE 0 143711 6 0 856289 G4 1 2 DICHLOROBENZENE 0 027425 6 0 490233 7 0 482342 G4 DICHLORODIETHYL ETHER 0 0563811 6 0 335942 8 0 111874 7 0 495802 G4 1 2 DICHLOROETHANE 0 8 96 062 00184212 594 42 49 x03 115 ol 1058 4832 ETTO 13 L 3048 2199 2351 176 1 152 3 395 85 166 3 77 6 74 6 87 76 7 440 7 553 1 89 1 156 135 2 56 4 106 5 103 3
35. But this subset contains all the most interesting use cases The tracking cost for navigating in a Boolean solid in the current implementation is proportional to the number of constituent solids So care must be taken to avoid extensive unecessary use of Boolean solids in performance critical areas of a geometry description where each solid is created from Boolean combinations of many other solids Examples of the creation of the simplest Boolean solids are given below G4Box box new G4Box Box 20 mm 30 mm 40 mm G4Tubs cyl new G4Tubs Cylinder 0 50 mm 50 mm 0 twopi r 0 mm gt 50 mm 11 28 50 mm 50 mm MORI Quem 2 51 G4UnionSolid union new G4UnionSolid Box Cylinder box cyl G4IntersectionSolid intersection new G4IntersectionSolid Box Cylinder box cyl G4SubtractionSolid subtraction new G4SubtractionSolid Box Cylinder box cyl where the union intersection and subtraction of a box and cylinder are constructed The more useful case where one of the solids is displaced from the origin of coordinates also exists In this case the second solid is positioned relative to the coordinate system and thus relative to the first This can be done in two ways Either by giving a rotation matrix and translation vector that are used to transform the coordinate system of the second solid to the coordinate system of the first solid This is called the passive method Or by creating a tr
36. By default the track weight is not taken into account but could be used as a multiplier of each step length if the Weighted method of this class object is invoked Deposited energy scorers G4PSEnergyDeposit This scorer stores a sum of particles energy deposits at each step in the cell The particle weight is multiplied at each step G4PSDoseDeposit In some cases dose is a more convenient way to evaluate the effect of energy deposit in a cell than simple deposited energy The dose deposit is defined by the sum of energy deposits at each step in a cell divided by the mass of the cell The mass is calculated from the density and volume of the cell taken from the methods of G4VSolid and G4LogicalVolume The particle weight is multiplied at each step Current and flux scorers There are two different definitions of a particle s flow for a given geometry One is a current and the other is a flux In our scorers the current is simply defined as the number of particles with the particle s weight at a certain surface or volume while the flux takes the particle s injection angle to the geometry into account The current and flux are usually defined at a surface but volume current and volume flux are also provided G4PSFlatSurfaceCurrent Flat surface current is a surface based scorer The present implementation is limited to scoring only at the Z surface of a G4Box solid The quantity is defined by the number of tracks that reach the surface
37. EIER 40 34 1 Basic concept of Run cette ssa RP ES Fe bara SE eg ESE 40 3 4 2 Geant4 as a state machine sssessesesee em em e mH aaa aaa aaa aaa 42 3 4 3 User s hook for state change 5 inier eR ERE ERR 42 3 4 4 Customizing the Run Manager sese HI em eme hee 43 3 5 ane T 45 3 5 1 Representation of an event orars cee eme enm en aaa enm aaa 45 35 2 Structire of n event i noe deer HO HR ed Ee epe si he Ere Rees Ere Reed ue 45 3 5 3 Mandates of G4EventManager ee emen mee mee hehe rre 45 3 5 4 Stacking mechanism 2i tnr E Et es atlas ape Pare reste ret bar ORE 45 3 6 Event Generator Interface sosina beige eee speed K ai ye ceste prec dete ve cesi voy a 46 3 6 1 Structure of a primary event seeded bee PER PEEL ER sai 46 3 6 2 Interface to a primary generator 0 eect e em emm enm hent eere 47 3 6 3 Event overlap using multiple generators sse 48 3 7 Event Biasing Techniques nsession eS HER eate ERE erede eer tee eerie EET Pre Een 48 3 7 1 Scoring Geometrical Importance Sampling and Weight Roulette 48 3 7 2 Physics Bas d Bi simg oett eee leto tele temer hi ere ria rire Pede 55 4 Detector Definition and Response 1 ie ee ER EOD e TERR E RE rU IRE eee epa e Porc ES 58 4 1 Geometry uerit Et ge tete gebe eoc rie euet E IEEE detain deste cse SEES Te peb ruin 58 4 1 1 Introduction 24 sans kata iso RD rt ERI RETI a aa sai 58 4 12 Soli
38. G4UIcommand command G4String newValues if command listCmd particleTable gt dumpTable else if command particleCmd G4ParticleDefinition pd particleTable gt findParticle newValues if pd NULL fParticleGun SetParticleDefinition pd else if command directionCmd fParticleGun SetParticleMomentumDirection directionCmd GetNew3VectorValue newValues else if command energyCmd fParticleGun 5SetParticleEnergy energyCmd gt GetNewDoubleValue newValues else if command positionCmd fParticleGun 5SetParticlePosition directionCmd gt GetNew3VectorValue newValues else if command timeCmd fParticleGun SetParticleTime timeCmd gt GetNewDoubleValue newValues G4String G4ParticleGunMessenger GetCurrentValue G4UIcommand command G4String cv if command directionCmd cv directionCmd ConvertToString fParticleGun gt GetParticleMomentumDirection else if command energyCmd cv energyCmd gt ConvertToString fParticleGun gt GetParticleEnergy Gev else if command positionCmd cv positionCmd gt ConvertToString fParticleGun gt GetParticlePosition cm else if command timeCmd cv timeCmd ConvertToString fParticleGun gt GetParticleTime ns else if command particleCmd update candidate list G4String candidateList G4int nPtcl particleTable entries for G4int i 0 i lt nPt
39. It is foreseen to allow the setting of a NULL pointer in this case of the parallel geometry inthe construct method of your concrete G4VUserDetectorConstruction class instantiate your Readout geometry MyROGeom ROgeom new MyROGeom ROName build it ROgeom buildROGeometry That will invoke your build method Instantiate the sensitive detector which will receive the ROGeom pointer MySensitive and add this sen sitive to the G4SDManager Associate this sensitive to the volume s of the tracking geometry as usual Associate the sensitive to the Readout geometry MySensitive gt SetROgeomet ry ROgeom 4 4 4 G4SDManager G4SDManager is the singleton manager class for sensitive detectors Activation inactivation of sensitive detectors The user interface commands activate and inactivate are available to control your sensitive detectors For example hits activate detector_name hits inactivate detector name where detector name can be the detector name or the category name For example if your EM calorimeter is named myDet myCal myEMcal hits inactivate myCal will inactivate all detectors belonging to the myCa1 category Access to the hit collections 121 Hit collections are accessed for various cases Detector Definition and Response Digitization Event filtering in G4VUserStackingAction End of event simple analysis Drawing printing hits The follow
40. Static const G4Colour amp Yellow For example a local G4Colour could be constructed as G4Colour myRed G4Colour Red 239 Visualization After instantiation of a G4Colour object you can access to its components with the following access functions G4double G4Colour GetRed const Get the red component G4double G4Colour GetGreen const Get the green component G4double G4Colour GetBlue const Get the blue component 8 6 2 2 Colour Map G4Colour also provides a static colour map giving access to predefined G4Colour s through a G4String key The default mapping is G4String G4Colour white G4Colour White gray G4Colour Gray grey G4Colour Grey black G4Colour Black red G4Colour Red green G4Colour Green blue G4Colour Blue cyan G4Colour Cyan magenta G4Colour Magenta yellow G4Colour Yellow Colours can be retrieved through the GetColour method bool G4Colour GetColour const G4String amp key G4Colour amp result For example G4Colour myColour G4Colour Black if G4Colour GetColour red myColour Successfully retrieved colour red myColour is now red else Colour did not exist in map myColour is still black If the key is not registered in the colour map a warning message is printed and the input colour is not changed The colour map is case insensitive It is also possible to load user defined G4Colou
41. The G4VFastSimulationModel has three pure virtual methods which must be overriden in your concrete class G4VFastSimulationModel const G4String amp aName Here aName identifies the parameterisation model G4bool ModelTrigger const G4FastTrack amp You must return true when the dynamic conditions to trigger your parameterisation are ful filled G4FastTrack provides access to the current G4Track gives simple access to the current root G4Logical Volume related features its G4VSolid and G4AffineTransform references between the global and the root G4LogicalVolume local coordinates systems and simple access to the position and momentum ex pressed in the root G4LogicalVolume coordinate system Using these quantities and the G4VSolid methods you can for example easily check how far you are from the root G4Logical Volume boundary G4bool IsApplicable const G4ParticleDefinition amp In your implementation you must return true when your model is applicable to the G4ParticleDefinition passed to this method The G4ParticleDefinition provides all intrinsic particle information mass charge spin name If you want to implement a model which is valid only for certain particle types it is recommended for effi ciency that you use the static pointer of the corresponding particle classes As an example in a model valid for gammas only the IsApplicable method should take the form include G4Gamma hh G4bool MyGammaModel IsAp
42. This is a G amp UIcommand derived class which takes one string type parameter G4UIcmdWithAString char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramName G4bool omittable Define the name of the string parameter and set the omittable flag If omittable is true you should define the default value using the next method 197 Communication and Control void SetDefaultValue char defVal Define the default value of the string parameter void SetCandidates char candidateList Define a candidate list which can be taken by the parameter Each candidate listed in this list should be separated by a single space If this candidate list is given a string given by the user but which is not listed in this list will be rejected G4UIcmdWith3Vector This is a G4UIcommand derived class which takes one three vector parameter e G4UIcmdWith3Vector char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramNamX char paramNamY char paramNamZ G4bool omittable Define the names of each component of the three vector and set the omittable flag If omittable is true you should define the default value using the next method e void SetDefaultValue G4ThreeVector defVal Define the default value of
43. and e region gt SetProductionCuts cuts regName calorimeter region G4RegionStore GetInstance gt GetRegion regName cuts new G4ProductionCuts cuts gt SetProductionCut 0 01 mm G4ProductionCuts Get Index gamma cuts gt SetProductionCut 0 1 mm G4ProductionCuts GetIndex e cuts gt SetProductionCut 0 1 mm G4ProductionCuts GetIndex e region gt SetProductionCuts cuts 5 6 Physics Table 5 6 1 General Concepts In Geant4 physics processes use many tables of cross sections energy losses and other physics values Before the execution of an event loop the BuildPhysicsTable method of G4VProcess is invoked for all processes and cross section tables are prepared Standard electromagnetic processes calculate cross section and or energy loss values for each material and for each production cut value assigned to each material A change in production cut values therefore require these cross sections to be re calculated Cross sections for hadronic processes do not depend on the production cut The G4PhysicsTable class is used to handle cross section tables G4PhysicsTable is a collection of instances of G4PhysicsVector and derived classes each of which has cross section values for a particle within a given energy range traveling in a material 5 6 2 Material Cuts Couple Users can assign different production cuts to different regions see Section 5 5 This means that if the same
44. bindings a la tcsh or bash A move cursor to the top B backward cursor LEFT cursor C except Windows terminal abort a run soft abort during event processing A program will be terminated while accepting a user com mand D delete exit show matched list E move cursor to the end F forward cursor RIGHT cursor K clear after the cursor N next command DOWN cursor P previous command UP cursor TAB command completion Getting Started with Geant4 Running a Simple Example DEL backspace BS backspace In addition the following string substitutions are supported Ps current application status Jol current working directory oh history number 2 8 2 2 G4UIXm G4UlXaw and G4UIWin32 classes These interfaces are versions of G4Ulterminal implemented over libraries Motif Athena and WIN32 respectively G4UIXm uses the Motif XmCommand widget G4UIXaw the Athena dialog widget and G4UIWin32 the Win dows edit component to do the command capturing These interfaces are useful if working in conjunction with visualization drivers that use the Xt library or the WIN32 one A command box is at disposal for entering or recalling Geant4 commands Command completion by typing amp ldquo TAB amp rdquo key is available on the command line The shellcommands exit cont help Is cd are also supported A menu bar could be customized through the AddMenu and AddButton method Ex gui
45. by aseries of conical sections with the same axis contiguous along it The polyconical solid GABREPSolidPCone is a shape defined by a set of inner and outer conical or cylindrical surface sections and two planes perpendicular to the Z axis Each conical surface is defined by its radius at two different planes perpendicular to the Z axis Inner and outer conical surfaces are defined using common Z planes G4BREPSolidPCone const G4String amp pName G4double start angle G4double opening angle G4int num_z_planes sections G4double z_start const G4double z_values const G4double RMIN const G4double RMAX The conical sections do not need to fill 360 degrees but can have a common start and opening angle start_angle starting angle opening_angle opening angle num_z_planes number of planes perpendicular to the z axis used z start starting value of Z z values Z coordinates of each plane RMIN radius of inner cone at each plane RMAX radius of outer cone at each plane 73 Detector Definition and Response The polygonal solid GGBREPSolidPolyhedra is a shape defined by an inner and outer polygonal surface and two planes perpendicular to the Z axis Each polygonal surface is created by linking a series of polygons created at different planes perpendicular to the Z axis All these polygons all have the same number of sides sides and are defined at the same Z planes for both inner and o
46. classes derived from G4VDecayChannel Default decay modes are created in the constructors of particle classes For example the de cay table of the neutral pion has G4PhaseSpaceDecayChannel and G4DalitzDecayChannel as follows create a decay channel G4VDecayChannel mode pi0 gt gamma gamma mode new G4PhaseSpaceDecayChannel pi0 0 988 2 gamma gamma table gt Insert mode pi0 gamma e e mode new G4DalitzDecayChannel pi0 0 012 e e 156 Tracking and Physics table gt Insert mode Decay modes and branching ratios defined in Geant4 are listed in Section 5 3 2 5 2 3 3 Pre assigned Decay Modes by Event Generators Decays of heavy flavor particles such as B mesons are very complex with many varieties of decay modes and decay mechanisms There are many models for heavy particle decay provided by various event generators and it is impossible to define all the decay modes of heavy particles by using G4VDecayChannel In other words decays of heavy particles cannot be defined by the Geant4 decay process but should be defined by event generators or other external packages Geant4 provides two ways to do this pre assigned decay mode and external decayer In the latter approach the class G4VExtDecayer is used for the interface to an external package which defines decay modes for a particle If an instance of G4VExtDecayer is attached to G4Decay daughter particles will be generated by
47. const G4String Name G4FieldManager pFieldMgr 0 G4VSensitiveDetector pSDetector 0 G4UserLimits pULimits 0 G4bool Optimise true The logical volume provides a way to estimate the mass of a tree of volumes defining a detector or sub detector This can be achieved by calling the method 76 Detector Definition and Response G4double GetMass G4bool forced false The mass of the logical volume tree is computed from the estimated geometrical volume of each solid and material associated with the logical volume and its daughters Note that this computation may require a considerable amount of time depending on the complexity of the geometry tree The returned value is cached by default and can be used for successive calls unless recomputation is forced by providing t rue for the boolean argument forced in input Computation should be forced if the geometry setup has changed after the previous call Finally the Logical Volume manages the information relative to the Envelopes hierarchy required for fast Monte Carlo parameterisations Section 5 2 6 4 1 3 1 Sub detector Regions In complex geometry setups such as those found in large detectors in particle physics experiments it is useful to think of specific Logical Volumes as representing parts sub detectors of the entire detector setup which perform specific functions In such setups the processing speed of a real simulation can be increased by assigning specific production
48. relations The class categories and their relations are presented by a class category diagram The class category diagram designed for Geant4 is shown in the figure below Each box in the figure represents a class category and a uses relation by a straight line The circle at an end of a straight line means the class category which has this circle uses the other category 7 Figure 3 1 Geant4 class categories The file organization of the Geant4 codes follows basically the structure of this class cateogory This User s Manual is also organized according to class categories In the development and maintenance of Geant4 one software team will be assigned to a class category This team will have a responsibility to develop and maintain all classes belonging to the class category 3 1 2 Class categories in Geant4 The following is a brief summary of the role of each class category in Geant4 31 Toolkit Fundamentals 1 Run and Event These are categories related to the generation of events interfaces to event generators and any secondary particles produced Their roles are principally to provide particles to be tracked to the Tracking Management 2 Tracking and Track These are categories related to propagating a particle by analyzing the factors limiting the step and applying the relevant physics processes The important asp
49. rotD3 G4ReflectX3D reflection G4Transform3D transform translation rotation reflection G4ReflectionFactory Instance gt Place transform the transformation with reflection Calorimeter the actual name logicCalor the logical volume logicHall the mother volume false no boolean operation 1 copy number false no overlap check triggered Replicate layers G4ReflectionFactory Instance Replicate Layer layer name logicLayer layer logical volume defined elsewhere logicCalor its mother kXAxis axis of replication 5 number of replica ZORE width of replica 4 1 8 The Geometry Navigator Navigation through the geometry at tracking time is implemented by the class G4Navigator The navigator is used to locate points in the geometry and compute distances to geometry boundaries At tracking time the navigator is intended to be the only point of interaction with tracking Internally the G4Navigator has several private helper utility classes G4NavigationHistory stores the compounded transformations replication parameterisation information and volume pointers at each level of the hierarchy to the current location The volume types at each level are also stored whether normal placement replicated or parameterised G4NormalNavigation provides location amp distance computation functions for geometries containing place ment volumes with no voxels G4Voxe
50. theParticlelterator gt reset while theParticleIterator G4ParticleDefinition particle theParticlelterator gt value G4ProcessManager pmanager particle GetProcessManager G4String particleName particle gt GetParticleName if theCerenkovProcess gt IsApplicable particle pmanager gt AddContinuousProcess theCerenkovProcess 5 2 5 2 Generation of Photons in processes electromagnetic xrays Scintillation Every scintillating material has a characteristic light yield SCINTILLATIONYIELD and an intrinsic resolu tion RESOLUTIONSCALE which generally broadens the statistical distribution of generated photons A wider intrinsic resolution is due to impurities which are typical for doped crystals like Nal TI and CsI TI On the other hand the intrinsic resolution can also be narrower when the Fano factor plays a role The actual num ber of emitted photons during a step fluctuates around the mean number of photons with a width given by ResolutionScale sqrt MeanNumberOfPhotons The average light yield MeanNumberOfPho tons has a linear dependence on the local energy deposition but it may be different for minimum ionizing and non minimum ionizing particles A scintillator is also characterized by its photon emission spectrum and by the exponential decay of its time spec trum In GEANTA the scintillator can have a fast and a slow component The relative strength of the fast component as a
51. virtual void G4VVisManager Draw const G4Text amp The real implementation of this method is described in class G4VisManager 8 5 9 Visualization of polylines and tracking steps Polylines i e sets of successive line segments are described by class G4Polyline For G4Polyline the following drawing method of class G4VVisManager is prepared f fm A drawing method of G4Polyline virtual void G4VVisManager Draw const G4Polyline The real implementation of this method is described in class G4VisManager Using this method C source codes to visualize G4Polyline are described as follows 235 Visualization Tal C source code How to visualize a polyline G4VVisManager pVVisManager G4VVisManager GetConcreteInstance if pVVisManager G4Polyline polyline AEAN C source codes to set vertex positions color etc pVVisManager gt Draw polyline end of C source codes Tracking steps are able to be visualized based on the above visualization of G4Polyline You can visualize track ing steps at each step automatically by writing a proper implementation of class MySteppingAction inheriting G4UserSteppingAction and also with the help of the Run Manager First you must implement a method MySteppingAction UserSteppingAction A typical imple mentation of this method is as follows ie a C source code An example of visualizing tracking steps void MySteppingAction UserSteppi
52. vis viewer reset vis viewer set style wireframe vis viewer set viewpointThetaPhi 45 45 vis viewer zoom 15 run beamOn 2 Set the drawing style to surface Candidates wireframe surface vis viewer set style surface Visualize plural events bird s eye view again with another drawing style surface run beamOn 2 itiiiitiiiiiiiiki END Of vis2 mac H HEEEEE EH HH HEHE EE 2 10 6 For More Information on Geant4 Visualization See the Chapter 8 Visualization part of this user guide 30 Chapter 3 Toolkit Fundamentals 3 1 Class Categories and Domains 3 1 1 What is a class category In the design of a large software system such as Geant4 it is essential to partition it into smaller logical units This makes the design well organized and easier to develop Once the logical units are defined independent to each other as much as possible they can be developed in parallel without serious interference In object oriented analysis and design methodology by Grady Booch Booch1994 class categories are used to create logical units They are defined as clusters of classes that are themselves cohesive but are loosely coupled relative to other clusters This means that a class category contains classes which have a close relationship for example the has a relation However relationships between classes which belong to different class categories are weak i e only limitted classes of these have uses
53. 0 0008 6 0 00225 7 0 00266 9 0 00194 20 9e 05 26 0 00037 30 1e 05 G4 M3 WAX ds 0 114318 6 0 655824 8 0 0921831 12 0 134792 20 0 002883 G4 MAGNESIUM CARBONATE 6 0 142455 8 0 569278 2 0 288267 G4 MAGNESIUM FLUORIDE 9 0 609883 2 0 390117 G4 MAGNESIUM OXIDE 8 0 396964 2 0 603036 G4 MAGNESIUM TETRABORATE 5 0 240837 8 0 62379 2 0 135373 G4_MERCURIC_IODIDE 53 0 55856 80 0 44144 G4_METHANE 0 251306 6 0 748694 G4_METHANOL 0 125822 6 0 374852 8 0 499326 G4_MIX_D_WAX 0 13404 6 0 77796 8 0 03502 2 0 038594 22 0 014386 G4_MS20_TISSUE 0 081192 6 0 583442 7 0 017798 8 0 186381 2 0 130287 0 0009 G4_MUSCLE_SKELETAL_ICRP 22 23s 1 635 82 494 44 05 05 958 58 53 36 000667151 7914 99 04 94 36 485 94 75 67 18 34 43 08 684 41 67 60 75 755 296 Appendix 0 100637 6 0 10783 7 0 02768 8 0 754773 1 0 00075 2 0 00019 5 0 0018 6 0 00241 7 0 00079 9 0 00302 20 3e 05 26 4e 05 30 5e 05 9 G4 MUSCLE STRIATED ICRU 1 04 74 0 101997 6 0 123 7 0 035 8 0 729003 1 0 0008 2 0 0002 5 0 002 6 0 005 9 0 003 4 G4_MUSCLE_WITH_SUCROSE LI 74 0 0982341 6 0 156214 7 0 03545 8 0 71010 4 G4 MUSCLE WITHOUT SUCROSE 1 07 74 0 101969 6 0 120058 7 0 03545 8 0 742522 2 G4_NAPHTHALENE 1 145 68 0 062909 6 0 93709 4 G4_NITROBENZENE 1 19867 T7545 0 04
54. 0 58842 G4_BENZENE 1 0 077418 6 0 922582 G4_BERYLLIUM_OXIDE 4 0 36032 8 0 63968 G4_BGO 8 0 154126 32 0 17482 83 0 671054 G4_BLOOD_ICRP o 0 3 0010967 43 5 92 00120479 42 97 000826019 0235 283 45 25 89 87865 01 13 06 58 qs 63 85 vb 145 63 531 66 69 85 72 375 285 63 93 534 754 291 Appendix 0 101866 6 0 10002 7 0 02964 8 0 759414 1 0 00185 2 4e 05 4 3e 05 5 0 00035 6 0 00185 7 0 00278 9 0 00163 20 6e 05 26 0 00046 30 1e 05 8 G4 BONE COMPACT ICRU 0 063984 6 0 278 7 0 027 8 0 410016 2 0 002 5 0 07 6 0 002 20 0 147 9 G4 BONE CORTICAL ICRP 0 047234 6 0 14433 7 0 04199 8 0 446096 2 0 0022 5 0 10497 6 0 00315 20 0 20993 30 0 0001 2 G4_BORON_CARBIDE 5 0 78261 6 0 21739 2 G4_BORON_OXIDE 5 0 310551 8 0 689449 13 G4_BRAIN_ICRP 0 110667 6 0 12542 7 0 01328 8 0 737723 1 0 00184 2 0 00015 5 0 00354 6 0 00177 d 0 00236 9 0 003 20 9e 05 26 5e 05 30 1e 05 2 G4_BUTANE 0 173408 6 0 826592 3 G4_N BUTYL_ALCOHOL 0 135978 6 0 648171 8 0 215851 5 G4_C 552 0 02468 6 0 501611 8 0 004527 9 0 465209 4 0 003973 2 G4_CADMIUM_TELLURIDE 48 0 468355 52 0 531645 3 G4_CADMIUM_TUNGSTATE 8 0 177644 48 0 312027 74 0 510329 3 G4 CALCIUM CARBONATE 6 0 120003 8 0 479554 20 0 400443 1 812 0 00249343 0 8098 91 9 106 4 84 7
55. 1 Print a constituent The following shows how to print a constituent G4cout lt lt elU lt lt endl G4cout lt lt Air lt lt endl 110 Detector Definition and Response 4 2 4 2 Print the table of materials The following shows how to print the table of materials G4cout lt lt G4Material GetMaterialTable lt lt endl 4 3 Electromagnetic Field 4 3 1 An Overview of Propagation in a Field Geant4 is capable of describing and propagating in a variety of fields Magnetic fields electric fields and electro magnetic uniform or non uniform can specified for a Geant4 setup The propagation of tracks inside them can be performed to a user defined accuracy In order to propagate a track inside a field the equation of motion of the particle in the field is integrated In general this is done using a Runge Kutta method for the integration of ordinary differential equations However for specific cases where an analytical solution is known it is possible to utilize this instead Several Runge Kutta methods are available suitable for different conditions In specific cases such as a uniform field where the ana lytical solution is known different solvers can also be used In addition when an approximate analytical solution is known it is possible to utilize it in an iterative manner in order to converge to the solution to the precision required This latter method is currently implemented and can be used partic
56. 27 2 10 5 Sample Visualization Sessions c secssesneseeereeesce sree saaa saaa saaa saaa aaa 28 Geant4 User s Guide for Application Developers 2 10 6 For More Information on Geant4 Visualization eee 30 3 Toolkit Fundamentals eim et re E a boing des D asa 31 3 1 Class Categories and Domains sesh nuserie seser a e e aaa aaa nhe mee hee hen nennen 31 3 1 1 What is a Class Category ius anas sis ss te ERR EVE ss REPRE PERDERE 31 3 1 2 Class categories in Geantd irren eiee o E E plebe a a a s 31 3 2 Global Usage Classes s o sas sai erp tb nia oi bad o sa Aa er k a pa ab 32 3 2 1 Signature of Geant4 classes lt aa aaa aaa aaa aaa IH seca aa aaa aaa 33 3 2 2 The HEPRandom module in CLHBP reden mede i si ss i 33 3 2 3 The HEPNumerics module sisses essien se aaa aaa aa aaa III aa aaa aaa aaa A e aaa 36 3 2 4 General management classes cett ette tree a a a a RR RERO TS 37 3 3 System Of UNIS seeker a serrer ETE ree Te petes i oye ener ter sete tae ye dert is nea RE 38 3 3 T Basic nits 2L erre e er Ea REESE a EEEE PEIES E nSP EEPE 38 3 3 2 Input your data tecto iuit eee ent ee Ee XH e ii eects laces 39 3 3 37 Output your data s ete c t Pte te rab ces deter area ia e de raga det 39 3 3 4 Introduce new units Ls is iii se Reese voce EE eth dis eee se Ure pe eee o UIS 40 3 3 5 Print tbe list of Units derer re a LER EE Rer RP Re HR ERES 40 32L Run ueeseuseuene Reip euadere
57. 3 3 2 Input your data 3 3 2 1 Avoid hard coded data You must give the units for the data you are going to introduce G4double Size 15 km KineticEnergy 90 3 GeV density 11 mg cm3 Indeed the full Geant4 code is written respecting these specifications and this makes it independent of the units chosen by the user If the units are not specified it is understood that the data is implicitly in the internal G4 system but this is strongly discouraged If the data set comes from an array or from an external file it is strongly recommended to set the units as soon as the data are read before any treatment For instance Eor int J 0 7 jMa gt E 6 OS SS ec E 16 Gj s mi libart my calculations 3 3 2 2 Interactive commands Some built in commands from the User Interface UI also require the units to be specified For instance gun energy 15 2 kev gun position 3 2 7 meter If the units are not specified or are not valid the command is refused 3 3 3 Output your data You can output your data with the units you wish To do so it is sufficient to divide the data by the corresponding unit G4cout lt lt KineticEnergy keV lt lt keV G4cout lt lt density g cm3 ae our emat Of course G4cout lt lt KineticEnergy will print the energy in the internal units system There is another way to output your data Let Geant4 choose the most appropriate units for the actual numerical value of your da
58. 4 0 377219 9 0 00332099 G4 GLASS LEAD 8 0 156453 4 0 080866 22 0 008092 33 0 002651 82 0 751938 G4 GLASS PLATE 8 0 4598 1 0 0964411 4 0 336553 20 0 107205 G4 GLUCOSE 0 071204 6 0 363652 8 0 565144 G4 GLUTAMINE 0 0689651 6 0 410926 7 0 191681 8 0 328427 G4 GLYCEROL 1 0 0875539 6 0 391262 8 0 521184 G4 GUANINE 2 0 033346 6 0 39738 7 0 463407 8 0 105867 G4 GYPSUM 0 023416 8 0 557572 6 0 186215 20 0 232797 G4 N HEPTANE 0 160937 6 0 839063 G4 N HEXANE 0 163741 6 0 836259 G4 KAPTON 0 026362 6 0 691133 7 0 07327 8 0 209235 G4 LANTHANUM OXYBROMIDE 8 0 068138 35 0 340294 57 0 591568 G4 LANTHANUM OXYSULFIDE 8 0 0936 16 0 093778 SW 0 812622 G4 LEAD OXIDE 8 0 071682 82 0 928318 G4 LITHIUM AMIDE An 0 087783 3 0 302262 7 0 609955 G4_LITHIUM_CARBONATE lis 6 54 31 2914 23 722 54 46 2613 58 32 68376 6603 42 28 86 53 T8 si 384 74 134 526 145 77 Te 425 75 129 54 54 TO 439 421 766 25 87 295 Appendix 13 13 3 0 187871 6 0 16255 8 0 649579 G4_LITHIUM_FLUORIDE 3 0 267585 9 0 732415 G4_LITHIUM_HYDRIDE 0 126797 3 0 873203 G4_LITHIUM_IODIDE 3 0 051858 53 0 948142 G4_LITHIUM_OXIDE 3 0 46457 8 0 53543 G4 LITHIUM TETRABORATE 3 0 082085 5 0 25568 8 0 662235 G4 LUNG ICRP 0 101278 6 0 10231 7 0 02865 8 0 757072 1 0 00184 p 0 00073 5
59. 54 Toolkit Fundamentals The weight roulette concept Weight roulette takes into account the importance Ic of the current cell and the importance Is of the cell in which the source is located by using the ratio R Is Ic Weight roulette uses a relative minimal weight limit and a relative survival weight When a particle falls below the weight limit Russian roulette is applied If the particle survives tracking will be continued and the particle weight will be set to the survival weight The weight roulette uses the following parameters with their default values wsurvival 0 5 wlimit 0 25 isource 1 The following algorithm is applied If a particle weight w is lower than R wlimit the weight of the particle will be changed to ws wsurvival R the probability for the particle to survive is p w ws 3 7 2 Physics Based Biasing Geant4 supports physics based biasing through a number of general use built in biasing technigues A utility class G4WrapperProcess is also available to support user defined biasing 3 7 2 1 Built in Biasing Options 3 7 2 1 1 Primary Particle Biasing Primary particle biasing can be used to increase the number of primary particles generated in a particular phase space region of interest The weight of the primary particle is modified as appropriate A general implementation is provided through the G4GeneralParticleSource class It is possible to bias position angular and energy
60. Al G4Box ghostSolid new G4Box GhostdBox 60 cm 60 cm 60 cm G4LogicalVolume ghostLogical new G4LogicalVolume ghostSolid 0 GhostLogical 0 0 0 new G4PVPlacement 0 G4ThreeVector ghostLogical GhostPhysical worldLogical 0 0 b In case the user needs to define more than one parallel worlds each of them must be implemented through its dedicated class Each parallel world should be registered to the mass geometry class using the method Regis terParallelWorld available through the class GAVUserDetectorConstruction The registration must be done before the mass world is registed to the G4RunManager Example 4 19 Typical implementation in the main to define a parallel world RunManager construction G4RunManager runManager new G4RunManager mass world MyDetectorConstruction massWorld new MyDetectorConstruction parallel world massWorld gt RegisterParallelWorld new MyParallelWorld ParallelScoringWorld set mass world to run manager runManager gt SetUserInitialization massWorld 4 7 3 Detector sensitivity in a parallel world Any kind of G4VSensitiveDetector object can be defined in volumes in a parallel world exactly at the same manner for the mass geometry Once the user defines the sensitive detector in a parallel world he she must define a process which takes care of these detectors The G4ParallelWorldScoringProcess is the class provided for this
61. Cuts method of G4VUserPhysicsList Section 5 5 discusses threshold and tracking cuts in detail 2 4 2 1 Setting the cuts Production threshold values should be defined in SetCuts which is a pure virtual method of the G4VUserPhysicsList class Construction of particles materials and processes should precede the invocation of SetCuts G4RunManager takes care of this sequence in usual applications The idea of a unique cut value in range is one of the important features of Geant4 and is used to handle cut values in a coherent manner For most applications users need to determine only one cut value in range and apply this value to gammas electrons and positrons alike In such a case the SetCutsWithDefault method may be used It is provided by the G4VuserPhysicsList base class which has a defaultCutValue member as the default range cut off value SetCutsWithDefault uses this value It is possible to set different range cut values for gammas electrons and positrons and also to set different range cut values for each geometrical region In such cases however one must be careful with physics outputs because Geant4 processes especially energy loss are designed to conform to the unique cut value in range scheme Example 2 14 Set cut values by using the default cut value void ExN04PhysicsList SetCuts the G4VUserPhysicsList SetCutsWithDefault method sets fl the default cut value for all particle types SetCutsW
62. E Re se E RE E Pone ERE sa sa ERR dET 248 8 8 1 Controlling from Commands sse emm ehem here 249 8 82 Example commands iskisti ka ba ui a a rA Oe ttr E i pes beri ges 249 8 5 3 Ait Filtering 1er e Ta ss si aa vr sa ai a repu etg cA versed Pes 250 8 9 Polylines Markers and Text scott rper EE Hone rete K sis a Es 250 829 1 Polylines Men 250 8 9 2 Markers 1 eG akiai ue cates dates aa k ante tha ote de Dr i a a i ii a 250 829 3 ikos T 252 8 10 Making a Movie ior uper eer En i pes dss sass i E ai a Ps sea Es 253 STOT 616 Ep k 253 8 10 72 DAWNEILE 5 5 2 nette ete tale nated ia Bai o Re ia i 254 8 10 3 Ray TraCerX iuigactesteu use repete ted va esie nee E yore dep ye deste edet t egere 254 9 Examples i erepti PETERE wes sted Sev i sas Ks 256 9 1 Novice Examples eles shed by ais Kas a i sa a aki si iii eda ieee 256 9 1 1 Novice Example Summary sss ertt tte thins ia us a a k i 256 9 12 Example NOU ote e as S HEIDE e vee cee ks 259 9 1 3 Example NO2 53 5 ce nec PR REC as Es i a Sess eee SS 259 9 1 4 Example N03 ee een eie aie ie ka Du ee nie vig 261 9 1 5 Example NOA 3 tet ct PR eh eet sss bathe he eat tases ERR io e e POE taper 262 viii Geant4 User s Guide for Application Developers 9 1 6 Example NUS 1 inintexEsine e bep bok wed L ee EI ees 264 9 1 7 Example NOG Ji tices e iot te ER Coe bote E CREE e DR EORR a 265 9 1 8 Example NO07 cxt eter et eerte tee deer to age ees cease ee e
63. Event event generator selection particleGun Tracking Geometry geometry definition includes Replica Region Hits Digi Primitive scorer Filter PIIM EM set mixtures and compound elements Physics EM processes Vis detector amp trajectory drawing G UI define user commands Global Table 9 3 The item chart for novice level example NO7 258 Examples 9 1 2 Example N01 Basic concepts minimal set for geantino transportation Classes main source file hard coded batch construction and deletion of G4RunManager hard coded verbose level setting to G4RunManager G4EventManager and G4TrackingManager construction and set of mandatory user classes hard coded beamOn Hard coded UI command application ExN01DetectorConstruction header file source file derived from G4VUserDetectorConstruction definitions of single element materials e CSG solids G4PVPlacement without rotation ExNO1PhysicsList header file source file derived from G4VUserPhysicsList definition of geantino assignment of transportation process ExNO1PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction construction of G4ParticleGun primary event generation via particle gun 9 1 3 Example N02 Basic concepts Detector fixed target type Processes EM Hits tracker type hits Classes main source file main for interactiv
64. G4 ElasticBrennerZaider Gro osssec CrossSec G4CrossSectionExcitationMillerGreen hh G4FinalStateExcitationMillerGreen hh G4CrossSectionChargeDecrease hh G4FinalStateChargeDecrease hh G4CrossSectionChargeIncrease hh G4FinalStateChargeIncrease hh tionElasticScreenedRutherford G4FinalStateElasticScreenedRutherford gt tionElasticScreenedRutherford G4FinalStateElasticBrennerZaider gt edef G4DNAProcess lt G4CrossSec xcitationEmfietzoglou edef G4DNAProcess lt G4CrossSec xcitationBorn edef G4DNAProcess lt G4 onisationBorn edef G4DNAProcess lt G4 onisationRudd edef G4DNAProcess lt G4CrossSec xcitationMillerGreen edef G4DNAProcess lt G4CrossSec hargeDecrease edef G4DNAProcess lt G4 hargerncreas Crosssee CrossSec noce Processes registration d MicrodosimetryPhysicsList ConstructEM heParticleIterator reset hile theParticleIterator G4ParticleDefinition particle G4ProcessManager processManager G4String particleName theParticleIterator value particle GetProcessManager particle GetParticleName if particleName e processManager gt AddDiscre processManager gt AddDiscre processManager gt AddDiscre processManager gt AddDiscre Process Proc ss Process POCA Ee Se E Br new new new new ExcitationEmfietzoglou ElasticScreenedRutherford ElasticBrennerZaider IonisationBorn else if process pro
65. G4LEDATA to the directory where he she has copied the files 5 2 2 Hadronic Interactions This section briefly introduces the hadronic physics processes installed in Geant4 For details of the implementa tion of hadronic interactions available in Geant4 please refer to the Physics Reference Manual 5 2 2 1 Treatment of Cross Sections Cross section data sets Each hadronic process object derived from G4HadronicProcess may have one or more cross section data sets associated with it The term data set is meant in a broad sense to be an object that encapsulates methods and data for calculating total cross sections for a given process The methods and data may take many forms from a simple equation using a few hard wired numbers to a sophisticated parameterisation using large data tables Cross section data sets are derived from the abstract class G4VCrossSectionDataSet and are required to implement the following methods G4bool IsApplicable const G4DynamicParticle const G4Element This method must return True if the data set is able to calculate a total cross section for the given particle and material and False otherwise G4double GetCrossSection const G4DynamicParticle const G4Element This method which will be invoked only if True was returned by IsApplicable must return a cross section in Geant4 default units for the given particle and material void BuildPhysicsTable const G4ParticleDefinitions amp This method ma
66. G4Nsplit Weight Calculate G4double init w G4double lowerWeightBound const 0 A concrete implementation is provided and used as a default class G4WeightWindowAlgorithm public G4VWeightWindowAlgorithm public G4WeightWindowAlgorithm G4double upperLimitFaktor 5 G4double survivalFaktor 3 G4int maxNumberOfSplits 5 virtual G4WeightWindowAlgorithm virtual G4Nsplit Weight Calculate G4double init w G4double lowerWeightBound const private hi The constructor takes three parameters which are used to calculate the upper weight bound upperLimitFaktor calculate the survival weight survivalFaktor and introduce a maximal number maxNumberOfSplits of copies to be created in one go In addition the inverse of the maxNumberOfSplits is used to specify the minimum survival probability in case of Russian roulette 3 7 1 6 The Weight Roulette Technique Weight roulette also called weight cutoff is usually applied if importance sampling and implicit capture are used together Implicit capture is not described here but it is useful to note that this procedure reduces a particle weight in every collision instead of killing the particle with some probability Together with importance sampling the weight of a particle may become so low that it does not change any result significantly Hence tracking a very low weight particle is a waste of computing time Weight roulette is applied in order to solve this problem
67. G4PVDivision divPconeZN division along Z giving nDiv and offset childLog motherLog kZAxis 2 0 1 m divPconePhiW is a division of a polycone along its phi axis in equal copies of width 30 degrees with an offset of 60 degrees As the mother extends from 0 to 180 degrees there s space for 4 copies All the copies 86 Detector Definition and Response have a starting angle of 20 degrees as for the mother and a phi extension of 30 degrees They are rotated around the Z axis by 60 and 30 degrees so that the first copy will extend from 80 to 110 and the last from 170 to 200 degrees e divPconeZN is a division of the same polycone along its Z axis As the mother polycone has two sections it will be divided in two one section polycones the first one extending from 1 to 0 25 meters the second from 0 25 to 1 meters Although specified the offset will not be used 4 1 5 Touchables Uniquely Identifying a Volume 4 1 5 1 Introduction to Touchables A touchable for a volume serves the purpose of providing a unique identification for a detector element This can be useful for description of the geometry alternative to the one used by the Geant4 tracking system such as a Sensitive Detectors based read out geometry or a parameterised geometry for fast Monte Carlo In order to create a touchable volume several techniques can be implemented for example in Geant4 touchables are implemented as solids associated to a transformation ma
68. G4ParticleDefinition Class G4ParticleDefinition has properties which characterize individual particles such as name mass charge spin and so on Most of these properties are read only and can not be changed by users without rebuilding the libraries 2 4 1 2 How to Access a Particle Each particle class type represents an individual particle type and each class has a single object This object can be accessed by using the static method of each class There are some exceptions to this rule please see Section 5 3 for details For example the class GaElectron represents the electron and the member G4Electron theInstance points its only object The pointer to this object is available through the static methods G4Electron ElectronDefinition G4Electron Definition More than 100 types of particles are provided by default to be used in various physics processes In normal applications users will not need to define their own particles Because particles are static objects of individual particle classes these objects are instantiated when the static method getting the pointer is invoked at the first time Therefore you must explicitly declare the particle classes required by your program at the initialization step otherwise no particles will be instantiated 10 Getting Started with Geant4 Running a Simple Example 2 4 1 3 Dictionary of Particles The G4ParticleTable class is provided as a dictionary of part
69. G4ParticleGun and all of them can be invoked from the generat ePri maries method in your concrete G4VUserPrimaryGeneratorAction class void SetParticleDefinition G4ParticleDefinition e void SetParticleMomentum G4ParticleMomentum e void SetParticleMomentumDirection G4ThreeVector void SetParticleEnergy G4double void SetParticleTime G4double e void SetParticlePosition G4ThreeVector e void SetParticlePolarization G4ThreeVector void SetNumberOfParticles G4int 2 7 How to Make an Executable Program 2 7 1 Building ExampleN01 in a UNIX Environment The code for the user examples in Geant4 is placed in the directory G4INSTALL examples where SGA4INSTALLis the environment variable set to the place where the Geant4 distribution is installed set by default to SHOME geant 4 In the following sections a quick overview on how the GNUmake mechanism works in Geant4 will be given and we will show how to build a concrete example ExampleNO1 which is part of the Geant4 distribution 2 7 1 1 How GNUmake works in Geant4 The GNUmake process in Geant4 is mainly controlled by the following GNUmake script files gmk scripts are placed in SG4INSTALL config Getting Started with Geant4 Running a Simple Example architecture gmk invoking and defining all the architecture specific settings and paths which are stored in G4INSTALL config sys common gmk defining all general GNUmake rules for bu
70. G4_He 0 000166322 41 8 3 G4 Li 0 534 40 4 G4 Be 1 848 63 7 5 G4 B 2 31 76 6 GA C 2 81 7 G4 0 0011652 82 8 G4 0 0 00133151 95 9 GA F 0 00158029 15 0 G4 Ne 0 000838505 31 1 G4 Na 0 971 49 2 G4 Mg 1 74 56 3 G4 Al 2 699 66 4 G4 Si 2 33 13 5 G4 P 2 2 13 6 GA S 2 80 7 G4_cl 0 00299473 74 8 G4_Ar 0 00166201 88 9 G4 K 0 862 90 20 G4 Ca 1 55 91 21 G4 Sc 2 989 216 22 G4 Ti 4 54 233 23 GA V 6 13 245 24 G4 Cr 7 18 257 25 G4 Mn 7 44 272 26 G4 Fe 7 874 286 27 G4 Co 8 9 297 28 G4_Ni 8 902 311 29 G4_Cu 8 96 322 30 G4 Zn 75133 330 31 G4 Ga 5 904 334 32 G4 Ge 5 323 350 33 G4 As 5 73 347 34 G4 Se 4 5 348 35 G4 Br 0 0070721 343 36 G4 Kr 0 00347832 352 37 G4_Rb 1 532 363 38 G4 Sr 2 54 366 39 G4 Y 4 469 379 40 G4 Zr 6 506 393 289 Appendix 41 G4 Nb 8 57 417 42 G4 Mo 10 22 424 43 G4 Tc 11 5 428 44 G4 Ru 12 41 441 45 G4 Rh 12 41 449 46 G4 Pd 12 02 470 47 G4_Ag 10 5 470 48 G4 Cd 8 65 469 49 G4 In 7 31 488 50 G4 Sn 7 31 488 51 G4 Sb 6 691 487 52 G4 Te 6 24 485 53 G4 4 93 491 54 G4 Xe 0 00548536 482 55 G4 Cs 1 873 488 56 G4 Ba 3 5 491 57 G4 La 6 154 501 58 G4 Ce 6 657 523 59 G4 Pr 6 71 535 60 G4 Nd 6 9 546 61 G4 Pm 7 22 560 62 G4 Sm 7 46 574 63 G4 Eu 5 243 580 64 G4 Gd 7 9004 59 65 G4 Tb 8 229 614 66 G4 Dy 8 55 628 67 G4 Ho 8 795 650 68 G4 Er 9 066 658 69 G4 Tm 9 321 674 70 G4 Yb 6 73 684 71 G4 Lu 9 84 694 72 G4_HE 13 31 705 73 G4 Ta 16 654 718 74 GA W 19 3 721 75 G4_Re 21 02 736 76 G4 Os 22 5
71. G4double G4double G4double G4double pZ pY px pLTX G4String amp pName G4double G4double G4double G4double G4double G4double pDz pehi PDL pAlpl pDx3 pAlp2 G4double G4double G4double G4double G4double pTheta pbyl pDx2 pDy2 pDx4 61 Detector Definiti on and Response In the picture pDxl 30 pDx2 40 pDyl 40 pDx3 10 pDx4 14 pDy2 16 pDz 60 pTheta 20 Degree pPhi 5 Degree pAlpl pAlp2 10 Degree to obtain a Right Angular Wedge with name pName and parameters DZ Length along z py Length along y pX Length along x at the wider side pLTX Length along x at the narrower side 9 1 TX lt pX or to obtain the general trapezoid see the Software Reference Manual pDx1 Half x length of the side at yz pDyl of the face at pDz pDx2 Half x length of the side at y pDy 1 of the face at pDz pDz Half z length pTheta Polar angle of the line joining the centres of the faces at pDz pPhi Azimuthal angle of the line joining the centre of the face at pDz to the centre of the face at pDz pDyl Half y length at pDz pDy2 Half y length at pDz pDx3 Half x length of the side at y pDy2 of the face at pDz pDx4 Half x length of the side at y pDy2 of the face at pDz pAlp1 Angle with respect to the y axis from the centre of the side lower endcap pAlp2 Angle with respect to the y axis from the centre of th
72. GAGTree driver provides a listing of the detector geometry tree within GAG the Geant Adaptive GUI http erpc naruto u ac jp geant4 GAG allows folding un folding a part of the geometry tree using the Tree Widget in Java A GAG Geant4 History Help Log to File vj to Terminal JAS vis GAGTree verbose 10 X 9 Gus 3 enable disable verbose 3 drawTree 3 drawVolume drawview C open specify ASCIITree 9 EI 6AGTree D verbose cJ scene 5 sceneHandler exampleN03 7 viewer 9 Ci World 0 0 camera 9 jCalorimeter 0 1 fere EE fe C claar 9 ALayer 1 2 l Beate ipleND3 in Idle ji Absorber 0 3 e scene handler name is auto generated he 2nd parameter is the window size hint stem name GAGTree ko graphic yo Deoa llo 312740 six p Layer 1 5 lla 1525116 59 hone 9 Layer 1 8 I2 733320 87 win Absorber 0 9 C Gap o 10 pI Layer 1 11 Layer 1 14 Absorber 0 15 3 6ap 0 16 Layer 1 17 yj Layer 1 20 E Layer 1 23 0 Absorber 0 24 3 Gap 0 25 A Layer 1 26 jLayer 1 29 220 Visualization 8 3 12 XML Tree The XML description of the geometry tree can be created in Geant4 by the XML Tree driver The XML source can also be edited on the fly The created
73. GNUmake targets one can invoke to build libraries and or executables gmake starts the compilation process for building a kernel library or a library associated with an example Kernel libraries are built with maximum granularity i e if a category is a compound this command will build all the related sub libraries not the compound one The top level GNUmakefile in G4INSTALL source will also build in this case a dependency map 1ibname map of each library to establish the linking order automatically at the bin step The map will be placed in SG4LIB SG4SYSTEM gmake global starts the compilation process to build a single compound kernel library per category If issued after gmake both granular and compound libraries will be available NOTE this will consistently increase the disk space required Compound libraries will then be selected by default at link time unless G4LIB_USE_GRANULAR is specified e gmake bin or gmake only for examples starts the compilation process to build an executable This command will build implicitly the library associated with the example and link the final application It assumes all kernel libraries are already generated and placed in the correct G4INSTALL path defined for them The linking order is controlled automatically in case libraries have been built with maximum granularity and the link list is generated on the fly make dll On Windows systems this will start the compilation pr
74. Geant4 provides two ways of doing this using G4DecayChannel in G4DecayTable and using thePreAssignedDecayProducts of G4DynamicParticle The G4Decay class calculates the PhysicalInteractionLength and boosts decay products created by G4VDecayChannel or event generators See below for information on the determination of the decay modes An object of G4Decay can be shared by particles Registration of the decay process to particles in the Con structPhysics method of PhysicsList see Section 2 5 3 is shown in Example 5 4 Example 5 4 Registration of the decay process to particles in the Const ructPhysics method of Physics List include G4Decay hh void ExN02PhysicsList ConstructGeneral Add Decay Process G4Decay theDecayProcess new G4Decay theParticlelterator gt reset while theParticleIterator G4ParticleDefinition particle theParticleIterator value G4ProcessManager pmanager particle gt GetProcessManager if theDecayProcess gt IsApplicable particle pmanager gt AddProcess theDecayProcess set ordering for PostStepDoIt and AtRestDoIt pmanager gt SetProcessOrdering theDecayProcess idxPostStep pmanager gt SetProcessOrdering theDecayProcess idxAtRest D 5 2 3 2 Decay Table Each particle has its G4DecayTable which stores information on the decay modes of the particle Each de cay mode with its branching ratio corresponds to an object of various decay channel
75. Grady Booch Object Oriented Analysis and Design with Applications The Benjamin Cummings Publishing Co Inc 1994 ISBN 0 8053 5340 2 Ellis1990 Margaret Ellis and Bjarne Stroustrup Annotated C Reference Manual ARM Addison Wesley Publishing Co 1990 Hecht1974 E Hecht and A Zajac Optics Addison Wesley Publishing Co 1974 pp 71 80 and pp 244 246 Josuttis1999 Nicolai M Josuttis The C Standard Library A Tutorial and Reference Addison Wesley Publishing Co 1999 ISBN 0 201 37926 0 Meyers2001 Scott Meyers Effective STL Addison Wesley Publishing Co 2001 ISBN 0 201 74962 9 Musser1996 David R Musser and Atul Saini STL Tutorial and Reference Guide C Programming with the Standard Template Library Addison Wesley Publishing Co 1996 ISBN 0 201 63398 1 Plauger1995 P J Plauger The Draft Standard C Library Prentice Hall Englewood Cliffs 1995 Chauvie2007 Geant4 physics processes for microdosimetry simulation design foundation and implementation of the first set of models To be published in IEEE Trans Nucl Sci Dec 2007 2007 302
76. LowEnergyCompton LowEnergyGammaConversion LowEnergyRayleigh pmanager gt AddDiscreteProcess pmanager gt AddDiscreteProcess pmanager gt AddDiscreteProcess pmanager gt AddDiscreteProcess theLEPhotoElectric theLECompton theLERayleigh theLEGammaConversion else if particleName e theLEIonisation new G4LowEnergylonisation theLEBremsstrahlung new G4LowEnergyBremsstrahlung el theeminusMultipleScattering new G4MultipleScattering pmanager gt AddProcess theeminusMultipleScattering 1 1 1 pmanager gt AddProcess theLEIonisation 1 2 2 pmanager gt AddProcess theLEBremsstrahlung 1 se if particleName e theeplusMultipleScattering theeplusIonisation theeplusBremsstrahlung theeplusAnnihilation 1 3 new G4MultipleScattering new G4elonisation new G4eBremsstrahlung new G4eplusAnnihilation pmanager gt AddProcess theeplusMultipleScattering 1 1 1 pmanager gt AddProcess pmanager gt AddProcess theeplus Ionisation 1 2 2 theeplusBremsstrahlung 1 1 3 pmanager gt AddProcess theeplusAnnihilation 0 1 4 145 Tracking and Physics Advanced examples illustrating the use of Low Energy Electromagnetic processes are available as part of the Geant4 release and are further documented here To run the Low Energy code for photon and electron electromagnetic processes data files need to be cop
77. MeV vis filtering trajectories attributeFilter 0 addInterval 2 5 MeV 1000 MeV List filters vis filtering trajectories list Note that although particleFilter 0 and chargeFilter 0 are automatically 249 Visualization chained particleFilter 0 will not have any effect since it is has been deactivated 8 8 3 Hit Filtering The attribute based filtering can be used on hits as well as trajectories To active the interactive attribute based hit filtering a filter call should be added to the Draw method of the hit class void MyHit Draw if pVVisManager gt FilterHit this return Interactive filtering can then be done through the commands in vis filtering hits 8 9 Polylines Markers and Text Polylines markers and text are defined in the graphics_reps category and are used only for visualization Here we explain their definitions and usages 8 9 1 Polylines A polyline is a set of successive line segments It is defined with a class G4Polyline defined in the graphics_reps category A polyline is used to visualize tracking steps particle trajectories coordinate axes and any other user defined objects made of line segments G4Polyline is defined as a list of G4Point3D objects i e vertex positions The vertex positions are set to a G4Polyline object with the push_back method For example an x axis with length 5 cm and with red color is defined in Example 8 5 Example 8 5 Def
78. Specifies to build kernel library for visualization including the OpenGL driver with XM extension It requires SOGLHOME set path to OpenGL installation G4VIS_USE_OPENGLXM Specifies to use OpenGL graphics with XM extension in the application to be built G4VIS_BUILD_OPENGLQT_DRIVER Specifies to build kernel library for visualization including the OpenGL driver with Qt extension It requires SQTHOME set to specify the path where Qt libraries and headers are installed G4VIS_USE_OPENGLQT Specifies to use OpenGL graphics with Qt extension in the application to be built G4VIS_BUILD_OI_DRIVER Specifies to build kernel library for visualization including the OpenInventor driver It requires O I HOME set paths to the OpenInventor installation G4VIS USE OI Specifies to use OpenInventor graphics in the application to be built G4VIS BUILD OIX DRIVER Specifies to build the driver for the free X11 version of OpenInventor G4VIS USE OIX Specifies to use the free X11 version of OpenInventor G4VIS BUILD RAYTRACERX DRIVER Specifies to build kernel library for visualization including the Ray Tracer driver with X11 extension It re quires X11 installed in the system G4VIS USE RAYTRACERX Specifies to use the X11 version of the Ray Tracer driver G4VIS BUILD OIWIN32 DRIVER Specifies to build the driver for the free X11 version of OpenInventor on Windows systems G4VIS USE OIWIN32 Specifies to use the free X11 version o
79. The user must choose a direction of the particle to be scored The choices are fCurrent_In fCurrent_Out or fCurrent_InOut one of which must be entered as the second argument of the constructor Here fCurrent In scores incoming particles to the cell while fCurrent Out scores only outgoing particles from the cell fCurrent InOut scores both directions The current is multiplied by particle weight and is normalized for a unit area G4PSSphereSurfaceCurrent Sphere surface current is a surface based scorer and similar to the G4PSFlatSurfaceCurrent The only differ ence is that the surface is defined at the inner surface of a G4Sphere solid G4PSPassageCurrent Passage current is a volume based scorer The current is defined by the number of tracks that pass through the volume A particle weight is applied at the exit point A passage current is defined for a volume G4PSFlatSurfaceFlux Flat surface flux is a surface based flux scorer The surface flux is defined by the number of tracks that reach the surface The expression of surface flux is given by the sum of W cos t A where W t and A represent particle weight injection angle of particle with respect to the surface normal and area of the surface The user must enter one of the particle directions fFlux_In fFlux_Out or fFlux_InOut in the constructor Here fFlux_In scores incoming particles to the cell while fFlux_Out scores outgoing particles from the cell fFlux_InOut scores both directio
80. They may be in a curved surface made out of polygons for example or in plane surface of complicated shape that has to be broken down into simpler polygons HepPoly hedron breaks all surfaces into triangles or quadrilaterals There will be auxiliary edges for any volumes with a curved surface such as a tube or a sphere or a volume resulting from a Boolean operation Normally they are not shown but sometimes it is useful to see them In particular a sphere because it has no egdes will not be seen in wireframe mode in some graphics systems unless requested by the view parameters or forced as described here To force auxiliary edges to be visible use void G4VisAttributes SetForceAuxEdgeVisible G4bool force The default value of the force auxiliary edges visible flag is false For volumes with edges that are parts of a circle such as a tube G4Tubs etc it is possible to force the precision of polyhedral representation for visualisation This is recommended for volumes containing only a small angle of circle for example a thin tube segment 241 Visualization For visualisation a circle is represented by an N sided polygon The default is 24 sides or segments The user may change this for all volumes in a particular viewer at run time with vis viewer set lineSegmentsPerCircle alternatively it can be forced for a particular volume with void G4VisAttributes SetForceLineSegmentsPerCircle G4int nSegments 8 6 4 Con
81. VRML Network any network enabled VRML viewer Linux UNIX RayTracer any JPEG viewer Linux UNIX Mac Windows ASCII Tree none Linux UNIX Mac Windows GAGTree GAG Linux UNIX Mac Windows XMLTree any XML viewer Linux UNIX Mac Windows Table 8 1 Required graphics systems and supported platforms for the various visualization drivers 8 3 2 OpenGL These drivers have been developed by John Allison and Andrew Walkden University of Manchester It is an interface to the de facto standard 3D graphics library OpenGL It is well suited for real time fast visualization and demonstration Fast visualization is realized with hardware acceleration reuse of shapes stored in a display list etc NURBS visualization is also supported Several versions of the OpenGL drivers are prepared Versions for Xlib Motif and Win32 platforms are available by default For each version there are two modes immediate mode and stored mode The former has no limitation on data size and the latter is fast for visualizing large data repetitively and so is suitable for animation 211 Visualization If you don t have Motif all control is done from Geant4 commands vis open OGLIX vis viewer set viewpointThetaPhi 70 20 vis viewer zoom 2 eter But if you have Motif libraries you can control Geant4 from Motif widgets vis open OGLIXm The OpenGL driver added Smooth shading and Transparency since Geant4 release 8 0 Further infor
82. WWW impr XXX YYY ZZZ where WWW assembly volume instance number XXX assembly volume imprint number YYY the name of the placed logical volume e ZZZ the logical volume index inside the assembly volume It is however possible to access the constituent physical volumes of an assembly and eventually customise ID and copy number 4 1 6 3 Destruction of an assembly volume At destruction all the generated physical volumes and associated rotation matrices of the imprints will be destroyed A list of physical volumes created by MakeImprint method is kept in order to be able to cleanup the objects when not needed anymore This requires the user to keep the assembly objects in memory during the whole job or during the life time of the G4Navigator logical volume store and physical volume store may keep pointers to physical volumes generated by the assembly volume The MakeImprint method will operate correctly also on transformations including reflections and can be applied also to recursive assemblies i e it is possible to generate imprints of assemblies including other assem blies Giving t rue as the last argument of the MakeImprint method it is possible to activate the volumes overlap check for the assembly s constituents the default is false At destruction of a G4AssemblyVolume all its generated physical volumes and rotation matrices will be freed 4 1 6 4 Example This example shows how to use the G4Assem
83. act independently for different purposes The main navigator which is activated automatically at the startup of a simulation program is the navigator used for the tracking and attached the world volume of the main tracking or mass geometry 93 Detector Definition and Response The navigator for tracking can be retrieved at any state of the application by messagging the G4TransportationManager G4Navigator tracking navigator G4TransportationManager GetInstance GetNavigatorForTracking The navigator for tracking also retains all the information of the current history of volumes transversed at a precise moment of the tracking during a run Therefore if the navigator for tracking is used during tracking for locating a generic point in the tree of volumes the actual particle gets also relocated in the specified position and tracking will be of course affected In order to avoid the problem above and provide information about location of a point without affecting the track ing it is suggested to either use an alternative G4Navigator object which can then be assigned to the world volume or access the information through the step Using the step to retrieve geometrical information During the tracking run geometrical information can be retrieved through the touchable handle associated to the current step For example to identify the exact copy number of a specific physical volume in the mass geometry one should do t
84. addMenu test Test gui addButton test Init run initialize gui addButton test Set gun control execute gun g4m gui addButton test Run one event run beamOn 1 G4UIXm runs on Unix Linux with Motif G4UIXaw less user friendly runs on Unix with Athena widgets G4UIWin32 runs on Windows 2 8 2 3 G4UIGAG and G4UI GainServer classes They are the front end classes of Geant4 which interface with their respective graphical user interfaces GAG Geant4 Adaptive GUI and Gain Geant4 adaptive interface for network While GAG must run on the same system Windows or Unixen as a Geant4 application Gain can run on a remote system Windows Linux etc to which JVM Java Virtual Machine is installed A Geant4 application is invoked on a Unix Linux system and behaves as a network server It opens a port waiting the connection from the Gain Gain is capable to connect to multiple Geant4 servers on Unixen systems at different institutes Client GUI GAG and Gain have almost similar look and feel So GAG s functionalities are briefly introduced here Please refer to the above URL for details and to download the client GUIs GAG is a Graphical User Interface tool with which user can set parameters and execute commands It is adaptive since GAG reflects the internal states of Geant4 that is a state machine GAG is based on the server client model GAG is the server while Geant4 executables are clients Hence GAG does nothing by itself
85. added is current Example Visualization of trajectories Idle vis scene add trajectories Idle run beamOn 10 Additional note 1 See the section Section 8 7 3 Enhanced Trajectory Drawing for details on how to control how trajectories are color coded For more options see the Control UICommands section of this user guide 8 4 7 Visualization of hits vis scene add hits com mand Command vis scene add hits adds hits to the current scene assuming that you have a hit class and that the hits have visualization information The visualization is performed with the command run beamOn unless you have non default values for vis scene endOfEventAction or vis scene endOfRunAction described above 8 4 8 HepRep Attributes for Hits The HepRep file formats HepRepFile and HepRepXML attach various attributes to hits such that you can view these attributes label trajectories by these attributes or make visibility cuts based on these attributes Examples of adding HepRep attributes to hit classes can be found in examples extended analysis AO1 and extended runAn dEvent REO1 For example in example REOI s class REO1CalorimeterHit cc available attributes will be Hit Type Track ID ZCell ID Phi Cell ID Energy Deposited Energy Deposited by Track Position Logical Volume You can add additional attributes of your choosing by modifying the relevant part of the hit class look for the methods GetAttDef
86. amp UIcommand derived class for a command which takes no parameter e G4UIcmdWithoutParameter char commandPath G4UImessenger theMessenger Constructor Arguments are the full path command name and the pointer to your messenger G4UlcmdWithABool This is a G amp UIcommand derived class which takes one boolean type parameter G4UIcmdWithABool char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramName G4bool omittable Define the name of the boolean parameter and set the omittable flag If omittable is true you should define the default value using the next method e void SetDefaultValue G4bool defVal Define the default value of the boolean parameter e G4bool GetNewBoolValue G4String paramString 196 Communication and Control Convert G4String parameter value given by the Set NewValue method of your messenger into boolean G4String convertToString G4bool currVal Convert the current boolean value to G4String whichshould be returned by the Get CurrentValue method of your messenger G4UlcmdWithAnlnteger This is a G amp UIcommand derived class which takes one integer type parameter G4UIcmdWithAnInteger char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramName G4boo
87. and it must invoke an executable simulation program Geant4 s front end class G4UIGAG must be instantiated to communicate with GAG This runs on Linux and Windows 2000 GAG is written in Java and its Jar Java Archive file is available from the above URL See the same pages to know how to install and run Java programs GAG has following functions Getting Started with Geant4 Running a Simple Example GAG Menu The menus are to choose and run a GEANT4 executable file to kill or exit a GEANT4 process and to exit GAG Upon the normal exit or an unexpected death of the Geant4 process GAG window are automatically reset to accept another GEANT4 executable GEANT4 Command tree Upon the establishment of the pipe with the GEANT4 process GAG displays the command menu tree whose look and feel is quite similar to Windows file browser Disabled commands are shown opaque GAG doesn amp rsquo t display commands that are just below the root of the command hierarchy Direct type in field is available for such input Guidance of command categories and commands are displayed upon focusing GAG has a command history function User can re execute a command with old parameters edit the history or save the history to create a macro file Command Parameter panel GAG s parameter panel is the user friendliest part It displays parameter name its guidance its type s inte ger double Boolean or string omittable default value s expression s of its
88. and may even vary dynamically during the execution of your job List of built in commands 7 2 User Interface Defining New Commands 7 2 1 G4Ulmessenger G4UlImessenger is a base class which represents a messenger that delivers command s to the destination class object Your concrete messenger should have the following functionalities Construct your command s in the constructor of your messenger Destruct your command s in the destructor of your messenger These requirements mean that your messenger should keep all pointers to your command objects as its data mem bers You can use G4UIcommand derived classes for the most frequent types of command These derived classes have their own conversion methods according to their types and they make implementation of the Set NewValue and GetCurrentValue methods of your messenger much easier and simpler For complicated commands which take various parameters you can use the G4Ulcommand base class and con struct G4UIparameter objects by yourself You don t need to delete G4UIparameter object s In the SetNewValue and GetCurrentValue methods of your messenger you can compare the G4UIcommand pointer given in the argument of these methods with the pointer of your command because your messenger keeps the pointers to the commands Thus you don t need to compare by command name Please re member in the cases where you use G4UIcommand derived classes you should store the pointe
89. be computationally intensive At verbosity level 4 ASCIITree calculates the mass of the complete geometry tree taking into account daughters up to the depth specified for each physical volume The calculation involves subtracting the mass of that part of the mother that is occupied by each daughter and then adding the mass of the daughter and so on down the hierarchy vis ASCIITree Verbose 4 vis viewer flush HadCalorimeterPhysical 0 HadCalorimeterLogical HadCalorimeterBox G4Box domom v eae eyes HadCalColumnPhysical 1 10 replicas HadCalColumnLogical HadCalColumnBox G4Box EROIOIDIOI NK mi IESS G Aems HadCalCellPhysical 1 2 replicas HadCalCellLogical HadCalCellBox G4Box 20000 em gt 30b S yis HadCalLayerPhysical 1 20 replicas HadCalLayerLogical HadCalLayerBox G4Box 2500 cmo 1 35 5 oma HadCalScintiPhysical 0 HadCalScintiLogical HadCalScintiBox G4Box S00 cm 12092 qom Calculating mass es Overall volume of worldPhysical 0 is 2400 m3 Mass of tree to unlimited depth is 22260 5 kg Some more examples of ASCIITree in action Idle vis ASCIITree verbose 1 Idle vis drawTree 219 Visualization Set verbosity with vis ASCIITree verbose lt IU does not print daughters of repeated placements does not repeat replicas gt 10 prints all physical volumes The level of detail is given by verbosity 10 for each volume ees O
90. be made visible later from controls in the HepRep browser If this behavior would cause files to be too large you can instead choose to have culled objects be omitted from the HepRep file See details in the HepRepFile Driver section of this user guide 8 4 15 Cut view Sectioning Sectioning means to make a thin slice of a 3D scene around a given plane At present this function is supported by the OpenGL drivers The sectioning is realized by setting a sectioning plane before performing visualization The sectioning plane can be set by the command vis viewer set sectionPlane on x y z units nx ny nz where the vector x y z defines a point on the sectioning plane and the vector nx ny nz defines the normal vector of the sectioning plane For example the following sets a sectioning plane to a yz plane at x 2 cm Idle gt vis viewer set sectionPlane on 2 0 0 0 0 0 cm 1 0 0 0 0 0 Cutting away Cutting away means to remove a half space defined with a plane from a 3D scene Cutting away is supported by the DAWNFILE driver off line Do the following Perform visualization with the DAWNFILE driver to generate a file g4 prim describing the whole 3D scene Make the application DAWNCUT read the generated file to make a view of cutting away See the following WWW page for details http geant4 kek jp GEANT4 vis DAWN About_DAWNCUT html Alternatively add up to three cutaway planes 229 Visualization vis view
91. check if it is alive G4Track theTrack theStep gt GetTrack if theTrack gt GetTrackStatus fAlive return get region information G4StepPoint thePrePoint theStep gt GetPreStepPoint G4LogicalVolume thePreLV thePrePoint gt GetPhysicalVolume gt GetLogicalVolume REOIRegionInformation thePreRInfo REOlRegionInformation thePreLV gt GetRegion gt GetUserInformation G4StepPoint thePostPoint theStep gt GetPostStepPoint G4LogicalVolume thePostLV thePostPoint gt GetPhysicalVolume gt Get LogicalVolume REO1lRegionInformation thePostRInfo REOlRegionInformation thePostLV gt GetRegion gt GetUserInformation check if it is entering to the calorimeter volume if thePreRInfo gt IsCalorimeter amp amp thePostRInfo gt IsCalorimeter theTrack gt SetTrackStatus fSuspend 194 Chapter 7 Communication and Control 7 1 Built in Commands Geant4 has various built in user interface commands each of which corresponds roughly to a Geant4 category These commands can be used e interactively via a Graphical User Interface G UI ina macro file via control execute command e within C code with the ApplyCommand method of G4UImanager Note The availability of individual commands the ranges of parameters the available candidates on individ ual command parameters vary according to the implementation of your application
92. ck ck ck ck ck ck ck ck ck ck ckckckckckck ko ko kok SUBROUTINE HEP2G4 Convert HEPEVT event structure to an ASCII file to be fed by G4HEPEvtInterface BAP ae Se KKKK KKK KKK ck ck ck ck ck KKK KKK KK KKK KKK KKK ck ck ckck ck ck ck ck ck ck ck ck ck ck ck ck ckckckckckckck ko k kk PARAMETER NMXHEP 2000 COMMON HEPEVT NEVHEP NHEP ISTHEP NMXHEP IDHEP NMXHEP gt JMOHEP 2 NMXHEP JDAHEP 2 NMXHEP PHEP 5 NMXHEP VHEP 4 NMXHEP DOUBLE PRECISION PHEP VHEP WRITE 6 NHEP DO IHEP 1 NHEP WRITE 6 10 gt ISTHEP IHEP IDHEP IHEP JDAHEP 1 IHEP JDAHEP 2 IHEP gt PHEP 1 IHEP PHEP 2 IHEP PHEP 3 IHEP PHEP 5 IHEP 10 FORMAT 4110 4 1X D15 8 ENDDO RETURN END 3 6 2 3 Future interface to the new generation generators Several activities have already been started for developing object oriented event generators Such new generators can be easily linked and used with a Geant4 based simulation Furthermore we need not distinguish a primary generator from the physics processes used in Geant4 Future generators can be a kind of physics process plugged in by inheriting G4VProcess 3 6 3 Event overlap using multiple generators Your G4VUserPrimaryGeneratorAction concrete class can have more than one G4VPrimaryGenerator concrete class Each G4VPrimaryGenerator concrete class can be accessed more than once per event Using these class objects one event can have more than one pri
93. class must not be overriden void AddTransportation VIM A MTU ADA IAA MAA AA AD AMAA AED ED ATA VUV AIA AAAS public with description SetCuts method sets a cut value for all particle types in the particle table virtual void Setcute 05 public with description set get the default cut value Calling SetDefaultCutValue causes re calcuration of cut values and physics tables just before the next event loop void SetDefaultCutValue G4double newCutValue G4double GetDefaultCutValue const TEE ATE EAA EET A ETA TA TTA ATTA AAA AAA public with description Invoke BuildPhysicsTable for all processes for all particles In case of Retrieve flag is ON PhysicsTable will be retrieved from files void BuildPhysicsTable do BuildPhysicsTable for specified particle type void BuildPhysicsTable G4ParticleDefinition Store PhysicsTable together with both material and cut value information in files under the specified directory return true if files are sucessfully created G4bool StorePhysicsTable const G4String amp directory Return true if Retrieve flag is ON i e PhysicsTable will be retrieved from files G4bool IsPhysicsTableRetrieved const G4bool IsStoredInAscii const Get directory path for physics table files const G4String amp GetPhysicsTableDirectory const Set Retrieve flag Directory path can be set together Null
94. class names This secondary template repository can be activated by defining in the environment or in the GNUmakefile related to the test example to be built the flag G4EXEC BUILD once activated the secondary repository will become the read write one while the primary repository will be considered read only At the current time only few compilers still make use of a template repository A good recommendation valid in general such compilers is to make use of a single template repository specified by the G4TREP environment variable for building all Geant4 libraries then use a secondary template repository G4TREP exec together with the G4EXEC BUILD flag when building any kind of example or application It s always good practise to clean up the secondary template repository from time to time 1 1 Sun OS SunOS Compiler CC The default optimisation level is O2 Since version 5 0 of the compiler native STL is supported and ISO ANSI compliance is required 1 2 Unix Linux g OS Linux Compiler GNU gcc Strict ISO ANSI compilation is forced Cansi pedantic compiler flags also code is compiled with high verbosity diagnostics Wa11 flag The default optimisation level is O2 279 Appendix Note Additional compilation options march pentium4 mfpmath sse to adopt Pentium4 chip spe cific floating point operations on the SSE unit can be activated by uncommenting the relevant pa
95. detector parts that had defaulted to be invisible the HepRepFile driver does not omit these invisible detector parts from the HepRep file But for very large files if you know that you will never want to make these parts visible you can choose to have them left entirely out of the file Set the environment variable G4HEPREPFILE CULL as in export G4HEPREPFILE_CULL 1 Further information e WIRED3 Users Home Page http www slac stanford edu BFROOT www Computing Graphics Wired HepRep graphics format 213 Visualization http www slac stanford edu perl heprep Geant4 Visualization Tutorial using the WIRED3 HepRep Browser http geant4 slac stanford edu Presentations vis G4WIREDTutorial G4WIREDTutorial html 8 3 5 HepRepXML The HepRepXML driver creates a HepRep file in the HepRep2 format suitable for viewing with the WIRED4 Plugin to the JAS3 Analysis System or the FRED event display This driver can write both Binary HepRep bheprep and XML HepRep heprep files Binary HepRep files are a one to one translation of XML HepRep files but they are considerably shorter and faster to parse by a HepRepViewer such as WIRED 4 Both Binary HepRep and XML HepRep can be compressed using the standard zlib library if linked into Geant4 using G4LIB_USE_ZLIB If a standard zlib is not available WIN32 VC for instance you should also set G4LIB_BUILD_ZLIB to build G4zlib included with Geant4 HepRep files Binary and XML can
96. distri butions G4GeneralParticleSource is a concrete implementation of G4VPrimaryGenerator To use instantiate G4GeneralParticleSource in the G4VUserPrimaryGeneratorAction class as demonstrated below MyPrimaryGeneratorAction MyPrimaryGeneratorAction generator new G4GeneralParticleSource void MyPrimaryGeneratorAction GeneratePrimaries G4Event anEvent generator gt GeneratePrimaryVertex anEvent The biasing can be configured through interactive commands Extensive documentation can be found in Primary particle biasing Examples are also distributed with the Geant4 distribution in examples extended eventgenera tor exgps 3 7 2 1 2 Radioactive Decay Biasing The G4RadioactiveDecay class simulates the decay of radioactive nuclei and implements the following biasing options Increase the sampling rate of radionuclides within observation times through a user defined probability distri bution function Nuclear splitting where the parent nuclide is split into a user defined number of nuclides e Branching ratio biasing where branching ratios are sampled with equal probability 55 Toolkit Fundamentals G4RadioactiveDecay is a process which must be registered with a process manager as demonstrated below void MyPhysicsList ConstructProcess G4RadioactiveDecay theRadioactiveDecay new G4RadioactiveDecay G4ProcessManager pmanager pmanager gt AddProcess theRadioactiveDecay
97. during the step A resolution scale of 1 0 produces a statistical fluctuation around the average yield set with AddConstProperty SCINTILLATIONYIELD while values gt 1 broaden the fluctuation A value of zero produces no fluctuation Each photon s frequency is sampled from the empirical spectrum The photons orig inate evenly along the track segment and are emitted uniformly into 4 with a random linear polarization and at times characteristic for the scintillation component 5 2 5 3 Generation of Photons in processes optical Wave length Shifting Wavelength Shifting WLS fibers are used in many high energy particle physics experiments They absorb light at one wavelength and re emit light at a different wavelength and are used for several reasons For one they tend to decrease the self absorption of the detector so that as much light reaches the PMTs as possible WLS fibers are also used to match the emission spectrum of the detector with the input spectrum of the PMT A WLS material is characterized by its photon absorption and photon emission spectrum and by a possible time delay between the absorption and re emission of the photon Wavelength Shifting may be simulated by specify ing these empirical parameters for each WLS material in the simulation It is sufficient to specify in the user s DetectorConstruction class a relative spectral distribution as a function of photon energy for the WLS material WLSABSLENGTH is the absorption le
98. dx etc The G4Material class is the one which is visible to the rest of the toolkit and is used by the tracking the geometry and the physics It contains all the information relative to the eventual elements and isotopes of which it is made at the same time hiding the implementation details 2 3 2 Define a Simple Material In the example below liquid argon is created by specifying its name density mass per mole and atomic number Getting Started with Geant4 Running a Simple Example Example 2 7 Creating liquid argon G4double density 1 390 g cm3 G4double a 39 95 g mole G4Material lAr new G4Material name liquidArgon z 18 a density The pointer to the material Ar will be used to specify the matter of which a given logical volume is made G4LogicalVolume myLbox new G4LogicalVolume aBox lAr Lbox 0 0 0 2 3 3 Define a Molecule In the example below the water H2O is built from its components by specifying the number of atoms in the molecule Example 2 8 Creating water by defining its molecular components a 1 01 g mole G4Element elH new G4Element name Hydrogen symbol H z 1 a a 16 00 g mole G4Element elO new G4Element name Oxygen symbol 0 z 8 a density 1 000 g cm3 G4Material H20 new G4Material name Water density ncomponents 2 H20 gt AddElement elH natoms 2 H20 gt AddElement elO natoms 1 2 3 4 Define a Mixture by Frac
99. gt GetDeltaPosition G4double tof step GetDeltaTime To get momentum kinetic energy and global time time since the beginning of the event of the track after the completion of the current step G4Track track step gt GetTrack G4ThreeVector momentum track gt GetMomentunm G4double kinEnergy track gt GetKineticEnergy G4double globalTime track gt GetGlobalTime GSE ous t Remark To transform a position from the global coordinate system to the local system of the current volume usethe prestepPoint transformation 8 ithe ceometrysection abeve Frequentry Asked Questions FAQ 5 Physics and cuts Q How do production cuts in range work in Geant4 Are they also used in tracking If a particle has an energy lower than the converted cut in energy for the given material and the distance to the next boundary is smaller than the cut in range is the particle killed Geant4 does NOT have a tracking cut The toolkit s default behaviour is to track particles down to zero range i e zero energy Of course it is possible for the user to create and register a process that kills particles below a certain energy or range this is however NOT provided by default in Geant4 So there s NO tracking cut For example suppose a particle that is nearing zero energy will at some point be proposed by its Ionisation process to undergo one final step from its current energy down to zero energy This is sti
100. gt Initialize endif set user action classes runManager gt SetUserAction new NO3PrimaryGeneratorAction detector runManager gt SetUserAction new NO3RunAction runManager gt SetUserAction new N03EventAction runManager gt SetUserAction new N03SteppingAction get the pointer to the User Interface manager G4UImanager UI G4UImanager GetUlpointer if argc 1 Define UI terminal for interactive mode G4UIsession session new G4UIterminal UI gt ApplyCommand control execute prerunN03 mac session SessionStart delete session else Batch mode G4String command control execute G4String fileName argv 1 UI gt ApplyCommand command fileName job termination ifdef G4VIS USE delete visManager endif delete runManager return 0 Notice that the visualization system is under the control of the precompiler variable G4VIS US E Notice also that in interactive mode few intializations have been put in the macro prerunN03 mac which is executed before the session start 25 Getting Started with Geant4 Running a Simple Example Example 2 25 The prerunN03 mac macro Macro file for the initialization phase of exampleN03 cc Sets some default verbose flags and initializes the graphics control verbose 2 control saveHistory run verbose 2 run particle dumpCutValues Create empty scene world is default vis
101. in Section 2 1 Within this class all particles and physics processes to be used in your simulation must be defined The range cut off parameter should also be defined in this class The user must create a class derived from G4VuserPhysicsList and implement the following pure virtual methods ConstructParticle construction of particles ConstructProcess construct processes and register them to particles SetCuts setting a range cut value for all particles This section provides some simple examples of the Const ructParticle and SetCuts methods For information on Const ructProcess methods please see Section 2 5 2 4 1 Particle Definition Geant4 provides various types of particles for use in simulations ordinary particles such as electrons protons and gammas resonant particles with very short lifetimes such as vector mesons and delta baryons nuclei such as deuteron alpha and heavy ions including hyper nuclei quarks di quarks and gluon Each particle is represented by its own class which is derived from G4ParticleDefinition Exception G4lons represents all heavy nuclei Please see Section 5 3 Particles are organized into six major categories lepton meson baryon boson shortlived and ion each of which is defined in a corresponding sub directory under geant 4 source particles There is also a corresponding granular library for each particle category 2 4 1 1 The
102. in Z For example to create a box that is 2 by 6 by 10 centimeters in full length and called BoxA one should use the following code G4Box aBox new G4Box BoxA 1 0 cm 3 0 cm 5 0 cm Cylindrical Section or Tube Similarly to create a cylindrical section or tube one would use the constructor G4Tubs const G4String amp pName G4double pRMin G4double pRMax G4double pDz G4double pSPhi G4double pDPhi In the picture pRMin 10 pRMax 15 pDz 20 giving its name pName and its parameters which are pRMin Inner radius pRMax Outer radius 59 Detector Definition and Response pDz half length in z pSPhi the starting phi angle in ra dians pDPhi the angle of the segment in radians Cone or Conical section Similarly to create a cone or conical section one would use the constructor G4Cons const G4String amp G4double G4double G4double G4double G4double G4double G4double pName pRminl pRmaxl pRmin2 pRmax2 pDz pSPhi pDPhi In the picture pRminl 5 pRmaxl 10 pRmin2 20 pRmax2 25 pDz 40 pSPhi 0 pDPhi 4 3 Pi giving its name pName and its parameters which are pRminl inside radius at pDz pRmaxl outside radius at pDz pRmin2 inside radius at pDz pRmax2 outside radius at pDz pDz half length in z pSPhi starting angle of the seg ment in radians pDPhi the angle of the segment in radians Parallelepiped
103. in the end might be more or less perfomant and more or less optimised depending on several factors also related to the system architecture which it applies to A peculiarity of C compilers nowadays is the way templated instances are treated during the compilation linkage process Some C compilers need to store temporarily template instantiation files object files or temporary source code files in a template repository or directory that can be specified as unique or not directly from the compilation command probably historically coming from the old cfront based implementation of the C compiler After the installation of the libraries we strongly suggest to always distinguish between the installation directory identified by G4INSTALL and the working directory identified by G4WORKDIR in order not to alter the installation area for the template repository In Geant4 the path to the template repository for those compilers which make use of it is specified by the environment variable G4TREP which is fixed and points by default to G4WORKDIR tmp G4SYSTEM g4 ptrepository where SG4SYSTEM identifies the system architecture compiler currently used and SGAWORKDIR is the path to the user working directory for Geant4 A secondary template repository G4TREP exec is created by default and can be used when building executables to isolate the main repository used for building the libraries in case of clashes provoked by conflicting
104. innerRa dius 20 outerRadius 30 G4Hype is shaped with curved sides parallel to the z axis has a specified half length along the z axis about which it is centred and a given minimum and maximum radius A minimum radius of 0 defines a filled Hype with hyperbolic inner surface i e inner radius 0 AND inner stereo angle 0 The inner and outer hyperbolic surfaces can have different stereo angles A stereo angle of 0 gives a cylindrical surface innerRadius Inner radius outerRadius Outer radius 67 Detector Definition and Response Inner stereo angle in radians innerStereo outerStereo Outer stereo angle in radians halfLenZ Half length in Z Tetrahedra A tetrahedra solid can be defined as follows G4Tet const G4String amp pName G4ThreeVector anchor G4ThreeVector p2 G4ThreeVector p3 G4ThreeVector p4 G4bool degeneracyFlag 0 In the picture anchor 0 0 sgrt 3 p2 0 2 sqrt 2 3 1 sart 3 p3 sqrt 2 sqrt 2 3 1 sqrt 3 p4 sqrt 2 sqrt 2 3 1 sgrt 3 The solid is defined by 4 points in space anchor Anchor point p2 Point 2 p3 Point 3 p4 Point 4 degeneracyFlag Flag indicating degeneracy of points Extruded Polygon The extrusion of an arbitrary polygon extruded solid with fixed outline in the defined Z sections can be defined as follows in a general way or as special construct
105. into account In the case of division along kRho of G4Cons G4Polycone G4Polyhedra if width is provided it is taken as the width at the Z radius the width at other radii will be scaled to this one 85 Detector Definition and Response Examples are given below in listings Example 4 4 and Example 4 5 Example 4 5 An example of a box division along different axes with or without offset G4Box motherSolid new G4Box motherSolid 0 5 m 0 5 m 0 5 m G4LogicalVolume motherLog new G4LogicalVolume motherSolid material mother 0 0 0 G4Para divSolid new G4Para divSolid 0 512 m 1 21 m 1 43 m G4LogicalVolume childLog new G4LogicalVolume divSolid material child 0 0 0 G4PVDivision divBoxl division along X giving nDiv childLog motherLog kXAxis 5 0 G4PVDivision divBox2 division along X giving width and offset childLog motherLog kXAxis 0 1 m 0 45 m G4PVDivision divBox3 division along X giving nDiv width and offset childLog motherLog kXAxis 3 0 1 m 0 5 m e divBoxl is a division of a box along its X axis in 5 equal copies Each copy will have a dimension in meters of T0 2 dos d e divBox2 is a division of the same box along its X axis with a width of 0 1 meters and an offset of 0 5 meters As the mother dimension along X of 1 meter 0 5 m of halflength the division will be sized in total 1 0 45 0 55 meters Therefore there s space for 5 copies the fir
106. is a boolean flag to control the visibility of objects that are passed to the Visualization Manager for visualization Visibility is set with the following access function void G4VisAttributes SetVisibility G4bool visibility If you give alse to the argument and if culling is activated see below visualization is skipped for objects for which this set of visualization attributes is assigned The default value of visibility is true 238 Visualization Note that whether an object is visible or not is also affected by the current culling policy which can be tuned with visualization commands By default the following public static function is defined static const G4VisAttributes amp GetInvisible which returns a reference to a const object in which visibility is set to false It can be used as follows experimentalHall_logical gt SetVisAttributes G4VisAttributes GetInvisible Direct access to the public static const data member G4VisAttributes Invisible is also possible but deprecated on account of initialisation issues with dynamic libraries 8 6 2 Colour 8 6 2 1 Construction Class G4Colour an equivalent class name G4Color is also available has 4 fields which represent the RGBA red green blue and alpha components of colour Each component takes a value between 0 and 1 If an irrele vant value i e a value less than 0 or greater than 1 is given as an argument of the constructor such a value
107. momentum etc These same attributes can be displayed as labels on the relevant objects and you can make visibility cuts based on these attributes show me only the photons or omit any volumes made of iron WIRED3 can read heprep files in zipped format as well as unzipped so you can save space by applying gzip to the heprep file This will reduce the file to about five percent of its original size Several environment variables are available to override some of HepRepFile s defaults You can specify a different directory for the heprep output files by setting the environment variable G4HEPREPFILE_DIR as in export G4HEPREPFILE_DIR someOtherDir someOtherSubDir You can specify a different file name the part before the number by setting the environment variable G4HEPREPFILE_NAME as in export G4HEPREPFILE_NAME myFileName which will produce files named myFileNameO heprep myFileName 1 heprep etc You can specify that each file should overwrite the previous file always rewriting to the same file name by setting the environment variable G4HEPREPFILE OVERWRITE as in export G4HEPREPFILE_OVERWRITE 1 This may be useful in some automated applications where you always want to see the latest output file in the same location Geant4 visualization supports a concept called culling by which certain parts of the detector can be made invisible Since you may want to control visibility from the HepRep browser turning on visibility of
108. netscape Of course the command path to the VRML viewer should be properly set 2 Log in to the remote host where a Geant4 executable is placed 3 Set an environment variable on the remote host as follows Remote_Host gt setenv G4VRML_HOST_NAME local_host_name For example if you are working on the local host named arkoop kek jp set this environment variable as follows Remote_Host gt setenv G4VRML_HOST_NAME arkoop kek jp This tells a Geant4 process running on the remote host where Geant4 Visualization should be performed i e where the visualized views should be displayed 4 Invoke a Geant4 process and perform visualization with the VRML Network driver For example Idle gt vis open VRML2 Idle gt vis drawVolume Idle gt vis viewer update In step 4 3D scene data are sent from the remote host to the local host as VRML formatted data and the VRML viewer specified in step 3 is invoked by the g4vrmlview process to visualize the VRML data The transferred VRML data are saved as a file named g4 wr1 in the current directory of the local host Further information http geant4 kek jp GEANT4 vis GEANT4 VRML_net_driver html Further information VRML drivers http geant4 kek jp GEANT4 vis GEANT4 VRML_file_driver html http geant4 kek jp GEANT4 vis GEANT4 VRML_net_driver html Sample VRML files http geant4 kek jp GEANT4 vis GEANT4 VRML2_FIG Further information VRML language and browsers e http www vrm
109. of matter density state temperature pressure and macro scopic quantities like radiation length mean free path dE dx etc Only the G4Material class is visible to the rest of the toolkit and used by the tracking the geometry and the physics It contains all the information relevant to its constituent elements and isotopes while at the same time hiding their implementation details 4 2 2 Introduction to the Classes 4 2 2 1 G4lsotope A G4Isotope object has a name atomic number number of nucleons mass per mole and an index in the table The constructor automatically stores this isotope in the isotopes table which will assign it an index number 106 Detector Definition and Response 4 2 2 2 G4Element A G4Element object has a name symbol effective atomic number effective number of nucleons effective mass of a mole an index in the elements table the number of isotopes a vector of pointers to such isotopes and a vector of relative abundances referring to such isotopes where relative abundance means the number of atoms per volume In addition the class has methods to add one by one the isotopes which are to form the element A G4Element object can be constructed by directly providing the effective atomic number effective number of nucleons and effective mass of a mole if the user explicitly wants to do so Alternatively a G4Element object can be constructed by declaring the number of isotopes of which it wi
110. or second order surfaces and checking their intersections 4 1 11 2 Detecting overlaps built in kernel commands In general the most powerful clash detection algorithms are provided by CAD systems treating the intersection between the solids in their topological form Geant4 provides some built in run time commands to activate verification tests for the user defined geometry geometry test grid_test recursion_flag to start verification of geometry for overlapping regions based on standard lines grid setup If the recursion flag is set to false the default the check is limited to the first depth level of the geometry tree otherwise it visits recursively the whole geometry tree In the latter case it may take a long time depending on the complexity of the geometry geometry test cylinder test recursion flag shoots lines according to a cylindrical pattern If the recursion flag is set to false the default the check is limited to the first depth level of the geometry tree otherwise it visits recursively the whole geometry tree In the latter case it may take a long time depending on the complexity of the geometry geometry test line test recursion flag shoots a line according to a specified direction and position defined by the user If the recursion flag is set to false the default the check is limited to the first depth level of the geometry tree otherwise it visits recursively the whole ge
111. oriented features of C such as robustness Instead Geant4 provides an ASCII file interface for such event generators G4HEPEvtInterface is one of G4VPrimaryGenerator concrete class and thus it can be used in your G4VUserPrimaryGeneratorAction concrete class G4HEPEvtinterface reads an ASCII file produced by an event generator and reproduces G4PrimaryParticle objects associated with a G4PrimaryVertex object It re produces a full production chain of the event generator starting with primary quarks etc In other words G4HEPEvtInterface converts information stored in the HEPEVT common block to an object oriented data structure Because the HEPEVT common block is commonly used by almost all event generators written in FORTRAN G4HEPEvtInterface can interface to almost all event generators currently used in the HEP commu nity The constructor of G4HEPEVvtInterface takes the file name Example 3 3 shows an example how to use G4HEPEvtInterface Note that an event generator is not assumed to give a place of the primary particles the interaction point must be set before invoking GeneratePrimaryVertex method Example 3 3 An example code for G4HEPEvtInterface ifndef ExN04PrimaryGeneratorAction h define ExN04PrimaryGeneratorAction h 1 include G4VUserPrimaryGeneratorAction hh include globals hh class G4VPrimaryGenerator class G4Event class ExN04PrimaryGeneratorAction public G4VUserPrimaryGeneratorAction
112. particle particleGun SetParticleDefinition G4Geantino GeantinoDefinition particleGun SetParticleEnergy 1 0 GeV particleGun SetParticlePosition G4ThreeVector 2 0 m 0 0 m 0 0 m ExNOlPrimaryGeneratorAction ExNOlPrimaryGeneratorAction delete particleGun void ExNO1PrimaryGeneratorAction generatePrimaries G4Event anEvent G4int i anEvent gt get eventID 3 switch i ewe Us particleGun SetParticleMomentumDirection G4ThreeVector 1 0 0 0 0 0 break Case Ia particleGun gt SetParticleMomentumDirection G4ThreeVector 1 0 0 1 0 0 break oase Z8 particleGun SetParticleMomentumDirection GAThreeVector 1 0 0 0 0 1 break particleGun generatePrimaryVertex anEvent 2 6 1 1 Selection of the generator In the constructor of your G4VUserPrimaryGeneratorAction you should instantiate the primary generator s If necessary you need to set some initial conditions for the generator s 15 Getting Started with Geant4 Running a Simple Example In Example 2 19 G4ParticleGun is constructed to use as the actual primary particle generator Methods of G4ParticleGun are described in the following section Please note that the primary generator object s you con struct in your G4VUserPrimaryGeneratorAction concrete class must be deleted in your destructor 2 6 1 2 Generation of an event G4VUserPrimaryGeneratorAction has a pure virtual method named generatePrimaries This meth
113. per channel Models can be selected by energy range particle type material etc Data encapsulation and polymorphism make it possible to give transparent access to the cross sections independently of the choice of reading from an ascii file or of interpolating from a tabulated set or of computing analytically from a formula Electromagnetic and hadronic physics were handled in a uniform way in such a design opening up the physics to the users 6 Hits and Digitization These two categories manage the creation of hits and their use for the digitization phase The basic design and implementation of the Hits and Digi had been realized and also several prototypes test cases and scenarios had been developed before the alpha release Volumes not necessarily the ones used by the tracking are aggregated in sensitive detectors while hits collections represent the logical read out of the detector Different ways of creating and managing hits collections had been delivered and tested notably for both single hits and calorimetry hits types In all cases hits collections had been successfully stored into and retrieved from an Object Data Base Management System 7 Visualization This manages the visualization of solids trajectories and hits and interacts with underlying graphical libraries the Visualization class category The basic and most frequently used graphics functionality had been imple mented already by the alpha release The OO design of th
114. performed with the DAWN driver the visualized view is automatically saved to a file named g4 eps in the current directory which describes a vectorized Encapsulated PostScript data of the view There are two kinds of DAWN drivers the DAWNFILE driver and the DAWN Network driver The DAWNFILE driver is usually recommended since it is faster and safer in the sense that it is not affected by network conditions The DAWNFILE driver sends 3D data to DAWN via an intermediate file named g4 prim in the current direc tory The file g4 prim can be re visualized later without the help of Geant4 This is done by invoking DAWN by hand 3 dawn g4 prim DAWN files can also serve as input to two additional programs A standalone program DAWNCUT can perform a planar cut on a DAWN image DAWNCUT takes as input a prim file and some cut parameters Its output is a new prim file to which the cut has been applied Another standalone program DAVID can show you any volume overlap errors in your geometry DAVID takes as input a prim file and outputs a new prim file in which overlapping volumes have been highlighted The use of DAVID is described in section Section 4 1 11 of this manual The DAWN Network driver is almost the same as the DAWNFILE driver except that 3D data are passed to DAWN via the TCP IP the socket default or the named pipe and that If you have not set up network configurations of your host machine set the environment variabl
115. plus some Windows availability Rendered photorealistic image with some interactive features zoom rotate translate Fast response can usually exploit full potential of graphics hardware Limited printing ability pixel graphics not vector graphics Openlnventor View directly from Geant4 Requires addition of OpenInventor libraries freely available for most Linux systems Rendered photorealistic image Many interactive features zoom rotate translate click to see inside opaque volumes Fast response can usually exploit full potential of graphics hardware Expanded printing ability vector and pixel graphics HepRep WIRED 204 Visualization Create a file to view in the WIRED3 HepRep Browser or the WIRED4 JAS Plugin Requires WIRED browser a Java application easily to install on all operating systems Wireframe or simple area fills not photorealistic Many interactive features zoom rotate translate click to show attributes momentum etc special projections FishEye etc control visibility from hierarchical tree view of data Hierarchical view of the geometry Export to many vector graphic formats PostScript PDF etc DAWN Create a file to view in the DAWN Renderer Requires DAWN available for all Linux and Windows systems Rendered photorealistic image No interactive features Highest quality technical rendering output to vector PostScript VRML Create a file
116. requires the installation of the XercesC DOM parser An example of how to import and export a detector description model based on GDML is provided and can be found in examples extended gdml A description on how to define a geometry in GDML together with an annotated example is provided in the GDML example page 4 1 14 Saving geometry tree objects in binary format The Geant4 geometry tree can be stored in the Root binary file format using the reflection technique provided by the Reflex tool included in Root Such a binary file can then be used to quickly load the geometry into the memory or to move geometries between different Geant4 applications See Chapter 4 6 for details and references 4 2 Material 4 2 1 General considerations In nature materials chemical compounds mixtures are made of elements and elements are made of isotopes Geant4 has three main classes designed to reflect this organization Each of these classes has a table which is a static data member used to keep track of the instances of the respective classes created G4Isotope This class describes the properties of atoms atomic number number of nucleons mass per mole etc G4Element This class describes the properties of elements effective atomic number effective number of nucleons ef fective mass per mole number of isotopes shell energy and quantities like cross section per atom etc G4Material This class describes the macroscopic properties
117. scene create Add volume to scene vis scene add volume Create a scene handler for a specific graphics system Edit the next line s to choose another graphic system vis sceneHandler create DAWNFILE vis sceneHandler create OGLIX Create a viewer vis viewer create Draw scene vis scene notifyHandlers for drawing the tracks if too many tracks cause core dump gt storeTrajectory 0 tracking storeTrajectory 1 vis scene include trajectories Also this example demonstrates that you can read and execute a macro interactively Idle gt control execute mySubMacro mac 2 10 How to Visualize the Detector and Events 2 10 1 Introduction This section briefly explains how to perform Geant4 Visualization The description here is based on the sample program examples novice N03 More details are given in Chapter 8 Visualization Example macro files can be found in examples novice N03 visTutor exN03VisX mac 2 10 2 Visualization Drivers The Geant4 visualization system was developed in response to a diverse set of requirements 1 Quick response to study geometries trajectories and hits 2 High quality output for publications 3 Flexible camera control to debug complex geometries 4 Tools to show volume overlap errors in detector geometries 5 Interactive picking to get more information on visualized objects No one graphics system is ideal for all of these requirements and many of the lar
118. string default means directory is not changed from the current value void SetPhysicsTableRetrieved const G4String amp directory void SetStoredInAscii Reset Retrieve flag void ResetPhysicsTableRetrieved 186 User Actions void ResetStoredInAscii TA AAA TUT AAA AA TEED QUU TQ ATA TAT ALATA AA TAA ATA ATA AAA public with description Print out the List of registered particles types void DumpList const public with description Request to print out information of cut values Printing will be performed when all tables are made void DumpCutValuesTable G4int nParticles 3 The following method actually trigger the print out requested by the above method This method must be invoked by RunManager at the proper moment void DumpCutValuesTableIfRequested public with description void SetVerboseLevel G4int value G4int GetVerboseLevel const set get controle flag for output message du rg Sucker 1 Warning message 2 More PAE TTY TAD AAAS AAA AA TAA AAA ATMA OD ATA TAT AAG MAM TAM ADA TATA AMAA TAA public with description SetCutsWithDefault method sets the default cut value Teh for all particles for the default region void SetCutsWithDefault Following are utility methods for SetCuts SetCutValue sets a cut value for a particle type for the default region void SetCutValue G4double aCut const G4String amp pname
119. the apparatus in a setup has a diameter of two meters a likely maximum acceptable steplength would be 10 meters A particle 115 Detector Definition and Response could then take large spiral steps but would not attempt to take for example a 1000 meter long step in the case of a very low density material Similarly for problems of a planetary scale such as the earth with its radius of roughly 6400 km a maximum acceptabe steplength of a few times this value would be reasonable An upper limit for the size of a step is a parameter of G4PropagatorInField and can be set by calling its SetLargestAcceptableStep method The minimum step size is used during integration to limit the amount of work in difficult cases It is possible that strong fields or integration problems can force the integrator to try very small steps this parameter stops them from becoming unnecessarily small Trial steps smaller than this parameter will be treated with less accuracy and may even be ignored depending on the situation The minimum step size is a parameter of the MagInt_Driver but can be set in the contstructor of G4ChordFinder as in the source listing above 4 3 2 8 Known Issues Currently it is computationally expensive to change the miss distance to very small values as it causes tracks to be limited to curved sections whose bend is smaller than this value The bend is the distance of the mid point from the chord between endpoints F
120. the dictionary for the given classes using the genreflex tool from ROOT this usually is done by adding the appropriate command to the makefile 2 Add initialization of ROOT I O and loading of the generated dictionary for the given classes in the appropriate part of the code 3 Whenever the objects to be persistified are available call the WriteObject method of TFile with the pointer to the appropriate object as argument usually it is some sort of container like std vector con taining the collection of objects to be persistified The two examples provided in examples extended persistency demonstrate how to perform object persistency using the Reflex mechanism in ROOT I O for storing hits and geometry description 129 Detector Definition and Response 4 7 Parallel Geometries Notice As of Geant4 release 8 2 this functionality for defining parallel geometries is still in beta release We appreciate your feedback 4 7 1 A parallel world Occasionally it is not straightforward to define geometries for sensitive detectors importance geometries or en velopes for shower parameterization to be coherently assigned to volumes in the tracking mass geometry The new parallel navigation functionality allows the user to define more than one worlds simultaneously The new G4Transportation process will see all worlds simultaneously steps will be limited by both boundaries of the mass geometry and parallel geometries In a paral
121. the external decay handler In the former case decays of heavy particles are simulated by an event generator and the primary event contains the decay information G4VPrimaryGenerator automatically attaches any daughter particles to the parent particle as the PreAssignedDecayProducts member of G4DynamicParticle G4Decay adopts these pre assigned daughter particles instead of asking G4VDecayChannel to generate decay products In addition the user may assign a pre assigned decay time for a specific track in its rest frame i e decay time is defined in the proper time by using the G4PrimaryParticle SetProperTime method G4VPrimaryGenerator sets the PreAssignedDecayProperTime member of G4DynamicParticle G4Decay uses this decay time instead of the life time of the particle type 5 2 4 Photolepton hadron Processes To be delivered 5 2 5 Optical Photon Processes A photon is considered to be optical when its wavelength is much greater than the typical atomic spacing In GEANT4 optical photons are treated as a class of particle distinct from their higher energy gamma cousins This implementation allows the wave like properties of electromagnetic radiation to be incorporated into the optical photon process Because this theoretical description breaks down at higher energies there is no smooth transition as a function of energy between the optical photon and gamma particle classes For the simulation of optical photons to work correctly in GEANT
122. the program In the present example the appl yCommand method is called three times to direct the program to print out information at the run event and tracking levels of simulation A wide range of commands is available which allows the user detailed control of the simulation A list of these commands can be found in Section 7 1 2 1 3 User Initialization and Action Classes 2 1 3 1 Mandatory User Classes There are three classes which must be defined by the user Two of them are user initialization classes and the other is a user action class They must be derived from the abstract base classes provided by Geant4 G4VUserDetectorConstruction G4VuserPhysicsList and G4VuserPrimaryGeneratorAction Geant4 does not pro vide default behavior for these classes G4RunManager checks for the existence of these mandatory classes when the initialize and BeamOn methods are invoked As mentioned in the previous section G4VUserDetectorConstruction requires the user to define the detector and G4VUserPhysicsList requires the user to define the physics Detector definition will be discussed in Sections Section 2 2 and Section 2 3 Physics definition will be discussed in Sections Section 2 4 and Section 2 5 The user action G4VuserPrimaryGeneratorAction requires that the initial event state be defined Primary event generation will be discussed in Section 2 7 2 1 3 2 Optional User Action Classes Geant4 provides five user hook classes G4UserRunA
123. the three vector G4ThreeVector GetNew3VectorValue G4String paramString Convert the G4String parameter value given by the SetNewValue method of your messenger into a G4ThreeVector e G4String convertToString G4ThreeVector currVal Convert the current three vector to G4String which should be returned by the Get Current Value method of your messenger G4UlcmdWithADoubleAndUnit This is a G amp UIcommand derived class which takes one double type parameter and its unit e G4UIcmdWithADoubleAndUnit char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramName G4bool omittable Define the name of the double parameter and set the omittable flag If omittable is true you should define the default value using the next method void SetDefaultValue G4double defVal Define the default value of the double parameter void SetUnitCategory char unitCategory Define acceptable unit category void SetDefaultUnit char defUnit Define the default unit Please use this method and the SetUnitCategory method alternatively e G4double GetNewDoubleValue G4String paramString Convert G4String parameter value given by the SetNewValue method of your messenger into double Please note that the return value has already been multiplied by the value of the given unit e G4double GetNewDoubleRawValue G4String paramStri
124. then calculates the scattered photon s new direction by requiring that it be perpendicular to the photon s new polarization in such a way that the final direction initial and final polarizations are all in one plane This process thus depends on the particle s polarization spin The photon s polarization is a data member of the G4DynamicParticle class A photon which is not assigned a polarization at production either via the SetPolarization method of the G4PrimaryParticle class or indirectly with the SetParticlePolarization method of the G4ParticleGun class may not be Rayleigh scattered Optical photons produced by the G4Cerenkov process have inherently a polarization perpendicular to the cone s surface at production Scintillation photons have a ran dom linear polarization perpendicular to their direction The process requires a G4MaterialPropertiesTabletobe filled by the user with Rayleigh scattering length data The Rayleigh scattering attenuation length is the average distance traveled by a photon before it is Rayleigh scattered in the medium and it is the distance returned by the Get MeanFreePath method The G40pRayleigh class provides aRayleighAttenuationLengthGenerator method which calculates the attenuation coef 161 Tracking and Physics ficient of a medium following the Einstein Smoluchowski formula whose derivation requires the use of statistical mechanics includes temperature and depends on the isothermal compressibilit
125. these and other parameters and how to choose different Integration Steppers 113 Detector Definition and Response The user can also create their own type of field inheriting from G4VF iela and an associated Equation of Motion class inheriting from G4EqRhs to simulate other types of fields 4 3 2 4 Choosing a Stepper Runge Kutta integration is used to compute the motion of a charged track in a general field There are many general steppers from which to choose of low and high order and specialized steppers for pure magnetic fields By default Geant4 uses the classical fourth order Runge Kutta stepper which is general purpose and robust If the field is known to have specific properties lower or higher order steppers can be used to obtain the same quality results using fewer computing cycles In particular if the field is calculated from a field map a lower order stepper is recommended The less smooth the field is the lower the order of the stepper that should be used The choice of lower order steppers includes the third order stepper G4SimpleHeum the second order G4ImplicitEuler and G4SimpleRunge and the first order G4ExplicitEuler A first order stepper would be useful only for very rough fields For somewhat smooth fields intermediate the choice between second and third order steppers should be made by trial and error Trying a few different types of steppers for a particular field or application is suggested if maxi
126. to define the physical volumes according to which scoring and or importance sampling is applied The user has the choice to score and or sample by importance the particles of the chosen type according to mass geometry or to parallel geometry It is possible to utilize several parallel geometries in addition to the mass ge ometry This provides the user with a lot of flexibility to define separate geometries for different particle types in order to apply scoring or and importance sampling Note Parallel geometries should be constructed using the implementation as described in Section 4 7 There are a few conditions for parallel geometries The world volume for parallel and mass geometries must be identical copies Scoring and importance cells must not share boundaries with the world volume 3 7 1 2 Changing the Sampling Samplers are higher level tools which perform the necessary changes of the Geant4 sampling in order to apply importance sampling and weight roulette Variance reduction and scoring through the G4MultiFunctionalDetector may be combined arbitrarily for chosen particle types and may be applied to the mass or to parallel geometries The G4Geomet rySampler can be applied equally to mass or parallel geometries with an abstract interface supplied by G4VSampler G4VSampler provides Prepare methods and a Configure method class G4VSampler public G4vSampler 49 Toolkit Fundamentals virtual G4VSampl
127. to take care of the deletion of any additional transformation or rotation matrices allocated dinamically in his her own application 4 1 4 1 Placements single positioned copy In this case the Physical Volume is created by associating a Logical Volume with a Rotation Matrix and a Transla tion vector The Rotation Matrix represents the rotation of the reference frame of the considered volume relatively to its mother volume s reference frame The Translation Vector represents the translation of the current volume in the reference frame of its mother volume Transformations including reflections are not allowed To create a Placement one must construct it using G4PVPlacement G4RotationMatrix pRot const G4ThreeVector amp ie bere G4LogicalVolume pCurrentLogical const G4String pName G4LogicalVolume pMotherLogical G4bool pMany G4int pCopyNo G4bool pSurfChk false where pRot Rotation with respect to its mother volume tlate Translation with respect to its mother volume pCurrentLogical The associated Logical Volume pName String identifier for this placement pMotherLogical The associated mother volume pMany For future use Can be set to false pCopyNo Integer which identifies this placement pSurfChk if true activates check for overlaps with existing vol umes Care must be taken because the rotation matrix is not copied by a GAPVPlacement So the user must not modify it after creating a Place
128. volume PhantomContainer name world logic mother volume false No op bool create an 0 object of type 96 Detector Definition and Response 1 Copy number The physical volume should be assigned as the container volume of the parameterisation param gt BuildContainerSolid cont_phys Assure that the voxels are completely filling the container volume Hi param gt CheckVoxelsFillContainer cont solid GetXHalfLength cont solid GetyHalfLength cont solid GetzHalfLength The parameterised volume which uses this parameterisation is placed in the container logical volume Al G4PVParameterised patient phys new G4PVParameterised Patient name patient logic logical volume GOD Our mother volume kXAxis optimisation hint nVoxelX nVoxelY nVoxelZ number of voxels param parameterisation Indicate that this physical volume is having a regular structure patient phys gt SetRegularStructureId 1 An example showing the application of the optimised navigation algorithm for phantoms geometries is avail able in examples extended medical DICOM It implements a real application for reading DICOM im ages and convert them to Geant4 geometries with defined materials and densities allowing for different imple mentation solutions to be chosen non optimised classical 3D optimisation nested parameterisations and use of G4PhantomParameterisation
129. which do not need to output event by event data but instead just accumulate them All the G4VPrimitiveScorer classes discussed in Section 4 4 5 use G4THitsMap G4THitsMap is derived from the G4VHitsCollection abstract base class and all objects of this class are also stored in G4HCofThisEvent at the end of an event How to access a G4THitsMap object is discussed in the following section Section 4 4 5 4 4 2 Sensitive detector G4VSensitiveDetector G4VSensitiveDetector is an abstract base class which represents a detector The principal mandate of a sensitive de tector is the construction of hit objects using information from steps along a particle track The ProcessHits method of G4VSensitiveDetector performs this task using G4Step objects as input In the case of a Readout geometry see Section 4 4 3 objects of the G4TouchableHistory class may be used as an optional input Your concrete detector class should be instantiated with the unique name of your detector The name can be associated with one or more global names with as a delimiter for categorizing your detectors For example myEMcal new MyEMcal myDet myCal myEMcal where myEMcal is the name of your detector The pointer to your sensitive detector must be set to one or more G4LogicalVolume objects to set the sensitivity of these volumes The pointer should also be registered to G4SDManager as described in Section 4 4 4 G4VSensitiveDetector has three major vir
130. you may do so either before or after initializing visManager gt RegisterGraphicsSytem new XXX 207 Visualization visManager gt Initialize By default you get the DAWNFILE HepRepFile RayTracer VRMLIFILE VRML2FILE ATree and GAGTree drivers Additionally you may choose from the OpenGL Xlib OpenGL Motif OpenInventor RayTracerX DAWN Network and VRML Network drivers each of which can be selected by setting the proper environment variable setenv G4VIS USE OPENGLX setenv G4VIS USE OPENGLXM setenv G4VIS USE OIX setenv G4VIS USE RAYTRACERX setenv G4VIS USE DAWN setenv G4VIS USE VRML BR ERB Of course this has to be chosen from the set incorporated into the Geant4 libraries during their compilation Unless the environment variable G4VIS NONE is set these set C pre processor flags of the same name Also unless the environment variable GAVIS NONE is set the C pre processor flag GAVIS USE is always set by default This flag is available in describing the main function You may have to set additional environment variables for your selected visualization drivers and graphics systems For example the OpenGL driver may reguire the setting of OGLHOME which points to the location of the OpenGL libraries For more details see Section 8 3 Visualization Drivers and pages linked from there 8 2 3 ASample Set up File The following can be part of the user s cshrcor tcshrc file ona Linux platform to con
131. 0 PAN NACE 280 2 25 VAIS Gaid s EE 280 2 3 Open Scientist Lab 3 ses sist ele ais aus si i ka sa REED a IA i es 280 DA CAIDAS iiy pe Rete er E a TUE a Oe UR be ru IR Tt eve Patch en 280 poc der EE 281 3 CLHEP Foundation Library sec ertt eripe e prit Ere TASSE pE RR Ere ee 281 4 C Standard Template Library sees He mem emere 281 5 Makefiles and Environment Variables esee em emen 281 5 1 The GNUmake system in Geant4 oo sss emere 282 5 2 Environment variables 5c Petr ed eer HERR ed ERR RCR ERROR REPRE Eni T 282 5 3 Linking External Libraries with Geant4 Lukaa aaa aaa aaa aaa kaka aaa meme 287 6 Step by Step Installation Guides csiis eretiers hehe rhe asas 288 6 1 Building on MS Visual C Lukaa aaa aaa aaa aa e e III HII He mener mener rennen 288 7 Development and debug tools reete rrt tires e Er sis Ss 289 TA UNIX sia ania si das aa i a I aka aa PI iig 289 8 Geant4 Material Database 52 5 5 etre tt rre i a i a a a as 289 8 T Pure Materials oe ie ASG A le ais sa 289 8 2 NIST Compounds 2 rr Eros i Ei sk sis Vi i si ss i sa Das sis ai 290 8 3 HEP Materials si aiti das ia ni i akas ais yn aa sien oad Ais eres eee des RAM ss 301 BibliOSraphY M LEE 302 Chapter 1 Introduction 1 1 Scope of this manual The User s Guide for Application Developers is the first manual the reader should consult when learning about Geant4 or developing a Geant4 base
132. 0935 6 0 585374 7 0 113773 8 0 259918 2 G4_NITROUS_OXIDE 0 00183094 84 7 0 636483 8 0 363517 4 G4 NYLON 8062 1 08 64 1 0 103509 6 0 648416 7 0 0995361 8 0 148539 4 G4 NYLON 6 6 1 14 63 X 0 097976 6 0 636856 7 0 123779 8 0 141389 4 G4 NYLON 6 10 1 14 63 RE 0 107062 6 0 680449 zi 0 099189 8 0 1133 4 G4 NYLON 11 RILSAN 1 425 61 1 0 115476 6 0 720818 7 0 0764169 8 0 0872889 2 G4_OCTANE 0 7026 54 0 158821 6 0 841179 2 G4 PARAFFIN 0 93 55 0 148605 6 0 851395 2 G4_N PENTANE 0 6262 53 0 167635 6 0 832365 8 G4 PHOTO EMULSION 3 815 331 0 0141 6 0 072261 T 0 01932 297 Appendix G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 G4 8 0 0 16 0 0 35 0 3 47 0 4 53 0 0 PLASTIC SC V 1 0 0 6 0 9 PLUTONIUM DIO 8 02 94 0 8 POLYACRYLONIT 0 0 6 0 6 7 0 2 POLYCARBONATE 0 0 6 0 7 8 0 1 POLYCHLOROSTY 0 0 6 0 6 7 0 2 POLYETHYLENE 0 1 6 0 8 YLAR 0 0 6 0 6 8 0 3 PLEXIGLASS 0 0 6 0 5 8 0 3 POLYOXYMETHYL 0 0 6 0 4 8 0 5 POLYPROPYLENE 1 Ord 6 0 8 POLYSTYRENE 2 0 0 6 0 9 TEFLON 6 0 2 9 0 7 POLYTRIFLUORO 6 0 2 9 0 4 7 0 3 POLYVINYL ACE 0 0 6 0 5 8 0 3 POLYVINYL ALC 0 0 6 0 5 8 0 3 POLYVINYL BUT 0 0 6 0 6 8 0 2 POLYVINYL CHL 0 0 6 0 3 7 0 5 POLYVINYLIDE 0 0 6 0 2 7 0 7 POLYVINYLIDE 0 0 6 0 3 66101 0189 49103 74105 0312 NYLTOLUENE 1 0
133. 1 kStateGas temperature pressure steam gt AddMaterial H20 fractionmass 1 What about vacuum Vacuum is an ordinary gas with very low density density universe mean density rom PhysicalConstants h pressure l e 19 pascal temperature 0 1 kelvin new G4Material name Galactic z 1 a 1 01 g mole density kStateGas temperature pressure density 1 e 5 g cm3 pressure Ope 2 bar temperature STP Temperature from PhysicalConstants h G4Material beam new G4Material name Beam density ncomponents 1 kStateGas temperature pressure beam gt AddMaterial Air fractionmass 1 print the table of materials G4cout lt lt G4Material GetMaterialTable lt lt endl 109 Detector Definition and Response return EXIT_SUCCESS As can be seen in the later examples a material has a state solid the default liquid or gas The constructor checks the density and automatically sets the state to gas below a given threshold 10 mg cm3 In the case of a gas one may specify the temperature and pressure The defaults are STP conditions defined in PhysicalConstants hh An element must have the number of nucleons gt number of protons gt 1 A material must have non zero values of density temperature and pressure Materials can also be defined using the internal Geant4 database Example 4 11 illustrates how to do this for the same materials used in Example 4 10 There are als
134. 1 public ExN04PrimaryGeneratorAction ExNO4PrimaryGeneratorAction public void GeneratePrimaries G4Event anEvent private G4vPrimaryGenerator HEPEvt hi endif include ExN04PrimaryGeneratorAction hh include G4Event hh include G4HEPEvtInterface hh ExN04PrimaryGeneratorAction ExN04PrimaryGeneratorAction HEPEvt new GA4HEPEvtInterface pythia event data ExNO4PrimaryGeneratorAction ExNO4PrimaryGeneratorAction delete HEPEvt void ExN04PrimaryGeneratorAction GeneratePrimaries G4Event anEvent HEPEvt gt SetParticlePosition G4ThreeVector 0 cm 0 cm 0 cm HEPEvt gt GeneratePrimaryVertex anEvent 47 Toolkit Fundamentals 3 6 2 2 Format of the ASCII file An ASCII file which will be fed by G4HEPEvtInterface should have the following format The first line of each primary event should be an integer which represents the number of the following lines of primary particles e Each line in an event corresponds to a particle in the HEPEVT common Each line has ISTHEP IDHEP JDAHEP 1 JDAHEP 2 PHEP 1 PHEP 2 PHEP 3 PHEP 5 Refer to the HEPEVT manual for the meanings of these variables Example 3 4 shows an example FORTRAN code to generate an ASCII file Example 3 4 A FORTRAN example using the HEPEVT common KKKKKK KKK ck ck ck ck ck ck ckckck ck ckckckckckckckckckckckckck ck ckckck ck ck ck
135. 137 Tracking and Physics AddSecondary G4DynamicParticle aSecondary G4double time In all but the first the construction of G4Track is done in the methods using informaton given by the arguments 5 1 4 User Actions There are two classes which allow the user to intervene in the tracking These are e G4UserTrackingAction and G4UserSteppingAction Each provides methods which allow the user access to the Geant4 kernel at specific points in the tracking For details see the Software Reference Manual 5 1 5 Verbose Outputs The verbose information output flag can be turned on or off The amount of information printed about the track step from brief to very detailed can be controlled by the value of the verbose flag for example G4UImanager UI G4UImanager GetUIpointer UI gt ApplyCommand tracking verbose 1 5 1 6 Trajectory and Trajectory Point G4Trajectory and G4TrajectoryPoint G4Trajectory and G4TrajectoryPoint are default concrete classes provided by Geant4 which are derived from the G4VTrajectory and G4VTrajectoryPoint base classes respectively A G4Trajectory class object is created by G4TrackingManager when a G4Track is passed from the G4EventManager G4Trajectory has the following data members ID numbers of the track and the track s parent particle name charge and PDG code acollection of G4TrajectoryPoint pointers G4TrajectoryPoint corresponds to a step point along the path foll
136. 32 85 15 XIDE 11 46 18055 81945 RILE Ld 569829 79055 63962 55491 55751 88758 RENE ee 61869 96325 41806 64 746 69 13 81 C 2H 4 N Polyethylene 0 94 43711 56289 41959 25016 33025 80538 99848 19614 ENE 425 67135 00017 32848 0 9 43711 56289 77418 22582 40183 59817 CHLOROETHYLENE 2 1 0625 89354 04395 TATE 19 70245 58066 71689 OHOL 3 91517 45298 63185 YRAL 12 92802 80561 26637 ORIDE 3 4838 8436 6726 E_CHLORIDE 1 7 20793 47793 31414 E_FLUORIDE 1 76 3148 75141 19 Ou 78 74 77 4 C 2H 4 N Polypropylene 56 5 68 7 oot 120 7 73 7 69 7 67 2 134 3 88 8 298 Appendix 13 9 0 5933 G4 POLYVINYL PYRROL d 0 0816 6 0 6484 7 0 1260 8 0 1439 G4 POTASSIUM IODIDE 9 0 2355 53 0 7644 G4 POTASSIUM OXIDE 8 0 1698 9 0 830 G4 PROPANE 0 1828 6 0 817 G4 lPROPANE 0 1828 6 0 817 G4 N PROPYL ALCOHOL 0 134 6 0 5995 8 0 2662 G4 PYRIDINE 0 0637 6 0 7592 7 0 1770 G4 RUBBER BUTYL 0 1437 6 0 8562 G4 RUBBER NATURAL 0 1183 6 0 8816 G4 RUBBER NEOPRENE 0 0569 6 0 5426 7 0 4004 G4 SILICON DIOXIDE 8 0 5325 4 0 4674 G4 SILVER BROMIDE 35 0 4255 47 0 5744 G4 SILVER CHLORIDE y 0 2473 47 0 7526 G4 SILVER HALIDES 35 0 4228 47 0 5731 53 0 0033 G4 SILVER IODIDE 47 0 4594 53 0 5405 G4 SKIN ICRP 0 1005 6 0 2282 7 0 0464 8 0 6190 1 7e 05 2 6
137. 37 Toolkit Fundamentals smooth trajectory points G4SmoothTrajectoryPoint aSmoothTrajectoryPointAllocator ray trajectories G4RayTrajectory G4RayTrajectoryAllocator ray trajectory points G4RayTrajectoryPoint G4RayTrajectoryPointAllocator For each of these allocators accessible from the global namespace it is possible to monitor the allocation in their memory pools or force them to release the allocated memory for example at the end of a run Return the size of the total memory allocated for tracks aTrackAllocator GetAllocatedSize Return allocated storage for tracks to the free store aTrackAllocator ResetStorage G4ReferenceCountedHandle Template class acting as a smart pointer and wrapping the type to be counted It performs the reference counting during the life time of the counted object G4FastVector Template class defining a vector of pointers not performing boundary checking G4PhysicsVector Defines a physics vector which has values of energy loss cross section and other physics values of a particle in matter in a given range of the energy momentum etc This class serves as the base class for a vector hav ing various energy scale for example like log G4PhysicsLog Vector linear G4PhysicsLinearVector free G4PhysicsFree Vector etc G4LPhysicsFreeVector Implements a free vector for low energy physics cross section data A subdivision method is used to find t
138. 4 Switch physics processes Inthe InitializePhysics method G4VUserPhysicsList Construct is invoked in order to de fine particles and physics processes in your application Basically you can not add nor remove any particles during execution because particles are static objects in Geant4 see Section 2 4 and Section 5 3 for details In addition it is very difficult to add and or remove physics processes during execution because registration procedures are very complex except for experts see Section 2 5 and Section 5 2 This is why the initializePhysics method is assumed to be invoked at once in Geant4 kernel initialization However you can switch on off physics processes defined in your G4VUserPhysicsList concrete class and also change parameters in physics processes during the run break 44 Toolkit Fundamentals You can use ActivateProcess and InActivateProcess methods of G4ProcessManager any where outside the event loop to switch on off some process You should be very careful to switch on off processes inside the event loop though it is not prohibited to use these methods even in the EventProc state It is a likely case to change cut off values in a run You can change defaultCutValue in G4VUserPhysicsList during the dle state In this case all cross section tables need to be recalculated before the event loop You should use the CutOffHasBeenModified method when you change cut off values so that the Set Cuts me
139. 4 8 1 Command based scoring sss eene menthe rene 132 4 82 Defining a scoring mesh i uii dete prete eet ia Saag ese i 133 4 8 3 DraWwiD SCOLES MNT EE 133 4 8 4 Writing scores foa file 1e adis iais ye as ii a i Ho Eina sa e sis i Es 134 2 Tracking and PHYSICS iere sa E i aga is Phi si ig pesdwanabeecdeia been cthieecossibes 135 5 E Tracking irt rr e roe t et RE EE Ct br Pa Eo a i bends oane ae 135 23 11 Basic Concepts sicr Ee er Mesa ogg scher G ii dota ea Pete ve ae Er Soin egy 135 5 1 2 Access to Track and Step Information sese HH 136 5 1 3 Handling of Secondary Particles 20 0 0 cece cece aaa aa aa aa cece Hem 137 514 User ACHOS Gor cete Cet mete sa ete leant si i Ki Fe atte te ER peris 138 3 1 5 Verbose Outputs e RE eene a oes reete rep opo ee E ERE Ded 138 5 1 6 Trajectory and Trajectory Point 1 5 crederet PESE EOP EE UPOS EEES S 138 3 2 Physics PrOCeSSeS ice en nne bep sa sia a Is sa I aa sa a EE irren ss 139 5 2 1 Electromagnetic Interactions ime ter RE EE ai ES 141 3 222 Hadronic Interactions i eee sedi na dos se asis epe va asi sk sa E os 150 5 2 3 Particle Decay Process tik i in s kiss Ere Eee Ere inser ss ds Das S 155 5 2 4 Photolepton hadron Processes LL aaa aaa aa aaa aaa aaa e e eH meme enne 157 5 2 5 Optical Photon Processes 1 ette terere retro dete Ee Perte e eaten eben Rl 157 3 2 6 Par metenzation LiL eme enero Win ORE ERE sias ii 164
140. 4Region object is automatically assigned to the world volume and is referred to as the default region The production cuts for this region are the defaults which are defined in the UserPhysicsList Unless the user defines different cut values for other regions the cuts in the default region will be used for the entire geometry Please note that the default region and its default production cuts are created and set automatically by G4RunManager The user is not allowed to set a region to the world volume nor to assign other production cuts to the default region 5 5 3 Assigning Production Cuts to a Region In the SetCuts method of the user s physics list the user must first define the default cuts Then a G4ProductionCuts object must be created and initialized with the cut value desired for a given region This ob ject must in turn be assigned to the region object which can be accessed by name from the G4RegionStore An example SetCuts code follows 177 Tracking and Physics Example 5 12 Setting production cuts to a region void MyPhysicsList SetCuts default production thresholds for the world volume SetCutsWithDefault Production thresholds for detector regions G4Region region G4String regName G4ProductionCuts cuts regName tracker region G4RegionStore GetInstance gt GetRegion regName cuts new G4ProductionCuts cuts gt SetProductionCut 0 01 mm same cuts for gamma e
141. 4Track objects All of G4Track objects representing the primary particles are sent to G4StackManager Pop one G4Track object from G4StackManager and send it to G4TrackingManager The current G4Track object is deleted by G4EventManager after the track is simulated by G4TrackingManager if the track is marked as killed In case the primary track is suspended or postponed to next event by G4TrackingManager it is sent back to the G4StackManager Secondary G4Track objects returned by G4TrackingManager are also sent to G4StackManager When G4StackManager returns NULL for the pop request G4EventManager terminates the current processing event invokes the user defined methods beginOfEventAction and endOfEventAction from the G4UserEventAction class See Section 6 3 for details 3 5 4 Stacking mechanism G4StackManager has three stacks named urgent waiting and postpone to next event which are objects of the G4TrackStack class By default all G4Track objects are stored in the urgent stack and handled in a last in first 45 Toolkit Fundamentals out manner In this case the other two stacks are not used However tracks may be routed to the other two stacks by the user defined G4UserStackingAction concrete class If the methods of G4UserStackingAction have been overridden by the user the postpone to next event and waiting stacks may contain tracks At the beginning of an event G4StackManager checks to see if any
142. 5 cm G4double startAngleOfTheTube 0 deg G4double spanningAngleOfTheTube 360 deg G4Tubs tracker_tube new G4Tubs tracker tube innerRadiusOfTheTube outerRadiusOfTheTube hightOfTheTube startAngleOfTheTube spanningAngleOfTheTube This creates a full cylinder named tracker tube of radius 60 centimeters and length 50 cm 2 2 4 Create a Logical Volume To create a logical volume you must start with a solid and a material So using the box created above you can create a simple logical volume filled with argon gas see materials by entering G4LogicalVolume experimentalHall_log new G4LogicalVolume experimentalHall_box Ar expHall_log This logical volume is named expHall log Similarly we create a logical volume with the cylindrical solid filled with aluminium G4LogicalVolume tracker_log new G4LogicalVolume tracker tube Al tracker log and named tracker log 2 2 5 Place a Volume How do you place a volume You start with a logical volume and then you decide the already existing volume inside of which to place it Then you decide where to place its center within that volume and how to rotate it Once you have made these decisions you can create a physical volume which is the placed instance of the volume and embodies all of these atributes 2 2 6 Create a Physical Volume You create a physical volume starting with your logical volume A physical volume is simply a placed instance
143. 52 7 Transportation Process i eite eere ther rm E Pee REPE ER Pr sK 170 2 3 Particles i e rea eE ne EEE eben ctp EUH biu PE ee Ep ROSS 170 5 3 Basic CONCEPIS Li artem ERREUR E UA er ER ee Ese RR Retard pea eret E heit o 170 3 32 Definition of particle i iere teret preset e eR eee RISE 171 5 3 3 Dynamic particle 1 5 irte repe FERRE EE PR aa ES E eS 174 5 4 Production Threshold versus Tracking Cut sss eee 174 5 4 General considerations ette p Pete te ue tre soon seeks cep Eee pU ae trei Ret 174 5 4 2 Set production threshold Set Cut methods seem 175 5 5 3 Apply cut rete e hn PR eh EHE E REPRE DEOR e S ia RET 175 5 4 4 Why produce secondaries below threshold Lake aaa aa aaa aaa aa aaa 175 5 4 5 Cuts in stopping range or in energy Lui aaa cece ee aaa s aa eee eee 176 23 16 Summary ree seg aaa E Ua rer as a a en si ss soe teas 176 5 47 Special tracking cuts eren ete gero Ri Va a REP RR 176 5 5 Cuts per REGION i i eI EDU IRE ees 177 25 9 General Concepts 52 sete pre o rb oe deae a POR De ete ka ea dite Ere dera dst 177 3 5 2 Default R gion 2 dai a e a sis La eiga EIS RI abe E scene deeds 177 5 5 3 Assigning Production Cuts to a Region sess eee 177 3 6 Physics Table 2A Sie iusque eiii 178 5 6 1 General Concepts 1 dott reo Pe tee Feb agree t a re EE ve emE rend 178 vi Geant4 User s Guide for Application Developers 5 6 2 Material Cuts Co
144. 7 746 771 G4 Ir 22 42 757 78 G4 Pt 21 45 790 79 G4_Au 19 32 790 80 G4 Hg 13 546 800 81 G4 Tl 11 72 810 82 G4 Pb 11 35 823 83 G4 Bi 9 747 823 84 G4 Po 9 32 830 85 G4 At 9 32 825 86 G4 Rn 0 00900662 794 87 G4 Fr 1 827 88 G4 Ra 5 826 89 G4 Ac 0 07 841 90 G4 Th 1 72 847 91 G4 Pa 5 37 878 92 GA U 8 95 890 93 G4 Np 20 25 902 94 G4 Pu 9 84 921 95 G4 Am 3 67 934 96 G4 Cm 3 51 939 97 G4_Bk 4 952 98 G4 Cf 0 966 8 2 NIST Compounds Ncomp Name density g cm 3 I eV 6 G4 A 150 TISSUE 1 127 65 1 1 0 101327 6 0 7755 Jg 0 035057 8 0 0523159 9 0 017422 20 0 018378 3 G4 ACETONE 0 7899 64 2 1 0 104122 6 0 620405 8 0 275473 290 Appendix 13 14 G4_ACETYLENE 0 077418 6 0 922582 G4_ADENINE 0 037294 6 0 44443 F 0 518276 G4_ADIPOSE_TISSUE_ICRP 0 119477 6 0 63724 7 0 00797 8 0 232333 1 0 0005 2 2e 05 5 0 00016 6 0 00073 7 0 00119 9 0 00032 20 2e 05 26 2e 05 30 2e 05 G4_AIR 6 0 000124 7 0 755268 8 0 231781 8 0 012827 G4_ALANINE 0 0791899 6 0 404439 7 0 157213 8 0 359159 G4_ALUMINUM_OXIDE Al 20 3 8 0 470749 3 0 529251 G4_AMBER 0 10593 6 0 788974 8 0 105096 G4_AMMONIA 0 177547 7 0 822453 G4_ANILINE 0 075759 6 0 773838 7 0 150403 G4 ANTHRACENE 0 05655 6 0 94345 G4_B 100_BONE 0 0654709 6 0 536944 7 0 0215 8 0 032085 9 0 167411 20 0 176589 G4_BAKELITE ds 0 057441 6 0 774591 8 0 167968 G4_BARIUM_FLUORIDE 9 0 21672 56 0 78328 G4_BARIUM_SULFATE 8 0 274212 16 0 137368 56
145. 8 4 2 Geometry volume target When the user chooses a GAErrorGeomVolumeTarget as target the track is propagated until the surface of a GEANTA volume is reached User can choose if the track will be stopped only when the track enters the volume only when the track exits the volume or in both cases The object has to be instantiated giving the name of a logical volume existing in the geometry G4ErrorGeomVolumeTarget const G4String amp name 5 8 4 3 Track Length target When the user chooses a G4ErrorTrackLengthTarget as target the track is propagated until the given track length is reached The object has to be instantiated giving the value of the track length G4ErrorTrackLengthTarget const G4double maxTrkLength It is implemented as a GAVDiscreteProcess and it limits the step in Post StepGetPhysicalInter actionLength To ease its use the process is registered to all particles in the constructor 5 8 5 Managing the track propagation The user needs to propagate just one track so there is no need of run and events neither of G4VPrimaryGeneratorAction G4ErrorPropagator creates a track from the information given in the G4ErrorTrajState and manages the step propagation The propagation is done by the standard GEANT4 methods invoking G4SteppingManager Stepping to propagate each step After one step is propagated G4ErrorPropagator takes cares of propagating the track errors for this step what is done by G4Erro
146. 9 6 0 456179 7 0 035172 8 0 40678 G4 TISSUE PROPANE i 0 102672 6 0 56894 Zi 0 035022 8 0 293366 G4 TITANIUM DIOXIDE 8 0 400592 22 0 599408 G4 TOLUENE 0 08751 6 0 91249 G4 TRICHLOROETHYLENE 0 007671 6 0 182831 7 0 809498 G4 TRIETHYL PHOSPHATE 0 082998 6 0 395628 8 0 351334 5 0 17004 9707 5805 234 04 1 625 7 004 00106409 00182628 26 8669 46 07 67 7 TRS Theol LS 1 5912 690 3 T2 3 74 9 61 2 29155 179 5 62 5 148 1 81 2 300 Appendix 2 G4_TUNGSTEN_HEXAFLUORIDE 2 4 354 4 9 0 382723 74 0 617277 2 G4_URANIUM_DICARBIDE 11 28 752 6 0 091669 92 0 908331 2 G4_URANIUM_MONOCARBIDE 13 63 862 6 0 048036 92 0 951964 2 G4_URANIUM_OXIDE 10 96 720 6 8 0 118502 92 0 881498 4 G4_UREA 13323 72 8 0 067131 6 0 199999 7 0 466459 8 0 266411 4 G4_VALINE 1 23 67 7 d 0 0946409 6 0 512644 H 0 119565 8 0 27315 3 G4 VITO 1 8 98 6 0 009417 6 0 280555 9 0 710028 2 G4 WATER H 20 1 75 0 111894 8 0 888106 2 G4 WATER VAPOR H 20 Gas 0 000756182 71 6 0 111894 8 0 888106 2 G4 XYLENE 0 87 61 8 0 094935 6 0 905065 1 G4_GRAPHITE Graphite Leal 78 8 3 HEP Materials Ncomp Name density g cm 3 I eV 1 G4 1H2 0 0708 21 8 1 G4 lAr 1 396 188 Bh G4 1Kr 2 418 352 I G4 1Xe 2 953 482 3 G4 PbWO4 8 28 0 8 0 140637 82 0 455366 74 0 403998 1 G4 Galactic 1e 25 21 8 301 Bibliography Booch1994
147. A they must be imputed a linear polarization This is unlike most other particles in GEANTA but is automatically and correctly done for optical photons that are generated as secondaries by existing processes in GEANT4 Not so if the user wishes to start optical photons as primary particles In this case the user must set the linear polarization using particle gun methods the General Particle Source or his her PrimaryGeneratorAction For an unpolarized source the linear polarization should be sampled randomly for each new primary photon The GEANTA catalogue of processes at optical wavelengths includes refraction and reflection at medium bound aries bulk absorption and Rayleigh scattering Processes which produce optical photons include the Cerenkov ef fect transition radiation and scintillation Optical photons are generated in GEANT4 without energy conservation and their energy must therefore not be tallied as part of the energy balance of an event The optical properties of the medium which are key to the implementation of these types of processes are stored as entries in a GaMaterialPropertiesTable which is linked to the G4Material in question These properties may be constants or they may be expressed as a function of the photon s wavelength This table is a private data member of the G4Material class The GaMaterialPropertiesTable is implemented as a hash directory in which each entry consists of a value and a key The key is used to quickly
148. A parallelepiped is constructed using G4Para const G4String amp pName G4double dx G4double dy G4double d2 G4double alpha G4double theta G4double phi dx 30 dy 40 dz 60 giving its name pName and its parameters which are dx dy dz Half length in x y z 60 Detector Definition and Response alpha Angle formed by the y axis and by the plane joining the centre of the faces parallel to the z x plane at dy and dy theta Polar angle of the line joining the centres of the faces at dz and dz in z phi Azimuthal angle of the line joining the centres of the faces at dz and dz in z Trapezoid To construct a trapezoid use G4Trd const G4String amp pName G4double G4double G4double G4double G4double daxi dx2 dyl dy2 dz In the picture dxl 30 dx2 10 dyl 40 dy2 15 dz 60 to obtain a solid with name pName and parameters dx1 Half length along x at the surface positioned at dz dx2 gt Half length along x at the surface positioned at dz dyl Half length along y at the surface positioned at dz dy2 gt Half length along y at the surface positioned at dz dz Half length along z axis Generic Trapezoid To build a generic trapezoid the G4Trap class is provided Here are the two costructors for a Right Angular Wedge and for the general trapezoid for it G4Trap const G4String amp pName G4Trap const
149. BREPs solids Pcons Pgons are supported at present All related parameters of such a solid can be specified in a parameter widget Users will be able to view each solid using DAWN 4 1 9 3 Logical Volume GGE can specify the following items Name Solid Material VisAttribute The construction and assignment of appropriate entities for G4FieldManager and G4VSensitiveDetector are left to the user 4 1 9 4 Physical Volume A single copy of a physical volume can be created Also repeated copies can be created in several manners First a user can translate the logical volume linearly Name Logi Mother Many XO YO ZO Direction StepSize Unit CopyNum calVolume Volume ber Combined translation and rotation are also possible placing an object repeatedly on a cylindrical pattern Simple models of replicas and parametrised volume are also implemented In the replicas a volume is slices to create new sub volumes In parametrised volumes several patterns of volumes can be created 4 1 9 5 Generation of C code MybetectorConstruction cc By simply pushing a button source code in the form of an include file and a source file are created They are called MyDetectorConstruction cc and hh files They reflect all current user modifications in real time 4 1 9 6 Visualization Examples of individual solids can be viewed with the help of DAWN The visualization of the whole geome
150. C colIDSum i j mapSum i j evtMap for size_t k 0 k lt 3 k G4THitsMap lt G4double gt evtMap G4THitsMap lt G4double gt HCE gt GetHC colIDMin i k std map lt G4int G4double gt iterator itr evtMap gt GetMap gt begin for itr evtMap gt GetMap gt end itr G4int key itr gt first G4double val itr gt second G4double mapP mapMin i k key if mapP amp amp val gt mapP continue mapMin i k set key val 4 4 6 Concrete classes of G4VPrimitiveScorer With Geant4 version 8 0 several concrete primitive scorer classes are provided all of which are derived from the G4VPrimitiveScorer abstract base class and which are to be registered to G4MultiFunctionalDetector Each of them contains one G4THitsMap object and scores a simple double value for each key 124 Detector Definition and Response Track length scorers G4PSTrackLength The track length is defined as the sum of step lengths of the particles inside the cell Bt default the track weight is not taken into account but could be used as a multiplier of each step length if the Weighted method of this class object is invoked G4PSPassageTrackLength The passage track length is the same as the track length in G4PSTrackLength except that only tracks which pass through the volume are taken into account It means newly generated or stopped tracks inside the cell are excluded from the calculation
151. Classes implementing the Gauss Chebyshev Gauss Hermite Gauss Jacobi Gauss Laguerre and Gauss Leg endre quadrature methods Roots of orthogonal polynomials and corresponding weights are calculated based on iteration method by bisection Newton algorithm G4Integrator Template class collecting integrator methods for generic functions Legendre Simpson Adaptive Gauss La guerre Hermite Jacobi G4SimpleIntegration Class implementing simple numerical methods Trapezoidal MidPoint Gauss Simpson Adaptive Gauss for integration of functions with signature double f double 3 2 4 General management classes The global category defines also a set of utility classes generally used within the kernel of Geant4 These classes include G4Allocator A class for fast allocation of objects to the heap through paging mechanism It s meant to be used by associating it to the object to be allocated and defining for it new and delete operators via MallocSingle and FreeSingle methods of G4Allocator Note classes which are handled by G4Al locator should avoid to be used as base classes for others and therefore define their eventually empty destructors to be virtual and or inlined Such measure is necessary in order to prevent bad aliasing optimisations by compilers which may potentially lead to crashes in the attempt to free the allocated chunks of memory The list of allocators implicitely defined and used in Geant4 is reported h
152. Example N01 G4VPhysicalVolume experimentalHall phys new G4PVPlacement 0 no rotation G4ThreeVector 0 0 0 translation position experimentalHall_log its logical volume expHall its name 0 its mother volume false no boolean operations 0 its copy number 2 2 7 Coordinate Systems and Rotations In Geant4 the rotation matrix associated to a placed physical volume represents the rotation of the reference system of this volume with respect to its mother A rotation matrix is normally constructed as in CLHEP by instantiating the identity matrix and then applying a rotation to it This is also demonstrated in Example N04 2 3 How to Specify Materials in the Detector 2 3 1 General Considerations In nature general materials chemical compounds mixtures are made of elements and elements are made of isotopes Therefore these are the three main classes designed in Geant4 Each of these classes has a table as a static data member which is for keeping track of the instances created of the respective classes The G4Element class describes the properties of the atoms atomic number number of nucleons atomic mass shell energy as well as quantities such as cross sections per atom etc The G4Material class describes the macroscopic properties of matter density state temperature pressure as well as macroscopic quantities like radiation length mean free path dE
153. ForAbortState_H define UserHookForAbortState_H 1 include G4VStateDependent hh class UserHookForAbortState public G4VStateDependent public UserHookForAbortState FI COSE EOR UserHookForAbortState destructor virtual G4bool Notify G4ApplicationState requiredState i 42 Toolkit Fundamentals Example 3 2 Source file of UserHookForAbortState include UserHookForAbortState hh UserHookForAbortState UserHookForAbortState UserHookForAbortState UserHookForAbortState G4bool UserHookForAbortState Notify G4ApplicationState requiredState if requiredState Abort return true Do book keeping here ESCRITO MEETS A 3 4 4 Customizing the Run Manager 3 4 4 1 Virtual Methods in the Run Manager G4RunManager is a concrete class with a complete set of functionalities for managing the Geant4 kernel It is the only manager class in the Geant4 kernel which must be constructed in the main method of the user s application Thus instead of constructing the G4RunManager provided by Geant4 you are free to construct your own RunManager It is recommended however that your RunManager inherit G4RunManager For this purpose G4RunManager has various virtual methods which provide all the functionalities required to handle the Geant4 kernel Hence your customized run manager need only override the methods particular to your needs the remaining methods in G4RunManager base class can sti
154. G4InelasticInteraction puolto G4LEProtonInelastic G4InelasticInteraction SetMinEnergy 020 jy SetMaxEnergy 25 GeV G4LEProtonInelastic G4ParticleChange ApplyYourself const G4Track aTrack G4Nucleus amp targetNucleus private void CascadeAndCalculateMomenta required arguments include G4LEProtonInelastic hh G4ParticleChange G4LEProton Inelastic ApplyYourself const G4Track amp aTrack G4Nucleus amp targetNucleus theParticleChange Initialize aTrack const G4DynamicParticle incidentParticle aTrack GetDynamicParticle create the target particle G4DynamicParticle targetParticle targetNucleus ReturnTargetParticle CascadeAndCalculateMomenta required arguments O return amp theParticleChange 154 Tracking and Physics The CascadeAndCalculateMomenta function is the bulk of the model and is to be provided by the model s creator It should determine what secondary particles are produced in the interaction calculate the momenta for all the particles and put this information into the ParticleChange object which is returned The G4LEProtonInelastic class derives from the G4InelasticInteraction class which is an abstract base class since the pure virtual function ApplyYourself is not defined there G4InelasticInteraction itself derives from the G4HadronicInteraction abstract base class This class is the base class for all the model classes It sorts out the energ
155. G4NeutronHPElasticData G4NeutronHPCaptureData G4NeutronHP FissionData and G4NeutronHPInelasticData For detailed descriptions of the low energy neutron total cross sections they may be registered by the user as described above with the data stores of the corresponding processes for neutron interactions It should be noted that using these total cross section classes does not require that the neutron_hp models also be used It is up to the user to decide whethee this is desirable or not for his particular problem 5 2 2 2 Hadrons at Rest List of implemented Hadron at Rest processes The following process classes have been implemented pi absorption class name G4PionMinusAbsorptionAtRest or G4PiMinusAbsorptionAtRest kaon absorption class name G4KaonMinusAbsorptionAtRest or G4KaonMinusAbsorption neutron capture class name G4NeutronCaptureAtRest anti proton annihilation class name G4AntiProtonAnnihilationAtRest anti neutron annihilation class name G4AntiNeutronAnnihilationAtRest mu capture class name G4MuonMinusCaptureAtRest alternative CHIPS model for any negativly charged particle class name G4QCaptureAtRest Obviously the last process does not strictly speaking deal with a hadron at rest It does nonetheless share common features with the others in the above list because of the implementation model chosen The differences between the alternative implementation for kaon and pion absorption concer
156. G4UImanager getUlpointer G4String command control execute G4String fileName argv 1 UI gt applyCommand command fileName delete runManager return 0 This example will be executed with the command gt myProgram runi mat where myP rogram is the name of your executable and run1 mac is a macro of commands located in the current directory which could look like Example 2 22 A typical command macro Macro file for myProgram cc set verbose level for this run run verbose 2 event verbose 0 d tracking verbose Set the initial kinematic and run 100 events electron 1 GeV to the direction 1 0 0 gun particle e gun energy 1 GeV run beamOn 100 Indeed you can re execute your program with different run conditions without recompiling anything Digression many G4 category of classes have a verbose flag which controls the level of verbosity 22 Getting Started with Geant4 Running a Simple Example Usually verbose 0 means silent For instance run verbose is for the RunManager e event verbose is for the EventManager e tracking verbose is for the TrackingManager etc 2 9 4 Interactive Mode Driven by Command Lines Below is an example of the main program for an application which will run interactively waiting for command lines entered from the keyboard Example 2 23 An example of the main routine for an application which will run interactively waiting f
157. G4VHitsCollection an abstract class which represents a vector collection of user defined hits G4THitsCollection is a template class derived from G4VHitsCollection and the concrete hit collection class of a particular G4VHit concrete class can be instantiated from this template class Each object of a hit collection must have a unique name for each event G4Event has a G4HCofThisEvent class object that is a container class of collections of hits Hit collections are stored by their pointers whose type is that of the base class An example of a concrete hit class Example 4 14 shows an example of a concrete hit class Example 4 14 An example of a concrete hit class ifndef ExN04TrackerHit h define ExN04TrackerHit h 1 include G4VHit hh include G4THitsCollection hh include G4Allocator hh include G4ThreeVector hh class ExN04TrackerHit public G4VHit public ExN04TrackerHit ExN04TrackerHit ExN04TrackerHit const ExN04TrackerHit amp right const ExN04TrackerHit amp operator const ExN04TrackerHit amp right int operator const ExN04TrackerHit amp right const inline void operator new size_t inline void operator delete void aHit void Draw const once COSE private G4double edep G4ThreeVector pos jowlailae s inline void SetEdep G4double de edep de inline G4double GetEdep const return edep inline void SetPos G4ThreeVector xyz pos xyz inline G4Th
158. Geant4 Collaboration Geant4 and CLHEP The Geant4 project contributed to the development of CLHEP The random number package physics units and constants and some of the numeric and geometry classes had their origins in Geant4 Geant4 also benefits from the development of CLHEP In addition to the already mentioned classes for random numbers and numerics we use the classes for points vectors and planes and their transformations in 3D space and lorentz vectors and their transformations Although these classes have Geant4 names like G4ThreeVector these are just typedefs to the CLHEP classes 4 C Standard Template Library Overview The Standard Template Library STL is a general purpose library of generic algorithms and data structures It is part of the C Standard Library Nowadays most compiler vendors include a version on STL in their products and there are commercial implementations available as well Good books on STL are e Nicolai M Josuttis The C Standard Library A Tutorial and Reference Josuttis1999 e David R Musser Atul Saini STL Tutorial and Reference Guide C Programming with the Standard Tem plate Library Musser1996 Scott Meyers Effective STL Meyers2001 Resources available online include the reference of the SGI implementation SGI STL homepage this is the basis of the native egcs STL implementation STL in Geant4 Since release 0 1 Geant4 supports STL the Standard Template
159. Geant4 User s Guide for Application Developers Version geant4 9 1 Published 14 December 2007 Geant4 Collaboration Geant4 User s Guide for Application Developers by Geant4 Collaboration Version geant4 9 1 Published 14 December 2007 Table of Contents Ls Introduction 1 eed ete sa a i sia ii Ar a rie Sb at a i i tea nh a a i apd ha piece sess 1 1 1 Scope oF this manual cene eR yi ss Bee ss ss ibe ees ais 1 1 2 How to use this manual ssi erede tee bem Ee E sects sds vedas SR pre CR gs verse SES EEE 1 2 Getting Started with Geant4 Running a Simple Example sss 2 2 1 How to Detine the Main Programi ioci a eR rs rete Ie ps A S i ai Lean 2 2 1 1 amp Sample main Method eerte Kasas sai K a An ei ede av avere e ERI 2 2 12 G4RunMand get 3er be e re isexe ribi 2 2 1 3 User Initialization and Action Classes seem 4 2 1 4 G4UImanager and UI CommandSubmission esee 4 2 1 5 G4cout and G4cefr 5s sein san es asai na a ya E a oi te e y eT BABS a T AE D 2 2 How to Define a Detector Geometry e mense aaa t enm en ee ener 6 22 15 Basic Concepts oer EIUS ag bons 6 2 2 2 Create a Simple Volume 2 ettet Ere ru ERR eT ses ERO see 6 2 2 3 Choose a Solid REESE REP wees OR REI EE eere pese RR 6 2 24 Create Logical Volume 5 P eer RE erra re ania a 7 2 2 3 Place a Volume Louie IRURE RAN EIU AUI REI 7 2 2 6 Cr ate a Physical Volume
160. H ppckov absorption NUMENTRIES scintillator gt SetMaterialPropertiesTable MPT 5 2 5 1 Generation of Photons in processes electromagnetic xrays Cerenkov Effect The radiation of Cerenkov light occurs when a charged particle moves through a dispersive medium faster than the group velocity of light in that medium Photons are emitted on the surface of a cone whose opening angle with respect to the particle s instantaneous direction decreases as the particle slows down At the same time the frequency of the photons emitted increases and the number produced decreases When the particle velocity drops below the local speed of light the radiation ceases and the emission cone angle collapses to zero The photons produced by this process have an inherent polarization perpendicular to the cone s surface at production The flux spectrum polarization and emission of Cerenkov radiation in the AlongStepDoIt method of the class G4Cerenkov follow well known formulae with two inherent computational limitations The first arises from step wise simulation and the second comes from the requirement that numerical integration calculate the average number of Cerenkov photons per step The process makes use of a G4PhysicsTable which contains incremental integrals to expedite this calculation The time and position of Cerenkov photon emission are calculated from quantities known at the beginning of a charged particle s step The step is assumed to be
161. However the executables created are debuggable using the debugger of MS Visual Studio You may have to help the debugger finding the path to source files the first time you debug a given executable Listed below are some useful pages with instructions on how to start with the installation of CygWin and also tips for creating a project under Visual Studio Getting started with Cygwin Cygwin Installation Notes Building a MSVC Visual Studio 2005 Geant4 project 288 Appendix 7 Development and debug tools 7 1 UNIX Although not in the scope of this user manual in this appendix section we provide a set of references to rather known and established development tools and environments we think are useful for code development in C in general It s a rather limited list far from being complete of course e The KDevelop environment on Linux systems e The GNU Data Display Debugger DDD e Valgrind a system for debugging and profiling Linux programs SUN SUN ONE Studio environment former Workshop Microsoft Visual Studio development environment e Parasoft Insure run time debugger and memory checker e Parasoft C Test source code analyzer Rational Rose CASE tool Together ControlCenter development environment Logiscope tool for metrics analysis Rational Unified Process RUP tool for Software engineering 8 Geant4 Material Database 8 1 Pure Materials 1 G4_H 8 3748e 05 19 2 2
162. Idle gt vis sceneHandler create OGLIX Create a viewer Idle gt vis viewer create Draw the scene etc dle gt vis scene notifyHandlers dle gt run verbose 0 dle gt event verbose 0 dle gt tracking verbose 1 dle gt gun particle mu dle gun energy 10 GeV dle run beamOn 1 dle gun particle proton dle gun energy 100 MeV dle run beamOn 3 dle exit For the meaning of the machine state Idle see Section 3 4 2 This mode is useful for running a few events in debug mode and visualizing them Notice that the VisManager is created in the main and the visualization system is choosen via the command vis sceneHandler create OGLIX 2 9 5 General Case Most of the examples in the SG4INSTALL examples directory have the following main which covers cases 2 and 3 above Thus the application can be run either in batch or interactive mode 24 Getting Started with Geant4 Running a Simple Example Example 2 24 The typical main routine from the examples directory int main int argc char argv Construct the default run manager G4RunManager runManager new G4RunManager set mandatory initialization classes NO3DetectorConstruction detector new N03DetectorConstruction runManager gt SetUserInitialization detector runManager SetUserInitialization new NO3PhysicsList ifdef G4VIS USE visualization manager G4VisManager visManager new G4VisExecutive visManager
163. Library From release 1 0 of Geant4 STL is required Native implementations of STL are foreseen on all supported platforms 5 Makefiles and Environment Variables This section describes how the GNUmake infrastructure is implemented in Geant4 and provides a quick reference guide for the user installer about the most important environment variables defined 281 Appendix 5 1 The GNUmake system in Geant4 As described in Section 2 1 of the Installation Guide the GNUmake process in Geant4 is mainly controlled by the following GNUmake script files gmk scripts are placed in SG4INSTALL config e architecture gmk defining all the architecture specific settings and paths System settings are stored in SG4INSTALL config sys in separate files e common gmk defining all general GNUmake rules for building objects and libraries globlib gmk defining all general GNUmake rules for building compound libraries binmake gmk defining the general GNUmake rules for building executables GNUmake scripts placed inside each directory in the G4 distribution and defining directives specific to build a library or a set of sub libraries or and executable To build a single library or a set of sub libraries or an executable you must explicitly change your current directory to the one you re interested in and invoke the gmake command from there gmake global for building a compound library Here is a list of the basic commands or
164. MAX G4double uTrakMax DBL MAX G4double uTimeMax DBL MAX G4double uEkinMin 0 G4double uRangMin 0 uStepMax Maximum step length uTrakMax Maximum total track length uTimeMax Maximum global time for a track uEkinMin Minimum remaining kinetic energy for a track uRangMin Minimum remaining range for a track Note that uStepMax is affecting to each step while all other limits are affecting to a track The user can set G4UserLimits to logical volume and or to a region User limits assigned to logical volume do not propagate to daughter volumes while User limits assigned to region propagate to daughter volumes unless daughters belong to another region If both logical volume and associated region have user limits those of logical volume win 5 7 2 Processes co working with G4UserLimits In addition to instantiating G4UserLimits and setting it to logical volume or region the user has to assign the following process es to particle types he she wants to affect If none of these processes is assigned that kind of particle is not affected by G4UserLimits Limitation to step uSt epMax G4StepLimiter process must be defined to affected particle types This process limits a step but it does not kill a track 179 Tracking and Physics Limitations to track uTrakMax uTimeMax uEkinMin uRangMin G4UserSpecialCuts process must be defined to affected particle types This process limits a step and kills the track
165. Name G4LogicalVolume pCurrentLogical G4LogicalVolume pMotherLogical const EAxis pAxis const G4int nDivisions const G4double offset Giving only the division width G4PVDivision const G4String amp pName G4LogicalVolume pCurrentLogical G4LogicalVolume pMotherLogical const EAxis pAxis const G4double width const G4double offset Giving the number of divisions and the division width G4PVDivision const G4String amp pName G4LogicalVolume pCurrentLogical G4LogicalVolume pMotherLogical const EAxis pAxis const G4int nDivisions 84 Detector Definition and Response const G4double width const G4double offset where pName String identifier for the replicated volume pCurrentLogical The associated Logical Volume pMotherLogical The associated mother Logical Volume pAxis The axis along which the division is applied nDivisions The number of divisions width The width of a single division along the axis offset Possible offset associated to the mother along the axis of division The parameterisation is calculated automatically using the values provided in input Therefore the dimen sions of the solid associated with pCurrentLogical will not be used but recomputed through the G4VParameterisation ComputeDimension method Since G4VPVParameterisation may have different ComputeDimension methods for each solid type the user must provide a solid that is of the s
166. P can be overridden G4LIB G4LIBDIR Used by the system to specify the place where to store libraries By default they re set to G4INSTALL 1lib and 5G4LIB G4SYSTEM respectively G4LIB can be overridden Build specific G4TARGET Specifies the target name of the source file defining the main of the application example to be built This variable is set automatically for the examples and tests placed in SG4INSTALL examples G4EXEC_BUILD Flag specifying if to use a secondary template repository or not for handling template instantiations at the time of building a user application example For internal category tests in Geant4 this variable is already in the related GNUmakefile It s however not needed for examples and tests in G4INSTALL examples where class names are already mangled and different each other It applies only on those compilers which make use of template repositories see Appendix A 2 of this Guide The secondary template repository is set to SG4TREP exec 283 Appendix G4DEBUG Specifies to compile the code libraries or examples including symbolic information in the object code for debugging The size of the generated object code can increase considerably By default code is compiled in optimised mode G40PTIMISE set G4NO_OPTIMISE Specifies to compile the code libraries or examples without compiler optimisation G4_NO_VERBOSE Geant4 code is compiled by default in high verbosity m
167. SetFilter positronFilter det gt RegisterPrimitive primitive primitive new G4PSMinKinEAtGeneration minEkinGamma j primitive gt SetFilter gammaFilter det gt RegisterPrimitive primitive primitive new G4PSMinKinEAtGeneration minEkinElectron j primitive gt SetFilter electronFilter det gt RegisterPrimitive primitive primitive new G4PSMinKinEAtGeneration minEkinPositron j primitive gt SetFilter positronFilter det gt RegisterPrimitive primitive primitive new G4PSTrackLength trackLength j primitive gt SetFilter epFilter det gt RegisterPrimitive primitive primitive new G4PSNofStep nStep j primitive gt SetFilter epFilter det gt RegisterPrimitive primitive 7 G4SDManager Get SDMpointer gt AddNewDetector det aue O layerLogical i gt SetSensitiveDetector det elese gapLogical i gt SetSensitiveDetector det Each G4THitsMap object can be accessed from G4HCofThisEvent with a unique collection ID number This ID number can be obtained from G4SDManager GetCollectionID with a name of G4MultiFunctionalDetector 123 Detector Definition and Response and G4VPrimitiveScorer connected with a slush G4THitsMap has a operator taking the key value as an argument and returning the pointer of the value Please note that the operator returns the pointer of the value If you get zero from the op
168. ShowerModel new GFlashShowerModel fastShowerModel m_calo_region m theParametrisation new GFlashHomoShowerParamterisation matManager getMaterial mat m theParticleBounds GFlashParticleBounds m theHMaker new GFlashHitMaker m theFastShowerModel SetParametrisation m theParametrisation m theFastShowerModel gt SetParticleBounds m theParticleBounds B 0 169 Tracking and Physics m theFastShowerModel gt SetHitMaker m theHMaker The user must also set the material of the calorimeter since the computation depends on the material tis mandatory to use G4VGFlashSensitiveDetector as additional base class for the sensitive detector class ExGflashSensitiveDetector public G4VSensitiveDetector public G4VGFlashSensitiveDetector Here it is necessary to implement a separate interface where the GFlash spots are processed ProcessHits G4GFlashSpot aSpot G4TouchableHistory ROhist A separate interface is used because the Gflash spots naturally contain less information than the full simulation Since the parameters in the Gflash package are taken from fits to full simulations with Geant3 some retuning might be necessary for good agreement with Geant4 showers For experiment specific geometries some retuning might be necessary anyway The tuning is quite complicated since there are many parameters some correlated and cannot be described here see again hep ex 0001020 For brave users the Gflash
169. State Ouit state When the destructor of G4RunManager is invoked the application comes to this dead end state Managers of the Geant4 kernel are being deleted and thus the application cannot come back to any other state G4State_Abort state When a G4Exception occurs the application comes to this dead end state and causes a core dump The user still has a hook to do some safe opperations e g storing histograms by implementing a user concrete class of G4VStateDependent The user also has a choice to suppress the occurence of G4Exception by a UI command control suppressAbortion When abortion is suppressed you will still get error messages issued by G4Exception and there is NO guarantee of a correct result after the G4Exception error message G4StateManager belongs to the intercoms category 3 4 3 User s hook for state change In case the user wants to do something at the moment of state change of Geant4 the user can create a concrete class of the G4VStateDependent base class For example the user can store histograms when G4Exception occurs and Geant4 comes to the Abort state but before the actual core dump The following is an example user code which stores histograms when Geant4 becomes to the Abort state This class object should be mabe in for example main by the user code This object will be automatically registered to G4StateManager at its construction Example 3 1 Header file of UserHookForA bortState ifndef UserHook
170. String PN PN store PN GA4AttDef PN Particle Name Physics G4String G4String IMom IMom store IMom G4AttDef IMom Momentum of track at start of trajectory Physics G4ThreeVector Then fill the attributes with lines such as std vector lt G4AttValue gt values new std vector lt G4AttValue gt values push back G4AttValue PN ParticleName s seekp std ios beg S lt lt G4BestUnit initialMomentum Energy lt lt std ends values push back G4AttValue IMom c See geant4 source tracking src G4Trajectory cc for a good example G4AttValue objects are light containing just the value for the long description and other sharable information the G4ArtValue object refers to a G4AttDef object They are based on the HepRep standard described at http www slac stanford edu perl heprep Geant4 also provides an G4AttDefStore Geant4 provides some default examples of the use of this facility in the trajectory classes in source tracking such as G4Trajectory G4SmoothTrajectory G4Trajectory CreateAttValues shows how G4AttValue objects can be made and G4Trajectory GetAttDefs shows how to make the corresponding G4AttDef objects and use the G4AttDefStore Note that the user of CreateAttValues guarantees to destroy them this is a way of allowing cre ation on demand and leaving the G4Trajectory object for example free of such objects in memory The comments in G4VTraj
171. T new G4MaterialPropertiesTable SMPT AddProperty RINDEX pp rindex NUM SMPT gt AddProperty SPECULARLOBECONSTANT pp specularlobe NUM SMPT gt AddProperty SPECULARSPIKECONSTANT pp specularspike NUM SMPT AddProperty BACKSCATTERCONSTANT pp backscatter NUM SMPT gt AddProperty REFLECTIVITY pp reflectivity NUM SMPT gt AddProperty EFFICIENCY pp efficiency NUM OpSurface gt SetMaterialPropertiesTable SMPT The original GEANT3 21 implementation of this process is also available via the GLISUR methods flag GEANT Detector Description and Simulation Tool Application Software Group Computing and Networks Division CERN PHYS260 6 tp 260 7 163 Tracking and Physics Example 5 11 Dielectric metal surface properties defined via the G4OpticalSurface G4LogicalVolume volume_log G4OpticalSurface OpSurface new G4OpticalSurface name G4LogicalSkinSurface Surface new G4LogicalSkinSurface name volume_log OpSurface OpSurface gt SetType dielectric metal OpSurface SetFinish ground OpSurface SetModel glisur G4double polish 0 8 G4MaterialPropertiesTable OpSurfaceProperty new G4MaterialPropertiesTable OpSurfaceProperty gt AddProperty REFLECTIVITY pp reflectivity NUM OpSurfaceProperty gt AddProperty EFFICIENCY pp efficiency NUM OpSurface gt SetMaterialPropertiesTable OpSurfaceProperty The r
172. The public methods of this class are GetDEDX kinEnergy particle material G4Region region 0 GetRangeFromRestrictedaDEDX kinEnergy particle material G4Region region 0 GetCSDARange kinEnergy particle material G4Region region 0 GetRange kinEnergy particle material G4Region region 0 GetKinEnergy range particle material G4Region region 0 GetCrosSectionPerVolume kinEnergy particle material G4Region region 0 GetMeanFreePath kinEnergy particle material G4Region region 0 PrintDEDXTable particle PrintRangeTable particle PrintInverseRangeTable particle ComputeDEDX kinEnergy particle process material cut DBL_MAX ComputeElectronicDEDX kinEnergy particle material cut DBL_MAX ComputeNuclearDEDX kinEnergy particle material cut DBL_MAX ComputeTotalDEDX kinEnergy particle material cut DBL MAX ComputeCrosSectionPerVolume kinEnergy particle process material cut 0 ComputeCrosSectionPerAtom kinEnergy particle process Z A cut 0 ComputeMeanFreePath kinEnergy particle process material cut 0 ComputeEnergyCutFromRangeCut range particle material FindParticle const G4String amp FindMaterial const G4String amp FindRegion const G4String amp FindCouple const G4Material const G4Region region 0 SetVerbose G4int For these interfaces particles materials or processes may be pointers or strings with names 144 Tracking and Physics 5 2 1 2 Low Energy Electromagnetic Processes The following is a summary of the Low En
173. To control the precision associated to computation of intersections default precision is set to 9 it is possible to use the environmental variable for the DAWNFILE graphics driver as follows setenv G4DAWNFILE PRECISION 10 If necessary re visualize the detector geometry with intersected parts highlighted The data are saved in a file e4david prim in the current directory This file can be re visualized with DAWN as follows 3 dawn g4david prim It is also helpful to convert the generated file g4david prim into a VRML formatted file and perform interactive visualization of it with your WWW browser The file conversion tool prim2wrml can be downloaded from the DAWN web site download pages For more details see the document of DAVID mentioned above 4 1 11 4 Using the geometry debugging tool OLAP OLAP is a tool developed in the CMS experiment at CERN to help in identifying ovelapping volumes in a detector geometry It is placed in the area for specific tools examples in geant 4 examples extended geometry The technique consists in shooting geant inos particles in one direction and the opposite one and verifying that the boundary crossings are the same The tool can be used for any Geant4 geometry provided that the user geometry to be debugged is available as a subclass of G4VUserDetectorConstruction and is used to construct the OlapDetConstr class of the tool A dummy class RandomDetector is provided for this purpose in the tool i
174. TopTransform TransformPoint worldPosition where worldPosition here stays for the position related to the world volume while localPosition refers to the coordinates local to the volume where the particle is currently placed FAQ 4 Tracks and steps Q Howcanlaccess the track information through the step object and what information am I allowed to access A AG4Step object consists of two points G4StepPoint pointl step gt GetPreStepPoint G4StepPoint point2 step GetPostStepPoint 274 Frequentry Asked Questions To get their positions in the global coordinate system G4ThreeVector posl point1 gt GetPosition G4ThreeVector pos2 point2 gt GetPosition Hereafter we call current volume the volume where the step has just gone through Geometrical informations are available from preStepPoint G4VTouchable and its derivates keep these geometrical informa tions We retrieve a touchable by creating a handle for it G4TouchableHandle touchl point1 gt GetTouchableHandle To get the current volume G4VPhysicalVolume volume touchl GetVolume To get its name G4String name volume gt GetName To get the physical volume copy number G4int copyNumber touch1 gt GetCopyNumber To get logical volume G4LogicalVolume 1Volume volume gt GetLogicalVolume To get the associated material the following statements are eguivalent G4Material material pointl gt Ge
175. VPhysicalVolume ghostWorld pdet GetWorldVolume G4GeometrySampler pgs ghostWorld neutron 50 Toolkit Fundamentals pgs SetParallel true Also note that the preparation and configuration of the samplers has to be carried out after the instantiation of the UserPhysicsList and after the initialisation of the G4RunManager pgs PrepareImportanceSampling amp aIstore 0 pgs Configure Due to the fact that biasing is a process and has to be inserted after all the other processes have been created 3 7 1 3 Importance Sampling Importance sampling acts on particles crossing boundaries between importance cells The action taken depends on the importance values assigned to the cells In general a particle history is either split or Russian roulette is played if the importance increases or decreases respectively A weight assigned to the history is changed according to the action taken The tools provided for importance sampling require the user to have a good understanding of the physics in the problem This is because the user has to decide which particle types require importance sampled define the cells and assign importance values to the cells If this is not done properly the results cannot be expected to describe a real experiment The assignment of importance values to a cell is done using an importance store described below An importance store with the interface G4VISt ore is used to store importance valu
176. XML files are visualizable with any XML browser in Windows a good XML viewer is XML Notepad Folding and un folding fi Output XML Notepad File Edit View Insert Tools Help D H 4 RBs dal Pla gt j F IE amp po logical volume solid name solid type EQ Calorimeter copy_no Ps ee logical volume solid name 6 solid type b Layer D uM logical volume solid name solid type Eg Absorber scm copy no logical volume i solid name solid type EMA World For Help press F1 221 Visualization Searching a string 4 Output XML Notepad File Edit View Insert Tools Help D s m e e a EE 5 ol World copy_no POO logical volume solid name solid type Egg Calorimeter copy no Oo logical volume solid name solid type d L6 copy no logical volume solid name 9 solid Find H Abso 9 Gap Find what Layer Search in Content IV Element Tags Attribute Names Attribute Values Comments Direction C Up Down For Help press F1 Match case Cancel 8 4 Controlling Visualization from Commands This section describes just a few of the more commonly used visualization commands For the complete list of commands and options see the Control UICommands sec
177. agement system ODBMS When a usual transient object is created in C the object is placed onto the application heap and it ceases to exist when the application terminates Persistent objects on the other hand live beyond the termination of the application process and may then be accessed by other processes in some cases by processes on other machines Database Environment persistent obiect constructor destructor Application Cache Time Figure 4 9 Persistent object C does not have as an intrinsic part of the language the ability to store and retrieve persistent objects Geant4 provides an abstract framework for persistency of hits digits and events Two examples demonstrating an implementation of object persistency using one of the tools accessible through the available interface is provided in examples extended persistency 4 6 2 Using Reflex for persistency of Geant4 objects Object persistency of Geant4 objects is also possible by the mean of the Reflex library Reflex provides in a non intrusive way reflection capabilities to C classes by generating dictionary information for them Those dictionaries can then be loaded in memory allowing direct persistency of the given objects without any instrumen tation of the code The Reflex library is also part of ROOT since release v5 08 The basic steps that one needs to do in order to use Reflex with ROOT I O for arbitrary C classes is 1 Generate
178. ager ifdef G4VIS_USE visualization manager G4VisManager visManager new G4VisExecutive visManager gt Initialize endif Job termination ifdef G4VIS USE delete visManager endif return 0 f end of C In the instantiation initialization and deletion of the Visualization Manager the use of the macro G4VIS USE is recommended This is set unless the environment variable GAVIS NONE is set This allows one easily to build an executable without visualization if required without changing the code but remember you have to force re compilation whenever you change the environment Note that it is your responsibility to delete the instantiated Visualization Manager by yourself A complete description of a sample main function is described in exam ples novice N03 exampleN03 cc 2 10 5 Sample Visualization Sessions In this section we present typical sessions of Geant4 visualization You can test them with the sample program geant4 examples novice N03 Run a binary executable exampleNO3 without an argument and then execute the commands below in the Idle state Explanation of each command will be described later Note that the OpenGL Xlib driver and the DAWNFILE driver are incorporated into the executable and that Fukui Renderer DAWN is installed in your machine 2 10 5 1 Visualization of detector components The following session visualizes detector components with the OpenGL Xlib driver and the
179. al boundary Thus a drawn trajectory may not be circular Customizing trajectory and trajectory point G4Track and G4Step are transient classes they are not available at the end of the event Thus the concrete classes G4VTrajectory and G4VTrajectoryPoint are the only ones a user may employ for end of event analy sis or for persistency As mentioned above the default classes which Geant4 provides i e G4Trajectory and G4TrajectoryPoint have only very primitive quantities The user can customize his her own trajectory and trajec tory point classes by deriving directly from the respective base classes To use the customized trajectory the user must construct a concrete trajectory class object in the G4UserTrackingAction PreUserTrackingAction method and make its pointer available to G4TrackingManager by using the SetTrajectory method The customized trajectory point class object must be constructed in the Ap pendStep method of the user s implementation of the trajectory class This AppendStep method will be invoked by G4TrackingManager To customize trajectory drawing the user can override the DrawTrajectory method in his her own trajectory class When a customized version of G4Trajectory declares any new class variables operator new and operator delete must be provided It is also useful to check that the allocation size in operator new is equal to sizeof G4Trajectory These two points do not apply to G4VTrajectory because it h
180. ale Sy LONN G4PVReplica repRZPhi RZPhiSlices pRepRZPhiLogical amp repRZ Pod A O mechs OE RepX is an array of 5 replicas of width 10 mm positioned inside and completely filling the volume pointed by pContainingMother The mother s X length must be 5 10 mm 50 mm for example if the mother s solid were a Box of half lengths 25 25 25 then the replica s solid must be a box of half lengths 25 25 5 If the containing mother s solid is a tube of radius 50 mm and half Z length of 25 mm RepR divides the mother tube into 5 cylinders hence the solid associated with pRepRLogical must be a tube of radius 10 mm and half 80 Detector Definition and Response Z length 25 mm repRZ divides it into 5 shorter cylinders the solid associated with pRepRZLogical must be a tube of radius 10 mm and half Z length 5 mm finally repRZPhi divides it into 4 tube segments with full angle of 90 degrees the solid associated with pRepRZPhiLogical must be a tube segment of radius 10 mm half Z length 5 mm and delta phi of M PI 0 5 rad No further volumes may be placed inside these replicas To do so would result in intersecting boundaries due to the r replications Parameterised Volumes Parameterised Volumes are repeated volumes in the case in which the multiple copies of a volume can be different in size solid type or material The solid s type its dimensions the material and the transformation matrix can all be parameterised in f
181. alised navigation it is required to first G4PhantomParameterisation G4PhantomParameterisation param new G4PhantomParameterisation Then fill it with the all the necessary data Voxel dimensions in the three dimensions Ai G Ad ple balt ass CAclowiolke Dal AS 5p GAclowleiks Hariz 6055 param gt SetVoxelDimensions halfX halfY halfZ Number of voxels in the three dimensions G4int nVoxelX G4int nVoxelY G4int nVoxelZ param gt SetNoVoxel nVoxelX nVoxelY nVoxelZ Vector of materials of the voxels std vector lt G4Material gt theMaterials theMaterials push_back new G4Material theMaterials push_back new G4Material param gt SetMaterials theMaterials List of material indices For each voxel it is a number that correspond to the index of its material in the vector of materials defined above size t mateIDs new size t nVoxelX nVoxelY nVoxelZ mateIDs 0 n0 mateIDs 1 n1 param gt SetMaterialIndices mateIDs Then define the volume that contains all the voxels G4Box cont solid new G4Box PhantomContainer nVoxelX halfX nVoxelY halfY nVoxelZ halfZ G4LogicalVolume cont_logic new G4LogicalVolume cont_solid matePatient material is not relevant here PhantomContainer a ee OA G4vPhysicalVolume cont_phys new G4PVPlacement rotm rotation pos translation Come LeS logical
182. alization procedures are controlled by the Visualization Manager a class which must inherit from G4VisManager defined in the visualization category Most users will find that they can just use the default visual ization manager G4VisExecutive The Visualization Manager accepts users requests for visualization processes them and passes the processed requirements to the abstract interface i e to the currently selected visualization driver 8 2 5 How to Write the main Function In order for your Geant4 executable to perform visualization you must instantiate and initialize your Visual ization Manager in the main function The core of the Visualization Manager is the class G4VisManager defined in the visualization category This class requires that one pure virtual function be implemented namely void RegisterGraphicsSystems The easiest way to do this is to use G4VisExecutive as de scribed above but you may write your own class see above Example 8 2 shows the form of the main function Example 8 2 The form of the main function d C source codes Instantiation and initialization of G4VisManager Your Visualization Manager include G4VisExecutive hh Instantiation and initialization of the Visualization Manager ifdef G4VIS_USE G4VisManager visManager new G4VisExecutive visManager gt initialize endif ifdef G4VIS USE delete visManager endif ff end of C
183. ame type as of the one associated to the mother volume As for any replica the coordinate system of the divisions is related to the centre of each division for the carte sian axis For the radial axis the coordinate system is the same of the mother volume For the phi axis the new coordinate system is rotated such that the X axis bisects the angle made by each wedge and Z remains parallel to the mother s Z axis As divisions are parameterised volumes with constant dimensions they may be placed inside other divisions except in the case of divisions along the radial axis It is also possible to place other volumes inside a volume where a division is placed The list of volumes that currently support divisioning and the possible division axis are summarised below G4Box kXAxis kYAxis kZAxis G4Tubs kRho kPhi kZAxis G4Cons kRho kPhi kZAxis G4Trd kXAxis kYAxis kZAxis G4Para kXAxis kYAxis kZAxis G4Polycone kRho kPhi kZAxis G4Polyhedra kRho kPhi kZAxis G4Polycone e kZAxis the number of divisions has to be the same as solid sections i e numZPlanes 1 the width will not be taken into account G4Polyhedra kPhi the number of divisions has to be the same as solid sides i e numSides the width will not be taken into account e kZAxis the number of divisions has to be the same as solid sections i e numZPlanes 1 the width will not be taken
184. ample N05 Basic concepts Use of shower parameterisation definition of an EM shower model assignment to a Logical Volume definition of ghost volume when ready nteractivity build of messengers classes Hits Digi filled from detailed and parameterised simulation calorimeter type hits Classes main source file main for interactive mode construction and deletion of G4RunManager construction and set of mandatory user classes construction of the G4GlobalFastSimulationmanager construction of a G4FastSimulationManager to assign fast simulation model to a logical volume envelope definition of ghost volume for parameterisation construction EM physics shower fast simulation model ExN05EMShowerModel header file source file derived from G4VFastSimulationModel energy deposition in sensitive detector ExN05PionShowerModel header file source file derived from G4VFastSimulationModel energy deposition in sensitive detector ExNO5DetectorConstruction header file source file derived from G4VUserDetectorConstruction definitions of single materials and mixtures e CSG solids 264 Examples G4PVPlacement ExN05PhysicsList header file source file derived from G4VUserPhysicsList assignment of G4FastSimulationManagerProcess ExN05PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction construction of G4ParticleGun
185. anager visManager new G4VisExecutive visManager gt SetVerboseLevel 1 visManager gt Initialize This can also be set with the vis verbose command 210 Visualization 8 3 The Visualization Drivers As explained in the Introduction to Visualization Geant4 provides many different choices of visualization sys tems Features and notes on each driver are briefly described here along with links to detailed web pages for the various drivers Details are given below for Section 8 3 2 OpenGL Section 8 3 3 OpenInventor Section 8 3 4 HepRepFile Section 8 3 5 HepRepXML Section 8 3 6 DAWN Section 8 3 8 VRML Section 8 3 9 RayTracer Section 8 3 10 ASCIITree Section 8 3 11 GAGTree Section 8 3 12 XML Tree 8 3 1 Availability of drivers on the supported systems Table 8 1 lists required graphics systems and supported platforms for the various visualization drivers Driver Required Graphics System Platform OpenGL Xlib OpenGL Linux Unix Mac with Xlib OpenGL Motif OpenGL Linux UNIX Mac with Motif OpenGL Win32 OpenGL Windows OpenInventor X OpenInventor OpenGL Linux UNIX Mac with Xlib or Mo tif OpenInventor Win32 OpenInventor OpenGL Windows HepRep WIRED or FRED HepRep Browser Linux UNIX Mac Windows DAWNFILE Fukui Renderer DAWN Linux Unix Mac Windows DAWN Network Fukui Renderer DAWN Linux UNIX VRMLFILE any VRML viewer Linux UNIX Mac Windows
186. and efficiently retrieve the corresponding value All values in the dictionary are either instantiations of G4double or the class G4MaterialPropertyVector and all keys are of type G4St ring 157 Tracking and Physics A G4MaterialPropertyVector is composed of instantiations of the class G4MPVEntry The G4MPVEnt ry is a pair of numbers which in the case of an optical property are the photon momentum and corresponding property value The G4MaterialPropertyVector is implemented as a G4std vector with the sorting operation defined as MPV Entry lt MPVEntry2 photon momentum lt photon momentum This results in all GGMaterialPropertyVectors being sorted in ascending order of photon momenta It is possible for the user to add as many material optical properties to the material as he wishes using the methods supplied by the G4MaterialPropertiesTable class An example of this is shown in Example 5 5 Example 5 5 Optical properties added to a G4MaterialPropertiesTable and linked to a G4Material const G4int NUMENTRIES 32 G4double ppckov NUMENTRIES 2 034 eV EDS OOV G4double rindex NUMENTRIES 1 3435 p d SoOsy 7 G4double absorption NUMENTRIES 344 8 cm ERIS OO mills G4MaterialPropertiesTable MPT new G4MaterialPropertiesTable MPT AddConstProperty SCINTILLATIONYIELD 100 MeV MPT gt AddProperty RINDEX ppckov rindex NUMENTRIES MPT gt AddProperty ABSLENGT
187. anged A run is represented by a G4Run class object A run starts with BeamOn method of G4RunManager 3 4 1 1 Representation of a run G4Run represents a run It has a run identification number which should be set by the user and the number of events simulated during the run Please note that the run identification number is not used by the Geant4 kernel and thus can be arbitrarily assigned at the user s convenience G4Run has pointers to the tables G4VHitsCollection and G4VDigiCollection These tables are associated in case sensitive detectors and digitizer modules are simulated respectively The usage of these tables will be mentioned in Section 4 4 and Section 4 5 3 4 1 2 Manage the run procedures G4RunManager manages the procedures of a run In the constructor of G4RunManager all of the manager classes in Geant4 kernel except for some static managers are constructed These managers are deleted in the destructor of G4RunManager G4RunManager must be a singleton and the pointer to this singleton object can be obtained by the getRunManager static method 40 Toolkit Fundamentals As already mentioned in Section 2 1 all of the user initialization classes and user action classes defined by the user should be assigned to G4RunManager before starting initialization of the Geant4 kernel The assignments of these user classes are done by Set UserInitialization and SetUserAction methods All user classes defined by the Gea
188. annel number As an example the accordion calorimeter of ATLAS has a complicated tracking geometry however the readout can be done by simple cylindrical sectors divided by theta phi and depth Tracks will be traced in the tracking geometry the real one and the sensitive detector will have its own readout geometry Geant4 will message to find to which readout cell the current hit belongs The Tracking Geometry A Readout Geometry builds by G4VUserDetectorC onstruction builds by a G4VReadoutGeometry G4VSensitiveDetector object W World of RO geometry Figure 4 8 Association of tracking and readout geometry Figure 4 8 shows how this association is done in Geant4 The first step is to associate a sensitive detector to a volume of the tracking geometry in the usual way see Section 4 4 2 The next step is to associate your G4VReadoutGeometry object to the sensitive detector At tracking time the base class G4VReadoutGeometry will provide to your sensitive detector code the G4TouchableHistory in the Readout geometry at the beginning of the step position position of PreStepPoint of G4Step and at this position only This G4TouchableHistory is given to your sensitive detector code through the G4VSensitiveDetector virtual method G4bool processHits G4Step aStep G4TouchableHistory ROhist by the ROhist argument Thus you will be able to use information from both the G4Step and the G4TouchableHistor
189. ansformation that moves the second solid from its desired position to its standard position e g a box s standard position is with its centre at the origin and sides parallel to the three axes This is called the active method In the first case the translation is applied first to move the origin of coordinates Then the rotation is used to rotate the coordinate system of the second solid to the coordinate system of the first G4RotationMatrix yRot new G4RotationMatrix Rotates X and Z axes only yRot rotateY M PI 4 rad Rotates 45 degrees G4ThreeVector zTrans 0 0 50 G4UnionSolid unionMoved new G4UnionSolid Box CylinderMoved box cyl yRot zTrans The new coordinate system of the cylinder is translated so that its centre is at 50 on the original Z axis and it is rotated with its X axis halfway between the original X and Z axes Now we build the same solid using the alternative method G4RotationMatrix invRot yRot gt invert G4Transform3D transform invRot zTrans G4UnionSolid unionMoved 72 Detector Definition and Response new G4UnionSolid Box CylinderMoved box cyl transform Note that the first constructor that takes a pointer to the rotation matrix G4RotationMatrix does NOT copy it Therefore once used a rotation matrix to construct a Boolean solid it must NOT be modified In contrast with the alternative method shown a G4Transform3D is provided to t
190. antiated engine the old engine status is kept and the new random sequence will start exactly from the last one previously interrupted For example HepRandom setTheEngine amp myOldEngine Other static methods defined in this class are e void setTheSeeds const G4long seeds G4int const G4long getTheSeeds To set get an array of seeds for the generator in the case of a RanecuEngine this corresponds also to set get the current status of the engine HepRandomEngine getTheEngine To get a pointer to the current engine used by the static generator 3 2 2 3 HEPRandom distributions A distribution class can collect different algorithms and different calling sequences for each method to define distribution parameters or range intervals it also collects methods to fill arrays of specified size of random values according to the distribution This class collects either static and not static methods A set of distribution classes are defined in HEPRandom Here is the description of some of them RandFlat Class to shoot flat random values integers or double within a specified interval The class provides also meth ods to shoot just random bits RandExponential Class to shoot exponential distributed random values given a mean default mean 1 RandGauss Class to shoot Gaussian distributed random values given a mean default 0 or specifying also a deviation default 1 Gaussian random numbers ar
191. are used to store the final state information of the track including sec ondary tracks which has been generated by the DoIt methods The instance of G4VParticleChange is the only object whose information is updated by the physics processes hence it is responsible for updating the step The stepping manager collects secondary tracks and only sends requests via particle change to update G4Step G4VParticleChange is introduced as an abstract class It has a minimal set of methods for updating G4Step and handling secondaries A physics process can therefore define its own particle change derived from G4VParticleChange Three pure virtual methods are provided virtual G4Step UpdateStepForAtRest G4Step step virtual G4Step UpdateStepForAlongStep G4Step step and virtual G4Step UpdateStepForPostStep G4Step step which correspond to the three DoIt methods of G4VProcess Each derived class should implement these methods 5 2 1 Electromagnetic Interactions This section summarizes the electromagnetic physics processes which are installed in Geant4 For details on the implementation of these processes please refer to the Physics Reference Manual 5 2 1 1 Standard Electromagnetic Processes The following is a summary of the standard electromagnetic processes available in Geant4 Photon processes Compton scattering class name G4ComptonScattering Gamma conversion also called pair production class name G4GammaConversion
192. as no operator new or operator delete 5 2 Physics Processes Physics processes describe how particles interact with a material Seven major categories of processes are provided by Geant4 1 electromagnetic 2 hadronic 3 decay 4 photolepton hadron 5 optical 6 parameterization and 7 transportation The generalization and abstraction of physics processes is a key issue in the design of Geant4 All physics pro cesses are treated in the same manner from the tracking point of view The Geant4 approach enables anyone to create a process and assign it to a particle type This openness should allow the creation of processes for novel domain specific or customised purposes by individuals or groups of users Each process has two groups of methods which play an important role in tracking Get PhysicalInterac tionLength GPIL and DoIt The GPIL method gives the step length from the current space time point to the next space time point It does this by calculating the probability of interaction based on the process s cross section information At the end of this step the DoIt method should be invoked The DoIt method implements the details of the interaction changing the particle s energy momentum direction and position and producing secondary tracks if required These changes are recorded as G4VParticleChange objects see Particle Change G4VProcess G4VProcess is the base class for all physics processes Each physics proc
193. ase of containment Geant4 uses the concept of Logical Volume to manage the representation of detector element properties The concept of Physical Volume is used to manage the representation of the spatial positioning of detector elements and their logical relations The concept of Solid is used to manage the representation of the detector element solid modeling Volumes and solids must be dynamically allocated in the user program objects allocated are automatically registered in dedicated stores which also take care to free the memory at the end of a job The Geant4 solid modeler is STEP compliant STEP is the ISO standard defining the protocol for exchanging geometrical data between CAD systems This is achieved by standardizing the representation of solid models via the EXPRESS object definition language which is part of the STEP ISO standard 4 1 2 Solids The STEP standard supports multiple solid representations Constructive Solid Geometry CSG representations and Boundary Represented Solids BREPs are available Different representations are suitable for different pur poses applications required complexity and levels of detail CSG representations are easy to use and normally give superior performance but they cannot reproduce complex solids such as those used in CAD systems BREP representations can handle more extended topologies and reproduce the most complex solids All constructed solids can stream out their contents via ap
194. ash equations An example provided in examples extended parametrisation gflash shows how to interface Gflash to your application The simulation time is measured so the user can immediately see the speed increase resulting from the use of Gflash 5 2 6 9 Using the Gflash Parameterisation To use Gflash out of the box the following steps are necessary The user must add the fast simulation process to his process manager void MyPhysicsList addParameterisation G4FastSimulationManagerProcess theFastSimulationManagerProcess new G4FastSimulationManagerProcess theParticlelterator gt reset while theParticleIterator G4ParticleDefinition particle theParticleIterator value G4ProcessManager pmanager particle GetProcessManager pmanager gt AddProcess theFastSimulationManagerProcess 1 0 0 The envelope in which the parameterization should be performed must be specified below G4Region m_calo_region and the GFlashShowerModel must be assigned to this region Furthermore the class es GFlashParticleBounds which provides thresholds for the parameterization like minimal energy etc GflashHitMaker a helper class to generate hits in the sensitive detector and GFlashHomoShowerParamteri sation which does the computations must be constructed by the user at the moment and assigned to the GFlashShowerModel Please note that at the moment only homogeneous calorimeters are supported m_theFast
195. atabase which were derived from the NIST database of mate rial properties Additionally a number of materials friquently used in HEP is included in the database Materials are interrogated or constructed by their names Section 8 There are UI commands for the material category which provide an interactive access to the database If material is created using the NIST database by it will consist by default of elements with the natural composition of isotopes 4 2 2 4 Final Considerations The classes will automatically decide if the total of the mass fractions is correct and perform the necessary checks The main reason why a fixed index is kept as a data member is that many cross section and energy tables will be built in the physics processes by rows of materials or elements or even isotopes The tracking gives the physics process the address of a material object the material of the current volume If the material has an index according to which the cross section table has been built then direct access is available when a number in such a 107 Detector Definition and Response table must be accessed We get directly to the correct row and the energy of the particle will tell us the column Without such an index every access to the cross section or energy tables would imply a search to get to the correct material s row More details will be given in the section on processes Isotopes elements and materials must be instantiated d
196. ath h package For detailed documentation on the HEPRandom classes see the CLHEP reference guide and the CLHEP user manual Information written in this manual is extracted from the original manifesto distributed with the HEPRandom package The HEPRandom module consists of classes implementing different random engines and different random distributions A distribution associated to an engine constitutes a random generator A distribution class can collect different algorithms and different calling sequences for each method to define distribution parameters or range intervals An engine implements the basic algorithm for pseudo random numbers generation There are 3 different ways of shooting random values 1 Using the static generator defined in the HepRandom class random values are shot using static methods shoot defined for each distribution class The static generator will use as default engine a HepJamesRan dom object and the user can set its properties or change it with a new instantiated engine object by using the static methods defined in the HepRandom class 33 Toolkit Fundamentals 2 Skipping the static generator and specifying an engine object random values are shot using static methods shoot HepRandomEngine defined for each distribution class The user must instantiate an engine ob ject and give it as argument to the shoot method The generator mechanism will then be by passed by using the basic
197. ats including PostScript and PDF 8 4 14 Culling Culling means to skip visualizing parts of a 3D scene Culling is useful for avoiding complexity of visualized views keeping transparent features of the 3D scene and for quick visualization Geant4 Visualization supports the following 3 kinds of culling Culling of invisible physical volumes Culling of low density physical volumes Culling of covered physical volumes by others In order that one or all types of the above culling are on i e activated the global culling flag should also be on Table 8 2 summarizes the default culling policies 228 Visualization Culling Type Default Value global ON invisible ON low density OFF covered daughter OFF Table 8 2 The default culling policies The default threshold density of the low density culling is 0 01 g cm The default culling policies can be modified with the following visualization commands Below the argument flag takes a value of true or false global vis viewer set culling global flag invisible vis viewer set culling invisible flag low density value is a proper value of a treshold density unit is either g cm3 mg cm3 or kg m3 vis viewer set culling density flag value unit covered daughter vis viewer set culling coveredDaughters flag density The HepRepFile graphic system will by default include culled objects in the file so that they can still
198. ave the global cut that we wanted but with energy conservation and we respect boundary constraint safety and the wishes of the processes via good for tracking 5 4 4 Why produce secondaries below threshold A process may have good reasons to produce particles below the recommended threshold checking the range of the secondary versus geometrical quantities like safety may allow one to realize the possibility that the produced particle even below threshold will reach a sensitive part of the detector another example is the gamma conversion the positron is always produced even at zero energy for further annihilation These secondary particles are sent to the Stepping Manager with a flag GoodForTracking to pass the filter explained in the previous section even when ApplyCut is ON 175 Tracking and Physics 5 4 5 Cuts in stopping range or in energy The cuts in stopping range allow one to say that the energy has been released at the correct space position lim iting the approximation within a given distance On the contrary cuts in energy imply accuracies of the energy depositions which depend on the material 5 4 6 Summary In summary we do not have tracking cuts we only have production thresholds in range All particles produced and accepted are tracked up to zero range It must be clear that the overall coherency that we provide cannot go beyond the capability of processes to produce particles dow
199. ay_charging illustrating an application aimed at simulating the electrostatic charging of isolated test masses in the LISA mission by galactic cosmic ray protons and helium nuclei composite calorimeter test beam simulation of the CMS Hadron calorimeter at LHC lAr calorimeter simulating the Forward Liquid Argon Calorimeter FCAL of the ATLAS Detector at LHC raredecay_calorimetry illustrating how to estimate importance of photonuclear reactions for photon ineffi ciency of calorimeters and compare effectiveness of different absorbers in order to reduce it e Rich simulating the TestBeam Setup of the Rich detector at the LHCb experiment testing the performance of the aerogel radiator Tiara a simulation of the neutron shielding experiment TIARA providing a realistic example for applying geometrical importance sampling Further documentation about the analysis tools used in these examples is available at AIDA Abstract Interfaces for Data Analysis and AIDA PI JAS and OpenScientist 271 Chapter FAQ Frequentry Asked Questions FAQ 1 Installation Q When I download the source from the web and unpack the tar file some files unpack into the top level directory The problem you describe usually is the result of using UNIX tar to unpack the gtar GNU tar file or vice versa or using zip on either the gtar or tar file Please make certain that you download the correct file for your system and that you use th
200. bda that is lambda 90 theta where theta is the usual angle with respect to the Z axis fYperp and fZperp are the coordinates of the trajectory in a local orthonormal reference frame with the X axis along the particle direction the Y axis being parallel to the X Y plane obtained by the vectorial product of the global Z axis and the momentum 5 8 2 2 Trajectory state on a surface In the trajectory state on a surface representation the five trajectory parameters are G4double fInvP G4double fPV G4double fPW G4double fV G4double fW where InvP is the inverse of the momentum PV and PW are the momentum components in an orthonormal coordinate system with axis U V and W V and fW are the position components on this coordinate system For this representation the user has to provide the plane where the parameters are calculated This can be done by providing two vectors V and W contained in the plane 181 Tracking and Physics G4ErrorSurfaceTrajState const G4String amp partType const G4Point3D amp pos const G4Vector3D amp mom const G4Vector3D amp vecV const G4Vector3D amp vecW const G4ErrorTrajErr amp errmat G4ErrorTrajErr 5 0 or by providing a plane G4ErrorSurfaceTrajState const G4String amp partType const G4Point3D6 pos const G4Vector3D amp mom const G4Plane3D amp plane const G4ErrorTrajErr amp errmat G4ErrorTrajErr 5 0 In this second case the vector V is calculat
201. bers TestEm11 how to plot a depth dose profile in a rectangular box TestEm12 how to plot a depth dose profile in spherical geometry point like source TestEm13 how to compute cross sections of EM processes from rate of transmission coefficient TestEm14 how to compute cross sections of EM processes from direct evaluation of the mean free path How to plot final state TestEm15 compute and plot final state of Multiple Scattering as an isolated process TestEm16 simulation of synchrotron radiation TestEm17 check the cross sections of high energy muon processes TestEm18 energy lost by a charged particle in a single layer due to ionization and bremsstrahlung Check basic quantities Total cross sections mean free paths Em0 Em13 Em14 Stopping power particle range Em0 Em1 Em5 Em11 Em12 Final state energy spectra angular distributions Em14 Energy loss fluctuations Em18 Multiple Coulomb scattering as an isolated mechanism Em15 as a result of particle transport Em5 More global verifications Single layer transmission absorption reflexion Em5 Bragg curve tallies Em7 Depth dose distribution Em11 Em12 Shower shapes Moliere radius Em2 Sampling calorimeters energy flow Em3 Crystal calorimeters Em9 Other specialized programs High energy muon physics Em17 Other rare high energy processes Em6 Synchrotron radiation Em16 Transiti
202. bject can have one or more G4PrimaryParticle class objects which share the same vertex As shown in Fig primary vertexes and primary particles are associated with the G4 Event object by a form of linked list A concrete class of G4VPrimaryGenerator the G4PrimaryParticle object is constructed with either a pointer to G4ParticleDefinition or an integer number which represents P D G particle code For the case of some arti ficial particles e g geantino optical photon etc or exotic nuclear fragments which the P D G particle code does not cover the G4PrimaryParticle should be constructed by G4ParticleDefinition pointer On the other hand elementary particles with very short life time e g weak bosons or quarks gluons can be instantiated as G4PrimaryParticle objects using the P D G particle code It should be noted that even though primary parti cles with such a very short life time are defined Geant4 will simulate only the particles which are defined as G4ParticleDefinition class objects Other primary particles will be simply ignored by G4EventManager But it may still be useful to construct such intermediate particles for recording the origin of the primary event 3 6 1 2 Forced decay channel The G4PrimaryParticle class object can have a list of its daughter particles If the parent particle is an interme diate particle which Geant4 does not have a corresponding G4ParticleDefinition this parent particle is ignored and daugh
203. ble Section 8 3 The Visualization Drivers Section 8 4 Controlling Visualization from Commands Section 8 5 Controlling Visualization from Compiled Code Section 8 6 Visualization Attributes Section 8 7 Enhanced Trajectory Drawing Section 8 9 Polylines Markers and Text Other useful references for Geant4 visualization outside of this user guide Introduction to Geant4 Visualization pdf ppt Status of Geant4 Visualization giving current status and a summary of what has been improved over the last few releases pdf ppt Macro files distributed in Geant4 source in examples novice N03 visTutor 8 2 Adding Visualization to Your Executable This section explains how to incorporate your selected visualization drivers into the main function and create an executable for it In order to perform visualization with your Geant4 executable you must compile it with realized visualization driver s You may be dazzled by the number of choices of visualization driver but you need not use all of them at one time 8 2 1 Installing Visualization Drivers Depending on what has been installed on your system several kinds of visualization driver are available One or many drivers may be chosen for realization in compilation depending on your visualization requirements Features 206 Visualization and notes on each driver are briefly described in Section 8 3 Visualization Drivers along with links to detailed web pages for the
204. blyVolume class It implements a layered detector where each layer consists of 4 plates In the code below at first the world volume is defined then solid and logical volume for the plate are created followed by the definition of the assembly volume for the layer The assembly volume for the layer is then filled by the plates in the same way as normal physical volumes are placed inside a mother volume Finally the layers are placed inside the world volume as the imprints of the assembly volume see Example 4 7 89 Detector Definition and Response Example 4 7 An example of usage of the G4AssemblyVolume class static unsigned int layers 5 void TstVADetectorConstruction ConstructAssembly Define world volume G4Box WorldBox new G4Box WBox worldX 2 worldY 2 worldZ 2 G4LogicalVolume worldLV new G4LogicalVolume WorldBox selectedMaterial WLog 0 0 0 G4VPhysicalVolume worldVol new G4PVPlacement 0 G4ThreeVector WPhys worldLV OQ farse Upg Define a plate G4Box PlateBox new G4Box PlateBox plateX 2 plateY 2 plateZ 2 G4LogicalVolume plateLV new G4LogicalVolume PlateBox Pb PlateLV 0 0 0 Define one layer as one assembly volume G4AssemblyVolume assemblyDetector new G4AssemblyVolume Rotation and translation of a plate inside the assembly G4RotationMatrix Ra G4ThreeVector Ta Rotation of the assembly inside the world G4RotationMatrix Rm
205. c limit smaller than the production threshold for instance 0 The list of secondaries is sent to the SteppingManager via a ParticleChange object Before being recopied to the temporary stack for later tracking the particles below the production threshold will be kept or deleted according to the safe mechanism explained hereafter The ParticleDefinition or ParticleWithCuts has a boolean data member ApplyCut ApplyCut is OFF do nothing All the secondaries are stacked and then tracked later on regardless of their initial energy The Geant4 kernel respects the best that the physics can do but neglects the overall coherence and the efficiency Energy conservation is respected as far as the processes know how to handle correctly the particles they produced ApplyCut in ON the TrackingManager checks the range of each secondary against the production threshold and against the safety The particle is stacked if range min cut safety Ifnot check if the process has nevertheless set the flag good for tracking and then stack it see Section 5 4 4 below for the explanation of the GoodForTracking flag If not recuperate its kinetic energy in the localEnergyDeposit and set t kin 0 Then check in the ProcessManager if the vector of ProcessAtRest is not empty If yes stack the particle for performing the Action At Rest later If not and only in this case abandon this secondary With this sophisticated mechanism we h
206. c moment does not participate and the need thus arises to propagate it independent of the momentum vector In the case of a polarized muon beam for example it is important to predict the muon s spin direction at decay time in order to simulate the decay electron Michel distribution correctly In order to track the spin of a particle in a magnetic field you need to code the following 1 in your DetectorConstruction include G4Mag SpinEqRhs hh G4Mag EqRhs fEguation new G4Mag SpinEgRhs magField G4MagIntegratorStepper pStepper new G4ClassicalRK4 fEquation 12 notice the 12 2 in your PrimaryGenerator 116 Detector Definition and Response particleGun gt SetParticlePolarization G4ThreeVector p for example particleGun gt SetParticlePolarization particleGun gt GetParticleMomentumDirection Ab xe particleGun gt SetParticlePolarization particleGun gt GetParticleMomentumDirection cross G4ThreeVector 0 1 0 where you set the initial spin direction While the G4Mag SpinEgRhs class constructor G4Mag SpinEqRhs G4Mag SpinEgRhs G4MagneticField MagField G4Mag EgRhs MagField anomaly 1 165923e 3 sets the muon anomaly by default the class also comes with the public method inline void SetAnomaly G4double a anomaly a with which you can set the magnetic anomaly to any value you require For the moment the code is written such that field tracking of
207. cally set if G4LIB_BUILD_GDML is set in the environment G4LIB_BUILD_ZLIB If set triggers compilation of a specific z1ib module for the compression of output files mainly in use currently for the HepRep graphics driver By default the flag is not set and the built in system library for compression is adopted instead Setting this flag will also implicitely set the flag below G4LIB_USE_ZLIB Specifies to use the z1ib module either system built in or Geant4 specific G4LIB_BUILD_G3TOG4 If set triggers compilation of the g3t og4 module for conversions of simple legacy geometries descriptions to Geant4 By default the flag is not set and the module s library is not built Setting this flag will also implicitely set the flag below G4LIB USE G3TOG4 Specifies to use the g3tog4 module assuming the related library has been already installed Analysis specific G4ANALYSIS USE Specifies to activate the appropriate environment for analysis if an application includes code for histogram ming based on A DA Additional setup variables are reguired G4ANALYSIS AIDA CONFIG CFLAGS G4ANALYSIS AIDA CONFIG LIBS to define config options for AIDA aida config cflags and aida config libs See installation instructions of the specific analysis tools for details Directory paths to Physics Data G4NEUTRONHPDATA Path to external data set for Neutron Scattering processes G4LEDATA Path to external data set for low energy electroma
208. cess process process process particleName anager AddDiscre anager AddDiscre anager AddDiscre anager AddDiscre anager AddDiscre wlsweenc JJ if teProcess new teProcess new ExcitationMillerGreen teProcess new ExcitationBorn IonisationRudd IonisationBorn ChargeDecrease teProcess new teProcess new a a a d 7 else if process process particleName anager gt AddDiscre anager gt AddDiscre hydrogen teProcess new IonisationRudd teProcess new Chargelncrease else if process process process particleName anager gt AddDiscre anager gt AddDiscre anager gt AddDiscre TALONS 3 ca teProcess new teProcess new teProcess new ExcitationMillerGreen IonisationRudd ChargeDecrease else if process process process process particleName anager gt AddDiscre anager gt AddDiscre anager gt AddDiscre anager gt AddDiscre Uadiphad Ua i teProcess new teProcess new teProcess new teProcess new ExcitationMillerGreen IonisationRudd ChargeDecrease ChargeIncrease Wem meyer teProcess new teProcess new teProcess new else if process process process particleName anager gt AddDiscre anager gt AddDiscre anager gt AddDiscre ExcitationMillerGreen IonisationRudd ChargeIncrease 149 tionExcitationEmfietzoglou G4FinalStateExcitationEmfietzog
209. charged amp amp trj GetCharge 0 trj gt DrawTrajectory 50 else if drawFlag neutral amp amp trj GetCharge 0 trj gt DrawTrajectory 50 end of C source codes 8 5 4 Enhanced trajectory drawing It is possible to use the enhanced trajectory drawing functionality in compiled code as well as from commands Multiple trajectory models can be instantiated configured and registered with G4VisManager For details see the section on Section 8 7 4 Enhanced Trajectory Drawing 8 5 5 HepRep Attributes for Trajectories The HepRep file formats HepRepFile and HepRepXML attach various attributes to trajectories such that you can view these attributes label trajectories by these attributes or make visibility cuts based on these attributes If you use the default Geant4 trajectory class from tracking src G4Trajectory cc available attributes will be Track ID Parent ID Particle Name Charge PDG Encoding Momentum 3 Vector Momentum magnitude 232 Visualization Number of points You can add additional attributes of your choosing by modifying the relevant part of G4Trajectory look for the methods GetAttDefs and CreateAttValues If you are using your own trajectory class you may want to consider copying these methods from G4Trajectory 8 5 6 Visualization of hits Hits are visualized with classes G4Square or G4Circle or other user defined classes inheriting the abstra
210. cker type hit generation ExNO 2TrackerHit header file source file 260 Examples derived from G4VHit draw hit point 9 1 4 Example N03 Basic concepts Visualize Em processes nteractivity build messenger classes Gun shoot particle randomly Tracking collect energy deposition total track length Classes main source file main for interactive mode and batch mode via macro file construction and deletion of G4RunManager construction and deletion of G UI session and VisManager construction and set of mandatory user classes automatic initialization of geometry and visualization via a macro file ExNO3DetectorConstruction header file source file derived from G4VUserDetectorConstruction definitions of single materials and mixtures e CSG solids G4PVPlacement without rotation Interactivity change detector size material magnetic field gt messenger class visualization ExN03PhysicsList header file source file derived from G4VUserPhysicsList definition of geantinos gamma leptons light mesons barions and ions Transportation process standard Em processes Decay Interactivity SetCut process on off gt messenger class ExNO3PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction construction of G4ParticleGun primary event generation via particle gun Interactivity shoot particle randomly
211. cl i 1 candidateList particleTable GetParticleName i candidateList particleCmd gt SetCandidates candidateList Tere lay NP 7 2 4 How to control the output of G4cout G4cerr Instead of cout and cerr Geant4 uses G4cout and G4cerr Output streams from G4cout G4cerr are handled by G4UImanager which allows the application programmer to control the flow of the stream Output strings may therefore be displayed on another window or stored in a file This is accomplished as follows 1 Derive a class from G4UIsession and implement the two methods G4int ReceiveG4cout G4String coutString G4int ReceiveG4cerr G4String cerrString 202 Communication and Control These methods receive the string stream of G4cout and G4cerr respectively The string can be handled to meet specific requirements The following sample code shows how to make a log file of the output stream ostream logFile logFile open MyLogFile G4int MySession ReceiveG4cout G4String coutString i logFile lt lt coutString lt lt flush teturn Q 2 Set the destination of G4cout G4cerr using G4UImanager SetCoutDestination session Typically this method is invoked from the constructor of G4UIsession and its derived classes such as G4UIGAG G4Ulteminal This method sets the destination of G4cout G4cerr to the session For example when the following code appears in the constructor of G4Ulterminal the metho
212. cleGunMessenger which is made by inheriting G4Ulcommand 199 Communication and Control Example 7 1 An example of G4ParticleGunMessenger hh ifndef G4ParticleGunMessenger_h define G4ParticleGunMessenger_h 1 lass G4ParticleGun lass G4ParticleTable lass G4UIcommand lass G4UIdirectory lass G4UIcmdWithoutParameter lass G4UIcmdWithAString lass G4UIcmdWithADoubleAndUnit lass G4UIcmdWith3Vector lass G4UIcmdWith3VectorAndUnit ONGNECNONCNECEOEGNG include G4UImessenger hh include globals hh class G4ParticleGunMessenger public G4UImessenger Bu bitie G4ParticleGunMessenger G4ParticleGun fPtclGun G4ParticleGunMessenger PUDILGI void SetNewValue G4UIcommand command G4String newValues G4String GetCurrentValue G4UIcommand command private G4ParticleGun fParticleGun G4ParticleTable particleTable private commands G4UIdirectory gunDirectory G4UIcmdWithoutParameter JLsk ese Ciao tp G4UIcmdWithAString particleCmg G4UIcmdWith3Vector directionCmd G4UIcmdWithADoubleAndUnit energyCmd G4UIcmdWith3VectorAndUnit positionCmd G4UIcmdWithADoubleAndUnit timeCmd hi endif 200 Communication and Control Example 7 2 An example of G4ParticleGunMessenger cc include G4ParticleGunMessenger hh include G4ParticleGun hh include G4Geantino hh include G4ThreeVector hh include G4ParticleTable hh include G4UIdirectory
213. clude globals hh include G4VisExecutive hh include G4VisExtent hh include G4UImanager hh include G4UIterminal hh include G4UItcsh hh include StandaloneVisAction hh sized marni G4VisManager visManager new G4VisExecutive visManager gt Initialize visManager gt SetUserAction new StandaloneVisAction G4VisExtent 5 m 5 m 5 m 5 m 5 m 5 m 2nd argument optional G4UImanager UI G4UImanager GetUIpointer UI gt ApplyCommand control execute standalone g4m G4UIsession session new G4UIterminal new G4UItcsh session gt SessionStart delete session delete visManager 8 6 Visualization Attributes Visualization attributes are extra pieces of information associated with the visualizable objects This information is necessary only for visualization and is not included in geometrical information such as shapes position and orientation Typical examples of visualization attributes are Color Visible Invisible Wireframe Solid For exam ple in visualizing a box the Visualization Manager must know its colour If an object to be visualized has not been assigned a set of visualization attributes then an appropriate default set is used automatically A set of visualization attributes is held by an instance of class G4VisAttributes defined in the graphics_reps category In the following we explain the main fields of the G4VisAttributes one by one 8 6 1 Visibility Visibility
214. constant represents the reflection probability about the normal of a micro facet The specular spike constant in turn illustrates the probability of reflection about the average surface normal The diffuse lobe constant is for the probability of internal Lambertian reflection and finally the back scatter spike constant is for the case of several reflections within a deep groove with the ultimate result of exact back scattering The four probabilities must add up to one with the diffuse lobe constant being implicit The reader may consult the reference for a thorough description of the model Example 5 10 Dielectric dielectric surface properties defined via the G4OpticalSurface G4VPhysicalVolume volumel G4VPhysicalVolume volume2 G4OpticalSurface OpSurface new G4OpticalSurface name G4LogicalBorderSurface Surface new G4LogicalBorderSurface name volumel volume2 OpSurface G4double sigma_alpha 0 1 OpSurface gt SetType dielectric_dielectric OpSurface gt SetModel unified OpSurface gt SetFinish groundbackpainted OpSurface gt SetSigmaAlpha sigma alpha const G4int NUM 2 G4double pp NUM 2 038 eV 4 144 eV G4double specularlobe NUM 0 3 0 3 G4double specularspike NUM 0 2 0 2 G4double backscatter NUM 0 1 0 1 G4double rindex NUM 1 35 1 40 G4double reflectivity NUM 0 3 0 5 G4double efficiency NUM 0 8 0 1 G4MaterialPropertiesTable SMP
215. contain multiple HepRep events geometries If the file contains more than one HepRep it is not strictly XML anymore Files can be written in heprep zip heprep gz or heprep format and their binary versions bheprep zip bheprep gz or bheprep The heprep zip is the default for file output the heprep is the default for stdout and stderr Optional To set the filename with a particular extension such as heprep zip heprep gz heprep bheprep zip bheprep gz or bheprep use for instance vis scene create filename bheprep zip Optional To create separate files for each event you can set a suffix such as 0001 to start writing files from filename 0001 bheprep zip to filename 9999 bheprep zip or up while 55 sub will start write files filename 55 sub bheprep zip to filename 99 sub bheprep zip or up vis heprep setEventNumberSuffix 0001 Note suffix has to contain at least one digit Optional To route the HepRep XML output to stdout or stderr by default uncompressed use vis scene create stdout Optional To add attributes to each point on a trajectory use vis heprep addPointAttributes 1 Be aware that this may increase the size of the output dramatically Optional You may use the commands vis viewer zoom to set an initial zoom factor vis viewer set viewpointThetaPhi to set an initial view point vis heprep setCoordinateSystem uvw to change the coordinate system where uvw Gavai dore epa US Grad
216. control alias timeRange 1 control loop movie loop timeRange 40 0 1 where fade gives a vapour trail effect displayHeadTime displays the time of the leading edge as 2D text and movie loop is a macro file vis ogl set startTime startTime ns timeRange ns From there it s straightforward to Section 8 10 make a movie 8 8 Trajectory Filtering Trajectory filtering allows you to visualise a subset of available trajectories This can be useful if you only want to view interesting trajectories and discard uninteresting ones Trajectory filtering can be run in two modes Soft filtering In this mode uninteresting trajectories are marked invisible Hence they are still written but depending on the driver will not be displayed Some drivers for example the HepRepFile driver will allow you to selectively view these soft filtered trajectories Hard filtering In this mode uninteresting trajectories are not drawn at all This mode is especially useful if the job produces huge graphics files dominated by data from uninteresting trajectories Trajectory filter models are used to apply filtering according to specific criteria The following models are currently supplied with the Geant4 distribution e G4TrajectoryChargeFilter chargeFilter G4TrajectoryParticleFilter particleFilter G4TrajectoryOriginVolumeFilter originVolumeFilter e G4TrajectoryAttributeFilter attributeFilter Multiple filters are automatically chained
217. ct base class G4VMarker Drawing methods for hits are not supported by default Instead ways of their implementa tion are guided by virtual methods G4VHit Draw and G4VHitsCollection DrawAllHits of the abstract base classes G4VHit and G4VHitsCollection These methods are defined as empty functions in the digits hits category You can overload these methods using the following drawing methods of class G4VVisManager in order to visualize hits p Drawing methods of G4Square and G4Circle virtual void G4VVisManager Draw const G4Circle amp virtual void G4VVisManager Draw const G4Sguare The real implementations of these Draw methods are described in class G4VisManager The overloaded implementation of G4VHits Draw will be held by for example class MyTrackerHits in heriting G4VHit as follows C source codes An example of giving concrete implementation of G4VHit Draw using class MyTrackerHit public G4VHit void MyTrackerHit Draw G4VVisManager pVVisManager G4VVisManager GetConcreteInstance if pVVisManager define a circle in a 3D space G4Circle circle pos circle SetScreenSize 0 3 circle SetFillStyle G4Circle filled make the circle red EAC ikouie ieoilkeuue h 70s Cie m G4VisAttributes attribs colour circle SetVisAttributes attribs make a 3D data for visualization pVVisManager Draw circle end of C source codes The o
218. ct made of line segments using class G4Polyline and its drawing method defined in class G4VVisManager See for example the implementation of the vis scene add axes command 8 5 10 Visualization User Action You can implement the Draw method of G4VUserVisAction e g the class definition could be class StandaloneVisAction public G4VUserVisAction void Draw hi and the implementation void StandaloneVisAction Draw G4VVisManager pVisManager G4VVisManager GetConcreteInstance if pVisManager Simple box pVisManager gt Draw G4Box box 2 m 2 m 2 m G4VisAttributes G4Colour 1 1 0 Boolean solid G4Box DOXA boxA 3 m 3 m 3 m G4Box boxB boxB 1 m 1 m 1 m G4SubtractionSolid subtracted subtracted_boxes amp boxA amp boxB G4Translate3D 3 m 3 m 3 m pVisManager gt Draw subtracted G4VisAttributes G4Colour 0 1 1 G4Translate3D 6 m 6 m 6 m Explicit use of polyhedron objects is equivalent e g Same but explicit polyhedron G4Polyhedron pA G4Box boxA 3 m 3 m 3 m CreatePolyhedron G4Polyhedron pB G4Box boxB 1 m 1 m 1 m CreatePolyhedron pB gt Transform G4Translate3D 3 m 3 m 3 m G4Polyhedron pSubtracted new G4Polyhedron pA gt subtract pB G4VisAttributes subVisAtts G4Colour 0 1 1 pSubtracted gt SetVisAttributes amp subVisAtts pVisManager gt Draw pSubtracted G4Translate3D 6 m 6 m 6 m
219. ction G4UserEventAction G4UserStackingAction e G4UserTrackingAction G4UserSteppingAction There are several virtual methods in each of these classes which allow the specification of additional procedures at alllevels of the simulation application Details of the user initialization and action classes are provided in Chapter 6 2 1 4 G4U manager and UI CommandSubmission Geant4 provides a category named intercoms G4UImanager is the manager class of this category Using the functionalities of this category you can invoke set methods of class objects of which you do not know the pointer In Example 2 2 the verbosities of various Geant4 manager classes are set Detailed mechanism description and usage of intercoms will be given in the next chapter with a list of available commands Command submission can be done all through the application Getting Started with Geant4 Running a Simple Example Example 2 2 An example of main using interactive terminal and visualization Code modified from the previous example are shown in blue include G4RunManager hh include G4UImanager hh include G4UIterminal hh include G4VisExecutive hh include N02DetectorConstruction hh include NO2PhysicsList hh include N02PrimaryGeneratorAction hh include NO2RunAction hh include N02EventAction hh include N02SteppingAction hh include g4templates hh Tigle Ties pans eneo e celsus eei construct the
220. ction with a volume boundary and the accuracy of the integration of other steps As such they play an important role for tracking The delta intersection parameter is the accuracy to which an intersection with a volume boundary is calculated If a candidate boundary intersection is estimated to have a precision better than this it is accepted This parameter is especially important because it is used to limit a bias that our algorithm for boundary crossing in a field exhibits This algorithm calculates the intersection with a volume boundary using a chord between two points on the curved particle trajectory As such the intersection point is always on the inside of the curve By setting a value for this parameter that is much smaller than some acceptable error the user can limit the effect of this bias on for example the future estimation of the reconstructed particle momentum 111 Detector Definition and Response Figure 4 7 The distance between the calculated chord intersection point C and a computed curve point D is used to determine whether C is an accurate representation of the intersection of the curved path ADB with a volume boundary Here CD is likely too large and a new intersection on the chord AD will be calculated The delta one step parameter is the accuracy for the endpoint of ordinary integration steps those which do not intersect a volume boundary This parameter is a limit on the estimated error of the endp
221. ctive processes are invoked What is a Track G4Track keeps information on the final status of the particle after the completion of one step This means that G4Track has information on the previous step while the AlongStepDoLts are being invoked for the step in progress Only after finishing all AlongStepDoIts will G4Track have the final information e g the final position for the step in progress Also G4Track will be updated after each invocation of a Post StepDoIt 5 1 2 Access to Track and Step Information How to Get Track Information Track information may be accessed by invoking various Get methods provided in the G4Track class For details see the Software Reference Manual Typical information available includes Quy Global time time since the event was created Local time time since the track was created Proper time time in its rest frame since the track was created Momentum direction unit vector Kinetic energy Accumulated geometrical track length Accumulated true track length Pointer to dynamic particle Pointer to physical volume Track ID number Track ID number of the parent Current step number Track status e x y z at the start point vertex position of the track Momentum direction at the start point vertex position of the track Kinetic energy at the start point vertex position of the track Pinter to the process which created the current track How to Get S
222. ctories testChargeModel setRGBA 1 0 5 0 5 0 5 1 vis modeling trajectories testChargeModel setRGBA 0 11 0 1 Create a drawByParticleID model named drawByParticleID 0 vis modeling trajectories create drawByParticleID Configure drawByParticleID 0 model 245 Visualization vis modeling trajectories drawByParticleID 0 set gamma red vis modeling trajectories drawByParticleID 0 setRGBA e 1 0 1 1 List available models vis modeling trajectories list select drawByParticleID 0 to be current vis modeling trajectories select drawByParticleID 0 Create a drawByAttribute model named drawByAttribute 0 vis modeling trajectories create drawByAttribute Configure drawBy Attribute 0 model vis modeling trajectories drawByAttribute 0 verbose true Select attribute CPN vis modeling trajectories drawByAttribute 0 setAttribute CPN Configure single value data vis modeling trajectories drawByAttribute 0 addValue brem key eBrem vis modeling trajectories drawByAttribute 0 addValue annihil key annihil vis modeling trajectories drawByAttribute 0 addValue decay key Decay vis modeling trajectories drawByAttribute 0 addValue mulon key muloni vis modeling trajectories drawByAttribute 0 addValue elon key eloni vis modeling trajectories drawByAttribute 0 brem key setLineColour red vis modeling trajectories drawByAttribute 0 annihil key setLineColour green vis modeling trajectories drawByAttribute 0 decay ke
223. cuts to each of these detector parts This allows a more detailed simulation to occur only in those regions where it is required The concept of detector Region was introduced to address this need Once the final geometry setup of the detector has been defined a region can be specified by constructing it with G4Region const G4String amp rName where rName String identifier for the detector region A G4Region must then be assigned to a logical volume in order to make it a Root Logical Volume G4Region emCalorimeter new G4Region EM Calorimeter emCalorimeter AddRootLogicalVolume emCalorimeter A root logical volume is the first volume at the top of the hierarchy to which a given region is assigned Once the region is assigned to the root logical volume the information is automatically propagated to the volume tree so that each daughter volume shares the same region Propagation on a tree branch will be interrupted if an already existing root logical volume is encountered A specific Production Cut can be assigned to the region by defining and assigning to ita G4ProductionCut object emCalorimeter gt SetProductionCuts emCalCuts Section 5 4 2 describes how to define a production cut The same region can be assigned to more than one root logical volume and root logical volumes can be removed from an existing region A logical volume can have only one region assigned to it Regions will be automatically re
224. cy class names G4FinalStateElasticScreenedRutherford or G4FinalStateElasticBrennerZaider Excitation one model Cross section policy class name G4CrossSectionExcitationEmfietzoglou Final state policy class name G4FinalStateExcitationEmfietzoglou Jonisation one model e Cross section policy class name G4CrossSectionIonisationBorn Final state policy class names G4FinalStatelonisationBorn Proton processes Excitation two complementary models available depending on energy range Cross section policy class name G4CrossSectionExcitationMillerGreen Final state policy class name G4FinalStateExcitationMillerGreen Cross section policy class name G4CrossSectionExcitationBorn Final state policy class name G4FinalStateExcitationBorn onisation two complementary models available depending on energy range e Cross section policy class name G4CrossSectionIonisationRudd Final state policy class name G4FinalStatelonisationRudd e Cross section policy class name G4CrossSectionlonisationBorn e Final state policy class name G4FinalStatelonisationBorn Charge decrease one model Cross section policy class name G4CrossSectionChargeDecrease Final state policy class name G4FinalStateChargeDecrease Hydrogen processes Jonisation one model e Cross section policy class name G4CrossSectionlonisationRudd Final state policy class name G4FinalStatelonisationRudd Charge increase one model e Cross sec
225. d e G4vParticleChange AtRestDoIt const G4Track amp track const G4Step amp stepData This method is invoked only for stopped particles and only if its process produced the minimum step length or the process is forced to occur For each of the above DoIt methods G4VProcess provides a corresponding pure virtual GPIL method e G double PostStepGetPhysicallnteractionLength const G4Track track G4double previousStepSize G4ForceCondition condition This method generates the step length allowed by its process It also provides a flag to force the interaction to occur regardless of its step length e G double AlongStepGetPhysicallnteractionLength const G4Track amp track G4double previousStepSize G4double currentMinimumStep G4double amp proposed Safety G4GPILSelection selection This method generates the step length allowed by its process G4double AtRestGetPhysicallnteractionLength const G4Track track G4ForceCondition condition This method generates the step length in time allowed by its process It also provides a flag to force the inter action to occur regardless of its step length Other pure virtual methods in G4VProcess follow virtual G4bool IsApplicable const G4ParticleDefinition returns true if this process object is applicable to the particle type virtual void PreparePhysicsTable const G4ParticleDefinition amp and virtual void BuildPhysicsTable const G4ParticleDefinition amp
226. d one The reflection transformation is applied as a decompo sition into rotation and translation transformations The factory is a singleton object which provides the following methods G4PhysicalVolumesPair Place const G4Transform3D amp transform3D const G4String name G4LogicalVolume LV G4LogicalVolume motherLV G4bool isMany G4int copyNo G4bool surfCheck false G4PhysicalVolumesPair Replicate const G4String amp name G4LogicalVolume LV G4LogicalVolume motherLV EAxis axis G4int nofReplicas G4double width G4double offset 0 G4PhysicalVolumesPair Divide const G4String amp name G4LogicalVolume LV G4LogicalVolume motherLV EAxis axis G4int nofDivisions G4double width G4double offset The method Place used for placements evaluates the passed transformation In case the transformation con tains a reflection the factory will act as follows 1 Performs the transformation decomposition 2 Creates a new reflected solid and logical volume or retrieves them from a map if the reflected object was already created 3 Transforms the daughters if any and place them in the given mother If successful the result is a pair of physical volumes where the second physical volume is a placement in a reflected mother Optionally it is also possible to force the overlaps check at the time of placement by activating the surfCheck flag The method Replicate creates replicas in the given mother If succ
227. d TrackerChamber parameterisedPV trackerChamberLV Its logical volume logicTracker Mother logical volume kUndefined Allow default voxelising no axis 6 Number of chambers chamberParam The parameterisation kUndefined is the suggested choice giving 3D voxelisation i e along the three cartesian axes as is applied for placements Note In some cases where volume have clear separation along a single axis this axis eg kZAxis can be used to choose force optimisation only along this axis in geometrical calculations When an axis is given it forces the use of one dimensional voxelisation The general constructor is G4PVParameterised const G4String pName G4LogicalVolume pCurrentLogical G4LogicalVolume pMotherLogical OR G4VPhysicalVolume const EAxis pAxis const G4int nReplicas 81 Detector Definition and Response G4VPVParameterisation pParam G4bool pSurfChk false Note that for a parameterised volume the user must always specify a mother volume So the world volume can never be a parameterised volume nor it can be sliced The mother volume can be specified either as a physical or a logical volume pAxis specifies the tracking optimisation algorithm to apply if a valid axis the axis along which the parameter isation is performed is specified a simple one dimensional voxelisation algorithm is applied if kUndefined is specified instead the default three
228. d Set CoutDest ination this tells UImanager that this instance of G4UIterminal receives the stream generated by G4cout G4UIterminal G4UIterminal UI G4UImanager GetUlpointer UI gt SetCoutDestination this Val Similarly UI gt SetCoutDestination NULL must be added to the destructor of the class 3 Write or modify the main program To modify examp1eNO1 to produce a log file derive a class as described in step 1 above and add the following lines to the main program include MySession hh main get the pointer to the User Interface manager G4UImanager UI G4UImanager GetUIpointer construct a session which receives G4cout G4cerr MySession LoggedSession new MySession UI gt SetCoutDestination LoggedSession session gt SessionStart not required in this case M eado SO SEUN Enee IEE M delete LoggedSession return 0 Note G4cout G4cerr should not be used in the constructor of a class if the instance of the class is intended to be used as static This restriction comes from the language specification of C See the documents below for details e M A Ellis B Stroustrup Annotated C Reference Manual Section 3 4 Ellis1990 P J Plauger The Draft Standard C Library Plauger1995 203 Chapter 8 Visualization 8 1 Introduction to Visualization The Geant4 visualization system was developed in response to a diverse set of requirements 1 Quick re
229. d adds physical characteristics the material of the volume whether it contains any sensitive detector elements the magnetic field etc We have yet to describe how to position the volume To do this you create a physical volume which places a copy of the logical volume inside a larger containing volume 2 2 2 Create a Simple Volume What do you need to do to create a volume Create a solid Create a logical volume using this solid and adding other attributes 2 2 3 Choose a Solid To create a simple box you only need to define its name and its extent along each of the Cartesian axes You can find an example how to do this in Novice Example NOI In the detector description in the source file ExNO1DetectorConstruction cc you will find the following box definition Example 2 3 Creating a box G4double expHall x 3 0 m G4double expHall y 1 0 m G4double expHall z 1 0 m G4Box experimentalHall box new G4Box expHall box expHall x expHall y expHall z This creates a box named expHall box with extent from 3 0 meters to 3 0 meters along the X axis from 1 0 to 1 0 meters in Y and from 1 0 to 1 0 meters in Z It is also very simple to create a cylinder To do this you can use the G4Tubs class Getting Started with Geant4 Running a Simple Example Example 2 4 Creating a cylinder G4double innerRadiusOfTheTube 0 cm G4double outerRadiusOfTheTube 60 cm G4double hightOfTheTube 2
230. d and the SetUnitCategory method alternatively G4ThreeVector GetNew3VectorValue G4String paramString Convert a G4String parameter value given by the SetNewValue method of your messenger into a G4ThreeVector Please note that the return value has already been multiplied by the value of the given unit G4ThreeVector GetNew3VectorRawValue G4String paramString Convert a G4String parameter value given by the SetNewValue method of your messenger into three vector but without multiplying the value of the given unit G4double GetNewUnitValue G4String paramString Convert a G4String unit value given by the SetNewValue method of your messenger into a double G4String convertToString G4ThreeVector currVal char unitName Convert the current three vector to a G4String which should be returned by the Get CurrentValue method of your messenger The three vector value will be divided by the value of the given unit and converted to a string Given unit will be added to the string Additional comments on the SetParameterName method You can add one additional argument of G4bool type for every SetParameterName method mentioned above This additional argument is named currentAsDefaultFlag and the default value of this argument is false If you assign this extra argument as t rue the default value of the parameter will be overriden by the current value of the target class 7 2 3 An example messenger This example is of G4Parti
231. d detector simulation program This manual is designed to e introduce the first time user to the Geant4 object oriented detector simulation toolkit provide a description of the available tools and how to use them and supply the practical information required to develop and run simulation applications which may be used in real experiments This manual is intended to be an overview of the toolkit rather than an exhaustive treatment of it Related physics discussions are not included unless required for the description of a particular tool Detailed discussions of the physics included in Geant4 can be found in the Physics Reference Manual Details of the design and functionality of the Geant4 classes can be found in the User s Guide for Toolkit Developers and a complete list of all Geant4 classes is given in the Software Reference Manual Geant4 is a completely new detector simulation toolkit written in the C language The reader is assumed to have a basic knowledge of object oriented programming using C No knowledge of earlier FORTRAN versions of Geant is required Although Geant4 is a fairly complicated software system only a relatively small part of it needs to be understood in order to begin developing detector simulation applications 1 2 How to use this manual A very basic introduction to Geant4 is presented in Chapter 2 Getting Started with Geant4 Running a Simple Example It is a recipe for writing and running a simple Gea
232. d for use in geometrical descriptions Details about regions and how to use them are available in Section 4 1 3 1 As an example suppose a user defines three regions corresponding to the tracking volume the calorimeter and the bulk structure of a detector For performance reasons the user may not be interested in the detailed development of electromagnetic showers in the insensitive bulk structure but wishes to maintain the best possible accuracy in the tracking region In such a use case Geant4 allows the user to set different production thresholds cuts for each geometrical region This ability referred to as cuts per region is also a new feature provided by the Geant4 5 1 release The general concepts of production thresholds were presented in the Section 5 4 Please note that this new feature is intended only for users who 1 are simulating the most complex geometries such as an LHC detector and 2 are experienced in simulating electromagnetic showers in matter We strongly recommend that results generated with this new feature be compared with results using the same geometry and uniform production thresholds Setting completely different cut values for individual regions may break the coherent and comprehensive accuracy of the simulation Therefore cut values should be carefully opti mized based on a comparison with results obtained using uniform cuts 5 5 2 Default Region The world volume is treated as a region by default A G
233. d in Geant4 Geant4 classes which can accommodate user information classes are G4Event G4Track G4Primary Vertex G4PrimaryParticle and G4Region These classes are discussed here 6 3 1 GAVUserEventlnformation G4VUserEventInformation is an abstract class from which the user can derive his her own concrete class for storing user information associated with a G4Event class object It is the user s responsibility to construct a concrete class object and set the pointer to a proper G4Event object Within a concrete implementation of G4UserEventAction the SetUserEventInformation method of G4EventManager may be used to set a pointer of a concrete class object to G4Event given that the G4Event object is available only by pointer to const Alternatively the user may modify the GenerateEvent method of his her own RunManager to instantiate a G4VUserEventInformation object and set it to G4Event The concrete class object is deleted by the Geant4 kernel when the associated G4Event object is deleted 192 User Actions 6 3 2 G4VUserTrackinformation This is an abstract class from which the user can derive his her own concrete class for storing user information associated with a G4Track class object It is the user s responsibility to construct a concrete class object and set the pointer to the proper G4Track object Within a concrete implementation of G4UserTrackingAction the SetUserTrackInformation method of G4TrackingManager may be
234. d of the step is used always smaller than at the beginning G4ErrorEnergyLoss computes once the energy loss and then replaces the original energy loss by subtracting adding half of this value what is approximately the same as computing the energy loss with the energy at the middle of the step In this way a better calculation of the energy loss is obtained with a minimal impact on the total CPU time The user may use his her own physics list instead of G4ErrorPhysicsList As it is not needed to define a physics list when running this package the user may have not realized that somewhere else in his her application it has been defined therefore a warning will be sent to advert the user that he is using a physics list different to G4ErrorPhysicsList If anew physics list is used it should also initialize the G4ErrorMessenger with the classes that serve to limit the step G4ErrorEnergyLoss eLossProcess new G4ErrorEnergyLoss G4ErrorStepLengthLimitProcess stepLengthLimitProcess new G4ErrorStepLengthLimitProcess G4ErrorMagFieldLimitProcess magFieldLimitProcess new G4ErrorMagFieldLimitProcess new G4ErrorMessenger stepLengthLimitProcess magFieldLimitProcess eLossProcess To ease the use of this package in the reconstruction code the physics list whether G4ErrorPhysicsList or the user s one will be automatically initialized before starting the track propagation if it has not been done by the us
235. d via the replicas logical volume should have the dimensions of the first volume created and must be of the correct symmetry type in order to assist in good visualisation ex For X axis replicas in a box the solid should be another box with the dimensions of the replications same Y amp Z dimensions as mother box X dimension mother s X dimension nReplicas Replicas may be placed inside other replicas provided the above rule is observed Normal placement volumes may be placed inside replicas provided that they do not intersect the mother s or any previous replica s boundaries Parameterised volumes may not be placed inside Because of these rules it is not possible to place any other volume inside a replication in radius The world volume cannot act as a replica therefore it cannot be sliced During tracking the translation rotation associated with each G4PVReplica object is modified according to the currently active replication The solid is not modified and consequently has the wrong parameters for the cases of phi and r replication and for when the cross section of the mother is not constant along the replication Example Example 4 2 An example of simple replicated volumes with G4PVReplica G4PVReplica repX Linear Array pRepLogical pContainingMother KXAS iS D7 LOSM G4PVReplica repR RSlices pRepRLogical pContainingMother KERHO Sy WO DE G4PVReplica repRZ RZSlices pRepRZLogical amp repR leg
236. default run manager G4RunManager runManager new G4RunManager set mandatory initialization classes NO2DetectorConstruction detector new N02DetectorConstruction runManager SetUserInitialization detector runManager SetUserInitialization new NO2PhysicsList visualization manager G4VisManager visManager new G4VisExecutive visManager gt initialize set user action classes runManager gt SetUserAction new NO2PrimaryGeneratorAction detector runManager gt SetUserAction new NO2RunAction runManager gt SetUserAction new NO2EventAction runManager gt SetUserAction new NO2SteppingAction get the pointer to the User Interface manager G4UImanager UI G4UImanager GetUIpointer if argc 1 Define G UI terminal for interactive mode 4 G4UIsession session new G4UIterminal UI gt ApplyCommand control execute prerun g4mac session gt sessionStart delete session else Batch mode 4 G4String command control execute G4String fileName argv 1 UI gt ApplyCommand command fileName job termination delete visManager delete runManager return 0 2 1 5 G4cout and G4cerr Although not yet included in the above examples output streams will be needed G4cout and G4cerr are iostream objects defined by Geant4 The usage of these objects is exactly the same as the ordinary cout and cerr except that the output streams will be handled by G4UImanager T
237. dering is important if you use ghost geometries since the G4FastSimulationManagerProcess will provide navigation in the ghost world to limit the step on ghost boundaries The G4FastSimulationManager must be added to the process list of a particle as a continuous and discrete process if you use ghost geometries for this particle You can add it as a discrete process if you don t use ghosts The following code registers the G4FastSimulationManagerProcess with all the particles as a discrete and contin uous process void MyPhysicsList addParameterisation G4FastSimulationManagerProcess theFastSimulationManagerProcess new G4FastSimulationManagerProcess theParticlelterator gt reset while theParticleIterator G4ParticleDefinition particle theParticleIterator gt value G4ProcessManager pmanager particle GetProcessManager pmanager gt AddProcess theFastSimulationManagerProcess 1 0 0 5 2 6 6 The G4GlobalFastSimulationManager Singleton Class This class is a singleton which can be accessed as follows include G4GlobalFastSimulationManager hh G4GlobalFastSimulationManager globalFSM 167 Tracking and Physics globalFSM G4GlobalFastSimulationManager getGlobalFastSimulationManager Presently you will mainly need to use the GlobalFastSimulationManager if you use ghost geometries 5 2 6 7 Parameterisation Using Ghost Geometries In some cases volumes of the tracking geo
238. descriptions of the examples are listed below 9 2 1 1 Analysis e AOI hit scoring and histogramming using the AIDA interface e AnaEx01 histogram and tuple manipulations using an AIDA compliant system 267 Examples N03Con modified novice example N03 showing how to use a Convergence Tester 9 2 1 2 Electromagnetic TestEm0 how to print cross sections and stopping power used in input by the standard EM package TestEml how to count processes activate inactivate them and survey the range of charged particles How to define a maximum step size TestEm2 shower development in an homogeneous material longitudinal and lateral profiles TestEm3 shower development in a sampling calorimeter collect energy deposited survey energy flow and print stopping power TestEm4 9 MeV point like photon source plot spectrum of energy deposited in a single media TestEm5 how to study transmission absorption and reflection of particles through a single thin or thick layer TestEm6 physics list for rare high energy electromagnetic processes gamma conversion and e annihilation into pair of muons TestEm7 how to produce a Bragg curve in water phantom How to compute dose in tallies TestEm8 test of photo absorption ionisation model in thin absorbers and transition radiation TestEm9 shower development in a crystal calorimeter cut per region TestEm10 XTR transition radiation model investigation of ionisation in thin absor
239. dimensional voxelisation algorithm applied for normal placements will be ac tivated In the latter case more voxels will be generated therefore a greater amount of memory will be consumed by the optimisation algorithm pSurfChk if true activates a check for overlaps with existing volumes or paramaterised instances The parameterisation mechanism associated to a parameterised volume is defined in the parameterisation class and its methods Every parameterisation must create two methods e ComputeTransformation defines where one of the copies is placed ComputeDimensions defines the size of one copy and aconstructor that initializes any member variables that are required An example is ExNO2ChamberParameterisation that parameterises a series of boxes of different sizes Example 4 4 An example of Parameterised boxes of different sizes class ExNO2ChamberParameterisation public G4VPVParameterisation void ComputeTransformation const G4int copyNo G4VPhysicalVolume physVol const void ComputeDimensions G4Box amp trackerLayer const G4int copyNo const G4VPhysicalVolume physVol const These methods works as follows The ComputeTransformation method is called with a copy number for the instance of the parameterisation under consideration It must compute the transformation for this copy and set the physical volume to utilize this transformation void ExN02ChamberParameterisation ComputeTransformation const G4int c
240. ds dee aec apteilueeee pipi 58 4 1 3 Logical Volumes i4 iet rates teet eo qe Deere Or esie a 76 4 T4 Physical Volumes ika eee ee eet ute py E er ree ERE EP Wu ERE E Ee is Tik TI 4 1 5 Touchables Uniquely Identifying a Volume ses 87 4 1 6 Creating an Assembly of Volumes cece cece cece eee eI Ie HI mH emere 88 4 1 7 Reflecting Hierarchies of Volumes sess 91 4 1 8 The Geometry Navigator III eH mee EE aaa 92 4 1 9 A Simple Geometry Editor 11 5 oie eterne Gg Ere ia sie 98 4 1 10 Converting Geometries from Geant3 21 Lukaa aaa aaa aa aaa aaa aa aa aaa 99 4 1 11 Detecting Overlapping Volumes 0 2 0 0 cece cece HH HH meme 101 4 1 12 Dynamic Geometry Setups 2 0 0 eee cece ence aaa aaa aa aa aaa aaa aaa 105 4 1 13 Importing XML Models Using GDML oo see 106 4 1 14 Saving geometry tree objects in binary format sssssse aaa 106 stu au US 106 4 2 1 Daedra 106 4 22 Introduction to the Classes inet rete Per e e EE e tr aa a ERR 106 4 2 3 Recipes for Building Elements and Materials e 108 424 The Tables rte e PO eoe tecto er rie io te it pesta Ue 110 4 3 Electromagnetic Field cironi ene GRE i sa asa ERE REIS 111 4 3 1 An Overview of Propagation in a Field 111 4 32 Practical Aspects 1 eei be RES 112 4 3 3 S pm Tracking i e te Ie D itat en Etre ete oes bat
241. e static interface const G4long table entry table entry HepRandom getTheSeeds it returns a pointer table entry to the local SeedTable at the current index position The couple of seeds accessed represents the current status of the engine itself G4int index n G4long seeds 2 HepRandom setTheSeeds seeds index sets the new index for seeds and modify the values inside the local SeedTable at the index position If the index is not specified the current index in the table is considered The setSeed method resets the current status of the engine to the original seeds stored in the static table of seeds in HepRandom at the specified index Except for the RanecuEngine for which the internal status is represented by just a couple of longs all the other engines have a much more complex representation of their internal status which currently can be obtained only through the methods saveStatus restoreStatus and showStatus which can also be statically called from HepRandom The status of the generator is needed for example to be able to reproduce a run or an event in a run at a given stage of the simulation RanecuEngine is probably the most suitable engine for this kind of operation since its internal status can be fetched reset by simply using get Seeds set Seeds get TheSeeds set TheSeeds for the stat ic interface in HepRandom 3 2 2 2 The static interfac
242. e if pVVisManager Declare begininng of visualization G4UImanager GetUIpointer gt ApplyCommand vis scene notifyHandlers Draw trajectories for G4int i 0 i lt n trajectories i evt gt get trajectoryContainer i gt DrawTrajectory Construct 3D data for hits MyTrackerHitsCollection THC MyTrackerHitsCollection HCE gt get HC trackerCollID if THC THC gt DrawAllHits MyCalorimeterHitsCollection CHC MyCalorimeterHitsCollection HCE get HC calorimeterCollID if CHC CHC gt DrawAllHits Declare end of visualization G4UImanager GetUIpointer gt ApplyCommand vis viewer update fd end of C codes You can re visualize a physical volume where a hit is detected with a highlight color in addition to the whole set of detector components It is done by calling a drawing method of a physical volume directly The method is fd Drawing methods of a physical volume virtual void Draw const G4VPhysicalVolume amp This method is for example called in a method MyXXXHit Draw describing the visualization of hits with markers The following is an example for this l C source codes An example of visualizing hits with void MyCalorimeterHit Draw G4VVisManager pVVisManager G4VVisManager GetConcreteInstance if pVVisManager G4Transform3D trans rot pos 234 Visualization G4VisAttributes attribs
243. e G4DAWN NAMED PIPEto l e g setenv G4DAWN_NAMED_PIPE 1 This setting switches the default socket connection to the named pipe connection within the same host machine The DAWN Network driver also saves the 3D data to the file g4 prim in the current directory 8 3 7 Remote Visualization with the DAWN Network Driver Visualization in Geant4 is considered to be remote when it is performed on a machine other than the Geant4 host Some of the visualization drivers support this feature Usually the visualization host is your local host while the Geant4 host is a remote host where you log in for example with the telnet command This enables distributed processing of Geant4 visualization avoiding the 215 Visualization transfer of large amounts of visualization data to your terminal display via the network This section describes how to perform remote Geant4 visualization with the DAWN Network driver In order to do it you must install the Fukui Renderer DAWN on your local host beforehand The following steps realize remote Geant4 visualization viewed by DAWN 1 Invoke DAWN with G option on your local host Local Host gt dawn G This invokes DAWN with the network connection mode 2 Login to the remote host where a Geant4 executable is placed 3 Set an environment variable on the remote host as follows Remote_Host gt setenv G4DAWN_HOST_NAME local_host_name For example if you are working in the l
244. e side upper endcap Note on pA1ph1 2 the two angles have to be the same due to the planarity condition Sphere or Spherical Shell Section To build a sphere or a spherical shell section use G4Sphere const G4String amp pName G4double pRmin G4double pRmax G4double BEBE G4double EDENI G4double pSTheta G4double pDTheta In the picture pRmin 100 pRmax 120 pSPhi O Degree pDPhi 180 Degree pSTheta 0 De gree pDTheta 180 Degree 6 2 Detector Definition and Response to obtain a solid with name pName and parameters pRmin Inner radius pRmax Outer radius pSPhi Starting Phi angle of the segment in radians pDPhi Delta Phi angle of the segment in radians pSTheta Starting Theta angle of the segment in radians pDTheta Delta Theta angle of the segment in radians Full Solid Sphere To build a full solid sphere use G4Orb const G4String amp pName G4double pRmax In the picture pRmax 100 The Orb can be obtained from a Sphere with pRmin 0 pSPhi 0 pDPhi 2 Pi pSTheta 0 pDTheta Pi pRmax Outer radius Torus To build a torus use G4Torus const G4String amp pName G4double pRmin G4double pRmax G4double pRtor G4double pSPhi G4double pDPhi to obtain a solid with name pName and parameters In the picture pRmin 40 pRmax 60 200 pSPhi 0 pDPhi pRtor 90 Degree
245. e targetSize 0 50 E G4ThreeVector targetSize targetSize 05097 G4ThreeVector ORO 0 0 targetSize ABSOLUTE G4QuadrangularFacet facet5 new G4QuadrangularFacet G4ThreeVector targetSize targetSize 0 0 G4ThreeVector targetSize targetSize OP G4ThreeVector ttargetSize targetSize ORO 0 0 G4ThreeVector ttargetSize targetSize ABSOLUTE Now add the facets to the solid 24 solidTarget gt AddFacet G4VFacet facetl solidTarget gt AddFacet G4VFacet facet2 solidTarget gt AddFacet G4VFacet facet3 F 7 solidTarget gt AddFacet G4VFacet facet4 solidTarget gt AddFacet G4VFacet facet5 7 Finally declare the solid is complete ah solidTarget gt SetSolidClosed true The G4TriangularFacet class is used for the contruction of G4TessellatedSolid It is defined by three vertices which shall be supplied in anti clockwise order looking from the outside of the solid where it belongs Its constructor looks like G4TriangularFacet const G4ThreeVector PEO const G4ThreeVector UELS const G4ThreeVector NAE E G4FacetVertexType fType i e it takes 4 parameters to define the three vertices G4FacetVertexType ABSOLUTE in which case Pt 0 vt1 and vt2 are the three vertices in anti clockwise order looking from the outside G4FacetVertexType RELATIVE in which case the first vertex is Pt O the second vertex is PtO vt1 and t
246. e visualization of a selected logical volume with coordinate axes Idle vis specify Absorber Idle vis scene add axes 0 0 0 500 mm Idle vis scene add text 0 0 0 mm 40 100 200 LogVol Absorber Idle vis viewer flush For more options see the Control UICommands section of this user guide 8 4 6 Visualization of trajectories vis scene add tra jectories command Command vis scene add trajectories smooth rich adds trajectories to the current scene The optional parameters smooth and or rich you may specify either both or neither invoke if smooth is specified the storing and displaying of extra points on curved trajectories and if rich is specified the storing for possible subsequent selection and display of additional information such as volume names creator process energy deposited global time Be aware of course that this imposes computational and memory overheads Note that this automatically issues the appropriate t racking storeTrajectory command so that trajectories are stored by default they are not The visualization is performed with the command run beamOn unless you have non default values for vis scene endOfEventAction or vis scene endOfRunAction described below 224 Visualization Command vis scene add trajectories smooth rich Action The command adds trajectories to the current scene Trajectories are drawn at end of event when the scene in which they are
247. e 05 5 0 0003 6 0 0015 7 0 0026 9 0 0008 20 0 0001 26 1e 05 30 1e 05 G4 SODIUM CARBONATE 6 0 1133 8 0 4528 11 0 4338 G4 SODIUM IODIDE 11 0 1533 53 0 8466 G4 SODIUM MONOXIDE 8 0 2581 11 0 7418 G4 SODIUM NITRATE 79 IDONE 16 07 24 53 28 72 52 48 55 45 55 45 73 95 32 1 17 T3 11 89 71 29 2 46 34 SL0 2 65 35 37 63 68 32 95 48 57 58 42 88 5 2 02 3 9 7 5 5 23 61 15 18 27 43 57 Ts 2 25 SIS 232 00187939 43 8035 9819 92 92 123 32 473 56 47 01 532 27 261 67 7 431 9 189 9 47 1 52 61 1 66 2 56 5 59 8 93 139 2 486 6 487 1 543 5 TZ 25 48 8 299 Appendix 13 13 7 0 164795 8 0 56472 1 0 270485 G4_STILBENE 0 067101 6 0 932899 G4_SUCROSE 0 064779 6 0 42107 8 0 514151 G4_TERPHENYL 0 044543 6 0 955457 G4_TESTES_ICRP 0 104166 6 0 09227 74 0 01994 8 0 773884 1 0 00226 2 0 00011 5 0 00125 6 0 00146 7 0 00244 9 0 00208 20 0 000 26 2e 05 30 2e 05 G4_TETRACHLOROETHY LENE 6 0 144856 2 0 855144 G4 THALLIUM CHLORIDE 7 0 147822 81 0 852178 G4 TISSUE SOFT ICRP 0 104472 6 0 23219 7 0 02488 8 0 630238 1 0 00113 2 0 00013 5 0 00133 6 0 00199 7 0 00134 9 0 00199 20 0 00023 26 5e 05 30 3e 05 G4_TISSUE_SOFT_ICRU 4 ur 0 101172 6 0 111 7 0 026 8 0 761828 G4 TISSUE METHANE L 0 10186
248. e 2 eg pion model mother volume of hierarchy tree G4VFastSimulationModel root F4LogicalVolume 1 mother volume of hierarchy tree G4FastSimulationManagerProcess This is a G4VProcess It provides the interface between the tracking and the parameterisation It must be set in the process list of the particles you want to parameterise G4GlobalFastSimulationManager This a singleton class which provides the management of the G4FastSimulationManager objects and some ghost facilities 5 2 6 3 The G4VFastSimulationModel Abstract Class Constructors The G4VFastSimulationModel class has two constructors The second one allows you to get started quickly G4VFastSimulationModel const G4String amp aName Here aName identifies the parameterisation model G4VFastSimulationModel const G4String aName G4Region G4bool IsUnique false In addition to the model name this constructor accepts a G4Region pointer The needed G4FastSimulationManager object is constructed if necessary passing to it the G4Region pointer and the boolean value If it already exists the model is simply added to this manager Note that the G4VFastSimulationModel object will not keep track of the G4Region passed in the constructor The 165 Tracking and Physics boolean argument is there for optimization purposes if you know that the G4Region has a unique root G4LogicalVolume uniquely placed you can set the boolean value to true Virtual methods
249. e centre of the side Twisted Trapezoid with x and y dimensions varying along z A twisted trapezoid with the x and y dimensions varying along z can be defined as follows G4TwistedTrd const G4String amp G4double G4double G4double G4double G4double G4double pName poxi JSIBP pDyl pDy2 pDz twistedangle i j j NSS In the picture dxl 30 dx2 10 dyl 40 dy2 15 dz 60 twistedangle 30 Degr where pDx1 Half x length at the surface positioned at dz pDx2 Half x length at the surface positioned at dz 70 Detector Definition and Response pDyl Half y length at the surface positioned at dz pDy2 Half y length at the surface positioned at dz pDz Half z length twistedangle Twisted angle Tube Section Twisted along Its Axis A tube section twisted along its axis can be defined as follows G4TwistedTubs const G4String amp pName G4double twistedangle G4double endinnerrad G4double endouterrad G4double halfzlen G4double dphi In the picture ndinnerrad 10 endouterrad 15 halfzlen 20 dphi 90 De gree twistedangle 60 Degr G4TwistedTubs is a sort of twisted cylinder which placed along the z axis and divided into phi segments is shaped like an hyperboloid where each of its segmented pieces can be tilted with a stereo angle It can have inner and outer surfaces with the same stereo angle
250. e correct unpacking tool Note that for Linux you must download the gtar gz file I cannot find CLHEP files or library and I have it installed in my system If the standard CLHEP installation procedure has been adopted the variable CLHEP_BASE_DIR should point to the area where include and lib directories for CLHEP headers amp library are installed in your system In case the library file name is different than the one expected 1ilbCLHEP a you should either create a symbolic link with the expected name or define the variable CLHEP_LIB in your environment which explicitly sets the name of the CLHEP library If a non standard CLHEP installation has been adopt ed define variables CLHEP_INCLUDE_DIR CLHEP_LIB_DIR and CLHEP LIB to refer explicitly to the place where headers library and library name respectively are placed in your system On Windows systems the full library file name with extension should be specified as CLHEP_LIB while for UNIX like systems just the name is required i e CLHEP for libCLHEP a While installing the Geant4 libraries I get the following message printed gmake 1 cernlib Command not found Has Geant4 been installed properly What to do to solve this error The message gmake 1 cernlib Command not found shows that you don t have the cernlib command installed in your system cernlib is a command from the CERN program library cernlib retu
251. e generated two at the time so every other time a number is shot the number returned is the one generated the time before RandBreitWigner Class to shoot numbers according to the Breit Wigner distribution algorithms plain or mean 2 RandPoisson Class to shoot numbers according to the Poisson distribution given a mean default 1 Algorithm taken from W H Press et al Numerical Recipes in C Second Edition 3 2 3 The HEPNumerics module A set of classes implementing numerical algorithms has been developed in Geant4 Most of the algorithms and methods have been implemented mainly based on recommendations given in the books B H Flowers An introduction to Numerical Methods In C Claredon Press Oxford 1995 e M Abramowitz I Stegun Handbook of mathematical functions DOVER Publications INC New York 1965 chapters 9 10 and 22 This set of classes includes G4ChebyshevApproximation 36 Toolkit Fundamentals Class creating the Chebyshev approximation for a function pointed by fFunction data member The Chebyshev polynomial approximation provides an efficient evaluation of the minimax polynomial which among all poly nomials of the same degree has the smallest maximum deviation from the true function G4Datalnterpolation Class providing methods for data interpolations and extrapolations Polynomial Cubic Spline G4GaussChebyshevQ G4GaussHermiteQ G4GaussJacobiQ G4GaussLaguerreQ
252. e in the HepRandom class HepRandom a singleton class and using a HepJamesRandom engine as default algorithm for pseudo random num ber generation HepRandom defines a static private data member theGenerator and a set of static methods to manipulate it By means of theGenerator the user can change the underlying engine algorithm get and set the seeds and use any kind of defined random distribution The static methods set TheSeed and get The Seed will set and get respectively the initial seed to the main engine used by the static generator For example HepRandom setTheSeed seed to change the current seed to seed int startSeed HepRandom getTheSeed to get the current initial seed HepRandom saveEngineStatus to save the current engine status on file HepRandom restoreEngineStatus to restore the current engine to a previous saved configuration HepRandom showEngineStatus to display the current engine status to stdout int index n long seeds 2 HepRandom getTheTableSeeds seeds index fills seeds with the values stored in the global seedTable at position index 35 Toolkit Fundamentals Only one random engine can be active at a time the user can decide at any time to change it define a new one if not done already and set it For example RanecuEngine theNewEngine HepRandom setTheEngine amp theNewEngine or simply setting it to an old inst
253. e mode and batch mode via macro file construction and deletion of G UI session and VisManager random number engine construction and deletion of G4RunManager construction and set of mandatory user classes 259 Examples ExNO2DetectorConstruction header file source file derived from G4VUserDetectorConstruction definitions of single element mixture and compound materials e CSG solids Uniform magnetic field construction of ExN02MagneticField Physical Volumes G4Placement volumes with amp without rotation G4PVParameterised volumes without rotation ExNO2MagneticField header file source file derived from G4MagneticField Uniform field ExNO2MagneticField ExNO2PhysicsList header file source file derived from G4VUserPhysicsList definition of geantinos electrons positrons gammas utilisation of transportation and standard EM processes Interactivity chooses processes interactively gt messenger class ExNO2PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction construction of G4ParticleGun primary event generation via particle gun ExNO2RunAction header file source file derived from G4VUserRunAction draw detector ExNO2EventAction header file source file derived from G4VUserEventAction print time information ExNO2TrackerSD header file source file derived from G4VSensitiveDetector tra
254. e parameterisation by material A more complex example is provided in examples extended medical DICOM where a phantom grid of cells is built using a parameterisation by material de fined through a map Note Currently for many cases it is not possible to add daughter volumes to a parameterised volume Only parameterised volumes all of whose solids have the same size are allowed to contain daughter volumes When the size or type of solid varies adding daughters is not supported So the full power of parameterised volumes can be used only for leaf volumes which contain no other volumes Advanced parameterisations for nested parameterised volumes A new type of parameterisation enables a user to have the daughter s material also depend on the copy number of the parent when a parameterised volume daughter is located inside another parent repeated volume The parent volume can be a replica a parameterised volume or a division if the key feature of modifying its contents is utilised Note a nested parameterisation inside a placement volume is not supported because all copies of a placement volume must be identical at all levels In such a nested parameterisation the user must provide a ComputeMaterial method that utilises the new argument that represents the touchable history of the parent volume Sample Parameterisation class SampleNestedParameterisation public G4VNestedParameterisation public other methods
255. e scintillation yield of a scintillator depends on the particle type different scintillation processes may be defined for them How this yield scales to the one specified for the material is expressed with the Scin tillationYieldFactor in the user s PhysicsList as shown in Example 5 8 In those cases where the fast to slow excitation ratio changes with particle type the method Set ScintillationExcitationRatio can be called for each scintillation process see the advanced underground_physics example This overwrites the YieldRatio obtained from the GaMaterialPropertiesTable Example 5 8 Implementation of the scintillation process in PhysicsList G4Scintillation theMuonScintProcess new G4Scintillation Scintillation theMuonScintProcess SetTrackSecondariesFirst true theMuonScintProcess SetScintillationYieldFactor 0 8 theParticlelterater gt reset i while theParticleIterator G4ParticleDefinition particle theParticleIterator value G4ProcessManager pmanager particle gt GetProcessManager G4String particleName particle gt GetParticleName if theMuonScintProcess gt IsApplicable particle if particleName mu pmanager gt AddProcess theMuonScintProcess pmanager gt SetProcessOrderingToLast theMuonScintProcess idxAtRest pmanager gt SetProcessOrderingToLast theMuonScintProcess idxPostStep A Gaussian distributed number of photons is generated according to the energy lost
256. e tcsh shell like interface in the application to be built G4UI BUILD XM SESSION G4UI BUILD XAW SESSION Specifies to include in kernel library the XM or XAW Motif based user interfaces G4UI USE XM G4UI USE XAW Specifies to use the XM or XAW interfaces in the application to be built G4UI BUILD WIN32 SESSION Specifies to include in kernel library the WIN32 terminal interface for Windows systems G4UI USE WIN32 Specifies to use the WIN32 interfaces in the application to be built on Windows systems G4UI BUILD QT SESSION Specifies to include in kernel library the Qt terminal interface SOTHOME should specify the path where Qt libraries and headers are installed G4UI USE OT Specifies to use the Ot interfaces in the application to be built 284 Appendix G4UI_NONE If set no UI sessions nor any UI libraries are built This can be useful when running a pure batch job or in a user framework having its own UI system Visualization specific The most relevant flags for visualization graphics drivers are just listed here A description of these variables is given also in section 2 of this User s Guide G4VIS_BUILD_OPENGLX_DRIVER Specifies to build kernel library for visualization including the OpenGL driver with X11 extension It requires SOGLHOME set path to OpenGL installation G4VIS_USE_OPENGLX Specifies to use OpenGL graphics with X11 extension in the application to be built G4VIS_BUILD_OPENGLXM_DRIVER
257. e touchable history is the minimal set of information required to specify the full genealogy of a given physical volume up to the root of the geo metrical tree These touchable volumes are made available to the user at every step of the Geant4 tracking in G4VUserSteppingAction To create access a G4TouchableHistory the user must message G4Navigator which provides the method CreateTouchableHistoryHandle G4TouchableHistoryHandle CreateTouchableHistoryHandle const this will return a handle to the touchable The methods that differentiate the touchable history from other touchables since they have meaning only for this type are G4int GetHistoryDepth const G4int MoveUpHistory G4int num_levels 1 The first method is used to find out how many levels deep in the geometry tree the current volume is The second method asks the touchable to eliminate its deepest level As mentioned above MoveUpHistory num significantly modifies the state of a touchable 4 1 6 Creating an Assembly of Volumes G4AssemblyVolume is a helper class which allows several logical volumes to be combined together in an arbitrary way in 3D space The result is a placement of a normal logical volume but where final physical volumes are many However an assembly volume does not act as a real mother volume being an envelope for its daughter volumes Its role is over at the time the placement of the logical assembly volume is done The physical volume ob
258. e tree terr attt res ba a si bara sess 7 2 2 7 Coordinate Systems and Rotations 2 0 0 0 cece cece eee cece cece nce em em e meme e mene 8 2 3 How to Specify Materials in the Detector sss Hee 8 2 3 General Considerations ceiiiec i ssa eee ka a i Ia ka sa ss 8 2 32 Define a Simple Material 1 ee a ask asses REP Da k a ss ESE p SE 8 2 3 3 Define a Molecule etre ete a a se is as ia dne eerie Dr segete Ne reb DER ean 9 2 3 4 Define a Mixture by Fractional Mass sese 9 2 3 5 Define a Material from the Geant4 Material Database e 9 2 3 6 Print Material Information 2 eere bere ee eter te bue eds re e epp pers 9 2 4 How to Specify Particles dede odes ees come a as elec weet eer up epe eet 10 24 1 Particle Definition rer Perm RE rr Es Sendo sects si ass serra sees 10 24 2 Range CUfs eene aces ig asa ss REIP RUD IM ahead ey 12 2 5 How to Specify Physics Processes eit tte e tree S aa a a peeve k RE 13 2521 Physics PEOCeSSeS sss teret ee aeter dent teresa Sion ssepe a eye deste eroe ny 13 2 52 Managing Processes sss miissen aiaee tee ERR aa RE PRESE ERU Ee P asas 13 2 5 3 Specifying Physics Processes essssssseee III ehem aaa ment entree 14 2 6 How to Generate a Primary Event i etae Pte i a i E a esos 14 2 6 1 Generating Primary Events 20 0 0 cece cee kaka kaka aaa aaa aaa ceca aa aaa aaa aaa aaa 14 2 6 2 GAVPrimaryGenerator i kas ss a is asi sia di e
259. e visualization component allowed us to develop sev eral drivers independently such as for OpenGL and OpenInventor for X11 and Windows DAWN Postscript via DAWN and VRML 8 Interfaces This category handles the production of the graphical user interface GUI and the interactions with external software OODBMS reconstruction etc 3 2 Global Usage Classes The global category in Geant4 collects all classes types structures and constants which are considered of general use within the Geant4 toolkit This category also defines the interface with third party software libraries CLHEP STL etc and system related types by defining where appropriate t ypedefs according to the Geant4 code conventions 32 Toolkit Fundamentals 3 2 1 Signature of Geant4 classes In order to keep an homogeneous naming style and according to the Geant4 coding style conventions each class part of the Geant4 kernel has its name beginning with the prefix G4 e g G4VHit G4GeometryManager G4ProcessVector etc Instead of the raw C types G4 types are used within the Geant4 code For the basic numer ic types int float double etc different compilers and different platforms provide different value ranges In order to assure portability the use of G4int G4float G4double which are base classes globally defined is preferable G4 types implement the right generic type for a given architecture 3 2 1 1 Basic types The basic types in G
260. eKineticEnergy kinetic energy G4double theProperTim proper time G4double theDynamicalCharge dynamical electric charge i e total electric charge as a ion atom G4ElectronOccupancy theElectronOccu electron orbits for ions pancy Table 5 4 Methods to set get cut off values Here the dynamical mass is defined as the mass for the dynamic particle For most cases it is same as the mass defined in G4ParticleDefinition class i e mass value given by Get PDGMass method However there are two exceptions resonance particle ions Resonance particles have large mass width and the total energy of decay products at the center of mass system can be different event by event As for ions Gd4ParticleDefintion defines a nucleus and G4DynamicParticle defines an atom G4ElectronOccupancy describes state of orbital electrons So the dynamic mass can be different from the PDG mass by the mass of electrons and their binding energy In addition the dynamical charge spin and magnetic moment are those of the atom ion i e including nucleus and orbit electrons Decay products of heavy flavor particles are given in many event generators In such cases G4VPrimaryGenerator sets this information in thePreAssignedDecayProducts In addition decay time of the particle can be set arbitrarily time by using PreAssignedDecayProperTime 5 4 Production Threshold versus Tracking Cut 5 4 1 General considerations We have to fulf
261. eant4 are considered to be the following G4int e Gdlong G4float G4double G4bool e G4complex G4String which currently consist of simple t ypede fs to respective types defined in the CLHEP STL or system libraries Most definitions of these basic types come with the inclusion of a single header file globals hh This file also provides inclusion of required system headers as well as some global utility functions needed and used within the Geant4 kernel 3 2 1 2 Typedefs to CLHEP classes and their usage The following classes are t ypede fs to the corresponding classes of the CLHEP Computing Library for High Energy Physics distribution For more detailed documentation please refer to the CLHEP reference guide and the CLHEP user manual G4ThreeVector G4RotationMatrix G4LorentzVector and G4LorentzRotation Vector classes defining 3 component x y z vector entities rotation of such objects as 3x3 matrices 4 com ponent x y z t vector entities and their rotation as 4x4 matrices G4Plane3D G4Transform3D G4Normal3D G4Point3D and G4Vector3D Geometrical classes defining geometrical entities and transformations in 3D space 3 2 2 The HEPRandom module in CLHEP The HEPRandom module originally part of the Geant4 kernel and now distributed as a module of CLHEP has been designed and developed starting from the Random class of MC the original CLHEP s HepRandom module and the Rogue Wave approach in the M
262. ecific physical volume in my mass geometry I tried with GetCopyNo from my physical volume pointer but it doesn t seem to work A The correct way to identify uniquely a physical volume in your mass geometry is by using the touchables see also section 4 1 5 of the User s Guide for Application Developers as follows G4Step aStep G4StepPoint preStepPoint aStep GetPreStepPoint G4TouchableHandle theTouchable preStepPoint GetTouchableHandle G4int copyNo theTouchable GetCopyNumber G4int motherCopyNo theTouchable GetCopyNumber 1 where Copy here stays for any duplicated instance of a physical volume either if itis a G4PVP lacement multiple placements of the same logical volume or a G4PVReplica G4PVParameterised The method GetCopyNo is meant to return only the serial number of placements not duplicated in the ge ometry tree O How can I determine the exact position in global coordinates in my mass geometry during tracking and how can I convert it to coordinates local to the current volume A You need again to do it through the touchables see also section 4 1 5 of the User s Guide for Application Developers as follows G4Step aStep G4StepPoint preStepPoint aStep GetPreStepPoint G4TouchableHandle theTouchable preStepPoint GetTouchableHandle G4ThreeVector worldPosition preStepPoint gt GetPosition G4ThreeVector localPosition theTouchable gt GetHistory gt Get
263. ect of the design was that a generalized Geant4 physics process or interaction could perform actions along a tracking step either localized in space or in time or distributed in space and time and all the possible combinations that could be built from these cases 3 Geometry and Magnetic Field These categories manage the geometrical definition of a detector solid modeling and the computation of distances to solids also in a magnetic field The Geant4 geometry solid modeler is based on the ISO STEP standard and it is fully compliant with it in order to allow in future the exchange of geometrical information with CAD systems A key feature of the Geant4 geometry is that the volume definitions are independent of the solid representation By this abstract interface for the G4 solids the tracking component works identically for various representations The treatment of the propagation in the presence of fields has been provided within specified accuracy An OO design allows us to exchange different numerical algorithms and or different fields not only B field without affecting any other component of the toolkit 4 Particle Definition and Matter These two categories manage the the definition of materials and particles 5 Physics This category manages all physics processes participating in the interactions of particles in matter The abstract interface of physics processes allows multiple implementations of physics models per interaction or
264. ector of the atoms or molecules numbers of each element and an index in the materials table In addition the class has methods to add one by one the elements which will comprise the material A G4Material object can be constructed by directly providing the resulting effective numbers if the user explicitly wants to do so an underlying element will be created with these numbers Alternatively a G4Material object can be constructed by declaring the number of elements of which it will be composed The constructor will new a vector of pointers to G4Element and a vector of doubles to store their fraction of mass Finally the method to add an element must be invoked for each of the desired pre existing element objects providing their addresses and mass fractions At the last element entry the system will automatically compute the vector of the number of atoms of each element per volume the total number of electrons per volume and will store this material in the materials table In the same way a material can be constructed as a mixture of other materials and elements It should be noted that if the user provides the number of atoms or molecules for each element comprising the chemical compound the system automatically computes the mass fraction A few quantities with physical meaning or not which are constant in a given material are computed and stored here as derived data members Some materials are included in the internal Geant4 d
265. ectory aTrack Activate storing of auxiliary points for smoother trajectory static G4IdentityTrajectoryFilter curvedFilter G4TransportationManager GetTransportationManager gt GetPropagatorInField gt SetTrajectoryFilter amp curvedFilter and register an instance of this with the run manager this can be done once and for all as soon as the run manager is instantiated probably in your main program include MyTrackingAction hh runManager gt SetUserAction new MyTrackingAction When you run you need to create a trajectory model and set the time slice interval remembering that paticles are often relativistic and travel 30 cm ns vis modeling trajectories create drawByCharge vis modeling trajectories drawByCharge 0 default setDrawStepPts true vis modeling trajectories drawByCharge 0 default setStepPtsSize 5 vis modeling trajectories drawByCharge 0 default setDrawAuxPts true vis modeling trajectories drawByCharge 0 default setAuxPtsSize 5 vis modeling trajectories drawByCharge 0 default setTimeSliceInterval 0 1 ns vis modeling trajectories list 247 Visualization and use a graphics driver that can display by time vis open OGLSX vis drawVolume vis scene add trajectories vis ogl set startTime 0 5 ns vis ogl set endTime 0 8 ns run beamOn vis viewer refresh A good way to see the particles moving through the detector is vis ogl set fade 1 vis ogl set displayHeadTime true
266. ectory hh explain further and additional insights might be obtained by looking at two methods which use them namely G4VTrajectory DrawTrajectory and G4VTrajectory ShowTrajectory Hits classes in examples extended analysis A01 and extended runAndEvent REO1 show how to do the same for your hits The base class no action methods CreateAttValues and GetAttDefs should be overridden in your concrete class The comments in G4VHit hh explain further In addition the user is free to add a G4std vector lt G4AttValue gt and a G4std vector lt G4AttDef gt to a G4VisAttributes object as could for example be used by a G4LogicalVolume object At the time of writing only the HepRep graphics systems are capable of displaying the G4AttValue information but this information will become useful for all Geant4 visualization systems through improvements in release 8 1 or later 8 7 Enhanced Trajectory Drawing 8 7 1 Default Configuration Trajectory drawing styles are specified through trajectory drawing models Each drawing model has a default configuration provided through a G4VisTrajContext object The default context settings are shown below Property Default Setting Line colour grey Line visibility true Draw line true Draw auxiliary points false Auxiliary point type squares Auxiliary point size 0 Auxiliary point fill style filled Auxiliary point colour magenta 243 Visualization
267. ed in reverse list order by invoking its IsApplicable method for the given particle and material The first data set object that responds positively will then be asked to return a cross section value via its Get CrossSection method If no data set responds positively a G4Exception is thrown and DBL_MIN is returned void AddDataSet G4VCrossSectionDataSet aDataSet This method adds the given cross section data set to the end of the list of data sets in the data store For the evaluation of cross sections the list has a LIFO Last In First Out priority meaning that data sets added later to the list will have priority over those added earlier to the list Another way of saying this is that the data store when given a Get CrossSection request does the IsApplicable queries in the reverse list order starting with the last data set in the list and proceeding to the first and the first data set that responds positively is used to calculate the cross section void BuildPhysicsTable const G4ParticleDefinition amp aParticleType This method may be invoked to indicate to the data store that there has been a change in the cuts or other parameters of the given particle type In response the data store will invoke the BuildPhysicsTable of each of its data sets void DumpPhysicsTable const G4ParticleDefinition amp This method may be used to request the data store to invoke the DumpPhysicsTable method of each of its data sets Defau
268. ed DeltaIntersection is used This is a maximum for the inaccuracy of a single boundary crossing Thus the accuracy of the position of the track after a number of boundary crossings is directly proportional to the number of boundaries 4 3 2 6 Choosing different accuracies for the same volume It is possible to create a FieldManager which has different properties for particles of different momenta or de pending on other parameters of a track This is useful for example in obtaining high accuracy for important tracks e g muons and accept less accuracy in tracking others e g electrons To use this you must create your own field manager which uses the method void ConfigureForTrack const G4Track to configure itself using the parameters of the current track An example of this will be available in examples ex tended field05 4 3 2 7 Parameters that must scale with problem size The default settings of this module are for problems with the physical size of a typical high energy physics setup that is distances smaller than about one kilometer A few parameters are necessary to carry this information to the magnetic field module and must typically be rescaled for problems of vastly different sizes in order to get reasonable performance and robustness Two of these parameters are the maximum acceptable step and the minimum step size The maximum acceptable step should be set to a distance larger than the biggest reasonable step If
269. ed as the vector in the plane perpendicular to the global vector X if the plane normal is equal to X Z is used instead and W is calculated as the vector in the plane perpendicular to V 5 8 3 Trajectory state error The 5X5 error matrix should also be provided at the creation of the trajectory state as a G4ErrorTrajErr object If it is not provided a default object will be created filled with null values Currently the G4ErrorTrajErr is a G4ErrorSymMatrix a simplified version of CLHEP HepSymMa trix The error matrix is given in units of GeV and cm Therefore you should do the conversion if your code is using other units 5 8 4 Targets The user has to define up to where the propagation must be done the target The target can be a surface G4ErrorSurfaceTarget which is not part of the GEANT4 geometry It can also be the surface of a GEANTA volume G4ErrorGeomVolumeTarget so that the particle will be stopped when it enters this volume Or it can be that the particle is stopped when a certain track length is reached by implementing a G4ErrorTrackLengthTarget 5 8 4 1 Surface target When the user chooses a G4ErrorSurfaceTarget as target the track is propagated until the surface is reached This surface is not part of GEANT4 geometry but usually traverses many GEANT4 volumes The class G4ErrorNavigator takes care of the double navigation for each step the step length is calculated as the min imum of the step lengt
270. ed repe RE 116 Geant4 User s Guide for Application Developers 4 4 HIS een ESSERI eS as as ed atl bite a ee Whit eed ete 117 AMAT PAN E E ke T 117 4 4 2 Sensitive detector 25 1 e ai iets Asha SS eis Gest a deka ss Many es 119 4 4 3 Readout geometty once er eR EP OT oases RE EEEE ETSE 120 AAAs GASDManager iiie ep ger IRURE RA UR EIN rE 121 4 4 5 G4MultiFunctionalDetector and G4VPrimitiveScorer esee e 122 4 4 6 Concrete classes of G4VPrimitiveScorer eene 124 4 4 7 G4VSDFilter and its derived classes sees 126 4 4 8 Scoring for Event Biasing sese HH meme mme TERI EREE KESS 126 4 3 Digitization i ERR GERE a EO SE CERES ee e ER Ere ER a patsy Ere E ER Eg e 127 42 5 1 Digi sit Re pe iere dase sa a hatin desires Mies ie Ene 127 4 52 Digitizer module 5n er t PR As inas k a Okis EDS SE Sala Re e ud 128 4 6 Object Persistency i eee eeepc terii beckon I is ss ERE TRUE ss EE vge d 129 4 6 1 Persi stency in Geant4 1 2 ne Ge sa i a i ss eee Pi Ie Ev ER br tess 129 4 6 2 Using Reflex for persistency of Geant4 objects csssss seen aaa 129 4 7 Parallel Geometries 5 er Rete o a i E i REIR E Es ia 130 47 1 A parallel world iere pp E RIDES 130 47 2 Defining a parallel world 5 5 itti e ie FR ee REPE TRES RES 130 4 7 3 Detector sensitivity in a parallel world sese 131 4 8 Command based Scoring inier ertet ERE e ss ao a n EES 132
271. ee bie ae aU geste Et ie 266 9 2 Extended Examples 2 irte ee rtr t ER E ERR EP EE FEE PR HR si a a ees i i ess 267 9 2 1 Extended Example Summary aaa oiner kaka kaka aa aaa eme HH HII ener 267 9 3 Advanced Examples rr ert terret tree dmi tereti tere toned 270 9 3 1 Advanced Examples 5 5 nie eere er ha De ERE De e epe e ep ee de 270 FAQ Prequentry Asked Questions iiec ero rr PEE aa ia esa Cosa X i E ERREEXEEPI EE SPEE EEE OS 272 BAO Te Installation RERO c HE 272 EAQ 2 Run Timme Problems ome rte etre dre e teas IRR IET 273 EAQ 3 Geometry inest eleme yep vue a der Feci seres py ecce t cer etre ses S si 273 EAQ 4 Tracks and steps vives onte ER FR POE HR S SA ERES E PERRA k a PERSE ESSERE 274 EAQ 5 Physics dnd Cuts coetui eene T RA Eee ERES ss A MEER EAE EE QUU 277 EAQ 6 Visualization 1 5 etra terae Taa a aa i dat ie gabe eve as 277 FAQ 7 User Support Policy 5 3 oreet wes kas gs esa eode ins ss Dov sis els ss sias 277 Appendix iode tess cR RR ER a Kas a K a a ia ss i a Ei 279 1 Tips for Program Compilation 2 0 0 cece kaka kaka HII em ene mee rre herren 279 MOUSE EN 279 1 2 Unix Linux Bb oc sess ss a is sa as ai chs teste i ese ceva Aa os sa a ia ss 279 1 3 Windows MS Visual GHE i iere sekas kas s ba sae FERE RR ees tees seh ae ERR sa 280 1 4 MacOS X BE Lai ia sis Boi is Ia sea Sigi simas r Ape eM e sia Ie as 280 2 Hi StO SPAMMING 2 orte bte eere ii Sis Das Ga o aa a a a pa eee en S 28
272. eflectivity off a metal surface can also be calculated by way of a complex index of refraction Instead of stor ing the REFLECTIVITY directly the user stores the real part REALRINDEX and the imaginary part IMAGI NARYRINDEX as a function of photon energy separately in the G4MaterialPropertyTable Geant4 then calcu lates the reflectivity depending on the incident angle photon energy degree of TE and TM polarization and this complex refractive index The program defaults to the GLISUR model and polished surface finish when no specific model and sur face finish is specified by the user In the case of a dielectric metal interface or when the GLISUR model is specified the only surface finish options available are polished or ground For dielectric metal surfaces the G4OpBoundaryProcess also defaults to unit reflectivity and zero detection efficiency In cases where the user specifies the UNIFIED model but does not otherwise specify the model reflection probability constants the default becomes Lambertian reflection 5 2 6 Parameterization In this section we describe how to use the parameterization or fast simulation facilities of GEANT4 Examples are provided in the examples novice N05 directory 5 2 6 1 Generalities The Geant4 parameterization facilities allow you to shortcut the detailed tracking in a given volume and for given particle types in order for you to provide your own implementation of the physics and of the detector res
273. egion is recognized by the fact that its associated G4FastSimulationManager retains a non empty list of placements The G4GlobalFastSimulationManager will then use both those placements and the IsApplicable methods of the models attached to the G4FastSimulationManager objects to build the flavour dependant ghost geometries Then at the beginning of the tracking of a particle the appropriate ghost world if any will be selected The steps required to build one ghost G4Region are 1 built the ghost G4Region myGhostRegion 2 build the root G4Logical Volume myGhostLogical set it to myGhostRegion 3 build a G4FastSimulationManager object myGhostFSManager giving myGhostRegion as argument of the constructor 4 give to the G4FastSimulationManager the placement of the myGhostLogical by invoking for the G4FastSimulationManager method AddGhostPlacement G4RotationMatrix const G4ThreeVectors amp or AddGhostPlacement G4Transform3D where the rotation matrix and translation vector of the 3 D transformation describe the placement relative to the ghost world coordinates 5 build your G4VFastSimulationModel objects and add them to the myGhostFSManager The IsApplicable methods of your models will be used by the G4GlobalFastSimulationManager to build the ghost geometries corresponding to a given particle type 6 Invoke the G4GlobalFastSimulationManager method 168 Tracking and Physics G4GlobalFastSimulationManager
274. elmportance G4double importance const G4VPhysicalVolume amp G4int aRepNum 0 G4double GetImportance const G4VPhysicalVolume amp G4int aRepNum 0 const piaikvakes ee 51 Toolkit Fundamentals The member function AddImportanceGeometryCell enters a cell and an importance value into the im portance store The importance values may be returned either according to a physical volume and a replica num ber or according to a G4GeometryCe11 The user must be aware of the interpretation of assigning importance values to a cell If scoring is also implemented then this is attached to logical volumes in which case the physical volume and replica number method should be used for assigning importance values See examples extend ed biasing B01 and B02 for examples of this Note e An importance value must be assigned to every cell The different cases Cell is not in store Not filling a certain cell in the store will cause an exception Importance value zero Tracks of the chosen particle type will be killed importance values 0 Normal allowed values Importance value smaller zero Not allowed 3 7 1 4 The Importance Sampling Algorithm Importance sampling supports using a customized importance sampling algorithm To this end the sampler inter face G4VSampler may be given a pointer to the interface G4VImportanceAlgorithm class G4VImportanceAlgorithm PUBLICI G4VImportanceAlgorithn v
275. er 5 8 2 Trajectory state The user has to provide the particle trajectory state at the initial point To do this it has to create an object of one of the children classes of G4ErrorTrajState providing Particle type 180 Tracking and Physics Position Momentum Trajectory error matrix G4ErrorTrajState const G4String amp partType const G4Point3D amp pos const G4Vector3D amp mom const G4ErrorTrajErr amp errmat G4ErrorTrajErr 5 0 A particle trajectory is characterized by five independent variables as a function of one parameter e g the path length Among the five variables one is related to the curvature to the absolute value of the momentum two are related to the direction of the particle and the other two are related to the spatial location There are two possible representations of these five parameters in the error propagator package as a free trajectory state class G4ErrorTrajStateFree or as a trajectory state on a surface class G4ErrorTrajStateonSurface 5 8 2 1 Free trajectory state In the free trajectory state representation the five trajectory parameters are G4double fInvP G4double fLambda G4double fPhi G4double fYPerp G4double fZPerp where InvP is the inverse of the momentum Lambda and fPhi are the dip and azimuthal angles related to the momentum components in the following way p_x p cos lambda cos phi p y p cos lambda sin phi p_z p sin lam
276. er virtual void PrepareImportanceSampling G4VIStore istore const G4VImportanceAlgorithm ialg 0 0 virtual void PrepareWeightRoulett G4double wsurvive 0 5 G4double wlimit 0 25 G4double isource 1 0 virtual void PrepareWeightWindow G4VWeightWindowStore wwstore G4VWeightWindowAlgorithm wwAlg 0 G4PlaceOfAction placeOfAction onBoundary 0 virtual void Configure 0 virtual void ClearSampling 0 virtual G4bool IsConfigured const 0 The methods for setting up the desired combination need specific information e Importance sampling message PrepareImportanceSampling with a G4VIStore and optionally a G4VImportanceAlgorithm Weight window message PrepareWeightWindow with the arguments wwstore a G4VWeightWindowStore for retrieving the lower weight bounds for the energy space cells e wwAlg a G4VWeightWindowAlgorithm if a customized algorithm should be used e placeOfAction a G4P laceOfAction specifying where to perform the biasing Weight roulette message PrepareWeightRoulett with the optional parameters e wsurvive survival weight wlimit minimal allowed value of weight source importance cell importance e isource importance of the source cell Each object of a sampler class is responsible for one particle type The particle type is given to the constructor of the sampler classes via the particle type name e g neutron Depending on the specific purpose the Con figure o
277. er exN03Vis9 mac A basic macro for visualization of detector geometry and events using OpenGL for Windows exN03Vis10 mac A basic macro for visualization of detector geometry and events using OpenInventor on Windows exN03Vis11 mac A basic macro for visualization of detector geometry and events using OpenGL in Stored Motif mode and DAWN exN03Vis12 mac and exNO3Vis12 loop 230 Visualization A basic macro for demonstrating time slicing e exNO3Vis13 mac and exN03Vis3 loop Time development of an electrmagnetic shower e exN03Tree0 mac A macro to demonstrate ASCII tree e exN03Tree1 mac A macro to demonstrate GAG tree 8 5 Controlling Visualization from Compiled Code While a Geant4 simulation is running visualization can be performed without user intervention This is accomplished by calling methods of the Visualization Manager from methods of the user action classes G4UserRunAction and G4UserEventAction for example In this section methods of the class G4VVisManager which is part of the graphics_reps category are described and examples of their use are given 8 5 1 G4VVisManager The Visualization Manager is implemented by classes G4VisManager and G4VisExecutive See Section 8 2 Mak ing a Visualization Executable In order that your Geant4 be compilable either with or without the visualization category you should not use these classes directly in your C source code other than in the main funct
278. er PREPS ka bene ERES E SERES PER ed 209 8 2 5 How to Write the main Function lt a aaa HH meme aa aaa aaa 209 8 3 The Visualization Drivers iet satis ai pa sa e ka i ERES y a T 211 8 3 1 Availability of drivers on the supported systems sese 211 8 322 OpenGL iss sis sonus ais aaa ee Aa a oases ais eere eR ds ses Megas e sae RE ER ose 211 8 3535 OpenInventOr 4 etu seima Is ks I erster reet bes a a eT EEEE ia 212 8 3 4 HepRepEile sau rte ttt bett ete E D Et sa iii te ia a i e axe 212 8 35 HepRepXML toe cess es E a iota e Ee epe sai eee 214 8 3 0 DAWN isse re Rr erede e re Re e RE RR RR ERE EIER 215 8 3 7 Remote Visualization with the DAWN Network Driver eee 215 8 3 8 VRML iter tete eth Pure eee reb Ere pt t EROR E EY ERE Ree ease aah 217 8 3 9 Ray Tracer 5 eet Eee REESE ava PIER es ERR PNE PQeRr E 218 8 3 10 Visualization of detector geometry tree 219 8 3 LI GAG Tree ud tiksi i sg pink La jsi Eris inda Ia is RB Ip Ene 220 8 3 12 XML Tree tee siais Ii Pas tiber certe is ka IRE bs i a S EEE 221 8 4 Controlling Visualization from Commands lt aa sess eene 222 8 4 1 Scene scene handler and viewer kaka kaka asas asas aaa aaa aaa rennen 222 8 4 2 Create a scene handler and a viewer vis open command sese 223 8 4 3 Create an empty scene vis scene create command sese 223 vil Geant4 User s Guide for Application Develope
279. er addCutawayPlane 0 0 vis viewer addCutawayPlane 0 1 0 9 wa 3 0 00m 0 0 and for more that one plane you can change the mode to a add or equivalently union default or b multiply or equivalently intersection vis viewer set cutawayMode multiply To de activate vis viewer clearCutawayPlanes OpenGL supports this feature 8 4 16 Tutorial macros The followings are tutorial macros in the directory examples novice N03 visTutor exN03 VisO mac A basic macro for visualization of detector geometry and events using OpenGL in Immediate mode and DAWN exN03Vis1 mac A basic macro for visualization of detector geometry using OpenGL in Stored mode and DAWN exN03Vis2 mac A basic macro for visualization of detector geometry and events using OpenGL in Stored mode and DAWN exN03Vis3 mac A basic macro for demonstrating various drawing styles using OpenGL in Immediate mode and DAWN exN03Vis4 mac An example of visualizing specific logical volumes using OpenGL in Immediate mode and DAWN exN03Vis5 mac A basic macro for visualization of detector geometry and events using OpenInventor on Unix exN03Vis6 mac A basic macro for visualization of detector geometry and events using VRML exN03Vis7 mac A macro to demonstrate batch visualization to generate PostScript files with the DAWNFILE driver exN03Vis8 mac A macro to demonstrate creation of a multi page PostScript file with the DAWNFILE driv
280. er of steps of positron are scored Example 4 22 UI commands to define a scoring mesh and scorers define scoring mesh score create boxMesh boxMesh 1 score mesh boxSize 100 100 100 cm score mesh nBin 30 30 30 define scorers and filters score quantity energyDeposit eDep Score quantity nOfStep nOfStepGamma score filter particle gammaFilter gamma Score quantity nOfStep nOfStepEMinus score filter particle eMinusFilter e score guantity nOfStep nOfStepEPlus score filter particle ePlusFilter e score close 4 8 3 Drawing scores Once scores are filled the user can visualize the scores The score is drawn on top of the mass geometry with the current visualization settings 133 Detector Definition and Response viewer 0 OpenGLimmediateX x Figure 4 10 Drawing scores in slices left and projection right By default entries are linearly mapped to colors gray blue green red This color mapping is implemented in G4DefaultLinearColorMap class and registered to G4ScoringManager with the color map name defaultLinearColorMap The user may alternate color map by implementing his her own color map class derived from G4VScoreColorMap and register it to G4ScoringManager Then for each draw command the user can specify the color map of his her own 4 8 4 Writing scores to a fil e The user may dump a score in a
281. eraction with a water target Different aspects of beam target interaction are included 9 2 1 11 Medical Applications DICOM geometry set up using the Geant4 interface to the DICOM image format GammaTherapy gamma radiation field formation in water phantom by electron beam hitting different targets fanoCavity dose deposition in an ionization chamber by a monoenergetic photon beam fanoCavity2 dose deposition in an ionization chamber by an extended one dimensional monoenergetic elec tron source 9 2 1 12 Optical Photons General ReadMe LXe optical photons in a liquid xenon scintillator 9 2 1 13 Parallel Computing General ReadMe ExDiane example of a medical application run in a distributed environment using the DIANE framework 269 Examples MPI interface and examples of applications parallelized with different MPI compliant libraries such as LAM MPI MPICH2 OpenMPI etc ParGeant4 set of examples derived from novice using parallelism at event level with the TopC application 9 2 1 14 Persistency General ReadMe POI storing calorimeter hits using reflection mechanism with Root e P02 storing detector description using reflection mechanism with Root 9 2 1 15 Polarisation e Pol01 interaction of polarized beam e g circularly polarized photons with polarized target 9 2 1 16 Radioactive Decay General ReadMe decays of radioactive isotopes as well as induced radioactivi
282. erator it does not mean the value is zero but that the provided key does not exist The value itself is accessible with an astarisk It is advised to check the validity of the returned pointer before accessing the value G4THitsMap also has a operator in order to accumulate event data into run data Example 4 16 shows the use of G4THitsMap Example 4 16 An example of accessing to G4THitsMap objects include ExN07Run hh include G4Event hh include G4HCofThisEvent hh include G4SDManager hh EXNO7Run ExNO7Run G4String detName 6 Calor A abs Calor A gap Calor B abs Calor B gap dto GESTOS GadKo C dapi i G4String primNameSum 6 eDep nGamma nElectron nPositron trackLength nStep G4String primNameMin 3 minEkinGamma minEkinElectron minEkinPositron G4SDManager SDMan G4SDManager GetSDMpointer G4String fullName for size t i 0 i lt 6 i for size t j 0 3 lt 6 j fullName detName i primNameSum j colIDSum i j SDMan gt GetCollectionID fullName for size t k 0 k lt 3 k fullName detName i primNameMin k colIDMin i k SDMan GetCollectionID fullName void ExN07Run RecordEvent const G4Event evt G4HCofThisEvent HCE evt gt GetHCofThisEvent if HCE return numberOfEvent Kon Size t ISO 61 for size t j 0 3 lt 6 j G4THitsMap lt G4double gt evtMap G4THitsMap lt G4double gt HCE gt GetH
283. ere events G4Event anEventAllocator tracks G4Track alrackAllocator stacked tracks iG4Stackedtrack e astackedIrackAl locaton primary particles G4PrimaryParticle aPrimaryParticleAllocator primary vertices G4PrimaryVertex aPrimaryVertexAllocator decay products G4DecayProducts aDecayProductsAllocator digits collections of an event G4DCofThisEvent anDCoTHAllocator digits collections G4DigiCollection aDCAllocator hits collections of an event G4HCofThisEvent anHCoTHAllocator hits collections G4HitsCollection anHCAllocator trajectories G4Trajectory aTrajectoryAllocator trajectory points G4TrajectoryPoint aTrajectoryPointAllocator trajectory containers G4TrajectoryContainer aTrajectoryContainerAllocator navigation levels G4NavigationLevel aNavigationLevelAllocator navigation level nodes G4NavigationLevelRep aNavigLevelRepAllocator reference counted handles G4ReferenceCountedHandle lt X gt aRCHAllocator counted objects G4CountedObject X aCountedObjectAllocator HEPEvt primary particles G4HEPEvtParticle aHEPEvtParticleAllocator electron occupancy objects G4ElectronOccupancy aElectronOccupancyAllocator rich trajectories G4RichTrajectory aRichTrajectoryAllocator rich trajectory points G4RichTrajectoryPoint aRichTrajectoryPointAllocator smooth trajectories G4SmoothTrajectory aSmoothTrajectoryAllocator
284. ergy Electromagnetic processes available in Geant4 Further informa tion is available in the homepage of the Geant4 Low Energy Electromagnetic Physics Working Group The physics content of these processes is documented in Geant4 Physics Reference Manual and in other papers Photon processes Compton scattering class G4LowEnergyCompton Polarized Compton scattering class G4LowEnergyPolarizedCompton Rayleigh scattering class G4LowEnergyRayleigh Gamma conversion also called pair production class G4LowEnergyGammaConversion Photo electric effect classG4LowEnergyPhotoElectric Electron processes Bremsstrahlung class G4LowEnergyBremsstrahlung Ionisation and delta ray production class G4LowEnergylonisation Hadron and ion processes e onisation and delta ray production class G4hLowEnergylonisation An example of the registration of these processes in a physics list is given in Example 5 2 Example 5 2 Registration of electromagnetic low energy electron photon processes void LowEnPhysicsList ConstructEM theParticlelterator gt reset while theParticleIterator G4ParticleDefinition particle theParticleIterator value G4ProcessManager pmanager particle GetProcessManager G4String particleName particle GetParticleName if particleName gamma theLEPhotoElectric theLECompton theLEGammaConversion theLERayleigh G4 G4 G4 G4 new new new new LowEnergyPhotoElectric
285. eringToLast theParallelWorldScoringProcess idxPostStep At the end of processing an event all hits collections made for the parallel world are stored in G4HCofThisEvent as well as those for the mass geometry 4 8 Command based scoring Notice As of Geant4 release 9 1 this functionality of command based scoring is still in alpha release and func tionality offered is preliminary We do not guarantee the correctness of the code Also we may change any of the commands methods in the near future release We appreciate your feedback 4 8 1 Command based scoring This new command based scoring utilizes the parallel world described in the previous section With UI interactive commands the user can define A parallel world for scoring and three dimensional mesh in it e Arbitrary number of physics quantities to be scored and filters After scoring i e a run the user can visualize the score and dump scores into a file All available UI commands are listed in List of built in commands For the time being of the alpha release this command based scoring is an optional functional ity and the user has to explicity define its use in his her main To do this the method G4ScoringManager GetScoringManager must be invoked right after the instantiation of G4RunManager Example 4 21 A user main to use the command based scoring include G4RunManager hh include G4ScoringManager hh int main int argc char argv
286. es fast navigation Alternative implementations taking into account the regular structure of such geometries in navigation are under study Divisions of Volumes Divisions in Geant4 are implemented as a specialized type of parameterised volumes They serve to divide a volume into identical copies along one of its axes providing the possibility to define an offset and without the limitation that the daugthers have to fill the mother volume as it is the case for the replicas In the case for example of a tube divided along its radial axis the copies are not strictly identical but have increasing radii although their widths are constant To divide a volume it will be necessary to provide 1 the axis of division and 2 either the number of divisions so that the width of each division will be automatically calculated or the division width so that the number of divisions will be automatically calculated to fill as much of the mother as possible or both the number of divisions and the division width this is especially designed for the case where the copies do not fully fill the mother An offset can be defined so that the first copy will start at some distance from the mother wall The dividing copies will be then distributed to occupy the rest of the volume There are three constructors corresponding to the three input possibilities described above Giving only the number of divisions G4PVDivision const G4String amp p
287. es related to cells In order to do importance sampling the user has to create an object e g of class G4I Store of type G4VIStore The samplers may be given a G4VIStore The user fills the store with cells and their importance values Animportance store has to be constructed with a reference to the world volume of the geometry used for importance sampling This may be the world volume of the mass or of a parallel geometry Importance stores derive from the interface GaVIStore class G4VIStore public G4VIStore virtual G4VIStore virtual G4double GetImportance const G4GeometryCell amp gCell virtual G4bool IsKnown const G4GeometryCell amp gCell const virtual const G4VPhysicalVolume amp GetWorldVolume const 0 A concrete implementation of an importance store is provided by the class G4VStore The public part of the class is class G4IStore public G4VIStore public explicit G4IStore const G4VPhysicalVolume amp worldvolume virtual G4IStore virtual G4double GetImportance const G4GeometryCell amp gCell const virtual G4bool IsKnown const G4GeometryCell amp gCell const virtual const G4VPhysicalVolume amp GetWorldVolume const void AddImportanceGeometryCell G4double importance const G4GeometryCell amp gCell void AddImportanceGeometryCell G4double importance const G4VPhysicalVolume 4 G4int aRepNum 0 void Changelmportance G4double importance const G4GeometryCell amp gCell void Chang
288. ess must implement virtual methods of G4VProcess which describe the interaction Dolt and determine when an interaction should occur GPIL In order to accommodate various types of interactions G4VProcess provides three DoIt methods 139 Tracking and Physics G4vParticleChange AlongStepDoIt const G4Track amp track const G4Step amp step Data This method is invoked while G4SteppingManager is transporting a particle through one step The correspond ing AlongStepDoLIt for each defined process is applied for every step regardless of which process produces the minimum step length Each resulting change to the track information is recorded and accumulated in G4Step After all processes have been invoked changes due to AlongStepDolIt are applied to G4Track including the particle relocation and the safety update Note that after the invocation of AlongStepDolIt the endpoint of the G4Track object is in a new volume if the step was limited by a geometric boundary In order to obtain information about the old volume G4Step must be accessed since it contains information about both endpoints of a step e G4vParticleChange PostStepDoIt const G4Track amp track const G4Step amp step Data This method is invoked at the end point of a step only if its process has produced the minimum step length or if the process is forced to occur G4Track will be updated after each invocation of Post StepDoIt in contrast to the AlongStepDoIt metho
289. essful the result is a pair of physical volumes where the second physical volume is a replica in a reflected mother The method Divide creates divisions in the given mother If successful the result is a pair of physical volumes where the second physical volume is a division in a reflected mother There exists also two more variants of this method which may specify or not width or number of divisions Notes In order to reflect hierarchies containing divided volumes it is necessary to explicite ly instantiate a concrete division factory before applying the actual reflection ie G4PVDivisionFactory GetInstance Reflection of generic parameterised volumes is not possible yet 91 Detector Definition and Response Example 4 8 An example of usage of the GGReflectionFactory class include G4ReflectionFactory hh Calor placement with rotation G4double calThickness 100 cm G4double Xpos calThickness 1 5 G4RotationMatrix rotD3 new G4RotationMatrix rotD3 gt rotateY 10 deg G4VPhysicalVolume physiCalor new G4PVPlacement rotD3 rotation G4ThreeVector Xpos 0 0 at Xpos 0 0 logicCalor its logical volume defined elsewhere Calorimeter its name lagichaild its mother volume defined elsewhere false no boolean operation 0 copy number Calor reflection with rotation 727 G4Translate3D translation Xpos 0 0 G4Transform3D rotation G4Rotate3D
290. etectorConstruction runManager gt SetUserInitialization new ExN01PhysicsList set mandatory user action class runManager gt SetUserAction new ExNO1PrimaryGeneratorAction initialize G4 kernel runManager gt initialize get the pointer to the UI manager and set verbosities G4UImanager UI G4UImanager GetUIpointer UI gt ApplyCommand run verbose 1 UI gt ApplyCommand event verbose 1 UI gt ApplyCommand tracking verbose 1 start a run int numberOfEvent 3 runManager gt BeamOn numberOfEvent job termination delete runManager return 0 The main method is implemented by two toolkit classes G4RunManager and G4UImanager and three class es ExNO1DetectorConstruction ExNO1PhysicsList and ExNO1PrimaryGeneratorAction which are derived from toolkit classes Each of these are explained in the following sections 2 1 2 G4RunManager The first thing main must do is create an instance of the G4RunManager class This is the only manager class in the Geant4 kernel which should be explicitly constructed in the user s main It controls the flow of the program and manages the event loop s within a run When G4RunManager is created the other major manager classes are also created They are deleted automatically when G4RunManager is deleted The run manager is also responsible for managing initialization procedures including methods in the user initialization classes Through these the r
291. etup CreateTouchableHistory Creates a G4TouchableHistory object for which the caller has deletion responsibility The touchable volume is the volume returned by the last Locate operation The object includes a copy of the current Naviga tionHistory enabling the efficient relocation of points in close to the current volume in the hierarchy As stated previously the navigator makes use of utility classes to perform location and step computation functions The different navigation utilities manipulate the G4NavigationHistory object In LocateGlobalPointAndSetup the process of locating a point breaks down into three main stages optimisation determination that the point is contained with a subtree mother and daughters and determination of the actual containing daughter The latter two can be thought of as scanning first up the hierarchy until a volume that is guaranteed to contain the point is found and then scanning down until the actual volume that contains the point is found In ComputeStep three types of computation are treated depending on the current containing volume The volume contains normal placement daughters or none The volume contains a single parameterised volume object representing many volumes The volume is a replica and contains normal placement daughters 4 1 8 2 Using the navigator to locate points More than one navigator objects can be created inside an application these navigators can
292. evel and a member function to move the level in this stack Then calling the above member functions for another level the information for that level can be retrieved The top of the history tree is by convention the world volume 6 GetHistoryDepth gives the depth of the history tree 7 MoveUpHistory num moves the current pointer inside the touchable to point num levels up the history tree Thus e g calling it with num 1 will cause the internal pointer to move to the mother of the current volume WARNING this function changes the state of the touchable and can cause errors in tracking if applied to Pre Post step touchables 87 Detector Definition and Response These methods are valid only for the touchable history type as specified also below An update method with different arguments is available so that the information in a touchable can be updated 8 UpdateYourself vol history takes a physical volume pointer and can additionally take a Navi gationHistory pointer 4 1 5 3 Touchable history holds stack of geometry data As shown in Sections Section 4 1 3 and Section 4 1 4 a logical volume represents unpositioned detector ele ments and a physical volume can represent multiple detector elements On the other hand touchables provide a unique identification for a detector element In particular the Geant4 transportation process and the tracking system exploit touchables as implemented in G4TouchableHistory Th
293. ew G4SDParticleFilter filterName G4SDParticleFilter positronFilter new G4SDParticleFilter filterName positronFilter particleName et G4SDParticleFilter epFilter new G4SDParticleFilter filterName epFilter epFilter add particleName e epFilter gt add particleName e electronrilter part iclename e 7 for G4int i 0 i1 lt 3 i for G4int j 0 j lt 2 j Loop counter j 0 absorber T 1 gap G4String detName calName i aie 3535 detName abs else detName gap G4MultiFunctionalDetector det new G4MultiFunctionalDetector detName The second argument in each primitive means the level of geometrical hierarchy the copy number of that level is used as the key of the G4THitsMap For absorber j 0 the copy number of its own physical volume is used For gap j 1 the copy number of its mother physical volume is used since there is only one physical volume of gap is placed with respect to its mother G4vPrimitiveScorer primitive primitive new G4PSEnergyDeposit eDep j det gt RegisterPrimitive primitive primitive new G4PSNofSecondary nGamma j primitive gt SetFilter gammaFilter det gt RegisterPrimitive primitive primitive new G4PSNofSecondary nElectron j primitive gt SetFilter electronFilter det gt RegisterPrimitive primitive primitive new G4PSNofSecondary nPositron j primitive gt
294. ew requirement will trigger a cycle of analysis design implementation testing and documentation which may involve different working groups Any new software or enhancement which will become a part of Geant4 must be agreed upon by the TSB which is charged with ensuring the consistency of the entire toolkit Is there a regular user meeting which I should attend There is only one Geant4 workshop per year However many experiments and institutes in the Geant4 collaboration organize their own regular and or special Geant4 user workshops Where can I find solutions to particular problems as well as general user support Solutions and tips for solving practical problems can be found on the current FAQ page General and specific user support information is available at the User Support page 278 Appendix Appendix 1 Tips for Program Compilation This section is dedicated to illustrate and justify some of the options used and fixed by default in the compilation of the Geant4 toolkit It is also meant to be a simple guide for the user installer to avoid or overcome problems which may occur on some compilers Solutions proposed here are based on the experience gained while porting the Geant4 code to different architectures compilers and are specific to the OS s and compiler s version valid at the current time of writing of this manual It s well known that each compiler adopts its own internal techniques to produce the object code which
295. ewParameters By default square and circle are supported in Geant4 Visualization The former is described with class G4Square and the latter with class G4Circle Marker Type Class Name circle G4Circle right square G4Square These classes are inherited from class G4VMarker They have constructors as follows 1 gt gt gt gt Constructors of G4Circle and G4Sguare G4Circle G4Circle const G4Point3D amp pos G4Square G4Square const G4Point3D amp pos Access functions of class G4VMarker are summarized below Access functions of markers Example 8 6 shows the access functions inherited from the base class G4VMarker Example 8 6 The access functions inherited from the base class G4V Marker Jd m Set functions of G4VMarker void G4VMarker SetPosition const G4Point3D amp void G4VMarker SetWorldSize G4double void G4VMarker SetWorldDiameter G4double void G4VMarker SetWorldRadius G4double void G4VMarker SetScreenSize G4double void G4VMarker SetScreenDiameter G4double void G4VMarker SetScreenRadius G4double void G4VMarker SetFillStyle FillStyle Note enum G4VMarker FillStyle noFill hashed filled fi Get functions of G4VMarker G4Point3D G4VMarker GetPosition const G4double G4VMarker GetWorldSize const G4double G4VMarker GetWorldDiameter const G4double G4VMarker GetWorldRadius const G4double G4VMarker GetScreenSize con
296. ewers each with its own set of parameters with easy switching from one scene to another But for the most common case of just having one scene and one viewer many steps are handled implicitly for you 8 4 2 Create a scene handler and a viewer vis open command Command vis open creates a scene handler and a viewer which corresponds to Step 1 Command vis open driver_tag_name Argument A name of a mode of an available visualization driver Action Create a visualization driver i e a set of a scene hander and a viewer Example Create the OpenGL Xlib driver with its immediate mode Idle vis open OGLIX Additional notes For immediate viewers such as OGLIX your geometry will immediately be rendered in the new GL window How to list available driver tag name Idle help vis open or Idle help vis sceneHandler create The list is for example displayed as follows Candidates DAWNFILE OGLIX OGLSX For additional options see the Control UICommands section of this user guide 8 4 3 Create an empty scene vis scene create com mand Command vis scene create creates an empty scene which corresponds to Step 2 Command vis scene create scene name Argument A name for this scene Created for you if you don t specify one 8 4 4 Visualization of a physical volume vis drawVol ume command Command vis drawVolume adds a physical volume to the scene It also does some of the othe
297. f OpenInventor on Windows systems G4VIS BUILD DAWN DRIVER Specifies to build kernel library for visualization including the driver for DAWN G4VIS USE DAWN Specifies to use DAWN as a possible graphics renderer in the application to be built G4DAWN HOST NAME To specify the hostname for use with the DAWN network driver 285 Appendix G4VIS_NONE If specified no visualization drivers will be built or used Hadronic physics specific G4NEUTRONHP_USE_ONLY_PHOTONEVAPORATION When using high precision neutron code user may choose to force the use of Photon Evaporation model instead of using the neutron capture final state data G4NEUTRONHP_SKIP_MISSING_ISOTOPES User can force high precison neutron code to use only exact isotope data files instead of allowing nearby isotope files to be used If the exact file is not available the cross section will be set to zero and a warning message will be printed G4NEUTRONHP_NEGLECT_DOPPLER Sets neglecting doppler broadening mode for boosting performance GDML zlib and g3tog4 modules G4LIB_BUILD_GDML If set triggers compilation of a plugin module gdm1 for allowing import export of detector description setups geometrical volumes solids materials etc By default the flag is not set if set the path to the installation of XercesC package must be specified through the variable SXERCESCROOT G4LIB_USE_GDML Specifies to use the gdm1 module The flag is automati
298. f materials and mixtures G4Box with G4PVPlacement and G4PVReplica Dynamic changing of size position orientation and number of volumes G4Region for each calorimeter tower 266 Examples G4VPrimitiveScorer and G4VSDFilter visualization ExN07DetectorMessenger header file source file derived from G4UIMessenger definition of example specific geometry commands ExN07PhysicsList header file source file derived from G4VUserPhysicsList difine all types of particles define standard EM and decay processes production thresholds for each region ExN07PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction construction of G4ParticleGun primary event generation via particle gun ExN07RunAction header file source file derived from G4UserRunAction constructing ExNO7Run class object print out a run summary with ExNO7Run class object ExN07Run header file source file derived from G4Run uses G4THitsMap template class to accumulate physics quantities extracts event data from G4Event and add up to run data 9 2 Extended Examples 9 2 1 Extended Example Summary Geant4 extended examples serve three purposes testing and validation of processes and tracking demonstration of Geant4 tools and extending the functionality of Geant4 The code for these examples is maintained as part of the categories to which they belong Links to
299. fa sampler will set up specialized processes derived from G4VProcess for transportation in the parallel geometry importance sampling and weight roulette for the given particle type When Configure is invoked the sampler places the processes in the correct order independent of the order in which user invoked the Prepare methods Note The Prepare functions may each only be invoked once To configure the sampling the function Configure must be called after the G RunManager has been initialized and the PhysicsList has been instantiated The interface and framework are demonstrated in the examples extended biasing directory with the main changes being to the G4GeometrySampler class and the fact that in the parallel case the WorldVolume is a copy of the Mass World The parallel geometry now has to inherit from G4VUserParallelWorld which also has the GetWorld method in order to retrieve a copy of the mass geometry WorldVolume class BO2ImportanceDetectorConstruction public G4VUserParallelWorld ghostWorld GetWorld The constructor for G4GeometrySampler takes a pointer to the physical world volume and the particle type name e g neutron as arguments In a single mass geometry the sampler is created as follows G4GeometrySampler mgs detector GetWorldVolume neutron mgs SetParallel false Whilst the following lines of code are required in order to set up the sampler for the parallel geometry case G4
300. fault value is NONE which means that no viewer is invoked and only the file g4 wr1 is generated Remote Visualization with the VRML Network Driver Visualization in Geant4 is considered to be remote when it is performed on a machine other than the Geant4 host Some of the visualization drivers support this feature Usually the visualization host is your local host while the Geant4 host is a remote host where you log in for example with the telnet command This enables distributed processing of Geant4 visualization avoiding the transfer of large amounts of visualization data to your terminal display via the network In order to perform remote visualization with the VRML Network driver the following must be installed on your local host beforehand 1 a VRML viewer 2 the Java application g4vrmlview The Java application g4vrmlview is included as part of the Geant4 package and is located at source visualization VRML g4vrmlview Installation instructions for g4vrmlview can be found in the README file there or on the WWW page below The following steps realize remote Geant4 visualization displayed with your local VRML browser 1 Invoke the g4vrmlview on your local host giving a VRML viewer name as its argument Local Host java g4vrmlview VRML viewer name For example if you want to use the Netscape browser as your VRML viewer execute g4vrmlviewas follows 217 Visualization Local_Host gt java g4vrmlview
301. fic to my simulation application or ask for first aid help who can I contact Every institute and experiment participating in Geant4 has a G4 Technical Steering Board TSB represen tative who may be contacted for help with problems relating to simulations Please contact the TSB repre sentative closest to your project or to your laboratory To find out who your TSB representative is go to G4 Technical Board You may also post your question in the Geant4 HyperNews Forum If I find a bug or other problem with the code who should be informed A WWW interface available at Problem tracking system will forward the bug report to the person respon sible for the affected Geant4 domain The Geant4 web makes available a database of open incident reports tagging the ones already fixed and showing their status An acknowledgement of the bug report will be sent If I propose a fix who is responsible for approving it 277 Frequentry Asked Questions The responsible person is the working group coordinator of the domain in which the fix is to be applied This person is usually also a TSB member If the fix affects more than one domain the matter will be addressed by the TSB To whom should I send a proposal for an improvement in Geant4 functionality Any new requirement should be submitted via the automatic web system It will be discussed at the Geant4 TSB You may also ask your TSB representative to forward your requirement to the TSB A n
302. figure the environment for creating Geant4 executables available for Geant4 visualization This sample is shown only as an example it may NOT correspond to a specific platform configuration and does NOT apply in general for any specific setup Example 8 1 Part of a sample cshrc setup file for the Linux platform HHH FE E FE HE AE FE FE HE FE FE EE FE AE HE AE FE FE HE FE FE FE FE FE AE EH HEE HH RHE HE HH FE E E E HH EE HEE E Main Environment Variables for GEANT4 with Visualization FE EFE FE AEE FE AE FE FE HE FE FE E FE FE E HE AE FE FE AE FE FE E FE FE AE E FE AE FE TE AE FE FE E FE FE E FE TE AE FE EE TE E E E E E E EEE EEE Platform setenv G4SYSTEM Linux g CLHEP base directory setenv CLHEP_BASE_DIR opt local OpenGL base directory setenv OGLHOME usr X11R6 GAVIS BUILD Td Incorporation of OpenGL Xlib and OpenGL Motif drivers Td into Geant4 libraries setenv G4VIS BUILD OPENGLX DRIVER 1 setenv G4VIS BUILD OPENGLXM DRIVER 1 GAVIS USE Td Incorporation of OpenGL Xlib and OpenGL Motif drivers Td into Geant4 executables setenv G4VIS USE OPENGLX E setenv G4VIS_USE_OPENGLXM 1b Viewer for DAWNFILE driver Default value is dawn You can change it to say david for volume overlapping tests setenv G4DAWNFILE_VIEWER david Viewer for VRMLFILE drivers setenv G4VRMLFILE_VIEWER vrmlview THHHHHEHEHEEE end 208 Visualization 8 2 4 Visualization Manager Visu
303. file derived from G4MagneticField solenoid and toroidal fields 262 Examples ExN04TrackerSD header file source file derived from G4VSensitiveDetector tracker type hit generation ExN04TrackerHit header file source file derived from G4VHit draw hit point ExN04CalorimeterSD header file source file derived from G4VSensitiveDetector calorimeter type hit generation ExN04CalorimeterHit header file source file derived from G4VHit draw physical volume with variable color ExN04MuonSD header file source file derived from G4VSensitiveDetector e Scintillator type hit generation ExN04MuonHit header file source file derived from G4VHit draw physical volume with variable color ExN04PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction e construction of G4HEPEvtInterface primary event generation with PYTHIA event ExN04EventAction header file source file store the initial seeds ExN04StackingAction header file source file derived from G4UserStackingAction e stage control and priority control 263 Examples event abortion ExN04StackingActionMessenger header file source file derived from G4UImessenger define abortion conditions ExN04TrackingAction header file source file derived from G4UserTrackingAction select trajectories select secondaries 9 1 6 Ex
304. files are Driver File type DAWNFILE prim then eps using dawn HepRepFile HepRepl HepRep HepRep2 OGLX eps RayTracer jpeg VRMLFILE vrml So far only DAWNFILE OGLX and RayTracer have been road tested Once in a standard format such as eps the convert program from ImageMagick can convert to ppm files suitable for mpeg2encode 8 10 1 OGLX Make a macro something like this control verbose 2 vis open OGLSX 600x600 0 0 vis drawVolume vis viewer reset vis viewer set style surface vis viewer set projection perspective 50 deg control alias phi 30 control loop movie loop theta 0 360 1 which invokes movie loop which is something like vis viewer set viewpointThetaPhi theta phi vis viewer zoom 1 005 vis ogl printEPS This produces lots of eps files Then make mpeg2encode parfile sh G4OpenGL eps Then edit mpeg2encode par to specify file type and size etc diff mpeg2encode par mpeg2encode par Wicd Ke ik JA inpuc picture rile Eormat qw SY Ui iene 5 9 fe enpu jepteiebwess er TESEO rmata OS AU VAL Sy deal AU lt horizontal_size lt vertical_size lt 8 aspect ratio information 1 sguare pel 2 4 3 600 horizontal size gt 600 vertical size pd aspect ratio information 1 square pel 2 4 3 yuv 2 ppm yuv 2 ppm sido VEDI c s SEO Cac slab Ral 47 253 Visualization Then convert
305. for dividing volumes are implemented using G4PVReplicas for shapes BOX TUBE TUBS PARA all axes CONE CONS axes 2 3 TRD1 TRD2 TRAP axis 3 PGON PCON axis 2 PARA axis 1 axis 2 3 for a special case GSPOSP is implemented via individual logical volumes for each instantiation GSROTM is implemented Reflections of hierachies based on plain CSG solids are implemented through the G3Division class 100 Detector Definition and Response Hits are not implemented Conversion of GEANT 3 21 magnetic field is currently not supported However the usage of magnetic field has to be turned on 4 1 11 Detecting Overlapping Volumes 4 1 11 1 The problem of overlapping volumes Volumes are often positioned within other volumes with the intent that one is fully contained within the other If however a volume extends beyond the boundaries of its mother volume it is defined as overlapping It may also be intended that volumes are positioned within the same mother volume such that they do not intersect one another When such volumes do intersect they are also defined as overlapping The problem of detecting overlaps between volumes is bounded by the complexity of the solid model description Hence it requires the same mathematical sophistication which is needed to describe the most complex solid topol ogy in general However a tunable accuracy can be obtained by approximating the solids via first and
306. for each viewer They are initialized with command vis viewer re set A similar pair of commands scale and scaleTo allow non uniform scaling i e zoom differently along different axes For details see the Control UICommands section of this user guide Command vis viewer set style style name Arguments Candidate values of the argument are wireframe and surface w and s also work Action Set a drawing style to wireframe or surface Example Set the drawing style to surface Idle vis viewer set style surface Additional notes The style of some geometry components may have been forced one way or the other through calls in compiled code The set style command will NOT override such force styles Drawing style should be set for each viewer The drawing style is initialized with command vis view er reset 8 4 10 Declare the end of visualization for flushing vis viewer flush command Command vis viewer flush 226 Visualization Action Declare the end of visualization for flushing Additional notes Command vis viewer flush should follow vis drawVolume vis specify etc in or der to complete visualization It corresponds to Step 7 The flush is done automatically after every run beamOn command unless you have non default values for vis scene endOfEventAction or vis scene endOfRunAction described above 8 4 11 End of Event Action and End of Run Action vi
307. fraction of total scintillation yield is given by the YIELDRATIO Scintillation may be simulated by specifying these empirical parameters for each material It is sufficient to specify in the user s DetectorConstruction class a relative spectral distribution as a function of photon energy for the scintillating material An example of this is shown in Example 5 7 Example 5 7 Specification of scintillation properties in DetectorConstruction const G4int NUMENTRIES 9 G4double Scnt PP NUMENTRIES 6 6 eV 6 7 eV 6 8 eV 6 9 eV TOCE oN VES EET G4double Scnt FAST NUMENTRIES 0 000134 0 004432 0 053991 0 241971 0 398942 0 000134 0 004432 0 053991 0 241971 G4double Scnt SLOW NUMENTRIES 0 000010 0 000020 0 000030 0 004000 0 008000 0 005000 0 020000 0 001000 0 000010 G4Material Sont G4MaterialPropertiesTable Scnt MPT new G4MaterialPropertiesTable Scnt_MPT gt AddProperty FASTCOMPONENT Scnt PP Scent FAST NUMENTRIES Scnt MPT AddProperty SLOWCOMPONENT Scnt PP Scnt_SLOW NUMENTRIES Scnt MPT AddConstProperty SCINTILLATIONYIELD 5000 MeV Scnt MPT AddConstProperty RESOLUTIONSCALE 2 0 Scnt MPT gt AddConstProperty FASTTIMECONSTANT eS iy Scnt MPT gt AddConstProperty SLOWTIMECONSTANT 10 ns Scnt MBT AddConNS CE 60PE tY T YTELDRATITOT OB Scnt gt SetMaterialPropertiesTable Scnt MPT 159 Tracking and Physics In cases where th
308. framework already forsees the possibility of passing a class with the users parameters GV FlashHomoShowerTuning to the GFlashHo moShowerParamterisation constructor The default parameters are the original Gflash parameters GFlashHomoShowerParameterisation G4Material aMat GVFlashHomoShowerTuning aPar 0 Now there is also a preliminary implemenation of a parameterization for sampling calorimeters The user must specify the active and passive material as well as the thickness of the active and passive layer The sampling structure of the calorimeter is taken into account by using an effective medium to compute the shower shape All material properties needed are calculated automatically If tuning is required the user can pass his own pa rameter set in the class GFlashSamplingShowerTuning Here the user can also set his calorimeter resolution All in all the constructor looks the following GFlashSamplingShowerParamterisation G4Material Matl G4Material Mat2 G4double d1 G4double d2 GVFlashSamplingShowerTuning aPar 0 An implementation of some tools that should help the user to tune the parameterization is forseen 5 2 7 Transportation Process To be delivered by J Apostolakis lt John Apostolakis cern ch gt 5 3 Particles 5 3 1 Basic concepts There are three levels of classes to describe particles in Geant4 G4ParticleDefinition defines a particle G4DynamicParticle describes a particle interactin
309. g to be visualized and pos is the 3D position at which the text is visualized Note that class G4Text also inherits G4VMarker Size of text is recognized as font size i e height of the text All the access functions defined for class G4VMarker mentioned above are available In addition the following access functions are available too Set functions of G4Text void G4Text SetText const G4String amp text void G4Text SetOffset double dx double dy a Get functions of G4Text G4String G4Text GetText const G4double G4Text GetxOffset const G4double G4Text GetYOffset const Method Set Text defines text to be visualized and Get Text returns the defined text Method Set Of set defines x horizontal and y vertical offsets in the screen coordinates By default both offsets are zero and the text starts from the 3D position given to the constructor or to the method G4VMarker SetPosition Offsets should be given with the same units as the one adopted for the size i e world size or screen size units Example 8 8 shows sample C source code to define text with the following properties Text Welcome to Geant4 Visualization Position 0 0 0 in the world coordinates Horizontal offset 10 pixels Vertical offset 20 pixels Colour blue default Example 8 8 An example of defining text JA C source codes An example of defining a visualizable text Pia Instantiation CAMHS te
310. g One Axis trapezoid twisted along one axis can be defined as follows G4TwistedTrap const G4String amp pName G4double twistedangle G4double pDxxl G4double pDxx2 G4double pDy G4double pDz G4TwistedTrap const G4String amp pName G4double twistedangle G4double pDz G4double pTheta G4double pPhi G4double pDyl G4double pDxl In the picture G4double pDx2 GHeewiele We Dx1 30 Dx2 40 Dyl 40 G4double pDx3 P B BOY r pDx3 10 pDx4 14 pDy2 16 69 Detector Definition and Response G4double G4double pDx4 pDz 60 pTheta 20 Degree puer pDphi 5 Degree pAlph 10 De gree twistedangle 30 Degr The first constructor of G4TwistedTrap produces a regular trapezoid twisted along the z axis where the caps of the trapezoid are of the same shape and size The second constructor produces a generic trapezoid with polar azimuthal and tilt angles The twist angle cannot be greater than 90 degrees twistedangle Twisted angle pDx1 Half x length at y pDy pDx2 Half x length at y pDy pDy Half y length pDz Half z length pTheta Polar angle of the line joining the centres of the faces at pDz pDyl Half y length at pDz pDx1 Half x length at pDz y pDy1 pDx2 Half x length at pDz y pDy1 pDy2 Half y length at pDz pDx3 Half x length at pDz y pDy2 pDx4 Half x length at pDz y pDy2 pAlph Angle with respect to the y axis from th
311. g with materials 170 Tracking and Physics G4Track describes a particle traveling in space and time G4ParticleDefinition aggregates information to characterize a particle s properties such as name mass spin life time and decay modes G4DynamicParticle aggregates information to describe the dynamics of particles such as energy momentum polarization and proper time as well as particle definition information G4Track includes all information necessary for tracking in a detector simulation such as time position and step as well as dynamic particle information G4Track has all the information necessary for tracking in Geant4 It includes position time and step as well as kinematics Details of G4Track will be described in Section 5 1 5 3 2 Definition of a particle There are a large number of elementary particles and nuclei Geant4 provides the G4ParticleDefinition class to represent particles and various particles such as the electron proton and gamma have their own classes derived from G4ParticleDefinition We do not need to make a class in Geant4 for every kind of particle in the world There are more than 100 types of particles defined in Geant4 by default Which particles should be included and how to implement them is determined according to the following criteria Of course the user can define any particles he wants Please see the User s Guide For ToolKit Developers 5 3 2 1 Particle List
312. ge software frameworks into which Geant4 has been incorporated already have their own visualization systems so Geant4 visualization was designed around an abstract interface that supports a diverse family of graphics systems Some of these graphics systems use a graphics library compiled with Geant4 such as OpenGL while others involve a separate application such as WIRED or DAWN You need not use all visualization drivers You can select those suitable to your purposes In the following for sim plicity we assume that the Geant4 libraries are built installed with the OpenGL Xlib driver and the DAWN FILE driver incorporated 26 Getting Started with Geant4 Running a Simple Example In order to use the DAWNFILE driver you need Fukui Renderer DAWN which is obtainable from the following Web site http geant4 kek jp GEANT4 vis In order to use the the OpenGL drivers you need the OpenGL library which is installed in many platforms by default You also need to set an environmental variable G4VIS_BUILD_OPENGLX_DRIVER to 1 in building installing Genat4 libraries and also set another environmental variable G4VIS_USE_OPENGLX to 1 in com piling your Geant4 executable You may also have to set an environmental variable OGLHOME to the OpenGL root directory For example setenv G4VIS_BUILD_OPENGLX_DRIVER 1 setenv G4VIS_USE_OPENGLX 1 setenv OGLHOME usr X11R6 Some other visualization drivers depending on external
313. ger pman theParticleDef GetProcessManager pman AddRestProcess theProcess 5 2 2 3 Hadrons in Flight What processes do you need For hadrons in motion there are four physics process classes Table 5 1 shows each process and the particles for which it is relevant G4HadronElasticProcess pit pi K KOS K K p p bar n n bar lambda lambda bar Sigma Sigma Sigma bar Sigma bar Xil Xi Xi bar Xi bar G4HadronInelasticProcess pit pi K Ks Ki K p p bar n n bar lambda lambda bar Sigma Sigma Sigma bar Sigma bar Xi Xi Xi bar Xi bar G4HadronFissionProcess all G4CaptureProcess n n bar Table 5 1 Hadronic processes and relevant particles How to register Models To register an inelastic process model for a particle a proton for example first get the pointer to the particle s process manager G4ParticleDefinition theProton G4Proton ProtonDefinition G4ProcessManager theProtonProcMan theProton gt GetProcessManager 153 Tracking and Physics Create an instance of the particle s inelastic process G4ProtonInelasticProcess theProtonIEProc new G4ProtonInelasticProcess Create an instance of the model which determines the secondaries produced in the interaction and calculates the momenta of the particles G4LEProtonInelastic theProtonIE new GA4LEProtonInelastic Register the model with the particle s inelastic
314. gistered in a store which will take care of destroying them at the end of the job A default region with a default production cut is automatically created and assigned to the world volume 4 1 4 Physical Volumes Physical volumes represent the spatial positioning of the volumes describing the detector elements Several tech niques can be used They range from the simple placement of a single copy to the repeated positioning using either a simple linear formula or a user specified function The simple placement involves the definition of a transformation matrix for the volume to be positioned Repeated positioning is defined using the number of times a volume should be replicated at a given distance along a given 77 Detector Definition and Response direction Finally it is possible to define a parameterised formula to specify the position of multiple copies of a volume Details about these methods are given below Note For geometries which vary between runs and for which components of the old geometry setup are ex plicitely deleted it is required to consider the proper order of deletion which is the exact inverse of the actual construction i e first delete physical volumes and then logical volumes Deleting a logical volume does NOT delete its daughter volumes It is not necessary to delete the geometry setup at the end of a job the system will take care to free the volume and solid stores at the end of the job The user has
315. gnetic processes G4LEVELGAMMADATA Path to the data set for Photon Evaporation 286 Appendix G4RADIOACTIVEDATA Path to the data set for Radiative Decay processes G4ABLADATA Path to nuclear shell effects data set for INCL ABLA hadronic model 5 3 Linking External Libraries with Geant4 The Geant4 GNUmake infrastructure allows to extend the link list of libraries with external or user defined packages which may be required for some user s applications to generate the final executable 5 3 1 Adding external libraries which do not use Geant4 In the GNUmakefile of your application before including binmake gmk specify the extra library in EX TRALIBS either using the L 1 syntax or by specifying the full pathname e g EXTRALIBS L your path lib l myExtraLib Or EXTRALIBS lt your path gt lib lib lt myExtraLib gt a You may also specify EXTRA_LINK_DEPENDENCIES which is added to the dependency of the target exe cutable and you may also specify a rule for making it e g EXTRA LINK DEPENDENCIES lt your path gt lib lib lt myExtraLib gt a your path lib lib myExtraLib a cd lt your path gt lib MAKE Note that you almost certainly need to augment CPPFLAGS for the header files of the external library e g CPPFLAGS I lt your path gt include See Example 86 Example 86 An example of a customised GNUmakefile for an application or example us
316. gning a set of visualization attributes with cyan colour and forced wireframe style to a logical volume f C source codes Assigning G4VisAttributes to a logical volume Instantiation of a logical volume myTargetLog new G4LogicalVolume myTargetTube BGO TLog 0 0 0 Instantiation of a set of visualization attributes with cyan colour G4VisAttributes calTubeVisAtt new G4VisAttributes G4Colour 0 1 1 Set the forced wireframe style calTubeVisAtt gt SetForceWireframe true Assignment of the visualization attributes to the logical volume myTargetLog gt SetVisAttributes calTubeVisAtt end of C source codes Note that the life of the visualization attributes must be at least as long as the objects to which they are assigned it is the users responsibility to ensure this and to delete the visualization attributes when they are no longer needed or just leave them to die at the end of the job 8 6 6 Additional User Defined Attributes Geant4 Trajectories and Hits can be assigned additional arbitrary attributes that will be displayed when you click on the relevant object in the WIRED or FRED HepRep browsers WIRED then lets you label objects by any of these attributes or cut visibility based on these attributes Define the attributes with lines such as 242 Visualization std map lt G4String G4AttDef gt store G4AttDefStore GetInstance G4Trajectory isNew G4
317. gorithm is included it first tests a target volume then it loops over all daughter volumes and calls itself 102 Detector Definition and Response Pay attention For a complex geometry checking the entire volume hierarchy can be extremely time consuming 4 1 11 3 Detecting overlaps at construction Since release 8 0 the Geant4 geometry modeler provides the ability to detect overlaps of placed volumes nor mal placements or parameterised at the time of construction This check is optional and can be activated when instantiating a placement see G4PVPlacement constructor in Section 4 1 4 1 or a parameterised volume see G4PVParameterised constructor in Section 4 1 4 2 The positioning of that specific volume will be checked against all volumes in the same hierarchy level and its mother volume Depending on the complexity of the geometry being checked the check may require considerable CPU time it is therefore suggested to use it only for debugging the geometry setup and to apply it only to the part of the geometry setup which requires debugging The classes G4PVPlacement and G4PVParameterised also provide a method G4bool CheckOverlaps G4int res 1000 G4double tol 0 G4bool verbose true which will force the check for the specified volume The check verifies if each placed or parameterised instance is overlapping with other instances or with its mother volume A default resolution for the number of points to be generated and ve
318. h HAT AW AX m K i MW nt M i i i i iN In the picture pySemiAxis pzTopCut 25 pxSemiAxis 30 75 60 75 zMax 50 where pxSemiAxis Semiaxis in X pySemiAxis Semiaxis in Y zMax Height of elliptical cone pzTopCut upper cut plane level 66 Detector Definition and Response An elliptical cone of height zMax semiaxis pxSemiAxis and semiaxis pySemiAxis is given by the para metric equations x pxSemiAxis zMax u u Cos v y pySemiAxas zMax uw uw Sunt z u Where v is between 0 and 2 Pi and u between 0 and h respectively Paraboloid a solid with parabolic profile A solid with parabolic profile and possible cuts along the Z axis can be defined as follows G4Parabolid const G4String amp pName G4double R1 G4double R2 G4double Dz The equation for the solid is weno lt lt etl ws va 12 dz lt Zz lt dz wiles kl S la t k2 38220582 kl s dz t K2 R1 20 R2 35 Dz 20 R1 Radius at Dz R2 Radius at Dz Dz Half length Z greater than R1 Tube with Hyperbolic Profile A tube with a hyperbolic profile HYPE can be defined as follows G4Hype const G4String amp pName G4double innerRadius G4double outerRadius G4double innerStereo G4double outerStereo G4double halfLenZ In the picture innerStereo 0 7 outerStereo 0 7 halfLenZ 50
319. h in the full geometry up to a GEANT4 volume surface and the distance to the user de fined surface To do it G4ErrorNavigator inherits from G4Navigator and overwrites the methods Com puteStep and ComputeSafety Two types of surface are currently supported more types could be easily implemented at user request plane and cylindrical 5 8 4 1 1 Plane surface target G4ErrorPlaneSurfaceTarget implements an infinite plane surface The surface can be given as the four coefficients of the plane equation ax by cz d O G4ErrorPlaneSurfaceTarget G4double a 0 G4double b 0 G4double c 0 G4double d 0 or as the normal to the plane and a point contained in it G4ErrorPlaneSurfaceTarget const G4Normal3D n const G4Point3D amp p or as three points contained in it 182 Tracking and Physics G4ErrorPlaneSurfaceTarget const G4Point3D amp pl const G4Point3D amp p2 const G4Point3D amp p3 5 8 4 1 2 Cylindrical surface target G4ErrorCylSurfaceTarget implements an infinite length cylindrical surface a cylinder without end caps The surface can be given as the radius the translation and the rotation G4ErrorCylSurfaceTarget const G4double amp radius const G4ThreeVector amp trans G4ThreeVector const G4RotationMatrix amp rotm G4RotationMatrix or as the radius and the affine transformation G4ErrorCylSurfaceTarget const G4double amp radius const G4AffineTransform amp trans 5
320. hart for novice level examples NO1 NO2 and NO3 257 Examples ExampleN04 ExampleN05 ExampleN06 comments simplified collider geome parametrised shower ex Optical photon example try ample Run main for interactive main for interactive main for interactive mode mode mode Event e event generator selection event generator selection event generator selection HEPEvtInterface HEPEvtInterface particleGun Stack control Tracking select trajectories selecting secondaries Geometry geometry definition in ghost volume for shower geometry definition BREP cludes Param Replica parametrisation with rotation non uniform magnetic field Hits Digi Tracker calorimeter Sensitive detector for counter types shower parametrisation e ReadOut geometry PIIM Full particle set EM set EM set e mixtures and compound mixtures and compound mixtures and compound elements elements elements Physics Full physics processes Parametrized shower Optical photon processes Vis e detector amp hit drawing detector amp hit drawing calorimeter type hits drawing G UI define user commands define user commands define user commands Global random number engine Table 9 2 The item chart for novice level examples NO4 NO5 and NO6 ExampleN07 comments Cuts per region Run main for interactive mode Customized run class
321. he energylmomentum bin G4PhysicsOrderedFreeVector A physics ordered free vector inherits from G4PhysicsVector It provides in addition a method for the user to insert energy value pairs in sequence Methods to retrieve the max and min energies and values from the vector are also provided G4Timer Utility class providing methods to measure elapsed user system process time Uses lt sys times h gt and lt unistd h gt POSIX 1 G4UserLimits Class collecting methods for get and set any kind of step limitation allowed in Geant4 G4UnitsTable Placeholder for the system of units in Geant4 3 3 System of units 3 3 1 Basic units Geant4 offers the user the possibility to choose and use the units he prefers for any guantity In fact the Geant4 kernel takes care of the units Internally it uses a consistent set on units based on the HepSystemOfUnits millimeter mm nanosecond ns Mega electron Volt MeV positron charge eplus degree Kelvin kelvin the amount of substance mole luminous intensity candela 38 Toolkit Fundamentals radian radian steradian steradian All other units are defined from the basic ones For instance millimeter mm 1 meter m 1000 mm m3 m m m In the file source global management include SystemOfUnits h you will find all of these defi nitions That file is part of CLHEP Moreover the user is free to change the system of units to be used by the kernel
322. he particle motion in space and time It is the mandatory process for tracking particles In the ConstructProcess method physics processes should be created and registered with each particle s instance of G4ProcessManager An example of process registration is given in the G4VUserPhysicsList AddTransportation method Registration in G4ProcessManager is a complex procedure for other processes and particles because the relations between processes are crucial for some processes Please see Section 5 2 and the example codes An example of electromagnetic process registration for photons is shown below Example 2 18 Register processes for a gamma void MyPhysicsList ConstructProcess Define transportation process AddTransportation electromagnetic processes ConstructEM void MyPhysicsList ConstructEM Get the process manager for gamma G4ParticleDefinition particle G4Gamma GammaDefinition G4ProcessManager pmanager particle GetProcessManager Construct processes for gamma G4PhotoElectricEffect thePhotoElectricEffect new G4PhotoElectricEffect G4ComptonScattering theComptonScattering new G4ComptonScattering G4GammaConversion theGammaConversion new G4GammaConversion Register processes to gamma s process manager pmanager gt AddDiscreteProcess thePhotoElectricEffect pmanager gt AddDiscreteProcess theComptonScattering pmanager gt AddDiscreteProcess theGammaConve
323. he constructor by value and its transformation is stored by the Boolean solid The user may modify the G4Transform3D and eventually use it again When positioning a volume associated to a Boolean solid the relative center of coordinates considered for the positioning is the one related to the first of the two constituent solids 4 1 2 3 Boundary Represented BREPS Solids BREP solids are defined via the description of their boundaries The boundaries can be made of planar and second order surfaces Eventually these can be trimmed and have holes The resulting solids such as polygonal polycon ical solids are known as Elementary BREPS In addition the boundary surfaces can be made of Bezier surfaces and B Splines or of NURBS Non Uniform Rational B Splines surfaces The resulting solids are Advanced BREPS Currently the implementation for surfaces generated by Beziers B Splines or NURBS is only at the level of prototype and not fully functional Extensions in this area are foreseen in future We have defined a few simple Elementary BREPS that can be instantiated simply by a user in a manner similar to the construction of Constructed Solids CSGs We summarize their capabilities in the following section Most BREPS Solids are however defined by creating each surface separately and tying them together Specific BREP Solids We have defined one polygonal and one polyconical shape using BREPS The polycone provides a shape defined
324. he following Given the pointer to the step object G4Step aStep retrieve the pre step point Jd G4StepPoint preStepPoint aStep GetPreStepPoint retrieve a touchable handle and access to the information Fi G4TouchableHandle theTouchable preStepPoint GetTouchableHandle G4int copyNo theTouchable gt GetCopyNumber G4int motherCopyNo theTouchable gt GetCopyNumber 1 To determine the exact position in global coordinates in the mass geometry and convert to local coordinates local to the current volume G4ThreeVector worldPosition preStepPoint gt GetPosition G4ThreeVector localPosition theTouchable gt GetHistory gt GetTopTransform TransformPoint worldPosition Using an alternative navigator to locate points In order to know when in the idle state of the application in which physical volume a given point is located in the detector geometry it is necessary to create an alternative navigator object first and assign it to the world volume G4Navigator aNavigator new G4Navigator aNavigator gt SetWorldVolume worldVolumePointer Then locate the point myPoint defined in global coordinates retrieve a touchable handle and do whatever you need with it aNavigator LocateGlobalPointAndSetup myPoint G4TouchableHistoryHandle aTouchable 94 Detector Definition and Response aNavigator CreateTouchableHistoryHandle Do whatever y
325. he new kinetic energy after each continuos process was invoked and NOT the sum of the energy difference before and after the process invocation and updating position and time 9 The discrete process is invoked After the invocation the energy of the current track particle is updated and the secondaries from ParticleChange are stored in SecondaryList This includes constructing G4Track objects and setting their member data Note that the stepping manager is responsible for deleting secodaries from ParticleChange 10 The track is checked to see whether or not it has been terminated by the discrete process 11 Safety is updated 12 If the step was limited by the volume boundary push the particle into the next volume 13 Invoke the user intervention G4UserSteppingAction 14 Handle hit information 15 Save data to Trajectory 16 Update the mean free paths of the discrete processes 17 If the parent particle is still alive reset the maximum interaction length of the discrete process which has occurred 135 Tracking and Physics 18 One step completed What is a Step G4Step stores the transient information of a step This includes the two endpoints of the step PreStepPoint and Post StepPoint which contain the points coordinates and the volumes containing the points G4Step also stores the change in track properties between the two points These properties such as energy and momentum are updated as the various a
326. he third vertex is 75 Detector Definition and Response PtO vt2 all in anti clockwise order when looking from the outside The G4QuadrangularFacet class can be used for the contruction of GGTessellatedSolidas well It is defined by four vertices which shall be in the same plane and be supplied in anti clockwise order looking from the outside of the solid where it belongs Its constructor looks like G4QuadrangularFacet const G4ThreeVector PEO const G4ThreeVector SEL const G4ThreeVector NAE const G4ThreeVector PE Shy G4FacetVertexType fType i e it takes 5 parameters to define the four vertices G4FacetVertexType ABSOLUTE in which case Pt0 vt 1 vt 2 and vt 3 are the four vertices required in anti clockwise order when looking from the outside G4FacetVertexType RELATIVE in which case the first vertex is Pt O the second vertex is Pt 0 vt the third vertex is PtO vt2 and the fourth vertex is Pt 0 vt 3 in anti clockwise or der when looking from the outside Importing CAD models as tessellated shapes Tessellated solids can also be used to import geometrical models from CAD systems see Figure 4 1 In order to do this it is required to convert first the CAD shapes into tessellated surfaces A way to do this is to save the shapes in the geometrical model as STEP files and convert them using a tool like STViewer or FASTRAD to tessellated faceted surfaces solids This strateg
327. he user can specify the luxury level to the constructor if not the default value 3 is taken For example RanluxEngine theRanluxEngine seed 4 instantiates an engine with seed and the best luxury level tue OT RanluxEngine theRanluxEngine instantiates an engine with default seed value and luxury level The class provides a get Luxury method to get the engine luxury level The SetSeed and Set Seeds methods to set the initial seeds for the engine can be invoked specifying the luxury level For example 34 Toolkit Fundamentals static interface HepRandom setTheSeed seed 4 sets the seed to seed and luxury to 4 HepRandom set TheSeed seed sets the seed to seed keeping the current luxury level RanecuEngine The algorithm for RanecuEngine is taken from the one originally written in FORTRANT7 as part of the MATH LIB HEP library The initialisation is carried out using a Multiplicative Congruential generator using formula constants of L Ecuyer as described in F James Comp Phys Comm 60 1990 329 344 Handling of seeds for this engine is slightly different than the other engines in HEPRandom Seeds are taken from a seed table given an index the get Seed method returns the current index of seed table The set Seeds method will set seeds in the local SeedTable at a given position index if the index number specified exceeds the table s size index size is taken For exampl
328. he very end of the BeamOn method Typical use cases of this method are store print histograms manipulate run summaries 41 Toolkit Fundamentals 3 4 2 Geant4 as a state machine Geant4 is designed as a state machine Some methods in Geant4 are available for only a certain state s G4RunManager controls the state changes of the Geant4 application States of Geant4 are represented by the enu meration G4ApplicationState It has six states through the life cycle of a Geant4 application G4State Prelnit state A Geant4 application starts with this state The application needs to be initialized when it is in this state The application occasionally comes back to this state if geometry physics processes and or cut off have been changed after processing a run G4State_Init state The application is in this state while the Initialize method of G4RunManager is being invoked Meth ods defined in any user initialization classes are invoked during this state G4State_Idle state The application is ready for starting a run G4State_GeomClosed state When BeamOn is invoked the application proceeds to this state to process a run Geometry physics pro cesses and cut off cannot be changed during run processing G4State EventProc state A Geant4 application is in this state when a particular event is being processed GetCurrentEvent and GetPreviousEvent methods of G4RunManager are available only at this state G4
329. hh include G4UIcmdWithoutParameter hh include G4UIcmdWithAString hh include G4UIcmdWithADoubleAndUnit hh include G4UIcmdWith3Vector hh include G4UIcmdWith3VectorAndUnit hh include lt iostream h gt G4ParticleGunMessenger G4ParticleGunMessenger G4ParticleGun fPtclGun fParticleGun fPtclGun particleTable G4ParticleTable GetParticleTable gunDirectory new G4Uldirectory gun gunDirectory gt SetGuidance Particle Gun control commands listCmd new G4UIcmdWithoutParameter gun list this listCmd gt SetGuidance List available particles listCmd gt SetGuidance Invoke G4ParticleTable particleCmd new G4UIcmdWithAString gun particle this particleCmd gt SetGuidance Set particle to be generated particleCmd gt SetGuidance geantino is default particleCmd gt SetParameterName particleName true particleCmd gt SetDefaultValue geantino G4String candidateList G4int nPtcl particleTable gt entries for G4int i 0 i lt nPtcl it candidateList particleTable gt GetParticleName i candidateList particleCmd gt SetCandidates candidateList directionCmd new G4UIcmdWith3Vector gun direction this directionCmd gt SetGuidance Set momentum direction directionCmd gt SetGuidance Direction needs not to be a unit vector directionCmd gt SetParameterName Px Py Pz true true directionCmd gt SetRange Px
330. hich you can invoke and run You should actually add G4WORKDIR bin G4SYSTEM to PATH in your environment 2 7 2 Building ExampleN01 in a Windows Environment The procedure to build a Geant4 executable on a system based on a Windows system is similar to what should be done on a UNIX based system assuming that your system is equipped with GNUmake MS Visual C compiler and the required software to run Geant4 see Installation Guide 2 7 2 1 Building the executable See paragraph Section 2 7 1 2 8 How to Set Up an Interactive Session 2 8 1 Introduction 2 8 1 1 Roles of the intercoms category The intercoms category provides an expandable command interpreter It is the key mechanism of Geant4 to realize user interactions of all categories without being annoyed by the dependencies among categories The direct use of Geant4 classes in a C program offers a first ground level of interactivity i e the batch session As seen in the examples novice N01 Geant4 commands and macros are to be hard coded in the program Getting Started with Geant4 Running a Simple Example 2 8 1 2 User Interfaces to steer the simulation To avoid too much programming the intercoms category provides the abstract class G4UIsession that captures interactive commands The concrete implementation of the user interface and Graphical User Interfaces GUI is left to the interfaces category This interfacing strategy opens an important door
331. his variable is set automatically if the Configure script is adopted for the installation This will result in the proper settings also for configuring the environment with the generated shell scripts env c sh Installation paths G4INSTALL Defines the path where the Geant4 toolkit should be installed It should be set by the system installer By default it sets to SHOME geant 4 assuming the Geant4 distribution is placed in HOME G4BASE Defines the path to the source code Internally used to define SCPPFLAGS and LDFLAGS for I and L directives It has to be set to SG4INSTALL src G4WORKDIR Defines the path for the user s workdir for Geant4 It is set by default to SHOME geant 4 assuming the user s working directory for Geant4 is placed in HOME G4INCLUDE Defines the path where source header files may be mirrored at installation by issuing gmake includes default is set to SG4INSTALL include G4BIN G4BINDIR Used by the system to specify the place where to store executables By default they re set to G4WORKDIR bin and 5G4BIN G4SYSTEM respectively The path to GAWORKDIR bin S GA4SYSTEM should be added to PATH in the user environment G4BIN can be overridden G4TMP G4TMPDIR Used by the system to specify the place where to store temporary files products of the compilation build of a user application or test By default they re set to G4WORKDIR tmp and G4TMP G4SYSTEM respec tively G4TM
332. hus output strings may be displayed on another window or stored in a file Manipulation of these output streams will be described in Section 7 2 4 These objects should be used instead of the ordinary cout and cerr Getting Started with Geant4 Running a Simple Example 2 2 How to Define a Detector Geometry 2 2 1 Basic Concepts A detector geometry in Geant4 is made of a number of volumes The largest volume is called the World volume It must contain with some margin all other volumes in the detector geometry The other volumes are created and placed inside previous volumes included in the World volume The most simple and efficient shape to describe the World is a box Each volume is created by describing its shape and its physical characteristics and then placing it inside a con taining volume When a volume is placed within another volume we call the former volume the daughter volume and the latter the mother volume The coordinate system used to specify where the daughter volume is placed is the coordinate system of the mother volume To describe a volume s shape we use the concept of a solid A solid is a geometrical object that has a shape and specific values for each of that shape s dimensions A cube with a side of 10 centimeters and a cylinder of radius 30 cm and length 75 cm are examples of solids To describe a volume s full properties we use a logical volume It includes the geometrical properties of the solid an
333. iate such an object It is also the ideal place to set variables which affect the physics table such as production thresholds for a particular run because GenerateRun is invoked before the calculation of the physics table BeginOfRunAction This method is invoked before entering the event loop A typical use of this method would be to initialize and or book histograms for a particular run This method is invoked after the calculation of the physics tables EndOfRunAction This method is invoked at the very end of the run processing It is typically used for a simple analysis of the processed run Example 6 4 G4UserRunAction class G4UserRunAction public G4UserRunAction virtual G4UserRunAction public virtual G4Run GenerateRun virtual void BeginOfRunAction const G4Run virtual void EndOfRunAction const G4Run 188 User Actions G4UserEventAction This class has two virtual methods which are invoked by G4Event Manager for each event beginOfEventAction This method is invoked before converting the primary particles to G4Track objects A typical use of this method would be to initialize and or book histograms for a particular event endOfEventAction This method is invoked at the very end of event processing It is typically used for a simple analysis of the processed event If the user wants to keep the currently processing event until the end of the current run the user can invo
334. ic it may be platform specific FAQ 3 Geometry Q I have a generic point and I would like to know in which physical volume I m located in my detector ge ometry The best way of doing this is by invoking the G4Navigator First get a pointer of the navigator through the G4TransportationManager and then locate the point i e include G4TransportationManager hh include G4Navigator hh G4ThreeVector myPoint G4Navigator theNavigator G4TransportationManager GetTransportationManager GetNavigatorForTracking G4VPhysicalVolume myVolume theNavigator LocateGlobalPointAndSetup myPoint Frequentry Asked Questions Note by using the navigator for tracking as shown above the actual particle gets also relocated in the specified position Therefore if this information is needed during tracking time in order to avoid affecting tracking you should either use an alternative G4Navigator object which you then assign to your world volume or you access the information through the track or touchable as specified in the FAQ for tracking and steps Q How can I access the daughter volumes of a specific physical volume A Through the associated logical volume G4VPhysicalVolume myPVolume G4LogicalVolume myLVolume myPVolume gt GetLogicalVolume for G4int i 0 iGetNoDaughters i myPVolume myLVolume GetDaughter i Q How can I identify the exact copy number of a sp
335. ich takes the unigue module name G4DigiManager fDM G4DigiManager GetDMpointer MyDigitizer myDM fDM Digitize myDet myCal myEMdigiMod How to get hitsCollection and or digiCollection G4DigiManager has the following methods to access to the hits or digi collections of the currently processing event or of previous events First you have to get the collection ID number of the hits or digits collection G4DigiManager DM G4DigiManager GetDMpointer G4int myHitsCollID fDM GetHitsCollectionID hits collection name G4int myDigiCollID DM gt GetDigiCollectionID digi collection name Then you can get the pointer to your concrete G47THits Collection object or G4TDigiCollection object of the currently processing event 128 Detector Definition and Response MyHitsCollection HC MyDigiCollection DC DM gt GetHitsCollection myHitsCollID fDM GetDigiCollection myDigiCollID In case you want to access to the hits or digits collection of previous events add the second argument MyHitsCollection HC MyDigiCollection DC fDM GetHitsCollection myHitsCollID n fDM GetDigiCollection myDigiCollID n where n indicates the hits or digits collection of the p previous event 4 6 Object Persistency 4 6 1 Persistency in Geant4 Object persistency is provided by Geant4 as an optional category so that the user may run Geant4 with or without an object database man
336. icle encoding number by PDG G4int GetAntiPDGEncoding encoding for anti particle of this particle Table 5 2 Methods to get particle properties Table 5 3 shows the methods of G4ParticleDefinition for getting information about decay modes and the life time of the particle G4bool GetPDGStable stable flag G4double GetPDGLifeTime life time G4DecayTable GetDecayTable decay table Table 5 3 Methods to get particle decay modes and life time 173 Tracking and Physics Users can modify these properties though the other properties listed above can not be change without rebuilding the libraries Each particle has its own G4ProcessManger object that manages a list of processes applicable to the particle see Section 2 5 2 5 3 3 Dynamic particle The G4DynamicParticle class has kinematics information for the particle and is used for describing the dynamics of physics processes The properties in G4DynamicParticle are listed in Table 5 4 G4double theDynamicalMass dynamical mass G4ThreeVector theMomentumDirection normalized momentum vector G4ParticleDefinition theParticleDef definition of particle inition G4double theDynamicalSpin dynamical spin i e total angular momentum as a ion atom G4ThreeVector thePolarization polarization vector G4double theMagneticMoment dynamical magnetic moment i e total magnetic mo ment as a ion atom G4double th
337. icles Various utility methods are provided such as FindParticle G4String name find the particle by name FindParticle G4int PDGencoding find the particle by PDG encoding G4ParticleTable is defined as a singleton object and the static method G4ParticleTable GetParticleTable provides its pointer As for heavy ions including hyper nuclei objects are created dynamically by requests from users and processes The G4ParticleTable class provides methods to create ions such as G4ParticleDefinition GetIon G4int atomicNumber G4int atomicMass G4double excitationEnergy Particles are registered automatically during construction The user has no control over particle registration 2 4 1 4 Constructing Particles ConstructParticle is a pure virtual method in which the static member functions for all the particles you require should be called This ensures that objects of these particles are created WARNING You must define All PARTICLE TYPES which are used in your application except for heavy ions All PARTICLE TYPES means not only primary particles but also all other particles which may appear as secondaries generated by physics processes you use Beginning with Geant4 version 8 0 you should keep this tule strictly because all particle definitions are revised to non static objects For example suppose you need a proton and a geantino which is a virtual particle used for simulation and which does not interact
338. ied by the user to his her code repository These files are distributed together with Geant4 release The user should set the environment variable G4LEDATA to the directory where he she has copied the files Options are available for low energy electromagnetic processes for hadrons and ions in terms of public member functions of the G4hLowEnergylonisation class e SetHighEnergyForProtonParametrisation G4double SetLowEnergyForProtonParametrisation G4double e SetHighEnergyForAntiProtonParametrisation G4double SetLowEnergyForAntiProtonParametrisation G4double e SetElectronicStoppingPowerModel const G4ParticleDefinition const G4String amp SetNuclearStoppingPowerModel const G4String amp SetNuclearStoppingOn SetNuclearStoppingOff SetBarkasOn SetBarkasOff SetFluorescence const G4bool ActivateAugerElectronProduction G4bool SetCutForSecondaryPhotons G4double SetCutForSecondaryElectrons G4double The available models for ElectronicStoppingPower and NuclearStoppingPower are documented in the class di agrams Options are available for low energy electromagnetic processes for electrons in the G4LowEnergylonisation class ActivateAuger G4bool SetCutForLowEnSecPhotons G4double SetCutForLowEnSecElectrons G4double Options are available for low energy electromagnetic processes for electrons positrons in the G4LowEnergyBremsstrahlung class that allow the use of alternative bremsstrahlung angu
339. ields can also vary with time as can magnetic fields Source listing Example 4 12 shows how to define a uniform electric field for the whole of a detector Example 4 12 How to define a uniform electric field for the whole of a detector extracted from example in examples extended field field02 in the header file or first include G4EqMagElectricField hh include G4UniformElectricField hh G4ElectricField fEMfield G4EqMagElectricField fEquation G4MagIntegratorStepper fStepper G4FieldManager fFieldMgr G4double fMinStep G4ChordFinder fChordFinder in the source file fEMfield new G4UniformElectricField G4ThreeVector 0 0 100000 0 kilovolt cm 0 0 Create an equation of motion for this field fEquation new G4EqMagElectricField fEMfield G4int nvar 8 fStepper new G4ClassicalRK4 fEquation nvar Get the global field manager fFieldManager G4TransportationManager GetTransportationManager gt GetFieldManager Set this field to the global field manager fFieldManager gt SetDetectorField fEMfield fMinStep 0 010 mm minimal step of 10 microns flntgrDriver new G4MagInt Driver fMinStep fStepper fStepper GetNumberOfVariables fChordFinder new G4ChordFinder fIntgrDriver fFieldManager SetChordFinder fChordFinder An example with an electric field is examples extended field field02 where the class FO2ElectricFieldSetup demonstrates how to set
340. ilding objects and libraries globlib gmk defining all general GNUmake rules for building compound libraries binmake gmk defining the general GNUmake rules for building executables GNUmakefile placed inside each directory in the Geant4 distribution and defining directives specific to build a library a set of sub libraries or an executable Kernel libraries are placed by default in G4INSTALL 1lib SG4SYSTEM where G4SYSTEM specifies the system architecture and compiler in use Executable binaries are placed in G4WORKDIR bin S G4SYSTEM and temporary files object files and data products of the compilation process in G4WORKDIR tmp SG4SYSTEM GAWORKDIR set by default to G4INSTALL should be set by the user to specify the place his her own workdir for Geant4 in the user area For more information on how to build Geant4 kernel libraries and set up the correct environment for Geant4 refer to the Installation Guide 2 7 1 2 Building the executable The compilation process to build an executable such as an example from G4INSTALL examples is start ed by invoking the gmake command from the sub directory in which you are interested To build for in stance exampleNO1 in your G4WORKD IR area you should copy the module G4INSTALL examples to your SGAWORKDIR and do the following actions gt cd G4WORKDIR examples novice NO1 gt gmake This will create in SG4WORKDIR bin SG4SYSTEM the exampleNO1 executable w
341. ill two contradictory requirements It is the responsibility of each individual process to produce secondary particles according to its own capabilities On the other hand it is only the Geant4 kernel i e tracking which can ensure an overall coherence of the simulation 174 Tracking and Physics The general principles in Geant4 are the following 1 Each process has its intrinsic limit s to produce secondary particles 2 All particles produced and accepted will be tracked up to zero range 3 Each particle has a suggested cut in range which is converted to energy for all materials and defined via a SetCut method see Section 2 4 2 Points 1 and 2 imply that the cut associated with the particle is a recommended production threshold of sec ondary particles 5 4 2 Set production threshold SetCut methods As already mentioned each kind of particle has a suggested production threshold Some of the processes will not use this threshold e g decay while other processes will use it as a default value for their intrinsic limits e g ionisation and bremsstrahlung See Section 2 4 2 to see how to set the production threshold 5 4 3 Apply cut The DoIt methods of each process can produce secondary particles Two cases can happen process sets its intrinsic limit greater than or equal to the recommended production threshold OK Nothing has to be done nothing can be done e process sets its intrinsi
342. ime time since the current event began Local time time since the current track began Proper time How to Get particle change Particle change information can be accessed by invoking various Get methods provided in the G4ParticleChange class Typical information available includes for details see the Software Reference Manual final momentum direction of the parent particle final kinetic energy of the parent particle final position of the parent particle final global time of the parent particle final proper time of the parent particle final polarization of the parent particle status of the parent particle G4TrackStatus true step length this is used by multiple scattering to store the result of the transformation from the geometrical step length to the true step length local energy deposited this consists of either energy deposited by the energy loss process or the energy lost by secondaries which have NOT been generated because each of their energies was below the cut threshold number of secondaries particles list of secondary particles list of G4Track 5 1 3 Handling of Secondary Particles Secondary particles are passed as G4Tracks from a physics process to tracking G4ParticleChange provides the following four methods for a physics process AddSecondary G4Track aSecondary AddSecondary G4DynamicParticle aSecondary AddSecondary G4DynamicParticle aSecondary G4ThreeVector position
343. in Geant4 This list includes all particles in Geant4 and you can see properties of particles such as PDG encoding e mass and width electric charge spin isospin and parity magnetic moment quark contents life time and decay modes Here is a list of particles in Geant4 This list is generated automatically by using Geant4 functionality so listed values are same as those in your Geant4 application as far as you do not change source codes Categories gluon quarks di quarks leptons mesons baryons ions others 5 3 2 2 Classification of particles 1 elementary particles which should be tracked in Geant4 volumes All particles that can fly a finite length and interact with materials in detectors are included in this category In addition some particles with a very short lifetime are included for user s convenience a stable particles Stable means that the particle can not decay or has a very small possibility to decay in detectors e g gamma electron proton and neutron 171 Tracking and Physics b long life gt 10 sec particles Particles which may travel a finite length e g muon charged pions c short life particles that decay immediately in Geant4 For example pi eta d K system KO decays immediately into Ks or Ko and then K9y K decays according to its life time and decay modes e optical photon Gamma and optical photon are distinguished in the si
344. inal Xm Xaw Win32 GAG GainServer in a user s program he has the following lines in his main program to include the class definition in his main program include G4Uixxx hh to instantiate a session of his choice and start the session G4UIsession session new G4UIxxx session gt SessionStart the line next to the SessionStart is usually to finish the session delete session For a tcsh session the second line must be G4UIsession session new G4UIterminal new G4UItcsh See the examples in examples novice NOx in which the terminal session is used If the user wants to deactivate the default signal handler soft abort raised by Ctr C the false flag can be set in the second argument of the G4Ulterminal constructor like 20 Getting Started with Geant4 Running a Simple Example G4Ulsession session new G4Ul terminal new G4UItcsh false Again environment variable selects a given interface But for your convenience some of them are set defaults e G4Ulterminal G4UItcsh G4UIGAG and G4UIGainServer can be used without any environment variables Sessions not needing external packages or libraries are always built see G4UI BUILD gmk and linked so the user can instantiate one of these sessions without rebuilding the libraries and without setting any environ ment variables For backwards compatibility with user code as typified by geant4 examples main programs the C pre processor variables co
345. ined in the current geometry setup and only physics vectors corresponding to the MaterialCutsCouples used in the current setup are restored Note that nothing happens just after the retrievePhysicsTable command is issued Restoration of physics tables will be executed in parallel with the calculation of physics tables 5 6 4 Building the Physics Table In the G4RunManagerKernel RunInitialization method after the list of MaterialCutsCouples is updated the G4VUserPhysicsList BuildPhysicsTable method is invoked to build physics tables for all processes Initially the GaVProcess PreparePhysicsTable method is invoked Each process creates G4PhysicsTable objects as necessary It then checks whether the MaterialCutsCouples have been modified after a run to determine if the corresponding physics vectors can be used in the next run or need to be re calculated Next the GAVProcess RetrievePhysicsTable method is invoked if the GAVUserPhysicsList fRetrievePhysicsTable flag is asserted After checking materials and cuts in files physics vectors corresponding to the MaterialCutsCouples used in the current setup are restored Finally the GAVProcess BuildPhysicsTable method is invoked and only physics vectors which need to be re calculated are built 5 7 User Limits 5 7 1 General Concepts The user can define artificial limits affecting to the Geant4 tracking G4UserLimits G4double uStepMax DBL
346. ing 8 7 3 Controlling from Commands Multiple trajectory models can be created and configured using commands in the vis modeling trajec tories directory It is then possible to list available models and select one to be current Model configuration commands are generated dynamically when a model is instantiated These commands apply directly to that instance This makes it possible to have multiple instances of the drawByCharge model for example each independently configurable through it s own set of commands See the interactive help for more information on the available commands 8 7 3 1 Example commands Create a generic model named generic 0 by default vis modeling trajectories create generic Configure context to colour all trajectories red vis modeling trajectories generic 0 default setLineColour red Create a drawByCharge model named drawCharge 0 by default Subsequent models will be named drawBy Charge 1 drawByCharge 2 etc vis modeling trajectories create drawByCharge Create a drawByCharge model named testChargeModel vis modeling trajectories create drawByCharge testChargeModel Configure drawByCharge 0 model vis modeling trajectories drawByCharge 0 set 1 red vis modeling trajectories drawByCharge 0 set 1 red vis modeling trajectories drawByCharge 0 set 0 white Configure testCharge model through G4Colour components vis modeling trajectories testChargeModel setRGBA 10 11 1 vis modeling traje
347. ing an external module not bound to Geant4 Ani AS i L MR EL AT a i RAS Mr S a A GNUmakefile for the application sim depending on module Xplotter m m im mm i P M me name sim G4TARGET name G4EXLIB true CPPFLAGS IS HOME Xplotter include EXTRALIBS L HOME Xplotter lib 1Xplotter EXTRA LINK DEPENDENCIES HOME Xplotter lib libXplotter a ETIN adis alie dail pin include G4INSTALL config binmake gmk HOME Xplotter lib libXplotter a cd HOME Xplotter MAKE 5 3 2 Adding external libraries which use Geant4 In addition to the above specify in EXTRALIBSSOURCEDIRS a list of directories containing source files in its src subdirectory Thus your GNUmake file might contain 287 Appendix EXTRALIBS G4WORKDIR tmp G4SYSTEM lt myApp gt lib lt myApp gt a L your path lib l lt myExtraLib gt EXTRALIBSSOURCEDIRS lt your path gt lt myApp gt lt your path gt lt MyExtraModule gt EXTRA LINK DEPENDENCIES G4WORKDIR tmp GASYSTEM lt myApp gt lib lt myApp gt a MYSOURCES wildcard lt your path gt lt myApp gt src cc GAWORKDIR tmp GASYSTEM lt myApp gt lib lt myApp gt a MYSOURCES cd lt your path gt lt myApp gt S MAKE See Example 87 Example 87 An example of a customised GNUmakefile for an application or example usi
348. ing is an example of how to access the hit collection of a particular concrete type G4SDManager fSDM G4SDManager GetSDMpointer G4RunManager fRM G4RunManager GetRunManager G4int collectionID fSDM GetCollectionID collection name const G4Event currentEvent fRM GetCurrentEvent G4HCofThisEvent HCofEvent currentEvent gt GetHCofThisEvent MyHitsCollection myCollection MyHitsCollection HC0fEvent gt GetHC collectionID 4 4 5 G4MultiFunctionalDetector and G4VPrimitiveScorer G4MultiFunctionalDetector is a concrete class derived from G4VSensitiveDetector Instead of implementing a user specific detector class G4MultiFunctionalDetector allows the user to register G4VPrimitiveScorer classes to build up the sensitivity G4MultiFunctionalDetector should be instantiated in the users detector construction with its unique name and should be assigned to one or more G4LogicalVolumes G4VPrimitiveScorer is an abstract base class representing a class to be registered to G4MultiFunctionalDetector that creates a G4THitsMap object of one physics quantity for an event Geant4 provides many concrete primitive scorer classes listed in Section 4 4 6 and the user can also implement his her own primitive scorers Each prim itive scorer object must be instantiated with a name that must be unique among primitive scorers registered in a G4MultiFunctionalDetector Please note that a primitive scorer object must not be shared by
349. ing reached the specified depth the default being the full depth of the geometry tree The new settings will then be applied to any recursive test To detect overlapping volumes the built in test uses the intersection of solids with linear trajectories For example consider Figure 4 4 Mother Volume Figure 4 4 Different cases of placed volumes overlapping each other Here we have a line intersecting some physical volume large black rectangle Belonging to the volume are four daughters A B C and D Indicated by the dots are the intersections of the line with the mother volume and the four daughters This example has two geometry errors First volume A sticks outside its mother volume this practice sometimes used in GEANT3 21 is not allowed in Geant4 This can be noticed because the intersection point leftmost magenta dot lies outside the mother volume as defined by the space between the two black dots The second error is that daughter volumes A and B overlap This is noticeable because one of the intersections with A rightmost magenta dot is inside the volume B as defined as the space between the red dots Alternatively one of the intersections with B leftmost red dot is inside the volume A as defined as the space between the magenta dots Each of these two types of errors is represented by a line segment which has a start point an end point and a length Depending on the type of error the points are most c
350. ining an x axis with length 5 cm and with colour red I C source codes An example of defining a line segment Instantiate an emply polyline object G4Polyline x_axis Set red line colour G4Colour wc sO 10 0 Oo G4VisAttributes att red x axis SetVisAttributes amp att Set vertex positions x axis push back G4Point3D 0 0 0 sas Sp uS BASRI Aeron sD Sem 010 end of C source codes 8 9 2 Markers Here we explain how to use 3D markers in Geant4 Visualization What are Markers Markers set marks at arbitrary positions in the 3D space They are often used to visualize hits of particles at detector components A marker is a 2 dimensional primitive with shape square circle etc color and special properties a of always facing the camera and b of having the possibility of a size defined in screen units pixels Here size means overall size e g diameter of circle and side of square but diameter and radius access functions are defined to avoid ambiguity 250 Visualization So the user who constructs a marker should decide whether or not it should be visualized to a given size in world coordinates by setting the world size Alternatively the user can set the screen size and the marker is visualized to its screen size Finally the user may decide not to set any size in that case it is drawn according to the sizes specified in the default marker specified in the class G4Vi
351. ion ExN06PhysicsList header file source file derived from G4VUserPhysicsList definition of gamma leptons and optical photons transportation standard EM processes decay Cerenkov scintillation standard optical and boundary process modify augment optical process parameters ExNO6PrimaryGeneratorAction header file source file derived from G4VPrimaryGeneratorAction construction of G4ParticleGun primary event generation via particle gun ExNO6RunAction header file source file derived from G4VUserRunAction draw detector 9 1 8 Example N07 Basic concepts Geometry Changing geometry of three simplified sandwitch calorimeters without re building a world volume Region Defining geometrical regions ans setting production thresholds for each region Run Utilizing a concrete run class derived from G4Run base class for accumulating physics quantities and hits as a run Hits Demonstrating the use of primitive scorer and filter classes without implementing sensitive detector class Classes main source file main for interactive mode and batch mode via macro file construction and deletion of G4RunManager construction and deletion of G4VisExective and G4UITerminal construction and set of mandatory user classes construction and set of ExNO7RunAction ExN07DetectorConstruction header file source file derived from G4VUserDetectorConstruction definitions o
352. ion Instead you should use their abstract base class G4VVisManager defined in the intercoms category The pointer to the concrete instance of the real Visualization Manager can be obtained as follows Kfz Getting a pointer to the concrete Visualization Manager instance G4VVisManager pVVisManager G4VVisManager GetConcreteInstance The method GaVVisManager GetConcreteInstance returns NULL if Geant4 is not ready for visu alization Thus your C source code should be protected as follows Liar em How to protect your C source codes in visualization if pVVisManager pVVisManager gt Draw 8 5 2 Visualization of detector components If you have already constructed detector components with logical volumes to which visualization attributes are properly assigned you are almost ready for visualizing detector components All you have to do is to describe proper visualization commands within your C codes using the ApplyCommand method For example the following is sample C source codes to visualize the detector components please gt C source code How to visualize detector components 2 using visualization commands in source codes G4VVisManager pVVisManager G4VVisManager GetConcreteInstance if pVVisManager camera setting etc G4UImanager GetUIpointer gt ApplyCommand vis drawVolume G4UImanager GetUIpointer gt ApplyCommand vis viewer flush 231 Vis
353. ion of the G4OpBoundaryProcess class employs the UNIFIED model A Levin and C Moisan A More Physical Approach to Model the Surface Treatment of Scintillation Counters and its Implementa tion into DETECT TRIUMF Preprint TRI PP 96 64 Oct 1996 of the DETECT program G F Knoll T F Knoll and T M Henderson Light Collection Scintillation Detector Composites for Neutron Detection IEEE Trans Nu cl Sci 35 1988 872 It applies to dielectric dielectric interfaces and tries to provide a realistic simulation which deals with all aspects of surface finish and reflector coating The surface may be assumed as smooth and covered with a metallized coating representing a specular reflector with given reflection coefficient or painted 162 Tracking and Physics with a diffuse reflecting material where Lambertian reflection occurs The surfaces may or may not be in optical contact with another component and most importantly one may consider a surface to be made up of micro facets with normal vectors that follow given distributions around the nominal normal for the volume at the impact point For very rough surfaces it is possible for the photon to inversely aim at the same surface again after reflection of refraction and so multiple interactions with the boundary are possible within the process itself and without the need for relocation by G4Navigator The UNIFIED model provides for a range of different reflection mechanisms The specular lobe
354. ions where a volume is coded with a reflector and is placed into many different mother volumes A limitation is that the skin surface can only have one and the same optical property for all of the enclosed volume s sides The border surface is an ordered pair of physical volumes so in principle the user can choose different optical properties for photons arriving from the reverse side of the same interface For the optical boundary process to use a border surface the two volumes must have been positioned with G4PVPlacement The ordered combination can exist at many places in the simulation When the surface concept is not needed and a perfectly smooth surface exists beteen two dielectic materials the only relevant property is the index of refraction a quantity stored with the material and no restriction exists on how the volumes were positioned The physical surface object also specifies which model the boundary process should use to simulate interactions with that surface In addition the physical surface can have a material property table all its own The usage of this table allows all specular constants to be wavelength dependent In case the surface is painted or wrapped but not a cladding the table may include the thin layer s index of refraction This allows the simulation of boundary effects at the intersection between the medium and the surface layer as well as the Lambertian reflection at the far side of the thin layer This occurs within
355. irtual G4VImportanceAlgorithm virtual G4Nsplit_Weight Calculate G4double ipre G4double ipost G4double init w const 0 The method Calculate takes the arguments ipre ipost importance of the previous cell and the importance of the current cell respectively init w the particles weight It returns the struct class G4Nsplit Weight public G4int fN G4double fW e fN the calculated number of particles to exit the importance sampling fW the weight of the particles The user may have a customized algorithm used by providing a class inheriting from G4VImportanceAlgorithm 22 Toolkit Fundamentals If no customized algorithm is given to the sampler the default importance sampling algorithm is used This algo rithm is implemented in G4ImportanceAlgorithm 3 7 1 5 The Weight Window Technique The weight window technique is a weight based alternative to importance sampling applies splitting and Russian roulette depending on space cells and energy user defines weight windows in contrast to defining importance values as in importance sampling In contrast to importance sampling this technique is not weight blind Instead the technique is applied according to the particle weight with respect to the current energy space cell Therefore the technique is convenient to apply in combination with other variance reduction techniques such as cross section biasing and implicit capture A weigh
356. is automatically clipped to 0 or 1 Alpha is opacity which is not used at present You can use its default value 1 which means opaque in instantiation of G4Colour A G4Colour object is instantiated by giving red green and blue components to its constructor i e G4Colour G4Colour G4double r 1 0 G4double g 1 0 G4double b 1 0 G4double a 1 0 O lt red green blue lt 1 0 The default value of each component is 1 0 That is to say the default colour is white opaque For example colours which are often used can be instantiated as follows G4Colour white white G4Colour white ha0 dbeQuE 2 0 6 d rune G4Colour gray Qu 49m 4955 p JU pcs G4Colour black 0 105 19407 0500 2 Ju Jaulausi G4Colour red GLO Ft Ole OF 00 0 5B Jf sszel G4Colour green QUU 2 0 Webi g T oreen G4Colour blue OO WoO SO 6 7 ehe G4Colour cyan 0 0 OPEN NE Wy EV QT G4Colour magenta 1 0 0 0 1 0 magenta GiCcolour vellon iO O0 00 4 Wy elio It is also possible to instantiate common colours through static public data member functions G4Colour amp White G4Colour amp Gray Static const G4Colour amp Grey Static const G4Colour amp Black static const t E E static const G4Colour amp Red ET E t iE 0 SaicokEeomns Static const G4Colour amp Green Static const G4Colour amp Blue Static const G4Colour amp Cyan Static const G4Colour amp Magenta
357. is filtering trajectories directory All generated filter models are chained together automatically Model configuration commands are generated dynamically when a filter model is instantiated These commands apply directly to that instance See the interactive help for more information on the available commands 8 8 2 Example commands Create a particle filter Configure to pass only gammas Then invert to pass anything other than gammas Set verbose printout and then deactivate filter vis filtering trajectories create particleFilter vis filtering trajectories particleFilter 0 add gamma vis filtering trajectories particleFilter 0 invert true vis filtering trajectories particleFilter 0 verbose true vis filtering trajectories particleFilter 0 active false Create a charge filter Configure to pass only neutral trajectories Set verbose printout Reset filter and reconfigure to pass only negativly charged trajectories vis filtering trajectories create chargeFilter vis filtering trajectories chargeFilter 0 add 0 vis filtering trajectories chargeFilter 0 verbose true vis filtering trajectories chargeFilter 0 reset true vis filtering trajectories chargeFilter 0 add 1 Create an attribute filter named attributeFilter O vis filtering trajectories create attributeFilter Select attribute IMag vis filtering trajectories attributeFilter 0 setAttribute IMag Select trajectories with 2 5 MeV lt IMag lt 1000
358. ist lal in2p3 fr v 15r0 html osc g4 vis ui html Overall OpenScientist Home http openscientist lal in2p3 fr v15rO html osc g4 vis ui html e HEPVis http www pat fnal gov graphics HEPVis www Further information OpenInventor http oss sgi com projects inventor Josie Wernecke The Inventor Mentor Addison Wesley ISBN 0 201 62495 8 Josie Wernecke The Inventor Toolmaker Addison Wesley ISBN 0 201 62493 1 The Open Inventor C Reference Manual Addison Wesley ISBN 0 201 62491 5 8 3 4 HepRepFile The HepRepFile driver creates a HepRep XML file in the HepRepl format suitable for viewing with the WIRED3 HepRep Browser The HepRep graphics format is further described at http www slac stanford edu perl heprep To write just the detector geometry to this file use the command 212 Visualization vis viewer flush Or to also include trajectories and hits after the appropriate vis viewer add trajectories or vis viewer add hits commands just issue cun beamOn 1 HepRepFile will write a file called G4DataO heprep to the current directory Each subsequent file will have a file name like G4Datal heprep G4Data2 heprep etc View the file using the WIRED3 HepRep Browser available from http www slac stanford edu BFROOT www Computing Graphics Wired WIRED3 allows you to pick on volumes trajectories and hits to find out their associated HepRep Attributes such as volume name particle ID
359. ith the two application packages i e Fukui Renderer DAWN and a visual intersection debugger DAVID DAWN and DAVID can be downloaded from the Web How to compile Geant4 with the DAWNFILE driver incorporated is described in Section 8 3 103 Detector Definition and Response If the DAWNFILE driver DAWN and DAVID are all working well in your host machine the visual intersection debugging of physical volume surfaces can be performed as follows Run your Geant4 executable invoke the DAWNFILE driver and execute visualization commands to visualize your detector geometry Idle gt vis open DAWNFILE e eue setting camera etc Idle vis drawVolume Idle vis viewer update Then a file g4 prim which describes the detector geometry is generated in the current directory and DAVID is invoked to read it The description of the format of the file g4 prim can be found from the DAWN web site documentation If DAVID detects intersection of physical volume surfaces it automatically invokes DAWN to visualize the de tector geometry with the intersected physical volumes highlighted See the above sample visualization If no intersection is detected visualization is skipped and the following message is displayed on the console Number of intersected volumes 0 Vrrocongrstuletzone EN Coty Do If you always want to skip visualization set an environmental variable as follows beforehand setenv DAVID NO VIEW 1
360. ithDefault The defaultCutValue is set to 1 0 mm by default Of course you can set the new default cut value in the constructor of your physics list class as shown below Example 2 15 Set the default cut value ExN04PhysicsList ExN04PhysicsList G4VUserPhysicsList default cut value 1 0mm defaultCutValue 1 0 mm The SetDefaultCutValue method in G4VUserPhysicsList may also be used and the run setCut command may be used to change the default cut value interactively WARNING DO NOT change cut values inside the event loop Cut values may however be changed between runs An example implementation of Set Cuts is shown below Example 2 16 Example implementation of the SetCuts method void ExN03PhysicsList SetCuts set cut values for gamma at first and for e second and next for et because some processes for e e need cut values for gamma SetCutValue cutForGamma gamma SetCutValue cutForElectron e SetCutValue cutForElectron e 12 Getting Started with Geant4 Running a Simple Example Beginning with Geant4 version 5 1 it is now possible to set production thresholds for each geometrical region This new functionality is described in Section 5 5 2 5 How to Specify Physics Processes 2 5 1 Physics Processes Physics processes describe how particles interact with materials Geant4 provides seven major categories of pro cesses electromagnetic hadro
361. ive hh int main Run Manager G4RunManager runManager new G4RunManager Detector components runManager gt set_userInitialization new MyDetectorConstruction runManager set userInitialization new MyPhysicsList UserAction classes runManager set userAction new MyRunAction runManager set userAction new MyPrimaryGeneratorAction runManager set userAction new MyEventAction runManager gt set userAction new MySteppingAction ifdef G4VIS USE G4VisManager visManager new G4VisExecutive visManager gt initialize endif Event loop Define G UI terminal G4UIsession session new G4UIterminal session gt sessionStart delete session delete runManager ifdef G4VIS USE delete visManager fendif return 0 Gilel ie Came Useful information on incorporated visualization drivers can be displayed in initializing the Visualization Man ager This is done by setting the verbosity flag to an appropriate string Simple graded message scheme give first letter or a digit 0 1 2 3 4 5 6 quiet Nothing is printed startup Startup and endup messages are printed errors Jy ce end ePrens warnings and warnings confirmations and confirming messages parameters and parameters of scenes and views all and everything available For example in your main function write the following code G4VisM
362. jects become independent copies of each of the assembled logical volumes This class is particularly useful when there is a need to create a regular pattern in space of a complex component which consists of different shapes and can t be obtained by using replicated volumes or parametrised volumes see also Figure 4 2 reful usage of G4AssemblyVolume must be considered though in order to avoid cases of proliferation of physical volumes all placed in the same mother ae i Figure 4 2 Examples of assembly of volumes 88 Detector Definition and Response 4 1 6 1 Filling an assembly volume with its daughters Participating logical volumes are represented as a triplet of lt logical volume translation rotation gt G4AssemblyTriplet class The adopted approach is to place each participating logical volume with respect to the assembly s coordinate system according to the specified translation and rotation 4 1 6 2 Assembly volume placement An assembly volume object is composed of a set of logical volumes imprints of it can be made inside a mother logical volume Since the assembly volume class generates physical volumes during each imprint the user has no way to specify identifiers for these An internal counting mechanism is used to compose uniquely the names of the physical volumes created by the invoked MakeImprint method s The name for each of the physical volume is generated with the following format av
363. ke pEventManager KeepTheCurrentEvent so that it is kept in G4Run object This should be quite useful if you simulate quite many events and want to visualize only the most interest ones after the long execution Given the memory size of an event and its contents may be large it is the user s responsibility not to keep unnecessary events Example 6 5 G4UserEventAction class G4UserEventAction PubleKcr G4UserEventAction virtual G4UserEventAction virtual void BeginOfEventAction const G4Event virtual void EndOfEventAction const G4Event protected G4EventManager fpEventManager G4UserStackingAction This class has three virtual methods CLassifyNewTrack NewStage and PrepareNewEvent which the user may override in order to control the various track stacking mechanisms ExampleN04 could be a good example to understand the usage of this class ClassifyNewTrack is invoked by G4StackManager whenever a new G4Track object is pushed onto a stack by G4EventManager ClassifyNewTrack returns an enumerator G4ClassificationOfNewTrack whose value indicates to which stack if any the track will be sent This value should be determined by the user G4ClassificationOfNewTrack has four possible values fUrgent track is placed in the urgent stack fWaiting track is placed in the waiting stack and will not be simulated until the urgent stack is empty fPostpone track is postponed to the next e
364. l omittable Define the name of the integer parameter and set the omittable flag If omittable is true you should define the default value using the next method void SetDefaultValue G4int defVal Define the default value of the integer parameter G4int GetNewIntValue G4String paramString Convert G4String parameter value given by the SetNewValue method of your messenger into integer G4String convertToString G4int currVal Convert the current integer value to G4String which should be returned by the Get Current Value method of your messenger G4UIcmdWithADouble This is a G amp UIcommand derived class which takes one double type parameter G4UIcmdWithADouble char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramName G4bool omittable Define the name of the double parameter and set the omittable flag If omittable is true you should define the default value using the next method void SetDefaultValue G4double defVal Define the default value of the double parameter G4double GetNewDoubleValue G4String paramString Convert G4String parameter value given by the Set NewValue method of your messenger into double G4String convertToString G4double currVal Convert the current double value to G4String which should be returned by the GetCurrentValue method of your messenger G4UlcmdWithAString
365. lNavigation provides location and distance computation functions for geometries containing place ment physical volumes with voxels Internally a stack of voxel information is maintained Private functions allow for isotropic distance computation to voxel boundaries and for computation of the next voxel in a spec ified direction G4Parameterised Navigation provides location and distance computation functions for geometries containing parameterised volumes with voxels Voxel information is maintained similarly to GAVoxelNavigation but computation can also be simpler by adopting voxels to be one level deep only unrefined or 1D optimisation G4ReplicaNavigation provides location and distance computation functions for replicated volumes 92 Detector Definition and Response In addition the navigator maintains a set of flags for exiting entry optimisation A navigator is not a singleton class this is mainly to allow a design extension in future e g geometrical event biasing 4 1 8 1 Navigation and Tracking The main functions required for tracking in the geometry are described below Additional functions are provided to return the net transformation of volumes and for the creation of touchables None of the functions implicitly requires that the geometry be described hierarchically SetWorldVolume Sets the first volume in the hierarchy It must be unrotated and untranslated from the origin LocateGlobalPointAndSetup
366. lable to the user to control the execution of the simulation After Chapter 2 Chapters 6 and 7 are of formeost importance to the new application developer The display of detector geometry tracks and events may be incorporated into a simulation application by using the tools described in Chapter 8 Visualization Chapter 9 Examples provides a set of novice and advanced simulation codes which may be compiled and run as is from the Geant4 source code These examples may be used as educational tools or as base code from which more complex applications are developed Chapter 2 Getting Started with Geant4 Running a Simple Example 2 1 How to Define the main Program 2 1 1 A Sample main Method The contents of main will vary according to the needs of a given simulation application and therefore must be supplied by the user The Geant4 toolkit does not provide a main method but a sample is provided here as a guide to the beginning user Example 2 1 is the simplest example of main required to build a simulation program Example 2 1 Simplest example of main include G4RunManager hh include G4UImanager hh include ExN01DetectorConstruction hh include ExN01PhysicsList hh include ExN01PrimaryGeneratorAction hh int main construct the default run manager G4RunManager runManager new G4RunManager set mandatory initialization classes runManager gt SetUserInitialization new ExN0lD
367. lar generators SetAngularGenerator G4V BremAngularDistribution distribution e SetAngularGenerator const G4String amp name Currently three angular generators are available G4ModifiedTsai 2BNGenerator and 2BSGenerator G4ModifiedTsai is set by default but it can be forced using the string tsai 2BNGenerator and 2BSGenerator can be set using the strings 2bs and 2bn Information regarding conditions of use performance and energy limits of different models are available in the Physics Reference Manual and in the Geant4 Low Energy Electromagnetic Physics Working Group homepage Other options G4LowEnergyBremsstrahlung class are SetCutForLowEnSecPhotons G4double Options can also be set in the G4LowEnergyPhotoElectric class that allow the use of alternative photoelectron angular generators e SetAngularGenerator G4VPhotoElectricAngularDistribution distribution e SetAngularGenerator const G4String amp name Currently three angular generators are available G4PhotoElectricAngularGeneratorSimple G4PhotoElectricAngularGeneratorSauterGavrilla and G4PhotoElectricAngularGeneratorPolarized 146 Tracking and Physics G4PhotoElectricAngularGeneratorSimple is set by default but it can be forced using the string default G4PhotoElectricAngularGeneratorS auterGavrilla and G4PhotoElectricAngularGeneratorPolarized can be set us ing the strings standard and polarized Information regarding conditions of use performa
368. lat method of the specified engine The user must take care of the engine objects he she instantiates 3 Skipping the static generator and instantiating a distribution object random values are shot using fire methods NOT static defined for each distribution class The user must instantiate a distribution object giving as argument to the constructor an engine by pointer or by reference By doing so the engine will be associated to the distribution object and the generator mechanism will be by passed by using the basic flat method of that engine In this guide we ll only focus on the static generator point 1 since the static interface of HEPRandom is the only one used within the Geant4 toolkit 3 2 2 1 HEPRandom engines The class HepRandomEngine is the abstract class defining the interface for each random engine It implements the getSeed and get Seeds methods which return the initial seed value and the initial array of seeds if any respectively Many concrete random engines can be defined and added to the structure simply making them inheriting from HepRandomEngine Several different engines are currently implemented in HepRandom we describe here five of them HepJamesRandom It implements the algorithm described in F James Comp Phys Comm 60 1990 329 for pseudo random number generation This is the default random engine for the static generator it will be invoked by each distri bution class unles
369. ld public MyParallelWorld G4String worldName virtual MyParallelWorld public virtual void Construct endif A parallel world must have its unique name which should be set to the G4VUserParallelWorld base class as an argument of the base class constructor The world physical volume of the parallel world is provided by the G4RunManager as a clone of the mass geometry In the Construct virtual method of the user s class the pointer to this cloned world physical volume is available through the GetWorld method defined in the base class The user should fill the volumes in the parallel world by using this provided world volume For a logical volume in a parallel world the material 130 Detector Definition and Response pointer can be NULL Even if specified a valid material pointer it will not be taken into account by any physics process Example 4 18 An example source code of a concrete user parallel world class include MyParallelWorld hh include G4LogicalVolume hh include G4VPhysicalVolume hh include G4Box hh include G4PVPlacement hh MyParallelWorld MyParallelWorld G4String worldName G4VUserParallelWorld worldName 7 MyParallelWorld MyParallelWorld 7 void MyParallelWorld Construct G4VPhysicalVolume ghostWorld GetWorld G4LogicalVolume worldLogical ghostWorld gt GetLogicalVolume place volumes in the parallel world here For example
370. learly recognized in either the coordinate system of the volume the global coordinate system or the coordinate system of the daughters involved Also notice that certain errors will be missed unless a line is supplied in precisely the correct path Unfortunately it is hard to predict which lines are best at uncovering potential geometry errors Instead the geometry testing code uses a grid of lines in the hope of at least uncovering gross geometry errors More subtle errors could easily be missed Another difficult issue is roundoff error For example daughters C and D lie precisely next to each other It is possible due to roundoff that one of the intersections points will lie just slightly inside the space of the other In addition a volume that lies tightly up against the outside of its mother may have an intersection point that just slightly lies outside the mother To avoid spurious errors caused by roundoff a rather generous tolerance of 0 1 micron is used by default This tolerance can be adjusted as needed by the application through the run time command geometry test tolerance new value Finally notice that no mention is made of the possible daughter volumes of A B C and D To keep the code simple only the immediate daughters of a volume are checked at one pass To test these granddaughter volumes the daughters A B C and D each have to be tested themselves in turn To make this more automatic an optional recursive al
371. lel world the user can define volumes in arbitrary manner with sensitivity regions shower parameteri zation setups and or importance weight for biasing Volumes in different worlds can overlap Here are restrictions to be considered for the parallel geometry Materials production thresholds and EM field are used only from the mass geometry Even if such physical quantities are defined in a parallel world they do not affect to the simulation e Although all worlds will be comprehensively taken care by the G4Transportation process for the naviga tion each parallel world must have its own process assigned to achieve its purpose For example in case the user defines a sensitive detector to a parallel world a process dedicated to the parallel world is responsible to invoke this detector The G4SteppingManager treats only the detectors in the mass geometry For this case of detector sensitivity defined in a parallel world a G4ParallelWorldScoringProcess process must be defined in the physics list see Section 4 7 3 4 7 2 Defining a parallel world A parallel world should be defined in the Construct virtual method of the user s class derived from the abstract base class G4VUserParallelWorld Example 4 17 An example header file of a concrete user parallel world class ifndef MyParallelWorld_h define MyParallelWorld_h 1 include globals hh include G4VUserParallelWorld hh class MyParallelWorld public G4VUserParallelWor
372. lf to its associated data store and hence data set objects Thus each data set is assumed to be formulated to calculate cross sections for one and only one type of process Of course this does not prevent different data sets from sharing common data and or calculation methods as in the case of the G4HadronCrossSections class mentioned above Indeed G4VCrossSectionDataSet specifies only the abstract interface between physics processes and their data sets and leaves the user free to implement whatever sort of underlying structure is appropriate The current implementation of the data set G4HadronCrossSections reuses the total cross sections for inelastic and elastic scattering radiative capture and fission as used with GHEISHA to provide cross sections for calculation of the respective mean free paths of a given particle in a given material Cross sections for low energy neutron transport The cross section data for low energy neutron transport are organized in a set of files that are read in by the corresponding data set classes at time zero Hereby the file system is used in order to allow highly gran ular access to the data The root directory of the cross section directory structure is accessed through an environment variable Neut ronHPCrossSections which is to be set by the user The classes access ing the total cross sections of the individual processes i e the cross section data set classes for low energy neutron transport are
373. libraries are also required to set the similar environmental variables G4VIS BUILD DRIVERNAME DRIVER and G4VIS USE DRIVERNAME to 1 All visualization drivers independent of external libraries e g DAWNFILE and VRMLFILE drivers need not such setting But you must prepare a proper visualization manager class and a proper main function anyway See below For all visualization drivers available in your Geant4 executable the C pre processor flags GAVIS USE DRIVERNAME are automatically set by config G4VIS USE gmk in compilation Sim ilarly for all visualization drivers incorporated into the Geant4 libraries the C pre processor flags G4VIS BUILD DRIVERNAME DRIVER are automatically set by config G4VIS_BUILD gmk in installa tion 2 10 3 How to Incorporate Visualization Drivers into an Executable You can realize use visualization driver s you want in your Geant4 executable These can only be from the set installed in the Geant4 libraries You will be warned if the one you request is not available In order to realize visualization drivers you must instantiate and initialize a subclass of G4VisManager that implements the pure virtual function RegisterGraphicsSystems This subclass must be compiled in the user s domain to force the loading of appropriate libraries in the right order The easiest way to do this is to use G4VisExecut ive a provided class with included implementa
374. ll cells physical volumes or replicas of a given geometry e be customizable Standard scoring must be provided for quantities such as tracks entering a cell average weight of entering tracks energy of entering tracks and collisions inside the cell A number of scorers have been created for this specific appliction G4PSNofCollision This scorer records the number of collisions that occur within a scored volume cell There is the additional possibility to take into account the track weight whilst scoring the number of collisions via the following command G4PSNofCollision scorerl new G4PSNofCollision psName CollWeight Scorerl Weighted true GAPS Population This scores the number of tracks within in a given cell per event G4PSTrackLength The track lengths within a cell are measured and if additionally the result is desired to be weighted then the following code has to be implemented G4PSTrackLength scorer5 new G4PSTrackLength psName SLW Scorer5 Weighted true Further if the energy track flux is required then the following should be implemented G4PSTrackLength scorer6 new G4PSTrackLength psName SLWE scorer6 Weighted true Scorer6 MultiplyKineticEnergy true MFDet gt RegisterPrimitive scorer6 Alternatively to measure the flux per unit velocity then G4PSTrackLength scorer7 new G4PSTrackLength psName SLW V Scorer7 Weighted true Scorer7 DivideByVelocity true
375. ll only a proposal If during this step the particle crosses a boundary then the transportation will limit the step at a length smaller than the Ionisation so the particle will still see and cross the relevant boundary and another step will occur on the other side of that boundary In summary the production threshold range and its equivalent in energy are not utilised as a tracking cut A particle is not abandoned by Geant4 below a certain range energy unless the user registers a process to do this by him her self FAQ 6 Visualization I have set G4VIS environmental variables but visualization does not appear to be enabled This might be because you set the environment variables after already compiling The environment variables control C pre processor macros of the same name and therefore influence what code gets com piled It is suggested to proceed with the following manual procedure to correct the current installation G4VIS_BUILD_ name _DRIVERG4VIS_USE_ name cd SG4INSTALL source visualization gmake clean gmake cd SG4INSTALL source interfaces gmake clean gmake cd G4INSTALL source gmake libmap setenv G4WORKDIR your working directory or export cd your application directory gmake clean gmake Configure the environment according to the installation making sure to unset the G4WORKDIR envi ronment variable if set FAQ 7 User Support Policy Q If I need to discuss technical matters speci
376. ll be composed The constructor will new a vector of pointers to G4Isotopes and a vector of doubles to store their relative abundances Finally the method to add an isotope must be invoked for each of the desired pre existing isotope objects providing their addresses and relative abundances At the last isotope entry the system will automatically compute the effective atomic number effective number of nucleons and effective mass of a mole and will store this element in the elements table A few quantities with physical meaning or not which are constant in a given element are computed and stored here as derived data members Using the internal Geant4 database a G4Element can be accessed by atomic number or by atomic symbol Al Fe Pb In that case G4Element will be found from the list of existing elements or will be constructed using data from the Geant4 database which is derived from the NIST database of elements and isotope compositions Thus the natural isotope composition can be built by default The same element can be created as using the NIST database with the natural composition of isotopes and from scratch in user code with user defined isotope composition 4 2 2 3 G4Material A G4Material object has a name density physical state temperature and pressure by default the standard con ditions the number of elements and a vector of pointers to such elements a vector of the fraction of mass for each element a v
377. ll be used A summary of the available methods is presented here public virtual void Initialize main entry point of Geant4 kernel initialization protected virtual void InitializeGeometry geometry construction protected virtual void InitializePhysics physics processes construction public virtual void BeamOn G4int n event main entry point of the event loop protected virtual G4bool ConfirmBeamOnCondition check the kernel conditions for the event loop protected virtual void RunInitialization prepare a run protected virtual void DoEventLoop G4int n events manage an event loop protected virtual G4Event GenerateEvent G4int i event generation of G4Event object protected virtual void AnalyzeEvent G4Event anEvent storage analysis of an event protected virtual void RunTermination terminate a run public virtual void DefineWorldVolume GAVPhysicalVolume worldVol set the world volume to G4Navigator public virtual void AbortRun abort the run 43 Toolkit Fundamentals 3 4 4 2 Customizing the Event Loop In G4RunManager the event loop is handled by the virtual method DoEvent Loop This method is imple mented by a for loop consisting of the following steps 1 construct a G4Event object and assign to it primary vertex es and primary particles This is done by the virtual GeneratePrimaryEvent method 2
378. lou tionExcitationBorn G4FinalStateExcitationBorn gt tionIonisationBorn G4FinalStatelIonisationBorn gt tionlonisationRudd G4FinalStatelonisationRudd tionExcitationMillerGreen G4FinalStateExcitationMillerGreen gt tionChargeDecrease G4FinalStateChargeDecrease gt tionChargelncrease G4FinalStateChargelncrease gt Tracking and Physics EV I POO OUUO OO e Uere 9oov00 0000 OO 11 11 OOCOOU OOO CO rm yer norton WOOQOU00 OOS 44 Note that in the above example alpha particles are helium atoms ionised twice and helium particles are neutral helium atoms The definition of particles in the physics list may be for example implemented as follows Uc ee OMS DOO 4 oco99099999 7 porte Oo9990990999 rer tere ela 9 018 1010 8 clele amare include G4DNAGenericlonsManager hh void MicrodosimetryPhysicsList ConstructBaryons 1 Aliconstrauce locus Geant4 DNA particles G4DNAGenericIonsManager genericlonsManager genericIonsManager G4DNAGenericIonsManager Instance genericIonsManager gt GetIon alpha genericIonsManager gt GetIon alpha genericlonsManager GetIon helium genericlonsManager GetIon hydrogen ae Bong ODDS 44 HEN oeoo909909oo rete ooo99 090900o90 9 rer tee COOSDOUOOOOD x VIS To run the Geant4 DNA extension data files need to be copied by the user to his her code repository These files are distributed together with the Geant4 release The user should set the environment variable
379. lsite com 8 3 9 RayTracer This driver was developed by Makoto Asai and Minamimoto Hirosihma Instutute of Technology It performs ray tracing visualization using the tracking routines of Geant4 It is therefore available for every kinds of shapes solids which Geant4 can handle It is also utilized for debugging the user s geometry for the tracking routines of Geant4 It is well suited for photo realistic high guality output for presentation and for intuitive debugging of detector geometry It produces a JPEG file This driver is by default listed in the available visualization drivers of user s application Some pieces of geometries may fail to show up in other visualization drivers due to algorithms those drivers use to compute visualizable shapes and polygons but RayTracer can handle any geometry that the Geant4 navigator can handle Because RayTracer in essence takes over Geant4 s tracking routines for its own use RayTracer cannot be used to visualize Trajectories or hits 218 Visualization An X Window version called RayTracerX can be selected by setting G4VIS BUILD RATRACERX DRIVER at Geant4 library build time and G4VIS USE RAYTRACERX at application user code build time assuming you use the standard visualization manager G4VisExecut ive or an equally smart vis manager RayTracerX builds the same jpeg file as RayTracer but simultaneously renders to screen so you can watch as rendering grows progressively smoother
380. lt cross sections The defaults for total cross section data and calculations have been encapsulated in the singleton class G4HadronCrossSections Each hadronic process G4HadronInelasticProcess G4HadronElasticProcess G4HadronFissionProcess and G4HadronCaptureProcess comes already equipped with a cross section data store and a default cross section data set The data set objects are really just shells that invoke the singleton G4HadronCrossSections to do the real work of calculating cross sections The default cross sections can be overridden in whole or in part by the user To this end the base class G4HadronicProcess has a get method G4CrossSectionDataStore GetCrossSectionDataStore which gives public access to the data store for each process The user s cross section data sets can be added to the data store according to the following framework 151 Tracking and Physics cAHadron ue ProcessEdPBRoOCcessi E MyCrossSectionDataSet myDataSet aProcess GetCrossSectionDataStore AddDataSet amp MyDataSet The added data set will override the default cross section data whenever so indicated by its IsApplicable method In addition to the get method G4HadronicProcess also has the method void SetCrossSectionDataStore G4CrossSectionDataStore which allows the user to completely replace the default data store with a new data store It should be noted that a process does not send any information about itse
381. mary event One possible use is the following Within an event a G4HEPEvtInterface class object instantiated with a minimum bias event file is accessed 20 times and another G4HEPEvtinterface class object instantiated with a signal event file is accessed once Thus this event represents a typical signal event of LHC overlapping 20 minimum bias events It should be noted that a simulation of event overlapping can be done by merging hits and or digits associated with several events and these events can be simulated independently Digitization over multiple events will be mentioned in Section 4 5 3 7 Event Biasing Techniques 3 7 1 Scoring Geometrical Importance Sampling and Weight Roulette Geant4 provides event biasing techniques which may be used to save computing time in such applications as the simulation of radiation shielding These are geometrical splitting and Russian roulette also called geometrical 48 Toolkit Fundamentals importance sampling and weight roulette Scoring is carried out by G4MultiFunctionalDetector see Section 4 4 5 and Section 4 4 6 using the standard Geant4 scoring technique Biasing specific scorers have been implemented and are described within G4MultiFunctionDetector documentation In this chapter it is assumed that the reader is familiar with both the usage of Geant4 and the concepts of importance sampling More detailed documentation may be found in the documents Latest development in importance sam
382. material is used in regions with different cut values the processes need to prepare several different cross sections for that material The G4ProductionCutsTable has G4MaterialCutsCouple objects each of which consists of a material paired with a cut value These G4MaterialCutsCouples are numbered with an index which is the same as the index of a G4PhysicsVector for the corresponding G4MaterialCutsCouplein the G4PhysicsTable The list of Material CutsCouples used in the current geometry setup is updated before starting the event loop in each run 5 6 3 File I O for the Physics Table Calculated physics tables for Standard electromagnetic processes can be stored in files The user may thus elim inate the time required for the calculation of physics tables by retrieving them from the files Using the built in user command storePhysicsTable see Section 7 1 stores physics tables in files Informa tion on materials and cuts defined in the current geometry setup are stored together with physics tables because calculated values in the physics tables depend on MaterialCutsCouple Note that physics tables are calculated before the event loop not in the initialization phase So at least one event must be executed before using the storePhysicsTable command 178 Tracking and Physics Calculated physics tables can be retrieved from files by using the retrievePhysicsTable command Materials and cuts from files are compared with those def
383. mation OpenGL and Mesa http www opengl org http www mesa3d org e Geant4 Visualization Tutorial using the OpenGL Graphics System 8 3 3 Openlnventor These drivers were developed by Jeff Kallenbach FNAL and Guy Barrand IN2P3 based on the Hepvis class library originated by Joe Boudreau Pittsburgh University The OpenInventor drivers and the Hepvis class library are based on the well established OpenInventor technology for scientific visualization They have high extendibil ity They support high interactivity e g attribute e diting of picked objects Some OpenInventor viewers support stereoscopic effects It is also possible to save a visualized 3D scene as an OpenInventor formatted file and re visualize the scene afterwards Because it is connected directly to the Geant4 kernel using same language as that kernel C OpenInventor systems can have direct access to Geant4 data geometry trajectories etc Because OpenInventor uses OpenGL for rendering it supports lighting and transparency Openlnventor provides thumbwheel control to rotate and zoom OpenInventor supports picking to ask about data Control Clicking on a volume turns on rendering of that volume s daughters Shift Clicking a daughter turns that rendering off If modeling opaque solid effect is like opening a box to look inside Further information HEPVis and OpenScientist e Geant4 Inventor Visualization with OpenScientist http openscient
384. ment that uses it However the same rotation matrix can be re used for many volumes Currently boolean operations are not implemented at the level of physical volume So pMany must be false However an alternative implementation of boolean operations exists In this approach a solid can be created from the union intersection or subtraction of two solids See Section 4 1 2 2 above for an explanation of this The mother volume must be specified for all volumes except the world volume An alternative way to specify a Placement utilizes a different method to place the volume The solid itself is moved by rotating and translating it to bring it into the system of coordinates of the mother volume This active method can be utilized using the following constructor 78 Detector Definition and Response G4PVPlacement G4Transform3D solidTransform G4LogicalVolume pCurrentLogical const G4String pName G4LogicalVolume pMotherLogical G4bool pMany G4int pCopyNo G4bool pSurfChk false An alternative method to specify the mother volume is to specify its placed physical volume It can be used in either of the above methods of specifying the placement s position and rotation The effect will be exactly the same as for using the mother logical volume Note that a Placement Volume can still represent multiple detector elements This can happen if several copies exist of the mother logical volume Then different detector elements will belong
385. mesh score dumpQuantityToFile command or all scores in a mesh Score dumpAllQuantitiesToFile command to a file The default file format is the simple CSV To alter nate the file format the user should overwrite G4VScoreWriter class and register it to G4ScoringManager Please refer to examples extended runAndi Event RI E03 for the detail 134 Chapter 5 Tracking and Physics 5 1 Tracking 5 1 1 Basic Concepts Philosophy of Tracking All Geant4 processes including the transportation of particles are treated generically In spite of the name track ing particles are not transported in the tracking category G4TrackingManager is an interface class which bro kers transactions between the event track and tracking categories An instance of this class handles the message passing between the upper hierarchical object which is the event manager and lower hierarchical objects in the tracking category The event manager is a singleton instance of the G4EventManager class The tracking manager receives a track from the event manager and takes the actions required to finish tracking it G4TrackingManager aggregates the pointers to G4SteppingManager G4Trajectory and G4UserTrackingAction Also there is a use relation to G4Track and G4Step G4SteppingManager plays an essential role in tracking the particle It takes care of all message passing between objects in the different categories relevant to transporting a
386. meterisation geometrical biasing particle scoring readout geometries etc and can overlap with the mass geometry defined for the tracking The par allel transportation will be activated only after the registration of the parallel geometry in the detector descrip tion setup see Section Section 4 7 for how to define a parallel geometry and register it to the run manager The G4TransportationManager provides all the utilities to verify retrieve and activate the navigators as sociated to the various parallel geometries defined 4 1 8 4 Fast navigation in regular patterned geometries and phan toms Since release 9 1 of Geant4 a specialised navigation algorithm has been introduced to allow for optimal memory use and extremely efficient navigation in geometries represented by a regular pattern of volumes and particularly three dimensional grids of boxes A typical application of this kind is the case of a DICOM phantoms for medical physics studies The class G4RegularNavigation is used and automatically activated when such geometries are defined It is required to the user to implement a parameterisation of the kind GGPhantomParameterisation and place the parameterised volume containing it in a container volume so that all cells in the three dimensional grid voxels completely fill the container volume This way the location of a point inside a voxel can be done in a fast way transforming the position to the coordinate system of the containe
387. method is called and the track is assigned to the appropriate stack Example 6 6 G4UserStackingAction include G4ClassificationOfNewTrack hh class G4UserStackingAction pubis G4UserStackingAction virtual G4UserStackingAction protected G4StackManager stackManager virtual G4ClassificationOfNewTrack ClassifyNewTrack const G4Track 190 User Actions G4UserTrackingAction 191 User Actions G4UserSteppingAction Example 6 8 G4UserSteppingAction G4UserSteppingAction hh Descriptions This class represents actions taken place by the user at each end of stepping VVV I class G4UserSteppingAction VAM VVV A Constructor and destructor G4UserSteppingAction virtual G4UserSteppingAction Member functions virtual void UserSteppingAction const G4Step Member data G4SteppingManager fpSteppingManager 6 3 User Information Classes Additional user information can be associated with various Geant4 classes There are basically two ways for the user to do this derive concrete classes from base classes used in Geant4 These are classes for run hit digit trajectory and tra jectory point which are discussed in Section 6 2 for G4Run Section 4 4 for G4VHit Section 4 5 for G4VDigit and Section 5 1 6 for G4VTrajectory and G4VTrajectoryPoint create concrete classes from provided abstract base classes and associate them with classes use
388. metry do not allow envelopes to be defined This may be the case with a geometry coming from a CAD system Since such a geometry is flat a parallel geometry must be used to define the envelopes Another interesting case involves defining an envelope which groups the electromagnetic and hadronic calorime ters of a detector into one volume This may be useful when parameterizing the interaction of charged pions You will very likely not want electrons to see this envelope which means that ghost geometries have to be organized by particle flavours Using ghost geometries implies some more overhead in the parameterisation mechanism for the particles sensitive to ghosts since navigation is provided in the ghost geometry by the G4FastSimulationManagerProcess Usually however only a few volumes will be placed in this ghost world so that the geometry computations will remain rather cheap In the existing implementation temporary implementation with G4Region but before parallel geometry implementation you may only consider ghost G4Regions with just one root G4LogicalVolume The G4GlobalFastSimulationManager provides the construction of the ghost geometry by making first an empty clone of the world for tracking provided by the construct method of your G4VUserDetectorConstruction con crete class You provide the placement of the G4Region root G4LogicalVolume relative to the ghost world coor dinates in the G4FastSimulationManager objects A ghost G4R
389. mitiveScorer It defines a virtual method G4bool Accept const G4Step that should return true if this particular step should be scored by the G4VSensitiveDetector or G4VPrimitiveScorer While the user can implement his her own filter class Geant4 version 8 0 provides the following concrete filter classes G4SDChargedFilter All charged particles are accepted G4SDNeutralFilter All neutral particles are accepted G4SDParticleFilter Particle species which are registered to this filter object by Add particle_name are accepted More than one species can be registered G4SDKineticEnergyFilter A track with kinetic energy greater than or equal to EKmin and smaller than EKmin is accepted EKmin and EKmax should be defined as arguments of the constructor The default values of EKmin and EKmax are zero and DBL_MAX G4SDParticleWithEnergyFilter Combination of G4SDParticleFilter and G4SDParticleWithEnergyFilter The use of the G4SDParticleFilter class is demonstrated in Example 4 15 where filters which accept gamma electron positron and electron positron are defined 4 4 8 Scoring for Event Biasing Scoring for Event Biasing described in Section 3 7 is a very specific use case whereby particle weights and fluxes through importance cells are required The goals of the scoring technique are to 126 Detector Definition and Response appraise particle quantities related to special regions or surfaces be applicable to a
390. more than one G4MultiFunctionalDetector object As mentioned in Section 4 4 1 each G4VPrimitiveScorer generates one G4THitsMap object per event The name of the map object is the same as the name of the primitive scorer Each of the concrete primitive scorers listed in Section 4 4 6 generates a G4THitsMap G4double that maps a G4double value to its key integer number By default the key is taken as the copy number of the G4LogicalVolume to which G4MultiFunctionalDetector is assigned In case the logical volume is uniquely placed in its mother volume and the mother is replicated the copy number of its mother volume can be taken by setting the second argument of the G4VPrimitiveScorer constructor depth to 1 i e one level up Furthermore in case the key must consider more than one copy number of a different geometry hierarchy the user can derive his her own primitive scorer from the provided concrete class and implement the GetIndex G4Step virtual method to return the unique key Example 4 15 shows an example of primitive sensitivity class definitions 122 Detector Definition and Response Example 4 15 An example of defining primitive sensitivity classes taken from ExN07DetectorConstruction void ExN07DetectorConstruction SetupDetectors i G4String filterName particleName G4SDParticleFilter gammaFilter new G4SDParticleFilter filterName gammaFilter particleName gamma G4SDParticleFilter electronFilter n
391. mple processes the AddAtRestProcess AddContinuousProcess and AddDis creteProcess methods may be used G4ProcessManager is able to turn some processes on or off during a run by using the ActivateProcess and InActivateProcess methods These methods are valid only after process registration is complete so they must not be used in the Prelnit phase 13 Getting Started with Geant4 Running a Simple Example The G4VUserPhysicsList class creates and attaches G4ProcessManager objects to all particle classes defined in the ConstructParticle method 2 5 3 Specifying Physics Processes G4VUserPhysicsList is the base class for a mandatory user class see Section 2 1 in which all physics pro cesses and all particles required in a simulation must be registered The user must create a class derived from G4VUserPhysicsList and implement the pure virtual method Const ructProcess For example if just the G4Geantino particle class is required only the transportation process need be registered The ConstructProcess method would then be implemented as follows Example 2 17 Register processes for a geantino void ExNO1PhysicsList ConstructProcess Define transportation process AddTransportation Here the AddTransportation method is provided in the G4VUserPhysicsList class to register the G4Transportation class with all particle classes The G4Transportation class and or related classes describes t
392. mulation view though both are the same particle photons with different energies For example optical photon is used for Cerenkov light and scintillation light f geantino charged geantino Geantino and charged geantino are virtual particles for simulation which do not interact with materials and undertake transportation processes only nuclei Any kinds of nucleus can be used in Geant4 such as alpha He 4 uranium 238 and excited states of carbon 14 In addition Geant4 provides hyper nuclei Nuclei in Geant4 are divided into two groups from the viewpoint of implementation a light nuclei Light nuclei frequently used in simulation e g alpha deuteron He3 triton b heavy nuclei including hyper nuclei Nuclei other than those defined in the previous category Note that G4ParticleDefinition represents nucleus state and G4DynamicParticle represents atomic state with some nucleus Both alpha particle with charge of 2e and helium atom with no charge aggregates the same particle definition of G4Alpha but different G4DynamicParticle objects should be assigned to them Details can be found below Short lived particles Particles with very short life time decay immediately and are never tracked in the detector geometry These particles are usually used only inside physics processes to implement some models of interactions G4VShortLivedParticle is provided as the base class for these particles All classes related to particles in thi
393. mum performance is a goal The choice of stepper depends on the type of field magnetic or general A general field can be an electric or electromagnetic field it can be a magnetic field or a user defined field which requires a user defined equation of motion For a general field several steppers are available as alternatives to the default G4ClassicalRK4 G4int nvar 8 To integrate time amp energy oe in addition to position momentum G4EgMagElectricField fEquation new G4EqMagElectricField fEMfield fStepper new G4SimpleHeum fEquation nvar 3rd order a good alternative to ClassicalRK fStepper new G4SimpleRunge fEquation nvar 2nd order for less smooth fields fStepper new G4CashKarpRKF45 fEquation 4 5th order for very smooth fields Specialized steppers for pure magnetic fields are also available They take into account the fact that a local tra jectory in a slowly varying field will not vary significantly from a helix Combining this in with a variation the Runge Kutta method can provide higher accuracy at lower computational cost when large steps are possible G4Mag UsualEgRhs fEquation new G4Mag UsualEgRhs fMagneticField fStepper new G4HelixImplicitEuler fEquation Note that for magnetic field that do not vary with time the default number of variables suffices dg E m fStepper new G4HelixExplicitEuler fEquation fStepper new G4HelixSimpleRunge fEquatio
394. n You can choose an alternative stepper either when the field manager is constructed or later At the construction of the ChordFinder it is an optional argument G4ChordFinder G4MagneticField itsMagField G4double stepMinimum 1 0e 2 mm G4MagIntegratorStepper pItsStepper 0 To change the stepper at a later time use pChordFinder GetIntegrationDriver RenewStepperAndAdjust newStepper 4 3 2 5 How to Adjust the Accuracy of Propagation In order to obtain a particular accuracy in tracking particles through an electromagnetic field it is necessary to adjust the parameters of the field propagation module In the following section some of these additional parameters are discussed 114 Detector Definition and Response When integration is used to calculate the trajectory it is necessary to determine an acceptable level of numerical imprecision in order to get performant simulation with acceptable errors The parameters in Geant4 tell the field module what level of integration inaccuracy is acceptable In all quantities which are integrated position momentum energy there will be errors Here however we focus on the error in two key quantities the position and the momentum The error in the energy will come from the momentum integration Three parameters exist which are relevant to the integration accuracy DeltaOneStep is a distance and is roughly the position error which is acceptable in an integratio
395. n step Since many integration steps may be required for a single physics step DeltaOneStep should be a fraction of the average physics step size The next two parameters impose a further limit on the relative error of the position momentum inaccuracy EpsilonMin and EpsilonMax impose a minimum and maximum on this relative error and take precedence over DeltaOneStep Note if you set EpsilonMin EpsilonMax your value then all steps will be made to this relative precision Example 4 13 How to set accuracy parameters for the global field of the setup G4FieldManager globalFieldManager G4TransportationManager transportMgr G4TransportationManager GetTransportationManager globalFieldManager transportMgr GetFieldManager Relative accuracy values G4double minEps 1 0e 5 Minimum amp value for smallest steps G4double maxEps 1 0e 4 Maximum amp value for largest steps globalFieldManager gt SetMinimumEpsilonStep minEps globalFieldManager gt SetMaximumEpsilonStep maxEps globalFieldManager gt SetDeltaOneStep 0 5e 3 mm 0 5 micrometer G4cout EpsilonStep set min minEps max maxEps G4endl We note that the relevant parameters above limit the inaccuracy in each step The final inaccuracy due to the full trajectory will accumulate The exact point at which a track crosses a boundary is also calculated with finite accuracy To limit this inaccuracy a parameter call
396. n the fast part of the emitted parti cle spectrum G4PiMinusAbsorptionAtRest and G4KaonMinusAbsorptionAtRest focus especially on a good de scription of this part of the spectrum 152 Tracking and Physics Implementation Interface to Geant4 All of these classes are derived from the abstract class G4VRestProcess In addition to the constructor and de structor methods the following public methods of the abstract class have been implemented for each of the above six processes e AtRestGetPhysicallnteractionLength const G4Track amp G4ForceCondition This method returns the time taken before the interaction actually occurs In all processes listed above except for muon capture a value of zero is returned For the muon capture process the muon capture lifetime is returned e AtRestDoIt const G4Track amp const G4Step amp This method generates the secondary particles produced by the process e IsApplicable const G4ParticleDefinition This method returns the result of a check to see if the process is possible for a given particle Example of how to use a hadron at rest process Including a hadron at rest process for a particle a pi for example into the Geant4 system is straightforward and can be done in the following way create a process theProcess new G4PionMinusAbsorptionAtRest register the process with the particle s process manager theParticleDef G4PionMinus PionMinus G4ProcessMana
397. n to the recommended threshold In other words a process can produce the secondaries down to the recommended threshold and by interrogating the geometry or by realizing when mass to energy conversion can occur recognize when particles below the threshold have to be produced 5 4 7 Special tracking cuts One may need to cut given particle types in given volumes for optimisation reasons This decision is under user control and can happen for particles during tracking as well The user must be able to apply these special cuts only for the desired particles and in the desired volumes without introducing an overhead for all the rest The approach is as follows special user cuts are registered in the UserLimits class or its descendant which is associated with the logical volume class The current default list is max allowed step size max total track length max total time of flight min kinetic energy min remaining range The user can instantiate a UserLimits object only for the desired logical volumes and do the association The first item max step size is automatically taken into account by the G4 kernel while the others items must be managed by the user as explained below Example see novice N02 in the Tracker region in order to force the step size not to exceed 1 10 of the Tracker thickness it is enough to put the following code in DetectorConstruction Construct G4double maxStep 0 1 TrackerLength l
398. n with the DAWN FILE driver The former exhibits minimal visualization commands to visualize detector geometry while the latter exhibits customized visualization visualization of a selected physical volume coordinate axes texts etc FE FE AE HE AE AE EE HH FE AE AE AE HE FE EE HH AE AE E FE EE EE HEHEHE EEE HE HHH visl mac A Sample macro to demonstrate visualization of detector geometry USAGE Save the commands below as a macro file say visl mac and execute it as follows 28 Getting Started with Geant4 Running a Simple Example E 6 G4BINDIR exampleN03 Idle gt control execute visl mac E E AE E AE AE AE AE AE HHH AE AE FE AE AE FE HE E AE AE AE AE AE AE AE FE E E E aE a RHE FE AE AE FE AE FE FE AE FE FE FE E FE E AE FE AE FE FE AE FE FE FE HE FE AE E FE AE FE HERE E E E E H Visualization of detector geometry with the OGLIX OpenGL Immediate X driver HEHE HHH HE FE FE EE FE HE AE FE FE FE FE AE FE FE EH HEE AE FE FE E HH EE E EH OGLIX driver scene handler and LIX Invoke the Createva vis open OG a viewer for the OGLIX driver Visualize the whole detector geometry with the default camera parameters Command vis drawVolume visualizes the detector geometry and command vis viewer flush declares the end of visualization The command vis viewer flush can be omitted for the OGLIX and OGLSX drivers The default argument of vis drawVolume is world vis drawVolume
399. nNuclearProcess RegisterMe theElectroReaction theElectronNuclearProcess BiasCrossSectionByFactor 100 pManager gt AddDiscreteProcess amp theElectronNuclearProcess More details can be found in Hadronic cross section biasing 3 7 2 2 G4WrapperProcess G4WrapperProcess can be used to implement user defined event biasing G4WrapperProcess which is a process itself wraps an existing process By default all function calls are forwared to the wrapped process It is a non in vasive way to modify the behaviour of an existing process To use this utility first create a derived class inheriting from G4WrapperProcess Override the methods whose behaviour you would like to modify for example PostStepDolt and register the derived class in place of the process to be wrapped Finally register the wrapped process with G4WrapperProcess The code snippets below demonstrate its use class MyWrapperProcess public G4WrapperProcess 56 Toolkit Fundamentals 57 Chapter 4 Detector Definition and Response 4 1 Geometry 4 1 1 Introduction The detector definition requires the representation of its geometrical elements their materials and electronics properties together with visualization attributes and user defined properties The geometrical representation of detector elements focuses on the definition of solid models and their spatial position as well as their logical relations to one another such as in the c
400. nager new G4RunManager set mandatory initialization classes runManager gt SetUserInitialization new ExN0lDetectorConstruction runManager gt SetUserInitialization new ExN01PhysicsList set mandatory user action class runManager gt SetUserAction new ExNOlPrimaryGeneratorAction Initialize G4 kernel runManager gt Initialize start a run int numberOfEvent 1000 runManager gt BeamOn numberOfEvent job termination delete runManager return 0 21 Getting Started with Geant4 Running a Simple Example Even the number of events in the run is frozen To change this number you must at least recompile main 2 9 3 Batch Mode with Macro File Below is an example of the main program for an application which will run in batch mode but reading a file of commands Example 2 21 An example of the main routine for an application which will run in batch mode but reading a file of commands int masina Einc arga gt Shia eaten Construct the default run manager G4RunManager runManager new G4RunManager set mandatory initialization classes runManager gt SetUserInitialization new MyDetectorConstruction runManager gt SetUserInitialization new MyPhysicsList set mandatory user action class runManager gt SetUserAction new MyPrimaryGeneratorAction Initialize G4 kernel runManager gt Initialize read a macro file of commands G4UImanager UI
401. nce and energy limits of different models are available in the Physics Reference Manual and in the Geant4 Low Energy Electromagnetic Physics Working Group homepage 5 2 1 3 Very Low energy Electromagnetic Processes Geant4 DNA extension Geant4 low energy electromagnetic Physics processes have been extended down to energies of a few electron Volts suitable for the simulation of radiation effects in liquid water for applications at the cellular and sub cellular level These developments take place in the framework of the Geant4 DNA project http www ge infn it geant4 dna and are fully described in the paper Chauvie2007 Their implementation in Geant4 is based on the usage of innovative techniques first introduced in Monte Carlo simulation policy based class design to ensure openness to future extension and evolution as well as flexibility of configuration in user applications In this new design a generic Geant4 DNA physics process is configured by template specialization in order to acquire physical properties cross section final state using policy classes a Cross Section policy class and a Final State policy class These processes apply to electrons protons hydrogen alpha particles and their charge states Electron processes Elastic scattering two complementary models available depending on energy range Cross section policy class name common to both models G4CrossSectionElasticScreenedRutherford Final state poli
402. ng Convert G4String parameter value given by the Set NewValue method of your messenger into double but without multiplying the value of the given unit 198 Communication and Control e G double GetNewUnitValue G4String paramString Convert G4String unit value given by the SetNewValue method of your messenger into double G4String convertToString G4bool currVal char unitName Convert the current double value to a G4String which should be returned by the Get CurrentValue method of your messenger The double value will be divided by the value of the given unit and converted to a string Given unit will be added to the string G4UIcmdWith3VectorAndUnit This is a G amp UIcommand derived class which takes one three vector parameter and its unit G4UIcmdWith3VectorAndUnit char commandpath G4UImanager theMessenger Constructor Arguments are the full path command name and the pointer to your messenger void SetParameterName char paramNamX char paramNamY char paramNamZ G4bool omittable Define the names of each component of the three vector and set the omittable flag If omittable is true you should define the default value using the next method void SetDefaultValue G4ThreeVector defVal Define the default value of the three vector void SetUnitCategory char unitCategory Define acceptable unit category void SetDefaultUnit char defUnit Define the default unit Please use this metho
403. ng external modules bound to Geant4 cc ee ME E SS E ee IE E ME GNUmakefile for the application phys depending on module reco an mn ne Ai li ae a a es gs a e i Sa iki ae a A gt Ka ca ata A a aa a i Sh a pe name phys GATARGET name G4EXLIB true EXTRALIBS G4WORKDIR tmp G4SYSTEM name libphys a L HOME reco lib lreco EXTRALIBSSOURCEDIRS HOME phys HOME reco EXTRA LINK DEPENDENCIES G4WORKDIR tmp G4SYSTEM name libphys a PHONY all art lajos Jens include G4INSTALL config binmake gmk MYSOURCES wildcard HOME phys src cc GAWORKDIR tmp GASYSTEM name libphys a MYSOURCES cd HOME phys MAKE 6 Step by Step Installation Guides You can find below some useful pages collecting instructions on how to install Geant4 in a detailed step by step tutorial Step by step Installation Guides 6 1 Building on MS Visual C Geant4 can be compiled with the C compiler of MS Visual Studio C and the Cygwin toolset Detailed instructions are given in the Installation manual As the build system relies on make and other Unix tools using only the compiler of MS Visual Studio the section on Section 5 Makefile and environment variables applies also for building with MS Visual C We do not support compilation directly under MS Visual Studio i e we do not provide workspace files dsw or project files dsp
404. ngAction G4VVisManager pVVisManager G4VVisManager GetConcreteInstance if pVVisManager jose Get the Stepping Manager const G4SteppingManager pSM GetSteppingManager e Define a line segment G4Polyline polyline G4double charge pSM gt GetTrack gt GetDefinition gt GetPDGCharge G4Colour colour TE ehamges 105 COLON CAC OLOU abor or SNS else ifi charge lt 0r colour G4colouE 0707 175 else colour G4Colour 0 1 AEE KE G4VisAttributes attribs colour polyline SetVisAttributes attribs polyline push_back pSM gt GetStep gt GetPreStepPoint gt GetPosition polyline push_back pSM gt GetStep gt GetPostStepPoint gt GetPosition I Call a drawing method for G4Polyline pVVisManager gt Draw polyline end of C source code Next in order that the above C source code works you have to pass the information of the MySteppingAction to the Run Manager in the main function C source code Passing what to do at each step to the Run Manager int main Run Manager G4RunManager runManager new G4RunManager User initialization classes runManager gt SetUserAction new MySteppingAction end of C source code 236 Visualization Thus you can visualize tracking steps with various visualization attributes e g color at each step automatically As well as tracking steps you can visualize any kind 3D obje
405. ngth of the material as a function of the photon s momentum WLSCOMPONENT is the relative emission spectrum of the material as a function of the photon s momentum and WLSTIMECONSTANT accounts for any time delay which may occur between absorption and re emission of the photon An example is shown in Example 5 9 160 Tracking and Physics Example 5 9 Specification of WLS properties in DetectorConstruction const G4int nEntries 9 G4double PhotonEnergy nEntries 6 6 eV 6 7 eV 6 8 eV 6 9 eV ISO V Tsien Wee cV G4double RIndexFiber nEntries 1 60 AsO JL 1 60 1 60 14607 35995 1 60 3550 135 G4double AbsFiber nEntries Hl Mesias 0 2 satis 0 s Sait Ol AZ em 0 S 1 0 eqq 1E 49 aay ALO e 000v 1500 5 OU G4double EmissionFiber nEntries 10407 10407 O40 0415 0455 UO 5507 10407 1050 15 G4Material WLSFiber G4MaterialPropertiesTable MPTFiber new G4MaterialPropertiesTable MPTFiber gt AddProperty RINDEX PhotonEnergy RIndexFiber nEntries MPTFiber gt AddProperty WLSABSLENGTH PhotonEnergy AbsFiber nEntries MPTFiber gt AddProperty WLSCOMPONENT PhotonEnergy EmissionFiber nEntries MPTFiber gt AddConstProperty WLSTIMECONSTANT 0 5 ns WLSFiber gt SetMaterialPropertiesTable MPTFiber The process is defined in the PhysicsList in the usual way The process class name is G4OpWLS It should be instantiated with theWLSProcess new G4OpWLS OpWLS and attached to the proce
406. nic transportation decay optical photolepton hadron and parameterisation All physics processes are derived from the G4VProcess base class Its virtual methods e AtRestDoIt e AlongStepDoIt and PostStepDoIt and the corresponding methods AtRestGetPhysicallnteractionLength e AlongStepGetPhysicallInteractionLength and e PostStepGetPhysicallnteractionLength describe the behavior of a physics process when they are implemented in a derived class The details of these methods are described in Section 5 2 The following are specialized base classes to be used for simple processes G4VAtRestProcess Processes with only AtRestDoIt G4VContinuousProcess Processes with only AlongStepDoIt G4VDiscreteProcess processes with only PostStepDoIt Another 4 virtual classes such as G4VContinuousDiscreteProcess are provided for complex processes 2 5 2 Managing Processes The G4ProcessManager class contains a list of processes that a particle can undertake It has information on the order of invocation of the processes as well as which kind of DoIt method is valid for each process in the list A G4ProcessManager object corresponds to each particle and is attached to the G4ParticleDefiniton class In order to validate processes they should be registered with the particle s G4ProcessManager Process order ing information is included by using the AddProcess and SetProcessOrdering methods For reg istration of si
407. ns G4PSCellFlux Cell flux is a volume based flux scorer The cell flux is defined by a track length L of the particle inside a volume divided by the volume V of this cell The track length is calculated by a sum of the step lengths 125 Detector Definition and Response in the cell The expression for cell flux is given by the sum of W L V where W is a particle weight and is multiplied by the track length at each step G4PSPassageCellFlux Passage cell flux is a volume based scorer similar to G4PSCellFlux The only difference is that tracks which pass through a cell are taken into account It means generated or stopped tracks inside the volume are excluded from the calculation Other scorers G4PSMinKinEAtGeneration This scorer records the minimum kinetic energy of secondary particles at their production point in the volume in an event This primitive scorer does not integrate the quantity but records the minimum quantity G4PSNofSecondary This class scores the number of secondary particles generated in the volume The weight of the secondary track is taken into account G4PSNofStep This class scores the number of steps in the cell A particle weight is not applied G4PSCellCharge This class scored the total charge of particles which has stoped in the volume 4 4 7 G4VSDFilter and its derived classes G4VSDFilter is an abstract class that represents a track filter to be associated with G4VSensitiveDetector or G4VPri
408. nsportationManager GetTransportationManager GetFieldManager fieldMgr SetDetectorField magField 3 create the objects which calculate the trajectory fieldMgr CreateChordFinder magField To change the accuracy of volume intersection use the SetDeltaChord method fieldMgr gt GetChordFinder gt SetDeltaChord G4double newValue 112 Detector Definition and Response 4 3 2 2 Creating a Field for a Part of the Volume Hierarchy It is possible to create a field for a part of the detector In particular it can describe the field with pointer fEmField for example inside a logical volume and all its daughters This can be done by simply creating a G4FieldManager and attaching it to a logical volume with pointer logicVolumeWithField for example or set of logical volumes G4bool allLocal true logicVolumeWithField gt SetFieldManager localFieldManager allLocal Using the second parameter to SetFieldManager you choose whether daughter volumes of this logical volume will also be given this new field If it has the value t rue the field will be assigned also to its daughters and all their sub volumes Else if it is false it will be copied only to those daughter volumes which do not have a field manager already 4 3 2 3 Creating an Electric or Electromagnetic Field The design and implementation of the Field category allows and enables the use of an electric or combined elec tromagnetic field These f
409. nt4 application program New users of Geant4 should read this chapter first It is strongly recommended that this chapter be read in conjunction with a Geant4 system installed and running on your computer It is helpful to run the provided examples as they are discussed in the manual To install the Geant4 system on your computer please refer to the Installation Guide for Setting up Geant4 in Your Computing Environment Chapter 3 Toolkit Fundamentals discusses generalGeant4 issues such as class categories and the physical units system It goes on to discuss runs and events which are the basic units of a simulation Chapter 4 Detector Definition and Response describes how to construct a detector from customized materials and geometric shapes and embed it in electromagnetic fields It also describes how to make the detector sensitive to particles passing through it and how to store this information How particles are propagated through a material is treated in Chapter 5 Tracking and Physics The Geant4 philosophy of particle tracking is presented along with summaries of the physics processes provided by the toolkit The definition and implementation of Geant4 particles is discussed and a list of particle properties is provided Chapter 6 User Actions is a description of the user hooks by which the simulation code may be customized to perform special tasks Chapter 7 Communication and Control provides a summary of the commands avai
410. nt4 kernel will be summarized in Chapter 6 G4RunManager has several public methods which are listed below Initialize All initializations required by the Geant4 kernel are triggered by this method Initializations are construction of the detector geometry and set up of sensitive detectors and or digitizer modules construction of particles and physics processes calculation of cross section tables This method is thus mandatory before proceeding to the first run This method will be invoked automatically for the second and later runs in case some of the initialized quantities need to be updated BeamOn G4int numberOfEvent This method triggers the actual simulation of a run that is an event loop It takes an integer argument which represents the number of events to be simulated GetRunManager This static method returns the pointer to the G4RunManager singleton object GetCurrentEvent This method returns the pointer to the G4Event object which is currently being simulated This method is available only when an event is being processed At this moment the application state of Geant4 which is explained in the following sub section is EventProc When Geant4 is in a state other than EventProc this method returns nu11 Please note that the return value of this method is const G4Event and thus you cannot modify the contents of the object SetNumberOfEventsToBeStored G4int nPrevious When simulating the pile
411. o UI commands which allow the database to be accessed The list of currently avalable material names Section 8 is extended permanetly Example 4 11 A program which shows how to define materials from the internal database include globals hh include G4Material hh include G4NistManager hh int main G4NistManager man G4NistManager Instance man gt SetVerbose 1 define elements G4Element C man gt FindOrBuildElement C G4Element Pb man gt FindOrBuildMaterial Pb define pure NIST materials G4Material Al man gt FindOrBuildMaterial G4 Al G4Material Cu man gt FindOrBuildMaterial G4 Cu define NIST materials G4Material H20 man gt FindOrBuildMaterial G4 WATER G4Material Sci man gt FindOrBuildMaterial G4 PLASTIC SC VINYLTOLUENE G4Material Si02 man gt FindOrBuildMaterial G4 SILICON DIOXIDE G4Material Air man gt FindOrBuildMaterial G4 AIR HEP materials G4Material PbWO4 man gt FindOrBuildMaterial G4_PbWO4 G4Material lAr man gt FindOrBuildMaterial G4 lAr G4Material vac man gt FindOrBuildMaterial G4 Galactic define gas material at non STP conditions T 120K P 0 5atm G4Material coldAr man gt ConstructNewGasdMaterial ColdAr G4 Ar 120 kelvin 0 5 atmosphere print the table of materials G4cout lt lt G4Material GetMaterialTable lt lt endl return EXIT SUCCESS 4 2 4 The Tables 4 2 4
412. ocal host named arkoop kek jp set this environment variable as follows Remote_Host gt setenv G4DAWN_HOST_NAME arkoop kek jp This tells a Geant4 process running on the remote host where Geant4 Visualization should be performed i e where the visualized views should be displayed 4 Invoke a Geant4 process and perform visualization with the DAWN Network driver For example Idle gt vis open DAWN Idle gt vis drawVolume Idle gt vis viewer flush In step 4 3D scene data are sent from the remote host to the local host as DAWN formatted data and the local DAWN will visualize the data The transferred data are saved as a file named g4 prim in the current directory of the local host Further information http geant4 kek jp GEANT4 vis DAWN About_DAWN html http geant4 kek jp GEANT4 vis DAWN G4PRIM FORMAT 24 Further information Fukui Renderer DAWN http geant4 kek jp GEANT4 vis DAWN About_DAWN html The DAWNFILE driver http geant4 kek jp GEANT4 vis GEANT4 DAWNFILE_driver html The DAWN Network driver http geant4 kek jp GEANTA vis GEANTA DAWNNET driver html Environmental variables to customize DAWN and DAWN drivers http geant4 kek jp GEANT4 vis DAWN DAWN_ENV html http geant4 kek jp GEANT4 vis GEANT4 g4vis_on_linux html DAWN format g4 prim format manual http geant4 kek jp GEANT4 Ais DAWN G4PRIM FORMAT 24 216 Visualization Geant4 Fukui University Group Home Page ht
413. ocess to build single compound kernel library per category and generate Dynamic Link Libraries DLLs Once the libraries are generated the process will imply also the deletion of all temporary files generated during the compilation lib bin and tmp directories The G4INSTALL environment variable specifies where the installation of the Geant4 toolkit should take place therefore kernel libraries will be placed in G4INSTALL lib The G4WORKDIR environment variable is set by the user and specifies the path to the user working directory temporary files object files and data products of the installation process of Geant4 will be placed in G4WORKDIR tmp according to the system architecture used Binaries will be placed in GAWORKDIR bin according to the system architecture used The path to SG4WORKDIR bin G4SYSTEM should be added to PATH in the user environment 5 2 Environment variables Here is a list of the most important environment variables defined within the Geant4 GNUmake infrastructure with a short explanation of their use 282 Appendix We recommend that those environment variables listed here and marked with NOT be overriden or set explicitly or by accident They are already set and used internally in the default setup System configuration CLHEP_BASE_DIR Specifies the path where the CLHEP package is installed in your system G4SY STEM Defines the architecture and compiler currently used NOTE T
414. ociated G4Primary Vertex or G4PrimaryParticle class objects are deleted along with the deletion of G4Event 6 3 4 G4VUserRegionInformation This abstract base class allows the user to attach information associated with a region For example it would be quite beneficial to add some methods returning a boolean flag to indicate the characteristics of the region e g tracker calorimeter etc With this example the user can easily and quickly identify the detector component 193 User Actions Example 6 10 A sample region information class class RE0lRegionInformation public G4VUserRegionInformation publier RE0lRegionInformation RE01RegionInformation Weel Piguiae GODS private G4bool isWorld G4bool isTracker G4bool isCalorimeter public inline void SetWorld G4bool v true isWorld v inline void SetTracker G4bool v true isTracker v inline void SetCalorimeter G4bool v true isCalorimeter v inline G4bool IsWorld const return isWorld inline G4bool IsTracker const return isTracker inline G4bool IsCalorimeter const return isCalorimeter hi The following code is an example of a stepping action Here a track is suspended when it enters the calorimeter region from the tracker region Example 6 11 Sample use of a region information class void REO1SteppingAction UserSteppingAction const G4Step theStep Suspend a track if it is entering into the calorimeter
415. od is invoked at the beginning of each event In this method you have to invoke the G4VPrimaryGenerator concrete class you instantiated via the generatePrimaryVertex method You can invoke more than one generator and or invoke one generator more than once Mixing up several generators can produce a more complicated primary event 2 6 2 G4VPrimaryGenerator Geant4 provides two G4VPrimaryGenerator concrete classes One is G4ParticleGun which will be discussed here and the other is G4HEPEvtInterface which will be discussed in Section 3 6 2 6 2 1 G4ParticleGun G4ParticleGun is a generator provided by Geant4 This class generates primary particle s with a given momen tum and position It does not provide any sort of randomizing The constructor of G4ParticleGun takes an integer which causes the generation of one or more primaries of exactly same kinematics It is a rather frequent user re quirement to generate a primary with randomized energy momentum and or position Such randomization can be achieved by invoking various set methods provided by G4ParticleGun The invocation of these methods should be implemented in the generatePrimaries method of your concrete G4VUserPrimaryGeneratorAction class before invoking generatePrimaryVertex of G4ParticleGun Geant4 provides various random number generation methods with various distributions see Section 3 2 2 6 2 2 Public methods of G4ParticleGun The following methods are provided by
416. ode G4VERBOSE flag set For better performance verbosity code can be left out by defining G4_NO_VERBOSE G4LIB_BUILD_SHARED Flag specifying if to build kernel libraries as shared libraries libraries will be then used by default If not set static archive libraries are built by default G4LIB_BUILD_STATIC Flag specifying if to build kernel libraries as static archive libraries in addition to shared libraries in case SG4LIB_BUILD_SHARED is set as well G4LIB_BUILD_DLL Internal flag for specifying to build DLL kernel libraries for Windows systems The flag is automatically set when requested to build DLLs G4LIB_USE_DLL For Windows systems only Flag to specify to build an application using the installed DLL kernel libraries for Windows systems It is required to have this flag set in the environment in order to successfully build an application if the DLL libraries have been installed G4LIB_USE_GRANULAR To force usage of granular libraries against compound libraries at link time in case both have been in stalled The Geant4 building system chooses compound libraries by default if installed UI specific The most relevant flags for User Interface drivers are just listed here A more detailed description is given also in section 2 of this User s Guide G4UI USE TERMINAL Specifies to use dumb terminal interface in the application to be built default G4UI USE TCSH Specifies to use th
417. of the logical volume This instance must be placed inside a mother logical volume For simplicity it is unrotated Example 2 5 A simple physical volume G4double trackerPos x 1 0 meter G4double trackerPos y 0 0 meter G4double trackerPos z 0 0 meter G4VPhysicalVolume tracker phys new G4PVPlacement 0 no rotation G4ThreeVector trackerPos_x trackerPos_y trackerPos_z If translation position tracker log its logical volume tracker its name experimentalHall log its mother logical volume false no boolean operations 0 its copy number This places the logical volume tracker log at the origin of the mother volume experimentalHall log shifted by one meter along X and unrotated The resulting physical volume is named tracker and has a copy number of 0 Getting Started with Geant4 Running a Simple Example An exception exists to the rule that a physical volume must be placed inside a mother volume That exception is for the World volume which is the largest volume created and which contains all other volumes This volume obviously cannot be contained in any other Instead it must be created as a G4PVPlacement with a null mother pointer It also must be unrotated and it must be placed at the origin of the global coordinate system Generally it is best to choose a simple solid as the World volume and in Example NO1 we use the experimental hall Example 2 6 The World volume from
418. of hadronic shower models have been implemented parametrisation driven models data driven mod els and theory driven models Parametrisation driven models are used for all processes pertaining to particles coming to rest and interacting with the nucleus For particles in flight two sets of models exist for inelastic scattering low energy and high en ergy models Both sets are based originally on the GHEISHA package of Geant3 21 and the original approaches to primary interaction nuclear excitation intra nuclear cascade and evaporation is kept The models are located in the sub directories hadronics models low energy and hadronics models high energy The low energy models are targeted towards energies below 20 GeV the high energy models cover the ener gy range from 20 GeV to O TeV Fission capture and coherent elastic scattering are also modeled through parametrised models Data driven models are available for the transport of low energy neutrons in matter in sub directory hadron ics models neutron hp The modeling is based on the data formats of ENDF B VI and all distributions of this standard data format are implemented The data sets used are selected from data libraries that conform to these standard formats The file system is used in order to allow granular access to and flexibility in the use of the cross sections for different isotopes and channels The energy coverage of these models is from thermal energies to 20 MeV The
419. ogicTracker gt SetUserLimits new G4UserLimits maxStep The G4UserLimits class is in source global management Concerning the others cuts the user must define dedicaced process es He registers this process or its descen dant only for the desired particles in their process manager He can apply his cuts in the DoIt of this process since via G4Track he can access the logical volume and UserLimits An example of such process called UserSpecialCuts is provided in the repository but not inserted in any process manager of any particle Example neutrons One may need to abandon the tracking of neutrons after a given time of flight or a charged particle in a magnetic field after a given total track length etc 176 Tracking and Physics Example see novice NO2 in the Tracker region in order to force the total time of flight of the neutrons not to exceed 10 milliseconds put the following code in DetectorConstruction Construct G4double maxTime 10 ms logicTracker gt SetUserLimits new G4UserLimits DBL MAX DBL MAX maxTime and put the following code in NO2PhysicsList G4ProcessManager pmanager G4Neutron Neutron gt GetProcessManager pmanager gt AddProcess new G4UserSpecialCuts 1 1 1 The default G4UserSpecialCuts class is in source processes transportation 5 5 Cuts per Region 5 5 1 General Concepts Beginning with Geant4 version 5 1 the concept of a region has been define
420. oint of each physics step It can be seen as akin to a statistical uncertainty and is not expected to contribute any systematic behavior to physical quantities In contrast the bias addressed by delta intersection is clearly correlated with potential systematic errors in the momentum of reconstructed tracks Thus very strict limits on the intersection parameter should be used in tracking detectors or wherever the intersections are used to reconstruct a track s momentum Delta intersection and delta one step are parameters of the Field Manager the user can set them according to the demands of his application Because it is possible to use more than one field manager different values can be set for different detector regions Note that reasonable values for the two parameters are strongly coupled it does not make sense to request an accuracy of nm for delta intersection and accept 100 amp 956m for the delta one step error value Nevertheless delta intersection is the more important of the two It is recommended that these parameters should not differ significantly certainly not by more than an order of magnitude 4 3 2 Practical Aspects 4 3 2 1 Creating a Magnetic Field for a Detector The simplest way to define a field for a detector involves the following steps 1 create a field G4UniformMagField magField new G4UniformMagField G4ThreeVector 0 0 fieldValue 2 set it as the default field G4FieldManager fieldMgr G4Tra
421. ol Liss rot E eT EE SE ERR T re I EE OR tes 195 7T Builtzm Coinmands 2 ee ERE E I II e ES PEU Ete deri 195 7 2 User Interface Defining New Commands lt kaka aaa kaka aaa aaa aaa eene 195 72 1 G4U ImessSenger aie teer E DEMETRII MEE IR gs IRE tenes 195 7 2 2 G4UIcommand and its derived classes sse emen 196 7 2 3 An example Messenger Liukas niece ied ai a coves reete ede eei pr segetes ve eed 199 7 2 4 How to control the output of G4cout G4cerr sesssse HH 202 S Visualization tue etas tene qe tog deena NE AMT IEEE EIS S 204 8 1 Introduction to Visualization 5 eot m rere pk ee TRE sands EPOR ERE ERR TRES ETER ERU 204 8 11 What Can be Visualized ure ry eI EIE eee 204 8 1 2 You have a Choice of Visualization Drivers sess m 204 8 1 3 Choose the Driver that Meets Your Needs ceececceecneeeeceeeeeceeeeeeaeeeeaeeneeaeenes 205 8 1 4 Controlling Visualization sisisi nter er Mi cates chs a sa a beatae ET a 206 8 1 5 Vasualization Details Li iui ete rers ii ere ce as K esi nye de sa G 206 8 2 Adding Visualization to Your Executable 20 0 0 eee cece ce aaa aaa emere 206 8 2 1 Installing Visualization Drivers sese HMM emere 206 8 2 2 How to Realize Visualization Drivers in an Executable esee 207 8 2 3 A Sample Set up Fle LL skinas senis gees iseis av ass ee ew Ia sk Das sa soe sense is 208 8 2 4 Visualization Manager iier t
422. olicy class name G4FinalStateExcitationMillerGreen Jonisation one model e Cross section policy class name G4CrossSectionlonisationRudd Final state policy class name G4FinalStatelonisationRudd Charge decrease one model Cross section policy class name G4CrossSectionChargeDecrease Final state policy class name G4FinalStateChargeDecrease An example of the registration of these processes in a physics list is given here below Un opo ODDO E I ere oco9909090c ners Ooo9ou9 ooo tr gOSDO0UOOOODOD 11414 Geant4 DNA header files include G4DNAGenericIonsManager hh include G4FinalStateProduct hh include G4DNAProcess hh include G4CrossSectionExcitationEmfietzoglou hh include G4FinalStateExcitationEmfietzoglou hh include G4CrossSectionElasticScreenedRutherford hh include G4FinalStateElasticScreenedRutherford hh include G4FinalStateElasticBrennerZaider hh include G4CrossSectionExcitationBorn hh include G4FinalStateExcitationBorn hh include G4CrossSectionIonisationBorn hh include G4FinalStatelonisationBorn hh include G4CrossSectionIonisationRudd hh include G4FinalStateIlonisationRudd hh 148 Tracking and Physics typ E typ E typ I typ at typ E typ Cc typ e A voi ic W include include include include include include typedef G4 typedef G4 Processes definition DNAProcess lt G4 ElasticScreenedRutherford DNAProcess lt
423. olid bounded with a generic surface made of planar facets It is important that the supplied facets shall form a fully enclose space to represent the solid 74 Detector Definition and Response Two types of facet can be used for the construction of a G4TessellatedSolid a triangular facet G4TriangularFacet and a quadrangular facet G4QuadrangularFacet An example on how to generate a simple tessellated shape is given below Example 4 1 An example of a simple tessellated solid with G4TessellatedSolid First declare a tessellated solid G4TessellatedSolid solidTarget new G4TessellatedSolid Solid_name Define the facets which form the solid Ay G4double targetSize 10 cm G4TriangularFacet facetl new G4TriangularFacet G4ThreeVector targetSize targetSize 00 G4ThreeVector targetSize targetSize Qe ner G4ThreeVector Qr 0 0 targetSize ABSOLUTE facet2 new G4ThreeVector targetSize targetSize 05107 G4ThreeVector targetSize targetSize 0 56 7 G4ThreeVector 01410 0 0 targetSize ABSOLUTE e h h h e h h h G4TriangularFace G4TriangularFace P Tot G4TriangularFacet facet3 new G4TriangularFacet G4ThreeVector targetSize targetSize 0 509 G4ThreeVector targetSize targetSize O O G4ThreeVector 0 0 0 0 targetSize ABSOLUTE G4TriangularFacet facet4 new G4TriangularFacet G4ThreeVector targetSiz
424. om various options For example you can select your detector components to be visualized in wireframe or with surfaces In the former only the edges of your detector are drawn and so the detector looks transparent In the latter your detector looks opaque with shading effects The forced wireframe and forced solid styles make it possible to mix the wireframe and surface visualization if your selected graphics system supports such visualization For example you can make only the outer wall of your detector wired transparent and can see inside in detail Forced wireframe style is set with the following access function void G4VisAttributes SetForceWireframe G4bool force If you give true as the argument objects for which this set of visualization attributes is assigned are always visualized in wireframe even if in general the surface drawing style has been requested The default value of the forced wireframe style is false Similarly forced solid style i e to force that objects are always visualized with surfaces is set with void G4VisAttributes SetForceSolid G4bool force The default value of the forced solid style is false too You can also force auxiliary edges to be visible Normally they are not visible unless you set the appropriate view parameter Forcing the auxiliary edges to be visible means that auxiliary edges will be seen whatever the view parameters Auxiliary edges are not genuine edges of the volume
425. ometry de SNS e geometry test position to specify position for the line test geometry test direction to specify direction for the line test geometry test grid cells to define the resolution of the lines in the grid test as number of cells specifying them for each dimension X Y and Z The new settings will be applied to the grid test command geometry test cylinder_geometry gt to define the details of the cylinder geometry by specifying nPhi number of lines per Phi nZ number of Z points nRho number of Rho points he new settings will be applied to the cylinder test command geometry test cylinder scaleZ to define the resolution of the cylinder geometry by specifying the fraction scale for points along Z The new settings will be applied to the cylinder test command geometry test cylinder scaleRho to define the resolution of the cylinder geometry by specifying the fraction scale for points along Rho The new settings will be applied to the cylinder test command geometry test recursion start 101 Detector Definition and Response to set the initial level in the geometry tree for starting the recursion default value being zero i e the world volume The new settings will then be applied to any recursive test geometry test recursion_depth to set the depth in the geometry tree for recursion so that recursion will stop after hav
426. on radiation Em8 Photo absorption ionization model Em10 Table 9 4 TestEm by theme 268 Examples 9 2 1 3 Event Biasing General ReadMe 9 2 1 4 Event Generator e HepMCEx01 simplified collider detector using HepMC interface and stacking e HepMCEx02 connecting primary particles in Geant4 with various event generators using the HepMC interface e MCTruth demonstrating a mechanism for Monte Carlo truth handling using HepMC as the event record e exgps illustrating the usage of the GaGeneralParticleSource utility 9 2 1 5 Fields BlineTracer tracing and visualizing magnetic field lines e fieldO1 tracking using magnetic field and field dependent processes e field02 tracking using electric field and field dependent processes e field03 tracking in a magnetic field where field associated with selected logical volumes varies e field04 definition of overlapping fields either magnetic electric or both 9 2 1 6 Geant3 to Geant4 General ReadMe converting simple geometries in Geant3 21 to their Geant4 equivalents 9 2 1 7 Geometry Definition Markup Language General ReadMe illustrating import and export of a detector geometry with GDML 9 2 1 8 Geometry ReadMe OLAP debugging tool for overlapping geometries 9 2 1 9 Error Propagation Geant4E error propagation utility 9 2 1 10 Hadronic e Hadr01 example based on the application IION developed for simulation of proton or ion beam int
427. onsequently you may use your favourite package together with the Geant4 toolkit 2 1 JAS Please refer to the JAS documentation on histogramming for using the JAVA Analysis Studio tool 2 2 iAida Please refer to the iAIDA an implementation of AIDA in C documentation tool for generating histograms with AIDA to HBook Root and AIDA native compressed XML format 2 3 Open Scientist Lab Please refer to the Open Scientist Lab documentation on histogramming for using the Lab Analysis plug in for the OnX package 2 4 rAIDA Please refer to the rAIDA documentation a Root implementation of AIDA Root plugin for generating histograms with AIDA 280 Appendix 2 5 Examples Examples in Geant4 showing how to use AIDA compliant tools for histogramming are available in the code distribution in the following directories geant4 examples extended analysis geant4 examples extended electromagnetic geant4 examples advanced 3 CLHEP Foundation Library CLHEP is a set of Class Libraries containing many basic classes for use in High Energy Physics Both a CLHEP Reference Guide and a User Guide are available Origin and current situation of CLHEP CLHEP started in 1992 as a library for fundamental classes mostly needed for and in fact derived from the MC event generator MC written in C Since then various authors added classes to this package including several contributions made by developers in the
428. ontrol alias phi 30 control loop movie loop theta 0 360 1 where movie loop is as above This produces lots of jpeg files but takes 3 days Then make mpeg2encode parfile sh g4RayTracer jpeg Then edit mpeg2encode par to specify file type and size etc diff mpeg2encode par orig mpeg2encode par iow l Akkinpucpiecune gracile Eormacs Woe Uo oo Wr diss DIN Anput pict une Ele ar ewoushe n OMe Up M dla 15 1L 7e p AA lt A ieioea eiaa o vertical_size 78 aspect ratio information 1 sguare pel 2 4 3 600 horizontal size 600 vertical size gt i aspect ratio information l square pel 2 4 3 Then convert to ppm encode and play for i in g4 jpeg GNAUNAT Pss PB ONAGK 2 gt BPM Scd oo 4 2 1 Ral 7 S 16 10 Apr do je basename i jpeg command convert i j ppm echo command command done mpeg2encode mpeg2encode par g4RayTracer mpg open g4RayTracer mpg 255 Chapter 9 Examples 9 1 Novice Examples The Geant4 toolkit includes several fully coded examples which demonstrate the implementation of the user classes required to build a customized simulation Seven novice examples are provided ranging from the simulation of a non interacting particle and a trivial detector to the simulation of electromagnetic and hadronic physics processes in a complex detector Each example may be used as a base from which more detailed applications can be developed A se
429. opyNo G4VPhysicalVolume physVol const G4double Zposition fStartZ copyNo fSpacing G4ThreeVector origin 0 0 Zposition physVol gt SetTranslation origin physVol gt SetRotation 0 Note that the translation and rotation given in this scheme are those for the frame of coordinates the passive method They are not for the active method in which the solid is rotated into the mother frame of coordinates Similarly the ComputeDimensions method is used to set the size of that copy void ExN02ChamberParameterisation ComputeDimensions GABox amp trackerChamber const G4int copyNo const G4VPhysicalVolume physVol const G4double halfLength fHalfLengthFirst copyNo 1 fHalfLengthIncr trackerChamber SetXHalfLength halfLength 82 Detector Definition and Response trackerChamber SetYHalfLength halfLength trackerChamber SetZHalfLength fHalfWidth The user must ensure that the type of the first argument of this method in this example G4Box amp corresponds to the type of object the user give to the logical volume of parameterised physical volume More advanced usage allows the user e to change the type of solid by creating a Comput eSolid method or e to change the material of the volume by creating a Comput eMaterial method This method can also utilise information from a parent or other ancestor volume see the Nested Parameterisation below for the parameterisation Example N07 shows a simpl
430. or commands from the keyboard int main int argc char argv Construct the default run manager G4RunManager runManager new G4RunManager set mandatory initialization classes runManager gt SetUserInitialization new MyDetectorConstruction runManager SetUserInitialization new MyPhysicsList visualization manager G4VisManager visManager new G4VisExecutive visManager gt Initialize set user action classes runManager gt SetUserAction new MyPrimaryGeneratorAction runManager gt SetUserAction new MyRunAction runManager gt SetUserAction new MyEventAction runManager gt SetUserAction new MySteppingAction Initialize G4 kernel runManager gt Initialize Define UI terminal for interactive mode G4UIsession session new G4UIterminal session gt SessionStart delete session job termination delete visManager delete runManager return 0 This example will be executed with the command gt myProgram where myP rogram is the name of your executable The G4 kernel will prompt Idle and you can start your session An example session could be Create an empty scene world is default 23 Getting Started with Geant4 Running a Simple Example Idle gt vis scene create Add a volume to the scene Idle gt vis scene add volume Create a scene handler for a specific graphics system Change the next line to choose another graphic system
431. or tracks with small curvature typically low momentum particles in strong fields this can cause a large number of steps even in areas where there are no volumes to intersect something that is expected to be addressed in future development in which the safety will be utilized to partially alleviate this limitation especially in a region near a volume boundary in which case it is necessary in order to discover whether a track might intersect a volume for only a short distance Requiring such precision at the intersection is clearly expensive and new development would be necessary to minimize the expense By contrast changing the intersection parameter is less computationally expensive It causes further calculation for only a fraction of the steps in particular those that intersect a volume boundary 4 3 3 Spin Tracking The effects of a particle s motion on the precession of its spin angular momentum in slowly varying external fields are simulated The relativistic equation of motion for spin is known as the BMT equation The equation demonstrates a remarkable property in a purely magnetic field in vacuum and neglecting small anomalous mag netic moments the particle s spin precesses in such a manner that the longitudinal polarization remains a constant whatever the motion of the particle But when the particle interacts with electric fields of the medium and multi ple scatters the spin which is related to the particle s magneti
432. orAction is an example of a user action class which is derived from G4VUserPrimaryGeneratorAction In this class the user must describe the initial state of the primary event This class has a public virtual method named generatePrimaries which will be invoked at the beginning of each event Details will be given in Section 2 6 Note that Geant4 does not provide any default behavior for gen erating a primary event The next instruction runManager gt initialize performs the detector construction creates the physics processes calculates cross sections and otherwise sets up the run The final run manager method in main int numberOfEvent 3 runManager gt beamOn numberOfEvent begins a run of three sequentially processed events The beamOn method may be invoked any number of times within main with each invocation representing a separate run Once a run has begun neither the detector setup nor the physics processes may be changed They may be changed between runs however as described in Section 3 4 4 More information on G4RunManager in general is found in Section 3 4 Getting Started with Geant4 Running a Simple Example As mentioned above other manager classes are created when the run manager is created One of these is the user interface manager G4UImanager In main a pointer to the interface manager must be obtained G4UImanager UI G4UImanager getUIpointer in order for the user to issue commands to
433. ory driven models are available for inelastic scattering in a first implementation covering the full energy range of LHC experiments They are located in sub directory hadronics models generator The cur rent philosophy implies the usage of parton string models at high energies of intra nuclear transport models at intermediate energies and of statistical break up models for de excitation 5 2 3 Particle Decay Process This section briefly introduces decay processes installed in Geant4 For details of the implementation of particle decays please refer to the Physics Reference Manual 5 2 3 1 Particle Decay Class Geant4 provides a G4Decay class for both at rest and in flight particle decays G4Decay can be applied to all particles except 155 Tracking and Physics massless particles i e G4ParticleDefinition thePDGMass lt 0 particles with negative life time i e G4ParticleDefinition thePDGLifeTime 0 shortlived particles i e G4ParticleDefinition fShortLivedFlag True Decay for some particles may be switched on or off by using G4ParticleDefinition SetPDGStable as well as ActivateProcess and InActi vateProcess methods of G4ProcessManager G4Decay proposes the step length or step time for AtRest according to the lifetime of the particle unless PreAssignedDecayProperTime is defined in G4DynamicParticle The G4Decay class itself does not define decay modes of the particle
434. ou need with it convert point in local coordinates local to the current volume G4ThreeVector localPosition aTouchable gt GetHistory gt GetTopTransform TransformPoint myPoint convert back to global coordinates system G4ThreeVector globalPosition aTouchable GetHistory GetTopTransform Inverse TransformPoint localPosition If outside of the tracking run and given a generic local position local to a given volume in the geometry tree it is not possible to determine a priori its global position and convert it to the global coordinates system The reason for this is rather simple nobody can guarantee that the given local point is located in the right copy of the physical volume In order to retrieve this information some extra knowledge related to the absolute position of the physical volume is required first i e one should first determine a global point belonging to that volume eventually making a dedicated scan of the geometry tree through a dedicated G4Navigator object and then apply the method above after having created the touchable for it 4 1 8 3 Navigation in parallel geometries Since release 8 2 of Geant4 it is possible to define geometry trees which are parallel to the tracking geometry and having them assigned to navigator objects that transparently communicate in sync with the normal tracking geometry Parallel geometries can be defined for several uses fast shower para
435. owed by the track Its position is given by a G4ThreeVector G4TrajectoryPoint class objectis created in the AppendStep method of G4Trajectory and this method is invoked by G4TrackingManager at the end of each step The first point is created when the G4Trajectory is created thus the first point is the original vertex The creation of a trajectory can be controlled by invoking G4TrackingManager SetStoreTrajectory G4bool The UI command tracking storeTrajectory bool does the same The user can set this flag for each individual track from his her G4UserTrackingAction PreUserTrackingAction method The user should not create trajectories for secondaries in a shower due to the large amount of memory consumed All the created trajectories in an event are stored in G4TrajectoryContainer class object and this object will be kept by G4Event To draw or print trajectories generated in an event the user may invoke the DrawTrajectory or Show Trajectory methods of G4VTrajectory respectively from his her G4UserEventAction EndOfEventAction The geometry must be drawn before the trajectory drawing The color of the drawn trajectory depends on the particle charge negative red neutral green 138 Tracking and Physics positive blue Due to improvements in G4Navigator a track can execute more than one turn of its spiral trajectory without being broken into smaller steps as long as the trajectory does not cross a geometric
436. particle for example geometry and interactions in matter Its public method Stepping steers the stepping of the particle The algorithm to handle one step is given below 1 The particle s velocity at the beginning of the step is calculated 2 Each active discrete or continuous process must propose a step length based on the interaction it describes The smallest of these step lengths is taken 3 The geometry navigator calculates Safety the distance to the next volume boundary If the minimum physi cal step length from the processes is shorter than Safety the physical step length is selected as the next step length In this case no further geometrical calculations will be performed 4 If the minimum physical step length from the processes is longer than Safety the distance to the next bound ary is re calculated 5 The smaller of the minimum physical step length and the geometric step length is taken 6 All active continuous processes are invoked Note that the particle s kinetic energy will be updated only after all invoked processes have completed The change in kinetic energy will be the sum of the contributions from these processes 7 The track is checked to see whether or not it has been terminated by a continuous process 8 The current track properties are updated before discrete processes are invoked This includes updating the kinetic energy of the current track particle note that sumEnergyChange is the sum of t
437. plicable const G4ParticleDefinition amp partDef return amp partDef G4Gamma GammaDefinition G4bool ModelTrigger const G4FastTrack amp You must return true when the dynamic conditions to trigger your parameterisation are fulfilled The G4FastTrack provides access to the current G4Track gives simple access to envelope related features G4Logical Volume G4V Solid and G4AffineTransform references between the global and the envelope local coordinates systems and simple access to the position and momentum expressed in the envelope coordinate system Using these quantities and the G4VSolid methods you can for example easily check how far you are from the envelope boundary void DoIt const G4FastTrack amp G4FastStep amp The details of your parameterisation will be implemented in this method The G4FastTrack reference provides the input information and the final state of the particles after parameterisation must be returned through the G4FastStep reference Tracking for the final state particles is requested after your parameterisation has been invoked 5 2 6 4 The G4FastSimulationManager Class G4FastSimulationManager functionnalities regarding the use of ghost volumes are explained in Section 5 2 6 7 Constructor G4FastSimulationManager G4Region anEnvelope G4bool IsUnique false This is the only constructor You specify the G4Region by providing its pointer The G4FastSimulationManager object will bind itself to
438. pling and scoring A detailed description of different use cases which employ the sampling and scoring techniques can be found in the document Scoring and geometrical importance sampling use cases The purpose of importance sampling is to save computing time by sampling less often the particle histories en tering less important geometry regions and more often in more important regions Given the same amount of computing time an importance sampled and an analogue sampled simulation must show equal mean values while the importance sampled simulation will have a decreased variance The implementation of scoring is independent of the implementation of importance sampling However both share common concepts Scoring and importance sampling apply to particle types chosen by the user which should be borne in mind when interpreting the output of any biased simulation Examples on how to use scoring and importance sampling may be found in examples extended biasing and examples advanced Tiara 3 7 1 1 Geometries The kind of scoring referred to in this note and the importance sampling apply to spatial cells provided by the user A cell is a physical volume further specified by it s replica number if the volume is a replica Cells may be defined in two kinds of geometries 1 mass geometry the geometry setup of the experiment to be simulated Physics processes apply to this geom etry 2 parallel geometry a geometry constructed
439. ponse Parameterisations are bound to a G4Region object which in the case of fast simulation is also called an enve lope Prior to release 8 0 parameterisations were bound to a G4LogicalVolume the root of a volume hierar chy These root volumes are now attributes of the G4Region Envelopes often correspond to the volumes of sub detectors electromagnetic calorimeters tracking chambers etc With GEANT4 it is also possible to define envelopes by overlaying a parallel or ghost geometry as discussed in Section 5 2 6 7 In GEANT4 parameterisations have three main features You must specify the particle types for which your parameterisation is valid the dynamics conditions for which your parameterisation is valid and must be triggered the parameterisation itself where the primary will be killed or moved whether or not to create it or create secondaries etc and where the detector response will be computed GEANT4 will message your parameterisation code for each step starting in any root G4Logical Volume including daughters sub daughters etc of this volume of the G4Region It will proceed by first asking the available parameterisations for the current particle type if one of them and only one wants to issue a trigger If so it will invoke its parameterisation In this case the tracking will not apply physics to the particle in the step Instead the UserSteppingAction will be invoked 164 Tracking and Physics Pa
440. process theProtonIEProc gt RegisterMe theProtonIE Finally add the particle s inelastic process to the list of discrete processes theProtonProcMan gt AddDiscreteProcess theProtonIEProc The particle s inelastic process class G4ProtonInelasticProcess in the example above derives from the G4HadronicInelasticProcess class and simply defines the process name and calls the G4HadronicInelasticProcess constructor All of the specific particle inelastic processes derive from the G4HadronicInelasticProcess class which calls the Post StepDoIt function which returns the particle change object from the G4HadronicProcess function GeneralPostStepDolt This class also gets the mean free path builds the physics table and gets the microscopic cross section The G4HadronicInelasticProcess class derives from the G4HadronicProcess class which is the top level hadronic process class The G4HadronicProcess class derives from the G4VDiscreteProcess class The inelastic elastic capture and fission processes derive from the G4HadronicProcess class This pure virtual class also provides the energy range manager object and the Reg isterMe access function A sample case for the proton s inelastic interaction model class is shown in Example 5 3 where G4LEProtonInelastic hh is the name of the include file Example 5 3 An example of a proton inelastic interaction model class include G4InelasticInteraction hh class G4LEProtonInelastic public
441. propriate methods and streaming operators For all solids it is possible to estimate the geometrical volume and the surface area by invoking the methods G4double GetCubicVolume G4double GetSurfaceArea which return an estimate of the solid volume and total area in internal units respectively For elementary solids the functions compute the exact geometrical quantities while for composite or complex solids an estimate is made using Monte Carlo techniques For all solids it is also possible to generate pseudo random points lying on their surfaces by invoking the method G4ThreeVector GetPointOnSurface const which returns the generated point in local coordinates relative to the solid 4 1 2 1 Constructed Solid Geometry CSG Solids CSG solids are defined directly as three dimensional primitives They are described by a minimal set of parameters necessary to define the shape and size of the solid CSG solids are Boxes Tubes and their sections Cones and their sections Spheres Wedges and Toruses Box To create a box one can use the constructor 58 Detector Definition and Response G4Box const G4String amp pName G4double pX G4double pY G4double pZ by giving the box a name and its half lengths along the X Y and Z axis pX half lengthin X pY half length in Y pZ half length in Z This will create a box that extends from pX to pX in X from pY to pY in Y and from pZ to pZ
442. ption from a GDML representation medical linac illustrating a typical medical physics application simulating energy deposit in a Phantom filled with water for a typical linac used for intensity modulated radiation therapy The experimental set up is very similar to one used in clinical practice microbeam simulates the cellular irradiation beam line installed on the AIFIRA electrostatic accelerator facility located at CENBG Bordeaux Gradignan France purging magnet illustrating an application that simulates electrons traveling through a 3D magnetic field used in a medical environment for simulating a strong purging magnet in a treatment head 270 Examples radiation monitor illustrating an application for the study of the effects of a chip carrier on silicon radiation monitoring devices used in the LHC environment radioprotection illustrating an application to evaluate the dose in astronauts in vehicle concepts and Moon surface habitat configurations in a defined interplanetary space radiation environment gammaray telescope illustrating an application to typical gamma ray telescopes with a flexible configuration xray telescope illustrating an application for the study of the radiation background in a typical X ray tele scope xray_fluorescence illustrating the emission of X ray fluorescence and PIXE underground_physics illustrating an underground detector for dark matter searches cosmicr
443. purpose This process must be defined to all kinds of particles which need to be detected This process must be ordered just after G4Transporation and prior to any other physics processes The name of the parallel world where the G4ParallelWorldScoringProcess is responsible for must be defined through the method SetParallelWorld available from the class G4ParallelWorldScoringProcess If the user has more than one parallel worlds with detectors for each of the parallel worlds dedicated G4ParallelWorldScoringProcess objects must be instantiated with the name of each parallel world re spectively and registered to the particles 131 Detector Definition and Response Example 4 20 Define G4ParallelWorldScoringProcess Add parallel world scoring process G4ParallelWorldScoringProcess theParallelWorldScoringProcess new G4ParallelWorldScoringProcess ParaWorldScoringProc theParallelWorldScoringProcess SetParallelWorld ParallelScoringWorld theParticleIterator reset while theParticleIterator G4ParticleDefinition particle theParticlelterator gt value if particle gt IsShortLived G4ProcessManager pmanager particle GetProcessManager pmanager gt AddProcess theParallelWorldScoringProcess pmanager gt SetProcessOrderingToLast theParallelWorldScoringProcess idxAtRest pmanager gt SetProcessOrdering theParallelWorldScoringProcess idxAlongStep 1 pmanager gt SetProcessOrd
444. r added Whenever such a change happens the geometry setup needs to be first opened for the change to be applied and afterwards closed for the optimisation to be reorganised In the general case in order to notify the Geant4 system of the change in the geometry setup the G4RunManager has to be messaged once the new geometry setup has been finalised G4RunManager GeometryHasBeenModified The above notification needs to be performed also if a material associated to a positioned volume is changed in order to allow for the internal materials cuts table to be updated However for relatively complex geometries the re optimisation step may be extremely inefficient since it has the effect that the whole geometry setup will be re optimised and re initialised In cases where only a limited portion of the geometry has changed it may be suitable to apply the re optimisation only to the affected portion of the geometry subtree Since release 7 1 of the Geant4 toolkit it is possible to apply re optimisation local to the subtree of the geometry which has changed The user will have to explicitly open close the geometry providing a pointer to the top physical volume concerned Example 4 9 Opening and closing a portion of the geometry without notifying the G4RunManager include G4GeometryManager hh Open geometry for the physical volume to be modified rU G4GeometryManager OpenGeometry physCalor Modify dimension of the
445. r s into the map through the public AddToMap method For ex ample CAC OMouiamny Colonia WE 0525 0 vg G4Colour AddToMap custom myColour This loads a user defined G4Colour with key custom into the colour map 8 6 2 3 Colour and G4VisAttributes Class G4VisAttributes holds its colour entry as an object of class G4Colour A G4Colour object is passed to a G4VisAttributes object with the following access functions ti Set functions of G4VisAttributes void G4VisAttributes SetColour const G4Colour amp colour void G4VisAttributes SetColor const G4Color amp color We can also set RGBA components directly Ve Set functions of G4VisAttributes void G4VisAttributes SetColour G4double red j G4double green G4double blue 240 Visualization G4double alpha 1 0 void G4VisAttributes SetColor G4double red G4double green G4double blue G4double alpha The following constructor with G4Colour as its argument is also supported aaa Constructor of G4VisAttributes G4VisAttributes G4VisAttributes const G4Colour amp colour Note that colour assigned to a G4VisAttributes object is not always the colour that ultimately appears in the visu alization The ultimate appearance may be affected by shading and lighting models applied in the selected visual ization driver or stand alone graphics system 8 6 3 Forcing attributes As you will see later you can select a drawing style fr
446. r steps if you haven t done them explicitly It takes care of steps 2 3 4 and 6 Command vis viewer flush should follow in order to do the final Step 7 Commands 223 Visualization vis drawVolume physical volume name Idle gt vis viewer flush Argument A physical volume name The default value is world which is omittable Action Creates a scene consisting of the given physical volume and asks the current viewer to draw it The scene becomes current Command vis viewer flush should follow this command in order to declare end of visualization Example Visualization of the whole world with coordinate axes Idle vis drawVolume Idle vis scene add axes 0 0 0 500 mm Idle vis viewer flush 8 4 5 Visualization of a logical volume vis specify command Command vis specify visualizes a logical volume If allows you to control how much details is shown and whether to show booleans voxels and readout geometries It also does some of the other steps if you haven t done them explicitly It takes care of steps 2 3 4 and 6 Command vis viewer flush should follow the command in order to do the final Step 7 Command vis specify logical volume name depth of descent booleans flag voxels flag readout f1ag Argument A logical volume name Action Creates a scene consisting ofthe given logical volume and asks the current viewer to draw it The scene becomes current Exampl
447. r volume and doing a simple calculation of the kind copyNo x localPoint x fVoxelHalfX fNoVoxelX fVoxelHalfX 2 where VoxelHalfX is the half dimension of the voxel along X and NoVoxelxX is the number of vox els in the X dimension Voxel 0 will be the one closest to the corner VoxelHalfX fNoVoxelX fVoxelHalfY fNoVoxelY fVoxelHalfZ fNoVoxelZ Having the voxels filling completely the container volume allows to avoid the lengthy computation of Com puteStep and ComputeSafety methods required in the traditional navigation algorithm In this case when a track is inside the parent volume it has always to be inside one of the voxels and it will be only necessary to calculate the distance to the walls of the current voxel 95 Detector Definition and Response Skipping borders of voxels with same material Another speed optimisation can be provided by skipping the frontiers of two voxels which the same material assigned so that bigger steps can be done This optimisation may be not very useful when the number of materials is very big in which case the probability of having contiguous voxels with same material is reduced or when the physical step is small compared to the voxel dimensions very often the case of electrons The optimisation can be switched off in such cases by invoking the following method with argument skip G4RegularParameterisation SetSkipEqualMaterials G4bool skip Example To use the speci
448. rTrajStateFree PropagateError The equations of error propagation are only implemented in the representation of G4ErrorTrajStateFree Therefore if the user has provided instead a G4ErrorTrajStateOnSurface object it will be transformed into a G4ErrorTrajStateFree at the beginning of tracking and at the end it is converted back into G4ErrorTrajStateOnSurface on the target surface on the normal plane to the surface at the final point The user G4VUserTrackingAction PreUserTrackingAction const G4Track and G4VUserTrackingAction PreUserTrackingAction const G4Track are also invoked at the beginning and at the end of the track propagation G4ErrorPropagator stops the tracking when one of the three conditions is true Energy is exhausted 183 Tracking and Physics World boundary is reached User defined target is reached In case the defined target is not reached GaErrorPropagator Propagate returns a negative value The propagation of a trajectory state until a user defined target can be done by invoking the method of G4ErrorPropagatorManager G4int Propagate G4ErrorTrajState currentTS const G4ErrorTarget target G4ErrorMode mode G4ErrorMode PropForwards You can get the pointer to the only instance of G4ErrorPropagatorManager with G4ErrorPropagatorManager g4emgr G4ErrorPropagatorManager GetErrorPropagatorManager Another possibility is to invoke the propagation s
449. rameterisations look like a user stepping action but are more advanced because parameterisation code is messaged only in the G4Region to which it is bound e parameterisation code is messaged anywhere in the G4Region that is any volume in which the track is located GEANTA will provide information to your parameterisation code about the current root volume of the G4Region in which the track is travelling 5 2 6 2 Overview of Parameterisation Components The GEANT4 components which allow the implementation and control of parameterisations are G4VFastSimulationModel This is the abstract class for the implementation of parameterisations You must inherit from it to implement your concrete parameterisation model G4FastSimulationManager The G4VFastSimulationModel objects are attached to the G4Region through a G4FastSimulationManager This object will manage the list of models and will message them at tracking time G4Region Envelope As mentioned before an envelope in GEANT4 is a G4Region The parameterisation is bound to the G4Region by setting a G4FastSimulationManager pointer to it The figure below shows how the G4VFast SimulationModel and G4FastSimulationManager ob jects are bound to the G4Region Then for all root G4Logical Volume s held by the G4Region the fast sim ulation code is active G4Region G4FastSimulationManager G4VFastSimulationModel eg e e gamma model G4VFastSimulationModel hobt G4LogicalVolum
450. range and candidate list s for example of units Range check is done by intercoms and the error message from it is shown in the pop up dialog box When a parameter component has a candidate list a list box is automatically displayed When a file is requested by a command the file chooser is available Logging Log can be redirected to the terminal xterm or cygwin window from which GAG is invoked It can be interrupted as will in the middle of long session of execution Log can be saved to a file independent of the above redirection GAG displays warning or error messages from GEANT4 in a pop up warning widget 2 8 3 Building the Interface Libraries The libraries that don t depend on external packages are made by default They include G4Ulterminal G4UItcsh and G4UIGAG in libraries libG4UIbasic a so and libG4UIGAG a so G4UIGainServer o is packed in the libG4UIGAG To make the libraries of G4UIXm G4UIXaw and G4UIWin32 respective environment variables G4UI BUILD XM SESSION G4UI BUILD XAW SESSION or G4UI BUILD WIN32 SESSION must be set explicitly However if the environment variable G4UI NONE is set no interface libraries are built at all Build scheme of the user interface libraries is specified in G4INSTALL config G4UI_BUILD gmk makefile and the dependencies on the external packages are specified in G4INSTALL config interactivity gmk 2 8 4 How to Use the Interface To use a given interface GAUIxxx where xxx term
451. rate the vectorized PostScript data In such a case visualize the 3D scene with a faster visualization driver beforehand for previewing and then use the DAWNFILE drivers For example the following visualizes the whole detector with the OpenGL Xlib driver immediate mode first and then with the DAWNFILE driver to generate an EPS file g4 XX eps to save the visualized view Invoke the OpenGL visualization driver in its immediate mode vis open OGLIX Camera setting vis viewer set viewpointThetaPhi 20 20 Camera setting vis drawVolume vis viewer flush Invoke the DAWNFILE visualization driver vis open DAWNFILE Camera setting vis viewer set viewpointThetaPhi 20 20 Camera setting vis drawVolume vis viewer flush This is a good example to show that the visualization drivers are complementary to each other In the OpenInventor drivers you can simply click the Print button on their GUI to generate a PostScript file as a hard copy of a visualized view The OpenGL X drivers can also generate PostScript files either from a pull down menu Motif drivers or with vis ogl printEPS It can generate either vectorized or rasterized PostScript data In generating vectorized PostScript data hidden surface removal is performed based on the painter s algorithm after dividing facets of shapes into small sub triangles The WIRED HepRep Browser and WIREDA JAS Plug In can generate a wide variety of bitmap and vector output form
452. re coloured according to charge with all other configuration parameters provided by the default context The default colouring scheme is shown below Charge Colour ik Blue i Red 0 Green G4TrajectoryDrawByParticlelD This model colours trajectory lines according to particle type All other configuration parameters are provided by the default context By default all trajectories are coloured grey Chosen particle types can be highlighted with specified colours G4TrajectoryDrawByOriginVolume This model colours trajectory lines according to the trajectories originating volume name The volume can be either a logical or physical volume Physical volume takes precedence over logical volume All trajectories are coloured grey by default 244 Visualization G4TrajectoryDrawByAttribute This model draws trajectories based on the HepRep style attributes associated with trajectories Each attribute drawer can be configured with interval and or single value data A new context object is created for each inter val single value This makes it possible to have different step point markers etc as well as line colour for trajec tory attributes falling into different intervals or matching single values The single value data should override the interval data allowing specific values to be highlighted Units should be specified on the command line if the attribute unit is specified either as a G4BestUnit or if the unit is part of the value str
453. re ii i is ie ERR EE sa E is ss 16 2 7 How to Make an Executable Program sese HH aaa aaa aaa 16 2 7 1 Building ExampleNO1 in a UNIX Environment eH 16 2 7 2 Building ExampleNO1 in a Windows Environment see 17 2 8 How to Set Up an Interactive Session sesssse IH ehem emere 17 29 1 Introd ction eere ipe certe oper tes ui Eee AERE eR eens he 17 2 8 2 A Short Description of Available Interface Classes ee 18 2 8 3 Building the Interface Libraries esses e 20 2 8 4 How to Use the Interface ice ener E CR EE ER POR EER ii ks ERR Eos 20 2 9 How to Execute a Program i kia sis ii epit ree EI rr eruere i ka eser ss 21 2 9 Introd ction 1 2 tre Het te Om et bat Ye op P Ss En 21 2 9 2 Hard coded Batch Mode sss emeret hene 21 2 93 Batch Mode with Macro Fil 1 eei ei Pere re ER Ft ERES PERS seai aens PERS 22 2 9 4 Interactive Mode Driven by Command Lines esee 23 2 9 5 General Case 5e p reete a te a ore eta states seated RTS 24 2 10 How to Visualize the Detector and Events sese HH 26 2 10 1 Introducti n 1 1 5 rnt De erem reper RE RES ERR 26 2 10 2 Visualization Drivers 5 iie emet hier eve sea Ege DI Re Ie pe APR e DER aaa 26 2 10 3 How to Incorporate Visualization Drivers into an Executable lt a kaka 27 2 10 4 Writing the main Method to Include Visualization eee
454. rectilinear even in the presence of a magnetic field The user may limit the step size by specifying a maximum average number of Cerenkov photons created during the step using the SetMaxNumPhotonsPerStep const G4int NumPhotons method The actual number generated will necessarily be different due to the Poissonian nature of the production In the present implementation the production density of photons is distributed evenly along the particle s track segment even if the particle has slowed significantly during the step The frequently very large number of secondaries produced in a single step about 300 cm in water compelled the idea in GEANT3 21 of suspending the primary particle until all its progeny have been tracked Despite the fact that GEANT4 employs dynamic memory allocation and thus does not suffer from the limitations of GEANT3 21 with its fixed large initial ZEBRA store GEANT4 nevertheless provides for an analogous functionality with the public method Set TrackSecondariesFirst An example of the registration of the Cerenkov process is given in Example 5 6 158 Tracking and Physics Example 5 6 Registration of the Cerenkov process in PhysicsList include G4Cerenkov hh void ExptPhysicsList ConstructoOp G4Cerenkov theCerenkovProcess new G4Cerenkov Cerenkov G4int MaxNumPhotons 300 theCerenkovProcess gt SetTrackSecondariesFirst true theCerenkovProcess gt SetMaxNumPhotonsPerStep MaxNumPhotons
455. reeVector GetPos const returni pos a typedef G4THitsCollection lt ExN04TrackerHit gt ExN04TrackerHitsCollection extern G4Allocator lt ExN04TrackerHit gt ExN04TrackerHitAllocator inline void ExN04TrackerHit operator new size t void aHit aHit void ExN04TrackerHitAllocator MallocSingle return aHit inline void ExNO4TrackerHit operator delete void aHit ExN04TrackerHitAllocator FreeSingle ExN04TrackerHit aHit endif 118 Detector Definition and Response G4Allocator is a class for fast allocation of objects to the heap through the paging mechanism For details of G4Allocator refer to Section 3 2 4 Use of G4Allocator is not mandatory but it is recommended especially for users who are not familiar with the C memory allocation mechanism or alternative tools of memory allocation On the other hand note that G4Allocator is to be used only for the concrete class that is not used as a base class of any other classes For example do not use the G4Trajectory class as a base class for a customized trajectory class since G4Trajectory uses G4Allocator G4THitsMap G4THitsMap is an alternative to G4THitsCollection G4THitsMap does not demand G4VHit but instead any variable which can be mapped with an integer key Typically the key is a copy number of the volume and the mapped value could for example be a double such as the energy deposition in a volume G4THitsMap is conve nient for applications
456. report and you can live without quick rotate and zoom DAWN is the way to go If you want to render to a 3D format that others can view in a variety of commodity browsers including some web browser plug ins VRML is the way to go 205 Visualization If you want to visualize a geometry that the other visualization drivers can t handle or you need transparency or mirrors and you don t need to visualize trajectories e RayTracer will do it If you just want to quickly check the geometry hierarchy or if you want to calculate the volume or mass of any geometry hierarchy e ASCIITree will meet your needs e You can also add your own visualization driver Geant4 s visualization system is modular By creating just three new classes you can direct Geant4 informa tion to your own visualization system 8 1 4 Controlling Visualization Your Geant4 code stays basically the same no matter which driver you use Visualization is performed either with commands or from C code e Some visualization drivers work directly from Geant4 OpenGL Openlnventor RayTracer e ASCIITree For other visualization drivers you first have Geant4 produce a file and then you have that file rendered by another application which may have GUI control HepRep WIRED DAWN VRML 8 1 5 Visualization Details The following sections of this guide cover the details of Geant4 visualization Section 8 2 Adding Visualization to Your Executa
457. rified is provided The method returns t rue if an overlap occurs It is also possible to specify a tolerance by which overlaps not exceeding such quantity will not be reported by default all overlaps are reported Using the visualization driver DAVID The Geant4 visualization offers a powerful debugging tool for detecting potential intersections of physical vol umes The Geant4 DAVID visualization tool can infact automatically detect the overlaps between the volumes defined in Geant4 and converted to a graphical representation for visualization purposes The accuracy of the graphical representation can be tuned onto the exact geometrical description In the debugging physical volume surfaces are automatically decomposed into 3D polygons and intersections of the generated polygons are investi gated If a polygon intersects with another one physical volumes which these polygons belong to are visualized in color red is the default The Figure 4 5 below is a sample visualization of a detector geometry with intersecting physical volumes highlighted Figure 4 5 A geometry with overlapping volumes highlighted by DAVID At present physical volumes made of the following solids are able to be debugged G4Box G4Cons G4Para G4Sphere G4Trd G4Trap G4Tubs Existence of other solids is harmless Visual debugging of physical volume surfaces is performed with the DAWNFILE driver defined in the visual ization category and w
458. rning a list of libraries needed to link a cernlib application This command is only used in the g3tog4 module however if you do not make use of the g3tog4 tool it s harmless The cernlib script and the needed cernlib libraries are available from http cern ch cernlib Trying building the Geant4 libraries I see several of these errors appearing and my installation fails ice ci G4Exception d 1 missing separator Stop 5 G4DalitzDecayChannel d 1 missing separator Stop Has Geant4 been installed properly What to do to solve this error It looks like some file dependencies d are corrupted possibly due to previous build attempts which failed for some reason You need to remove each of them A quick recipe for doing this is to Configure the environment with the installation to be repaired e Unset the G4WORKDIR environment variable in case it is eventually set Type 272 Frequentry Asked Questions gmake clean dependencies from the affected module i e for this case from G4INSTALL source global management and G4INSTALL source particles management and rebuild Alternatively you may use gmake clean dependencies from G4INSTALL source and rebuild FAQ 2 Run Time Problems On Linux I get a segmentation fault as soon as I run one of the official examples Check that the CLHEP library has been installed and compiled coherently with the same compiler you use for installing Geant4 and for
459. rresponding to the original environment variables for the above three i e G4UI_USE_TERMINAL G4UI_USE_TCSH and G4UI USE GAG are set However if he she sets no environment variables then the C pre processor variable G4UI USE TERMINAL is set by default although there is no need to use it The environment variable GAUI USE XM G4UI USE XAW or GdUI USE WIN32 must be set to use the respective interface The file G4INSTALL config interactivity gmk resolves their dependencies on external packages If the environment variable G4UI NONE is set no externa ibraries are selected Also for your convenience if any GAUI USE XXX environment variable is set then the corresponding C pre processor flag is also set However if the environment variable G4UI NONE is set no C pre processor flags are set 2 9 How to Execute a Program 2 9 1 Introduction A Geant4 application can be run either in purely hard coded batch mode batch mode but reading a macro of commands interactive mode driven by command lines interactive mode via a Graphical User Interface The last mode will be covered in Section 2 8 The first three modes are explained here 2 9 2 Hard coded Batch Mode Below is an example of the main program for an application which will run in batch mode Example 2 20 An example of the main routine for an application which will run in batch mode int main Construct the default run manager G4RunManager runMa
460. rs 8 4 4 Visualization of a physical volume vis drawVolume command 223 8 4 5 Visualization of a logical volume vis specify command sessss 224 8 4 6 Visualization of trajectories vis scene add trajectories command 224 8 4 7 Visualization of hits vis scene add hits command sse 225 8 4 8 HepRep Attributes for Hits ehem aaa 225 8 4 9 Basic camera workings vis viewer commands see 225 8 4 10 Declare the end of visualization for flushing vis viewer flush command 226 8 4 11 End of Event Action and End of Run Action vis viewer endOfEventAc tion and vis viewer endOfEventAction commands esee 227 8 4 12 HepRep Attributes for Trajectories sse 227 8 4 13 How to save a visualized views to PostScript files esse 228 8 4 14 Culling 1 5 rt te s ovens seca Et ROSE ER ERR 228 8uL15 Cut VIEW issiskiria Va a PETRI 229 8 4 16 Tutorial macros torte Pe E P eO eee Ee PO De rr ERU pe b Ert edd 230 8 5 Controlling Visualization from Compiled Code sese 231 8 5 1 G4V ViasManager i nose roter ERE E RR Sr D RO PP P ERR oes 231 8 5 2 Visualization of detector components eme 231 8 5 3 Visualization of trajectories 2 t ER P RR ER E E ee t ter e err os 232 8 5 4 Enhanced trajectory drawing sss me eme m e mee meme 232 8 5 5 HepRep Attribute
461. rs with the types of these derived classes so that you can use methods defined in the derived classes according to their types without casting G4UImanager G4UIcommand G4UIparameter have very powerful type and range checking routines You are strongly recommended to set the range of your parameters For the case of a numerical value int or double the range can be given by a G4String using C notation e g X gt 0 amp amp X lt 10 Forthe case of a string type parameter you can set a candidate list Please refer to the detailed descriptions below GetCurrentValue will be invoked after the user s application of the corresponding command and before the SetNewValue invocation This GetCurrentValue method will be invoked only if atleast one parameter of the command has a range atleast one parameter of the command has a candidate list atleast the value of one parameter is omitted and this parameter is defined as omittable and currentVal ueAsDefault 195 Communication and Control For the first two cases you can re set the range or the candidate list if you need to do so but these re set parameters are needed only for the case where the range or the candidate list varies dynamically A command can be state sensitive i e the command can be accepted only for a certain G4ApplicationState s For example the run beamOn command should not be accepted when Geant4 is processing another event G4Sta
462. rsion 2 6 How to Generate a Primary Event 2 6 1 Generating Primary Events G4VuserPrimaryGeneratorAction is one of the mandatory classes available for deriving your own concrete class In your concrete class you have to specify how a primary event should be generated Actual generation of primary 14 Getting Started with Geant4 Running a Simple Example particles will be done by concrete classes of G4VPrimaryGenerator explained in the following sub section Your G4VUserPrimaryGeneratorAction concrete class just arranges the way primary particles are generated Example 2 19 An example of a G4VUserPrimaryGeneratorAction concrete class using G4ParticleGun For the usage of G4ParticleGun refer to the next subsection ifndef ExN01PrimaryGeneratorAction_h define ExN01PrimaryGeneratorAction_h 1 include G4VUserPrimaryGeneratorAction hh class G4ParticleGun class G4Event class ExNOlPrimaryGeneratorAction public G4VUserPrimaryGeneratorAction public ExNOlPrimaryGeneratorAction ExN01PrimaryGeneratorAction public void generatePrimaries G4Event anEvent private G4ParticleGun particleGun ji endif include ExN01PrimaryGeneratorAction hh include G4Event hh include G4ParticleGun hh include G4ThreeVector hh include G4Geantino hh include globals hh ExNOlPrimaryGeneratorAction ExNOlPrimaryGeneratorAction G4int n_particle 1 particleGun new G4ParticleGun n
463. rt 7 text SetText Welcome to Geant4 Visualization text SetPosition G4Point3D 0 0 0 These three lines are equivalent to G4Text text Welcome to Geant4 Visualization A G4Point3D 0 0 0 ff Size font size in units of pixels G4double fontsize 24 Should be 24 pixels to be implemented text SetScreenSize fontsize Jf fe Offsets G4double x offset 10 Should be 10 pixels to be implemented G4double y offset 20 Should be 20 pixels to be implemented text SetOffset x offset y offset fd Color Blue is the default setting and so the codes below are omissible Gacodounel bue Os Wor ik Wie G4VisAttributes att blue text SetVisAttributes att end of C source codes 252 Visualization 8 10 Making a Movie These instructions are suggestive only The following procedures have not been tested on all platforms There are clearly some instructions that apply only to Unix like systems with an X Windows based windowing system However it should not be difficult to take the ideas presented here and extend them to other platforms and systems The procedures described here need graphics drivers that can produce picture files that can be converted to a form suitable for an MPEG encoder There may be other ways of capturing the screen images and we would be happy to hear about them Graphics drivers currently capable of producing picture
464. rt in the Linux g gmk configuration script By doing so it has been verified a greater stability of results making possible reproducibility of exact outputs between debug non optimised and optimised runs A little performance improvement in the order of 2 can also be achieved in some cases To be consid ered that binaries built using these chip specific options will NOT be portable cross platforms generated applications will only run on Pentium4 based architectures 1 3 Windows MS Visual C OS MS Windows Compiler MS VC Since version NET 7 0 of the compiler ISO ANSI compliance is required See Section 3 1 of the Installation Guide for more detailed information See also Section 6 1 for more tips 1 4 MacOS X g OS MacOS Darwin Compiler GNU gcc The setup adopted for the g compiler on MacOS resembles in great part the one for Linux systems The default optimisation level in this case is O2 Dynamic libraries dy1ib are supported as well once built in order to run the generated application the user must specify the absolute path in the system where they re installed with the DYLD LIBRARY PATH system variable 2 Histogramming Geant4 is independent of any histogramming package The Geant4 toolkit has no drivers for histogramming and no drivers are needed in Geant4 to use a histogramming package The code for generating histograms should be compliant with the AIDA abstract interfaces for Data Analysis C
465. s viewer endOfEventAction and vis viewer end OfEventAction commands By default a separate picture is created for each event You can change this behavior to accumulate multiple events or even multiple runs in a single picture Command vis scene endOfEventAction refresh accumulate Action Control how often the picture should be cleared refresh means each event will be written to a new picture accumulate means events will be accumulated into a single picture Picture will be flushed at end of run unless you have also set vis scene endOfRunAction accumulate Additional note You may instead choose to use update commands from your BeginOfRunAction or EndOfEventAction as in early examples but now the vis manager ia able to do most of what most users require through the above commands Command vis scene endOfRunAction refresh accumulate Action Control how often the picture should be cleared refresh means each run will be written to a new picture accumulate means runs will be accumulated into a single picture To start a new picture you must explicitly issue vis viewer refresh vis viewer update or vis viewer flush 8 4 12 HepRep Attributes for Trajectories The HepRep file formats HepRepFile and HepRepXML attach various attributes to trajectories such that you can view these attributes label trajectories by these attributes or make visibility cuts based on these attributes If you use the default Geant4 trajec
466. s v Cn GO IND Ups physical volume name logical volume name and names of sensitive detector and readout geometry if any solid name and type volume and density daughter subtracted volume and mass and in the summary at the end of printing gt dis dE db db db db db db db db db db dk Y daughter included mass of top physical volume s in scene to depth specified Calorimeter copy no 0 belongs to logical volume Calorimeter Layer copy no 1 belongs to logical volume Layer 10 replicas Absorber copy no 0 belongs to logical volume Absorber Gap copy no 0 belongs to logical volume Gap Idle vis ASCIITree verbose 15 Idle vis drawTree tube phys 0 tube L tube G4Tubs 395841 cm3 1 782 mg cm3 JBS egisse 2 0 5 o TO NEC divided tube phys 0 divided tube L divided tube G4Tubs 65973 4 cm3 como ems 5 CUR M orm MTS SAT divided tube inset phys 0 divided tube inset L divided tube inset G4Tubs 58385 9 cm3 1 782 mg cm3 6 03369e 09 mm3 1 0752e 11 mg sub divided tube phys 0 sub divided tube L sub divided tube G4Tubs 145906 5 omo 1 792 me ona 120196 5 ems 2171541 E Calculating mass es Overall volume of expHall P 0 is 8000 m3 and the daughter included mass to unlimited depth is 78414 kg For the complete list of commands and options see the Control UICommands section of this user guide 8 3 11 GAG Tree The
467. s category can be found in short lived sub directory under the particles directory a quarks di quarks For example all 6 quarks b gluon c baryon excited states with very short life For example spin 3 2 baryons and anti baryons d meson excited states with very short life For example spin 1 vector bosons 5 3 2 3 Implementation of particles Single object created in the initialization Categories a b 1 These particles are frequently used for tracking in Geant4 An individual class is defined for each particle in these categories The object in each class is unique The user can get pointers to these objects by using static methods in their own classes The unique object for each class is created when its static method is called in the initialization phase 172 Tracking and Physics On the fly creation Category b 2 Ions will travel in a detector geometry and should be tracked however the number of ions which may be used for hadronic processes is so huge that ions are dynamically created by requests from processes and users Each ion corresponds to one object of the G4Jons class G4lonTable class is a dictionary for ions G4ParticleTable GetIon method invokes G4IonTable GetIon method to create ions on the fly Users can register a G4IsotopeTable to the G4IonTable G4IsotopeTable describes properties of ions exited en ergy decay modes life time and magnetic moments which are used to create ions
468. s a container class of collections of digits The usages of G4VDigi and G4TDigiCollection are almost the same as G4VHit and G4THitsCollection respec tively explained in the previous section 4 5 2 Digitizer module G4VDigitizerModule G4VDigitizerModule is an abstract base class which represents a digitizer module It has a pure virtual method Digitize A concrete digitizer module must have an implementation of this virtual method The Geant4 kernel classes do not have a built in invocation to the Digitize method You have to implement your code to invoke this method of your digitizer module In the Digitize method you construct your G4VDigi concrete class objects and store them to your G4TDigiCollection concrete class object s Your collection s should be associated with the G4DCofThisEvent object G4DigiManager G4DigiManager is the singleton manager class of the digitizer modules All of your concrete digitizer modules should be registered to G4DigiManager with their unique names G4DigiManager DM G4DigiManager GetDMpointer MyDigitizer myDM new MyDigitizer myDet myCal myEMdigiMod DM gt AddNewModule myDM Your concrete digitizer module can be accessed from your code using the unigue module name G4DigiManager DM G4DigiManager GetDMpointer MyDigitizer myDM fDM FindDigitizerModule myDet myCal myEMdigiMod myDM gt Digitize Also G4DigiManager has a Digitize method wh
469. s and CreateAttValues 8 4 9 Basic camera workings vis viewer commands Commands in the command directory vis viewer set camera parameters and drawing style of the current viewer which corresponds to Step 5 Note that the camera parameters and the drawing style should be set separately for each viewer They can be initialized to the default values with command vis viewer reset Some visualization systems such as the VRML and HepRep browsers also allow camera control from the standalone graphics application Just a few of the camera commands are described here For more commands see the Control UICommands section of this user guide Command vis viewer set viewpointThetaPhi theta phi deg rad 225 Visualization Arguments Arguments theta and phi are polar and azimuthal camera angles respectively The default unit is degree Action Set a view point in direction of theta phi Example Set the viewpoint in direction of 70 deg 20 deg Idle vis viewer set viewpointThetaPhi 70 20 Additional notes Camera parameters should be set for each viewer They are initialized with command vis viewer re Set Command vis viewer zoom scale factor Argument The scale factor The command multiplies magnification of the view by this factor Action Zoom up down of view Example Zoom up by factor 1 5 Idle vis viewer zoom 1 5 Additional notes Camera parameters should be set
470. s for Trajectories sssse HH ehem 232 8 5 6 Visualization of hits 1 iis ene RESET ERIS 233 8 5 7 HepRep Attributes for Hits 12d rte etre ter k EE Ee babes eens 235 8 5 8 Visualization Of text 15 ois egre teres ee eee e ire Te e eR e ea NEUE 235 8 5 9 Visualization of polylines and tracking steps sese 235 8 5 10 Visualization User Action ssssseseee Imm HH II eI enne 237 8 5 11 Standalone Visualization sissies teii n a e tt rere erp ro PR ER ea Pede 238 8 6 Visualization a Une 238 8 6 1 Visibility 7 he rte d TIE dees IR EET Sd rt a sa 238 8 6 2 Colo r iiie eene E Reese eerie Ere st 239 8 6 3 Forcing attributes to pectet pepe is eer Er RERO E e POE Rha wate 241 8 6 4 Constructors of G4VisAttributes cee kaka eem Hee He aa 242 8 6 5 How to assign G4VisAttributes to a logical volume eA 242 8 6 6 Additional User Defined Attributes sss ee 242 8 7 Enhanced Trajectory Drawing eite ttr E e RR ERREUR RR e Rp Os 243 8 7 1 Default e uu uu 243 8 7 2 Trajectory Drawing Models eerte err e pr eer rire diss ai EEE PSRS 244 8 7 3 Controlling from Commands esses eere 245 8 7 4 Controlling from Compiled Code sse 247 8 7 5 Drawing by time corem I Ee ERE lene 247 8 8 Trajectory Filtering irre rer
471. s the user sets a different one DRand46Engine Random engine using the drand48 and srand48 system functions from C standard library to imple ment the lat basic distribution and for setting seeds respectively DRand46Engine uses the seed48 function from C standard library to retrieve the current internal status of the generator which is represented by 3 short values DRand48Engine is the only engine defined in HEPRandom which intrinsically works in 32 bits precision Copies of an object of this kind are not allowed RandEngine Simple random engine using the rand and srand system functions from the C standard library to im plement the 1at basic distribution and for setting seeds respectively Please note that it s well known that the spectral properties of rand leave a great deal to be desired therefore the usage of this engine is not recommended if a good randomness quality or a long period is required in your code Copies of an object of this kind are not allowed RanluxEngine The algorithm for RanluxEngine has been taken from the original implementation in FORTRANT77 by Fred James part of the MATHLIB HEP library The initialisation is carried out using a Multiplicative Congruen tial generator using formula constants of L Ecuyer as described in F James Comp Phys Comm 60 1990 329 344 The engine provides five different luxury levels for quality of random generation When instantiating a RanluxEngine t
472. send the G4Event object to G4EventManager for the detector simulation Hits and trajectories will be associated with the G4Event object as a consequence 3 perform bookkeeping for the current G4Event object This is done by the virtual AnalyzeEvent method DoEvent Loop performs the entire simulation of an event However it is often useful to split the above three steps into isolated application programs If for example you wish to examine the effects of changing discriminator thresholds ADC gate widths and or trigger conditions on simulated events much time can be saved by perform ing steps and 2 in one program and step 3 in another The first program need only generate the hit trajectory information once and store it perhaps in a database The second program could then retrieve the stored G4Event objects and perform the digitization analysis using the above threshold gate and trigger settings These settings could then be changed and the digitization program re run without re generating the G4Events 3 4 4 3 Changing the Detector Geometry The detector geometry defined in your G4VUserDetectorConstruction concrete class can be changed during a run break between two runs Two different cases are considered The first is the case in which you want to delete the entire structure of your old geometry and build up a completely new set of volumes For this case you need to set the new world physical volume poin
473. solid Ja physCalor GetLogicalVolume GetSolid SetXHalfLength 12 5 cm Close geometry for the portion modified Ud G4GeometryManager CloseGeometry physCalor If the existing geometry setup is modified locally in more than one place it may be convenient to apply such a technique only once by specifying a physical volume on top of the hierarchy subtree containing all changed portions of the setup 105 Detector Definition and Response An alternative solution for dealing with dynamic geometries is to specify NOT to apply optimisation for the subtree affected by the change and apply the general solution of invoking the G4RunManager In this case a performance penalty at run time may be observed depending on the complexity of the not optimised subtree considering that without optimisation intersections to all volumes in the subtree will be explicitely computed each time 4 1 13 Importing XML Models Using GDML Geometry Description Markup Language GDML is a markup language based on XML and suited for the de scription of detector geometry models It allows for easy exchange of geometry data in a human readable XML based description and structured formatting The GDML parser is component of Geant4 which can be built and installed as an optional choice It allows for importing and exporting GDML files following the schema specified in the GDML documentation The installa tion of the plugin is optional and
474. sponse to study geometries trajectories and hits 2 High quality output for publications 3 Flexible camera control to debug complex geometries 4 Tools to show volume overlap errors in detector geometries 5 Interactive picking to get more information on visualized objects No one graphics system is ideal for all of these requirements and many of the large software frameworks into which Geant4 has been incorporated already have their own visualization systems so Geant4 visualization was designed around an abstract interface that supports a diverse family of graphics systems Some of these graphics systems use a graphics library compiled with Geant4 such as OpenGL while others involve a separate application such as WIRED or DAWN 8 1 1 What Can be Visualized Simulation data can be visualized Detector components A hierarchical structure of physical volumes A piece of physical volume logical volume and solid Particle trajectories and tracking steps Hits of particles in detector components Other user defined objects can be visualized Polylines such as coordinate axes 3D Markers such as eye guides Text descriptive character strings comments or titles Scales Logos 8 1 2 You have a Choice of Visualization Drivers The many graphics systems that Geant4 supports are complementary to each other OpenGL View directly from Geant4 Uses GL libraries that are already included on most Linux systems
475. ss manager of the optical photon as a DiscreteProcess The way the WLSTIMECONSTANT is used depends on the time profile method chosen by the user If in the PhysicsList the WLSProcess gt UseTimeGenerator exponential option is set the time delay between absorption and re emission of the photon is sampled from an exponential distribution with the decay term equal to WLSTIMECONSTANT If on the other hand theWLSProcess UseTimeGenerator delta is chosen the time delay is a delta function and equal to WLSTIMECONSTANT The default is delta in case the G4OpWLS UseTimeGenerator const G4String name method is not used 5 2 5 4 Tracking of Photons in processes optical Absorption The implementation of optical photon bulk absorption G4OpAbsorption is trivial in that the process merely kills the particle The procedure requires the user to fill the relevant GGMaterialPropertiesTable with empirical data for the absorption length using ABSLENGTH as the property key in the public method AddP rop erty The absorption length is the average distance traveled by a photon before being absorpted by the medium i e itis the mean free path returned by the GetMeanFreePath method Rayleigh Scattering The differential cross section in Rayleigh scattering is proportional to cos where is the polar of the new polarization vector with respect to the old polarization vector The G4OpRayleigh scattering process samples this angle accordingly and
476. st G4double G4VMarker GetScreenDiameter const G4double G4VMarker GetScreenRadius const FillStyle G4VMarker GetFillStyle const Note enum G4VMarker FillStyle noFill hashed filled Example 8 7 shows sample C source code to define a very small red circle i e a dot with diameter 1 0 pixel Such a dot is often used to visualize a hit Example 8 7 Sample C source code to define a very small red circle faa C source codes An example of defining a red small maker G4Circle circle position Instantiate a circle with its 3D position The argument position is defined as G4Point3D instance circle SetScreenDiameter 1 0 Should be circle SetScreenDiameter 1 0 pixels to be implemented circle SetFillStyle G4Circle filled Make it a filled circle GAcolone colour E 005 Define red color G4VisAttributes attribs colour Define a red visualization attribute circle SetVisAttributes attribs Assign the red attribute to the circle end of C source codes 251 Visualization 8 9 3 Text Text i e a character string is used to visualize various kinds of description particle name energy coordinate names etc Text is described by the class G4Text The following constructors are supported fii Constructors of G4Text G4Text const G4String amp text G4Text const G4String amp text const G4Point3D amp pos where the argument text is the text strin
477. st extending from 0 05 to 0 05 meters in the mother s frame and the last from 0 35 to 0 45 meters divBox3 is a division of the same box along its X axis in 3 equal copies of width 0 1 meters and an offset of 0 5 meters The first copy will extend from 0 to 0 1 meters in the mother s frame and the last from 0 2 to 0 3 meters Example 4 6 An example of division of a polycone G4double zPlanem new G4double 3 zPlanem 0 1 m zPlanem es Sun zPlanem 2 SENI G4double rInnerm new G4double 3 rInnerm 0 0 rInnerm 0 1 m rInnerm 2 0 5 m G4double rOuterm new G4double 3 rOuterm 0 0 2 m rOuterm 0 4 m rOuterm 2 1 m G4Polycone motherSolid new G4Polycone motherSolid 20 deg 180 deg 3 zPlanem rInnerm rOuterm G4LogicalVolume motherLog new G4LogicalVolume motherSolid material mother 0 0 0 G4double zPlaned new G4double 3 zPlaned 0 3 m zPlaned 0 m zPlaned 2 1 m G4double rInnerd new G4double 3 rInnerd 0 0 2 rInnerd 0 4 m rInnerd 2 0 5 m G4double rOuterd new G4double 3 EOUce AION Oroe Mt rOuterd 0 8 m rOuterd 2 2 m G4Polycone divSolid new G4Polycone divSolid 0 deg 10 deg 3 zPlaned rInnerd rOuterd G4LogicalVolume childLog new G4LogicalVolume divSolid material child 0 0 0 G4PVDivision divPconePhiW division along phi giving width and offset childLog motherLog kPhi 30 deg 60 deg
478. structors of G4VisAttributes The following constructors are supported for class G4VisAttributes guess Constructors of class G4VisAttributes G4VisAttributes void G4VisAttributes G4bool visibility G4VisAttributes const G4Colour amp colour G4VisAttributes G4bool visibility const G4Colour amp colour 8 6 5 How to assign G4VisAttributes to a logical volume In constructing your detector components you may assign a set of visualization attributes to each logical volume in order to visualize them later if you do not do this the graphics system will use a default set You cannot make a solid such as G4Box hold a set of visualization attributes this is because a solid should hold only geometrical information At present you cannot make a physical volume hold one but there are plans to design a memory ef ficient way to do it however you can visualize a transient piece of solid or physical volume with a temporary assigned set of visualization attributes Class G4LogicalVolume holds a pointer of G4VisAttributes This field is set and referenced with the following access functions f Set functions of G4VisAttributes void G4VisAttributes SetVisAttributes const G4VisAttributes pVA void G4VisAttributes SetVisAttributes const G4VisAttributes amp VA jf Get functions of G4VisAttributes const G4VisAttributes G4VisAttributes GetVisAttributes const The following is sample C source codes for assi
479. t 0 Py 0 Pz 0 energyCmd new G4UIcmdWithADoubleAndUnit gun energy this energyCmd gt SetGuidance Set kinetic energy energyCmd gt SetParameterName Energy true true energyCmd gt SetDefaultUnit GeV energyCmd gt SetUnitCandidates eV keV MeV GeV TeV positionCmd new G4UIcmdWith3VectorAndUnit gun position this positionCmd gt SetGuidance Set starting position of the particle positionCmd SetParameterName X Y Z true true positionCmd gt SetDefaultUnit cm positionCmd SetUnitCandidates micron mm cm m km timeCmd new G4UIcmdWithADoubleAndUnit gun time this timeCmd gt SetGuidance Set initial time of the particle timeCmd gt SetParameterName t0 true true timeCmd gt SetDefaultUnit ns timeCmd gt SetUnitCandidates ns ms s Set initial value to G4ParticleGun fParticleGun gt SetParticleDefinition G4Geantino Geantino fParticleGun gt SetParticleMomentumDirection G4ThreeVector 1 0 0 0 0 0 fParticleGun gt SetParticleEnergy 1 0 GeV fParticleGun gt SetParticlePosition G4ThreeVector 0 0 cm 0 0 cm 0 0 cm fParticleGun gt SetParticleTime 0 0 ns G4ParticleGunMessenger G4ParticleGunMessenger 201 Communication and Control delete listCmd delete particleCmd delete directionCmd delete energyCmd delete positionCmd delete timeCmd delete gunDirectory void G4ParticleGunMessenger SetNewValue
480. t of extended examples implement simulations of actual high energy physics detectors and require some libraries in addition to those of Geant4 The advanced examples cover cases useful to the developement of the Geant4 toolkit itself The examples can be compiled and run without modification Most of them can be run both in interactive and batch mode using the input macro files in and reference output files out provided These examples are run routinely as part of the validation or testing of official releases of the Geant4 toolkit 9 1 1 Novice Example Summary Descriptions of the 7 novice examples are provided here along with links to the code ExampleN01 Description below Mandatory user classes Demonstrates how Geant4 kernel works i ExampleN02 Description below Simplified tracker geometry with uniform magnetic field Electromagnetic processes ExampleN03 Description below Simplified calorimeter geometry Electromagnetic processes Various materials ExampleN04 Description below Simplified collider detector with a readout geometry Full ordinary processes PYTHIA primary events Event filtering by stack ci ExampleN05 Description below Simplified BaBar calorimeter EM shower parametrisation 2 ExampleN06 Description below Optical photon processes ExampleN07 Description below Geometrical Regions for production thresholds 256
481. t window may be specified for every cell and for several energy regions space energy cell splitting to survival weight upper weight bound survival weight weight lower weight bound Russian roulette kill or move to survival weight Figure 3 2 Weight window concept Weight window concept The user specifies a lower weight bound W_L for every space energy cell The upper weight bound W_U and the survival weight W S are calculated as W_U C_U W_L and W_S C_S W_L The user specifies C S and C_U once for the whole problem The user may give different sets of energy bounds for every cell or one set for all geometrical cells e Special case if C S C U 1 for all energies then weight window is equivalent to importance sampling The user can choose to apply the technique at boundaries on collisions or on boundaries and collisions The energy space cells are realized by G4Geomet ryCel11 as in importance sampling The cells are stored in a weight window store defined by G4VWeightWindowStore class G4VWeightWindowStore public G4VWeightWindowStore virtual G4VWeightWindowStore virtual G4double GetLowerWeitgh const G4GeometryCell amp gCell G4double partEnergy const 0 virtual G4bool IsKnown const G4GeometryCell amp gCell const 0 virtual const G4VPhysicalVolume amp GetWorldVolume const 0 b A concrete implementation is provided class G4WeightWindowStore public G4VWeightWindowStore p plic
482. tMaterial G4Material material lVolume gt GetMaterial To get the geometrical region G4Region region lVolume GetRegion To get its mother volume G4vPhysicalVolume mother touchl GetVolume depth 1 gracie eher NECI IR o oo S o ME Frequentry Asked Questions To get the copy number of the mother volume G4int copyNumber touch1 gt GetCopyNumber depth 1 grandMothari depths 5 4 GSES os To get the process which has limited the current step G4VProcess aProcess point2 GetProcessDefinedStep To check that the particle has just entered in the current volume i e it is at the first step in the volume the preStepPoint is at the boundary if pointl gt GetStepStatus fGeomBoundary To check that the particle is leaving the current volume i e it is at the last step in the volume the post StepPoint is at the boundary if point2 gt GetStepStatus fGeomBoundary In the above situation to get touchable of the next volume G4TouchableHandle touch2 point2 gt GetTouchableHandle From t ouch2 all informations on the next volume can be retrieved as above Physics quantities are available from the step G4Step or from the track G4Track To get the energy deposition step length displacement and time of flight spent by the current step G4double eDeposit step gt GetTotalEnergyDeposit G4double sLength S5tep gt 2GetStepkength y G4ThreeVector displace step
483. ta It is sufficient to specify to which category your data belong Length Time Energy etc For example 39 Toolkit Fundamentals G4cout lt lt G4BestUnit StepSize Length StepSize will be printed in km m mm fermi etc depending of its actual value 3 3 4 Introduce new units If you wish to introduce new units there are two methods You can complete the file SystemOfUnits h include SystemOfUnits h static const G4double inch 2 54 cm Using this method it is not easy to define composed units It is better to do the following e You can instantiate an object of the class G4UnitDefinition G4UnitDefinition name symbol category value For example define a few units for speed G4UnitDefinition km hour km h Speed km 3600 s G4UnitDefinition meter ns m ns Speed m ns The category Speed does not exist by default in G4UnitsTable but it will be created automatically The class G4UnitDefinition is located in source global management 3 3 5 Print the list of units You can print the list of units with the static function GAUnitDefinition PrintUnitsTable or with the interactive command units list 3 4 Run 3 4 1 Basic concept of Run In Geant4 Run is the largest unit of simulation A run consists of a sequence of events Within a run the detector geometry the set up of sensitive detectors and the physics processes used in the simulation should be kept un ch
484. te_EventProc state You can set the states available for the command with the Available ForStates method 7 2 2 G4Ulcommand and its derived classes Methods available for all derived classes These are methods defined in the G4UIcommand base class which should be used from the derived classes e void SetGuidance char Define a guidance line You can invoke this method as many times as you need to give enough amount of guidance Please note that the first line will be used as a title head of the command guidance e void availableForStates G4ApplicationState sl If your command is valid only for certain states of the Geant4 kernel specify these states by this method Currently available states are G4State_PreInit G4State_Init G4State_Idle G4State_GeomClosed and G4State_EventProc Refer to the section 3 4 2 for meaning of each state Please note that the Pause state had been removed from G4ApplicationState void SetRange char range Define a range of the parameter s Use C notation e g x gt 0 amp amp x lt 10 with variable name s defined by the Set ParameterName method For the case of a G4ThreeVector you can set the relation between parameters e g x gt y G4Uldirectory This is a G4Ulcommand derived class for defining a directory e G4UIdirectory char directoryPath Constructor Argument is the full path directory which must begin and terminate with G4UIcmdWithoutParameter This is a G
485. tep Information Step and step point information can be retrieved by invoking various Get methods provided in the G4Step G4StepPoint classes For details see the Software Reference Manual Information in G4Step includes e Pointers to PreStep and Post StepPoint Geometrical step length step length before the correction of multiple scattering True step length step length after the correction of multiple scattering ncrement of position and time between PreStepPoint and PostStepPoint Increment of momentum and energy between PreStepPoint and PostStepPoint Note to get the en ergy deposited in the step you cannot use this Delta energy You have to use Total energy deposit as below 136 Tracking and Physics Pointer to G4Track Total energy deposited during the step this is the sum of the energy deposited by the energy loss process and the energy lost by secondaries which have NOT been generated because each of their energies was below the cut threshold Energy deposited not by ionization during the step Information in G4StepPoint PreStepPoint and PostStepPoint includes x y z px py pz Ek Momentum direction unit vector Pointers to physical volumes Safety Beta gamma Polarization Step status Pointer to the physics process which defined the current step and its DoIt type Pointer to the physics process which defined the previous step and its DoIt type Total track length Global t
486. tep by step returning control to the user after each step This can be done with the method G4int PropagateOneStep G4ErrorTrajState currentTS G4ErrorMode mode G4ErrorMode PropForwards In this case you should register the target first with the command G4ErrorPropagatorData GetG4ErrorPropagatorData gt SetTarget theG4eTarget 5 8 5 1 Error propagation Asin the GEANT3 based GEANE package the error propagation is based on the eguations of the European Muon Collaboration that take into account Error from curved trajectory in magnetic field e Error from multiple scattering Error from ionization The formulas assume propagation along an helix This means that it is necessary to make steps small enough to assure magnetic field constantness and not too big energy loss 5 8 6 Limiting the step There are three ways to limit the step The first one is by using a fixed length value This can be set by invoking the user command G4UImanager GetUIpointer gt ApplyCommand geant4e limits stepLength MY VALUE MY UNIT The second one is by setting the maximum percentage of energy loss in the step or energy gain is propagation is backwards This can be set by invoking the user command G4UImanager GetUIpointer gt ApplyCommand geant4e limits energyLoss MY VALUE The last one is by setting the maximum difference between the value of the magnetic field at the beginning and at the end of the step Indeed
487. ter to the RunManager Thus you should proceed in the following way G4RunManager runManager G4RunManager GetRunManager runManager gt DefineWorldVolume newWorldPhys Presumably this case is rather rare The second case is more freguent for the user The second case is the following Suppose you want to move and or rotate a particular piece of your detector component This case can easily happen for a beam test of your detector It is obvious for this case that you need not change the world volume Rather it should be said that your world volume experimental hall for your beam test should be big enough for moving rotating your test detector For this case you can still use all of your detector geometries and just use a Set method of a particular physical volume to update the transformation vector as you want Thus you don t need to re set your world volume pointer to RunManager If you want to change your geometry for every run you can implement it in the BeginOfRunAction method of G4UserRunAction class which will be invoked at the beginning of each run or derive the RunInitial ization method Please note that for both of the above mentioned cases you need to let RunManager know the geometry needs to be closed again Thus you need to invoke runManager gt GeometryHasBeenModified before proceeding to the next run An example of changing geometry is given in a Geant4 tutorial in Geant4 Training kit 2 3 4 4
488. ternative models are available Jonisation in thin absorbers class name G4PAIModel An example of the registration of these processes in a physics list is given in Example 5 1 similar method is used in EM builders of reference physics lists SGAINSTALL source physics lists builders and in EM examples G4INSTALL examples extended electromagnetic 142 Tracking and Physics Example 5 1 Registration of standard electromagnetic processes void PhysicsList ConstructEM theParticleIterator gt reset while theParticleIterator G4ParticleDefinition particle theParticleIterator value G4ProcessManager pmanager particle GetProcessManager G4String particleName particle gt GetParticleName if particleName gamma pmanager gt AddDiscreteProcess new G4PhotoElectricEffect pmanager gt AddDiscreteProcess new G4ComptonScattering pmanager gt AddDiscreteProcess new G4GammaConversion else if particleName e pmanager gt AddProcess new G4MultipleScattering 1 1 1 pmanager gt AddProcess new G4elonisation PAS AE pmanager gt AddProcess new G4eBremsstrahlung gt Bip 25 else if particleName e pmanager gt AddProcess new G4MultipleScattering Pakas E pmanager gt AddProcess new G4elonisation gt wis AB pmanager gt AddProcess new G4eBremsstrahlung 222 pmanager gt AddProcess new G4eplusAnnihilation 0 307 ADR else if particleName
489. ternative process for simulation of single Coulomb scattering of all charged particles class name G4CoulombScattering Alternative process for simulation of single Coulomb scattering of ions class name G4ScreenedNuclearRecoil Processes for simulation of polarized electron and gamma beams e Compton scattering of circularly polarized gamma beam on polarized target class name G4PolarizedCompton Pair production induced by circularly polarized gamma beam class name G4PolarizedGammaConversion e Photo electric effect induced by circularly polarized gamma beam class name G4PolarizedPhotoElectricEffect Bremsstrahlung of polarized electrons and positrons class name G4ePolarizedBremsstrahlung Jonisation of polarized electron and positron beam class name G4ePolarizedlonisation Annihilation of polarized positrons class name G4eplusPolarizedAnnihilation Processes for simulation of X rays and optical protons production by charged particles e Synchrotron radiation class name G4SynchrotronRadiation Transition radiation class name G4TransitionRadiation e Cerenkov radiation class name G4Cerenkov Scintillations class name G4Scintillation The processes described above use physics model classes which may be combined according to particle energy It is possible to change the energy range over which different models are valid and to apply other models specific to particle type energy range and G4Region The following al
490. ters are assumed to start from the vertex with which their parent is associated For example a Z boson is associated with a vertex and it has positive and negative muons as its daughters these muons will start from that vertex There are some kinds of particles which should fly some reasonable distances and thus should be simulated by Geant4 but you still want to follow the decay channel generated by an event generator A typical case of these particles is B meson Even for the case of a primary particle which has a corresponding G4ParticleDefinition it can have daughter primary particles Geant4 will trace the parent particle until it comes to decay obeying multiple scattering ionization loss rotation with the magnetic field etc according to its particle type When the parent comes to decay instead of randomly choosing its decay channel it follows the pre assigned decay channel To conserve the energy and the momentum of the parent daughters will be Lorentz transformed according to their parent s frame 46 Toolkit Fundamentals 3 6 2 Interface to a primary generator 3 6 2 1 G4HEPEvtinterface Unfortunately almost all event generators presently in use commonly are written in FORTRAN For Geant4 it was decided to not link with any FORTRAN program or library even though the C language syntax itself allows such a link Linking to a FORTRAN package might be convenient in some cases but we will lose many advantages of object
491. th the DAWNFILE driver The former exhibits minimal visualization commands to visualize events while the latter exhibits cus tomized visualization Note that the run action and event action classes should be described properly See for example the following classes examples novice NO3 src ExNO3RunAction cc HEP TE AE FE TE AE FE FE RE FE TE AE FE EH HE EE HE EH HE EE HE ER HE HEHE HE RHE E E EEH vis2 mac A Sample macro to demonstrate visualization d of events trajectories USAGE 29 Getting Started with Geant4 Running a Simple Example Save the commands below as a macro file say vis2 mac and execute it as follows 3 S G4BINDIR exampleN03 dle gt control execute visl mac RHE HEE AE FE FE HE HEE FE HE E FE AE FE FE HE FE FE AE FE FE E E FE AE FE FE HEH H EH E E H HHT FE E FE FE AE FE FE HE FE FE E FE FE FE EH FE FE HE FE FE FE FE FE E FE HEE FE FE E FE FE HE EH E HERE RE EE E E Store particle trajectories for visualization tracking storeTrajectory 1 RHE FE EE FE AE FE FE AE FE FE E FE FE AE FE FE AE FE FE HE FE FE E FE FE AE FE FE AE FE FE AE FE FE EE FE HE FE TE E AA E EE HH RHE FE E E FE AE FE FE AE FE FE E AE FE AE E FE FE FE FE AE FE FE FE E FE FE AE FE FE FE FE FE FE FE E AE FE E FE TE E E E EE E EE E EE Visualization with the OGLSX OpenGL Stored X driver RHE FE E FE FE AE FE FE AE FE FE E HE FE FE E FE FE FE FE FE FE FE FE E FE FE AE FE FE FE FE FE FE FE EE FE E EE E E E EE E E E E EE
492. the process itself and does not invoke the G4Navigator Combinations of surface finish properties such as polished or ground and front painted or back painted enumerate the different situations which can be simulated When a photon arrives at a medium boundary its behavior depends on the nature of the two materials that join at that boundary Medium boundaries may be formed between two dielectric materials or a dielectric and a metal In the case of two dielectric materials the photon can undergo total internal reflection refraction or reflection depending on the photon s wavelength angle of incidence and the refractive indices on both sides of the boundary Furthermore reflection and transmission probabilites are sensitive to the state of linear polarization In the case of an interface between a dielectric and a metal the photon can be absorbed by the metal or reflected back into the dielectric If the photon is absorbed it can be detected according to the photoelectron efficiency of the metal As expressed in Maxwell s equations Fresnel reflection and refraction are intertwined through their relative prob abilities of occurrence Therefore neither of these processes nor total internal reflection are viewed as individual processes deserving separate class implementation Nonetheless an attempt was made to adhere to the abstraction of having independent processes by splitting the code into different methods where practicable One implementat
493. the same version of Linux distribution For example a binary object produced with Red Hat 7 X is not fully compatible with binaries running on RH 9 X or higher due to different libc used in the two configurations I installed Geant4 libraries and built my application when I try to run it I get error in loading shared libraries libCLHEP so cannot open shared object file No such file or directory Your installation of CLHEP includes shared libraries You need to specify the path where libCLHEP so is installed through your environment variable LD_LIBRARY_PATH For example in tcsh UNIX shell setenv LD_LIBRARY_PATH LD LIBRARY PATH CLHEP BASE DIR lib On my system I get a Floating Point Exception FPE since some physics processes sometimes return DBL MAX as interaction length and this number is afterwards multiplied by a number greater than 1 Geant4 coding conventions and installation setup explicitly follow the ANSI TEEE 754 Standard for the initialization of floating point arithmetic hardware and portability The Standard foresees floating point arithmetic to be nonstop and underflows to be gradual On DEC platforms for example the ANSI IEEE 754 Standard compliance needs to be explicitly set since deactivated by default in this case we use infact the option ieee on the DEC cxx native C compiler to achieve this You should check if your compiler provides compilation options for activating Standard initialization of FP arithmet
494. the spin is done only for particles with non ze ro charge Please see the Forum posting http geant4 hn slac stanford edu 5090 Hyper News public get emfields 88 3 1 html for modifications the user is required to make to facilitate neutron spin tracking 4 4 Hits 4 4 1 Hit A hit is a snapshot of the physical interaction of a track in the sensitive region of a detector In it you can store information associated with a G4Step object This information can be e the position and time of the step the momentum and energy of the track the energy deposition of the step geometrical information or any combination of the above G4VHit G4VHit is an abstract base class which represents a hit You must inherit this base class and derive your own concrete hit class es The member data of your concrete hit class can be and should be your choice G4VHit has two virtual methods Draw and Print To draw or print out your concrete hits these methods should be implemented How to define the drawing method is described in Section 8 9 G4THitsCollection G4VHit is an abstract class from which you derive your own concrete classes During the processing of a giv en event represented by a G4Event object many objects of the hit class will be produced collected and associ 117 Detector Definition and Response ated with the event Therefore for each concrete hit class you must also prepare a concrete class derived from
495. this G4Region If you know that this G4Region has a single root G4Logical Volume placed only once you can set the IsUnique boolean to true to allow some optimization 166 Tracking and Physics Note that if you choose to use the G4VFastSimulationModel const G4String amp G4Region G4bool con structor for your model the G4FastSimulationManager will be constructed using the given G4Region and G4bool values of the model constructor G4VFastSimulationModel object management The following two methods provide the usual management functions e void AddFastSimulationModel G4VFastSimulationModel RemoveFastSimulationModel G4VFastSimulationModel Interface with the G4FastSimulationManagerProcess This is described in the User s Guide for Toolkit Developers section 3 9 6 5 2 6 5 The G4FastSimulationManagerProcess Class This G4VProcess serves as an interface between the tracking and the parameterisation At tracking time it col laborates with the G4FastSimulationManager of the current volume if any to allow the models to trigger If no manager exists or if no model issues a trigger the tracking goes on normally In the present implementation you must set this process in the G4ProcessManager of the particles you parame terise to enable your parameterisation The processes ordering is iQ 5 n 2 idi n Multiple Scattering G4FastSimulationManagerProcess G4Transportation This or
496. thod of your PhysicsList concrete class will be invoked 3 5 Event 3 5 1 Representation of an event G4Event represents an event An object of this class contains all inputs and outputs of the simulated event This class object is constructed in G4RunManager and sent to G4EventManager The event currently being processed can be obtained via the get CurrentEvent method of G4RunManager 3 5 2 Structure of an event A G4Event object has four major types of information Get methods for this information are available in G4Event Primary vertexes and primary particles Details are given in Section 3 6 Trajectories Trajectories are stored in G4TrajectoryContainer class objects and the pointer to this container is stored in G4Event The contents of a trajectory are given in Section 5 1 6 Hits collections Collections of hits generated by sensitive detectors are kept in G4HCofThisEvent class object and the pointer to this container class object is stored in G4Event See Section 4 4 for the details Digits collections Collections of digits generated by digitizer modules are kept in G4DCofThisEvent class object and the pointer to this container class object is stored in G4Event See Section 4 5 for the details 3 5 3 Mandates of G4EventManager G4EventManager is the manager class to take care of one event It is responsible for converting G4PrimaryVertex and G4PrimaryParticle objects associated with the current G4Event object to G
497. ticle Table 1 this routine is used in Construct void InitializeProcessManager 187 User Actions public with description remove and delete ProcessManagers for all particles in tha Particle Table EL this routine is invoked from RunManager void RemoveProcessManager public with description add process manager for particles created on the fly void AddProcessManager G4ParticleDefinition newParticle G4ProcessManager newManager 0 i G4VUserPrimaryGeneratorAction Example 6 3 G4VUserPrimaryGeneratorAction class G4VUserPrimaryGeneratorAction i Public G4VUserPrimaryGeneratorAction virtual G4VUserPrimaryGeneratorAction public virtual void GeneratePrimaries G4Event anEvent 0 6 2 Optional User Actions There are five virtual classes whose methods the user may override in order to gain control of the simulation at var ious stages Each method of each action class has an empty default implementation allowing the user to inherit and implement desired classes and methods Objects of user action classes must be registered with G4RunManager G4UserRunAction This class has three virtual methods which are invoked by G4RunManager for each run GenerateRun This method is invoked at the beginning of BeamOn Because the user can inherit the class G4Run and create his her own concrete class to store some information about the run the GenerateRun method is the place to instant
498. ticles and SetCuts G4double aValue tosetacut value in range for all particles in the particle table which invokes the rebuilding of the physics table When called the Construct method of G4VUserPhysicsList first invokes Const ructParticle and then ConstructProcess The ConstructProcess method must always invoke the AddTrans portation method in order to insure particle transportation AddTransportation must never be overridden G4VUserPhysicsList provides several utility methods for the implementation of the above virtual methods They are presented with comments in the class declaration in Example 6 2 185 User Actions Example 6 2 G4VUserPhysicsList class G4VUserPhysicsList Publier G4VUserPhysicsList virtual G4VUserPhysicsList public with description By calling the Construct method particles and processes are created Voir Construct OP protected with description These two methods of ConstructParticle and ConstructProcess will be invoked in the Construct method each particle type will be instantiated virtual void ConstructParticle 0 each physics process will be instantiated and registered to the process manager of each particle type virtual void ConstructProcess 0 protected with description User must invoke this method in his ConstructProcess implementation in order to insures particle transportation Caution this
499. tion G4VisExecut ive is sensitive to the G4VIS USE variables mentioned above If you do wish to write your own subclass you may do so You will see how to do this by looking at G4VisExecutive icc A typical extract is RegisterGraphicsSystem new G4DAWNFILE ifdef G4VIS_USE_OPENGLX RegisterGraphicsSystem new G4OpenGLImmediateX RegisterGraphicsSystem new G4OpenGLStoredX fendif If you wish to use G4VisExecut ive but register an additional graphics system XXX say you may do so either before or after initializing visManager gt RegisterGraphicsSytem new XXX visManager gt Initialize An example of a typical main function is given below 2 10 4 Writing the main Method to Include Visualization Now we explain how to write a visualization manager and the main function for Geant4 visualization In order that your Geant4 executable is able to perform visualization you must instantiate and initialize your Visualiza 27 Getting Started with Geant4 Running a Simple Example tion Manager in the main function The typical main function available for visualization is written in the following style Example 2 26 The typical main routine available for visualization fd C source codes main function for visualization ifdef GAVIS USE include G4VisExecutive hh endif int maintint age char argy d Instantiation and initialization of the Visualization Man
500. tion of this user guide For simplicity this section assumes that the Geant4 executable was compiled incorporating the DAWNFILE and the OpenGL Xlib drivers For details on creating an executable for visualization see Section 8 2 8 4 1 Scene scene handler and viewer In using the visualization commands it is useful to know the concept of scene scene handler and viewer A scene is a set of visualizable raw 3D data A scene handler is a graphics data modeler which processes raw data in a scene for later visualization And a viewer generates images based on data processed by a scene handler Roughly speaking a set of a scene handler and a viewer corresponds to a visualization driver The steps of performing Geant4 visualization are explained below though some of these steps may be done for you so that in practice you may use as few as just two commands such as vis open OGLIX plus vis drawVolume The seven steps of visualization are Step 1 Create a scene handler and a viewer Step 2 Create an empty scene Step 3 Add raw 3D data to the created scene Step 4 Attach the current scene handler to the current scene Step 5 Set camera parameters drawing style wireframe surface etc Step 6 Make the viewer execute visualization Step 7 Declare the end of visualization for flushing 222 Visualization These seven steps can be controlled explicitly to create multiple scenes and multiple vi
501. tion policy class name G4CrossSectionChargeIncrease Final state policy class name G4FinalStateChargeIncrease 147 Tracking and Physics Helium neutral processes Excitation one model Cross section policy class name G4CrossSectionExcitationMillerGreen Final state policy class name G4FinalStateExcitationMillerGreen Jonisation one model e Cross section policy class name G4CrossSectionlonisationRudd Final state policy class name G4FinalStatelonisationRudd Charge increase one model e Cross section policy class name G4CrossSectionChargeIncrease Final state policy class name G4FinalStateChargeIncrease Helium ionized once processes Excitation one model Cross section policy class name G4CrossSectionExcitationMillerGreen Final state policy class name G4FinalStateExcitationMillerGreen Jonisation one model e Cross section policy class name G4CrossSectionlonisationRudd Final state policy class name G4FinalStatelonisationRudd Charge increase one model e Cross section policy class name G4CrossSectionChargeIncrease Final state policy class name G4FinalStateChargeIncrease Charge decrease one model Cross section policy class name G4CrossSectionChargeDecrease Final state policy class name G4FinalStateChargeDecrease Helium ionised twice processes Excitation one model Cross section policy class name G4CrossSectionExcitationMillerGreen Final state p
502. tional Mass In the example below air is built from nitrogen and oxygen by giving the fractional mass of each component Example 2 9 Creating air by defining the fractional mass of its components a 14 01 g mole G4Element elN new G4Element name Nitrogen symbol N z 7 a a 16 00 g mole G4Element elO new G4Element name Oxygen symbol 0 z 8 a density 1 290 mg cm3 G4Material Air new G4Material name Air density ncomponents 2 Air gt AddElement elN fractionmass 70 perCent Air gt AddElement e10 fractionmass 30 perCent 2 3 5 Define a Material from the Geant4 Material Database In the example below air and water are accessed via the Geant4 material database Example 2 10 Defining air and water from the internal Geant4 database G4NistManager man G4NistManager Instance G4Material H20 man gt FindOrBuildMaterial G4 WATER G4Material Air man gt FindOrBuildMaterial G4 AIR 2 3 6 Print Material Information Example 2 11 Printing information about materials G4cout lt lt H20 print a given material G4cout lt lt G4Material GetMaterialTable print the list of materials In examples novice N03 N03DetectorConstruction cc you will find examples of all possible ways to build a material Getting Started with Geant4 Running a Simple Example 2 4 How to Specify Particles G4VuserPhysicsList is one of the mandatory user base classes described
503. tioning and completely filling the containing mother volume Consequently if a G4PVRep1ica is positioned inside a given mother it MUST be the mother s only daughter volume Replica s correspond to divisions or slices that completely fill the mother volume and have no offsets For Cartesian axes slices are considered perpendicular to the axis of replication The replica s positions are calculated by means of a linear formula Replication may occur along Cartesian axes kXAxis kYAxis kZAxis The replications of specified width have coordinates of form width nReplicas 1 0 5 n width 0 0 79 Detector Definition and Response where n 0 nReplicas 1 for the case of kXAxis and are unrotated Radial axis cylindrical polar kRho The replications are cons tubs sections centred on the origin and are unrotated They have radii of width nt offset to width n 1 offset where n 0 nReplicas 1 Phi axis cylindrical polar kPhi The replications are phi sections or wedges and of cons tubs form They have phi of offset n width to offset n 1 width where n 0 nReplicas 1 The coordinate system of the replicas is at the centre of each replica for the cartesian axis For the radial case the coordinate system is unchanged from the mother For the phi axis the new coordinate system is rotated such that the X axis bisects the angle made by each wedge and Z remains parallel to the mother s Z axis The solid associate
504. to different branches of the tree of the hierarchy of geometrical volumes 4 1 4 2 Repeated volumes In this case a single Physical Volume represents multiple copies of a volume within its mother volume allowing to save memory This is normally done when the volumes to be positioned follow a well defined rotational or translational symmetry along a Cartesian or cylindrical coordinate The Repeated Volumes technique is available for volumes described by CSG solids Replicas Replicas are repeated volumes in the case when the multiple copies of the volume are all identical The coordinate axis and the number of replicas need to be specified for the program to compute at run time the transformation matrix corresponding to each copy G4PVReplica const G4String amp pName G4LogicalVolume pCurrentLogical G4LogicalVolume pMotherLogical OR G4VPhysicalVolume const EAxis pAxis const G4int nReplicas const G4double width const G4double Onis Se 0 where pName String identifier for the replicated volume pCurrentLogical The associated Logical Volume pMotherLogical The associated mother volume pAxis The axis along with the replication is applied nReplicas The number of replicated volumes width The width of a single replica along the axis of replication offset Possible offset associated to mother offset along the axis of replication G4PVReplica represents nReplicas volumes differing only in their posi
505. to ppm for i in G4OpenGL eps do je basename i eps command convert i j ppm echo command command done Then mpeg2encode mpeg2encode par G4OpenGL mpg Then on Mac for example open G4OpenGL mpg opens a QuickTime player 8 10 2 DAWNFILE You need to invoke dawn in direct mode which picks up parameters from DAWN_1 history and suppress the GUI alias dawn dawn d export DAWN BATCH 1 Change OGLSX to DAWNFILE in the above set of Geant4 commands and run Then convert to ppm files as above for Eno SESI do je basename i eps command convert i j ppm echo Scommand command done Then make a par file make mpeg2encode parfile sh g4 ppm and edit mpeg2encode par diff mpeg2encode par mpeg2encode par ite MT fi sboyobie picture le omas 10 S NC 0 VA less vu ss OO 1 SS E input splekurewniskesrornmat e vy TU ne Wipe l vr UNT OE TOTO 7A Ves SUI number of first frame gt 0 number of first frame US IGS dl lt horizontal size lt vertical size gt 482 horizontal size gt 930 Vertical size Then encode and play mpeg2encode mpeg2encode par DAWN mpg open DAWN mpg 8 10 3 RayTracerX control verbose 2 vis open RayTracerX 600x600 0 0 Raytracer doesn t need a scene smoother not to vis drawVolume vis viewer reset 254 Visualization vis viewer set style surface vis viewer set projection perspective 50 deg c
506. to view in any VRML browser some as web browser plug ins Requires VRML browser many different choices for different operating systems Rendered photorealistic image with some interactive features zoom rotate translate Limited printing ability pixel graphics not vector graphics RayTracer Create a jpeg file Forms image by using Geant4 s own tracking to follow photons through the detector Can show geometry but not trajectories Canrender any geometry that Geant4 can handle such as Boolean solids e Supports shadows transparency and mirrored surfaces ASCIITree Text dump of the geometry hierarchy Not graphical Control over level of detail to be dumped Cancalculate mass and volume of any hierarchy of volumes 8 1 3 Choose the Driver that Meets Your Needs If you want very responsive photorealistic graphics and have the OpenGL libraries installed OpenGL is a good solution if you have the Motif extensions this also gives GUI control f you want very responsive photorealistic graphics plus more interactivity and have the OpenInventor libraries installed Openlnventor is a good solution f you want GUI control want to be able to pick on items to inquire about them identity momentum etc perhaps want to render to vector formats and a wireframe look will do HepRep WIRED will meet your needs f you want to render highest quality photorealistic images for use in a poster or a technical design
507. together and can configured either interactively or in commands or in compiled code The filters can be inverted set to be inactive or set in a verbose mode The above models are described briefly below followed by some example configuration commands G4TrajectoryChargeFilter This model filters trajectories according to charge In standard running mode only trajectories with charges match ing those registered with the model will pass the filter G4TrajectoryParticleFilter This model filters trajectories according to particle type In standard running mode only trajectories with particle types matching those registered with the model will pass the filter G4TrajectoryOriginVolumeFilter This model filters trajectories according to originating volume name In standard running mode only trajectories with originating volumes matching those registered with the model will pass the filter 248 Visualization G4TrajectoryAttributeFilter This model filters trajectories based on the HepRep style attributes associated with trajectories Each attribute drawer can be configured with interval and or single value data Single value data should override the interval data Units should be specified on the command line if the attribute unit is specified either as a G4BestUnit or if the unit is part of the value string 8 8 1 Controlling from Commands Multiple trajectory filter models can be created and configured using commands in the v
508. tory class from tracking src G4Trajectory cc this is what you get with the plain vis scene add trajectories command available attributes will be Track ID Parent ID Particle Name Charge PDG Encoding Momentum 3 Vector Momentum magnitude Number of points Using vis scene add trajectories rich will get you additional attributes You may also add addi tional attributes of your choosing by modifying the relevant part of G4Trajectory look for the methods GetAttDefs and CreateAttValues If you are using your own trajectory class you may want to consider copying these methods from G4Trajectory 227 Visualization 8 4 13 How to save a visualized views to PostScript files Most of the visualization drivers offer ways to save visualized views to PostScript files or Encapsulated PostScript EPS files by themselves The DAWNFILE driver which co works with Fukui Renderer DAWN generates vectorized PostScript data with analytical hidden line surface removal and so it is well suited for technical high quality outputs for pre sentation documentation and debugging geometry In the default setting of the DAWNFILE drivers EPS files named g4 00 eps g4_0l eps g4 02 eps are automatically generated in the current directory each time when visualization is performed and then a PostScript viewer gv is automatically invoked to visualize the generated EPS files For large data sets it may take time to gene
509. towards various user interface tools and allows Geant4 to utilize the state of the art GUI tools such as Motif and Java etc The richness of the collaboration has permitted for different groups to offer various user interfaces to the Geant4 command system Currently available are the following 1 Character terminal dumb terminal and tcsh bash like terminal the default user interface of Geant4 2 Xm Xaw Win32 variations of the upper terminal by using a Motif Athena or Windows widget to retrieve commands and 3 GAG a fully Graphical User Interface and its extension GainServer of the client server type Full implementation of the character terminals 1 and 2 is included in the standard Geant4 distribution in the source interfaces basic directory As for GAG with rich GUI functionalities its front end classes are included in the Geant4 distribution in the source interfaces GAG directory The corresponding GUI package is available either from the author s Web pages see URL below or in the distributed package under the environ ment s MOMO directory GAG GainServer s client GUI Gain http erpc 1 naruto u ac jp geant4 2 8 2 A Short Description of Available Interface Classes 2 8 2 1 G4Ulterminal and G4Ultcsh classes These interfaces open a session on the character terminal G4Ulterminal runs on all platform supported by Geant4 including cygwin on Windows while G4UItcsh runs on Solaris and Linux G4Ultesh supports user friendly key
510. tp geant4 kek jp GEANT4 vis DAWNCUT http geant4 kek jp GEANT4 vis DAWN About_DAWNCUT html DAVID http geant4 kek jp GEANT4 vis DAWN About DAVID html Geant4 Visualization Tutorial using the DAWN Renderer http geant4 slac stanford edu Presentations vis GDA WNTutorial G4DA WNTutorial html 8 3 8 VRML These drivers were developed by Satoshi Tanaka and Yasuhide Sawada Fukui University They generate VRML files which describe 3D scenes to be visualized with a proper VRML viewer at either a local or a remote host It realizes virtual reality visualization with your WWW browser There are many excellent VRML viewers which enable one to perform interactive spinning of detectors walking and or flying inside detectors or particle showers interactive investigation of detailed detector geometry etc There are two kinds of VRML drivers the VRMLFILE driver and the VRML Network driver The VRMLFILE driver is usually recommended since it is faster and safer in the sense that it is not affected by network conditions The VRMLFILE driver sends 3D data to your VRML viewer which is running on the same host machine as Geant4 via an intermediate file named g4 wr1 created in the current directory This file can be re visualization afterwards In visualization the name of the VRML viewer should be specified by setting the environment variable G4VRML_VIEWER beforehand For example 5 setenv G4VRML_VIEWER netscape Its de
511. tracks left over from the previous event are stored in the postpone to next event stack If so it attemps to move them to the urgent stack But first the PrepareNewEvent method of G4UserStackingAction is called Here tracks may be re classified by the user and sent to the urgent or waiting stacks or deferred again to the postpone to next event stack As the event is processed G4StackManager pops tracks from the urgent stack until it is empty At this point the NewStage method of G4UserStackingAction is called In this method tracks from the waiting stack may be sent to the urgent stack retained in the waiting stack or postponed to the next event Details of the user defined methods of G4UserStackingAction and how they affect track stack management are given in Section 6 3 3 6 Event Generator Interface 3 6 1 Structure of a primary event 3 6 1 1 Primary vertex and primary particle The G4Event class object should have a set of primary particles when it is sent to G4EventManager via pro cessOneEvent method It is the mandate of your G4VUserPrimaryGeneratorAction concrete class to send primary particles to the G4Event object The G4PrimaryParticle class represents a primary particle with which Geant4 starts simulating an event This class object has information on particle type and its three momenta The positional and time information of pri mary particle s are stored in the G4PrimaryVertex class object and thus this class o
512. trix in the global reference system or as a hierarchy of physical volumes up to the root of the geometrical tree A touchable is a geometrical entity volume or solid which has a unique placement in a detector description It is represented by an abstract base class which can be implemented in a variety of ways Each way must provide the capabilities of obtaining the transformation and solid that is described by the touchable 4 1 5 2 What can a Touchable do All G4VTouchable implementations must respond to the two following requests where in all cases by depth it is meant the number of levels up in the tree to be considered the default and current one is 0 1 Get Translation depth 2 GetRotation depth that return the components of the volume s transformation Additional capabilities are available from implementations with more information These have a default imple mentation that causes an exception Several capabilities are available from touchables with physical volumes 3 GetSolid depth gives the solid associated to the touchable 4 Get Volume depth gives the physical volume 5 GetReplicaNumber depth or Get CopyNumber depth which return the copy number of the phys ical volume replicated or not Touchables that store volume hierarchy history have the whole stack of parent volumes available Thus it is possible to add a little more state in order to extend its functionality We add a pointer to a l
513. truct a simple detector geometry The software installation instructions and notes for GGE and other JAV A based UI tools can be freely downloaded from the Geant4 GUI and Environments web site of Naruto University of Education in Japan 4 1 9 1 Materials elements and mixtures GGE provides the database of elements in a form of the periodic table which users can use to construct new materials GGE provides a pre constructed database of materials taken from the PDG book They can be loaded used edited and saved as persistent objects Users can also create new materials either from scratch or by combining other materials creating a material from scratch Use Name A Z Density Unit State Temper Unit Pressure Unit ature Only the elements and materials used in the logical volumes are kept in the detector object and are used to generate C constructors Use marks the used materials Constructor to create a material from a combination of elements subsequently added via AddElement Use Name Elements Density Unit State Tempera Unit Pressure Unit ture By clicking the column Elements a new window is open to select one of two methods 98 Detector Definition and Response Add an element giving fraction by weight Add an element giving number of atoms 4 1 9 2 Solids The most popular CSG solids G4Box G4Tubs G4Cons G4Trd and specific
514. try is be done after the compilation of the source code MyDetectorConstruction cc with appropriate parts of Geant4 In particular only the geometry and visualization together with the small other parts they depend on are needed 4 1 10 Converting Geometries from Geant3 21 4 1 10 1 Approach G3toG4 is the Geant4 facility to convert GEANT 3 21 geometries into Geant4 This is done in two stages 1 The user supplies a GEANT 3 21 RZ file rz containing the initialization data structures An executable rz tog4 reads this file and produces an ASCII call list file containing instructions on how to build the geometry The source code of rztog4 is FORTRAN 2 A call list interpreter G4BuildGeom cc reads these instructions and builds the geometry in the user s client code for Geant4 99 Detector Definition and Response 4 1 10 2 Importing converted geometries into Geant4 Two examples of how to use the call list interpreter are supplied in the directory examples extended g3tog4 1 cltog4 is a simple example which simply invokes the call list interpreter method G4BuildGeom from the G3toG4DetectorConstruction class builds the geometry and exits 2 clGeomet ry is more complete and is patterned as for the novice Geant4 examples It also invokes the call list interpreter but in addition allows the geometry to be visualized and particles to be tracked To compile and build the G3toG4 libraries you need to have set in your en
515. tself Run time commands are provided by the tool to navigate in the geometry tree UNIX like navigation of the logical volume hierarchy is provided by the o1ap cd command The root of the logical volume tree can be accessed by 104 Detector Definition and Response the character Any node in the volume tree can be accessed by a separated string of regular expressions If is at the beginning of the string the tree hierarchy is transversed from the root otherwise from the currently chosen logical volume Further the command olap goto regexp can be used to jump to the first logical volume matching the expression regexp Every successful navigation command olap cd olap goto results in the construction of a NewWorld the mother volume being the argument of the command and the daughter volumes being the direct daughters of the mother volume olap pwd always shows where in the full geometrical hierarchy the current NewWorld and mother volume are located For more detailed information view the README file provided with the tool 4 1 12 Dynamic Geometry Setups Geant4 can handle geometries which vary in time e g a geometry varying between two runs in the same job It is considered a change to the geometry setup whenever the shape or dimension of an existing solid is modified the positioning translation or rotation of a volume is changed a volume or a set of volumes tree is removed replaced o
516. tual methods ProcessHits This method is invoked by G4SteppingManager when a step is composed in the G4LogicalVolume which has the pointer to this sensitive detector The first argument of this method is a G4Step object of the current step The second argument is a G4TouchableHistory object for the Readout geometry described in the next section The second argument is NULL if Readout geometry is not assigned to this sensitive detector In this method one or more G4VHit objects should be constructed if the current step is meaningful for your detector Initialize This method is invoked at the beginning of each event The argument of this method is an object of the G4HCofThisEvent class Hit collections where hits produced in this particular event are stored can be associated with the G4HCofThisEvent object in this method The hit collections associated with the G4HCofThisEvent object during this method can be used for during the event processing digitization EndOfEvent This method is invoked at the end of each event The argument of this method is the same object as the previous method Hit collections occasionally created in your sensitive detector can be associated with the G4HCofThisEvent object 119 Detector Definition and Response 4 4 3 Readout geometry This section describes how a Readout geometry can be defined A Readout geometry is a virtual parallel ge ometry for obtaining the ch
517. ty resulted from nuclear inter actions 9 2 1 17 Run amp Event e REOI information between primary particles and hits and usage of user information classes REO2 simplified fixed target application for demonstration of primitive scorers REO3 use of Ul command based scoring showing how to create parallel world s for defining scoring mesh es 9 2 1 18 Visualization Examples of customisation for visualization 9 3 Advanced Examples 9 3 1 Advanced Examples Geant4 advanced examples illustrate realistic applications of Geant4 in typical experimental environments Most of them also show the usage of analysis tools such as histograms ntuples and plotting various visualization features and advanced user interface facilities together with the simulation core Note Maintenance and updates of the code is under the responsibility of the authors These applications are therefore not subject to regular system testing and no guarantee can be provided The advanced examples include air shower a simulation of the ULTRA detector with Fresnel lenses for UV and charged particles detection in cosmic rays brachytherapy illustrating a typical medical physics application simulating energy deposit in a Phantom filled with soft tissue hadrontherapy illustrating a application simulating an hadron therapy beam line for medical physics human phantom implementing an Anthropomorphic Phantom body built importing the descri
518. ualization ff endcof Crk source code In the above you should also describe vis open command somewhere in your C codes or execute the command from G UI at the executing stage 8 5 3 Visualization of trajectories In order to visualize trajectories you can use the method void G4Trajectory DrawTrajectory defined in the tracking category In the implementation of this method the following drawing method of G4VVisManager is used ff A drawing method of G4Polyline virtual void G4VVisManager Draw const G4Polyline amp The real implementation of this method is described in the class G4VisManager At the end of one event a set of trajectories can be stored as a list of G4Trajectory objects There fore you can visualize trajectories for example at the end of each event by implementing the method MyEventAction EndOfEventAction as follows LL C source codes void ExN03EventAction EndOfEventAction const G4Event evt extract the trajectories and draw them if G4VVisManager GetConcreteInstance G4TrajectoryContainer trajectoryContainer evt gt GetTrajectoryContainer G4int n_trajectories 0 if trajectoryContainer n trajectories trajectoryContainer gt entries for G4int i 0 i lt n trajectories i G4Trajectory trj G4Trajectory evt gt GetTrajectoryContainer i if drawFlag all trj gt DrawTrajectory 50 else if drawFlag
519. ularly well for magnetic fields that are almost uniform Once a method is chosen that calculates the track s propagation in a specific field the curved path is broken up into linear chord segments These chord segments are determined so that they closely approximate the curved path The chords are then used to interrogate the Navigator as to whether the track has crossed a volume boundary Several parameters are available to adjust the accuracy of the integration and the subsequent interrogation of the model geometry How closely the set of chords approximates a curved trajectory is governed by a parameter called the miss distance also called the chord distance This is an upper bound for the value of the sagitta the distance between the real curved trajectory and the approximate linear trajectory of the chord By setting this parameter the user can control the precision of the volume interrogation Every attempt has been made to ensure that all volume interrogations will be made to an accuracy within this miss distance miss distance real trajectory Figure 4 6 The curved trajectory will be approximated by chords so that the maximum estimated distance between curve and chord is less than the the miss distance In addition to the miss distance there are two more parameters which the user can set in order to adjust the accuracy and performance of tracking in a field In particular these parameters govern the accuracy of the interse
520. un manager must be given all the information necessary to build and run the simulation including Getting Started with Geant4 Running a Simple Example how the detector should be constructed all the particles and all the physics processes to be simulated how the primary particle s in an event should be produced and RWN any additional requirements of the simulation In the sample main the lines runManager 5SetUserInitialization new ExN0lDetectorConstruction runManager gt SetUserInitialization new ExNOlPhysicsList create objects which specify the detector geometry and physics processes respectively and pass their pointers to the run manager ExNO1DetectorConstruction is an example of a user initialization class which is derived from G4VUserDetectorConstruction This is where the user describes the entire detector setup including its geometry the materials used in its construction adefinition of its sensitive regions and the readout schemes of the sensitive regions Similarly ExNO1PhysicsList is derived from G4VUserPhysicsList and requires the user to define the particles to be used in the simulation e the range cuts for these particles and all the physics processes to be simulated The next instruction in main runManager gt SetUserAction new ExNO1PrimaryGeneratorAction creates an instance of a particle generator and passes its pointer to the run manager ExNO1IPrimaryGenerat
521. unction of the copy number both when a strong symmetry exist and when it does not The user implements the desired parameterisation function and the program computes and updates automatically at run time the information associated to the Physical Volume An example of creating a parameterised volume by dimension and position exists in novice exam ple N02 The implementation is provided in the two classes ExNO2DetectorConstruction and ExNO2ChamberParameterisation To create a parameterised volume one must first create its logical volume like trackerChamberLV below Then one must create his own parameterisation class ExNO2ChamberParameterisation and instantiate an object of this class chamberParam We will see how to create the parameterisation below Example 4 3 An example of Parameterised volumes bi morc exem Tracker segments ff frui es An example of Parameterised volumes dummy values for G4Box modified by parameterised volume G4VSolid solidChamber new G4Box chamberBox 10 cm 10 cm 10 cm G4LogicalVolume trackerChamberLV new G4LogicalVolume solidChamber Aluminum trackerChamberLV G4VPVParameterisation chamberParam new ExNO2ChamberParameterisation 6 NoChambers XA c Sti 2 of centre of first Olen Z spacing of centres Al CM Width Chamber 50 cm lengthInitial trackerSize 2 lengthFinal G4VPhysicalVolume trackerChamber phys new G4PVParameterise
522. up of more than one event it is essential to access more than one event at the same moment By invoking this method G4RunManager keeps nPrevious G4Event objects This method must be invoked before proceeding to BeamOn GetPreviousEvent G4int i_thPrevious The pointer to the i_thPrevious G4Event object can be obtained through this method A pointer to a const object is returned It is inevitable that i_thPrevious events must have already been simulated in the same run for getting the i_thPrevious event Otherwise this method returns nu11 AbortRun This method should be invoked whenever the processing of a run must be stopped It is valid for GeomClosed and EventProc states Run processing will be safely aborted even in the midst of processing an event However the last event of the aborted run will be incomplete and should not be used for further analysis 3 4 1 3 G4UserRunAction G4UserRunAction is one of the user action classes from which you can derive your own concrete class This base class has two virtual methods as follows BeginOfRunAction This method is invoked at the beginning of the BeamOn method but after confirmation of the conditions of the Geant4 kernel Likely uses of this method include setting a run identification number booking histograms setting run specific conditions of the sensitive detectors and or digitizer modules e g dead channels EndOfRunAction This method is invoked at t
523. uple uer e et tere in ss espe asta a ki wei aes 178 3 6 3 File T O for the Physics Table 3 re rtt E EE S SES 178 5 6 4 Building the Physics Table sse emere 179 JI User Limits iee MTS 179 5 7 1 General Concepts 1 skina sis ai ee a k ai Ka su PII PREIS 179 5 7 2 Processes co working with G4UserLimits 179 5 8 Track Error Propagation Likti eee eie a a a sk sis ks coast sa er TE 180 928215 PHYSICS une eruere RHEINE 180 5 82 Trajectory state usse hotte G si ais eR RU etg eee ees aa 180 3 8 3 Trajectory state Error sissioni Eee ses OR E p ere Dav i Eo asset agre o ree rete 182 2 8 4 bil AE 182 5 8 5 Managing the track propagation sssse meme 183 2 8 6 Limiting the Step iuo pvrese Eesti e periret Rie crei si 184 Os UserzActions irt s rore eR EP PEIPER E I bonnets REM ER POI teo kn d dads REX Pate veu v deest dn 185 6 1 Mandatory User Actions and Initializations esee 185 6 2 Optional User Actions pisser odere ERR RR a RE E ER Rp siai 188 0 3 User Information Classes ien tT Ier see tee dees peed TERR RPM 192 6 3 1 G4VUserBventIntorin tion eto OE ES PE a ERR MASTER ERO Pi ERE RA TEES 192 6 3 2 G4VUserTrackInformation esee HI HI HI men meme hee rene 193 6 3 3 GAVUserPrimary VertexInformation and G4V UserPrimaryTrackInformation 193 6 3 4 G4VUserRegionInformation esses HI ee hene rentrer 193 7 Communication and Contr
524. used to set a pointer of a concrete class object to G4Track given that the G4Track object is available only by pointer to const The ideal place to copy a G4VUserTrackInformation object from a mother track to its daughter tracks is G4UserTrackingAction PostUserTrackingAction Example 6 9 Copying G4VUserTrackInformation from mother to daughter tracks void REO1TrackingAction PostUserTrackingAction const G4Track aTrack G4TrackVector secondaries fpTlrackingManager gt GimmeSecondaries if secondaries REOlTrackInformation info REOlTrackInformation aTrack gt GetUserInformation size t nSeco secondaries gt size if nSeco gt 0 1 for size t i 0 i nSeco i REOlTrackInformation infoNew new REO1TrackInformation info secondaries 1 gt SetUserInformation infoNew The concrete class object is deleted by the Geant4 kernel when the associated G4Track object is deleted In case the user wants to keep the information it should be copied to a trajectory corresponding to the track 6 3 3 G4VUserPrimaryVertexInformation and G4VUserPrimaryTracklnformation These abstract classes allow the user to attach information regarding the generated primary vertex and pri mary particle Concrete class objects derived from these classes should be attached to G4PrimaryVertex and G4PrimaryParticle class objects respectively The concrete class objects are deleted by the Geant4 Kernel when the ass
525. uter polygonal surfaces The polygons do not need to fill 360 degrees but have a start and opening angle The constructor takes the following parameters G4BREPSolidPolyhedra const G4String amp pName G4double start angle G4double opening angle G4int sides G4int num_z_planes G4double z_start const G4double z_values const G4double RMIN const G4double RMAX which in addition to its name have the following meaning start angle starting angle opening angle opening angle sides number of sides of each polygon in the x y plane num z planes number of planes perpendicular to the z axis used z start starting value of z z values z coordinates of each plane RMIN radius of inner polygon at each corner RMAX radius of outer polygon at each corner the shape is defined by the number of sides sides of the polygon in the plane perpendicular to the z axis 4 1 2 4 Tessellated Solids In Geant4 it is also implemented a class GaTessellatedSolid which can be used to generate a generic solid defined by a number of facets GAVFacet Such constructs are especially important for conversion of complex geometrical shapes imported from CAD systems bounded with generic surfaces into an approximate description with facets of defined dimension see Figure 4 1 Figure 4 1 Example of geometries imported from CAD system and converted to tessellated solids They can also be used to generate a s
526. various drivers Note that not all drivers can be installed on all systems Table 8 1 in Section 8 3 lists all the available drivers and the platforms on which they can be installed For any of the visualization drivers to work the corresponding graphics system must be installed beforehand Unless the environment variable GAVIS NONE is set to 1 visualization drivers that do not depend on external libraries are automatically incorporated into Geant4 libraries during their installation Here installation of Geant4 libraries means the generation of Geant4 libraries by compilation The automatically incorporated visualization drivers are DAWNFILE HepRepFile HepRepXML RayTracer VRMLIFILE VRML2FILE and ATree and GAGTree The OpenGL OpenInventor and RayTracerX drivers are not incorporated by default Nor are the DAWN Net work and VRML Network drivers because they require the network setting of the installed machine In order to incorporate them the environment variables G4AVIS BUILD DRIVERNAME DRIVER should be set to 1 before installing the Geant4 libraries setenv G4VIS BUILD OPENGLX DRIVER setenv G4VIS BUILD OPENGLXM DRIVER setenv G4VIS BUILD OIX DRIVER setenv G4VIS BUILD RAYTRACERX DRIVER setenv G4VIS BUILD DAWN DRIVER setenv G4VIS BUILD VRML DRIVER OpenGL Xlib driver OpenGL Motif driver OpenInventor Xlib driver RayTracer XLib driver DAWN Network driver VRML Network ererererrrr Se Hb sb dE SE E
527. vent fKill the track is deleted immediately and not stored in any stack These assignments may be made based on the origin of the track which is obtained as follows G4int parent ID aTrack gt get parentID where parent ID 0 indicates a primary particle parent ID 0 indicates a secondary particle parent ID 0 indicates postponed particle from previous event NewStage is invoked when the urgent stack is empty and the waiting stack contains at least one G4Track object Here the user may kill or re assign to different stacks all the tracks in the waiting stack by calling the 189 User Actions stackManager gt ReClassify method which in turn calls the ClassifyNewTrack method If no user action is taken all tracks in the waiting stack are transferred to the urgent stack The user may also decide to abort the current event even though some tracks may remain in the waiting stack by calling stackManag er clear This method is valid and safe only if it is called from the G4UserStackingAction class A global method of event abortion is G4UImanager UImanager G4UImanager GetUlpointer UImanager ApplyCommand event abort PrepareNewEvent is invoked at the beginning of each event At this point no primary particles have been converted to tracks so the urgent and waiting stacks are empty However there may be tracks in the postponed to next event stack for each of these the ClassifyNewTrack
528. verloaded implementation of G4VHitsCollection DrawAllHits will be held by for example class MyTrackerHitsCollection inheriting class G4VHitsCollection as follows C source codes An example of giving concrete implementation of G4VHitsCollection Draw Li using class MyTrackerHit public G4VHitsCollection Jd void MyTrackerHitsCollection DrawAllHits G4int n_hit theCollection entries for G4int i 0 i lt n hit i theCollection i Draw end of C source codes 233 Visualization Thus you can visualize hits as well as trajectories for example at the end of each event by implementing the method MyEventAction EndOfEventAction as follows void MyEventAction EndOfEventAction const G4Event evt fpEventManager gt get const currentEvent G4SDManager SDman G4String colNam G4int trackerCollID SDman get collectionID colNam TrackerCollection G4int calorimeterCollID SDman get collectionID colNam CalCollection G4SDManager get SDMpointer G4TrajectoryContainer trajectoryContainer evt get trajectoryContainer G4int n trajectories 0 if trajectoryContainer n trajectories trajectoryContainer entries G4HCofThisEvent HCE G4int n_hitCollection if HCE n_hitCollection HCE gt get_capacity evt get HCofThisEvent 0 G4VVisManager pVVisManager G4VVisManager GetConcreteInstanc
529. vironment the variable G4LIB_BUILD_G3TOG4 at the time of installation The G3toG4 libraries are not built by default Then simply type gmake from the top level source g3tog4 directory To build the converter executable rztog4 simply type gmake bin To make everything simply type gmake global To remove all G3t 0G4 libraries executables and d files simply type gmake clean 4 1 10 3 Current Status The package has been tested with the geometries from experiments like BaBar CMS Atlas Alice Zeus L3 and Opal Here is a comprehensive list of features supported and not supported or implemented in the current version of the package Supported shapes all GEANT 3 21 shapes except for GTRA CTUB PGON PCON are built using the specific solids G4Polycone and G4Polyhedra GEANT 3 21 MANY feature is only partially supported MANY positions are resolved in the G3t oG4MANY function which has to be processed before G3toG4BuildTree it is not called by default In order to resolve MANY the user code has to provide additional info using G4gsbool G4String volName G4String manyVolName function for all the overlapping volumes Daughters of overlapping volumes are then resolved automatically and should not be specified via Gsbool Limitation a volume with a MANY position can have only this one position if more than one position is needed a new volume has to be defined gsvolu for each position e GSDV routines
530. vis viewer flush HEHEHE HEE HEE Visualization E E AE AE AE AE AE AE HH E AE FE FEE FE FE AE FE TE AE FE TE AE FE TE HE FE E E E EEE EEE with the DAWNFILE driver FE EAE FE AE FE TE AE FE FE AE FE TE HE FE E E E EE E EEE Invoke the DAWNFILE driver Create a scene handler and a viewer for the DAWNFILE driver vis open DAWNFILE Bird s eye view of a detector component Absorber drawing style hidden surface removal viewpoint theta phi 35 deg 45 deg zoom factor 1 1 of the full screen size coordinate axes x axis red y axis green z axis blue uui M 0 070 length 500 mm vis viewer reset vis viewer set style surface vis viewer zoom alg 3l vis viewer set viewpointThetaPhi 35 45 vis drawVolume Absorber vis scene add axes 0 0 0 500 mm vis scene add text D OG Omm x0 100 140 Absorber vis viewer flush Bird s eye view of the whole detector components vis viewer set culling global false makes the invisible world volume visible The invisibility of the world volume is set in ExN03DetectorConstruction cc vis viewer set style wireframe vis viewer set culling global false vis drawVolume vis scene add axes vis scene add text vis viewer flush HHTHEEHHEHEREHEEEEE END of visl mac H dHEEEHEEREEEE EE 500 mm 0 0 0 m SOS 505200 world 2 10 5 2 Visualization of events The following session visualizes events tajectories with the OpenGL Xlib driver and then wi
531. what is limited is the curvature or exactly the value of the magnetic field divided by the value of the momentum transversal to the field This can be set by invoking the user command G4UImanager GetUIpointer gt ApplyCommand geant4e limits magField MY VALUE The classes that limit the step are implemented as GEANT4 processes Therefore the invocation of the above mentioned commands should only be done after the initialization for example after G4ErrorPropagatorManager InitGeant4e 184 Chapter 6 User Actions 6 1 Mandatory User Actions and Initializations Geant4 has three virtual classes whose methods the user must override in order to implement a simulation They require the user to define the detector specify the physics to be used and describe how initial particles are to be generated G4VUserDetectorConstruction Example 6 1 G4VUserDetectorConstruction class G4VUserDetectorConstruction public G4VUserDetectorConstruction virtual G4VUserDetectorConstruction OUEST virtual G4VPhysicalVolume Construct 0 un GAVUserPhysicsList This is an abstract class for constructing particles and processes The user must derive a concrete class from it and implement three virtual methods ConstructParticle toinstantiate each requested particle type e ConstructPhysics to instantiate the desired physics processes and register each of them with the process managers of the appropriate par
532. when the track comes to one of these limits Step limitation occurs only for the final step Example of G4UserLimits can be found in examples novice N02 see DetectorConstruction and PhysicsList 5 8 Track Error Propagation The error propagation package serves to propagate one particle together with its error from a given trajectory state until a user defined target is reached a surface a volume a given track length 5 8 1 Physics The error propagator package computes the average trajectory that a particle would follow This means that the physics list must have the following characteristics No multiple scattering Norandom fluctuations for energy loss Nocreation of secondary tracks No hadronic processes It has also to be taken into account that when the propagation is done backwards in the direction opposed to the one the original track traveled the energy loss has to be changed into an energy gain All this is done in the G4ErrorPhysicsList class that is automatically set by G4ErrorPropagatorManager as the GEANT4 physics list It sets GAErrorEnergyLoss as unique elec tromagnetic process This process uses the GEANT4 class G4EnergyLossForExtrapolator to compute the average energy loss for forwards or backwards propagation To avoid getting too different energy loss calcu lation when the propagation is done forwards when the energy at the beginning of the step is used or backwards when the energy at the en
533. with materials The ConstructParticle method is implemented as below Example 2 12 Construct a proton and a geantino void ExN0O1PhysicsList ConstructParticle G4Proton ProtonDefinition G4Geantino GeantinoDefinition Due to the large number of pre defined particles in Geant4 it is cumbersome to list all the particles by this method If you want all the particles in a Geant4 particle category there are six utility classes corresponding to each of the particle categories which perform this function G4BosonConstructor G4LeptonConstructor G4MesonConstructor G4BarionConstructor e G4IonConstructor G4ShortlivedConstructor An example of this is shown in ExNO5PhysicsList listed below Example 2 13 Construct all leptons void ExN05PhysicsList ConstructLeptons Construct all leptons G4LeptonConstructor pConstructor pConstructor ConstructParticle 11 Getting Started with Geant4 Running a Simple Example 2 4 2 Range Cuts To avoid infrared divergence some electromagnetic processes require a threshold below which no secondary will be generated Because of this requirement gammas electrons and positrons require production thresholds which the user should define This threshold should be defined as a distance or range cut off which is internally converted to an energy for individual materials The range threshold should be defined in the initialization phase using the Set
534. with two Z sections G4ExtrudedSolid const G4String amp std vector lt G4TwoVector gt polygon std vector lt ZSection gt G4ExtrudedSolid const G4String amp std vector lt G4TwoVector gt polygon z G4double G4TwoVector offl G4TwoVector off2 G4double scalel G4double scale2 pName zsections pName Bz In the picture poligon 30 30 30 30 30 30 30 30 15 303 115 1543 15 15 1 15 30 60 0 30 0 8 0 30 1 60 0 30 1 2 zsections 15 10 0 0 0 6 68 Detector Definition and Response The z sides of the solid are the scaled versions of the same polygon polygon the vertices of the outlined polygon defined in clock wise order zsections the z sections defined by z position in increasing order hz Half length in Z offl off2 Offset of the side in hz and hz respectively scalel scale2 Scale of the side in hz and hz respectively Box Twisted A box twisted along one axis can be defined as follows G4TwistedBox const G4String amp pName G4double twistedangle G4double pDx G4double pDy G4double pDz In the picture twistedangle 30 Degree pDx 30 pDy 40 pDz 60 G4TwistedBox is a box twisted along the z axis The twist angle cannot be greater than 90 degrees twistedangle Twist angle pDx Half x length pDy Half y length pDz Half z length Trapezoid Twisted alon
535. y 2 200 g cm3 G4Material SiO2 new G4Material name quartz density ncomponents 2 SiO2 AddElement elSi natoms 1 Si02 gt AddElement 10 natoms 2 density 8 280 g cm3 G4Material PbWO4 new G4Material name PbWO4 density ncomponents 3 PbWO4 AddElement 610 natoms 4 PbWO4 AddElement elW natoms 1 PbWO4 AddElement elPb natoms 1 define a material from elements case 2 mixture by fractional mass density 1 290 mg cm3 G4Material Air new G4Material name Air density ncomponents 2 Air AddElement elN fractionmass 0 7 Air AddElement elO fractionmass 0 3 define a material from elements and or others materials mixture of mixtures density 0 200 g cm3 G4Material Aerog new G4Material name Aerogel density ncomponents 3 Aerog gt AddMaterial Si02 fractionmass 62 5 perCent Aerog gt AddMaterial H20 fractionmass 37 4 perCent Aerog gt AddElement elC fractionmass 0 1 perCent examples of gas in non STP conditions density 27 mg cm3 pressure 50 atmosphere temperature 325 kelvin G4Material CO2 new G4Material name Carbonic gas density ncomponents 2 kStateGas temperature pressure CO2 gt AddElement elC natoms 1 CO2 gt AddElement elO natoms 2 density 0 3 mg cm3 pressure 2 ratmosphere temperature 500 kelvin G4Material steam new G4Material name Water steam density ncomponents
536. y allows to import any shape with some degree of approximation the converted CAD models can then be imported through GDML Geometry Description Markup Language into Geant4 and be represented as G4TessellatedSolid shapes 4 1 3 Logical Volumes The Logical Volume manages the information associated with detector elements represented by a given Solid and Material independently from its physical position in the detector A Logical Volume knows which physical volumes are contained within it It is uniquely defined to be their mother volume A Logical Volume thus represents a hierarchy of unpositioned volumes whose positions relative to one another are well defined By creating Physical Volumes which are placed instances of a Logical Volume this hierarchy or tree can be repeated A Logical Volume also manages the information relative to the Visualization attributes Section 8 6 and user de fined parameters related to tracking electro magnetic field or cuts through the G4UserLimits interface By default tracking optimization of the geometry voxelization is applied to the volume hierarchy identified by a logical volume It is possible to change the default behavior by choosing not to apply geometry optimization for a given logical volume This feature does not apply to the case where the associated physical volume is a parameterised volume in this case optimization is always applied G4LogicalVolume G4VSolid pSolid G4Material pMaterial
537. y be invoked to request the data set to recalculate its internal database or otherwise reset its state after a change in the cuts or other parameters of the given particle type void DumpPhysicsTable const G4ParticleDefinition amp 0 150 Tracking and Physics This method may be invoked to request the data set to print its internal database and or other state information for the given particle type to the standard output stream Cross section data store Cross section data sets are used by the process for the calculation of the physical interaction length A given cross section data set may only apply to a certain energy range or may only be able to calculate cross sections for a particular type of particle The class G4CrossSectionDataStore has been provided to allow the user to specify if desired a series of data sets for a process and to arrange the priority of data sets so that the appropriate one is used for a given energy range particle and material It implements the following public methods G4CrossSectionDataStore G4CrossSectionDataStore and G4double GetCrossSection const G4DynamicParticle const G4Element For a given particle and material this method returns a cross section value provided by one of the collection of cross section data sets listed in the data store object If there are no known data sets a G4Exception is thrown and DBL_MIN is returned Otherwise each data set in the list is queri
538. y coming from your Readout geometry Note that since the association is done through a sensitive detector object it is perfectly possible to have several Readout geometries in parallel Definition of a virtual geometry setup The base class for the implementation of a Readout geometry is G4VReadoutGeometry This class has a single pure virtual protected method virtual G4VPhysicalVolume build 0 which you must override in your concrete class The G4VPhysicalVolume pointer you will have to return is of the physical world of the Readout geometry The step by step procedure for constructing a Readout geometry is inherit from G4VReadoutGeometry to define a MyROGeom class 120 Detector Definition and Response implement the Readout geometry in the build method returning the physical world of this geometry The world is specified in the same way as for the detector construction a physical volume with no mother The axis system of this world is the same as the one of the world for tracking In this geometry you need to declare the sensitive parts in the same way as in the tracking geometry by setting a non NULL G4VSensitiveDetector pointer in say the relevant G4LogicalVolume objects This sensitive class needs to be there but will not be used You will also need to assign well defined materials to the volumes you place in this geometry but these materials are irrelevant since they will not be seen by the tracking
539. y of the medium This generator is convenient when the Rayleigh attenuation length is not known from measurement but may be calculated from first principles using the above material constants For a medium named Water and no Rayleigh scattering attenutation length specified by the user the program automatically calls the RayleighAttenuationLengthGenera tor which calculates it for 10 degrees Celsius liquid water Boundary Process Reference E Hecht and A Zajac Optics Hecht1974 For the simple case of a perfectly smooth interface between two dielectric materials all the user needs to provide are the refractive indices of the two materials stored in their respective G4MaterialPropertiesTable In all other cases the optical boundary process design relies on the concept of surfaces The information is split into two classes One class in the material category keeps information about the physical properties of the surface itself and a second class in the geometry category holds pointers to the relevant physical and logical volumes involved and has an association to the physical class Surface objects of the second type are stored in a related table and can be retrieved by either specifying the two ordered pairs of physical volumes touching at the surface or by the logical volume entirely surrounded by this surface The former is called a border surface while the latter is referred to as the skin surface This second type of surface is useful in situat
540. y range for the models and provides class utilities The G4HadronicInteraction class provides the Set GetMinEnergy and the Set GetMaxEnergy functions which determine the minimum and maximum energy range for the model An energy range can be set for a specific element a specific material or for general appli cability void SetMinEnergy void SetMinEnergy void SetMinEnergy void SetMaxEnergy void SetMaxEnergy void SetMaxEnergy G4double anEnergy G4Element anElement G4double anEnergy G4Material aMaterial const G4double anEnergy G4double anEnergy G4Element anElement G4double anEnergy G4Material aMaterial const G4double anEnergy Which models are there and what are the defaults In Geant4 any model can be run together with any other model without the need for the implementation of a special interface or batch suite and the ranges of applicability for the different models can be steered at initialisation time This way highly specialised models valid only for one material and particle and applicable only in a very restricted energy range can be used in the same application together with more general code in a coherent fashion Each model has an intrinsic range of applicability and the model chosen for a simulation depends very much on the use case Consequently there are no defaults However physics lists are provided which specify sets of models for various purposes Three types
541. y setLineColour cyan vis modeling trajectories drawByAttribute 0 eIon key setLineColour yellow vis modeling trajectories drawByAttribute 0 mulon key setLineColour magenta Create a drawBy Attribute model named drawBy Attribute 1 vis modeling trajectories create drawByAttribute Select IMag attribute vis modeling trajectories drawByAttribute l setAttribute IMag Configure interval data vis modeling trajectories drawByAttribute 1 addlnterval intervall 0 0 keV 2 5MeV vis modeling trajectories drawByAttribute 1 addlnterval interval2 2 5 MeV 5 MeV vis modeling trajectories drawByAttribute 1 addlnterval interval3 5 MeV 7 5 MeV vis modeling trajectories drawByAttribute 1 addlnterval interval4 7 5 MeV 10 MeV vis modeling trajectories drawByAttribute 1 addlnterval interval5 10 MeV 12 5 MeV vis modeling trajectories drawByAttribute 1 addlnterval interval6 12 5 MeV 10000 MeV vis modeling trajectories drawByAttribute l intervall setLineColourRGBA 0 8 0 0 8 1 vis modeling trajectories drawByAttribute l interval2 setLineColourRGBA 0 23 0 41 1 vis modeling trajectories drawByAttribute l interval3 setLineColourRGBA 0 1 0 1 vis modeling trajectories drawByAttribute l interval4 setLineColourRGBA 1 10 1 vis modeling trajectories drawByAttribute l interval5 setLineColourRGBA 1 0 3 0 1 vis modeling trajectories drawByAttribute l interval6 setLineColourRGBA 10 0 1 246 Visualization 8 7 4 Controlling from Compiled Code
542. yhedra PGON Polyhedra PGON are implemented through G4Polyhedra G4Polyhedra const G4 G4 G4 G4 G4 G4 G4 G4 const const const G4Polyhedra const G4 G4 String amp double double int int doubl doub doub e e e String amp double pName phiStart phiTotal numSide numZPlanes zPlane rInner rOuter pName phiStart 64 Detector Definition and Response G4double G4int G4int const G4double const G4double phiTotal numSide numRZ r ey In the picture phiStart 1 4 Pi phiTotal 5 4 Pi numSide 3 nunZPlanes 7 rInner 0 0 0 0 0 0 0 rOUtex 0 15 15 4 4 10 10 m 105 5 S8 I3 30 32 35 where phiStart Initial Phi starting angle phiTotal Total Phi angle numSide Number of sides numZPlanes Number of z planes numRZ Number of corners in r z space zPlane Position of z planes rInner Tangent distance to inner surface rOuter Tangent distance to outer surface r r coordinate of corners z z coordinate of corners Tube with an elliptical cross section A tube with an elliptical cross section ELTU can be defined as follows G4EllipticalTube const G4String amp pName G4double Dx G4double Dy G4double Dz The equation of the surface in x y is 1 0 dx 2 y dy 2 bale S S CAA AN NN SANA Ss SAAS SSS SEE SSS SS E E e 8 g
543. ynamically in the user application they are automatically registered in internal stores and the system takes care to free the memory allocated at the end of the job 4 2 3 Recipes for Building Elements and Materials Example 4 10 illustrates the different ways to define materials Example 4 10 A program which illustrates the different ways to define materials include G4Isotope hh include G4Element hh include G4Material hh include G4UnitsTable hh Int maza eT G4String name symbol a mass of a mole G4double a z density z mean number of protons G4int iz n iz nb of protons in an isotope n nb of nucleons in an isotope G4int ncomponents natoms G4double abundance fractionmass G4double temperature pressure G4UnitDefinition BuildUnitsTable define Elements a 1 01 g mole G4Element elH new G4Element name Hydrogen symbol H z 1 a a 12 01 g mole G4Element elC new G4Element name Carbon symbol C z 6 a a 14 01 g mole G4Element elN new G4Element name Nitrogen symbol N z 7 a a 16 00 g mole G4Element elO new G4Element name Oxygen symbol 0 z 8 a a 28 09 g mole G4Element elSi new G4Element name Silicon symbol Si z 14 a a 55 85 g mole G4Element elFe new G4Element name Tron symbol Fe z 26 a a 183 84 g mole G4Element elW new G4Element name Tungsten symbol W z 74 a

Geant4 User's Guide for Application Developers

Contents

Download Pdf Manuals

Related Search

Related Contents