Skip to content
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

Fixing Negative Ice Fluxes from Ocean to Glacier #2222

Closed
Katetc opened this issue Oct 26, 2023 · 4 comments · Fixed by #2455
Closed

Fixing Negative Ice Fluxes from Ocean to Glacier #2222

Katetc opened this issue Oct 26, 2023 · 4 comments · Fixed by #2455
Assignees
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix enhancement new capability or improved behavior of existing capability

Comments

@Katetc
Copy link

Katetc commented Oct 26, 2023

The default method of running CISM in CESM is "No-Evolve" or non-active ice sheet. Because the ice sheet can't grow or change in this configuration, all water fluxes through the ice sheet must be balanced. As long as CISM is running in any form, CTSM will calculate and downscale surface mass balance over the ice sheet(s), including melt fluxes in the summer and high snow amounts in the winter. In order to balance summer time melt fluxes from the ice sheet, CTSM will pull water from the ocean (a negative ice flux) to counter ice sheet melting in the summer.

A more realistic method for handling this need for balance would be to store the excess snow that is sent as run-off in the winter (due to the inactive ice sheet not being able to grow) in a water reservoir that can be accessed in the summer months to balance glacier melt. Our plan is to have excess snow capping over Greenland added to a "snow reservoir" that can be dealt out to balance melt in the summer months and decrease the need for water from the ocean.

I have started implementation of this and we would love to see it go into the CTSM version for CESM3.

@Katetc Katetc self-assigned this Oct 26, 2023
@ekluzek ekluzek added the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Oct 26, 2023
@ekluzek ekluzek added the enhancement new capability or improved behavior of existing capability label Oct 26, 2023
@ekluzek
Copy link
Collaborator

ekluzek commented Oct 26, 2023

@Katetc thanks for filing this. Is this related to #423?

@ekluzek
Copy link
Collaborator

ekluzek commented Feb 15, 2024

@Katetc is this being worked on? Is there still desire for this for the CESM3 release?

@ekluzek ekluzek added this to the CESM3 milestone Feb 15, 2024
@ekluzek ekluzek removed the next this should get some attention in the next week or two. Normally each Thursday SE meeting. label Feb 15, 2024
@ekluzek
Copy link
Collaborator

ekluzek commented Mar 21, 2024

In discussion with @Katetc the plan now is to move this functionality out of CTSM and into a Data Glacier model dglc into CDEPS.

@ekluzek ekluzek added the closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix label Apr 1, 2024
@ekluzek
Copy link
Collaborator

ekluzek commented Apr 1, 2024

We are going to do #1136 rather than this, so closing this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: wontfix We won't fix this issue, because it would be too difficult and/or isn't important enough to fix enhancement new capability or improved behavior of existing capability
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants