Increase binding scope

Author: HaarigerHarald

.gitignore

@@ -13,3 +13,8 @@ examples/**/*.macro
 examples/**/*.root
 examples/**/*.csv
 examples/**/*.xml
+
+tests/*.macro
+tests/*.root
+tests/*.csv
+tests/*.xml

CMakeLists.txt

@@ -15,11 +15,11 @@ elseif(CMAKE_COMPILER_IS_GNUCC OR CMAKE_COMPILER_IS_GNUCXX)
   set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -Wall -Wno-long-long")
 endif()
 
-find_package(Geant4 10.0 REQUIRED)
+find_package(Geant4 10.7 REQUIRED)
 find_package(Geant4 OPTIONAL_COMPONENTS gdml ui_tcsh motif vis_raytracer_x11 vis_opengl_x11 vis_opengl_win32 qt)
 include_directories(${Geant4_INCLUDE_DIRS})
 
-set(PYBIND11_PYTHON_VERSION 3)
+set(PYBIND11_PYTHON_VERSION 3.5)
 
 if(EXISTS ${CMAKE_SOURCE_DIR}/pybind11/CMakeLists.txt)
   add_subdirectory(pybind11)

README.md

@@ -60,7 +60,7 @@ ui.SessionStart()
 
 **Full examples**
 
-Check out the [examples](examples) directory, which contains the Geant4 basic examples B1, B2 and B3 ported to Python. However, writing simulations in Python should be pretty straight forward as the API is almost identical to the C++ one. One notable exception are template classes, which have been renamed such that their type replaces the `T` (i.e. `G4TScoreNtupleWriter<G4RootAnalysisManager>` becomes `G4RootScoreNtupleWriter`).
+Check out the [examples](examples) directory, which contains the Geant4 basic examples ported to Python. However, writing simulations in Python should be pretty straight forward as the API is almost identical to the C++ one. One notable exception are template classes, which have been renamed such that their type replaces the `T` (i.e. `G4TScoreNtupleWriter<G4RootAnalysisManager>` becomes `G4RootScoreNtupleWriter`).
 
 ## Bugs?
 

examples/B1/README

@@ -42,12 +42,12 @@
                /process/(in)activate processName
    allows to activate/inactivate the processes one by one.
 
- 3- ACTION INITALIZATION
+ 3- ACTION INITIALIZATION
 
    A newly introduced class, B1ActionInitialization, instantiates and registers 
    to Geant4 kernel all user action classes.
 
-   While in sequential mode the action classes are instatiated just once,
+   While in sequential mode the action classes are instantiated just once,
    via invoking the method:
       B1ActionInitialization::Build() 
    in multi-threading mode the same method is invoked for each thread worker
@@ -75,7 +75,7 @@
    The energy deposited is collected step by step for a selected volume
    in B1SteppingAction and accumulated event by event in B1EventAction.
 
-   At end of event, the value acummulated in B1EventAction is added in B1RunAction
+   At end of event, the value accumulated in B1EventAction is added in B1RunAction
    and summed over the whole run (see B1EventAction::EndOfevent()).
 
    Total dose deposited is computed at B1RunAction::EndOfRunAction(), 
@@ -96,11 +96,11 @@
 
  The following paragraphs are common to all basic examples
 
- A- VISUALISATION
+ A- VISUALIZATION
 
    The visualization manager is set via the G4VisExecutive class
    in the main() function in exampleB1.cc.    
-   The initialisation of the drawing is done via a set of /vis/ commands
+   The initialization of the drawing is done via a set of /vis/ commands
    in the macro vis.mac. This macro is automatically read from
    the main function when the example is used in interactive running mode.
 

examples/B1/exampleB1.in

@@ -0,0 +1,16 @@
+# Macro file for example B1 test
+
+/run/initialize
+
+# gamma 6 MeV 
+/gun/particle gamma
+/gun/energy 6 MeV
+#
+/run/printProgress 100
+/run/beamOn 1000
+#
+# proton 210 MeV 
+/gun/particle proton
+/gun/energy 210 MeV
+#
+/run/beamOn 1000