Started by an SCM change42156254ef6787724e586ed16a974b53a66539af8a956254ef6787724e586ed16a974b53a66539af8a9refs/remotes/origin/master56254ef6787724e586ed16a974b53a66539af8a956254ef6787724e586ed16a974b53a66539af8a9refs/remotes/origin/master56254ef6787724e586ed16a974b53a66539af8a956254ef6787724e586ed16a974b53a66539af8a9refs/remotes/origin/masterhttps://github.com/larson-group/clubb.gitfalse#421307231419302clubb_release_diff_test #421421false421588SUCCESS1712392568765http://carson.math.uwm.edu/jenkins/view/all/job/clubb_release_diff_test/421/src/CLUBB_core/advance_windm_edsclrm_module.F9056254ef6787724e586ed16a974b53a66539af8a91712376324000http://carson.math.uwm.edu/jenkins/user/bmg2bmg2bmg2@uwm.eduThe 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). 2024-04-05 23:05:24 -050056254ef6787724e586ed16a974b53a66539af8a9The code that advances um and vm when l_predict_upwp_vpwp is turned offeditsrc/CLUBB_core/advance_windm_edsclrm_module.F90githttp://carson.math.uwm.edu/jenkins/user/bmg2bmg2false422http://carson.math.uwm.edu/jenkins/view/all/job/clubb_release_diff_test/422/420http://carson.math.uwm.edu/jenkins/view/all/job/clubb_release_diff_test/420/