How to get WRF-SFIRE - Revision history

Jmandel: /* Download */

2021-10-09T02:24:47Z

Download

← Older revision		Revision as of 02:24, 9 October 2021
Line 13:		Line 13:
	;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]		;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]
	:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>		:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>
	~~;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]~~
	~~:<tt><pre>git clone git://github.com/openwfm/WPS-merge.git</pre></tt>~~
	;http://repo.or.cz/WRF-SFIRE.git		;http://repo.or.cz/WRF-SFIRE.git
	:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git</pre></tt>		:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git</pre></tt>
	~~;http://repo.or.cz/WPS-merge.git~~		The home page of the mirror allows you to browse the source code as well as examine changes and view the different development branches.
	~~:<tt><pre>git clone git://repo.or.cz/WPS-merge.git</pre></tt>~~
	The home ~~pages~~ of the ~~mirrors allow~~ you to browse the source code as well as examine changes and view the different development branches~~. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably~~.

	It is also possible to download the latest source code as a		It is also possible to download the latest source code as a
	[[wikipedia:tar (file format)\|tarball]] or [[wikipedia:zip (file format)\|zip]] file from each mirror; however, this method is discouraged as it will be		[[wikipedia:tar (file format)\|tarball]] or [[wikipedia:zip (file format)\|zip]] file from each mirror; however, this method is discouraged as it will be difficult to update to the latest version and we cannot support code that is not under git control.
	difficult to update to the latest version.

	==Update==		==Update==

Jmandel: clarified what is supported

2021-10-09T02:22:02Z

clarified what is supported

← Older revision		Revision as of 02:22, 9 October 2021
Line 1:		Line 1:
	{{users guide}}		{{users guide}}
	'''The WRF-Fire code in [http://wrf-model.org WRF] release is an old version of the code here, from 2010~~. This is true even in newer WRF releases. See~~ [[Fire code in WRF release]] ~~for a detailed comparison~~. Many [[WRF-~~Fire~~ development notes\|~~errors~~ were ~~fixed and features~~ added]] since then. Please get the current version from ~~our repository~~ as described here, which includes current SFIRE and WRF. ~~We support~~ the ~~latest~~ version ~~of SFIRE from our repository only~~. We can even consider [[WRF-Fire development notes#Wish list\|adding features]] on request. ~~Sorry we cannot support or modify the fire code version in the WRF release.'''~~		'''The WRF-Fire code in [http://wrf-model.org/WRF WRF] release has an old version of the code here, from 2010, with [[Fire code in WRF release\|further modifications at NCAR]] and developments since WRF 4.0. We cannot support that version and it is not under our control. Many [[WRF-SFIRE development notes\|different features were added]] since then. Please get the current version from http://github.com/openwfm/WRF-SFIRE as described here, which includes current SFIRE and WRF. This is the only version we can support. We can even consider [[WRF-Fire development notes#Wish list\|adding features]] on request.

	SFIRE is maintained in a [[git]] repository. A git repository is a software version control system similar to [http://www.nongnu.org/cvs/ CVS] or [http://subversion.apache.org/ SVN]. There is a repository containing WRF-SFIRE and another repository containing WPS, and it is regularly synchronized with major WRF releases. They both need to be compiled with the same compiler and be present at the same directory level. In order to obtain the software from our repositories, you must first [http://git-scm.com/download download] and install the git software. The default view of the repository is the head of the master branch, which should contain a current stable and working code at any time.		SFIRE is maintained in a [[git]] repository. A git repository is a software version control system similar to [http://www.nongnu.org/cvs/ CVS] or [http://subversion.apache.org/ SVN]. There is a repository containing WRF-SFIRE and another repository containing WPS, and it is regularly synchronized with major WRF releases. They both need to be compiled with the same compiler and be present at the same directory level. In order to obtain the software from our repositories, you must first [http://git-scm.com/download download] and install the git software. The default view of the repository is the head of the master branch, which should contain a current stable and working code at any time.

Afarguell: /* See also */

2020-08-06T05:11:47Z

Afarguell: /* See also */

2020-08-06T05:11:23Z

Afarguell at 15:12, 2 July 2020

2020-07-02T15:12:20Z

← Older revision		Revision as of 15:12, 2 July 2020
Line 2:		Line 2:
	'''The WRF-Fire code in [http://wrf-model.org WRF] release is an old version of the code here, from 2010. This is true even in newer WRF releases. See [[Fire code in WRF release]] for a detailed comparison. Many [[WRF-Fire development notes\|errors were fixed and features added]] since then. Please get the current version from our repository as described here, which includes current SFIRE and WRF. We support the latest version of SFIRE from our repository only. We can even consider [[WRF-Fire development notes#Wish list\|adding features]] on request. Sorry we cannot support or modify the fire code version in the WRF release.'''		'''The WRF-Fire code in [http://wrf-model.org WRF] release is an old version of the code here, from 2010. This is true even in newer WRF releases. See [[Fire code in WRF release]] for a detailed comparison. Many [[WRF-Fire development notes\|errors were fixed and features added]] since then. Please get the current version from our repository as described here, which includes current SFIRE and WRF. We support the latest version of SFIRE from our repository only. We can even consider [[WRF-Fire development notes#Wish list\|adding features]] on request. Sorry we cannot support or modify the fire code version in the WRF release.'''

	SFIRE is maintained in a [[git]] repository. A git repository is a software version control system similar to [http://www.nongnu.org/cvs/ CVS] or		SFIRE is maintained in a [[git]] repository. A git repository is a software version control system similar to [http://www.nongnu.org/cvs/ CVS] or [http://subversion.apache.org/ SVN]. There is a repository containing WRF-SFIRE and another repository containing WPS, and it is regularly synchronized with major WRF releases. They both need to be compiled with the same compiler and be present at the same directory level. In order to obtain the software from our repositories, you must first [http://git-scm.com/download download] and install the git software. The default view of the repository is the head of the master branch, which should contain a current stable and working code at any time.
	[http://subversion.apache.org/ SVN]. There is a repository containing WRF and another repository containing WPS, and it is regularly synchronized with major WRF releases. In order to obtain the software from our
	repositories, you must first [http://git-scm.com/download download] and install the git software. The default view of the repository is the head of the master branch, which should contain a current stable and working code at any time.

	The best view of current activity is available at http://repo.or.cz/git-browser/by-commit.html?r=WRF-SFIRE.git		The best view of current activity is available at http://repo.or.cz/git-browser/by-commit.html?r=WRF-SFIRE.git

Afarguell: /* Download */

2020-07-02T15:10:16Z

Download

← Older revision		Revision as of 15:10, 2 July 2020
Line 14:		Line 14:
	We strongly recommend to use download by git (as opposed to a tar or zip file, also available from the repository), because git allows easy updates and identification of the state of all files in case of problems. The following public, read-only mirrors are available.		We strongly recommend to use download by git (as opposed to a tar or zip file, also available from the repository), because git allows easy updates and identification of the state of all files in case of problems. The following public, read-only mirrors are available.
	;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]		;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]
			:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>
	;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]		;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]
	:<tt><pre>~~git clone git://github.com/openwfm/WRF-SFIRE.git~~		:<tt><pre>git clone git://github.com/openwfm/WPS-merge.git</pre></tt>
	git clone git://github.com/openwfm/WPS-merge.git
	</pre></tt>
	;http://repo.or.cz/WRF-SFIRE.git		;http://repo.or.cz/WRF-SFIRE.git
			:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git</pre></tt>
	;http://repo.or.cz/WPS-merge.git		;http://repo.or.cz/WPS-merge.git
	:<tt><pre>~~git clone git://repo.or.cz/WRF-SFIRE.git~~		:<tt><pre>git clone git://repo.or.cz/WPS-merge.git</pre></tt>
	git clone git://repo.or.cz/WPS-merge.git
	</pre></tt>
	The home pages of the mirrors allow you to browse the source code as well as examine changes and view the different development branches. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably.		The home pages of the mirrors allow you to browse the source code as well as examine changes and view the different development branches. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably.

Afarguell at 15:08, 2 July 2020

2020-07-02T15:08:46Z

← Older revision		Revision as of 15:08, 2 July 2020
Line 15:		Line 15:
	;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]		;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]
	;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]		;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]
	:<tt><pre>		:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git
	git clone git://github.com/openwfm/WRF-SFIRE.git
	git clone git://github.com/openwfm/WPS-merge.git		git clone git://github.com/openwfm/WPS-merge.git
	</pre></tt>		</pre></tt>
	;http://repo.or.cz/WRF-SFIRE.git		;http://repo.or.cz/WRF-SFIRE.git
	;http://repo.or.cz/WPS-merge.git		;http://repo.or.cz/WPS-merge.git
	:<tt><pre>		:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git
	git clone git://repo.or.cz/WRF-SFIRE.git
	git clone git://repo.or.cz/WPS-merge.git		git clone git://repo.or.cz/WPS-merge.git
	</pre></tt>		</pre></tt>

