COD Class Examples - Revision history

Wilkin: /* Getting the files */

2024-03-22T01:38:56Z

Getting the files

← Older revision		Revision as of 01:38, 22 March 2024
Line 199:		Line 199:
	* <span class="blue">grid_pcoord_estuary.nc</span> (the grid file)		* <span class="blue">grid_pcoord_estuary.nc</span> (the grid file)
	* <span class="blue">ana_fsobc.h, ana_m2obc.h</span> These impose tidal forcing at the eastern boundary.		* <span class="blue">ana_fsobc.h, ana_m2obc.h</span> These impose tidal forcing at the eastern boundary.
	* <span class="blue">~~rivers_pcoord_estuary~~.nc</span> This imposes the river inflow.		* <span class="blue">ana_psource.h</span> This imposes the river inflow.

	Copy these files from <span class="blue">/projects/dmcs_1/courses/cod</span> to your working directory.		Copy these files from <span class="blue">/projects/dmcs_1/courses/cod</span> to your working directory.

Wilkin: /* Getting the files */

2024-03-22T01:38:32Z

Getting the files

← Older revision		Revision as of 01:38, 22 March 2024
Line 198:		Line 198:
	* <span class="blue">roms_cod_estuary.in</span> which sets the run time parameters		* <span class="blue">roms_cod_estuary.in</span> which sets the run time parameters
	* <span class="blue">grid_pcoord_estuary.nc</span> (the grid file)		* <span class="blue">grid_pcoord_estuary.nc</span> (the grid file)
	* <span class="blue">~~tides_pcoord_estuary_S2~~.nc</span> (the boundary ~~tidal forcing harmonics file)~~		* <span class="blue">ana_fsobc.h, ana_m2obc.h</span> These impose tidal forcing at the eastern boundary.
	* <span class="blue">rivers_pcoord_estuary.nc</span> (river inflow .~~.. this is for later)~~		* <span class="blue">rivers_pcoord_estuary.nc</span> This imposes the river inflow.

	Copy these files from <span class="blue">/projects/dmcs_1/courses/cod</span> to your working directory.		Copy these files from <span class="blue">/projects/dmcs_1/courses/cod</span> to your working directory.

Wilkin: /* Experimental design */

2024-03-22T01:36:19Z

Experimental design

← Older revision		Revision as of 01:36, 22 March 2024
Line 182:		Line 182:

	There are 128 by 32 points in the horizontal. The grid, bottom depth and land/sea mask are set in a netcdf grid file		There are 128 by 32 points in the horizontal. The grid, bottom depth and land/sea mask are set in a netcdf grid file

			At the head of the estuary there is a steady river transport inflow with a value set using the USER parameters at run time in <span class="blue">roms_cod_estuary.in</span>.

	The open ocean boundary conditions are ''radiation'' on temperature, salinity and velocity on all 3 open boundaries. At the eastern boundary the inflow velocity is specified as the sum of 2 simple harmonic tidal constituents with amplitude and period set by the user at run time in file <span class="blue">roms_cod_estuary.in</span>.		The open ocean boundary conditions are ''radiation'' on temperature, salinity and velocity on all 3 open boundaries. At the eastern boundary the inflow velocity is specified as the sum of 2 simple harmonic tidal constituents with amplitude and period set by the user at run time in file <span class="blue">roms_cod_estuary.in</span>.

Wilkin: /* Experimental design */

2024-03-22T01:34:17Z

Experimental design

← Older revision		Revision as of 01:34, 22 March 2024
Line 183:		Line 183:
	There are 128 by 32 points in the horizontal. The grid, bottom depth and land/sea mask are set in a netcdf grid file		There are 128 by 32 points in the horizontal. The grid, bottom depth and land/sea mask are set in a netcdf grid file

	The open ocean boundary conditions are ''radiation'' on temperature, salinity and velocity on all 3 open boundaries. At the eastern boundary the inflow velocity is specified as the sum of 2 simple harmonic tidal constituents with amplitude and period set by the user at run time in file roms_cod_estuary.in.		The open ocean boundary conditions are ''radiation'' on temperature, salinity and velocity on all 3 open boundaries. At the eastern boundary the inflow velocity is specified as the sum of 2 simple harmonic tidal constituents with amplitude and period set by the user at run time in file <span class="blue">roms_cod_estuary.in</span>.

	The experiment starts from rest, i.e. u = v = zeta = 0. Uniform initial temperature and salinity are uniform based on values set in the <span class="blue">roms_cod_estuary.in</span> file.		The experiment starts from rest, i.e. u = v = zeta = 0. Uniform initial temperature and salinity are uniform based on values set in the <span class="blue">roms_cod_estuary.in</span> file.

Wilkin: /* Experimental design */

2024-03-22T01:33:08Z

Experimental design

