-
Notifications
You must be signed in to change notification settings - Fork 7
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
edmf random seed not too random? #614
Comments
It all looks very ad hoc to me. Some attempt to pre-randomize a seed? |
This section of code was copied from ras.F90. I'm not sure what motivated lines 351-356. Is THE_SEED=0 disallowed? I think the current code works, in the sense of producing randomness and satisfying regression tests, but I will double check that. |
@narnold1 There are compilers where setting a seed that's not too random causes issues (see https://forums.developer.nvidia.com/t/random-number-seed-oddities/133398 by some "Matt Thompson"), so I always discourage that once I realized that. I mean, setting the seed based on input temperatures isn't bad, it's just like the seed construction was a bit oddly coded. 😄 |
This issue is addressed by PR #783 |
@narnold1 A question. While talking with NVIDIA about their GPU efforts with edmf we looked at this code:
GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSturbulence_GridComp/edmf.F90
Lines 347 to 356 in b3b07ba
and then
the_seed
is passed toPoisson
:GEOSgcm_GridComp/GEOSagcm_GridComp/GEOSphysics_GridComp/GEOSturbulence_GridComp/edmf.F90
Line 362 in b3b07ba
The thing is...I'm pretty sure
the_seed(1)
equalsthe_seed(2)
unless they are 0. We were thinking maybe it should be:at the beginning?
Just wondering.
Cc: @tclune as he probably knows more about algorithmically making random numbers than I do
The text was updated successfully, but these errors were encountered: