Import Geant4 10.3.0.beta source tree

source/run/History

@@ -1,4 +1,4 @@
-$Id: History 94420 2015-11-16 08:18:40Z gcosmo $
+$Id: History 97386 2016-06-02 10:01:40Z gcosmo $
 -------------------------------------------------------------------
 
      =========================================================
@@ -17,6 +17,72 @@ committal in the CVS repository !
      * Reverse chronological order (last date on top), please *
      ----------------------------------------------------------
 
+June 1, 2016 M.Asai      (run-V10-02-12)
+- G4PhysicsListHelper.cc: Fix the default process ordering parameters
+  for G4UnknownDecay that should not have AtRest.
+
+June 1, 2016 L.Desorgher (run-V10-02-11)
+- G4AdjointSimManager correction in the use of run actions to avoid 
+  infinite loop during an adjoint simulation.
+- G4AdjointPrimaryGenerationAction. Remove 3 times spliting of 
+  primary adjoint gamma.
+
+Apr 15rd, 2016 V.Ivanchenko(run-V10-02-10)
+- G4PhysicsListHelper - disable msc PostStep
+
+Feb 23rd, 2016 A.Dotti	   (run-V10-02-09)
+- minor typos correction in output
+
+Feb 22nd, 2016 A.Dotti     (run-V10-02-08)
+- Introduce new UI command: /run/workersProcessCmds to trigger
+  execution of UI commands by workers even without a /run/beamOn
+  C++ API is G4MTRunManager::RequestWorkersProcessCommandsStack()
+- When workers are terminated they execute the UI commands issued
+  after the last /run/beamOn
+
+Feb 18th, 2016 A.Dotti     (run-V10-02-07)
+- Fix compilation in WIN attempt #1
+
+Feb 18th, 2016 A.Dotti	   (run-V10-02-06)
+- Use new class G4MTBarrier to implement synchronization points.
+
+Feb 9th, 2016 A.Dotti      (run-V10-02-05)
+- Fix typo of G4CONDITIONBORADCAST (requires global-V10-02-03)
+- use scoped enum for G4MTRunManager:: WorkerAcitonRequest and
+  add PROCESSUI action
+- add G4MTRunManager::GetNumberActiveThreads() method
+- Introduced skeleton for new functionality to force workers to 
+  execute UI commands w/o beamOn (not functioning yet)
+
+Feb 5th, 2016 P.Gumplinger (run-V10-02-04)
+- fix val-grind memory leakage check tool error in G4RunMessenger
+
+Feb 1st, 2016 A.Dotti (run-V10-02-03)
+- removing automatic handling of multi-user actions 
+   in G4RunManager::SetUserAction(XYZ) (tag run-V10-02-01) since
+  reverse MC needs ability to replace user-actions. 
+  if needed, multiple user-actions must be instantiated and handled by
+  user code 
+
+Jan 29th, 2016 A.Dotti (run-V10-02-02)
+- Renaming all MT related exception to have code matching pattern:
+  Run01[0-9]{2} current maximum number Run0127 
+  (JIRA TASK: DEV-74)
+
+Jan 19th, 2016 A.Dotti (run-V10-02-01)
+- Adding G4MultiRunAction to allow multiple run actions in a single
+  job. 
+- Adding G4MultiPrimaryAction to allow multiple user-primary generation
+  actions in a single job
+- Adding hangling of multiple actions. Requires event-V10-02-01 and
+  tracking-V10-02-00
+
+Jan 27th, 2016 M.Asai (run-V10-02-00)
+- G4PhysicsListHelper: add entry for G4ParallelWorldProcess
+- G4RunManager, G4WorkerRunManager: change process order index of
+  G4ParallelWorldProcess to 9900 to make sure it is registered
+  prior to G4OpBoundaryProcess. 
+
 Nov 14th, 2015 M.Asai (run-V10-01-16)
 - Co-working with particles-V10-01-17. Destructor of G4WorkerRunManagerKernel
   invokes G4ParticleTable::DestroyWorkerG4ParticleTable() to cleanly delete