Difference between revisions of "Talk:WRF-Fire"
Jump to navigation
Jump to search
(about editing) |
|||
| Line 1: | Line 1: | ||
| − | This is a talk page in blog format. Enter your questions, wishes, or anything else as separate sections at the bottom (click the + tab above). See [[Help:Talk]] for more editing conventions for talk pages. | + | This is a talk page in blog format. Enter your questions, wishes, or anything else as separate sections at the bottom (click the + tab above). Start your response with : on a new line to offset, and signe your contribution by <nowiki>~~~~</nowiki>. See [[Help:Talk]] for more editing conventions for talk pages. |
==Current wish list== | ==Current wish list== | ||
Revision as of 01:31, 1 February 2010
This is a talk page in blog format. Enter your questions, wishes, or anything else as separate sections at the bottom (click the + tab above). Start your response with : on a new line to offset, and signe your contribution by ~~~~. See Help:Talk for more editing conventions for talk pages.
Current wish list
Restartdone- Read topography from file in ideal run
- Smoothing the terrain gradients for fire spread
- Canopy fire
- Output to WRF-Chem
Anything more? Jmandel 18:59, 19 January 2010 (UTC)
Proposed input of additional data in ideal run
- Single topography for both the atmosphere and the fire models - from an arbitrary rectangular mesh aligned with coordinate axes
- Fuel data for the fire model - at the centers of the fire mesh
- Surface data for WRF - see e.g.
/dyn_em/module_initialize_seabreeze2d_x.Faroundcall ns_set_iswater, at centers of the atmosphere mesh ("mass points")
The input will be done similarly as in dyn_em/module_initialize_b_wave.F per suggestion of the WRF developers. See subroutine read_input_jet.
This is as far as we want to go in ideal.exe, more complicated data input should be done trhough real.exe.
Jmandel 01:29, 1 February 2010 (UTC)