You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These changes are being requested to improve the ease-of-access of CESM data and to normalize the look of the metadata across CESM components. See ESCOMP/CESM#194 and especially the google doc referenced from ESCOMP/CESM#194 (comment).
@gold2718 I am not aware of any current usage for date and datesec in the ADF, but I'll ping that group to see if anyone uses those fields in general, and if it would be beneficial for them to have it match time.
@gold2718 that's a great catch. I for one do use the date variable as no conversion is necessary to read it (using ncdump for example). Yes, if we shift time to the center of the averaging period, date/datesec also needs to be shifted to align with the centered time. I will add this to #159.
cacraigucar
changed the title
Modify naming and attributes of time variables on history files to be consistent with other CESM components
Modify naming and attributes of time variables on history files to be consistent with other CESM components #554
May 2, 2022
These changes are being requested to improve the ease-of-access of CESM data and to normalize the look of the metadata across CESM components. See ESCOMP/CESM#194 and especially the google doc referenced from ESCOMP/CESM#194 (comment).
Current CAM time array output:
Proposed CAM time array output:
Changes made: time_bnds renamed as time_bounds, added units/calendar attributes to time_bounds, change bounds attribute of time to time_bounds
@billsacks @phillips-ad @strandwg are filing similar issues for each component.
The text was updated successfully, but these errors were encountered: