Closed ndkeen closed 4 years ago
OK, this looks like one of the issues I was tracking in https://github.com/E3SM-Project/E3SM/issues/3061
However, above is a our default F case.
Note that with threading, which is how it might run by default, I get a different error (earlier) with DEBUG=TRUE that is still not solved (https://github.com/E3SM-Project/E3SM/issues/2131)
F-cases using ne4 and ne11 do not fail in the same way.
Interesting that the threaded DEBUG case does not stop there. I added an init to zero as a test here:
cam/src/physics/cam/clubb_intr.F90
if (is_first_step()) then
...
call pbuf_set_field(pbuf2d, radf_idx, 0.0_r8)
+ call pbuf_set_field(pbuf2d, qrl_idx, 0.0_r8) ! ndk
And the problem goes away. If this is the proper place to init, I see other arrays that may need to be set here as well.
Discussing this with @singhbalwinder on slack.
@vlarson suggested we "set qrl to zero after it is added to pbuf". If that's not what I did above, then I may need help doing this. If it is, I can make a PR.
@vlarson can someone be assigned to work on this?
@vlarson Who should work on this?
@singhbalwinder, Noel and I talked, and it seems OK to me to initialize qrl to zero in clubb_intr, as suggested by Noel. What do you think? How do we make this happen?
With master of August 14th, I get an error with F-case in DEBUG. Using default compiler and same error with intel19. It seems to happen in ATM init.