1) Example compiles, runs (?)
   Compiles and runs.  Macros hadr01.in, antip.in, p_pb.in, testion.in all run.
   vis.mac (when run in control/execute) fails with message
   ***** COMMAND NOT FOUND </testhadr/DrawTracks all> *****

   Command line $G4WORKDIR/bin/Linux-g++/hadr01 QGSP_BERT p_pb.in does not work.
   Error message:  ***** Can not open a macro file <QGSP_BERT>

2) External software documentation (if present)

   Information about PI and AIDA is provided, but the installation process is too complicated.
   I doubt a casual or even half-serious user would want to do it.  I suggest either a
   simplified and clearer installation procedure, or a more rudimentary histogramming system.

   Other analysis file types (hbook, root) are mentioned but there is no documentation
   on how to use them.

3) Classification of classes
   List classes specific to demonstrated features:
   
   Apparently this is a demonstation of physics bahavior and not of a specific 
   Geant4 feature.  It is based on an existing application (IION).
   The physics list factory and cross section printing were demonstrated in Hadr00,
   scoring was demonstrated elsewhere, and so on.  So they are not unique here.
   For these reasons, I believe Hadr01 belongs not in Extended Examples but in the
   Advanced Examples.   
   
   List of classes which can be replaced with common ones:
   a) Histo, HistoMessenger, HistoManager are all used in Hadr00.  Duplication?

   b) Instead of using StackingAction for scoring, use the standard scoring
      code in  source/digits_hits/scorer
   
4) Messenger classes
   List commands defined in this example:
 
   /testhadr/histo/
   1) fileName * set name for the histograms file
   2) fileType * set type (hbook, XML) for the histograms file
   3) setHisto * Set bining of the histo number ih :

   /testhadr/  
   2) TargetMat * Select Material for the target
   3) WorldMat * Select Material for world
   4) TargetRadius * Set radius of the target
   5) TargetLength * Set length of the target
   6) NumberOfBinsE * Set number of bins for Energy
   7) NumberDivZ * Set number of slices
   8) MaxEdep * Set max energy in histogram
   9) Update * Update geometry.
  10) DefaultBeamPosition * show inelastic and elastic cross sections
  11) Verbose * Set verbose for 
  12) CutGamma * Set gamma cut.
  13) CutEl * Set electron cut.
  14) CutPos * Set positron cut.
  15) CutProt * Set proton cut.
  16) CutsAll * Set cut for all.
  17) Physics * Add modula physics list.
  18) ListPhysics * Available Physics Lists
  19) PrintModulo * Print events modulo n
  20) DebugEvent * D event to debug
  21) KillAllSecondaries *   Choice : true false
  22) Kill * Kill secondary particles of defined type

   List commands which do not work as expected:
   a) not at all
     These commands are mentioned in the README, but not in the command list:
     /testhadr/HistoName   name
     /testhadr/HistoType   type
     /testhadr/HistoOption "uncompress"
     /testhadr/HistoPrint  i
     /testhadr/DrawTracks  charged
     /testhadr/DrawTracks  charged+n
     /testhadr/DrawTracks  neutral
     /testhadr/DrawTracks  all

   b) in some G4 phase(s)
     All other commands OK.

5) Code review:
   Report on obsolete code (if present):
   Code is OK.
   
   Report on inefficient code (if present):
   Code is OK.
   
   Your recommendations to example owner:
   a) Use standard scoring code.
   b) Provide a build option, or maybe a macro, which contains no analysis,
       histogramming, etc.
   
6) Documentation review:
   Your recommendations to example owner:

   README
   a) Add more detailed introduction/purpose section.  Purpose(s) should be
      more clearly stated.  For example, what role does scoring play in the 
      example and how will aspects of beam-target interaction change under
      different target/beam situations.
   b) Add section on Setting Up and Running the Example which would include
      build instructions, necessary files, environment variables, execution
      arguments, etc.  Currently only a little of this information is listed
      and it is spread out in many places in the document.
   c) Each .in and .mac file must be described.
   d) Visualization section is not clear.  Explicit instructions for setting
      up visualization and environment variables should be included.
   e) Explicit details should be included on setting up histogramming.
   f) Add more instruction on how to use histograms, as well as information
      about what should be expected in a given histogram.
   g) English/spelling should be improved.
   
7) Comment on the adequacy in its physics domain
   (skip this item if you are not an expert in physics demonstrated 
   in the example):

   The physics domain is not well defined.  This could be remedied in the
   README.    
   
8) "Users questions to be addressed in examples"   
   List questions which can be naturally addressed in this example:

   None.