Reducing verbosity in output messages for cross sections and physics list

Physics Processes, Models and Cross Sections
1

Dear all,

I’m trying to decrease the level of verbosity of my program, related to the the following output messages about the physics list used by my model (G4HadronElasticPhysicsHP, G4HadronPhysicsQGSP_BERT_HP, G4EmStandardPhysics, G4EmExtraPhysics, G4DecayPhysics, G4StoppingPhysics, G4IonPhysics, G4RadioactiveDecayPhysics):

Schermata da 2021-12-12 17-13-42
Schermata da 2021-12-12 17-13-421665×733 125 KB

I tried to decrease the level of verbosity by using the solution suggested in Reducing Physics Verbosity and by setting the verbosity level to 0:


int verb = 0;
  SetVerboseLevel(verb);

  // EM Physics
  RegisterPhysics( new G4EmStandardPhysics(verb) );

  // Synchroton Radiation & Gamma Nuclear Physics
  RegisterPhysics( new G4EmExtraPhysics(verb) );

  // Decays
  RegisterPhysics( new G4DecayPhysics(verb) );

  // Hadron Elastic scattering
  RegisterPhysics( new G4HadronElasticPhysicsHP(verb) );

  // Hadron Physics
  RegisterPhysics( new G4HadronPhysicsQGSP_BERT_HP(verb));

  // Stopping Physics
  RegisterPhysics( new G4StoppingPhysics(verb) );

  // Ion Physics
  RegisterPhysics( new G4IonPhysics(verb));

  // Radioactive decay
  RegisterPhysics( new G4RadioactiveDecayPhysics(verb) );

My program is still printing the output messages as above. Any suggestion, please?

Christian

2
1 Like
3

Thank you very much! I used your function and it works well. The problem is that I noticed that the time spent by the simulation is the same in both cases, enabled or disabled stdout. Indeed, I want to reduce the time of the simulation lost by the verbosity.

Christian

4

In that case, you should compile Geant4 with -DGEANT4_BUILD_VERBOSE_CODE=OFF as suggested in the other Forum post (maybe also -DGEANT4_BUILD_STORE_TRAJECTORY if that’s enabled for you). Although for the initialization part, the options above will not change much. If you want to turn off most output from that, you can try adding this to your code (right after you create your run manager):

  G4UImanager* UI = G4UImanager::GetUIpointer();

  UI->ApplyCommand(G4String("/process/verbose       0"));
  UI->ApplyCommand(G4String("/process/em/verbose    0"));
  UI->ApplyCommand(G4String("/process/had/verbose   0"));
  UI->ApplyCommand(G4String("/process/eLoss/verbose 0"));

  UI->ApplyCommand(G4String("/control/verbose  0"));
  UI->ApplyCommand(G4String("/run/verbose      0"));
  UI->ApplyCommand(G4String("/event/verbose    0"));
  UI->ApplyCommand(G4String("/hits/verbose     0"));
  UI->ApplyCommand(G4String("/tracking/verbose 0"));
  UI->ApplyCommand(G4String("/stepping/verbose 0"));
1 Like
5

Ok thanks for your suggestion! I tried all the solutions provided, but Geant4 still works at the same speed with or without verbosity. At this point, I think it is a problem that should be fixed in the next versions of the code.

Christian

6

Hello,

In recent versions of Geant4 it is needed to set to zero “em” and “had” verbosity.

VI

7

In case it helps, the verbosity level can be passed as a parameter to the PhyscisList constructor. If you don’t want any output from the physics list just instantiate it like this example:

int verboseLevel = 0; // set to zero for non-verbosity
G4VModularPhysicsList* phys = new QGSP_BERT_HP(verboseLevel);