Started by user Brian GriffingriffinbBrian Griffin1901644e80604055cf7a4910e9ace4213ac15f38fbf1644e80604055cf7a4910e9ace4213ac15f38fbfrefs/remotes/origin/clubb_silhs_devel1644e80604055cf7a4910e9ace4213ac15f38fbf1644e80604055cf7a4910e9ace4213ac15f38fbfrefs/remotes/origin/clubb_silhs_devel1644e80604055cf7a4910e9ace4213ac15f38fbf1644e80604055cf7a4910e9ace4213ac15f38fbfrefs/remotes/origin/clubb_silhs_develhttps://github.com/larson-group/cam.gitfalse#19014562492314875cam_BFB_coarse_res_gfortran_test #190190false19010372SUCCESS1748038025879http://carson.math.uwm.edu/jenkins/view/all/job/cam_BFB_coarse_res_gfortran_test/190/src/physics/cam/clubb_intr.F901644e80604055cf7a4910e9ace4213ac15f38fbf1748037675000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduI am officially setting l_ascending_grid to false in CAM-CLUBB, meaning that CLUBB's grid is now officially in descending mode in CAM, matching CAM's grid direction. With -O0 optimization and with CLUBB's l_test_grid_generalization turned on, results are a bit-for-bit match to the previous revision. However, normally CAM-CLUBB doesn't run with these options, which means these results should be BIT_CHANGING. This is probably my final commit to our battery of repositories. Thank you for 23 years, and God bless you! 2025-05-23 17:01:15 -05001644e80604055cf7a4910e9ace4213ac15f38fbfI am officially setting l_ascending_grid to false in CAM-CLUBB, meaningeditsrc/physics/cam/clubb_intr.F90githttp://carson.math.uwm.edu/jenkins/user/bmg2bmg2false191http://carson.math.uwm.edu/jenkins/view/all/job/cam_BFB_coarse_res_gfortran_test/191/189http://carson.math.uwm.edu/jenkins/view/all/job/cam_BFB_coarse_res_gfortran_test/189/