-
Notifications
You must be signed in to change notification settings - Fork 136
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
2024.01 changelog and version updates #1507
Conversation
@bensonr @uramirez8707 This should be ready now, it's been updated for those two comments |
- Support defining subregions with indices | ||
- More flexibility when adding metadata and defining output frequency | ||
- FMS2_IO: Adds support for collective parallel reads to improve model startup time. The collective reads are disabled by default and enabled via the `use_collective` flag in `netcdf_io_mod`. | ||
- DATA_OVERRIDE: Adds multifile support for using 3 input netcdf files instead of one. Three keys have been added to the data_table: `is_multi_file` to be set to true to enable the feature, as well as `prev_file_name` and `next_file_name` to set to the names of the additional files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The multi-file support in data_override is only up to 3 files?
- FMS2_IO: Adds support for collective parallel reads to improve model startup time. The collective reads are disabled by default and enabled via the `use_collective` flag in `netcdf_io_mod`. | ||
- DATA_OVERRIDE: Adds multifile support for using 3 input netcdf files instead of one. Three keys have been added to the data_table: `is_multi_file` to be set to true to enable the feature, as well as `prev_file_name` and `next_file_name` to set to the names of the additional files. | ||
- INTERPOLATOR: Adds support for yearly/annual data | ||
- DATA_OVERRIDE: Adds support for monotonically increasing/decreasing arrays |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this needs clarified for which axes we are able to do this for or at a minimum a reference to the GitHub issue and/or PR.
- Self-describing YAML formatting for diag_table's | ||
- Allows 4d variables | ||
- Support defining subregions with indices | ||
- More flexibility when adding metadata and defining output frequency |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Updated math and buffer handling for better support when send_data is called in a threaded region
- New diag manager requires a call to diag send complete.
- @uramirez8707 Do you think there's anything else to add?
|
||
### Added | ||
- DIAG_MANAGER: The diag manager has been rewritten with a object oriented design. The old diag_manager code has been kept intact and will be used by default. The rewritten diag manager can be enabled via `use_modern_diag = .true.` to your `diag_manager_nml`. New features include: | ||
- Self-describing YAML formatting for diag_table's |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You dont need the apostrophe in diag_tables
Description
2024.01 updates
Checklist:
make distcheck
passes