Now that version 0.9.0 of my Fire Weather Index for personal weather stations (pwsFWI) has been released in the context of CumulusUtils (I may separate it later into an independent program), it is time to look at formula corrections.
Having developed theoretically a Fire Weather Index (see my pwsFWI) and creating a first implementation of it in C for analytical purposes, I needed to take the software a bit further to make it more robust and useful. I had some feedback which made me realize it was urgent to have a good Fire Weather Index (FWI) for Personal Weather Stations (PWSs).
This blog is about the context and the actual programming requirements.
In An effort for a Simpler Fire Weather Index I described my new FWI and the theory behind it. In short, this pwsFWI (as I have baptised it) is meant to be a generic FWI, valid everywhere and independent of geology and vegetation.
The pwsFWI is a (not too) complex measure of local meteorology, an indicator composed of humidity, wind speed and temperature. It fluctuates under ‘normal’ conditions and if it becomes dryer (a longer period without rain, the number becomes higher. As soon as it starts raining, the value starts dropping.
In this blog I will propose a fire weather index for PWSs. The goal is to get fuel parameters out of the equation. This means that species, litter type or geography, will not play a role as they do in the Canadian FWI. As such, it connects with a recent new development described by Goodrick et.al. 2 .
An example for this top10 approach you will find on the weather site.
As a variation to existing top10 lists, I wrote a small program (in C) which reads dayfile.txt from Cumulus once per day just after midnight and for selected measurements it creates a sorted top10-list. From that list it creates a HTML-table and writes that to a text-file. That file can be included by the user on a website wherever he wants simply by a PHP-include (which is the easy way to include I think).