Ice runoff changes when coupling an evolving Greenland ice sheet #393
Replies: 2 comments 4 replies
|
Hi @billsacks, @mvertens pointed me to this issue. Thanks for the detailed explanation and deep analysis. I am looking at the integrated ice runoff (variable QGLC_ICE_INPUT 'MOSART input ice runoff from glacier') over Greenland-ish* (*masking for lat-lon, as I don't have a Greenland mask on the 0.5 degree MOSART grid) for two identical NorESM runs, one with DGLC and one with evolving GrIS. We also see a very different behaviour, with values in the GrIS%EVOLVE case on the very high end than those found in the DGLC case, see screenshots below (the recurring zero values in the DGLC case is an issue we are looking at here, but not relevant for this discussion I think). Do you see an ice runoff increase of comparable magnitude in CESM, or is it way more? In our GrIS%EVOLVE case we have physical calving, frontal ablation and other artificial quantities such as remove_ice_caps and force_retreat (not sure you are using that, we use it to mask out ice outside the present-day GrIS extent) contributing to ice_runoff. So even though I haven't yet tried to compute the actual budget (probably very complicated, but I'll make an attempt), qualitatively the behaviour I am seeing in our GrIS%EVOLVE makes sense, as we know that this budget is very likely dominated by force_retreat, which is dumping ice year after year around the margins (see third screenshot below) and don't have much of a interannual variability signal. If the signal is dominated by QFLX_ICE_DYNBAL fluxes, am I wrong assuming that we would see much more interannual variability in our curve? |
|
From Bill's original post: It is not "in some sense undesirable", it is absolutely unacceptable. While I don't find the opaque explanation above helpful in understanding why the formulation of the CTSM/glacier model combo requires negative liquid or frozen runoff from another component model, the idea that the ocean should spontaneously create icebergs that then crawl up onto land preposterous and puts us at risk of having CESM3 exposed and labeled as an non-physical climate model by bad actors. This is not just an opinion about physical plausibility. The consequences of this negative runoff error - liquid or frozen - are far more severe in MOM6 than they were in POP. Removing fresh water from MOM6 changes the concentration of EVERY ocean tracer - the volume of water changes but the mass of tracer does not. In POP we did not change the actual volume of water, we changed only the salinity when adding/subtracting fresh water. Asking the ocean to provide water to the land model will change the concentration of zooplankton or dissolved CO2 for example. Do we really want to see phytoplankton blooms around Greenland when you need some snow? Asking for a phase change in the water additionally changes the ocean heat content and temperature even further. Any fixer required to offset inconsistencies or gaps in formulation within the land/glacier model combo should be offset within those models. |




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I have been talking with @gustavo-marques @cecilehannay @wwieder @dlawrenncar, @gunterl and @Katetc over the past couple of weeks about changes in ice runoff around Greenland when changing from DGLC to CISM with an evolving Greenland ice sheet. I am starting this discussion to record some findings and other general notes about that. (@whlipscomb - also keeping you in the loop here.)
This is connected to run 382, run 384, and some subsequent runs.
@gustavo-marques 's finding was that, when switching from DGLC to CISM, the ice runoff from CTSM increased dramatically. We dug into trying to understand the cause of this increase and what could be done to mitigate it.
First, let's take a moment to understand the major sources of ice runoff over Greenland, both with DGLC and with CISM. With the caveat that I may be forgetting something, here are the major sources I can think of:
Through some investigation, we determined that the main source of the fluxes @gustavo-marques found was this last term - the dynamic landunit conservation correction, QFLX_ICE_DYNBAL. From spot-checking some points where this term is large, I determined that the main source of this term is from differences in the snow pack between CTSM's vegetated / bare land column and its glacier columns. Therefore, when the ice sheet advances or retreats, the grid cell average snow pack water content changes, and QFLX_ICE_DYNBAL compensates for this change to conserve water.
(More details: In many cases, the snow pack in a given CTSM column is either near its maximum value (10 m water equivalent) or near 0 (less than about 1 m water equivalent). Differences in snow pack depth between columns largely arise from the differences in elevations of these different columns; glacier columns can have either more or less snow pack than vegetated columns. In some spot-checked grid cells, I was able to reproduce the QFLX_ICE_DYNBAL flux pretty closely by just looking at the difference in average H2OSNO before and after the ice sheet area change at the year boundary, and then calculating the annual-average flux that would be needed to balance this change, as is done in CTSM.)
The consistently positive ice runoff fluxes observed by @gustavo-marques arise from the interaction between three behaviors in the model:
We considered a few solutions or workarounds for this:
reset_dynbal_baselinesflag to true. This flag resets what is considered the zero point for some pieces of the DYNBAL flux calculations. It turns out, though, that this doesn't help with the ice runoff problem discussed here, because the snow pack is deliberately excluded from these baseline calculations. Nevertheless, I still recommend doing this at one or more points along the spinup to reduce the sensible heat flux generated from these landunit transitions. Without setting this flag, we can get dynbal sensible heat fluxes up to 10s of W m-2 in select grid cells, persistent across the year; based on some quick looks, we can reduce these dynbal sensible heat fluxes by about a factor of 10. Setting this flag to true can be done at the start of a hybrid run; doing so breaks conservation at the beginning of that run, but then conservation is maintained from that point forward. There is more documentation of this flag here. It takes some thought to determine when you do / don't want to set this flag, but it feels safe to set it at this relatively early stage of spinup, when we're still going to have some conservation breakages later anyway when we spin up the surface components offline.Longer-term, I have some ideas about how we could further reduce the DYNBAL fluxes from CTSM, and I will open a CTSM issue about that.
All reactions