Model setup and output for 'Tidal conversion and dissipation at steep topography in a channel poleward of the critical latitude'
<p><strong>Data supplement to Hughes and Klymak 2019</strong></p> <p>Model input and output in a reduced form associated with the following paper:</p> <p><strong>Tidal conversion and dissipation at steep topography in a channel poleward of the critical latitude<br></strong><em>Journal of Physical Oceanography.</em> <a href="http://dx.doi.org/10.1175/JPO-D-18-0132.1">doi:10.1175/JPO-D-18-0132.1</a></p> <p><strong>Inputs</strong></p> <p>As described in Table 1 of the associated paper, there are three main sets of simulations. The input files for these sets are contained in their respective directories (`vary_width`, `vary_forcing`, and `vary_freq`). The python script that creates all of the necessary files is `gendata.py`. A fourth directory is titled `baroclinic_terms` and includes that simulation in which <em>u'</em> and <em>p'</em> are output at high temporal resolution.</p> <p>A key point regarding the input files is that for the vary width and vary forcing cases, a single simulation involves multiple channels. This lets me compile a single executable `mitgcmuv` with a Nx × Ny grid of 600 × 1280, which I divide up into the necessary number of channels by putting vertical walls in appropriate places. For the vary width cases, the 'narrow' simulations are all channels from 0.2 to 32 km and the 'wide' simulations are all wider channels. Once the simulation has run, I use netcdf tools (`ncks`) to extract the individual channels using the scripts in the `extract_scripts` directory.</p> <p>Most of the files in the `code` directories will be familiar to anyone that uses the MITgcm. An exception is the `energy_diagnostics_fill.F` (and `diagnostics_main_init.F` and `do_statevars_diags.F`, which have minor additions). The original, from `https://github.com/jklymak/MITgcmcode`, was modified slightly to suit this project.</p> <p><strong>Outputs</strong></p> <p>The results directory contains five subdirectories to be described in turn.</p> <p>Notes that in all cases, energy terms in the netCDF files do not include a factor of ρ. This was added in at the plotting stage.</p> <p>All simulations used Checkpoint67b and were run on Graham: https://docs.computecanada.ca/wiki/Graham.</p> <p><strong>vary_width</strong></p> <p>The majority of the files are of the form `obstacle_FFF_YY.nc` where `FFF` is $1000 ω/f$ and `YY` is the channel width in kilometres. These files contain the tidally averaged, depth-integrated energy diagnostics for the seventh tidal cycle at all points (<em>x, y</em>) within the energy control volume.</p> <p>There are also three files entitled `tophat_995_YY.nc`, which contain fields of <em>U</em>, <em>V</em>, and <em>T</em> (which gives density with α = 0.0002) at two levels. These fields are used as examples for weakly and strongly responding channels.</p> <p><br><strong>vary_forcing</strong></p> <p>These files are of the form `forcing_UU.nc` where `UU` is the deep-water tidal current amplitude <em>U_</em>0 in cm/s. They contain the same energy terms as for the vary width simulations.</p> <p><strong>vary_freq</strong></p> <p>These files are of the form `freq_FFF_fields.nc` and contain fields of <em>U</em>, <em>V</em>, and <em>T</em> at two levels. Energy terms are not included because the vary frequency simulations were only run to get estimates of the along-ridge wavelength.</p> <p><strong>baroclinic_terms</strong></p> <p>The single file within this directory contains <em>u'</em> and <em>p'</em> at a single <em>x</em> position every five minutes for four tidal cycles.</p> <p><strong>gaussian_26</strong></p> <p>This directory, named for its obstacle and width, contains <em>U</em>, <em>V</em>, and <em>T</em> at every grid point for a snapshot in time and another file with the corresponding snapshots of all energy terms.</p>
ShareScore
40/100
Overall dataset sharing score
Score breakdown
These five areas show where the dataset supports — or may limit — practical reuse.
- Stewardship
- 8
- Harmonization
- 4
- Access
- 16
- Reuse readiness
- 8
- Engagement
- 4