GGSUserActionInitialization.cpp

/*
 * GGSUserActionInitialization.cpp
 *
 *  Created on: 22 Oct 2020
 *      Author: Nicola Mori
 */

#include "montecarlo/mccore/GGSUserActionInitialization.h"
#include "montecarlo/generators/GGSGunGeneratorAction.h"
#include "montecarlo/mccore/GGSMultiUserAction.h"
#include "montecarlo/mccore/GGSRunManager.h"
#include "utils/GGSFactory.h"
#include "utils/GGSSmartLog.h"

#include "G4Exception.hh"
#include "G4UIcmdWithAString.hh"
#include "G4UIcommand.hh"
#include "G4UImanager.hh"

#include <memory>

// Thread-local global variables
namespace {
G4ThreadLocal GGSMultiUserAction *muAction = nullptr;
G4ThreadLocal GGSMultiUserAction *muActionForMaster = nullptr;
} // namespace

void GGSUserActionInitialization::BuildForMaster() const {
  const std::string routineName("GGSUserActionInitialization::BuildForMaster");
  GGSCOUT(DEBUG) << "Setting the run actions for the master thread." << GGSENDL;

  /* ***** Build user action creation commands for master thread. ***** */
  // User action build commands are created for worker threads in Build(). During the creation process they are
  // also automatically registered in the UI manager for master thread by G4UImanager::AddWorkerCommand that is called
  // in G4UImanager::AddNewCommand. In this way the commands are recognized during the parsing of the data card by the
  // master thread and no error is generated. However, build commands create user actions that might create additional
  // commands in their constructors: these would not be registered for master thread, since a build command added to the
  // master UI manager from a worker thread is flagged as workerThreadOnly, so it is recognized but not executed by the
  // master thread; a subsequent action-created command would therefore be not registered in master UI and an error
  // would occur. The only solution seems to register all the build commands directly in the master thread, so that they
  // will be executed by master, all the user action configuration commands will be created and no error will occur
  // while parsing the data card. The master actions should not be executed during the simulation, so SetUserAction is
  // not called for the master malt-action.
  muActionForMaster = new GGSMultiUserAction; // Thread-local
}

void GGSUserActionInitialization::Build() const {
  const std::string routineName("GGSUserActionInitialization::Build");

  if (G4Threading::IsMultithreadedApplication()) {
    GGSCOUT(DEBUG) << "Setting the user actions for worker thread " << G4Threading::G4GetThreadId() << GGSENDL;
  } else {
    GGSCOUT(DEBUG) << "Setting the user actions" << GGSENDL;
  }
  delete muAction;
  muAction = new GGSMultiUserAction; // Thread-local
  SetUserAction((G4UserSteppingAction *)muAction);
  SetUserAction((G4UserTrackingAction *)muAction);
  SetUserAction((G4UserEventAction *)muAction);
  SetUserAction((G4UserRunAction *)muAction);
  SetUserAction((G4UserStackingAction *)muAction);

  // Add a dummy event generator for the MT dry run. Will be replaced by a real generator built with a datacard command.
  class DummyGenAction : public GGSGeneratorAction {
  public:
    void GeneratePrimaries(G4Event *){};
  };
  SetUserAction(new DummyGenAction);
}