Skip to content

Add an option to run OGGM on calendar years instead of hydro years #844

@fmaussion

Description

@fmaussion

While working on #824, I started thinking again about this problem. I also wrote this email to a few WGMS specialists:

it is really a small detail, but I'd like to get it "right" once for good. In OGGM, we use the "hydrological year" as time unit, with the "hydrological year" starting at month 10 in the northern hemisphere and at month 4 in the southern hemisphere. The main reason we use this convention is because we compare our modeled MB with the WGMS, which documents it this way in the guidelines for submission (https://www.wgms.ch/downloads/WGMS_GuidelinesforDataSubmission.pdf).

But I wonder if the equator really is the best separation line for the definition of the hydrological year. In particular, I wonder if the Peruvian and Central American WGMS correspondents really use the SH definition of an hydrological year: for example, the climate in Peru is equally well suited for a NH hydrological year convention. Do you have any comment on that, Michael and Antoine?

Anyways: it's not a big deal and I'm happy to keep the equator as separation between NH-hydro and SH-hydro years. The only "funny" situation is the RGI region "Low Latitudes" where our tabular files have different dates for different glaciers as a result.

We had a similar discussion at one GlacierMiP meeting - OGGM currently stores its annual output in "hydrological years units", and we should maybe switch back to calendar time for that reason...

As always, the best would always be to give all options to the user: calendar or hydro years.

Funny enough, the problem is more complex than one would expect, in particular because it involves changes in the mass-balance, flowline, and utils.compile* modules...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions