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
Is your feature request related to a problem? Please describe.
Snapshot diagnostics lack the time_bnds variable, causing the start_date and end_date from the intake-esm datastore to be incorrect.
One example is shown below, with the restart file access-om3.mom6.r.1915-01-01-00000.nc, where the output frequency is 2 hours and the total runlength is 30 hours, the start_date shows as 1915-01-01, 01:00:00 and the end_date is 1915-01-02, 07:00:00, instead of 1915-01-01, 00:00:00 and 1915-01-02 06:00:00.
path
realm
variable
frequency
start_date
end_date
xx
ocean
xx
2hr
1915-01-01, 01:00:00
1915-01-02, 07:00:00
Describe the feature you'd like
Properly parse the date info such as,
path
realm
variable
frequency
start_date
end_date
xx
ocean
xx
2hr
1915-01-01, 00:00:00
1915-01-02, 06:00:00
The text was updated successfully, but these errors were encountered:
I stupidly didn't think about snapshot data when writing get_timeinfo. There's some logic in there to try and guess the start and end dates when time bounds are not present, but I realise now that this will produce incorrect start and end dates for snapshot data. I guess this logic should probably just be removed (i.e. remove this), though that will mean the start and end dates will be wrong for non-snapshot output that doesn't provided time bounds...
Is your feature request related to a problem? Please describe.
Snapshot diagnostics lack the
time_bnds
variable, causing thestart_date
andend_date
from the intake-esm datastore to be incorrect.One example is shown below, with the restart file
access-om3.mom6.r.1915-01-01-00000.nc
, where the output frequency is 2 hours and the total runlength is 30 hours, thestart_date
shows as1915-01-01, 01:00:00
and theend_date
is1915-01-02, 07:00:00
, instead of1915-01-01, 00:00:00
and1915-01-02 06:00:00
.Describe the feature you'd like
Properly parse the date info such as,
The text was updated successfully, but these errors were encountered: