billsacks
commented
6 years ago Would it help if we could query the coupler alarm clock that handles the averaging of fields sent to glc? e.g., could we somehow query (from glc) the previous time that alarm would have triggered?? (However, even if this works, I think it would mean assuming that the last mass balance time step started at the time when the last averaging period started... I'm not sure if we can always assume that....)
From @billsacks on April 8, 2017 13:21
I am putting a kludge in the GLC layer (in glc_InitMod.F90) that assumes mass balance time steps always occur at the end of the year: If a non-continue run starts mid-year, I'm assuming that the mass balance time step started at the beginning of that year.
If we ever want to allow mid-year mass balance time steps, we'll have to add some code to determine the correct starting time of the current mass balance time step. Note that, in principle, this can differ from the run start time: For example, say we do five mass balance time steps per year, each 73 days. If we start a run 80 days into the year, then the start time for the current mass balance time step should be set to 73 days into the year.
Copied from original issue: NCAR/CISM#1