ADCIRC - Revision history

⚠️HamishBowman: /* Boundary node attribute preparation */

2021-01-06T01:17:12Z

Boundary node attribute preparation

← Older revision		Revision as of 01:17, 6 January 2021
Line 11:		Line 11:

	You can create a domain boundary polyline with r.contour. You can then output the domain boundary polyline either as Shapefiles with v.out.ogr, or as two column x,y ASCII data with the {{AddonCmd\|v.out.ascii.mat}} addon module for GRASS 6.		You can create a domain boundary polyline with r.contour. You can then output the domain boundary polyline either as Shapefiles with v.out.ogr, or as two column x,y ASCII data with the {{AddonCmd\|v.out.ascii.mat}} addon module for GRASS 6.

			==== Finding a coastline to use ====

			You can use the r.contour module with your DEM to create a level=0 shoreline.

			For those working in areas covering the USA, see the [[CUSP Coastline]] wiki page.

	==== Boundary node attribute preparation ====		==== Boundary node attribute preparation ====
Line 141:		Line 147:
	% then manually fix c2N2 -> 2N2		% then manually fix c2N2 -> 2N2
	</source>		</source>


	==== Creating Manning's n nodal attributes ====		==== Creating Manning's n nodal attributes ====

⚠️HamishBowman: /* Importing elevation or velocity reporting stations */

2021-01-06T01:07:14Z

Importing elevation or velocity reporting stations

@@ Line 172: / Line 172: @@
 With a little awk you can load in the elevation reporting stations for unit 61 with v.in.ascii.
-: example goes here
 ==== Visualizing sub-domains ====

⚠️HamishBowman: /* Importing unit 61, 62, 63, 64 results */

2020-07-03T23:01:24Z

Importing unit 61, 62, 63, 64 results

← Older revision		Revision as of 23:01, 3 July 2020
Line 212:		Line 212:
	==== Importing unit 61, 62, 63, 64 results ====		==== Importing unit 61, 62, 63, 64 results ====

	For this a useful approach is to import lat/lon coordinates of the nodes (as points) with the v.in.adcirc_grid AddOn module for GRASS 6, switch over to your target map projection in another GRASS location, pull in the points vector map from the lat/lon location, export them with v.out.ascii only keeping the projected points' x and y coordinate columns, tab separated (node order is preserved through all of this), this only needs to be done once.		For this a useful approach is to import lat/lon coordinates of the nodes (as points) with the v.in.adcirc_grid AddOn module for GRASS 6, switch over to your target map projection in another GRASS location, pull in the points vector map from the lat/lon location with v.proj, export them with v.out.ascii only keeping the projected points' x and y coordinate columns, tab separated (node order is preserved through all of this), this only needs to be done once.
	: Next using `ncdump` extract the 'z' or 'u' and 'v' values at each node point, and `paste` those (using the `paste` Unix command line tool) together with the x and y coordinates into a file ready for v.in.ascii or r.in.xyz. Repeat as necessary if the NetCDF output file includes multiple timsteps. All of this can be and should be scripted to save you time.		: Next using `ncdump` extract the 'z' or 'u' and 'v' values at each node point, and `paste` those (using the `paste` Unix command line tool) together with the x and y coordinates into a file ready for v.in.ascii or r.in.xyz. Repeat as necessary if the NetCDF output file includes multiple timsteps. All of this can be and should be scripted to save you time.

⚠️HamishBowman: /* Importing unit 61, 62, 63, 64 results */

2020-07-03T23:00:29Z

Importing unit 61, 62, 63, 64 results

← Older revision		Revision as of 23:00, 3 July 2020
Line 211:		Line 211:

	==== Importing unit 61, 62, 63, 64 results ====		==== Importing unit 61, 62, 63, 64 results ====

			For this a useful approach is to import lat/lon coordinates of the nodes (as points) with the v.in.adcirc_grid AddOn module for GRASS 6, switch over to your target map projection in another GRASS location, pull in the points vector map from the lat/lon location, export them with v.out.ascii only keeping the projected points' x and y coordinate columns, tab separated (node order is preserved through all of this), this only needs to be done once.
			: Next using `ncdump` extract the 'z' or 'u' and 'v' values at each node point, and `paste` those (using the `paste` Unix command line tool) together with the x and y coordinates into a file ready for v.in.ascii or r.in.xyz. Repeat as necessary if the NetCDF output file includes multiple timsteps. All of this can be and should be scripted to save you time.

	- addme: bash code + r.in.xyz + {{AddonCmd\|r.surf.nnbathy}}		- addme: bash code + r.in.xyz + {{AddonCmd\|r.surf.nnbathy}}

