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

Update history attributes for time according to new CESM standards #387

Closed
ekluzek opened this issue May 26, 2023 · 0 comments · Fixed by #394
Closed

Update history attributes for time according to new CESM standards #387

ekluzek opened this issue May 26, 2023 · 0 comments · Fixed by #394
Labels
cesm-coupling For cesm coupling enhancement Improving usability, performance or other types of enhancements

Comments

@ekluzek
Copy link
Collaborator

ekluzek commented May 26, 2023

CESM updated the standards for output history files. And mizuRoute needs to update to the new standards.

This is applying the changes that are needed for CTSM to mizuRoute...

ESCOMP/CTSM#1693

mizuRoute current output:

	float time(time) ;
		time:long_name = "time" ;
		time:units = "days since YYYY-MM-DD HH:MM:SS" ;
		time:calendar = "noleap" ;

mizuroute proposed output (Changes made: time changed to type double, add new time_bounds added to give the time bounds for the averaging period.

	double time(time) ;
		time:long_name = "time" ;
		time:units = "days since YYYY-MM-DD HH:MM:SS" ;
		time:calendar = "noleap" ;
		time:bounds = "time_bounds" ;
	double time_bounds(time, nbnd) ;
		time_bounds:long_name = "time interval endpoints" ;
		time_bounds:units = "days since YYYY-MM-DD HH:MM:SS" ;
		time_bounds:calendar = "noleap" ;
@ekluzek ekluzek added enhancement Improving usability, performance or other types of enhancements cesm-coupling For cesm coupling labels May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cesm-coupling For cesm coupling enhancement Improving usability, performance or other types of enhancements
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants