GFDL to main 2025-04-23 #1664

marshallward · 2025-04-23T20:29:24Z

An Earth Day PR from GFDL 🌎, containing local contributions from the last few months.

This PR is expected to report a regression. Diagnostic checksum testing now includes a model timestamp, which is used to sort the output. This will prevent false negatives from reordering of post_data calls. But it will report a regression with main, which does not have the timestamps.

Features/Diagnostics

Bugfix/Refactor

Bug fix for subroutine write_energy when DT<2 NOAA-GFDL/MOM6#749: (@herrwang0)
Make REMAPPING_USE_OM4_SUBCELLS the default NOAA-GFDL/MOM6#758: (@awallcraft)
Move Regridding and Remapping Out of step_MOM_thermo NOAA-GFDL/MOM6#761: (@theresa-cordero)
Remove extra copy of compute_global_grid_integrals NOAA-GFDL/MOM6#762: (@Hallberg-NOAA)
Fix rescaling of internal tide debugging code NOAA-GFDL/MOM6#763: (@Hallberg-NOAA)
+Remove dyn_horgrid_type%Rad_Earth and ocean_grid_type%Rad_Earth NOAA-GFDL/MOM6#769: (@Hallberg-NOAA)
Bug fix related to directional internal wave drag NOAA-GFDL/MOM6#774: (@c2xu)
+Refactor MOM_opacity to replace hard-coded params NOAA-GFDL/MOM6#775: (@Hallberg-NOAA)
Refactor horizontally_average_field NOAA-GFDL/MOM6#776: (@Hallberg-NOAA)
+Refactor homogenize_field and revise its interface NOAA-GFDL/MOM6#777: (@Hallberg-NOAA)
+Refactor spatial means and rescale some global integrals NOAA-GFDL/MOM6#778: (@Hallberg-NOAA)
Bug fixes for sea surface height related diagnostics/checks NOAA-GFDL/MOM6#783: (@herrwang0)
Update MOM_wave_interface.F90 NOAA-GFDL/MOM6#784: (@Zeracesharon)
Move MOM_generic_tracer.F90 to config_src/external/GFDL_ocean_BGC with no changes NOAA-GFDL/MOM6#790: (@yichengt900)
Refactor ice shelf rescaling and diagnostic calcs NOAA-GFDL/MOM6#795: (@Hallberg-NOAA)
Forget to set descale in reproducing_sum_3d NOAA-GFDL/MOM6#797: (@yichengt900)
Refactor spherical_harmonics_forward NOAA-GFDL/MOM6#807: (@Hallberg-NOAA)
Fix interior obcs NOAA-GFDL/MOM6#814: (@kshedstrom)
Fix rotation in set_coupler_type_data NOAA-GFDL/MOM6#813: (@marshallward)
Correct bug in kappa shear viscosity with vertex shear option. NOAA-GFDL/MOM6#824: (@breichl)
+Refactor totalTandS to optionally work with scaled variables NOAA-GFDL/MOM6#827: (@Hallberg-NOAA)
Bugfix for mixing up Rho0 and rho_ref in Boussinesq PGF NOAA-GFDL/MOM6#837: (@herrwang0)
Alternative interface to EQN_OF_STATE="LINEAR" NOAA-GFDL/MOM6#842: (@awallcraft)
Move some parts of btstep() into subroutines NOAA-GFDL/MOM6#845: (@theresa-cordero)
Add INTERFACE_FILTER_DT_BUG NOAA-GFDL/MOM6#850: (@awallcraft)
Correct temperature and salinity mean diagnostics when using conservative/absolute NOAA-GFDL/MOM6#860: (@breichl)
Refactor MOM_barotropic for clearer OBCs NOAA-GFDL/MOM6#861: (@Hallberg-NOAA)
Horvisc: Reorder if-blocks in rescaled Kh NOAA-GFDL/MOM6#862: (@marshallward)
Move barotropic time stepping into btstep_timeloop NOAA-GFDL/MOM6#863: (@Hallberg-NOAA)
Add merged Coriolis arrays in MOM_barotropic NOAA-GFDL/MOM6#868: (@Hallberg-NOAA)
Initialize use_ice_shelf in ALE_regridding_and_remapping NOAA-GFDL/MOM6#872: (@JosephMouallem)
*Restore PFv parentheses for symmetry with FMAs NOAA-GFDL/MOM6#875: (@Hallberg-NOAA)
Refactor barotropic time stepping and OBC code NOAA-GFDL/MOM6#878: (@Hallberg-NOAA)
Zero out bt_pgf_u at OBC points NOAA-GFDL/MOM6#880: (@Hallberg-NOAA)
*Restore Cor_v parentheses for symmetry with FMAs NOAA-GFDL/MOM6#882: (@Hallberg-NOAA)

Infrastructure

Contributors:

Fix a bug with subroutine write_energy when using a DT<2. Otherwise, the energy outputs are written at wrong time steps. The reason was that time type divide is essentially a floor. So DT/2 = 0 if DT<2.

The subroutine compute_global_grid_integrals appeared in both the MOM_state_initialization and MOM_shared_initialization modules, but was only being called from the latter. This commit removes the extra copy in MOM_state_initialization. It also removes some unnecessary parentheses in the copy that is being retained, in part to facilitate the review of this commit. All answers are bitwise identical, and no publicly visible interfaces are altered.

In addition to REMAPPING_USE_OM4_SUBCELLS, for ALE remapping, there are several parameters of the form XXX_REMAPPING_USE_OM4_SUBCELLS, where XXX identifies the target, and they all currently default to True. To simplify setting them all to False, which is recommended, the defaults for the XXX versions is changed to the value of REMAPPING_USE_OM4_SUBCELLS. Answers are only changed if REMAPPING_USE_OM4_SUBCELLS is set to False and the default (now False) is used for one or more of the other parameters. In such cases the original behaviour can be recovered by explicitly setting the other parameters to True.

Removed two instances of `fail_if_missing=.true., default=0.` which are contradictory: a default value is meaningless if the parameter must be specified. I encountered this when adding the `defaults=` option to `get_param_real_array()`.

The `default=` optional argument to get_param() only provides a uniform value to initialize an array of reals. This commit adds the optional `defaults=` argument that must have the same length as the `values` argument. I've also added a few instances of this optional argument: - by adding the `initialize_thickness_param()` procedure, selected by `THICKNESS_CONFIG = "param"`. The procedure was based on the "uniform" method, and uses the parameter `THICKNESS_INIT_VALUES` which defaults to uniform values derived from `MAXIMUM_DEPTH` - the setting of MLD_EN_VALS in MOM_diabatic_driver.F90 which was previously using a work around to set defaults to 25, 2500, 250000 J/m2. - two vectors of 4 values in user/user_change_diffusivity.F90 There will be some doc file changes, but no answer changes.

Two latent heat constants are imported directly from FMS, which is built independently of MOM6. Previously, it was a safe assumption that both would be built with double precision, but this is no longer the case since FMS now supports both single and double precision. This could cause conflicts with mixed-precision builds. This patch converts the values from FMS-precision to MOM-precision. Single->double should not affect reproducibility since every single-precision number can be exactly represented in double precision. Double->single could affect reproducibility, but this is not an issue since MOM6 does not run in single precision.

* Inline harmonic analysis Important bug fix: 1) The Cholesky decomposition was operating on entries below the main diagonal of FtF, whereas in the accumulator of FtF, only entries along and above the main diagonal were calculated. In this revision, I modified HA_accum_FtF so that entries below the main diagonal are accumulated instead. 2) In the accumulator of FtSSH, the first entry for the mean (zero frequency) is moved out of the loop over different tidal constituents, so that it is not accumulated multiple times within a single time step. * Inline harmonic analysis Another bug fix: initial state added back to the mean state. * Inline harmonic analysis Minor update to HA_solver

* Tidal angular frequency has units [rad s-1] Tidal frequencies are always angular frequencies to simplify applying sine and cosine. These have MKS units [rad s-1] but they are all currently listed as [s-1]. Updated dOxygen comments for variables, e.g. [T-1 ~> s-1] becomes [rad T-1 ~> rad s-1]. Updated get_param units. e.g. units="s-1" becomes units="rad s-1". No answers are changed, but the logged parameter units are different. There are frequencies in MOM_internal_tides.F90 but these have not been updated because they may be specified incorrectly. They are used as if they are [T-1] but they are calculated as 2PI/period [rad T-1]. real, allocatable, dimension(:) :: frequency !< The frequency of each band [T-1 ~> s-1]. real :: period ! A tidal period read from namelist [T ~> s] ! The periods of the tidal constituents for internal tides raytracing call read_param(param_file, "TIDAL_PERIODS", periods) do fr=1,num_freq period = US%s_to_T*extract_real(periods, " ,", fr, 0.) CS%frequency(fr) = 8.0*atan(1.0)/period enddo All MOM6-examples cases have INTERNAL_TIDES=False and so can't resolve this issue. * fixed too-long line

* add diagnostic for Kd_Work related to the Kd_add part * also corrects some capitalization typos * fix id init --------- Co-authored-by: Raphael Dussin <[email protected]> Co-authored-by: Alistair Adcroft <[email protected]>

Changed the code to issue a fatal error message when WIND_CONFIG = "SCM_ideal_hurr", with the message including instructions on how to recover mathematically equivalent solutions, and eliminated the subroutine SCM_idealized_hurricane_wind_forcing() from the Idealized_hurricane module. The ocean_only MOM_parameter_doc files have also been modified to reflect that "SCM_ideal_hurr" is no longer a valid setting for WIND_CONFIG. All answers are bitwise identical in any cases that run, but some cases may fail during initialization with instructions on how to fix them.

Corrected a bug that causes ePBL column to set the wrong variable and then use an uninitialized variable when EPBL_ORIGINAL_PE_CALC is set to false. This bug was present when the EPBL_ORIGINAL_PE_CALC was first added on Sept. 30, 2016, but it was not detected because only the default case with EPBL_ORIGINAL_PE_CALC = True appears to being used or tested. Any runs that used this code with debugging compile options would have trapped it immediately. This will change answers when EPBL_ORIGINAL_PE_CALC is false.

Added the new runtime parameter EPBL_MLD_ITER_BUG that can be set to false to correct buggy logic that gives the wrong bounds for the next iteration when USE_MLD_ITERATION is true and successive guesses increase by exactly EPBL_MLD_TOLERANCE. By default all answers are bitwise identical, but there is a new runtime parameter in some MOM_parameter_doc files.

Added the ability to passively run ePBL_column twice in a diagnostic mode and then provide diagnostics of the differences in the diffusivities and boundary layer depths that are generated with the two options. This is controlled by the new runtime parameter EPBL_OPTIONS_DIFF, which is an integer that specifies which options to change or 0 (the default) to disable this capability. Associated with this are the new diagnostics ePBL_opt_diff_Kd_ePBL, ePBL_opt_maxdiff_Kd_ePBL and ePBL_opt_diff_h_ML, which only are registered when the differencing is enabled. For now, only changes associated with the settings of EPBL_ORIGINAL_PE_CALC and EPBL_ANSWER_DATE can be evaluated, but this list will grow as new options are added. As a part of these changes, there were some other reforms to the way that MOM_energetic_PBL handles diagnostics, with the 2-d and 3-d arrays changed from allocatable arrays with enduring memory commitments in the energetic_PBL_CS type into simple arrays in energetic_PBL, relying on the fact that compilers will be smart enough to avoid actually allocating this memory when it is unused to avoid expanding the overall memory requirements of MOM6. A number of allocate and deallocate calls were eliminated by these changes. In addition, explicit 'units=' descriptors were added to numerous register_diag_field calls to help identify inconsistent conversion factors. Also, the diagnostic of the number of boundary layer depth iterations was added to the ePBL_column_diags, which enabled the intent of the CS and G arguments to ePBL_column to be changed to intent(in). The unnecessary extra logic associated with the use of the OBL_converged variable in ePBL_column was eliminated, but the results are uneffected. Because the MOM_parameter_doc files were changing anyway, and because this commit is only a diagnostic change, about 6 spelling errors were corrected in ePBL parameter descriptions as a part of this commit. All answers are bitwise identical, but there is a new runtime parameter and there may be new diagnostics depending on the choice of a non-default value for that new parameter.

Added the new internal subroutine find_Kd_from_PE_chg inside of the MOM_energetic_PBL module to directly calculate an increment in the diapycnal diffusivity from an energy input. This can be used when ePBL does not convert released mean kinetic energy into turbulent kinetic energy (i.e., if MKE_TO_TKE_EFFIC = 0.) and is more efficient than the more general iterative approach. To preserve old answers, this new option is only enabled for the surface boundary layer when the new runtime parameter DIRECT_EPBL_MIXING_CALC is set to true. This new option can be tested passively by setting EPBL_OPTIONS_DIFF to 3 in a run that uses ePBL. By default all answers are bitwise identical, but there is a new runtime parameter in some of the MOM_parameter_doc files.

Add the option to do energetically consistent bottom boundary layer mixing with the new routine ePBL_BBL_column. ePBL_BBL_column is closely based on the surface-focused ePBL mixing in ePBL_column, but without adding convective instability driven mixing or mean-TKE driven mixing to avoid possible double-counting. This new option is enabled by setting the new runtime parameter EPBL_BBL_EFFIC to be positive. If both EPBL_BBL_EFFIC and BBL_EFFIC are set to positive values, there is a risk of double-counting, but this case is not being trapped for now. The changes include the addition of a new mandatory vertvisc_type argument to the publicly visible routine energetic_PBL. When this new ePBL bottom boundary layer mixing option is enabled, there are several new diagnostics available that are related to bottom boundary layer mixing. Several new checksum calls were also added with this new option when DEBUG = True. The MOM_parameter_doc files are altered by the addition of two new runtime parameters, and by the correction of several spelling errors in the descriptions of other ePBL parameters. By default, all answers are bitwise identical.

Added the ability to modify the bottom boundary layer TKE budget to account for an exponential decay of TKE away from the boundary and the fact that when the diffusivity is increased at an interface, it causes an increased buoyancy flux that varies linearly throughout a well mixed bottom boundary layer and through the layer above. This new capability is enabled by the new runtime parameter DECAY_ADJUSTED_BBL_TKE and is implemented via the new internal function exp_decay_TKE_adjust. In addition, this commit adds 9 bottom-boundary layer specific run-time parameters that are analogous to parameters that set the properties of the surface-driven mixing, and take their defaults from them, but can now be set independently for the bottom boundary layer. The inefficient option to use bisection to estimate the bottom boundary layer depth was eliminated, as it certain that it is not being used yet in any cases, and it should be deprecated for the estimation of the surface boundary layer. By default, all answers are bitwise identical, but there are up to 10 new runtime parameters that will appear in some MOM_parameter_doc files.

Added the new optional unscale argument to reproducing_sum() and reproducing_sum_EFP(). When this is used, the resulting real sum is restored to the same scaling as the input arrays, but when there is an EFP_type returned it is the same as it would have been had the input array been rescaled before it was passed in. All answers are bitwise identical, but thre is a new optional argument to a two publicly visible interfaces.

Added the new element RZL2_to_kg to the unit_scale_type for convenience when rescaling masses and other globally integrated variables. All answers are bitwise identical, but there is a new element in a transparent type.

Revised write_energy() and accumulate_net_input() to work more extensively in dimensionally rescaled variables by using the new unscale arguments to the reproducing_sum functions. As a result of these changes, 15 rescaling factors were eliminated or moved toward the end of write_energy(). All answers are bitwise identical.

Use reproducing_sum with unscale to calculate the global mass diagnostic, globally integrated ocean surface area, offline tracer transport residuals and in calculating the OBC inflow area in tidal_bay_set_OBC_data(). This change allows for the elimination or replacement of 6 rescaling factors and one added instance with a consistent conversion factor and diagnostic units occur on the same line. All answers are bitwise identical.

Co-authored-by: Robert Hallberg <[email protected]>

Correct a bug that G%gridLonT/G%gridLatT were not using global indexing in outputing extreme surface information.

Previously extreme surface message is triggered when `sea_lev` is smaller than or **equal** to ocean topography: sfc_state%sea_lev(i,j) <= -G%bathyT(i,j) - G%Z_ref The equality is innocuous for a non-zero minimum thickness (Angstrom/=0), but it can be problematic for true zero thickness. Besides, there is the fourth criterion in this check: sfc_state%sea_lev(i,j) + G%bathyT(i,j) + G%Z_ref < CS%bad_val_col_thick This is supposed to allow a user-specified tolerance (default=0.0), which should be a more stringent check when the tolerance is larger than zero. The equality from the first check contradicts this logic.

Fix a bug that sea surface height averaged over every dynamic time step (SSH_inst) is not outputted correctly.

* Update MOM_wave_interface.F90 The index at the interface has been changed from I-1 ->i+1 and J-1 -> j+1, which helps fixed model error in 3D simulations while keeping halo_size to 1. * Update MOM_wave_interface.F90 Corrected the index for thickness which fixed the issue of 3D wave coupled simulations while keeping the halo_size in thickness as 1

- The present code only tests BBL_EFFIC when deciding whether to set the bottom TKE and ustar, but this means they are all zero when EPBL_BBL_EFFIC is non-zero and BBL_EFFIC is zero. - Adds logic to also check EPBL_BBL_EFFIC, thereby allowing non-zero ustar and TKE for EPBL_BBL_EFFIC>0.0 - Fixed BBL_TKE diagnostic in EPBL that was not populated. - Will change answers when EPBL_BBL_EFFIC>0.0, but won't change answers in any of our existing configurations.

* Move MOM_generic_tracer with no changes Renames src/tracer/MOM_generic_tracer.F90 to config_src/external/GFDL_ocean_BGC/MOM_generic_tracer.F90 * Remove MOM_generic_tracer Git rm MOM_generic_tracer.F90 --------- Co-authored-by: Theresa Morrison <[email protected]>

Added missing factors to the conversion arguments in the register_diag_field calls for the diagnostics of the KPP non-local transport tendency and the net surface tracer fluxes, and corrected the dimensional scaling that is being applied to the KPP_Vt2 diagnostic as calculated in KPP_compute_BLD. All solutions are bitwise identical, but now output files with these 3 sets of KPP diagnostics are invariant to dimensional rescaling. This can be verified with the visc.nc file generated by the single_column/KPP test case in MOM6-examples. Whereas previously the diagnostics KPP_Vt2, KPP_QminusSW, KPP_netSalt, KPP_NLT_dTdt and KPP_NLT_dSdt in that file would change when dimensional rescaling was applied, now they do not. No output is changed unless dimensional rescaling is used.

The `default=` optional argument to get_param() only provides a uniform value to initialize an array of integers. This commit adds an optional `defaults=` argument to get_param_int_array(), doc_param_int_array() and log_param_int_array() to allow for the specification of an array of default values. These additions are analogous to what had previously been added for real arrays in github.com//pull/760. This commit also adds the new internal function int_array_string(), analogous to real_array_string(), in MOM_document. This differs slightly from its real array counterpart in that it only uses the syntax like `3*75` for lists of integers that are longer than we would use to specify dates and times or pairs of layout parameters, because "(0, 0)" seems more readily interpretable than "(2*0)". The new defaults argument is now used in the get_param calls for LAYOUT and IO_LAYOUT, and in setting the tidal reference dates. Several spelling errors in comments were also corrected in the files that were being edited. All answers are bitwise identical, but there are minor changes in many MOM_parameter_doc.layout files and some MOM_parameter_doc.all files.

jiandewang · 2025-05-08T13:58:07Z

this PR passed UFS regression test on all platforms. @sanAkel is checking all modified codes at this moment and I will click approval when he give me greenlight (plus no code modification is required from NCAR side)

sanAkel · 2025-05-09T02:32:33Z

this PR passed UFS regression test on all platforms. @sanAkel is checking all modified codes at this moment and I will click approval when he give me greenlight (plus no code modification is required from NCAR side)

@jiandewang I have no problems with anything! Please approve it. Thanks!

alperaltuntas · 2025-05-12T15:31:44Z

Another source of answer changes is NOAA-GFDL#784. We are happy with those changes but there seems to be more causes for answer changes. I am looking further...

alperaltuntas

I couldn’t pinpoint the exact cause of the remaining answer changes, but there’s strong evidence they’re related to the reorganization of certain routines, which likely affected compiler optimizations. I believe @Hallberg-NOAA mentioned something along those lines earlier. All the failing tests (which are Intel-only) pass when compiled with GNU, which supports this idea. Reverting merge commit bf35f31 also seems to restore answers for at least some tests, though I wasn’t able to identify exactly which part of that merge is responsible. Given all that, I think we're ready to approve this PR.

sanAkel · 2025-05-27T17:35:25Z

Any ETA on when this PR will be merged or what's (yet) to do?

marshallward · 2025-05-27T17:50:32Z

We tried to do a little forensics into the answer changes from NCAR, but couldn't come up with anything.

Given that everyone has reviewed and accepted the changes, I think it's safe to merge.

In mom-ocean#1664, src/tracer/MOM_generic_tracers.F90 was moved to config_src/external/GFDL_ocean_BGC/MOM_generic_tracer.F90. This was done to simplify COBALT v3 development. However, having MOM_generic_tracers.F90 in the generic_tracers codebase doesnt work when compiling generic_tracers as a library, so we maintain MOM_generic_tracer.F90 in the MOM6 codebase

In mom-ocean#1664, src/tracer/MOM_generic_tracer.F90 was moved to config_src/external/GFDL_ocean_BGC/MOM_generic_tracer.F90. This was done to simplify COBALT v3 development. However, having MOM_generic_tracer.F90 in the generic_tracers codebase doesnt work when compiling generic_tracers as a library, so we maintain MOM_generic_tracer.F90 in the MOM6 codebase.

