Fort.26 file - Revision history

Akauppila: /* Specifying Output */

2020-04-03T14:48:38Z

Specifying Output

← Older revision		Revision as of 10:48, 3 April 2020
Line 25:		Line 25:

	In this example, longitude/latitude coordinates are specified (space delimited without header) inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output files will be written to the PE subgrid directories that contain the output location points. Example contents of SpecLongLat.loc:		In this example, longitude/latitude coordinates are specified (space delimited without header) inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output files will be written to the PE subgrid directories that contain the output location points. Example contents of SpecLongLat.loc:

	-81.299940 29.898530		-81.299940 29.898530

Akauppila: /* Specifying Output */

2020-04-03T14:48:22Z

Specifying Output

← Older revision		Revision as of 10:48, 3 April 2020
Line 26:		Line 26:
	In this example, longitude/latitude coordinates are specified (space delimited without header) inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output files will be written to the PE subgrid directories that contain the output location points. Example contents of SpecLongLat.loc:		In this example, longitude/latitude coordinates are specified (space delimited without header) inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output files will be written to the PE subgrid directories that contain the output location points. Example contents of SpecLongLat.loc:
	-81.299940 29.898530		-81.299940 29.898530

	-81.303200 29.898450		-81.303200 29.898450

	-81.303440 29.893390		-81.303440 29.893390

	-81.300740 29.889340		-81.300740 29.889340

	-81.295050 29.890450		-81.295050 29.890450

Akauppila: /* Specifying Output */

2020-04-03T14:48:03Z

Specifying Output

← Older revision		Revision as of 10:48, 3 April 2020
Line 24:		Line 24:
	TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC		TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC

	In this example, longitude/latitude coordinates are specified inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output ~~file~~ will written to the PE subgrid ~~directory~~ that ~~contains~~ the output location ~~point~~.		In this example, longitude/latitude coordinates are specified (space delimited without header) inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output files will be written to the PE subgrid directories that contain the output location points. Example contents of SpecLongLat.loc:
			-81.299940 29.898530
			-81.303200 29.898450
			-81.303440 29.893390
			-81.300740 29.889340
			-81.295050 29.890450


	[[Category:input files]]		[[Category:input files]]
	[[Category:SWAN]]		[[Category:SWAN]]

Akauppila: /* Specifying Output */

2020-03-26T21:44:47Z

Specifying Output

← Older revision		Revision as of 17:44, 26 March 2020
Line 24:		Line 24:
	TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC		TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC

	In this example, longitude/latitude coordinates are specified inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. Note that the output file will written to the PE subgrid directory that contains the output location point.		In this example, longitude/latitude coordinates are specified inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. The six values after the date and decimal represent HHMMSS, not decimal day. Note that the output file will written to the PE subgrid directory that contains the output location point.


	[[Category:input files]]		[[Category:input files]]
	[[Category:SWAN]]		[[Category:SWAN]]

Akauppila at 21:43, 26 March 2020

2020-03-26T21:43:47Z

← Older revision		Revision as of 17:43, 26 March 2020
Line 6:		Line 6:

	See Casey Dietrich's great webpage on running ADCIRC+SWAN [https://ccht.ccee.ncsu.edu/swanadcirc/]		See Casey Dietrich's great webpage on running ADCIRC+SWAN [https://ccht.ccee.ncsu.edu/swanadcirc/]

			== Specifying Input ==

			Typically, SWAN+ADCIRC runs do not force wave initial conditions. However, the SWAN portion of the model may be able to accommodate SWAN 2D spectral input as a boundary condition, though this has not yet been tested/confirmed. The BOUNDSPEC command could allow the user to identify the fort.14 boundary nodestring for applying the spectra and then define the spectral parameters. The SWAN manual includes documentation on ASCII file format for SWAN spectra, which applies to both input/output spectra:
			[http://swanmodel.sourceforge.net/online_doc/swanuse/node50.html]

	== Specifying Output ==		== Specifying Output ==
Line 19:		Line 24:
	TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC		TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC

	In this example, longitude/latitude coordinates are specified inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00.		In this example, longitude/latitude coordinates are specified inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00. Note that the output file will written to the PE subgrid directory that contains the output location point.


	[[Category:input files]]		[[Category:input files]]
	[[Category:SWAN]]		[[Category:SWAN]]

Akauppila: /* Specifying Output */

2020-03-25T21:55:28Z

Specifying Output

← Older revision		Revision as of 17:55, 25 March 2020
Line 11:		Line 11:
	Timing of SWAN global output files (swan_HS.63, swan_TPS.63, swan_TMM10.63, and swan_DIR.63) derives from the timing specified for ADCIRC global meteorological output in the fort.15 run control file. Note that the SWAN calculation interval in the fort.26 must coincide with the ADCIRC meteorological output interval or SWAN output will not be written. The fort.26 allows for output of wave parameters or 1D/2D spectra at user-specified points. For SWAN+ADCIRC applications, point output specification will typically occur after the QUANTITY command and before the TEST command. First, the user defines a group of points (‘sname’ from the SWAN manual) by either identifying their x and y coordinates directly in the fort.26 or within a separate file (‘fname’ in SWAN parlance). Next, the SPECOUT command triggers spectral output, and/or TABLE triggers time series output of desired wave parameters and time steps. The following lines show an example from a fort.26 that requests both spectral output and wave parameter point time series:		Timing of SWAN global output files (swan_HS.63, swan_TPS.63, swan_TMM10.63, and swan_DIR.63) derives from the timing specified for ADCIRC global meteorological output in the fort.15 run control file. Note that the SWAN calculation interval in the fort.26 must coincide with the ADCIRC meteorological output interval or SWAN output will not be written. The fort.26 allows for output of wave parameters or 1D/2D spectra at user-specified points. For SWAN+ADCIRC applications, point output specification will typically occur after the QUANTITY command and before the TEST command. First, the user defines a group of points (‘sname’ from the SWAN manual) by either identifying their x and y coordinates directly in the fort.26 or within a separate file (‘fname’ in SWAN parlance). Next, the SPECOUT command triggers spectral output, and/or TABLE triggers time series output of desired wave parameters and time steps. The following lines show an example from a fort.26 that requests both spectral output and wave parameter point time series:

	POINTS 'SpecPts' File 'SpecLongLat.loc'		POINTS 'SpecPts' File 'SpecLongLat.loc'

	SPECout 'SpecPts' SPEC1D ABS '1DSpecOutABS' OUT 19640903.000000 1200 SEC		SPECout 'SpecPts' SPEC1D ABS '1DSpecOutABS' OUT 19640903.000000 1200 SEC

	SPECout 'SpecPts' SPEC2D ABS '2DSpecOutABS' OUT 19640903.000000 1200 SEC		SPECout 'SpecPts' SPEC2D ABS '2DSpecOutABS' OUT 19640903.000000 1200 SEC

	TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC		TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC

Akauppila: /* Specifying Output */

2020-03-25T21:55:01Z

Specifying Output

← Older revision		Revision as of 17:55, 25 March 2020
Line 10:		Line 10:

	Timing of SWAN global output files (swan_HS.63, swan_TPS.63, swan_TMM10.63, and swan_DIR.63) derives from the timing specified for ADCIRC global meteorological output in the fort.15 run control file. Note that the SWAN calculation interval in the fort.26 must coincide with the ADCIRC meteorological output interval or SWAN output will not be written. The fort.26 allows for output of wave parameters or 1D/2D spectra at user-specified points. For SWAN+ADCIRC applications, point output specification will typically occur after the QUANTITY command and before the TEST command. First, the user defines a group of points (‘sname’ from the SWAN manual) by either identifying their x and y coordinates directly in the fort.26 or within a separate file (‘fname’ in SWAN parlance). Next, the SPECOUT command triggers spectral output, and/or TABLE triggers time series output of desired wave parameters and time steps. The following lines show an example from a fort.26 that requests both spectral output and wave parameter point time series:		Timing of SWAN global output files (swan_HS.63, swan_TPS.63, swan_TMM10.63, and swan_DIR.63) derives from the timing specified for ADCIRC global meteorological output in the fort.15 run control file. Note that the SWAN calculation interval in the fort.26 must coincide with the ADCIRC meteorological output interval or SWAN output will not be written. The fort.26 allows for output of wave parameters or 1D/2D spectra at user-specified points. For SWAN+ADCIRC applications, point output specification will typically occur after the QUANTITY command and before the TEST command. First, the user defines a group of points (‘sname’ from the SWAN manual) by either identifying their x and y coordinates directly in the fort.26 or within a separate file (‘fname’ in SWAN parlance). Next, the SPECOUT command triggers spectral output, and/or TABLE triggers time series output of desired wave parameters and time steps. The following lines show an example from a fort.26 that requests both spectral output and wave parameter point time series:

	POINTS 'SpecPts' File 'SpecLongLat.loc'		POINTS 'SpecPts' File 'SpecLongLat.loc'
	SPECout 'SpecPts' SPEC1D ABS '1DSpecOutABS' OUT 19640903.000000 1200 SEC		SPECout 'SpecPts' SPEC1D ABS '1DSpecOutABS' OUT 19640903.000000 1200 SEC

Akauppila: /* File Format */

2020-03-25T21:54:39Z

File Format

← Older revision		Revision as of 17:54, 25 March 2020
Line 6:		Line 6:

	See Casey Dietrich's great webpage on running ADCIRC+SWAN [https://ccht.ccee.ncsu.edu/swanadcirc/]		See Casey Dietrich's great webpage on running ADCIRC+SWAN [https://ccht.ccee.ncsu.edu/swanadcirc/]

			== Specifying Output ==

			Timing of SWAN global output files (swan_HS.63, swan_TPS.63, swan_TMM10.63, and swan_DIR.63) derives from the timing specified for ADCIRC global meteorological output in the fort.15 run control file. Note that the SWAN calculation interval in the fort.26 must coincide with the ADCIRC meteorological output interval or SWAN output will not be written. The fort.26 allows for output of wave parameters or 1D/2D spectra at user-specified points. For SWAN+ADCIRC applications, point output specification will typically occur after the QUANTITY command and before the TEST command. First, the user defines a group of points (‘sname’ from the SWAN manual) by either identifying their x and y coordinates directly in the fort.26 or within a separate file (‘fname’ in SWAN parlance). Next, the SPECOUT command triggers spectral output, and/or TABLE triggers time series output of desired wave parameters and time steps. The following lines show an example from a fort.26 that requests both spectral output and wave parameter point time series:
			POINTS 'SpecPts' File 'SpecLongLat.loc'
			SPECout 'SpecPts' SPEC1D ABS '1DSpecOutABS' OUT 19640903.000000 1200 SEC
			SPECout 'SpecPts' SPEC2D ABS '2DSpecOutABS' OUT 19640903.000000 1200 SEC
			TABLE 'SpecPts' HEAD 'WavesOut.txt' HS TPS DIR OUT 19640903.000000 1200 SEC

			In this example, longitude/latitude coordinates are specified inside a file called SpecLongLat.loc; the two SPECOUT lines request 1D and 2D spectra written to 1DSpecOutABS and 2DSpecOutABS; and a table of Hs, Tps, and Dir will be written to WavesOut.txt every 1200 seconds beginning 9/3/1964 at 00:00:00.


	[[Category:input files]]		[[Category:input files]]
	[[Category:SWAN]]		[[Category:SWAN]]

Taylorgasher: categories

2019-05-20T11:51:30Z

Bblanton at 14:59, 12 February 2019

2019-02-12T14:59:11Z

← Older revision		Revision as of 10:59, 12 February 2019
Line 1:		Line 1:
	~~== Fort.26 file ==~~

	The fort.26 file contains the the SWAN runtime parameters as well as the "coupling" details between ADCIRC and SWAN. This file is required to run the ADCIRC+SWAN model. Note that the name "fort.26" is ADCIRC's name (and fortran unit number) for the SWAN input command file, typically named INPUT by default.		The fort.26 file contains the the SWAN runtime parameters as well as the "coupling" details between ADCIRC and SWAN. This file is required to run the ADCIRC+SWAN model. Note that the name "fort.26" is ADCIRC's name (and fortran unit number) for the SWAN input command file, typically named INPUT by default.

← Older revision		Revision as of 07:51, 20 May 2019
Line 6:		Line 6:

	See Casey Dietrich's great webpage on running ADCIRC+SWAN [https://ccht.ccee.ncsu.edu/swanadcirc/]		See Casey Dietrich's great webpage on running ADCIRC+SWAN [https://ccht.ccee.ncsu.edu/swanadcirc/]

			[[Category:input files]]
			[[Category:SWAN]]