-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfaq.html
More file actions
432 lines (408 loc) · 24.6 KB
/
faq.html
File metadata and controls
432 lines (408 loc) · 24.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
<!DOCTYPE HTML>
<!--
Forty by HTML5 UP
html5up.net | @ajlkn
Free for personal and commercial use under the CCA 3.0 license (html5up.net/license)
-->
<html>
<head>
<title>WindNinja FAQ</title>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<link rel="stylesheet" href="assets/css/main.css" />
<noscript><link rel="stylesheet" href="assets/css/noscript.css" /></noscript>
<link rel="icon"
type="image/png"
href="favicon.ico">
</head>
<body class="is-preload">
<style>
/*FAQS*/
.faq_question {
margin: 0px;
padding: 0px 0px 5px 0px;
display: inline-block;
cursor: pointer;
font-weight: bold;
}
.faq_answer_container {
height: 0px;
overflow: hidden;
padding: 0px;
}
</style>
<!-- Wrapper -->
<div id="wrapper">
<!-- Header -->
<header id="header" class="alt style2">
<a href="/windninja/" class="logo"><strong>WindNinja</strong> <span>FireLab</span></a>
<nav>
<a href="about.html">About</a>
<a href="help.html">Help</a>
<a href="tutorials/">Tutorials</a>
<a href="mobile/">Mobile</a>
<a href="#menu">Menu</a>
<!-- <a href="https://weather.firelab.org/windninja_api/index.html">API</a> -->
<!-- <a href="publications/">Publications</a> -->
<!-- <a href=""> -->
</nav>
</header>
<!-- Menu -->
<nav id="menu">
<ul class="links">
<!-- <li><a href="about.html">About</a> -->
<!-- <li><a href="help.html">Help</a> -->
<!-- <li><a href="tutorials/">Tutorials</a> -->
<!-- <li><a href="mobile/">Mobile</a> -->
<li><a href="https://weather.firelab.org/windninja_api/index.html">API</a>
<li><a href="publications/">Publications</a></li>
<li><a href="field/">Field Observations</a></li>
<li><a href="howdoes/">How Does WindNinja Work?</a></li>
<li><a href="https://github.com/firelab/windninja/wiki">Developer Documentation</a></li>
<li><a href="building/">Building from Source</a></li>
<li><a href="contributors/">Contributors</a></li>
<li><a href="mobile/">WindNinja Mobile</a></li>
<li><a href="usage/">Usage Map</a></li>
<li><a href="who_uses/">Who Uses WindNinja?</a></li>
</ul>
<ul class="actions stacked">
<li><a href="#one" class="button fit">Download</a></li>
<!-- <li><a href="mobile/" class="button fit">WindNinja Mobile</a></li> -->
<!-- <li><a href="#" class="button fit">Log In</a></li> -->
</ul>
</nav>
<!-- Menu -->
<!-- Main -->
<div id="main" class="alt">
<section id="banner" class="style5">
<div class="inner">
<span class="image">
<img src="images/16banner.jpg" alt="" />
</span>
<header class="major">
<h1>
Frequently Asked Questions
</h1>
</header>
<div class="content">
</div>
</div>
</section>
<!-- One -->
<section id="one">
<div class="inner">
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>How do I install WindNinja?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<b>Windows</b>: Download the installer from
<a href="http://www.firelab.org/windninja">firelab.org</a>
and save it to your computer. Then, double-click on the installer in
this saved location. Follow the installation instructions in the window that opens.
Once installed, use the Start menu to start WindNinja.
<br>
<br>
<b>Linux</b>: Follow the instructions on
<a href="https://github.com/firelab/windninja/wiki/Building-WindNinja-on-Linux">
building from source</a>.
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>Where can documentation about running WindNinja be found?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<h4><a href="tutorials/">
Tutorials can be found online here.</a></h4>
<br>
<p style="font-size:105%;">Much of the available documentation is included in the WindNinja installation. To find this, first install WindNinja. Next, go to Start->Programs->WindNinja-x.x.x. Here you will find links to the included documentation, which includes tutorials, elevation file download instructions, wind vector viewing instructions, and example elevation files.</p>
<br>
<p style="font-size:105%;">
Another place to find WindNinja documentation is on
<a href="http://www.firelab.org/windninja">
WindNinja's distribution web site
</a>
</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question">
<h2>What is the difference between WindNinja and WindWizard?</h2>
</div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">
<a href="http://www.firelab.org/project/windwizard">WindWizard</a> is no longer available.
There is now an optional conservation of mass and momentum solver in
WindNinja which replaces the functionality of WindWizard.
<br>
<p style="font-size:105%;">The physics in the WindWizard solver were based on
proprietary software that required users to purchase a license. Because this
severely hampered usability, WindWizard is no longer available.
Instead, WindNinja has been upgraded to include the advanced physics previously included in
WindWizard, but without the licensing fees. As of version 3.0, WindNinja includes an optional
momentum solver that replaces the functionality of WindWizard. There are now two options for the
solver (the number-crunching part of WindNinja): 1) conservation of mass and 2) conservation
of mass and momentum. The conservation of mass option is the native, fast-running solver used
in previous versions of WindNinja. The conservation of mass and momentum option is a new solver
based on the OpenFOAM toolkit. OpenFOAM is free, open-source software for computational fluid dynamics (
CFD) from <a href="http://openfoam.org">the OpenFOAM Foundation</a>.</p><br>
<p style="font-size:105%;">The major differences, from a user’s perspective, between the two solvers are:</p>
<br>
<p>    1) The conservation of mass solver runs much faster than the conservation of mass and momentum solver (less than a minute for conservation of mass compared to about 1 hour for conservation of mass and momentum).</p><br>
<p>    2) The conservation of mass solver's approximation of the momentum equation is simpler and, at times, less accurate than that of the conservation of mass and momentum solver. This is mainly why the conservation of mass solver runs so much faster than the conservation of mass and momentum.</p><br>
<p>    3) The conservation of mass simulations are normally less accurate during stronger winds on the lee sides of ridges and mountains where re-circulation eddies can occur.</p><br>
<p>    4) The conservation of mass solver incorporates some non-neutral atmospheric stability effects, while the conservation of mass and momentum is only valid under near-neutral stability.</p><br>
<p>    5) WindNinja has a feature that allows users to enter measured wind information at several locations to drive the flow. WindNinja will produce a wind field that matches the winds as these locations. This feature is not currently available for the conservation of mass and momentum solver.</p><br>
<p>    6) WindNinja has a feature that automatically fetches and uses coarser U.S. National Weather Service forecast model outputs to drive the flow.</p><br>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>Is WindNinja faster than WindWizard? How much?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<a href="http://www.firelab.org/project/windwizard">WindWizard</a>
is no longer available.
There is now an optional conservation of mass and momentum solver in
WindNinja which replaces the functionality of WindWizard.<br>
<p style="font-size:105%;">
The conservation of mass solver (the native WindNinja solver)
runs much faster than the conservation of mass and momentum solver
(less than a minute for conservation of mass compared to about 1 hour
for conservation of mass and momentum).</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>How do I view WindNinja outputs?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">There are several ways to view WindNinja outputs. Probably the most convenient is to use Google Earth and WindNinja's KMZ output file (.kmz). As of version 3.0, WindNinja can generate a GeoPDF output file (.pdf). GeoPDFs can be viewed in any PDF reader, but can also be viewed in GIS programs including the Avenza PDF Maps mobile application. Another way, if you have a FARSITE landscape file (.lcp), is to use FlamMap with WindNinja's fire behavior output files (.asc). Last, you could use a GIS such as ArcView or ArcMap with WindNinja's shape file output files (.shp, .shx, .dbf). Instructions for plotting wind vectors using ArcView and ArcMap can be found within the help menu of WindNinja.</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>What elevation file formats does WindNinja accept?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">Starting with WindNinja 2.0.0, several common file formats can be used. They are:<br>
• Arc/Info ASCII Raster (*.asc)<br>
• FARSITE landscape file (*.lcp)<br>
• GeoTiff (*.tif)<br>
• ERDAS IMAGINE (*.img)<br><br>
WindNinja can now (as of 2.3.x) download dem files for you, and properly project the file.
</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>How do I obtain an elevation file?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">There are many different ways to obtain elevation files for WindNinja. WindNinja can now download a file for you with the best-fit UTM projection.
<br>
If you already have an elevation file, it can be used in WindNinja so long as it meets WindNinja's requirements. See the FAQ question about elevation file requirements.</p>
<br>
<br>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>What happens if I don't have GIS projection information with my elevation file?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;"><h3> Pre-2.3.0:</h3>
Without projection information, you can still use WindNinja but some options will not be available. Specifically, you won't be able to make Google Earth output files (.kmz). Also, if you want to do a diurnal simulation, you will have to manually enter a latitude and longitude for your area (with projection information WindNinja can automatically find the latitude and longitude for you).
<h3> 2.3.0 and after</h3>
WindNinja <b>requires</b> projection information with your DEM.
</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>What are the requirements for elevation files?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">
First, the elevation file must be one of the allowable file
formats (Arc/Info ASCII Raster (.asc), FARSITE landscape file (.lcp), GeoTiff (.tif),
ERDAS IMAGINE (.img)). Second, the elevation file
must not have any areas without data (NO_DATA values).
See WindNinja Tutorial 1 in the help menu for more information
about common reasons for having NO_DATA values and ways to fix these problems.
Third, elevation files must not be too large in extent.
We generally recommend that elevation files should be less than 50x50 km
(about 30x30 miles). Fourth, elevation files must be in units of meters.
This means both the horizontal and vertical units.
Last, if WindNinja 2.3.0 or newer is used, it must be georeferenced
in a projected coordinate system.</p>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>If I use a coarse (say 90m) DEM, can I simulate a larger area?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">The DEM resolution is really not so much the issue, it is the computational resolution of the wind simulation. WindNinja resamples the DEM to build the internal computational resolution, which is the resolution of the actual wind simulation. This computational resolution is the limiting factor in simulations when it comes to computational time and computational memory (running out of computer RAM). The choice of computational resolution should be such that the terrain is adequately resolved for the wind simulation, meaning that the scale of terrain that you want to resolve is resolved. For example, if you want to resolve all terrain features of a certain size, say hills of horizontal size of around 100 meters, then the computational resolution should probably be at least 10 to 30 meters so that there are several cells on the 100 meter hills. And so the computational resolution choice is probably really a function of the terrain. "Smoother" terrains with large average distances between hills/ridges could use larger cell sizes than "rougher" terrain.
<br><br>
Through experience, we've found that 100 to 300 meter computational (mesh) resolutions are usually adequate for most terrains. This can be obtained by choosing "fine" for mesh resolution and keeping the DEM extent to less than 40-50 km on a side. The user can choose "custom" for resolution and manually enter a computational cell size in meters. You could play around with a larger DEM (say 100 km by 100 km) and manually set the computational (mesh) resolution. The limiting factor will be computer RAM, at some point you'll run out.</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>Have you compared results with different grid resolutions to know if it markedly changes wind behavior?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">Indeed we have.<br> <br> For an example and discussion, you could look at the images on pages 30-31 of <a href="http://www.firelab.org/document/forthofer-thesis">Jason Forthofer's master's thesis</a>. Note that this terrain is fairly gentle though. The appropriate grid resolution is dependent on the specific terrain and what winds you want to resolve. Probably one of the best things to do is to experiment with different computational (mesh) resolutions for your terrain to see how much difference there is (sensitivity).</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>Is WindNinja accurate along the borders of the modeling domain?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">As with most numerical models of this type, winds along the border of the modeling domain may have some error. This is because, in reality, terrain features outside the modeling domain may affect the wind flow inside the domain. But since these terrain features are not modeled, the simulation results do not reflect them. There is a simple solution to deal with this problem. Use an elevation file that is slightly larger than the area you want to model so there is a buffer around your desired area. We recommend a 10-20% buffer size.</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>Are there any issues about using the model at fine scales?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;"><i>Say I'd like to use it to model the wind over an area of about 100 hectares which has a fairly complex topography - is WindNinja ok to use with (say) 10 m grid DEMs?</i><br>There shouldn't be any issues, although WindNinja hasn't been tested much at this scale.</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>Any insights on how well WindNinja captures flow eddies?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">Because of how the conservation of mass solver (the native solver) simulates momentum, it cannot capture eddies (reversed flow) at all. Instead you will just see very low wind speeds in these areas, but not reversed direction. The conservation of mass and momentum solver (available since version 3.0) will capture eddies in the flow field. We are in the process of evaluating the conservation of mass and momentum solver, including its ability to resolve lee-side eddies, against field observations in complex terrain.</p>
<br>
<br>
</div>
</div>
</div>
</div>
<div class="faq_container">
<div class="faq">
<div class="faq_question"><h2>How should I cite the model in a publication?</h2></div>
<div class="faq_answer_container">
<div class="faq_answer">
<p style="font-size:105%;">The best peer-reviewed reference is:<br>
Forthofer, J.M., Butler, B.W., Wagenbrenner, N.S., 2014. [A comparison of three approaches for simulating fine-scale surface winds in support of wildland fire management. Part I. Model formulation and comparison against measurements] (http://www.fs.fed.us/rm/pubs_other/rmrs_2014_forthofer_j001.pdf). Int. J. Wildland Fire. 23:969-981.
<br>
<i>Note: In this publication WindNinja is referred to as the "mass-conserving" model.</i></p>
<br>
<br>
</div>
</div>
</div>
</div>
</section>
<div class="inner">
<section id="two" class="spotlights">
<section style="background-color:#4CAF50">
<div class="content">
<div class="inner">
<header class="major">
<h3>Select Publications and Products</p>
</header>
<ul class="actions">
<li><a href="publications/" class="button">View Additional Publications</a></li>
</ul>
</div>
</div>
</section>
</div>
</div>
<!-- Footer -->
<footer id="footer">
<div class="inner">
<p style="text-align:center;"><img src="https://avatars1.githubusercontent.com/u/3028309?v=3&s=200" alt "firelab"></p>
<p style="text-align:center;"><a href="http://firelab.org/">firelab.org</a></p>
<ul class="icons">
</ul>
<ul class="copyright">
<li>© RMRS Missoula Fire Sciences Laboratory</li><li>Design: <a href="https://html5up.net">HTML5 UP</a></li>
</ul>
</div>
</footer>
</div>
<!-- Scripts -->
<script src="assets/js/jquery.min.js"></script>
<script src="assets/js/jquery.scrolly.min.js"></script>
<script src="assets/js/jquery.scrollex.min.js"></script>
<script src="assets/js/browser.min.js"></script>
<script src="assets/js/breakpoints.min.js"></script>
<script src="assets/js/util.js"></script>
<script src="assets/js/main.js"></script>
<script>
$(document).ready(function() {
$('.faq_question').click(function() {
if ($(this).parent().is('.open')){
$(this).closest('.faq').find('.faq_answer_container').animate({'height':'0'},500);
$(this).closest('.faq').removeClass('open');
}else{
var newHeight =$(this).closest('.faq').find('.faq_answer').height() +'px';
$(this).closest('.faq').find('.faq_answer_container').animate({'height':newHeight},500);
$(this).closest('.faq').addClass('open');
}
});
});
</script>
</body>
</html>