Import Geant4 9.6.0 source tree

examples/basic/B3/README

@@ -43,6 +43,10 @@ $Id$
      the G4LEDATA envirnoment variable
    - radioactive decay hadronic processes which path is defined via 
      the G4RADIOACTIVEDATA envirnoment variable.
+   
+   See more on installation of the datasets in Geant4 Installation Guide,
+   Chapter 3.3: Note On Geant4 Datasets:
+   http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/InstallationGuide/html/ch03s03.html
  	 
  3- PRIMARY GENERATOR
   
@@ -69,9 +73,9 @@ $Id$
    		
  5- STACKING ACTION
  
-   Beta decay of Fluor generates a neutrino. One wishes do not track this
-   neutrino. Therefore one kills it immediately, before created particles
-   will put in a stack.
+   Beta decay of Fluor generates a neutrino. One wishes not to track this
+   neutrino; therefore one kills it immediately, before created particles
+   are put in a stack.
    The function B3StackingAction::ClassifyNewTrack() is invoked by G4 kernel
    each time a new particle is created.       
 
@@ -85,18 +89,25 @@ $Id$
    in the macro vis.mac. This macro is automatically read from
    the main function when the example is used in interactive running mode.
 
-   By default, vis.mac opens an OpenGL viewer.
-   The user can switch to other graphics systems by commenting out this line
+   By default, vis.mac opens an OpenGL viewer (/vis/open OGL).
+   The user can change the initial viewer by commenting out this line
    and instead uncommenting one of the other /vis/open statements, such as
    HepRepFile or DAWNFILE (which produce files that can be viewed with the
-   HepRApp and DAWN viewers, respectively).
+   HepRApp and DAWN viewers, respectively).  Note that one can always
+   open new viewers at any time from the command line.  For example, if
+   you already have a view in, say, an OpenGL window with a name
+   "viewer-0", then
+      /vis/open DAWNFILE
+   then to get the same view
+      /vis/viewer/copyView viewer-0
+   or to get the same view *plus* scene-modifications
+      /vis/viewer/set/all viewer-0
+   then to see the result
+      /vis/viewer/flush
 
    The DAWNFILE, HepRepFile drivers are always available
-   (since they require no external libraries), but the OGL driver requires:
-     1- the visualisation & interfaces categories have been compiled
-        with the environment variable G4VIS_BUILD_OPENGLX_DRIVER.
-     2- exampleB3.cc has been compiled with G4VIS_USE_OPENGLX.
-   (This is best done through Configure or CMake.)
+   (since they require no external libraries), but the OGL driver requires
+   that the Geant4 libraries have been built with the OpenGL option.
 
    For more information on visualization, including information on how to
    install and run DAWN, OpenGL and HepRApp, see the visualization tutorials,
@@ -110,22 +121,14 @@ $Id$
  B- USER INTERFACES
  
    The user command interface is set via the G4UIExecutive class
-   in the the main() function in exampleB3.cc 
+   in the main() function in exampleB3.cc 
    The selection of the user command interface is then done automatically 
-   according to the Geant4 configuration. The default command interface, 
-   called G4UIterminal, is done via a standard G4cin/G4cout.
-   On Linux and Sun-cc one can use a smarter command interface G4UItcsh. 
-   It is enough to set the environment variable G4UI_USE_TCSH before compiling 
-   exampleB3.cc
- 
+   according to the Geant4 configuration or it can be done explicitly via 
+   the third argument of the G4UIExecutive constructor (see exampleB4a.cc). 
  
 C- HOW TO RUN
 
-    - compile and link to generate an executable
-        % cd B3
-        % make
- 
-    - execute exampleB3 in the 'interactive mode' with visualization
+    - Execute exampleB3 in the 'interactive mode' with visualization
         % exampleB3
       and type in the commands from run1.mac line by line:  
         Idle> /control/verbose 2
@@ -138,7 +141,7 @@ C- HOW TO RUN
         ....
         Idle> exit
 
-    - execute exampleB3 in the 'batch' mode from macro files 
+    - Execute exampleB3 in the 'batch' mode from macro files 
      (without visualization)
         % exampleB3 run2.mac
         % exampleB3 exampleB3.in > exampleB3.out