-
Notifications
You must be signed in to change notification settings - Fork 19
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
Incorrect file timestamp with 24-hour duration and 1-hour frequency time-average #1064
Comments
Here is the issue where it was first reported: geoschem/GCHP#162 |
…t_file_timestamp Fixes #1064. This bug has been in MAPL for a long time (classical "fe…
Auto PR - develop → MAPL-v3 - Fixes #1064. This bug has been in MAPL for a long time (classical fence-post problem). Once the new segment alarm rings, the new file should be open only after the current time step is written.
Sigh. Re-opening again. I guess I used a "closing keyword" with GitHub. |
I found what went wrong with my earlier "fix". Moving the logical variable NewSeg logic to a different location ended up being in another do-loop, and as a result NewSeg was overwritten by each iteration of the first loop. I promoted newSeg to an array and that resolved the issue. And new PR is coming shortly |
…t_new_file Fixes #1064. Fixed error related to NewSeg logic
Auto PR - develop → MAPL-v3 - Fixes #1064. Fixed error related to NewSeg logic
Follow up from today's GCHP-MAPL call.
Collections with mode time-average, frequency 1-hour, and duration 24-hour aren't timestamped correctly (with the default Reference of 000000). If you enable
timestampStart
the files are stamped the previous day at 23:00. I believe that withouttimestampStart
they are stamped at 23:30 of the previous day.The text was updated successfully, but these errors were encountered: