How to visualize WRF-Fire output in VAPOR - Revision history

Adamko: /* Directions */

2016-05-04T19:44:41Z

Directions

← Older revision		Revision as of 19:44, 4 May 2016
Line 15:		Line 15:
	* If the visualization computer is different from the computer where you run WRF-Fire, transfer the '''wrfout''' file to the visualization computer		* If the visualization computer is different from the computer where you run WRF-Fire, transfer the '''wrfout''' file to the visualization computer
	* Start VAPOR by clicking on its icon or '''vaporgui''' from the command line		* Start VAPOR by clicking on its icon or '''vaporgui''' from the command line
	* In the GUI, click "Data" on the top menu bar, then "Import WRF output files into current session" or "Data", then "Import data into current session" then select "WRF_ARW" from the submenu, and navigate to your '''wrfout''' file. In the black right panel, you should see an empty wireframe box from the top.		* In the GUI, click "Data" on the top menu bar, then "Import WRF output files into current session" or "Data", then "Import data into current session" then select "WRF_ARW" from the submenu, and navigate to your '''wrfout''' file.
			[[File:Vapor_WRF_import.png]]

			In the black right panel, you should see an empty wireframe box from the top.
	* Click the "Flow" tab, check the box "Instance 1", click "OK" on a warning about flow lines below zero. Select "Refinement" 2. You should see a picture like this (the starting points of the flow lines are picked randomly so they are different in every session):		* Click the "Flow" tab, check the box "Instance 1", click "OK" on a warning about flow lines below zero. Select "Refinement" 2. You should see a picture like this (the starting points of the flow lines are picked randomly so they are different in every session):
	[[File:Vapor-flowlines-window.png\|600px]]		[[File:Vapor-flowlines-window.png\|600px]]

Adamko: /* Directions */

2016-05-04T19:17:15Z

Directions

← Older revision		Revision as of 19:17, 4 May 2016
Line 14:		Line 14:
	* [[How to run WRF-Fire\|Run WRF-Fire]]. The pictures below are from the "hill" ideal run in WRF-Fire.		* [[How to run WRF-Fire\|Run WRF-Fire]]. The pictures below are from the "hill" ideal run in WRF-Fire.
	* If the visualization computer is different from the computer where you run WRF-Fire, transfer the '''wrfout''' file to the visualization computer		* If the visualization computer is different from the computer where you run WRF-Fire, transfer the '''wrfout''' file to the visualization computer
	* Convert the '''wrfout''' file for use with VAPOR: run from the command line
	** '''wrfvdfcreate yourwrfoutfile yourwdffile.vdf'''
	** '''wrf2vdf yourwdffile.vdf yourwrfoutfile'''
	* Start VAPOR by clicking on its icon or '''vaporgui''' from the command line		* Start VAPOR by clicking on its icon or '''vaporgui''' from the command line
	* In the GUI, click "Data" on the top menu bar, then "~~load dataset in the~~ current session", and navigate to ~~the~~ '''~~yourwdffile.vdf~~''' ~~you have just created~~. In the black right panel, you should see an empty wireframe box from the top.		* In the GUI, click "Data" on the top menu bar, then "Import WRF output files into current session" or "Data", then "Import data into current session" then select "WRF_ARW" from the submenu, and navigate to your '''wrfout''' file. In the black right panel, you should see an empty wireframe box from the top.
	* Click the "Flow" tab, check the box "Instance 1", click "OK" on a warning about flow lines below zero. Select "Refinement" 2. You should see a picture like this (the starting points of the flow lines are picked randomly so they are different in every session):		* Click the "Flow" tab, check the box "Instance 1", click "OK" on a warning about flow lines below zero. Select "Refinement" 2. You should see a picture like this (the starting points of the flow lines are picked randomly so they are different in every session):
	[[File:Vapor-flowlines-window.png\|600px]]		[[File:Vapor-flowlines-window.png\|600px]]

Adamko: /* Prerequistes */

2016-05-04T19:13:00Z

Prerequistes

← Older revision		Revision as of 19:13, 4 May 2016
Line 4:		Line 4:
	* [[How to run WRF-Fire\|A working installation]] of [[WRF-Fire]], possibly on a remote supercomputer or a cluster.		* [[How to run WRF-Fire\|A working installation]] of [[WRF-Fire]], possibly on a remote supercomputer or a cluster.
	* A visualization computer with a [http://www.vapor.ucar.edu/docs/install/index.php?id=depbin decent graphics card and drivers] (hardware accelerated [[wikipedia:OpenGL\|OpenGL]] required), 3 button mouse.		* A visualization computer with a [http://www.vapor.ucar.edu/docs/install/index.php?id=depbin decent graphics card and drivers] (hardware accelerated [[wikipedia:OpenGL\|OpenGL]] required), 3 button mouse.
	* [http://www.vapor.ucar.edu Download] and install [[VAPOR]] ('''for idealized cases we recommend using Vapor version 2.0.0 ~~or earlier~~''' as newer versions have problems with processing wrfoutput data without valid latitude and longitude provided in degrees)		* [http://www.vapor.ucar.edu Download] and install [[VAPOR]] ('''for idealized cases we recommend using Vapor version 2.0.0''' as newer versions have problems with processing wrfoutput data without valid latitude and longitude provided in degrees)
	** Read [http://www.vapor.ucar.edu/start Getting started with VAPOR] first.		** Read [http://www.vapor.ucar.edu/start Getting started with VAPOR] first.
	** On a Mac, run the installation package, then add to your path '''/Applications/VAPOR.app/Contents/MacOS'''		** On a Mac, run the installation package, then add to your path '''/Applications/VAPOR.app/Contents/MacOS'''

Adamko: /* Prerequistes */

2016-05-04T19:06:07Z

Prerequistes

← Older revision		Revision as of 19:06, 4 May 2016
Line 4:		Line 4:
	* [[How to run WRF-Fire\|A working installation]] of [[WRF-Fire]], possibly on a remote supercomputer or a cluster.		* [[How to run WRF-Fire\|A working installation]] of [[WRF-Fire]], possibly on a remote supercomputer or a cluster.
	* A visualization computer with a [http://www.vapor.ucar.edu/docs/install/index.php?id=depbin decent graphics card and drivers] (hardware accelerated [[wikipedia:OpenGL\|OpenGL]] required), 3 button mouse.		* A visualization computer with a [http://www.vapor.ucar.edu/docs/install/index.php?id=depbin decent graphics card and drivers] (hardware accelerated [[wikipedia:OpenGL\|OpenGL]] required), 3 button mouse.
	* [http://www.vapor.ucar.edu Download] and install [[VAPOR]]		* [http://www.vapor.ucar.edu Download] and install [[VAPOR]] ('''for idealized cases we recommend using Vapor version 2.0.0 or earlier''' as newer versions have problems with processing wrfoutput data without valid latitude and longitude provided in degrees)
	** Read [http://www.vapor.ucar.edu/start Getting started with VAPOR] first.		** Read [http://www.vapor.ucar.edu/start Getting started with VAPOR] first.
	** On a Mac, run the installation package, then add to your path '''/Applications/VAPOR.app/Contents/MacOS'''		** On a Mac, run the installation package, then add to your path '''/Applications/VAPOR.app/Contents/MacOS'''

Jmandel: {{users guide}}

2011-08-02T05:18:02Z

← Older revision		Revision as of 05:18, 2 August 2011
Line 1:		Line 1:
			{{users guide}}
	==Prerequistes==		==Prerequistes==

Sousedik at 19:48, 21 September 2010

2010-09-21T19:48:37Z

← Older revision		Revision as of 19:48, 21 September 2010
Line 44:		Line 44:
	The selection of variables can be done in two ways:		The selection of variables can be done in two ways:
	* create new NetCDF file with these variables by ("-O" switch overrides the file and if some variable is not available, it will simply skip it)		* create new NetCDF file with these variables by ("-O" switch overrides the file and if some variable is not available, it will simply skip it)
	ncks -v U,V,W,QVAPOR,P,T,GRNHFX,AVG_FUEL_FRAC,PH,PHB,UF,VF,HGT,ZSF,Times wrfout -O file		ncks -v U,V,W,QVAPOR,P,T,GRNHFX,AVG_FUEL_FRAC,PH,PHB,ROS,UF,VF,HGT,ZSF,Times wrfout -O file
	wrfvdfcreate file file.vdf		wrfvdfcreate file file.vdf
	wrf2vdf file.vdf file		wrf2vdf file.vdf file
	The wrfvdfcreate command creates a vdf metafile with a description of the data for Vapor and wrf2vdf created a directory file_data with the actual data.		The wrfvdfcreate command creates a vdf metafile with a description of the data for Vapor and wrf2vdf created a directory file_data with the actual data.
	* the other option is to specify the variables in the wrfvdfcreate call, i.e., run		* the other option is to specify the variables in the wrfvdfcreate call, i.e., run something like
	wrfvdfcreate -vars3d U:V:W:QVAPOR -vars2d GRNHFX:AVG_FUEL_FRAC wrfout file.vdf		wrfvdfcreate -vars3d U:V:W:QVAPOR -vars2d GRNHFX:AVG_FUEL_FRAC wrfout file.vdf
	wrf2vdf file.vdf wrfout		wrf2vdf file.vdf wrfout

Jmandel: /* More advanced visualization */ typo

2010-09-21T13:05:22Z

More advanced visualization: typo

← Older revision		Revision as of 13:05, 21 September 2010
Line 43:		Line 43:
	* If the wrfout file contains all WRF variables, which is way more than we need at this point, it is convenient to select only the desired variables: U,V,W for wind streamlines, GRNHFX for fire, QVAPOR for smoke and AVG_FUEL_FRAC for the burned area.		* If the wrfout file contains all WRF variables, which is way more than we need at this point, it is convenient to select only the desired variables: U,V,W for wind streamlines, GRNHFX for fire, QVAPOR for smoke and AVG_FUEL_FRAC for the burned area.
	The selection of variables can be done in two ways:		The selection of variables can be done in two ways:
	* create new NetCDF file with ~~this~~ variables by ("-O" switch overrides the file and if some variable is not available, simply skip it)		* create new NetCDF file with these variables by ("-O" switch overrides the file and if some variable is not available, it will simply skip it)
	ncks -v U,V,W,QVAPOR,P,T,GRNHFX,AVG_FUEL_FRAC,PH,PHB,UF,VF,HGT,ZSF,Times wrfout -O file		ncks -v U,V,W,QVAPOR,P,T,GRNHFX,AVG_FUEL_FRAC,PH,PHB,UF,VF,HGT,ZSF,Times wrfout -O file
	wrfvdfcreate file file.vdf		wrfvdfcreate file file.vdf

Sousedik at 06:37, 21 September 2010

2010-09-21T06:37:12Z

← Older revision		Revision as of 06:37, 21 September 2010
Line 44:		Line 44:
	The selection of variables can be done in two ways:		The selection of variables can be done in two ways:
	* create new NetCDF file with this variables by ("-O" switch overrides the file and if some variable is not available, simply skip it)		* create new NetCDF file with this variables by ("-O" switch overrides the file and if some variable is not available, simply skip it)
	ncks -v U,V,W,QVAPOR,GRNHFX,AVG_FUEL_FRAC,PH,PHB,Times wrfout -O file		ncks -v U,V,W,QVAPOR,P,T,GRNHFX,AVG_FUEL_FRAC,PH,PHB,UF,VF,HGT,ZSF,Times wrfout -O file
	wrfvdfcreate file file.vdf		wrfvdfcreate file file.vdf
	wrf2vdf file.vdf file		wrf2vdf file.vdf file

Jbeezley: changed information on compiling for large file support

2010-09-08T17:41:34Z

changed information on compiling for large file support

← Older revision		Revision as of 17:41, 8 September 2010
Line 30:		Line 30:
	==More advanced visualization==		==More advanced visualization==

	* Optional: If you plan to work with large files (over 2GB), [[How to run WRF-Fire~~\|recompile NetCDF~~]] ~~in bash as~~		* Optional: If you plan to work with large files (over 2GB), you must have WRF compiled with large file support. This requires a netcdf
	~~export WRFIO_NCD_LARGE_FILE_SUPPORT=1~~		library with large file support as well. To compile netcdf with large file support, follow the instructions at [[How to run WRF-Fire]], but add the flag
	~~and then run in your netcdf directory~~		<code>--enable-largefile</code> to the configure command, and set the environment variable
	~~./configure --disable-netcdf4 --disable-dap~~ --enable-~~large-file-tests --prefix=~~the ~~contents of your NETCDF~~ variable		<code>WRFIO_NCD_LARGE_FILE_SUPPORT=1</code> prior to compiling WRF.
	~~make~~
	~~make install~~		If you are running on a Mac, you can install nco with large file support using [http://www.macports.org/ macports],
	~~make check~~
	~~The last command will create~~, ~~manipulate and delete some large files, so expect that it will take some time to finish (note the "--enable-~~large-file~~-tests" switch). If you do not have~~ [http://~~nco~~.~~sourceforge~~.~~net~~/ ~~nco~~] ~~for command-line manipulation with large files~~, ~~install it on a Mac simply as~~
	sudo port install nco		sudo port install nco
	and see its [http://nco.sourceforge.net/nco.html user's guide] if you wish. ~~It should~~ not ~~be necessary (I believe)~~ to ~~reinstall WRF~~-~~fire~~.		and see its [http://nco.sourceforge.net/nco.html user's guide] if you wish. On some linux distributions, the binaries that come with the package manager do not support large files. You will need to recompile nco manually from the [http://nco.sourceforge.net/src/nco-4.0.3.tar.gz source package] with the following environment variables set to the location of you netcdf library.
			export NETCDF_LIB=${NETCDF}/lib
			export NETCDF_INC=${NETCDF}/include

	* If the wrfout file contains all WRF variables, which is way more than we need at this point, it is convenient to select only the desired variables: U,V,W for wind streamlines, GRNHFX for fire, QVAPOR for smoke and AVG_FUEL_FRAC for the burned area.		* If the wrfout file contains all WRF variables, which is way more than we need at this point, it is convenient to select only the desired variables: U,V,W for wind streamlines, GRNHFX for fire, QVAPOR for smoke and AVG_FUEL_FRAC for the burned area.

	The selection of variables can be done in two ways:		The selection of variables can be done in two ways:
	* create new NetCDF file with this variables by ("-O" switch overrides the file and if some variable is not available, simply skip it)		* create new NetCDF file with this variables by ("-O" switch overrides the file and if some variable is not available, simply skip it)
Line 91:		Line 91:
	* Use other VAPOR features for a more advanced visualization as desired.		* Use other VAPOR features for a more advanced visualization as desired.


	==Works with==		==Works with==
	* WRF-Fire {{WRF-Fire-commit\|1e710fc81479ea71ed74dd9903da9917fc9dcd93\|May 26 2010}} and hopefully later		* WRF-Fire {{WRF-Fire-commit\|1e710fc81479ea71ed74dd9903da9917fc9dcd93\|May 26 2010}} and hopefully later

Sousedik at 06:52, 7 September 2010

2010-09-07T06:52:59Z

← Older revision		Revision as of 06:52, 7 September 2010
Line 56:		Line 56:
	* If you are provided a "Vapor saved session file" *.vss click "File" in the top menu bar and load this file by "Open session" dialogue. In either case, click "Data" in the top menu bar, then "load dataset in the current session", and navigate to the file.vdf (you might have just created). In the black right panel, you should see an empty wireframe box.		* If you are provided a "Vapor saved session file" *.vss click "File" in the top menu bar and load this file by "Open session" dialogue. In either case, click "Data" in the top menu bar, then "load dataset in the current session", and navigate to the file.vdf (you might have just created). In the black right panel, you should see an empty wireframe box.
	* To label the axes with coordinate values click "Edit" in the top main menu, then "Edit Visualizer Features" and check "Show X, Y, Z (R,G,B) Arrows". You can also add "Enable axis annotation", "Time annotation", etc. In case you do not have a terrain image and you will not be able to acquire one using the steps described below, you might check "Display Terrain Surface" and pick (a constant) "Color" you like. If you have an image, do not import it here, but use the "Image tab" discussed below.		* To label the axes with coordinate values click "Edit" in the top main menu, then "Edit Visualizer Features" and check "Show X, Y, Z (R,G,B) Arrows". You can also add "Enable axis annotation", "Time annotation", etc. In case you do not have a terrain image and you will not be able to acquire one using the steps described below, you might check "Display Terrain Surface" and pick (a constant) "Color" you like. If you have an image, do not import it here, but use the "Image tab" discussed below.
	* If you do not have an image of the terrain, but your wrfout file contains the geo-coordinates of the domain you can acquire the image from the internet. If you already have an image or you don't know the coordinates then skip this step...		* If you do not have an image of the terrain, but your wrfout file contains the geo-coordinates of the domain you can acquire the image from the internet. If you already have an image or you don't know the coordinates then skip this step. We will use Vapor's bash-shell script [http://www.vapor.ucar.edu/docs/reference/index.php?id=man/getWMSImage getWMSImage.sh] for retrieving maps and imagery from a Web Mapping Server (WMS). The call of the script has a general form
			getWMSImage.sh [options] minLon minLat maxLon maxLat
			where we will use the following options to specify: map type -m landsat (the other option to consider is BMNG, but it seems to give worse quality images), the output file -o filename.tiff and the pixel resolution -r xres yres (the default is 1024x768). Assuming that minLon minLat maxLon maxLat are given as -95.03 29.3 -95.01 29.4, an example call of getWMSImage.sh can be
			getWMSImage.sh -m landsat -o fireflux_terrain_geo.tiff -r 1180 1580 -95.03 29.3 -95.01 29.4
			Such an image will be automatically geo-referenced, i.e. it will include the longitude/latitude information.
			If you have a tiff image which is not geo-referenced, e.g., an image obtained from the Google Earth screenshot, you can use [http://www.vapor.ucar.edu/docs/reference/index.php?id=man/tiff2geotiff tiff2geotiff] to convert it to a geo-referenced terrain image as
			tiff2geotiff -4 "+proj=longlat" -n "-95.03 29.3 -95.01 29.4" fireflux_terrain.tiff fireflux_terrain_geo.tiff
	* If you have a tiff image of the terrain click on the "Image" tab. In VAPOR 1.5.0 you are allowed to use only tiff images without any compression. If your image is a tiff but not a geotiff (or you are not sure) uncheck "Georeference", then "Select Image File" and navigate to your file. Finally check "Apply image to terrain" and "Instance: 1". After the image is displayed you may also check "Crop to bounds" if needed.		* If you have a tiff image of the terrain click on the "Image" tab. In VAPOR 1.5.0 you are allowed to use only tiff images without any compression. If your image is a tiff but not a geotiff (or you are not sure) uncheck "Georeference", then "Select Image File" and navigate to your file. Finally check "Apply image to terrain" and "Instance: 1". After the image is displayed you may also check "Crop to bounds" if needed.
	* Click the "Animation" tab and move the "Frame position" slider to a time when you know that the fire has already well developed.		* Click the "Animation" tab and move the "Frame position" slider to a time when you know that the fire has already well developed.