Add Boundary Tides to the Run

MOM6 can take tides data as a boundary condition in the regional domain. Many tides parameters are impacted by this and can be seen in case.process_forcings.

In our workflow, we take data from the TPXO tidal model and regrid onto our grid.

TPXO model data can be requested off of the TPXO website or is available on derecho.

The file paths of the tidal files can be passed into configure forcings as shown below with all wanted tidal constituents, like M2. There are three parameters in configure forcings and many parameters adjusted in MOM6.

case.configure_forcings(
    date_range = ["2020-01-01 00:00:00", "2020-01-09 00:00:00"],
    tidal_constituents = ['M2'],
    tpxo_elevation_filepath = "s3://crocodile-cesm/CrocoDash/data/tpxo/h_tpxo9.v1.zarr/",
    tpxo_velocity_filepath = "s3://crocodile-cesm/CrocoDash/data/tpxo/u_tpxo9.v1.zarr/"
)

---------------------------------------------------------------------------
NameError                                 Traceback (most recent call last)
Input In [1], in <cell line: 0>()
----> 1 case.configure_forcings(
      2     date_range = ["2020-01-01 00:00:00", "2020-01-09 00:00:00"],
      3     tidal_constituents = ['M2'],
      4     tpxo_elevation_filepath = "s3://crocodile-cesm/CrocoDash/data/tpxo/h_tpxo9.v1.zarr/",
      5     tpxo_velocity_filepath = "s3://crocodile-cesm/CrocoDash/data/tpxo/u_tpxo9.v1.zarr/"
      6 )

NameError: name 'case' is not defined