mrgmarsh / wfrog Goto Github PK

I want to add flash wiew of my web-cam on the page
where is webserver root directory to put there needed files?

Rationale:
- Allows very easy integration of other stations, the driver can be written
in a different language
- Allows for deploying the logger on a different machine.

This needs to specify 'standardized' XML for the sensor events sent from
the driver to the logger.

See http://code.google.com/p/wfrog/wiki/Architecture for details

What steps will reproduce the problem?
1.tempgaphic

What version of the product are you using?
0.71
On what operating system?
Kubuntu 10.04
konquer

the attach file is explain.

JanC
Texel-Nederland

What steps will reproduce the problem?
1. install wfrog 0.8 from svn
2.configure wu update service
It test normaly but did not run in normal mode
I've made file
/usr/lib/wfrog/bin/wu.sh
#! /bin/bash
exec /usr/bin/python /usr/lib/wfrog/wfrender/wfrender.py -f 
/usr/lib/wfrog/wfrender/config/wunderground.yaml --s /etc/wfrog/settings.yaml \
3. it fail update in midnight
I try to kill procces in 23:59 and start it again in 00:01 but it's did not help
In wfrender.log i see
2010-12-13 23:52:39,307 INFO [renderer.wunderground] Publishing Wunderground 
data (normal server, IU041CU02 station): 2010-12-13 20:49:39 / 24.3F / 96% / 
29.9inHg / 0.0inh / 0.0in / 5.8Mph(30deg.) / 5.8Mph(2$
2010-12-13 23:52:41,390 INFO [renderer.wunderground] Result Wunderground 
publisher: (200, 'OK', 'success\n')
2010-12-13 23:57:41,424 INFO [renderer.wunderground] Publishing Wunderground 
data (normal server, IU041CU02 station): 2010-12-13 20:54:49 / 24.3F / 96% / 
30.0inHg / 0.0inh / 0.0in / 5.8Mph(30deg.) / 5.8Mph(2$
2010-12-13 23:57:42,921 INFO [renderer.wunderground] Result Wunderground 
publisher: (200, 'OK', 'success\n')
2010-12-14 00:02:43,025 INFO [renderer.wunderground] Publishing Wunderground 
data (normal server, IU041CU02 station): 2010-12-13 20:54:49 / 24.3F / 96% / 
30.0inHg / 0.0inh / 0.0in / 5.8Mph(30deg.) / 5.8Mph(2$
2010-12-14 00:02:44,241 INFO [renderer.wunderground] Result Wunderground 
publisher: (200, 'OK', 'success\n')
2010-12-14 00:07:44,323 INFO [renderer.wunderground] Publishing Wunderground 
data (normal server, IU041CU02 station): 2010-12-13 20:54:49 / 24.3F / 96% / 
30.0inHg / 0.0inh / 0.0in / 5.8Mph(30deg.) / 5.8Mph(2$
2010-12-14 00:07:45,532 INFO [renderer.wunderground] Result Wunderground 
publisher: (200, 'OK', 'success\n')
OS: Ubuntu 10.10 x32 server

What steps will reproduce the problem?
1. Install wfrog 0.7 from file
2. Install dependences as spec-ed by wiki
3. as root or user, run "bin\wfrong 

What is the expected output? What do you see instead?
Not sure what to expect, but I get

This is the setup of wfrog user settings that will be written in 
/home/tux/.wfrog/settings.yaml

Please enter the altitude of your station (meters from sea level):
[0] > 100

Please enter the temperature unit:
 1) C
 2) F
[C] > F

Please enter the wind speed unit:
 1) km/h
 2) mph
 3) m/s
 4) kt
 5) bft
[km/h] > mph

Please enter the absolute rain fall unit:
 1) mm
 2) in
[mm] > in

Please enter the atmospheric pressure unit:
 1) hPa
 2) mmHg
 3) inHg
[hPa] > inHg

Thanks.
Now starting wfrog. Standard config serves on http://localhost:7680/.
Traceback (most recent call last):
  File "./wfrog", line 138, in <module>
    component.run(config_file, settings)
  File "/home/tux/Documents/wfrog-0.7/wflogger/wflogger.py", line 132, in run
    self.configure(config_file, settings_file)
  File "/home/tux/Documents/wfrog-0.7/wflogger/wflogger.py", line 94, in configure
    (config, self.context) = self.configurer.configure(options, self, config_file, settings_file)
  File "/home/tux/Documents/wfrog-0.7/wfcommon/config.py", line 116, in configure
    self.log_configurer.configure(options, config, context)
  File "/home/tux/Documents/wfrog-0.7/wfcommon/log.py", line 77, in configure
    handler = handler._init(context)
  File "/home/tux/Documents/wfrog-0.7/wfcommon/generic/include.py", line 58, in _init
    conf_str = str(Template(file=file(self.abs_path, "r"), searchList=[self.variables]))
  File "/usr/lib/python2.7/site-packages/Cheetah-2.4.3-py2.7-linux-i686.egg/Cheetah/Template.py", line 1259, in __init__
    self._compile(source, file, compilerSettings=compilerSettings)
  File "/usr/lib/python2.7/site-packages/Cheetah-2.4.3-py2.7-linux-i686.egg/Cheetah/Template.py", line 1553, in _compile
    keepRefToGeneratedCode=True)
  File "/usr/lib/python2.7/site-packages/Cheetah-2.4.3-py2.7-linux-i686.egg/Cheetah/Template.py", line 594, in compile
    ('file', 'string, file-like object, or None'))
TypeError: arg 'file' must be string, file-like object, or None
tux:~/Documents/wfrog-0.7/bin$



What version of the product are you using? On what operating system?
wfrog 0.7 on Slitaz 3.0

Please provide any additional information below.

I'm new to wfrog, but I expected it to at least start the web-server
and spool some synthetic or possbibly bogus data to the webpage.
Maybe there is more config needed before running but the wiki lead me to 
believe it work straight out of the tgz file.

I propose to create an alternative default rendering page for users (like me) 
who prefer static html (i.e. upload their meteo data by ftp). 
- The page look, charts, etc. should be the same (same yaml configuration).
- All data could be in one single html file (activating and deactivating divs 
as necessary)
- Current default page show different current data when switching pages on a 
static html. One single html file solves this.
- The current unit change system doesn't work with static html. Another system 
should be devised or we should skip this.

It will be good to have a simple command line app. to query the database
and check that the logger and render are online. Then this mechanism could
be integrated in the 'service' mecanism and implement the 'status'
argument. (similar to 'start' or 'stop').  

Support for several weather stations. This issue has been discussed in the 
early stages of wfrog design and should be formally registered here.

The idea is to have several drivers, each attached to its own weather station. 
At this point different options are possible:

A simple approach would be to have different drivers reporting events to a 
single logger (The WESTEP protocol already has a station identifier for such 
purposes).  For example, I plan to add a sun radiation sensor, maybe through 
1-wire protocol, to my WMRS200 station. In this case the solution is simple 
since each station would report different events to the logger, but other 
scenarios are more difficult to handle and would imply many changes to the 
accumulator.

Another option would be to have a pair driver-logger for each station, thus 
having different storage for each station. In this case the only necessary 
changes would be:
1) The render would have to be addapted  to use several storages (which I 
believe shouldn't be difficult).
2) The logger should be able to use different table names in database storages. 
(CSV storage ???)

wfrender wind graph (directions) doesn't paint North directions when saved
as 360 degrees. WMR928N driver records N as 0 deg., however WMRS200 records
360. The render doesn't recognize 360. 

It is interesting to add tables with numerical data on the webpage.
For example you can see weatherunderground.com historical data.

What is the reason for choosing Firebird as DB engine, why not sqlite or MySQL?

I'm really interested to get wfrog running on a qnap nas, which has MySQL
installed and I unfortunately can't install firebird trough IPKG.

I build new wfrog from svn and i see this problem
WU get only north direction
In real there is not only north:
(http://www.wunderground.com/weatherstation/WXDailyHistory.asp?ID=IU041CU02)WU 
page
http://weather.fire-mgou.ru/ wfrog page

What steps will reproduce the problem?
1. run bin/wfrog
2. watch the CSV file for missed entries (there should be one every 10 min)

What is the expected output? What do you see instead?
There should be an entry every 10 minutes. But I see occasional gaps of several 
hours. This happens about once every week.

1284298247,2010-09-12 15:30:47,27.7,31.0,0.8,212.6,1.9,247.5,9.0,0.0,0.0,1018.7,
1284298847,2010-09-12 15:40:47,27.3,30.0,1.0,208.4,2.4,180.0,8.2,0.0,0.0,1018.7,
1284304291,2010-09-12 17:11:31,26.9,32.0,0.2,180.7,0.7,225.0,8.8,0.0,0.0,1017.7,
1284304898,2010-09-12 17:21:38,26.4,34.0,0.0,45.0,0.6,45.0,9.3,0.0,0.0,1017.7,


Please use labels and text to provide additional information.

The log file does not show any errors of the data collector. It does show that 
the station driver is properly passing the data to the collector during the 
blackout period.

What steps will reproduce the problem?

1.editing /etc/wfrog/wfcommon/config/storage.yaml

2.storage: !user
    choices:
        root: !csv
            path: /var/lib/wfrog/wfrog.csv
        default: !csv
            path: data/wfrog.csv

storage: !firebird { database: 'localhost:/home/jan/firebird/data/wfrog.fdb',
                     user: sysdba,
                     password: masterkey }

#storage: !mysql { database: wfrog,
#                  host: localhost,
#                  user: root,
#                  password: root }

The # sign by firebird is changed

3.firebirdsql error -901

What is the expected output? What do you see instead?

2010-12-20 12:51:45,285 ERROR [storage.firebird] Error writting current data to 
database
Traceback (most recent call last):
  File "/usr/lib/wfrog/wfcommon/storage/base.py", line 58, in write_sample
    self.db.execute(sql)
  File "/usr/lib/wfrog/wfcommon/database.py", line 93, in execute
    cursor.execute(sql)
OperationalError: (-901, 'begin transaction: \n  invalid parameter in 
transaction parameter block')


What version of the product are you using? On what operating system?

wfrog_0.7-1_all.deb     

Please provide any additional information below.

kubuntu 10.04

wh1080

the other are changed with CustomizationGuide
and all database places are changed from 
'localhost:/var/lib/firebird/2.0/data/wfrog.db';  to  
'localhost:/home/jan/firebird/data/wfrog.fdb',

All other firebird-databases are working well

i hope you understand this all


JanC
Texel-Nederland

Create a class that receives all low battery events and generates a daily 
critical log message. This feature combined with critical messages notification 
by e-mail should be useful to detect a low battery problem.

wfrog works fine if you run it as vanilla - ie only settings.yaml in /etc/wfrog

However once --customise is run wfrog no longer updates - I suspect the 
bazillion config files (lots of complexity, but no doco guys!) are not entirely 
consistent in data locations. 

Cheers

Bret

What steps will reproduce the problem?
1. Install version 0.7 deb on debian (dockstar - similar to pogoplug)
2. Install pywws into python path
3. Plug in my wh1091 weather station
4. Run wfrog --customize
5. Change the driver to "station: !wh1080 {}" in 
/etc/wfrog/wfdriver/config/embedded.yaml

What is the expected output? What do you see instead?
Expected it to work, instead I get an error: 

ConstructorError: could not determine a constructor for the tag '!wh1080'
  in "/etc/wfrog//wflogger/config/../../wfdriver/config/embedded.yaml", line 3, column 10


What version of the product are you using? On what operating system?


Please provide any additional information below.
Thank you!

- Boxes are not correct on all browsers (IE)
- Replace webdings chars with icons

All database, weather calculation algorithms and other utilities should be
in wfcommon and be the same for all parts of wfrog.

wfrender with two schedulers in parallel experiences sporadic hangs. The
configuration which experienced these problems was:

    renderer: !multi
        parallel: true
        renderers:
            meteoclimatic: !scheduler
                period: 600  # in seconds
                renderer: !ftp
                    host: xxxx
                    username: xxxx
                    password: xxxx
                    directory: wfrog
                    renderers:
                        ESIBA0700000107240B.txt: !file
                            path: /tmp/ESIBA0700000107240B.txt
                            renderer: !meteoclimatic
                                id: ESIBA0700000107240B 
            htmlpages1: !scheduler
                period: 900
                renderer: !ftp
                    host: xxxx
                    username: xxxx
                    password: xxxx
                    directory: wfrog
                    renderers:
                        3hours.html: !file
                            path: /tmp/3hours.html
                            renderer: !include
                                path: default/3hours.yaml
                        24hours.html: !file
                            path: /tmp/24hours.html
                            renderer: !include
                                path: default/24hours.yaml
                        30days.html: !file
                            path: /tmp/30days.html
                            renderer: !include
                                path: default/30days.yaml

    So far the solution has been to have a single scheduler. I don't have a
clue on how it hangs or why... 

Thanks for quick unswer. for my past issue.
My config files are in issue 24.
when i  run
python wfrender.py 
Traceback (most recent call last):
  File "wfrender.py", line 27, in <module>
    import config
  File "/opt/wfrog/wfrender/config.py", line 20, in <module>
    import renderer
  File "/opt/wfrog/wfrender/renderer/__init__.py", line 21, in <module>
    import chart
  File "/opt/wfrog/wfrender/renderer/chart.py", line 32, in <module>
    import wfcommon.units
ImportError: No module named wfcommon.units

Earlier beta versions have been running on Windows with WMR928N. Testing
windows support with WMRS200 a problem was encountered with libusb, and no
further investigation was done.

All tools should be available in Windows and it shouldn't be too difficult
to run wfrog in Windows.

As a first 0.x version, wfrender reads current_conditions.xml file from the
driver to get the current conditions. 

wfrender should get the last values from the database.
current_conditions.xml is generated by the driver and does not need to have
the same format or values for all station drivers.

Good day
It's great tht you add support of wmr200 in wfrog
I  up my server on Ubuntu 10.04  and install wfrog 0.7 - it's work perfectly.
But i need to collect data in MySQL or PostgeSQL. Wfrog can write in mysql as i 
see, but it's do not write data in mysql.
What config you need to help me.\

With best regards Evgeny.

Currently, we have to copy all conf files and templates. We should find a 
overridable way.

Modify current www.meteoclimatic.com renderer to use new data accumulator class

As result of discussion in 
http://groups.google.com/group/wfrog-users/browse_thread/thread/4a45168875b0ca9d

The only thing to do is to write in wfrog a wrapper class
implementing the Station interface (see
http://code.google.com/p/wfrog/wiki/DeveloperGuide#Writing_a_station_...).
This station driver would instanciate the weather.stations.VantagePro
class and run an update loop, like weatherpub.py does and send events
after parse(). Quite trivial. 

wfrog expects to have data from all basic sensors (temp/hum, wind, rain and
barometer) before writting to the database. If one of the sensors fails
(bad reception, battery running down, etc.) no data is recorded. Each
sensor should be completely independent.

What steps will reproduce the problem?
1. Run wflogger -d with wfrog-svn-20100831 and pywws-10.10_r298
2.
3.

What is the expected output? What do you see instead?
Expect to see temperature recorded at 26.2 degrees celcius, instead, I see
11.2

2010-11-12 23:52:35,556 DEBUG [collector.xmlfile] Flushing: 
<current><thInt><humidity>61.7</humidity><temp>12.3</temp></thInt><th1><humidity
>60.9</humidity><temp>11.2</temp></th1><wind><avgSpeed>4.2</avgSpeed><dirDeg>127
.3</dirDeg><gustSpeed>6.2</gustSpeed></wind><time>2010-11-12 
23:52:35</time><rain><rate>11.3</rate></rain><barometer><pressure>1006.1</pressu
re></barometer></current> to /var/lib/wfrog/wfrog-current.xml


What version of the product are you using? On what operating system?
Ubuntu 10.10 (Server)
wfrog-svn-20100831
pywws-10.10_r298

Please provide any additional information below.

What steps will reproduce the problem?
1. Install wfrog 06 By documantation
By root i tried to start wflogger

python wflogger.py
Traceback (most recent call last):
  File "wflogger.py", line 168, in <module>
    driver.run()
  File "wflogger.py", line 162, in run
    time.sleep(sys.maxint)
IOError: [Errno 22] Invalid argument

My version with edited config is in attach
System ubuntu 10.04 x64 desktop

We need to implement the renderer datasource using the storage and no more
direct access to Firebird SQL.

Remove the Wx prefixes and lowercase python filenames.

Packaging for OS X

I think we need a station simulator driver. Just to be able to test new
developments on parts of wfrog which are not the driver without having to
unplug our real weather station.

It was suggested to allow wfrog to store data from several temp/hum sensors.

The project is young and we focused first on providing something working
for out-of-the-box stations, which have only two sensor pairs (outside and
inside). Of course, we want to see the project evolve and provide more
features. It is also important to keep wfrog simple, light, but also powerful. 

IMO there are two ways to handle several sensors:

- Configure at driver level which sensor(s) are reported to the logger. If
several temp/hum sensors are reported then the logger will calculate and
record the average value. 

This is easy to implement but might not be good enough in other situations.
For instance:
- to record swimming pool temperature (WMRX00 stations also have a pool sensor)
- to record green house hum/temp conditions
- to record indoor temperature.
- or just to be able to record each sensor separately and then decide later
which one(s) to show.
To allow this several fields temp/hum are necessary.

Both options are compatible. I think some discussion is needed to study the
different alternatives to carry them out.

normally backgrounding a program with something like wfrog -v > /var/log/wfrog 
& should put it into the background and send all console messages to the log 
file, but for some reason wfrog doesn't output its console messages in a 
"redirectable" manner...

Since some user already requested supporting another database and given
that different components needs acces to the database (logger for writing
but also for 12h mean temp, renderer to read data), we need to design an
'interface' for the database layer that can be implemented using different
db backends (firebird, mysql).

The provided methods should give the possibility to traverse the data using
callbacks, so that we can calculate formulas incrementally during the
traversing of database cursor without having to load everything in memory.
This, because we cannot delegate all calculations to the database (e.g.
dominant wind).

Methods we can expect having on the interface:

  write_record(temp, wind, wind_dir, ...)
  traverse_data(callback, from_timestamp=ever, to_timestamp=now)

This simple interface allows for easy implementation in other db. It could
even have a flat file implementation that could come by default in an
out-of-the-box distribution.

As stated in 
http://groups.google.com/group/wfrog-users/browse_thread/thread/87b8d0e2e0e2452b
, a support for getting data collected offline from the station memory is 
needed if we want to support more stations models.

There is already a draft of design in this post as well.

As a prospective work, this issue is about creating:
  * A ChunkEvent type
  * A ChunkCollector writing chunk events to storage

Notes from the discussion:

To support multiple
samples, I thought about using a new type of event, a ChunkEvent
containing a list timestamped of timestamped sample rows, each row
containing one or more events as we know them. This would also be part
of WESTEP.

Then, I would introduce another collector, a ChunkCollector treating
only the chunk events and writing them into the storage. Chunk events
are already aggregated values, I think, thus they must not go through
the aggregator. Of course, some refactoring of the aggregator to share
conversion code (pressure, ...) with the chunk collector may be
useful.

This implies that the drivers can choose if they issue chunk events
(treated by the chunk collector) or single events (treated by the
aggregator). They can do both provided that two conditions are
fulfilled: 1) The chronological order is respected, we cannot add
sample timestamped before the last sample we added. 2) The period of
chunk events is the same as the flush period of the aggregator, in
order to have consistent statistical computations.
Note also that even if the aggregator does not react to chunk events,
it will be reset its internal state upon reception of such an event. 

The renderer does not handle null values read from mysql. In my case the wind 
sensor stopped working and the logger writes a "null" in the stored row. Then, 
the renderer write a "9999" instead a "--", or something that simbolize a null 
value.

Im using wfrog 0.7 in Debian 5.

I have installed wfrog0.5 its take  data correctly and  can put it in xml
file and log. But i can not  se it on web

/etc/wfrog/wfrender.conf
context:
    database: { url: 'localhost:/var/lib/firebird/2.0/data/wfrog1.db' }  
renderer: !http    
    cookies: [ units ]
    root: !include
        path: /opt/wfrog/wfrender/config/default/24hours.yaml
    renderers:
        3hours.html: !include
            path: /opt/wfrog/wfrender/config/default/3hours.yaml
        24hours.html: !include
            path: /opt/wfrog/wfrender/config/default/24hours.yaml      
        30days.html: !include
            path: /opt/wfrog/wfrender/config/default/30days.yaml        
        365days.html: !include
            path: /opt/wfrog/wfrender/config/default/365days.yaml

logging:
    level: info    
    handlers:
        default:
            level: debug
            handler: !include 
                path: /opt/wfrog/wfcommon/config/loghandler.yaml
                variables:
                    process: wfrender

/etc/wfrog/wflogger.conf

context:
    altitude: 618

input: !service
    name: events  # Use embedded wfdriver to receive events
    instance: !function {}

#input: !http-in { port: 8888 }

#input: !stdio-in {}

collector: !multi
    children:        
        aggregator : !flush
            period: 300
            collector: !aggregator           
                storage : !service         
                    name: storage
                    instance: !include { path:
/opt/wfrog/wfcommon/config/storage.yaml }  
        current : !flush
            period: 10
            collector: !xmlfile
                path: /tmp/current_conditions.xml
                storage : !service
                    name: storage

embed:
    wfdriver: { config: /opt/wfrog/wfdriver/config/embedded.yaml }
    # wfrender: { config: /opt/wfrog/wfrender/config/wfrender.yaml }

logging:
    level: info    
    handlers:
        default:
            level: debug
            handler: !include 
                path: /opt/wfrog/wfcommon/config/loghandler.yaml
                variables:
                    process: wflogger

/var/log/wfrender.log 

2010-05-29 13:02:30,758 INFO [renderer.http] Started server on port 8080
2010-05-29 13:56:40,517 INFO [renderer.http] Started server on port 8080

/var/log/wflogger.log
2010-05-29 14:11:09,166 INFO [station.wmrs200] Wind batteryOk: True,
direction: 11 (247/WSW), gust: 0 m/s, avg. speed: 0 m/s
2010-05-29 14:11:09,229 INFO [station.wmrs200] Wind batteryOk: True,
direction: 11 (247/WSW), gust: 0 m/s, avg. speed: 0 m/s
2010-05-29 14:11:15,415 INFO [station.wmrs200] Temperature th1  Temp.: 25.7
C (Steady), Humidity: 33 % (Poor), Dew Point: 9 C
2010-05-29 14:11:17,414 INFO [station.wmrs200] Temperature thInt  Temp.:
26.4 C (Steady), Humidity: 33 % (Poor), Dew Point: 9 C
2010-05-29 14:11:17,857 INFO [station.wmrs200] Barometer Forecast:
PartlyCloudy, Absolute pressure: 1000.0 mb, Sea Level Pressure: 1000.0
2010-05-29 14:11:18,913 INFO [station.wmrs200] Clock 1/1/2007 15:45, power:
0, Powered: True, Battery: True, RF: True
2010-05-29 14:11:22,547 INFO [station.wmrs200] Barometer Forecast:
PartlyCloudy, Absolute pressure: 1000.0 mb, Sea Level Pressure: 1000.0
2010-05-29 14:11:25,415 INFO [station.wmrs200] Wind batteryOk: True,
direction: 11 (247/WSW), gust: 0 m/s, avg. speed: 0 m/s
2010-05-29 14:11:35,413 INFO [station.wmrs200] Temperature thInt  Temp.:
26.4 C (Steady), Humidity: 32 % (Poor), Dew Point: 9 C
2010-05-29 14:11:36,539 INFO [station.wmrs200] Temperature thInt  Temp.:
26.4 C (Steady), Humidity: 32 % (Poor), Dew Point: 9 C

Create a alternative way of obtaining current data from last stored measure 
compatible with current system (using xml file).

The need for this improvement comes from:
- The xml file cannot be accessed when the render is on a different system than 
the logger.
- When reporting data to sites like www.meteoclimatic.com reported data must be 
coherent (current - daily - monthly - yearly). Reporting current data from the 
xml file might not be coherent (min / max values) with those stored. Such 
differences produce alarms in sites like www.meteoclimatic.com.

Develop  a caching wrapper around the storage is to improve rendering
performance of most requests (using latest data).

- Maintains a FIFO list of samples
- Keeps only N last samples
- Updated on writes (put)
- Ideally updated on traversal with to_time>=first_val. Define algorithm...

Rain should be accumulative starting on 0 and adding the amount fallen on
each period. I like the way it is implemented in meteoclimatic.com. 

Optionally rain rate could be shown as vertical bars.

New  staition (direct render, WMR200). http://87.228.70.110/


Thanks for your work

Create a renderer to report meteo data to www.weatherunderground.com 

Unify the configuration mecanism used in wfrog. Currently config and yaml
are used. 

One proposal is to use yaml conf for wflogger as well as the wfdriver
process in the future. Needs some discussion...

Some values, like database connection, etc. should be in a unique
configuration file.

The new feature of sending e-mail when critical messages appear is not
compatible with python 2.5

Publish as debian package in an official repository

Currently wfrog only has only aggregation functions (Max, Min, Last, etc.). 
HeatIndex, Windchill and such scalar values are calculated created an 
equivalent aggregation function like MaxHeatIndex.

We should separate scalar functions from aggregation functions, allowing 
combination of both. Calculated scalar values should also be available to be 
shown as current data.

Scalar functions could be:
- windchill
- heatIndex
- humidex
- cloud base

I believe it would be good to always draw a line, even if measures are 0.
The y axis could start at -1, likewise as when some measures during the
period are > 0.