Afarguell: /* Download */

2020-07-02T15:08:19Z

Download

← Older revision		Revision as of 15:08, 2 July 2020
Line 15:		Line 15:
	;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]		;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]
	;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]		;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]
	:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git~~</pre></tt>~~		:<tt><pre>
	~~:<tt><pre>~~git clone git://github.com/openwfm/WPS-merge.git</pre></tt>		git clone git://github.com/openwfm/WRF-SFIRE.git
			git clone git://github.com/openwfm/WPS-merge.git
			</pre></tt>
	;http://repo.or.cz/WRF-SFIRE.git		;http://repo.or.cz/WRF-SFIRE.git
	;http://repo.or.cz/WPS-merge.git		;http://repo.or.cz/WPS-merge.git
	:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git~~</pre></tt>~~		:<tt><pre>
	~~:<tt><pre>~~git clone git://repo.or.cz/WPS-merge.git</pre></tt>		git clone git://repo.or.cz/WRF-SFIRE.git
			git clone git://repo.or.cz/WPS-merge.git
			</pre></tt>
	The home pages of the mirrors allow you to browse the source code as well as examine changes and view the different development branches. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably.		The home pages of the mirrors allow you to browse the source code as well as examine changes and view the different development branches. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably.

Afarguell: /* Download */

2020-07-02T15:07:35Z

Download

← Older revision		Revision as of 15:07, 2 July 2020
Line 16:		Line 16:
	;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]		;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]
	:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>		:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>
			:<tt><pre>git clone git://github.com/openwfm/WPS-merge.git</pre></tt>
	;http://repo.or.cz/WRF-SFIRE.git		;http://repo.or.cz/WRF-SFIRE.git
			;http://repo.or.cz/WPS-merge.git
	:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git</pre></tt>		:<tt><pre>git clone git://repo.or.cz/WRF-SFIRE.git</pre></tt>
			:<tt><pre>git clone git://repo.or.cz/WPS-merge.git</pre></tt>
	The home pages of the mirrors allow you to browse the source code as well as examine changes and view the different development branches. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably.		The home pages of the mirrors allow you to browse the source code as well as examine changes and view the different development branches. It is strongly recommended to use the <tt>git://</tt> transport protocol in the git commands as above, not <tt>http://</tt>, which does not work reliably.

Afarguell: /* Download */

2020-07-02T15:06:07Z

Download

← Older revision		Revision as of 15:06, 2 July 2020
Line 14:		Line 14:
	We strongly recommend to use download by git (as opposed to a tar or zip file, also available from the repository), because git allows easy updates and identification of the state of all files in case of problems. The following public, read-only mirrors are available.		We strongly recommend to use download by git (as opposed to a tar or zip file, also available from the repository), because git allows easy updates and identification of the state of all files in case of problems. The following public, read-only mirrors are available.
	;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]		;[http://github.com/openwfm/WRF-SFIRE http://github.com/openwfm/WRF-SFIRE]
			;[http://github.com/openwfm/WPS-merge http://github.com/openwfm/WPS-merge]
	:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>		:<tt><pre>git clone git://github.com/openwfm/WRF-SFIRE.git</pre></tt>
	;http://repo.or.cz/WRF-SFIRE.git		;http://repo.or.cz/WRF-SFIRE.git

← Older revision		Revision as of 05:11, 6 August 2020
Line 50:		Line 50:
	*[[WRF-Fire#Support\|WRF-Fire support]]		*[[WRF-Fire#Support\|WRF-Fire support]]

	[[Category:WRF-~~SFIRE~~]]		[[Category:WRF-Fire]]
	[[Category:Howtos\|Get WRF-Fire]]		[[Category:Howtos\|Get WRF-Fire]]

← Older revision		Revision as of 05:11, 6 August 2020
Line 46:		Line 46:
	==See also==		==See also==

	*[[How to run WRF-~~Fire~~]]		*[[How to run WRF-SFIRE]]
	*[[WRF-Fire development notes]]		*[[WRF-Fire development notes]]
	*[[WRF-Fire#Support\|WRF-Fire support]]		*[[WRF-Fire#Support\|WRF-Fire support]]

	[[Category:WRF-~~Fire~~]]		[[Category:WRF-SFIRE]]
	[[Category:Howtos\|Get WRF-Fire]]		[[Category:Howtos\|Get WRF-Fire]]