Example: g3tog4/clGeometry 1) Example compiles, runs (?) yes 2) External software documentation (if present) Building rztog4 executable in g3tog4 requires cernlib; it may be worth to be mentioned also in the README of this example. 3) Classification of classes List classes specific to demonstrated features: G3toG4DetectorConstruction List of classes which can be replaced with common ones: G3toG4EventAction G3toG4EventActionMessenger G3toG4PhysicsList G3toG4PrimaryGeneratorAction G3toG4RunAction The PrimaryGeneratorAction provide GetRandomDirection() which can be of general use and so integrated in ExG4PrimaryGeneratorAction01. 4) Messenger classes List commands defined in this example: /event/draw - not needed anymore List commands which do not work as expected: a) not at all - b) in some G4 phase(s) none 5) Code review: Report on obsolete code (if present): - In RunAction: UI->ApplyCommand("/vis~/clear/view"); UI->ApplyCommand("/vis~/draw/current"); these commands do not exist anymore - The command /event/draw can be replaced with vis commands Report on inefficient code (if present): - There is no need for fPV, fLV data members in G3toG4DetectorConstruction class. - Both examples cltog4 and clGeometry differ only in main (clGeometry calls vis.mac); we can keep just one of them and provide two init macros (init.mac and init_vis.mac as in basic examples) Your recommendations to example owner: - 6) Documentation review: Your recommendations to example owner: - Add info about rztog4 executable and a link to g3tog4/README in source. 7) Comment on the adequacy in its physics domain (skip this item if you are not an expert in physics demonstrated in the example): not related to physics 8) "Users questions to be addressed in examples" List questions which can be naturally addressed in this example: This example has a special purpose, it is not suitable to show other features than use of g3tog4 utility.