Started by an SCM change83d3946a586f66f155af6c32d7c6f9ed92389388cfd3946a586f66f155af6c32d7c6f9ed92389388cforigin/masterd3946a586f66f155af6c32d7c6f9ed92389388cfd3946a586f66f155af6c32d7c6f9ed92389388cforigin/master81c7eb33836dd22870dc48b2acd2b5b340dbeef909c7eb33836dd22870dc48b2acd2b5b340dbeef909origin/changes_to_not_breakc7eb33836dd22870dc48b2acd2b5b340dbeef909c7eb33836dd22870dc48b2acd2b5b340dbeef909origin/changes_to_not_break44107acaf17ed5e70d6886f2080bd303321dfd1982a07acaf17ed5e70d6886f2080bd303321dfd1982arefs/remotes/origin/master07acaf17ed5e70d6886f2080bd303321dfd1982a07acaf17ed5e70d6886f2080bd303321dfd1982arefs/remotes/origin/master07acaf17ed5e70d6886f2080bd303321dfd1982a07acaf17ed5e70d6886f2080bd303321dfd1982arefs/remotes/origin/masterhttps://github.com/larson-group/wrf.gitfalse#44150369465087586wrf_clubb_plot_ifort #441441false44111325SUCCESS1759394407248http://carson.math.uwm.edu/jenkins/view/all/job/wrf_clubb_plot_ifort/441/latin_hypercube_driver_module.F9050f5a9aa2d2a1e4894e9d0aa40f653db463beb151759358185000http://carson.math.uwm.edu/jenkins/user/hueblerGunther Hueblerhuebler@uwm.eduMaking the l_random_k_lh_start set the random generator seed before generating a random. This should fix the generalized grid test, which failed for the only flag set that turned on l_random_k_lh_start. Before, the test passed because we used the same random seed for all timesteps, preventing differences in the random call. But now we use a different seed each timestep, causing differences. To ensure reproducibility, we use the seed each timestep to generate rand_pool, which is an effective solution, but we need to do that for the rand_integer_in_range call in the l_random_k_lh_start code for the same reason. Since this does change the random that comes out, this is BIT_CHANGING, but only for runs using both SILHS and l_random_k_lh_start=.true. 2025-10-01 17:36:25 -050050f5a9aa2d2a1e4894e9d0aa40f653db463beb15Making the l_random_k_lh_start set the random generator seed before generating a random. This should fix the generalized grid test, which failed for the only flag set that turned on l_random_k_lh_start. Before, the test passed because we used the same random seed for all timesteps, preventing differences in the random call. But now we use a different seed each timestep, causing differences. To ensure reproducibility, we use the seed each timestep to generate rand_pool, which is an effective solution, but we need to do that for the rand_integer_in_range call in the l_random_k_lh_start code for the same reason. Since this does change the random that comes out, this is BIT_CHANGING, but only for runs using both SILHS and l_random_k_lh_start=.true.editlatin_hypercube_driver_module.F90githttp://carson.math.uwm.edu/jenkins/user/hueblerGunther Hueblerfalse442http://carson.math.uwm.edu/jenkins/view/all/job/wrf_clubb_plot_ifort/442/440http://carson.math.uwm.edu/jenkins/view/all/job/wrf_clubb_plot_ifort/440/