Describe the bug
Resampled cooling causes this error: Assertion failed: (x > 0 && "log divergent for x <= 0"), function fastlg, file FastMath.hpp, line 37.. This is not necessary a bug in the cooling routine, but what could've caused this?
To Reproduce
Steps to reproduce the behavior:
- Compile this problem 'test_sne' (require Aditi's branch with some bug fix)
- Run this problem 'test_sne'
- See error
Coarse STEP 1 at t = 0 (0%) starts ...
...[level 0] estimated hydro timestep: 1.565446e+12
...[level 0] hydro timestep limited at cell [31, 31, 255] with signal speed = 9.036961e+06
...[level 0] cell density = 1.642355e-29, |v| = 0.000000e+00, cs = 9.036961e+06
...[level 0] timestep limited by HYDRO
...coarse timestep set by level 0
[Level 0 step 1] ADVANCE with time = 0.0000000000e+00 dt = 1.5654460365e+12
cooling substeps (per cell): avg 1.03125, max 2
cooling substeps (per cell): avg 1, max 1
The total number of SN gone off= 4
The total number of SN gone off= 4
[Level 0 step 1] Advanced 262144 cells
Coarse STEP 2 at t = 1.565446036e+12 (0.01654455756%) starts ...
...[level 0] estimated hydro timestep: 2.296661e+11
...[level 0] hydro timestep limited at cell [0, 0, 116] with signal speed = 6.159757e+07
...[level 0] cell density = 6.983390e-25, |v| = 1.623054e+03, cs = 6.159595e+07
...[level 0] timestep limited by HYDRO
...coarse timestep set by level 0
[Level 0 step 2] ADVANCE with time = 1.5654460365e+12 dt = 2.2966611094e+11
cooling substeps (per cell): avg 1, max 1
Assertion failed: (x > 0 && "log divergent for x <= 0"), function fastlg, file FastMath.hpp, line 37.
SIGABRT
See Backtrace.0 file for details
--------------------------------------------------------------------------
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
Proc: [[25045,0],0]
Errorcode: 6
Additional context
Add any other context about the problem here.
Describe the bug
Resampled cooling causes this error:
Assertion failed: (x > 0 && "log divergent for x <= 0"), function fastlg, file FastMath.hpp, line 37.. This is not necessary a bug in the cooling routine, but what could've caused this?To Reproduce
Steps to reproduce the behavior:
Additional context
Add any other context about the problem here.