-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove deprecated history output #1281
Comments
Two questions on this:
|
Both variables should not even be available in any CLM5 or CTSM5.1 namelists flags. I'm assuming this is true for NWP too, but am less familiar with the soil hydrology used for WRF-CLM configurations. Does this help clarify? |
Maybe we need to talk about this. These variables are not appropriate for
specific settings of the hydrology lowery boundary condition. Not sure to
what extent we embed history output within namelist flags, but I guess this
is something we should do and maybe something that should be another
checklist item when creating a new namelist switch?
…On Sat, Feb 20, 2021 at 5:22 PM will wieder ***@***.***> wrote:
Both variables should not even be available in any CLM5 or CTSM5.1
namelists flags. I'm assuming this is true for NWP too, but am less
familiar with the soil hydrology used for WRF-CLM configurations. Does this
help clarify?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1281 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFABYVBYOKLNDNUBPJNLU3TTABG33ANCNFSM4XXRRBXQ>
.
|
Would the appropriate logic be: If this function returns a true value, then add those history variables; if not, they should not be available?: CTSM/src/biogeophys/SoilWaterMovementMod.F90 Lines 220 to 236 in f2faca6
|
I think so, though I don't off top of my head know how lres is subsequently
used (and what does lres stand for?)
…On Sun, Feb 21, 2021 at 8:24 AM Bill Sacks ***@***.***> wrote:
Would the appropriate logic be: If this function returns a true value,
then add those history variables; if not, they should not be available?:
https://github.com/ESCOMP/CTSM/blob/f2faca68cf854a2dd435b779841547e310536b32/src/biogeophys/SoilWaterMovementMod.F90#L220-L236
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1281 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFABYVHFQYORTMZ2JNUPXGTTAEQTRANCNFSM4XXRRBXQ>
.
|
lres is just the return value of the function. So use_aquifer_layer returns true if Unless I hear otherwise, I'll go ahead and make this change in a tag I'm working on in the next day or so. |
Refactor ozone code, and misc. small fixes (1) Restructure ozone code (#1276) in preparation for new ozone parameterization. (2) Fix non-standard hexadecimal constant (#1271), needed for gfortran 10 (3) Remove support for CISM1 (#1226) (4) Move final WaterGridcellBalance call out to clm_driver (resolves #1286) (5) Only add WA and QCHARGE history fields if use_aquifer_layer is true (resolves #1281) (6) Consolidate conditional structures for VIC initialization (resolves #1287) - Resolves #1286 (Move call to WaterGridcellBalance out to the driver) - Resolves #1281 (Remove deprecated history output) - Resolves #1287 (Inconsistent logic for VIC initialization can cause crash in debug mode) - Resolves #1270 (Hexadecimal constants use non-standard Fortran)
Refactor ozone code, and misc. small fixes (1) Restructure ozone code (ESCOMP#1276) in preparation for new ozone parameterization. (2) Fix non-standard hexadecimal constant (ESCOMP#1271), needed for gfortran 10 (3) Remove support for CISM1 (ESCOMP#1226) (4) Move final WaterGridcellBalance call out to clm_driver (resolves ESCOMP#1286) (5) Only add WA and QCHARGE history fields if use_aquifer_layer is true (resolves ESCOMP#1281) (6) Consolidate conditional structures for VIC initialization (resolves ESCOMP#1287) Conflicts: bld/namelist_files/namelist_defaults_ctsm.xml bld/unit_testers/build-namelist_test.pl
Refactor ozone code, and misc. small fixes (1) Restructure ozone code (ESCOMP#1276) in preparation for new ozone parameterization. (2) Fix non-standard hexadecimal constant (ESCOMP#1271), needed for gfortran 10 (3) Remove support for CISM1 (ESCOMP#1226) (4) Move final WaterGridcellBalance call out to clm_driver (resolves ESCOMP#1286) (5) Only add WA and QCHARGE history fields if use_aquifer_layer is true (resolves ESCOMP#1281) (6) Consolidate conditional structures for VIC initialization (resolves ESCOMP#1287) Conflicts: bld/namelist_files/namelist_defaults_ctsm.xml src/main/histFileMod.F90
Refactor ozone code, and misc. small fixes (1) Restructure ozone code (ESCOMP#1276) in preparation for new ozone parameterization. (2) Fix non-standard hexadecimal constant (ESCOMP#1271), needed for gfortran 10 (3) Remove support for CISM1 (ESCOMP#1226) (4) Move final WaterGridcellBalance call out to clm_driver (resolves ESCOMP#1286) (5) Only add WA and QCHARGE history fields if use_aquifer_layer is true (resolves ESCOMP#1281) (6) Consolidate conditional structures for VIC initialization (resolves ESCOMP#1287) Conflicts: src/biogeophys/CanopyFluxesMod.F90
Refactor ozone code, and misc. small fixes (1) Restructure ozone code (ESCOMP#1276) in preparation for new ozone parameterization. (2) Fix non-standard hexadecimal constant (ESCOMP#1271), needed for gfortran 10 (3) Remove support for CISM1 (ESCOMP#1226) (4) Move final WaterGridcellBalance call out to clm_driver (resolves ESCOMP#1286) (5) Only add WA and QCHARGE history fields if use_aquifer_layer is true (resolves ESCOMP#1281) (6) Consolidate conditional structures for VIC initialization (resolves ESCOMP#1287)
Looks like some model output may be written to history files for variables that have been deprecated in CLM5+.
Specifically, state and fluxes related to the unconfined aquifer (
QCHARGE
andWA
) are not needed in CLM5 and CTSM5.1.Removing these from history files will save space and avoid user confusion.
The text was updated successfully, but these errors were encountered: