Improve timestamp adjustment function in Glorys obc generation workflow #137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Several users have reported that the timestamp adjustment function in the current OBC workflow disrupts the original time variables and attributes, and will eventually mess up model run. This PR aims to address the issue by using
decode_times=False
when reading the files. Additionally, we have modified several boundary generation codes to further preserve the original time attributes and encoding.I have tested these updated codes with the ARCTIC case, and they appear to run successfully through the first month.
The example obc generation workflow for Arctic can be found on ppan:
/work/ynt/develop/20250124/CEFI-regional-MOM6/tools/boundary/glorys_obc_workflow
The Arctic 1-month test case can be found here:
/gpfs/f6/ira-cefi/proj-shared/ARC12_nofk_nsrwsp_newobcs.o207584449