-
Notifications
You must be signed in to change notification settings - Fork 114
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
IOOUTPUT is skipping times that would round to the next day #326
Comments
@mrjohnston It seems it is because when we wrote the codes, we always round the input observational time up (always use a later time, see below code chunk). So these times will be converted to a time value of 86400 (seconds). Lines 1262 to 1279 in fa80dab
Meanwhile, the model timer will automatically add one day and change time to zero when the time of day is greater or equal than 86400 (see below). So 86400 will never be reached in the model. ED2/ED/src/utils/update_derived_utils.f90 Lines 1817 to 1821 in fa80dab
One way to fix this is to similarly add one day and convert time to zero in read_obstime. |
You may be able to fix this by using some of the existing subroutines in ED2. Without thinking too much (so likely to have errors), you could try the following:
|
@mpaiao Thanks! It is always good to use existing utilities... |
@xiangtaoxu @mpaiao Thanks both! Fixing this is on my to-do list (feel free to assign me!), but it may take me a little while to get to. |
When the observation outputs are requested in ED2IN (IOOUTPUT = 3), the model should output fast timescale files within 10 minutes of the time requested in the input timelist (a text file).
It skips outputting files requested at times that would round to the next day, for example:
2018-08-01 23:54:08
2019-06-16 23:57:34
2020-02-13 23:51:48
The text was updated successfully, but these errors were encountered: