| Summary: | Not all code respects G4UIsession | ||
|---|---|---|---|
| Product: | Geant4 | Reporter: | Simon Spannagel <simon.spannagel> |
| Component: | intercoms | Assignee: | Vladimir.Ivantchenko |
| Status: | RESOLVED FIXED | ||
| Severity: | minor | ||
| Priority: | P4 | ||
| Version: | 10.7 | ||
| Hardware: | All | ||
| OS: | All | ||
|
Description
Simon Spannagel
2021-03-23 08:18:22 CET
Thanks for your report. Concerning about the Geant4 banner, it is shown to G4cout at the construction of the G4RunManagerKernel class. If you do need to write this banner to alternative destination, you need to instantiate your UIsession and CoutDestination prior to the construction of G4RunManager. You do not need to create your own RunManager. About the printout of "Pre-compound/De-excitation Physics Parameters", it is weird. As far as I see the source code of this printout, it is sent to G4cout. Thus, there is no reason it goes to the original window. Let me forward your report to the author of this class. Kind regards, Makoto Dear Makoto,
you are of course right concerning the Geant4 banner - I just don't catch it because the base constructor is called before my own RunManager's constructor. Thanks for the clarification.
As for the other part, I discovered that with Geant4 v10.6.p02 I also see this message from the G4RadioactiveDecay class, but with 10.7.p01 this message is gone. Checking the diff for the relevant files, I see several changes similar to:
source/processes/hadronic/models/radioactive_decay/src/G4RadioactiveDecay.cc
#ifdef G4VERBOSE
- if(G4Threading::IsMasterThread()) { StreamInfo(G4cout, "\n"); }
+ if(G4HadronicParameters::Instance()->GetVerboseLevel() > 0 &&
+ G4Threading::IsMasterThread()) { StreamInfo(G4cout, "\n"); }
#endif
So it seems like it has been fixed there by inheriting the verbosity from the G4HandronicParameters. Probably the same should be done here?
Best regards and many thanks,
Simon
Hello, this is likely the same problem as #2350 (https://bugzilla-geant4.kek.jp/show_bug.cgi?id=2350 ). The problem is fixed now and the fix will be publicly available with the new patch to 10.7 and in the new public release. VI |