Started by an SCM change357c9083983343f851915dccdd10d7d6ff7baad24b3c9083983343f851915dccdd10d7d6ff7baad24b3refs/remotes/origin/masterc9083983343f851915dccdd10d7d6ff7baad24b3c9083983343f851915dccdd10d7d6ff7baad24b3refs/remotes/origin/masterc9083983343f851915dccdd10d7d6ff7baad24b3c9083983343f851915dccdd10d7d6ff7baad24b3refs/remotes/origin/masterhttps://github.com/larson-group/clubb.githttp://carson.math.uwm.edu/jenkins/blue/organizations/jenkins/clubb_timestep_gfortran_tests/detail/clubb_timestep_gfortran_tests/357/artifactshttp://carson.math.uwm.edu/jenkins/blue/organizations/jenkins/clubb_timestep_gfortran_tests/detail/clubb_timestep_gfortran_tests/357/changeshttp://carson.math.uwm.edu/jenkins/blue/organizations/jenkins/clubb_timestep_gfortran_tests/detail/clubb_timestep_gfortran_tests/357/http://carson.math.uwm.edu/jenkins/blue/organizations/jenkins/clubb_timestep_gfortran_tests/detail/clubb_timestep_gfortran_tests/357/testsfalsefalse#357849299596301clubb_timestep_gfortran_tests #357357false357754SUCCESS1721203989102http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/357/src/advance_microphys_module.F90babbea90fd1f140ca1634aae59fd8df3366404571721151675000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduSetting the value of K_hm to 0 at the non-interactive upper and lower boundaries. The values of that variable at those levels don't get used in the code. This change is meant to keep stats the same between the master branch and the clubb_ghost_exorcism branch. This changes does not change the simulations, but yet it is BIT_CHANGING because it changes stat files output at those levels. 2024-07-16 12:41:15 -0500babbea90fd1f140ca1634aae59fd8df336640457Setting the value of K_hm to 0 at the non-interactive upper and lowereditsrc/advance_microphys_module.F90src/CLUBB_core/advance_clubb_core_module.F90src/CLUBB_core/stats_clubb_utilities.F90c9083983343f851915dccdd10d7d6ff7baad24b31721188165000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduI am committing changes to stats output for cloud_cover, rcm_in_layer, and z_cloud base owing to the gymnastics it takes to avoid the ghost point in calculations. These changes are BIT_CHANGING, but they don't change the answer. 2024-07-16 22:49:25 -0500c9083983343f851915dccdd10d7d6ff7baad24b3I am committing changes to stats output for cloud_cover, rcm_in_layer,editsrc/CLUBB_core/advance_clubb_core_module.F90editsrc/CLUBB_core/stats_clubb_utilities.F90githttp://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2falseStarted by an SCM change358876a5a7674acbc3609a50dfeb45e791acee01583876a5a7674acbc3609a50dfeb45e791acee01583refs/remotes/origin/master876a5a7674acbc3609a50dfeb45e791acee01583876a5a7674acbc3609a50dfeb45e791acee01583refs/remotes/origin/master876a5a7674acbc3609a50dfeb45e791acee01583876a5a7674acbc3609a50dfeb45e791acee01583refs/remotes/origin/masterhttps://github.com/larson-group/clubb.gitfalse#358828605596301clubb_timestep_gfortran_tests #358358false358826SUCCESS1721290389199http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/358/src/SILHS/latin_hypercube_driver_module.F901cb88726a7f824b8844fe32eff22b09991b8de6c1721242346000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduThere were furhter issues found with the k_lh_start code. The code would find that sometimes, the maximum location of rcm in cloud would occur at the ghost level, k = 1, and set that level as k_lh_start for SILHS. This is undesirable for two reasons: 1) k_lh_start should be set around a legimate, "within domain" grid level; and 2) Setting k_lh_start to 1 is unachievable for the ghostless branch of the model, making a match between the master and clubb_ghost_exorcism branhes unattainable. The issue is corrected here by allowing the maxloc function to only search over "in-domain levels" for maximum cloud. The results are BIT_CHANGING. 2024-07-17 13:52:26 -05001cb88726a7f824b8844fe32eff22b09991b8de6cThere were furhter issues found with the k_lh_start code.editsrc/SILHS/latin_hypercube_driver_module.F90src/CLUBB_core/advance_clubb_core_module.F90src/CLUBB_core/mixing_length.F90src/CLUBB_core/advance_helper_module.F90acdd31a8d397f5a8874cba8023e9376fe1d9e6511721258040000http://carson.math.uwm.edu/jenkins/user/noreplynoreplynoreply@github.comRi_zm calc (Part 3) - Moving calculations for Ri_zm out of diagnose_Lscale_from_taus (#1157) CLUBB tocket #1145 BIT_CHANGING for lscale since Ri_zm was not calculated before. 1. mixing_length.F90: - Removed unused input variables from diagnose_Lscale_from_taus: um, vm, exner, p_in_Pa, rtm, thlm, thvm, rcm, saturation_formula, l_brunt_vaisala_freq_moist, l_use_thvm_in_bv_freq, l_modify_limiters_for_cnvg_test; added ddzt_umvm_sqd as input; changed Ri_zm from out to in - Removed unused brunt_vaisala_freq_sqd variables from diagnose_Lscale_from_tau - Removed calculations for Ri_zm and ddzt_umvm_sqd - Fixed some line length issues 2. advance_helper_module.F90 - Removed unused input variables and imports - Fixed some line length issues 3. advance_clubb_core_module.F90 - Added calculations for ddzt_umvm_sqd and Ri_zm - Adjusted subroutine calls - Fixed some line length issues 2024-07-17 18:14:00 -0500acdd31a8d397f5a8874cba8023e9376fe1d9e651Ri_zm calc (Part 3) - Moving calculations for Ri_zm out of diagnose_Lscale_from_taus (#1157)editsrc/CLUBB_core/advance_clubb_core_module.F90editsrc/CLUBB_core/mixing_length.F90editsrc/CLUBB_core/advance_helper_module.F90src/SILHS/latin_hypercube_driver_module.F90370b85fd1991810e0a1dec311f66ad10fa92275f1721277738000http://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 -0500370b85fd1991810e0a1dec311f66ad10fa92275fIn my previous commit, I changed the domain of the maxloc commandseditsrc/SILHS/latin_hypercube_driver_module.F90src/CLUBB_core/precipitation_fraction.F90src/CLUBB_core/stats_clubb_utilities.F90876a5a7674acbc3609a50dfeb45e791acee015831721289115000http://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 -0500876a5a7674acbc3609a50dfeb45e791acee01583This commit brings the stats output from the all cases run witheditsrc/CLUBB_core/precipitation_fraction.F90editsrc/CLUBB_core/stats_clubb_utilities.F90githttp://carson.math.uwm.edu/jenkins/user/bmg2bmg2http://carson.math.uwm.edu/jenkins/user/noreplynoreplyfalse359http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/359/357http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/357/Started by an SCM change356933df4321f09c1fec44e953ec022ad2b3c7e4fb2933df4321f09c1fec44e953ec022ad2b3c7e4fb2refs/remotes/origin/master933df4321f09c1fec44e953ec022ad2b3c7e4fb2933df4321f09c1fec44e953ec022ad2b3c7e4fb2refs/remotes/origin/master933df4321f09c1fec44e953ec022ad2b3c7e4fb2933df4321f09c1fec44e953ec022ad2b3c7e4fb2refs/remotes/origin/masterhttps://github.com/larson-group/clubb.gitfalse#356854900596301clubb_timestep_gfortran_tests #356356false356706SUCCESS1721117589760http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/356/utilities/sens_matrix/set_up_dashboard_inputs.pyutilities/sens_matrix/create_figs.py360ded1ba8967a18620426bf0a2bef72c161525e1721073282000http://carson.math.uwm.edu/jenkins/user/vlarsonVince Larsonvlarson@uwm.eduQuadTune: Adds arrow plot and plot of bias vs. a diagnostic field such as U10. For #910. 2024-07-15 14:54:42 -0500360ded1ba8967a18620426bf0a2bef72c161525eQuadTune: Adds arrow plot and plot of bias vs. a diagnostic field such as U10.editutilities/sens_matrix/create_figs.pyeditutilities/sens_matrix/set_up_dashboard_inputs.pysrc/coamps_microphys_driver_module.F90253c4a69a11b450a9d100726820d9f35976f7d5a1721077282000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduI am making this commit because, as part of deghosting, I discovered 2 bugs in the way that COAMPS microphysics was set up. 1) The code that was handling the grid flipping for hydrometeor sedimentation velocities output from coamps (flipping from the coamps grid to the clubb grid) was mis-aligned; 2) The code within coamps then interpolated those velocities to the zm grid However, CLUBB expected that output on the zt grid. These issues were corrected in this commit that is BIT_CHANGING for mpace_b -- the only case that uses COAMPS microphysics by default. 2024-07-15 16:01:22 -0500253c4a69a11b450a9d100726820d9f35976f7d5aI am making this commit because, as part of deghosting, I discovered 2editsrc/coamps_microphys_driver_module.F90src/coamps_microphys_driver_module.F90933df4321f09c1fec44e953ec022ad2b3c7e4fb21721104295000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduI am updating the snowslope output stat so it matches bit-for-bit with the output of the clubb_ghost_exorcism branch. This commit is BIT_CHANGING. 2024-07-15 23:31:35 -0500933df4321f09c1fec44e953ec022ad2b3c7e4fb2I am updating the snowslope output stat so it matches bit-for-biteditsrc/coamps_microphys_driver_module.F90githttp://carson.math.uwm.edu/jenkins/user/bmg2bmg2http://carson.math.uwm.edu/jenkins/user/vlarsonVince Larsonfalse357http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/357/355http://carson.math.uwm.edu/jenkins/job/clubb_timestep_gfortran_tests/355/