Skip to content
Failed

Changes

Summary

  1. In my previous commit, I changed the domain of the maxloc commands (details)
  2. This commit brings the stats output from the all cases run with (details)
  3. Committing a change that will initialize this set of variables (details)
Commit fd2a66ac11b726371135f2233834e2e87562682c by bmg2
In 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.
The file was modified latin_hypercube_driver_module.F90 (diff)
Commit 0df67106e4001e1eda48b4740fe1b065df06cd77 by bmg2
This 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.
The file was modified stats_clubb_utilities.F90 (diff)
The file was modified precipitation_fraction.F90 (diff)
Commit 3e891b5d456b4ea869955e73e012cdd21813c1d9 by bmg2
Committing 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.
The file was modified pdf_closure_module.F90 (diff)