NOC-MSM / pyBDY

pyBDY: a Python based regional NEMO model configuration toolbox.
GNU General Public License v3.0
7 stars 7 forks source link

time_counter error: time_origin corresponds to child data rather than parent #128

Open jenjar93 opened 1 year ago

jenjar93 commented 1 year ago

In the BDY output, the time_counter units (for the benchmark data) are:

time_counter:units = "seconds since 1960-01-01 00:00:00" ; time_counter:title = "Time" ; time_counter:long_name = "Time axis" ; time_counter:time_origin = "1960-01-01 00:00:00" ;

But it looks like the time_origin is the year corresponding to the child data instead, e.g. 1979-01-01 for the benchmark.

jenjar93 commented 1 year ago

Potential easy fix:

Looks like the time_origin is set by the nn_base_year in the namelist. So the time_counter units in the child data are now the no. of seconds from nn_base_year. (In the past nn_base_year was set to the parent data's time_origin and the no. of seconds would be from that).

Without changing any of the base code, an easy solution would be to set nn_base_year the same as nn_year_00/nn_year_end?