Difference between revisions of "Porting WRF-SFIRE fuel moisture model to WRF4"

From openwfm
Jump to navigation Jump to search
Line 2: Line 2:
 
==Progress==
 
==Progress==
 
* I started {{wrf-fire-merge-branch|fuel-moisture-model}} from {{wrf-branch|develop}} as recommended in [https://github.com/wrf-model/WRF/wiki/Workflow-for-WRF-Code-Modification WRF instructions].  
 
* I started {{wrf-fire-merge-branch|fuel-moisture-model}} from {{wrf-branch|develop}} as recommended in [https://github.com/wrf-model/WRF/wiki/Workflow-for-WRF-Code-Modification WRF instructions].  
* Cherry pick {{wrf-fire-commit|f8193dad36|2011-09-25  adding moisture variables}} and {{wrf-fire-commit|5a6c4b8c06|2011-09-26 21:55:09 using variable fuel moisture in fmc_g}}. Making minimal changes against original. I had to check and understand any changes not just resolve conflicts. So that took a bit of time.
+
* Cherry pick {{wrf-fire-commit|f8193dad36|2011-09-25  adding moisture variables}} and {{wrf-fire-commit|5a6c4b8c06|2011-09-26 21:55:09 using variable fuel moisture in fmc_g}}. Making minimal changes against original. I had to check and understand any changes not just resolve the conflicts. Hard to automate. So that took a bit of time.
 
* I created {{wrf-fire-merge-tag|fuel-moisture-model-added-fmc_g}} at {{wrf-fire-merge-commit|132444f0db6754417|.}} The result should  
 
* I created {{wrf-fire-merge-tag|fuel-moisture-model-added-fmc_g}} at {{wrf-fire-merge-commit|132444f0db6754417|.}} The result should  
 
** give the same numbers  as code build by checking out {{wrf-fire-merge-tag|wrf-develop-baseline}} when <tt>fire_fmc_read=1</tt> in namelist.input or not set
 
** give the same numbers  as code build by checking out {{wrf-fire-merge-tag|wrf-develop-baseline}} when <tt>fire_fmc_read=1</tt> in namelist.input or not set

Revision as of 10:08, 21 January 2019

Progress

Should I swap 0 and 1?

To compile on kingspeak, please see How_to_build_WRF4#University_of_Utah_CHPC

The original plan (one out of several actually)

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.

See also