Fort.15 file - Revision history

Taylorgasher: /* Ramping Meteorological Forcing at Hot-Start */

2022-06-23T19:13:21Z

Ramping Meteorological Forcing at Hot-Start

← Older revision		Revision as of 15:13, 23 June 2022
Line 30:		Line 30:

	=== Ramping Meteorological Forcing at Hot-Start ===		=== Ramping Meteorological Forcing at Hot-Start ===
	It is generally best to [[~~ramp\|~~ramping]] in forcing terms to the model to avoid shocking the system, but ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Since it is common-place to initialize meteorological forcing at hotstart time, there is a special parameter to facilitate hotstart ramping of met. data. Let's say you run a 15-day tide-only run and output a hotstart file. Setting <br/>		It is generally best to [[ramping]] in forcing terms to the model to avoid shocking the system, but ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Since it is common-place to initialize meteorological forcing at hotstart time, there is a special parameter to facilitate hotstart ramping of met. data. Let's say you run a 15-day tide-only run and output a hotstart file. Setting <br/>
	<code>[[NRAMP]] = 8</code><br/>		<code>[[NRAMP]] = 8</code><br/>
	means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/>		means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/>

Taylorgasher: /* Ramping Meteorological Forcing at Hot-Start */

2021-11-16T15:05:25Z

Ramping Meteorological Forcing at Hot-Start

← Older revision		Revision as of 11:05, 16 November 2021
Line 30:		Line 30:

	=== Ramping Meteorological Forcing at Hot-Start ===		=== Ramping Meteorological Forcing at Hot-Start ===
	~~Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want~~ to ~~hotstart a simulation with meteorological~~ forcing~~. Initiating~~ the ~~hotstart simulation with full-strength met. forcing could apply a shock~~ to the system, ~~creating spurious waves. Therefore, it's best to ramp in the met. forcing. But,~~ ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Setting <br/>		It is generally best to [[ramp\|ramping]] in forcing terms to the model to avoid shocking the system, but ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Since it is common-place to initialize meteorological forcing at hotstart time, there is a special parameter to facilitate hotstart ramping of met. data. Let's say you run a 15-day tide-only run and output a hotstart file. Setting <br/>
	<code>[[NRAMP]] = 8</code><br/>		<code>[[NRAMP]] = 8</code><br/>
	means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/>		means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/>
	<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/>		<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP, DRAMPExtFlux, FluxSettlingTime, DRAMPIntFlux, DRAMPElev, DRAMPTip, DRAMPMete, DRAMPWRad, DRAMPUnMete</code><br/>
	What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).		What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).


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

Taylorgasher: /* Meteorological-Only Mode */

2021-02-12T23:43:11Z

Meteorological-Only Mode

← Older revision		Revision as of 19:43, 12 February 2021
Line 14:		Line 14:
	<code>[[NHASE]] = 0</code> <br/>		<code>[[NHASE]] = 0</code> <br/>
	<code>[[NHASV]] = 0</code> <br/>		<code>[[NHASV]] = 0</code> <br/>
	<code>[[~~NHAgE~~]] = 0</code> <br/>		<code>[[NHAGE]] = 0</code> <br/>
	<code>[[NHAGV]] = 0</code> <br/>		<code>[[NHAGV]] = 0</code> <br/>

Taylorgasher at 23:42, 12 February 2021

2021-02-12T23:42:37Z

← Older revision		Revision as of 19:42, 12 February 2021
Line 21:		Line 21:
	<code>[[NOUTGC]] = 0</code> <br/>		<code>[[NOUTGC]] = 0</code> <br/>

	while for barotropic or baroclinic 3D ADCIRC, also set:		while for barotropic or baroclinic 3D ADCIRC, also set: <br/>
	<code>[[I3DSD]] = 0</code> <br/>		<code>[[I3DSD]] = 0</code> <br/>
	<code>[[I3DSV]] = 0</code> <br/>		<code>[[I3DSV]] = 0</code> <br/>

Taylorgasher: updated met-only mode, per recommendations from Kyle Steffen

2021-02-12T23:40:49Z

updated met-only mode, per recommendations from Kyle Steffen

← Older revision		Revision as of 19:40, 12 February 2021
Line 6:		Line 6:
	== Tips and Tricks ==		== Tips and Tricks ==
	=== Meteorological-Only Mode ===		=== Meteorological-Only Mode ===
	By setting the following in the fort.15 file: <br/>		By turning off all ocean state-related outputting and disabling wave coupling, ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step). For typical 2D ADCIRC runs, this requires setting the following in the fort.15 file: <br/>
			<code>[[NOUTE]] = 0</code> <br/>
	<code>[[NOUTV]] = 0</code> <br/>		<code>[[NOUTV]] = 0</code> <br/>
			<code>[[NOUTGE]] = 0</code> <br/>
	<code>[[NOUTGV]] = 0</code> <br/>		<code>[[NOUTGV]] = 0</code> <br/>
	~~<code>[[NOUTE]] = 0</code> <br/>~~
	~~<code>[[NOUTGE]] = 0</code> <br/>~~
	<code>[[NHSTAR]] = 0</code> <br/>		<code>[[NHSTAR]] = 0</code> <br/>
	ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, ~~you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can~~ set <code>DT</code> ~~equal to the time interval you wish met. data to be output~~, ~~and then~~ set ~~the~~ <code>[[~~NSPOOLM~~]]</code> ~~and~~/or <code>[[~~NSPOOLGW~~]]</code> ~~(the local and global met. output intervals) to~~ <code>1</code> ~~(i.e. output every time step).~~		<code>[[NHASE]] = 0</code> <br/>
			<code>[[NHASV]] = 0</code> <br/>
			<code>[[NHAgE]] = 0</code> <br/>
			<code>[[NHAGV]] = 0</code> <br/>

			For passive scalar transport (<code>[[IM]] = 10</code>), also set: <br/>
			<code>[[NOUTC]] = 0</code> <br/>
			<code>[[NOUTGC]] = 0</code> <br/>

			while for barotropic or baroclinic 3D ADCIRC, also set:
			<code>[[I3DSD]] = 0</code> <br/>
			<code>[[I3DSV]] = 0</code> <br/>
			<code>[[I3DST]] = 0</code> <br/>
			<code>[[I3DGD]] = 0</code> <br/>
			<code>[[I3DGV]] = 0</code> <br/>
			<code>[[I3DGT]] = 0</code> <br/>

	=== Ramping Meteorological Forcing at Hot-Start ===		=== Ramping Meteorological Forcing at Hot-Start ===

Taylorgasher at 18:06, 7 February 2020

2020-02-07T18:06:02Z

← Older revision		Revision as of 14:06, 7 February 2020
Line 3:		Line 3:
	== File Format ==		== File Format ==
	See [[fort.15 file format]] for details.		See [[fort.15 file format]] for details.


	~~[[Category:input files]]~~



	== Tips and Tricks ==		== Tips and Tricks ==
Line 25:		Line 20:
	<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/>		<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/>
	What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).		What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).


			[[Category:input files]]

Taylorgasher: /* Tips and Tricks */ clean up formatting

2020-02-07T18:05:09Z

Tips and Tricks: clean up formatting

← Older revision		Revision as of 14:05, 7 February 2020
Line 11:		Line 11:
	== Tips and Tricks ==		== Tips and Tricks ==
	=== Meteorological-Only Mode ===		=== Meteorological-Only Mode ===
	By setting the following: <br/>		By setting the following in the fort.15 file: <br/>
	[[NOUTV]] = 0 <br/>		<code>[[NOUTV]] = 0</code> <br/>
	[[NOUTGV]] = 0 <br/>		<code>[[NOUTGV]] = 0</code> <br/>
	[[NOUTE]] = 0 <br/>		<code>[[NOUTE]] = 0</code> <br/>
	[[NOUTGE]] = 0 <br/>		<code>[[NOUTGE]] = 0</code> <br/>
	[[NHSTAR]] = 0 <br/>		<code>[[NHSTAR]] = 0</code> <br/>
	ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set the [[NSPOOLM]] and/or [[NSPOOLGW]] (the local and global met. output intervals) to 1 (i.e. output every time step).		ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing <code>DT</code>, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set <code>DT</code> equal to the time interval you wish met. data to be output, and then set the <code>[[NSPOOLM]]</code> and/or <code>[[NSPOOLGW]]</code> (the local and global met. output intervals) to <code>1</code> (i.e. output every time step).

	=== Ramping Meteorological Forcing at Hot-Start ===		=== Ramping Meteorological Forcing at Hot-Start ===
	Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want to hotstart a simulation with meteorological forcing. Initiating the hotstart simulation with full-strength met. forcing could apply a shock to the system, creating spurious waves. Therefore, it's best to ramp in the met. forcing. But, ramping parameters like [[DRAMP]] define the start of ramp time as being cold-start time. Setting <br/>		Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want to hotstart a simulation with meteorological forcing. Initiating the hotstart simulation with full-strength met. forcing could apply a shock to the system, creating spurious waves. Therefore, it's best to ramp in the met. forcing. But, ramping parameters like <code>[[DRAMP]]</code> define the start of ramp time as being cold-start time. Setting <br/>
	[[NRAMP]]=8<br/>		<code>[[NRAMP]] = 8</code><br/>
	means you can supply [[DRAMPUnMete]] ~~on the DRAMP line. This~~ is the number of ~~days~~ to ~~delay the~~ met. ~~ramp~~. Here's an example: <br/>		means you can supply <code>[[DRAMPUnMete]]</code>, which is the number of delays at which to start met. ramping, on the <code>DRAMP</code> line. Here's an example: <br/>
	5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete <br/>		<code>5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete</code><br/>
	What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).		What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).

