Example: analysis/AnaEx02 1) Example compiles, runs (?) yes 2) External software documentation (if present) yes Root can be installed without ROOTSYS environment variable set; it is better to use root-config in GNUmakefile (see the diff below) 3) Classification of classes List classes specific to demonstrated features: (same as in AnaEx01) DetectorConstruction DetectorMessenger EventAction HistoManager RunAction SteppingAction List of classes which can be replaced with common ones: (same as in AnaEx01) ExG4HbookAnalysisManager g4hbook_defs g4hbook PhysicsList PrimaryGeneratorAction 4) Messenger classes List commands defined in this example: (same as in AnaEx01) /N03/det/setAbsMat /N03/det/setGapMat /N03/det/setAbsThick /N03/det/setGapThick /N03/det/setSizeYZ /N03/det/setNbOfLayers /N03/det/update List commands which do not work as expected: (same as in AnaEx01) a) not at all - b) in some G4 phase(s) - By default the UI sesion opens in Idle> phase, so one cannot test commands in PreInit> without modifying main - when /N03/det/setAbs/GapMat fails (material not found) user is not notified about failure: /N03/det/setAbsMat Al 5) Code review: Report on obsolete code (if present): - Report on inefficient code (if present): - Your recommendations to example owner: (same as in AnaEx01) - Use classes from common as suggested in the item 3) - Share classes with AnaEx01 6) Documentation review: Your recommendations to example owner: (same as in AnaEx01) - The same scenario is now used in basic/B4 example; it should be good to comment in the documentation what is different here: - flexible geometry - only one scoring way - histo manager 7) Comment on the adequacy in its physics domain (skip this item if you are not an expert in physics demonstrated in the example): - 8) "Users questions to be addressed in examples" List questions which can be naturally addressed in this example: (same as in AnaEx01) General: (2) How to get the runID and eventID? (22) How to collect the energy of all shower particles that follow a gamma entering a detector, separately for each entering gamma? (maybe) DetectorConstruction: (1) How to modify the geometry during a run? Suggested change of GNUmakefile: Index: GNUmakefile =================================================================== 18a19,21 > CPPFLAGS += -I$(shell root-config --incdir) > EXTRALIBS = $(shell root-config --glibs) -lGeomPainter -lGeom > 29,37d31 < ifdef ROOTSYS < CPPFLAGS += -I$(shell $(ROOTSYS)/bin/root-config --incdir) < CPPFLAGS += $(shell $(ROOTSYS)/bin/root-config --cflags) < LDLIBS += $(shell $(ROOTSYS)/bin/root-config --libs) < < ifeq ($(G4SYSTEM),Linux-g++) < LDLIBS += -Wl,-rpath,$(shell $(ROOTSYS)/bin/root-config --libdir) < endif < endif