⚠️HamishBowman: /* Boundary node attribute preparation */

2019-08-20T00:39:57Z

Boundary node attribute preparation

← Older revision		Revision as of 00:39, 20 August 2019
Line 141:		Line 141:
	% then manually fix c2N2 -> 2N2		% then manually fix c2N2 -> 2N2
	</source>		</source>


			==== Creating Manning's n nodal attributes ====

			* See [[NLCD Land Cover]] for instructions on importing the base data

			You can load in your fort.14 mesh as points with <tt>v.in.adcirc_grid</tt>, then pull it into the Albers location with <tt>v.proj</tt>, then create a column of ''n'' values with '<tt>v.what.rast -i -p</tt>' that you can then form into a fort.13 file with UNIX command line power tools such as 'cut' and 'paste'.

	=== Post processing output data ===		=== Post processing output data ===

⚠️HamishBowman: /* OceanMesh2D */

2019-07-31T04:53:38Z

OceanMesh2D

← Older revision		Revision as of 04:53, 31 July 2019
Line 5:		Line 5:
	==== OceanMesh2D ====		==== OceanMesh2D ====

	[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with [http://adcirc.org ADCIRC] that performs an adaptive Delaunay triangulation, iteratively, providing fine mesh detail in areas of numerical complexity.		[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular finite element meshes]] suitable for use with [http://adcirc.org ADCIRC] that performs an adaptive Delaunay triangulation, iteratively, providing fine mesh detail in areas of numerical complexity.
	It likes to work in lat/lon coordinate system.		It likes to work in lat/lon coordinate system.

⚠️HamishBowman: /* Interfacing with the ADCIRC coastal ocean model */ +link

2019-07-31T04:51:43Z

Interfacing with the ADCIRC coastal ocean model: +link

← Older revision		Revision as of 04:51, 31 July 2019
Line 5:		Line 5:
	==== OceanMesh2D ====		==== OceanMesh2D ====

	[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with ADCIRC that performs an adaptive Delaunay triangulation, iteratively, providing fine mesh detail in areas of numerical complexity.		[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with [http://adcirc.org ADCIRC] that performs an adaptive Delaunay triangulation, iteratively, providing fine mesh detail in areas of numerical complexity.
	It likes to work in lat/lon coordinate system.		It likes to work in lat/lon coordinate system.

⚠️HamishBowman: /* OceanMesh2D */

2019-07-31T04:51:03Z

OceanMesh2D

← Older revision		Revision as of 04:51, 31 July 2019
Line 5:		Line 5:
	==== OceanMesh2D ====		==== OceanMesh2D ====

	[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with ADCIRC that performs an adaptive Delaunay ~~Triangulation~~, iteratively, providing fine mesh detail in areas of numerical complexity.		[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with ADCIRC that performs an adaptive Delaunay triangulation, iteratively, providing fine mesh detail in areas of numerical complexity.
	It likes to work in lat/lon coordinate system.		It likes to work in lat/lon coordinate system.

⚠️HamishBowman: /* OceanMesh2D */

2019-07-31T04:50:44Z

OceanMesh2D

← Older revision		Revision as of 04:50, 31 July 2019
Line 5:		Line 5:
	==== OceanMesh2D ====		==== OceanMesh2D ====

	[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with ADCIRC.		[https://github.com/CHLNDDEV/OceanMesh2D OceanMesh2D] is an open source (GPL3) generator of 2D [[Triangle_Mesh\|triangular meshes]] suitable for use with ADCIRC that performs an adaptive Delaunay Triangulation, iteratively, providing fine mesh detail in areas of numerical complexity.
	It likes to work in lat/lon coordinate system.		It likes to work in lat/lon coordinate system.

Neteler: +categories

2019-07-28T20:26:02Z

+categories

← Older revision		Revision as of 20:26, 28 July 2019
Line 208:		Line 208:

	{{AddonCmd\|d.barb}} addon module for GRASS 6 for rendering u,v vector arrows		{{AddonCmd\|d.barb}} addon module for GRASS 6 for rendering u,v vector arrows

			[[Category: Geodata]]
			[[Category: Import]]