Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HAD_RDM_011 Warnings (Geant4.10.0.p02) #32

Open
AndrewEdmonds11 opened this issue Sep 15, 2014 · 6 comments
Open

HAD_RDM_011 Warnings (Geant4.10.0.p02) #32

AndrewEdmonds11 opened this issue Sep 15, 2014 · 6 comments

Comments

@AndrewEdmonds11
Copy link

I get a lot of warnings of the following:

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : HAD_RDM_011
      issued by : G4RadioactiveDecay::GetMeanFreePath()
Ion has negative lifetime -1001 but is not stable.  Setting mean free path to DBL_MAX

*** This is just a warning message. ***

which is fine but I think it might be slowing things down for me (especially on the batch farm).

This is a known issue (hypernews link) with the only fix being in Geant4.10.01 beta.

There is another suggestion in that thread (reply 4.1.2) but it doesn't work since the HAD_RDM_011 warning gets issued by the GetIonLifetime() function.

Before I try installing Geant4.10.01 beta, does anyone know of a way to stop Geant4 printing exceptions? I've got all the verbosities set to 0 but that hasn't helped...

@thnam
Copy link

thnam commented Sep 15, 2014

I could not suppress that message either. It is annoying because the log file would be very huge, so I just delete the log files after letting g4sim runs a few minutes. Once the log files are removed, they will not be recreated in that batch job.

rm path_to_output/*.bosslog

I guess that is okay since what we might want to see is the error log, and saved scripts.

@wuchen1106
Copy link

I used to modify geant source code.
It's on ./processes/hadronic/models/radioactive_decay/src/G4RadioactiveDecay.cc line 627 for geant4.10.00.p02.

@quiksilv
Copy link

quiksilv commented Oct 3, 2018

The fix requires an updated Geant4 module for G4RadioactiveDecay, which is the radioactive decay database (RDM ~> 4.1). Either replace the module or upgrade Geant to at least 4.10.01.

Reference: http://hypernews.slac.stanford.edu/HyperNews/geant4/get/hadronprocess/1403/3.html

@AndrewEdmonds11
Copy link
Author

Wow! Thanks for following up on this! Do people have a preference between updating the database or updating geant? I wouldn't mind updating geant but I think all of our simulations should use one version.

@quiksilv
Copy link

quiksilv commented Oct 3, 2018

I personally ran 4.10.03.p02 on my own Mac and I think the version of Geant4 that John had installed on mu2e.bu.edu is also the same version.

The only annoying thing probably is that cmake3 is required for installing 4.10.03.

@jrquirk
Copy link

jrquirk commented Oct 5, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants