Difference between revisions of "How to get WRF-SFIRE"
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. | ||
− | 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 |
Revision as of 15:12, 2 July 2020
- Back to the WRF-SFIRE user guide.
The WRF-Fire code in 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 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 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 CVS or 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 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
Developers can get write access to the git repository on request, and must push changes to it.
Download
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
git clone git://github.com/openwfm/WRF-SFIRE.git
- http://github.com/openwfm/WPS-merge
git clone git://github.com/openwfm/WPS-merge.git
- http://repo.or.cz/WRF-SFIRE.git
git clone git://repo.or.cz/WRF-SFIRE.git
- http://repo.or.cz/WPS-merge.git
git clone git://repo.or.cz/WPS-merge.git
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 git:// transport protocol in the git commands as above, not http://, which does not work reliably.
It is also possible to download the latest source code as a tarball or zip file from each mirror; however, this method is discouraged as it will be difficult to update to the latest version.
Update
You can update your files any time to the current version, without downloading all again. If you have downloaded your copy by git, do in your WRF-SFIRE directory
git checkout master; git pull
If you have changed anything, the update will fail, and you have to commit your changes first by git commit -a. The git pull will then merge your changes with the new files from the repository. Please be sure you work with the latest files before contacting us for support. However, we may not be able to support code that you have changed.
Verify
To identify the version of files you have, do in your WRF-SFIRE directory
git log
To verify your files,
git diff
will give no output if your files have not changed from the version identified by git log.