Taylorgasher: /* Tips and Tricks */ added DRAMPUnMete

2020-02-07T17:55:27Z

Tips and Tricks: added DRAMPUnMete

← Older revision		Revision as of 13:55, 7 February 2020
Line 18:		Line 18:
	[[NHSTAR]] = 0 <br/>		[[NHSTAR]] = 0 <br/>
	ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set the [[NSPOOLM]] and/or [[NSPOOLGW]] (the local and global met. output intervals) to 1 (i.e. output every time step).		ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set the [[NSPOOLM]] and/or [[NSPOOLGW]] (the local and global met. output intervals) to 1 (i.e. output every time step).

			=== Ramping Meteorological Forcing at Hot-Start ===
			Let's say you run a 15-day tide-only run and output a hotstart file. Then, you want to hotstart a simulation with meteorological forcing. Initiating the hotstart simulation with full-strength met. forcing could apply a shock to the system, creating spurious waves. Therefore, it's best to ramp in the met. forcing. But, ramping parameters like [[DRAMP]] define the start of ramp time as being cold-start time. Setting <br/>
			[[NRAMP]]=8<br/>
			means you can supply [[DRAMPUnMete]] on the DRAMP line. This is the number of days to delay the met. ramp. Here's an example: <br/>
			5 0 0 0 0 0 0.5 0 15 ! DRAMP,DRAMPExtFlux,FluxSettlingTime,DRAMPIntFlux,DRAMPElev,DRAMPTip,DRAMPMete,DRAMPWRad,DRAMPUnMete <br/>
			What this says is that a 0.5-day ramp will be applied to the met. forcing, starting at run day 15.0 (the hotstart simulation's start time).

Taylorgasher: /* Meteorological-Only Mode */ cleaned up met.-only mode

2020-02-07T17:44:30Z

Meteorological-Only Mode: cleaned up met.-only mode

← Older revision		Revision as of 13:44, 7 February 2020
Line 11:		Line 11:
	== Tips and Tricks ==		== Tips and Tricks ==
	=== Meteorological-Only Mode ===		=== Meteorological-Only Mode ===
	By setting the following		By setting the following: <br/>
	[[NOUTV]] = 0		[[NOUTV]] = 0 <br/>
	[[NOUTGV]] = 0		[[NOUTGV]] = 0 <br/>
	[[NOUTE]] = 0		[[NOUTE]] = 0 <br/>
	[[NOUTGE]] = 0		[[NOUTGE]] = 0 <br/>
	[[NHSTAR]] = 0		[[NHSTAR]] = 0 <br/>
	ADCIRC will run in "met.-only" mode. In this mode, only routines ~~corresponding to~~ meteorological forcing are called, i.e. no water levels nor velocities are computed~~. This is a convenient way to quickly read in and write out meteorological data files~~. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set [[NSPOOLM]] and/or [[NSPOOLGW]] to 1 (output every time step).		ADCIRC will run in "met.-only" mode, a quick and convenient way to read in and write out meteorological data files. In this mode, only routines necessary for meteorological forcing are called, i.e. no water levels nor velocities are computed. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set the [[NSPOOLM]] and/or [[NSPOOLGW]] (the local and global met. output intervals) to 1 (i.e. output every time step).

Taylorgasher: added met-only mode notes

2020-02-07T17:08:47Z

added met-only mode notes

← Older revision		Revision as of 13:08, 7 February 2020
Line 6:		Line 6:

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



			== Tips and Tricks ==
			=== Meteorological-Only Mode ===
			By setting the following
			[[NOUTV]] = 0
			[[NOUTGV]] = 0
			[[NOUTE]] = 0
			[[NOUTGE]] = 0
			[[NHSTAR]] = 0
			ADCIRC will run in "met.-only" mode. In this mode, only routines corresponding to meteorological forcing are called, i.e. no water levels nor velocities are computed. This is a convenient way to quickly read in and write out meteorological data files. Note that by changing DT, you can speed up this "simulation". More specifically, since the only things being output are meteorological data, you can set DT equal to the time interval you wish met. data to be output, and then set [[NSPOOLM]] and/or [[NSPOOLGW]] to 1 (output every time step).