In mom-ocean#1664, src/tracer/MOM_generic_tracer.F90 was moved to config_src/external/GFDL_ocean_BGC/MOM_generic_tracer.F90. This was done to simplify COBALT v3 development. However, having MOM_generic_tracer.F90 in the generic_tracers codebase doesnt work when compiling generic_tracers as a library, so we maintain MOM_generic_tracer.F90 in the MOM6 codebase. This reverts commits 2208dd7 and fcf5fff.

herrwang0 and others added 30 commits November 30, 2024 15:29

Bug fix for write_energy with short dt (#749)

51b4fb6

Fix a bug with subroutine write_energy when using a DT<2. Otherwise, the energy outputs are written at wrong time steps. The reason was that time type divide is essentially a floor. So DT/2 = 0 if DT<2.

Removed default for mandatory time scale in OBCs

cfb53f1

Removed two instances of `fail_if_missing=.true., default=0.` which are contradictory: a default value is meaningless if the parameter must be specified. I encountered this when adding the `defaults=` option to `get_param_real_array()`.

Refactor of vertical reconstruction adding six new schemes (#741)

00fdee4

add diagnostic for Kd_Work related to the Kd_add part (#765)

61e3bcf

* add diagnostic for Kd_Work related to the Kd_add part * also corrects some capitalization typos * fix id init --------- Co-authored-by: Raphael Dussin <[email protected]> Co-authored-by: Alistair Adcroft <[email protected]>

+Add RZL2_to_kg element to unit_scale_type

7060d51

Added the new element RZL2_to_kg to the unit_scale_type for convenience when rescaling masses and other globally integrated variables. All answers are bitwise identical, but there is a new element in a transparent type.

Bug fix related to directional internal wave drag (#774)

e6e0870

Co-authored-by: Robert Hallberg <[email protected]>

Fix indexing error in extract_surface_state

dae6226

Correct a bug that G%gridLonT/G%gridLatT were not using global indexing in outputing extreme surface information.

Recover diagnostic "SSH_inst"

9371bb0

Fix a bug that sea surface height averaged over every dynamic time step (SSH_inst) is not outputted correctly.

jiandewang approved these changes May 9, 2025

View reviewed changes

minghangli-uni mentioned this pull request May 15, 2025

Parameter updates for improved stability in 25 km configuration ACCESS-NRI/access-om3-configs#556

Merged

15 tasks

alperaltuntas approved these changes May 15, 2025

View reviewed changes

marshallward merged commit d76d728 into mom-ocean:main May 27, 2025

marshallward deleted the gfdl-to-main-2025-04-23 branch May 27, 2025 17:49

This was referenced Jun 2, 2025

v3: Update MOM6 to mom-ocean/mom6 as of 2025-Jun-02 GEOS-ESM/GEOS_OceanGridComp#101

Merged

v2: Update MOM6 to mom-ocean/mom6 as of 2025-Jun-02 GEOS-ESM/GEOS_OceanGridComp#102

Merged

dougiesquire mentioned this pull request Jul 9, 2025

Compiler for next MOM update - release 2025.08.000 ? ACCESS-NRI/access-om3-configs#632

Closed

jiandewang mentioned this pull request Aug 14, 2025

DEV-EMC-20250813 (convert missing value to zero in Stokes drift) #1675

Merged

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

GFDL to main 2025-04-23 #1664

GFDL to main 2025-04-23 #1664

Uh oh!

marshallward commented Apr 23, 2025

Uh oh!

jiandewang commented May 8, 2025

Uh oh!

sanAkel commented May 9, 2025

Uh oh!

alperaltuntas commented May 12, 2025

Uh oh!

alperaltuntas left a comment

Uh oh!

sanAkel commented May 27, 2025

Uh oh!

marshallward commented May 27, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants

GFDL to main 2025-04-23 #1664

GFDL to main 2025-04-23 #1664

Uh oh!

Conversation

marshallward commented Apr 23, 2025

Features/Diagnostics

Bugfix/Refactor

Infrastructure

Uh oh!

jiandewang commented May 8, 2025

Uh oh!

sanAkel commented May 9, 2025

Uh oh!

alperaltuntas commented May 12, 2025

Uh oh!

alperaltuntas left a comment

Choose a reason for hiding this comment

Uh oh!

sanAkel commented May 27, 2025

Uh oh!

marshallward commented May 27, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

20 participants