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
Provide a clear and concise description of the requested feature/capability.
The first column in hafs.trak.patcf corresponds to the output time in seconds relative to 00Z of each day. We would like to change it into seconds since model initialization time.
Proposed solution
How should the new feature/capability be added? If you have thoughts on the implementation strategy, please share them here.
Update the related source code to write out the needed time information in hafs.trak.patcf.
Status (optional)
Do you (or a colleague) plan to work on adding this feature?
Related to (optional)
Directly reference any related issues or PRs in this or other repositories, and describe how they are related. Examples:
fixed by hafs-community/hafs/pull/<pr_number>
The text was updated successfully, but these errors were encountered:
This is now fixed by this FV3dycore commit.
The time string of yyyymmdd.hhmmss instead of seconds of the day is now being output in the hafs.trak.patcf file.
This fix will go into HAFS develop once the feature/hafs_sync_202210 branch is merged.
Description
Provide a clear and concise description of the requested feature/capability.
The first column in hafs.trak.patcf corresponds to the output time in seconds relative to 00Z of each day. We would like to change it into seconds since model initialization time.
Proposed solution
How should the new feature/capability be added? If you have thoughts on the implementation strategy, please share them here.
Update the related source code to write out the needed time information in hafs.trak.patcf.
Status (optional)
Do you (or a colleague) plan to work on adding this feature?
Related to (optional)
Directly reference any related issues or PRs in this or other repositories, and describe how they are related. Examples:
The text was updated successfully, but these errors were encountered: