Skip to content
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

+Rescale driver timestep variables and step_MOM args #260

Merged

Conversation

Hallberg-NOAA
Copy link
Member

This pull request applies dimensional rescaling to units of [T ~> s] for a
number of timestep variables in all of the driver codes and for some of the
arguments to step_MOM and 6 other routines. With this change, the rescaling
increasingly takes place at the driver level, especially on lines converting
time_types to real variables. All answers and output are bitwise identical, but
the scaling for several arguments in publicly visible interfaces have changed.

The commits in this PR include:

  • 604cd0a33 +Rescaled real time arguments to step_MOM
  • 81284483f +Rescaled time variables in all MOM6 drivers

  Dimensionally rescaled the internal variables with units of time in all of the
top-level driver codes, from units of [s] to [T ~> s], including thing
valid_time arguments to the various drivers' versions of convert_IOB_to_fluxes.
All answers are bitwise identical in all cases that have been tested, although
it should be noted that the mct_cap and nuopc_cap are not regularly tested as
a part of the GFDL MOM6-examples test suite.  These changes only apply to
dimensional rescaling of timestep variables and the documentation of units.
  Rescaled the dimensions of real time arguments to step_MOM and several other
MOM routines that are called from the driver code, including shelf_calc_flux,
iceberg_forces, iceberg_fluxes and step_offline, along with the routines
offline_advection_ale and offline_advection_layer that are called subsequently.
As a part of the development of this commit, it was found that one of the
scaling factors for setting fluxes%ustar_berg was missing with the mct_cap, and
this has been corrected.  All answers and output are bitwise identical, but the
scaling for several arguments in publicly visible interfaces have changed.
@codecov
Copy link

codecov bot commented Dec 1, 2022

Codecov Report

Merging #260 (5c0d857) into dev/gfdl (c6c84c8) will not change coverage.
The diff coverage is 39.13%.

@@            Coverage Diff            @@
##           dev/gfdl     #260   +/-   ##
=========================================
  Coverage     37.12%   37.12%           
=========================================
  Files           263      263           
  Lines         73444    73444           
  Branches      13675    13675           
=========================================
  Hits          27268    27268           
  Misses        41151    41151           
  Partials       5025     5025           
Impacted Files Coverage Δ
...ig_src/drivers/solo_driver/MOM_surface_forcing.F90 24.42% <ø> (ø)
src/ice_shelf/MOM_ice_shelf.F90 0.00% <0.00%> (ø)
src/tracer/MOM_offline_main.F90 0.00% <0.00%> (ø)
src/core/MOM.F90 51.23% <28.57%> (ø)
config_src/drivers/solo_driver/MOM_driver.F90 51.04% <46.15%> (ø)
src/core/MOM_forcing_type.F90 42.17% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Hallberg-NOAA
Copy link
Member Author

Hallberg-NOAA commented Dec 15, 2022

Alper Altuntas has tested these changes with NCAR's test suite, and indicates (via e-mail) that there are no problems and that this PR is passing dimensional consistency testing for them.

@marshallward
Copy link
Member

Gaea regression: https://gitlab.gfdl.noaa.gov/ogrp/MOM6/-/pipelines/17708 ✔️

@marshallward marshallward merged commit 60c1d7b into NOAA-GFDL:dev/gfdl Dec 15, 2022
@Hallberg-NOAA Hallberg-NOAA deleted the rescale_driver_time_vars branch February 2, 2023 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants