1) Example compiles, runs (?)

   example compiles and runs, macros run.  However, vis.mac only runs from
   /control/execute 

2) External software documentation (if present)

   AIDA information is adequate, but there is none for any of the other
   analysis options mentioned

3) Classification of classes
   List classes specific to demonstrated features:
   
   G4PhysListFactory
   G4HadronicProcessStore   
   Reference physics lists
   
   List of classes which can be replaced with common ones:
   
   None.
   
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/ 
   1) TargetMat * Select Material for the target
   2) WorldMat * Select Material for world
   3) TargetRadius * Set radius of the target
   4) TargetLength * Set length of the target
   5) nBinsE * Set number of bins for energy
   6) nBinsP * Set number of bins for momentum
   7) update * Update geometry.
   8) particle * Set particle name
   9) targetElm * Set element name
  10) minEnergy * Set min kinetic energy
  11) maxEnergy * Set max kinetic energy
  12) minMomentum * Set min momentum
  13) maxMomentum * Set max momentum
  14) verbose * Set verbose for 
  15) PrintModulo * Print events modulo n
  16) DebugEvent * D event to debug
   
   List commands which do not work as expected:
   a) not at all
     /testhadr/DrawTracks  charged
     /testhadr/DrawTracks  neutral
     /testhadr/DrawTracks  all
   
     The above commands are described in the README but do not work
     nor are they present in the command list

     /testhadr/histo/fileName
     /testhadr/histo/fileType
     /testhadr/histo/setHisto

     The above commands work, but they differ from those described in 
     README, which don't work.

     README mentions
     /testhadr/HistoName   name
     /testhadr/HistoType   type
     /testhadr/HistoOption "uncompress"

     but these don't appear in the command listing.

   b) in some G4 phase(s)
     OK.
   
5) Code review:
   Report on obsolete code (if present):

   Code is up-to-date
   
   Report on inefficient code (if present):
   
   Efficiency seems OK
   
   Your recommendations to example owner:
   
    a) Code is mostly clear and simple.
    b) Code like 
          G4double worldR  = fRadius + cm;
       is confusing and makes user think there is an error.
    c) root files are generated in the example but they cannot be
       read by root.

6) Documentation review:
   Your recommendations to example owner:
   
   README
   a) Add introduction/purpose section.  Purpose should be more clearly stated.
   b) Add section on Setting Up and Running the Example which would include
      build instructions, necessary files, environment variables, execution
      arguments, etc.
   c) Each .mac file must be described.
   d) Visualization section is not clear.  Explicit instructions for setting
      up visualization should be included.
   e) Explicit details should be included on setting up histogramming.
   f) README states that this example demonstrates a usage of G4PhysListFactory
      but does not indicate the code which does this.  Should mention
      code block in main and discuss a bit what the factory does.
   g) Cross section feature works, but need to mention that run/beamOn 1
      should be executed first.
   h) Physics list default is listed in README as QGSP_BERT, but FTFP_BERT is
      actually used.
   i) 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):

   a) Cross section listing feature is especially useful.
   b) G4PhysListFactory demonstration is useful, but not well explained
      (see item 6)
   
8) "Users questions to be addressed in examples"   
   List questions which can be naturally addressed in this example:
   
   None.