← Older revision		Revision as of 01:33, 22 March 2024
Line 179:		Line 179:
	===Experimental design===		===Experimental design===

	This example ~~is designed to simulate~~ tidal variability in a simple ~~version of a~~ funnel shaped estuary. The estuary is triangular in width~~, with depth that~~ shallows linearly from 20 m the mouth to 5 m at the head along the ''thalweg''~~, which is the name given to~~ the line of local maximum depth along the estuary axis. There are shallow flanks along the coast on either side of the thalweg~~, and there~~ a simple ~~continental shelf~~ at the open ocean.		This example simulates tidal variability in a simple funnel shaped estuary. The estuary is triangular in width. Depth shallows linearly from 20 m the mouth to 5 m at the head along the ''thalweg'' (the line of local maximum depth along the estuary axis). There are shallow flanks along the coast on either side of the thalweg. There is a simple linear increase in depth at the open ocean.

	~~The model grid has~~ 128 by 32 points in the horizontal. The grid ~~coordinates~~, bottom depth and land/sea mask are set in a netcdf grid file		There are 128 by 32 points in the horizontal. The grid, bottom depth and land/sea mask are set in a netcdf grid file

	The open ocean boundary conditions are ''radiation'' on temperature, salinity and velocity on all 3 open boundaries. At the eastern boundary~~, sea level~~ is ~~set to vary~~ as a simple ~~tide~~ with ~~harmonics (frequency~~ and ~~amplitude) that are~~ set in ~~a netcdf tide forcing~~ file.		The open ocean boundary conditions are ''radiation'' on temperature, salinity and velocity on all 3 open boundaries. At the eastern boundary the inflow velocity is specified as the sum of 2 simple harmonic tidal constituents with amplitude and period set by the user at run time in file roms_cod_estuary.in.

	The experiment starts from rest, i.e. u = v = zeta = 0. ~~The~~ initial temperature and salinity are uniform based on values set in the <span class="blue">roms_cod_estuary.in</span> file.		The experiment starts from rest, i.e. u = v = zeta = 0. Uniform initial temperature and salinity are uniform based on values set in the <span class="blue">roms_cod_estuary.in</span> file.

	Since this grid is much larger than the previous 1D example, it will be desirable to run this in parallel using multiple cores on the ''Amarel'' cluster.		Since this grid is much larger than the previous 1D example, it will be desirable to run this in parallel using multiple cores on the ''Amarel'' cluster.

Wilkin: /* Getting the files */

2024-03-06T14:48:47Z

Getting the files

← Older revision		Revision as of 14:48, 6 March 2024
Line 204:		Line 204:

	# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY		# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY
	# Compile ROMS using the build script, e.g. ./build_roms.sh -j 4 (to use 4 processors at once while compiling)		# Compile ROMS using the build script, e.g. <span class="forestGreen">./build_roms.sh -j 4</span> (to use 4 processors at once while compiling)
	# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly		# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly
	# Also modify the srun command in <span class="forestGreen">job.sh</span> to use the correct roms.in file		# Also modify the srun command in <span class="forestGreen">job.sh</span> to use the correct roms.in file

Wilkin: /* Getting the files */

2024-03-06T14:48:11Z

Getting the files

← Older revision		Revision as of 14:48, 6 March 2024
Line 204:		Line 204:

	# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY		# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY
	# Compile ROMS using the build script, e.g. ./build_roms.sh - j 4 (to use 4 processors at once while compiling)		# Compile ROMS using the build script, e.g. ./build_roms.sh -j 4 (to use 4 processors at once while compiling)
	# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly		# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly
	# Also modify the srun command in <span class="forestGreen">job.sh</span> to use the correct roms.in file		# Also modify the srun command in <span class="forestGreen">job.sh</span> to use the correct roms.in file

Wilkin: /* Getting the files */

2024-03-06T14:47:56Z

Getting the files

← Older revision		Revision as of 14:47, 6 March 2024
Line 204:		Line 204:

	# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY		# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY
	# Compile ROMS using the build script		# Compile ROMS using the build script, e.g. ./build_roms.sh - j 4 (to use 4 processors at once while compiling)
	# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly		# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly
	# Also modify the srun command in <span class="forestGreen">job.sh</span> to use the correct roms.in file		# Also modify the srun command in <span class="forestGreen">job.sh</span> to use the correct roms.in file

Wilkin: /* Getting the files */

2024-03-06T14:46:49Z

Getting the files

← Older revision		Revision as of 14:46, 6 March 2024
Line 203:		Line 203:
	To run this example you need to follow similar steps to the COD_1DMIX example:		To run this example you need to follow similar steps to the COD_1DMIX example:

	# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span> to COD_ESTUARY		# In <span class="forestGreen">build_roms.sh</span>, set the <span class="sandyBrown">ROMS_APPLICATION</span>=COD_ESTUARY
	# Compile ROMS using the build script		# Compile ROMS using the build script
	# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly		# Note the NtileI and NtileJ values in roms_cod_estuary.in and edit your <span class="forestGreen">job.sh</span> file accordingly

Wilkin: /* Getting the files */

2024-03-06T14:46:18Z

Getting the files

← Older revision		Revision as of 14:46, 6 March 2024
Line 218:		Line 218:
	These have estuary lengths that are, respectively, twice and half the length of the regular grid.		These have estuary lengths that are, respectively, twice and half the length of the regular grid.

	To run this model with these alternative grids, you need to modify the input parameter <span class="sandyBrown">GRDNAME</span> in <span class="blue">~~roms_cod_hunter_estuary~~.in</span>.		To run this model with these alternative grids, you need to modify the input parameter <span class="sandyBrown">GRDNAME</span> in <span class="blue">roms_cod_estuary.in</span>.

	==Example COD_CTW==		==Example COD_CTW==