search

brittonsmith / cloudy_cooling_tools

Create an N-dimensional grid of models with the Cloudy photoionization code.
MIT License
5 stars 4 forks source link

reproducing cooling tables with Cloudy 17.02 #2

Closed BenWibking closed 2 years ago

BenWibking commented 3 years ago

Hi,

I am trying to reproduce the HM2012 optically-thin cooling tables with the latest version of Cloudy (17.02). However, I get an error message:

cloudy_cooling_tools git:(main) ✗ ./CIAOLoop examples/grackle/hm_2012.par 
Run started at Thu May 13 14:22:42 2021
Thu May 13 14:22:42 2021 - 1/725 started.
Cloudy crashed for T = 1.000e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.122e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.259e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.413e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.585e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.778e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.995e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 2.239e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 2.512e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 2.818e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 3.162e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 3.548e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 3.981e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 4.467e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 5.012e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 5.623e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 6.310e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 7.079e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 7.943e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 8.913e+01 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.000e+02 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.122e+02 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.259e+02 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.413e+02 of run 1.  If this continues, think about exiting.
Cloudy crashed for T = 1.585e+02 of run 1.  If this continues, think about exiting.

Presumably, something changed with the newer version of Cloudy. However, I can't debug what is happening with this output. Is there a way to see what the output from Cloudy itself is before it crashes?

Thanks, Ben

brittonsmith commented 3 years ago

Hi Ben,

If you set the following parameter in your input file, the code will exit when it detects that Cloudy has crashed. exitOnCrash = 1

After it crashes, you should find a file ending in .cloudyOut.temp, which will have the output from Cloudy from the last run.

BenWibking commented 2 years ago

That enabled me to figure it out. Thanks.