Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Glacier surface mass balance (Flgl_qice) should be added to the budget tables in med_diag_mod

Abierto
#660 0 comentarios 0 reacciones 1 asignado Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
fortran
Área
backend

Línea de trabajo

Comienza localizando med_diag_mod y el código de las tablas de presupuesto; después, revisa la discusión 344 para obtener contexto. Rastrea los flujos de la GLC-grid, icemask_coupled_fluxes y el tratamiento de las clases de elevación para Flgl_qice y Flgl_qice_elev. Se considera terminado cuando los flujos de agua y calor aparecen en las tablas de presupuesto sin contar dos veces las celdas excluidas o ya contabilizadas.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Emerging from https://github.com/NCAR/cesm_dev/discussions/344 - though this is something I've periodically remembered and later forgotten for a long time....

I believe that we need to add glacier surface mass balance (Flgl_qice / Flgl_qice_elev) to the budget tables. This is an output flux from lnd and an input flux to glc; there is a water flux and a corresponding heat flux.

A few things make this more challenging than other fluxes in the budget tables (and I think this is part of why we haven't already done this):

(1) In some configurations, there is a non-zero qice flux but it shouldn't be included in the budgets because it is just a diagnostic term that is already accounted for with other fluxes. This was the case for CISM in NOEVOLVE mode. Now that we're using DGLC for NOEVOLVE mode, this is less of an issue. It would still be an issue if running CISM in NOEVOLVE mode (though @mvertens is doing some work to make CISM in NOEVOLVE mode work more like DGLC's NOEVOLVE mode, in that it will handle these fluxes), or with some less common configurations (CISM options that we can perhaps ignore).

(2) Even in now-standard configurations, we still shouldn't be including qice in the budget tables for all grid cells: I think CTSM sends non-zero qice even in areas where GLC can't handle these fluxes (as determined by icemask_coupled_fluxes); in these places, CTSM also sends an equivalent flux to the river; so including qice in the budget tables in these locations would be double-counting.

(3) QICE from LND is broken down by elevation class, so requires some custom code to make global averages (weighting each elevation class appropriately). (This could possibly be worked around by using the field mapped to the GLC grid, and not trying to work with the field on the LND grid.)

My initial thought on how to handle all this is: compute this piece of the budgets on the GLC grid rather than the LND grid; that will deal with point (3) (this wouldn't allow us to check the conservation of the lnd->glc mapping with the budget tables, but I think that's a reasonable price to pay). Multiply the GLC grid cell values by Sg_icemask_coupled_fluxes in computing the budget numbers; this will deal with both points (1) and (2).

Lenguaje dominante
Fortran
Estrellas
36
Forks
107
Merge medio
1 d 7 h
PR fusionados (30 d)
2

Preparar el entorno

  • Sin Dockerfile ni archivo de Docker Compose
  • Tiene una plantilla de pull request
  • Sin guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ESCOMP/CMEPS

Todos los issues de ESCOMP/CMEPS

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.