Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
jenjar93 opened this issue Jun 7, 2023 · 1 comment
Labels
question Further information is requested

Comments

@jenjar93
Copy link

jenjar93 commented Jun 7, 2023

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 jenjar93 added the question Further information is requested label Jun 8, 2023
@jenjar93
Copy link
Author

jenjar93 commented Jun 8, 2023

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant