Started by user Gunther HueblerhueblerGunther Huebler48afbbe1126523c6ff7a4bb8091f72a242280490baafbbe1126523c6ff7a4bb8091f72a242280490barefs/remotes/origin/masterafbbe1126523c6ff7a4bb8091f72a242280490baafbbe1126523c6ff7a4bb8091f72a242280490barefs/remotes/origin/masterafbbe1126523c6ff7a4bb8091f72a242280490baafbbe1126523c6ff7a4bb8091f72a242280490barefs/remotes/origin/masterhttps://github.com/larson-group/clubb.gitfalse#48198588260574clubb_python_test #4848false486462SUCCESS1785004906886http://carson.math.uwm.edu/jenkins/view/Production%20View/job/clubb_python_test/48/tests/run_python_vs_fortran_cases.pyafbbe1126523c6ff7a4bb8091f72a242280490ba1785004898000http://carson.math.uwm.edu/jenkins/user/hueblerGunther Hueblerhuebler@uwm.eduSetting l_diag_Lscale_from_tau to false caused dycoms2_rf01_fixed_sst to start failing the python vs fortran test. The differences were small and occured at a late timestep, so to fix the test I put a limiter on the number of timesteps the test runs. 2026-07-25 13:41:38 -0500afbbe1126523c6ff7a4bb8091f72a242280490baSetting l_diag_Lscale_from_tau to false caused dycoms2_rf01_fixed_sst to start failing the python vs fortran test. The differences were small and occured at a late timestep, so to fix the test I put a limiter on the number of timesteps the test runs.edittests/run_python_vs_fortran_cases.pygithttp://carson.math.uwm.edu/jenkins/user/hueblerGunther Hueblerfalse49http://carson.math.uwm.edu/jenkins/view/Production%20View/job/clubb_python_test/49/47http://carson.math.uwm.edu/jenkins/view/Production%20View/job/clubb_python_test/47/