Difference between revisions of "Porting WRF-SFIRE fuel moisture model to WRF4"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
* Created {{wrf-fire-merge-tag|fuel-moisture-model-added-fmc_g}} at {{wrf-fire-merge-commit|132444f0db6754417|.}} The result should | * Created {{wrf-fire-merge-tag|fuel-moisture-model-added-fmc_g}} at {{wrf-fire-merge-commit|132444f0db6754417|.}} The result should | ||
** give the same numbers when <tt>fire_fmc_read=1</tt> in namelist.input or not set | ** give the same numbers when <tt>fire_fmc_read=1</tt> in namelist.input or not set | ||
| − | ** take <tt>fmc_g</tt> from <tt>wrfinput</tt> when <tt>fire_fmc_read= | + | ** take <tt>fmc_g</tt> from <tt>wrfinput</tt> when <tt>fire_fmc_read=0</tt> |
** next: read from file when <tt>fire_fmc_read=2</tt> | ** next: read from file when <tt>fire_fmc_read=2</tt> | ||
Should I swap 0 and 1? | Should I swap 0 and 1? | ||
Revision as of 08:45, 21 January 2019
Progress
- Started branch fuel-moisture-model from branch develop.
- Cherry pick f8193dad36 2011-09-25 adding moisture variables and
5a6c4b8c06 2011-09-26 21:55:09 using variable fuel moisture in fmc_g. Making minimal changes against original. Needed to check any changes not only resolve conflicts.
- Created tag fuel-moisture-model-added-fmc_g at 132444f0db6754417 . The result should
- give the same numbers when fire_fmc_read=1 in namelist.input or not set
- take fmc_g from wrfinput when fire_fmc_read=0
- next: read from file when fire_fmc_read=2
Should I swap 0 and 1?
The original plan
Too much complexity. There were quite a few conflicts already in cherry pick to 3cdb542af7ce submitted to 3.3 where not much changed. After a day or so, I decided I may as well do it right.
- check out 26d8a8f91cad4 release_v3.3 branch release_v3.3
- copy over fire model files from 3cdb542af7ce submitted to 3.3
- commit as 4e7a17952e22a v3.3 with fire as submitted
- create branch v3.3_with_fire_as_submitted
- revert the commit to get e69ed0d635b4 the change from submitted to release 3.3
- check out 3cdb542af7ce submitted to 3.3
- create branch moisture-model-port
- apply the fuel moisture model commits
- test with v3.3 input files
- apply? the change from submitted to release 3.3
- test with v3.3 input files
- upgrade by merge with 093ea6274f0d0 v4.0.3
- upgrade by merge with branch develop
- test with v4.0 input files