Monthly files time axis

[MichaelSchulzMETNO]

The date counting in NorESM and CESM monthly files works is the following way :
during the simulation, monthly mean fields are calculated on the fly, and written to the file when the month is finished. The fields get the time-stamp of the time where the model is at that instant of time (of the writing) : so the file containing the mean of January will have as timestamp 1st of February 00h00. [the NCAR motivation behind this : if one would like, on can both put averaged and instantaneous fields in the same file, still using the same time-axis.]

Did anybody stumble over this ? Is that CMIP6 convention? Does xarray and pyaerocom read that month in as January ? @jgliss

[marekrataj]

Can be fixed by inserting this after importing pyaerocom:

import pyaerocom as pya
pya.const.GRID_IO.CORRECT_TIME_FILENAME = True
pya.const.GRID_IO.CHECK_TIME_FILENAME = True
pya.const.GRID_IO.PERFORM_FMT_CHECKS = True
pya.const.GRID_IO.CHECK_DIM_COORDS = True

*Jonas ;)

[MichaelSchulzMETNO]

From the CF convention on cell methods (7.3): @jgliss
The time axis values may coincide with the end of each interval. It is sometimes desirable, however, to use the midpoint of intervals as coordinate values for variables that are representative of an interval. An application may simply obtain the midpoint values by making use of the boundary data in time_bnds.