Michael Duda

> @mgduda thank you for your response. We are currently finalizing the support for AOCC 4.0 and Zen4 ARCH in WRF internally. Please give us some time to update this...

If I'm not mistaken, this is the last PR that we're waiting on before creating the `release-v4.6.0` branch. Do we have a sense for how soon we'll be able to...

@scrasmussen @rcabell Do you have an estimate for when this PR will be out of draft mode and ready for final review? Is it just a resolution to the MPI...

@islas Perhaps there have been changes to the modules on derecho, or perhaps my process was different, but I didn't find any issues in compiling with option 32 on derecho...

> @islas @mgduda Should we leave it for 4.6 consideration? I think that seems reasonable. It may turn out that we remove even the HDF5 I/O API code, which seems...

@islas I've changed the base branch for this PR to `develop`. Could you rebase the branch so that only the intended commits are included?

If I understand correctly, WRFDA sometimes requires HDF5 even outside of its use in the WRF I/O API; see the [installation instructions](https://www2.mmm.ucar.edu/wrf/users/wrf_users_guide/build/html/wrfda.html#installing-wrfda). Would this PR affect compilation of WRFDA with...

The WRF v4.6 release likely won't occur until around April 2024, and at that time we can consider using v4.6.0 as the version number. This would bring WRF's and MPAS's...

Leaving the issue open should be fine -- we can close it once we've released v4.6.0.

@WillTrojak If your changes work with older Jasper library versions (e.g., 1.900.X) and if they work when using the option that @weiwangncar mentioned to build an embedded copy of the...