You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are excited to share a significant development in our project's versioning system. As we release the official 0.1 version of our code, we want to introduce you to an enhanced versioning approach that incorporates the relationship between SFIRE code and WRF code. Moving forward, our versioning system will consist of two components: the Weather Research and Forecasting (WRF) code version and the Wildfire Spread Simulation (SFIRE) code version.
28
31
29
32
## Understanding the Versioning Scheme
30
-
The semantic versioning scheme we have adopted is designed to provide clarity and context about the interconnectedness of our code with the WRF and SFIRE codes. Each version will be represented in the following format: `Wx.y-Si.j`, where:
33
+
The semantic versioning scheme (https://semver.org) we have adopted is designed to provide clarity and context about the interconnectedness of our code with the WRF and SFIRE codes. Each version will be represented in the following format: `Wx.y-Si.j`, where:
31
34
32
35
-`Wx.y` denotes the version of the WRF code on which our codebase relies. For example, `W4.4` represents version 4.4 of the WRF code. This component indicates the underlying framework that drives our code's functionality.
33
36
@@ -164,7 +167,7 @@ Your contributions, such as code reviews, suggestions, and bug reports, are inva
164
167
## Miscellaneous
165
168
- Write fuels data into fuels.m file (development feature)
166
169
167
-
# Branches
170
+
# Branches <aname="branches"></a>
168
171
* master, develop - the merged code.
169
172
* WRF-track/master, WRF-track/develop, etc. - tracking the official WRF repository including release tags
170
173
* filtered/* - rebased commits from the original wrf-fire repository, directory wrfv2_fire mapped to root:
* In namelist input, ifire=1 is WRF-SFIRE, ifire=2 the fire code in WRF we put there in 2012 (see branch filtered/submitted-to-3.3) with changes at NCAR. Most namelist flags are the same but each version has some of its own.
193
188
* Test problems available in test/em_fire:
194
189
- rain ifire=2
@@ -197,7 +192,20 @@ _ two_fires ifire=2
197
192
* The problems with ifire=2 should give the same result in branch master (the merged code) and in branch WRF/develop (the WRF distribution)
198
193
* It seems to run serial and MPI and so far passed some limited testing on cheyenne.
199
194
200
-
# Notes
195
+
# Notes <aname="notes"></a>
201
196
Standalone is included but have not started on it yet.
202
197
Branches balbi and dvm_branch were carried over but they are not merged into master or tested yet because they were not merged into master in wrf-fire. Also I do not know how to test dvm_branch.
203
198
I can't do real problems yet, that requires pushing data through current WPS, which Adam and Angel are working on.
0 commit comments