Is your feature request related to a problem? Please describe.
Currently the translate test harness supports 4 different data layouts: "default," "microphysics," "mp3," and "shield" which are specified by setting one of those elements to True in the translate test variable declarations. All of them reflect different ad-hoc approaches to getting around the Fortran physics being j-blocked while GT4Py expects full 3D arrays, and they just accreted on as we tested more physics. Now that we have an actual solution in the "shield" format we can make it default, deprecate the unused ones, and turn this into a case-switch instead of having each format as a boolean toggle.
Describe the solution you'd like
- "shield" should be the default behavior
- the current default should be renamed "gfs" or "2d"
- "mp3" support should be dropped as the GFDL cloud microphysics data are now serialized like the other SHiELD data
- "microphysics" should also be dropped, tests using it should use the "gfs" format combined with a new switch to reverse fields along the k-axis
Describe alternatives you've considered
none at the moment
Additional context
Is your feature request related to a problem? Please describe.
Currently the translate test harness supports 4 different data layouts: "default," "microphysics," "mp3," and "shield" which are specified by setting one of those elements to True in the translate test variable declarations. All of them reflect different ad-hoc approaches to getting around the Fortran physics being j-blocked while GT4Py expects full 3D arrays, and they just accreted on as we tested more physics. Now that we have an actual solution in the "shield" format we can make it default, deprecate the unused ones, and turn this into a case-switch instead of having each format as a boolean toggle.
Describe the solution you'd like
Describe alternatives you've considered
none at the moment
Additional context