Initialize count for iseed_ca <= 0 in update_ca.F90#84
Initialize count for iseed_ca <= 0 in update_ca.F90#84NickSzapiro-NOAA wants to merge 2 commits into
Conversation
|
While we're here, the 7*mytile vs mytile is curious |
|
@lisa-bengtsson can you take a look at these issues? |
|
Hi Nick, I would like to keep the distinction between iseed_ca <= 0, and the case when it has an integer larger than 0. I don't recall why the count line is commented out - and I discussed it with Phil who did some updates to the initial seed generation to better match SPPT a few years ago, but we think you should just have to uncomment this line in update_ca.F90: !call system_clock(count, count_rate, count_max) In two places (for CA global and CA sgs). The curious 7 is there simply to distinguish the seed between the sub-grid-scale CA, and the global CA. Could you test if your warning goes away if you uncomment the call to system clock? Thanks, |
|
Sure. As you wish :) Thank you both for being so responsive By calling system_clock first, the warning goes away. Noting as well that cpld_control_gefs and control_p8 RTs are bit-for-bit too (as expected from iseed_ca>0) |
In compiling UFS (ufs-community/ufs-weather-model#2703), there is a warning that:
It seems that initializing count (if iseed_ca <= 0) via system_clock was removed in #47 .
I'm not familiar with the internals/intent here. One option is to remove the separate conditions (as here). Another is to initialize count more appropriately.
fyi, any change here is expected to be bit-for-bit in UFS regression tests as iseed_ca>0.