Skip to content
Sign in
Success

Changes

Summary

  1. Setting l_diag_Lscale_from_tau to false by default, and changing it to true in the flag set list the run_bindiff_w_flags test uses so that we keep testing the tau code nightly. This flag changes answers, so this is BIT_CHANGING. (details)
  2. Setting 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. (details)
Commit 02babc6b5a46bda3075bf071426fa20bf200a43b by Gunther Huebler
Setting l_diag_Lscale_from_tau to false by default, and changing it to true in the flag set list the run_bindiff_w_flags test uses so that we keep testing the tau code nightly. This flag changes answers, so this is BIT_CHANGING.
The file was modifiedinput/parameter_and_flag_configs/default/configurable_model_flags.in (diff)
The file was modifiedinput/flag_sets/run_bindiff_w_flags_config_core_flags.json (diff)
The file was modifiedsrc/CLUBB_core/model_flags.F90 (diff)
Commit afbbe1126523c6ff7a4bb8091f72a242280490ba by Gunther Huebler
Setting 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.
The file was modifiedtests/run_python_vs_fortran_cases.py (diff)