Started by an SCM change863655285cd4ce9d65cec1b44cf2e6e578f4d08fe73655285cd4ce9d65cec1b44cf2e6e578f4d08fe7origin/master3655285cd4ce9d65cec1b44cf2e6e578f4d08fe73655285cd4ce9d65cec1b44cf2e6e578f4d08fe7origin/master88d63a0f595d93dccafcc9e7917c00fe97fd034a35d63a0f595d93dccafcc9e7917c00fe97fd034a35origin/grid_fixesd63a0f595d93dccafcc9e7917c00fe97fd034a35d63a0f595d93dccafcc9e7917c00fe97fd034a35origin/grid_fixes79c5c01fc5da140dc13df06c2919c4f4f5a0318b5fc5c01fc5da140dc13df06c2919c4f4f5a0318b5forigin/changes_to_not_breakc5c01fc5da140dc13df06c2919c4f4f5a0318b5fc5c01fc5da140dc13df06c2919c4f4f5a0318b5forigin/changes_to_not_break701344f8a40d6116af1b567307eb389b4be1009fc41344f8a40d6116af1b567307eb389b4be1009fc4refs/remotes/origin/changes_to_not_break1344f8a40d6116af1b567307eb389b4be1009fc41344f8a40d6116af1b567307eb389b4be1009fc4refs/remotes/origin/changes_to_not_break851d226e398bae00fe10255274a70f3451b5cc7d9e1d226e398bae00fe10255274a70f3451b5cc7d9eorigin/wangara_updates1d226e398bae00fe10255274a70f3451b5cc7d9e1d226e398bae00fe10255274a70f3451b5cc7d9eorigin/wangara_updates3678ba78b184c939bdd6b65ca77d7142aaf3d4adb478ba78b184c939bdd6b65ca77d7142aaf3d4adb47refs/remotes/origin/master8ba78b184c939bdd6b65ca77d7142aaf3d4adb478ba78b184c939bdd6b65ca77d7142aaf3d4adb47refs/remotes/origin/master8ba78b184c939bdd6b65ca77d7142aaf3d4adb478ba78b184c939bdd6b65ca77d7142aaf3d4adb47refs/remotes/origin/masterhttps://github.com/larson-group/sam_clubb.gitfalse#36756285807834sam_clubb_nvhpc_build #367367false367936SUCCESS1721378709007http://carson.math.uwm.edu/jenkins/job/sam_clubb_nvhpc_build/367/latin_hypercube_driver_module.F90fd2a66ac11b726371135f2233834e2e87562682c1721277738000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduIn my previous commit, I changed the domain of the maxloc commands in the computation of k_lh_start to check over the arrays from levels 2:nz. However, when that happens, the output will be offset by 1. Consider a situation where the rcm max is at level 2. By being passed 2 through nz only, maxloc will return a value of 1. I needed to add +1 to the output to rectify this issue. The results are BIT_CHANGING. 2024-07-17 23:42:18 -0500fd2a66ac11b726371135f2233834e2e87562682cIn my previous commit, I changed the domain of the maxloc commandseditlatin_hypercube_driver_module.F90stats_clubb_utilities.F90precipitation_fraction.F900df67106e4001e1eda48b4740fe1b065df06cd771721289115000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduThis commit brings the stats output from the all cases run with the master branch (using the default configuration) in bit-for-bit agreement with the stats output from all cases run with the clubb_ghost_exorcism branch. Of course, this agreement ignores the ghost level output in the zt files run with the master branch. This commit is technically BIT_CHANGING because it alters a few stats for a couple cases, but does not change results. 2024-07-18 02:51:55 -05000df67106e4001e1eda48b4740fe1b065df06cd77This commit brings the stats output from the all cases run witheditstats_clubb_utilities.F90editprecipitation_fraction.F90pdf_closure_module.F903e891b5d456b4ea869955e73e012cdd21813c1d91721347695000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduCommitting a change that will initialize this set of variables under all circumstances. This change does not affect output except when the New Hybrid PDF is used. In the case of the New Hybrid PDF, the variables F_rt, F_thl, F_rt_min, F_rt_max, F_thl_min, and F_thl_max were never initialized and never set (they are not part of the New Hybrid PDF -- only in the original New PDF), resulting NaN values being output to stat files. 2024-07-18 19:08:15 -05003e891b5d456b4ea869955e73e012cdd21813c1d9Committing a change that will initialize this set of variableseditpdf_closure_module.F90githttp://carson.math.uwm.edu/jenkins/user/bmg2bmg2false368http://carson.math.uwm.edu/jenkins/job/sam_clubb_nvhpc_build/368/366http://carson.math.uwm.edu/jenkins/job/sam_clubb_nvhpc_build/366/