Atmospheric forcing - Revision history

Yjzhang: /* Global sources */

2015-04-04T18:40:24Z

‎Global sources

Yjzhang: /* Global sources */

2015-04-04T18:39:38Z

‎Global sources

Yjzhang: /* Global sources */

2015-04-04T18:38:31Z

‎Global sources

Yjzhang: /* Global sources */

2015-04-04T18:32:29Z

‎Global sources

Yjzhang: /* Global sources */

2015-04-01T21:46:22Z

‎Global sources

Yjzhang at 21:41, 1 April 2015

2015-04-01T21:41:23Z

Yjzhang: /* Using NARR files for your simulation (North America only) */

2015-04-01T21:37:23Z

‎Using NARR files for your simulation (North America only)

Yjzhang: /* File description */

2015-04-01T21:35:44Z

‎File description

Yjzhang at 17:34, 18 December 2014

2014-12-18T17:34:36Z

Eli: /* A few details */

2014-10-24T01:17:45Z

‎A few details

← Older revision		Revision as of 18:40, 4 April 2015
Line 228:		Line 228:
	You can select a region and computational grid and temporal resolution etc and then submit the request.		You can select a region and computational grid and temporal resolution etc and then submit the request.

−	Once you have downloaded the (compressed) netcdf files, you can use [http://ccrm.vims.edu/yinglong/wiki_files/process_CFSR.tgz these matlab scripts] to process them into sflux_[air,rad,prc]*.nc. Note that the files are bundled differently for difference period (e.g. before and after Oct. 1, 2011) and so you may need to modify those scripts slightly.	+	Once you have downloaded the (compressed) netcdf files, you can use [http://ccrm.vims.edu/yinglong/wiki_files/process_CFSR.tgz these 3 matlab scripts] to process them into sflux_[air,rad,prc]*.nc. Note that the files are bundled differently for difference period (e.g. before and after Oct. 1, 2011) and so you may need to modify those scripts slightly.

@@ Line 205: / Line 205: @@
 ===NCEP's CFSR===
-[http://rda.ucar.edu This web site] has many global atmospheric model files, and a very useful source the NCEP's CFSR.
+[http://rda.ucar.edu This web site] has many global atmospheric model files, and a very useful source is the NCEP's CFSR.
 Note that you need to register yourself at the site first.

← Older revision		Revision as of 18:38, 4 April 2015
Line 218:		Line 218:

	In the new window, select output format as netcdf, and remember to restrict the vertical heights for each variable. Note that pressure is given at a different grid than other variables and so you'd do it separately.		In the new window, select output format as netcdf, and remember to restrict the vertical heights for each variable. Note that pressure is given at a different grid than other variables and so you'd do it separately.
		+	*Wind u,v at 10m
		+	*(Air) pressure reduced to MSL
		+	*(Air) temperature at 2m AGL
		+	*Specific humidity at 2m AGL
		+	*Downward longwave radiation flux at ground level
		+	*Downward shortwave radiation flux at ground level
		+	*Precipitation rate at ground level
		+
		+	You can select a region and computational grid and temporal resolution etc and then submit the request.
		+
		+	Once you have downloaded the (compressed) netcdf files, you can use [http://ccrm.vims.edu/yinglong/wiki_files/process_CFSR.tgz these matlab scripts] to process them into sflux_[air,rad,prc]*.nc. Note that the files are bundled differently for difference period (e.g. before and after Oct. 1, 2011) and so you may need to modify those scripts slightly.

@@ Line 203: / Line 203: @@
 ==Global sources==
-===UCAR's CFSR===
+===NCEP's CFSR===
-[http://rda.ucar.edu UCAR web] site has many global atmospheric model files
+[http://rda.ucar.edu This web site] has many global atmospheric model files, and a very useful source the NCEP's CFSR.

← Older revision		Revision as of 21:46, 1 April 2015
Line 203:		Line 203:

	==Global sources==		==Global sources==
−	===~~NCEP~~'s CFSR===	+	===UCAR's CFSR===
		+
		+	[http://rda.ucar.edu UCAR web] site has many global atmospheric model files

← Older revision		Revision as of 21:41, 1 April 2015
Line 201:		Line 201:
	}		}
	</code>		</code>
		+
		+	==Global sources==
		+	===NCEP's CFSR===

@@ Line 52: / Line 52: @@
 First, make sure the  [http://ccrm.vims.edu/yinglong/wiki_files/narr.ll NARR grid] covers your hgrid.ll.
 In your run directory, mkdir sflux and inside it, create symbolic links to the NARR files. e.g., if you run starts from June 10, 2004 and ends June 20, 2004, then
@@ Line 64: / Line 66: @@
 Don't forget to update sflux_inputs.txt also.
 ==Preparing your own sflux inputs==

@@ Line 25: / Line 25: @@
 In SCHISM, atmoserpic forcings include wind, air pressure and temperature, precipitation, humidity and longwave and shortwave fluxes. These are specified in the netcdf files inside sflux/ dir, and conform to the [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.0/cf-conventions.html NetCDF Climate and Forecast (CF) Metadata Convention 1.0].
-There are 4 types of files in sflux/dir; see [http://www.stccmop.org/CORIE/modeling/selfe/NARR/narr.html this site] for sample files.
+There are 4 types of files in sflux/dir; see [http://ccrm.vims.edu/yinglong/wiki_files/NARR/ this site] for sample files.
 <OL>

@@ Line 1: / Line 1: @@
 ==Theory==
-[http://ccrm.vims.edu/yinglong/wiki_files/HeatExchange-Theory.pdf Here] is some info about the heat exchange module inside SELFE, based on Dr. Mike Zuluaf's slides.
+[http://ccrm.vims.edu/yinglong/wiki_files/HeatExchange-Theory.pdf Here] is some info about the heat exchange module inside SCHISM, based on Dr. Mike Zuluaf's slides.
 ==Summary of inputs==
@@ Line 23: / Line 23: @@
 ==File description==
-In SELFE, atmoserpic forcings include wind, air pressure and temperature, precipitation, humidity and longwave and shortwave fluxes. These are specified in the netcdf files inside sflux/ dir, and conform to the [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.0/cf-conventions.html NetCDF Climate and Forecast (CF) Metadata Convention 1.0].
+In SCHISM, atmoserpic forcings include wind, air pressure and temperature, precipitation, humidity and longwave and shortwave fluxes. These are specified in the netcdf files inside sflux/ dir, and conform to the [http://cf-pcmdi.llnl.gov/documents/cf-conventions/1.0/cf-conventions.html NetCDF Climate and Forecast (CF) Metadata Convention 1.0].
 There are 4 types of files in sflux/dir; see [http://www.stccmop.org/CORIE/modeling/selfe/NARR/narr.html this site] for sample files.
@@ Line 47: / Line 47: @@
 Using air as an example, it is assumed that the file sflux_air_2.001.nc is more resolved or accurate than sflux_air_1.001.nc. The two will be blended in the model in a way that favors the _2 file. This blending of the fields is only adjustable in the fortran as described in notes below. The default in sflux_9c.F90 is a 99:1 blend of the _2_ file to the _1_ file.
-As was remarked above, the files are arranged temporally in a stack of files starting with ".001". Given the sequence of forecasting and analysis, it is common for atmospheric files to overlap. A file might begin with a brief period of data assimilation plus a few days of forecast. SELFE assumes that a new file indicates the injection of information, so when it encounters overlap, it advances to the later file.
+As was remarked above, the files are arranged temporally in a stack of files starting with ".001". Given the sequence of forecasting and analysis, it is common for atmospheric files to overlap. A file might begin with a brief period of data assimilation plus a few days of forecast. SCHISM assumes that a new file indicates the injection of information, so when it encounters overlap, it advances to the later file.
 ==Using NARR files for your simulation (North America only)==
@@ Line 61: / Line 61: @@
 sflux_air_1.012.nc --> narr_air.2004_06_21.nc (extra day to account for time zone difference)<br/>
-Similarly for sflux_rad_*.nc and sflux_prc_*.nc. As described above, the number "1" after "air_" denotes the first data set used, with the second set taking priority; you can use up to 2 sets in SELFE (which combines them with some given weights set in sflux_subs.F90); here you only use 1 set.
+Similarly for sflux_rad_*.nc and sflux_prc_*.nc. As described above, the number "1" after "air_" denotes the first data set used, with the second set taking priority; you can use up to 2 sets in SCHISM (which combines them with some given weights set in sflux_subs.F90); here you only use 1 set.
 Don't forget to update sflux_inputs.txt also.
@@ Line 79: / Line 79: @@
 i.e. lat/lon
-'''watertype.gr3:''' 6 is clear water, 7 is muddiest. Search in selfe_init.F90 for watertype.
+'''watertype.gr3:''' 6 is clear water, 7 is muddiest. Search in schism_init.F90 for watertype.
 ==A few details==

@@ Line 82: / Line 82: @@
 ==A few details==
-Below is from sflux_9c.F90; search for "Joseph Z" near the beginning of the code for up to date info.
+Below are some details from sflux_9c.F90, near the beginning of the code.
-*Of all attributes in nc file, only 'base_date' is required;
+* Of all attributes in nc file, only 'base_date' is required;
-* air, rad and prc each can have up to 2 sources;
+* The grids for air, rad and prc can be different (but must be the same within each type and each source). Additional requirements for the structured grid in .nc: [lon,lat](nx,ny) give x,y coord., nx is # of pts in x. Suppose a node in the grid is given by (i,j) (1<=i<=nx), then the quad (i,j), (i+1,j), (i+1,j+1,i,j+1) must be along counter-clockwise direction;
-* grids for air, rad and prc can be different (but must be the same within each type and each source). Additional requirements for the structured grid in .nc: [lon,lat](nx,ny) give x,y coord., nx is # of pts in x. Suppose a node in the grid is given by (i,j) (1<=i<=nx), then the quad (i,j), (i+1,j), (i+1,j+1,i,j+1) must be along counter-clockwise direction;
+* Search for "relative_weight" (inside netcdf_io) to change relative weights of the 2 sources for air, rad and prc if needed. All weights must > 0!
 * in case of 2 sources/grids for a variable, use "1" as larger grid (i.e. encompassing hgrid.ll) and "2" as smaller grid. The code will calculate weights associated with the 2 grids, and if some nodes in hgrid.ll fall outside grid "2" the interpolation will be done on grid "1" only (see combine_sflux_data, in particular, bad_node_ based on area coordinates outside [0,1]). Both grids must start from stack  1 and have same # of stacks for each variable. However, within each nc file # of time steps can vary;
 *air_1_max_window_hours (etc) are set in netcdf_io to define the max. time stamp (offset from start time in each) within each nc file. Besides those in netcdf_io,   max_file_times (max. # of time records in each nc file) in routine get_times_etc ()  may need to be adjusted as well.