Skip to content
Success

Changes

Summary

  1. At the ghost point below the surface, which does not matter in (details)
  2. The code that advances um and vm when l_predict_upwp_vpwp is turned off (details)
Commit 9e61ef088724b119d7c7f61a21b4c3d306058bcf by bmg2
At the ghost point below the surface, which does not matter in
the calculations, a value of 0 is now being entered for
thermodynamic-level output stats coef_wprtp2_implicit,
term_wprtp2_explicit, etc.

Why would we do this? The answer is "Why Not??!!!!"

This is being done to keep the trunk results bit-for-bit with
the clubb_ghost_exorcism branch, which is no longer loops over
the ghost level below the surface in the region of code
where these stats are recorded.

In terms of the master, this commit is technically BIT_CHANGING.
However, only for these 6 output terms at the ghost point.
The file was modified advance_xp2_xpyp_module.F90 (diff)
Commit 68d7df96e0daefd601d9649c886f68401a780ba1 by bmg2
The code that advances um and vm when l_predict_upwp_vpwp is turned off
(as found in advance_windm_edsclrm) was accessing the ghost point in
one spot. I rewrote it in the exact way the code in the
clubb_ghost_exorcism branch is written so that it makes the same
calculation without referencing the ghost point.

I also rewrote a couple stats by outputting a value of 0 at the ghost
point to maintain stat consistency between the master and the ghost
exorcism branch.

This commit is BIT_CHANGING, but only when the l_predict_upwp_vpwp
flag is set to false (which is not the case by default).
The file was modified advance_windm_edsclrm_module.F90 (diff)