Skip to content
Changes
- Fixes for fill_holes and edsclr code (#1266)
—
noreply /
githubweb
- Grid reverse matrix test (#1265)
—
noreply /
githubweb
- BIT_CHANGING bug fix for the penta_lu solver, only BC when using penta_solve_method=2 (#1264)
—
noreply /
githubweb
- Bicgstab addition (#1261)
—
noreply /
githubweb
- Small bug fix to make gfortran+debug happy, without the _core_rknd this could be a potential type error
—
Gunther Huebler /
githubweb
- Making update_xp2_mc work with either grid mode (#1263)
—
noreply /
githubweb
- Improving variable name
—
Gunther Huebler /
githubweb
- Small bug fix, but this is BIT_CHANGING because it affects stats output. Some zm fields (w_1_zm, w_2_zm, varnce_w_1_zm, varnce_w_2_zm, and mixt_frac_zm) were all nan in the netcdf output when l_call_pdf_closure_twice=.false., because those come from pdf_params_zm.
—
Gunther Huebler /
githubweb
- Removing accidentally added files
—
Gunther Huebler /
githubweb
- Making clubb_at_least_debug_level not a device routine. It confuses the poor little nvidia compiler when compiling inside cam. Also making the compile script a little more robust.
—
Gunther Huebler /
githubweb
- New fill_holes methods (#1262)
—
noreply /
githubweb
- Making compatible with new fill_holes update (#208)
—
noreply /
githubweb
- Small bug fix in fill_holes_parallel on GPU
—
Gunther Huebler /
githubweb
- Clubb driver upgrades part2 (#1257)
—
noreply /
githubweb
- Clubb driver upgrades part2 (#1257)
—
noreply /
githubweb
- Changes needed for compatibility with clubb_driver_upgrades_part2, from PR https://github.com/larson-group/clubb/pull/1257 (#204)
—
noreply /
githubweb
- Adding variables to openacc data statements. Without this, the code crashes when using the GPU with l_godunov_upwind_xpyp_ta=.true.
—
Gunther Huebler /
githubweb
- thlm_ed and rtm_ed caused GPU errors since those variables were added to a acc loop, but never added to the acc data statement. This change makes it so they're only calculated on the CPU, since they are only used for stats, fixing the issue without adding the GPU memory footprint.
—
Gunther Huebler /
githubweb
- Clubb intr revert (#203)
—
noreply /
githubweb
- Making the l_random_k_lh_start set the random generator seed before generating a random. This should fix the generalized grid test, which failed for the only flag set that turned on l_random_k_lh_start. Before, the test passed because we used the same random seed for all timesteps, preventing differences in the random call. But now we use a different seed each timestep, causing differences. To ensure reproducibility, we use the seed each timestep to generate rand_pool, which is an effective solution, but we need to do that for the rand_integer_in_range call in the l_random_k_lh_start code for the same reason. Since this does change the random that comes out, this is BIT_CHANGING, but only for runs using both SILHS and l_random_k_lh_start=.true.
—
Gunther Huebler /
githubweb
- SILHS reproducibility (#1258)
—
noreply /
githubweb
- Change tolerance in way that affects only single precision builds (#1256)
—
noreply /
githubweb
- Remove module vars from grid_adaptation_module (#1255)
—
noreply /
githubweb
- Precip frac fix (#1254)
—
noreply /
githubweb
- The cmake update (#1253)
—
noreply /
githubweb
- The cmake update (#1253)
—
noreply /
githubweb
- Adding expldiff budget terms for thlm and rtm (#1252)
—
noreply /
githubweb
- I am officially setting l_ascending_grid to false in CAM-CLUBB, meaning
—
bmg2 /
githubweb
- fix precision error of reals
—
noreply /
githubweb
- rename grid_adaptation and remapping modules
—
0-freundlich-adenin /
githubweb
- add fix for grid generalization
—
0-freundlich-adenin /
githubweb
- I've got the magic fix
—
bmg2 /
githubweb
- Merge grid adaptation implementation (#1249)
—
noreply /
githubweb
- zm and zt were mixed up in the error prints argument list.
—
bmg2 /
githubweb
- Bug fix to dimensions that was causing crashes. This is technically BIT_CHANGING.
—
Gunther Huebler /
githubweb
- Cam clubb silhs rev dir (#196)
—
noreply /
githubweb
- Our little problem of having CLUBB's zm stats not match at boundaries
—
bmg2 /
githubweb
- Cam clubb error handling jenkins test (#195)
—
noreply /
githubweb
- Update clubb_intr.F90
—
noreply /
githubweb
- Removed simple wrappers from clubb_api_module (#1245)
—
noreply /
githubweb
- Removed simple wrappers from clubb_api_module (#1245)
—
noreply /
githubweb
- Using a CLUBB function to do a linear interpolation. It's possible that
—
bmg2 /
githubweb
- Cam clubb error handling jenkins test (#194)
—
noreply /
githubweb
- Fixed and equalized NaN checks in lapack_wrap (#1246)
—
noreply /
githubweb
- Update clubb_intr.F90
—
noreply /
githubweb
- Cam clubb error handling jenkins test (#193)
—
noreply /
githubweb
- Cleaning up some grid generalization issues that were found within
—
bmg2 /
githubweb