WSWIN Export oddity - one record every 5 minutes, instead or

Discussion of the Meteohub software package

Moderator: Mattk

Post Reply
skyewright
Platinum Boarder
Platinum Boarder
Posts: 873
Joined: Fri Jan 25, 2008 6:27 pm
Location: Isle of Skye, Scotland

WSWIN Export oddity - one record every 5 minutes, instead or

Post by skyewright »

Hi,

I've been doing some experiments with the WSWIN export, which includes observing how the export handles cases where a sensor drops out for a while. I decided to re-generate the 'export' files to test a theory.

The earlier export files, prepared with (I'm pretty sure) the same version of Meteohub had one csv record for each minute.

The newly generated set of export files only have one csv record every 5 minutes!

Any idea why this should have changed?

How do I get it back to producing a CSV with one record per minute?
User avatar
admin
Platinum Boarder
Platinum Boarder
Posts: 7953
Joined: Mon Oct 01, 2007 10:51 pm

Re:WSWIN Export oddity - one record every 5 minutes, instead

Post by admin »

this has been changed to reduce system load. you can switch it back to "min1" by editing this file:

meteohubpro:/home/meteohub# cat wswinrecompute
#!/bin/sh
#
(/usr/bin/nice /home/meteohub/wmr928eval -n -c min5 -w /data/weather/ -s /home/meteohub/wmr928eval.conf -e /home/meteohub/wswin.conf)&


will be changed back to "min1" with the next update.
skyewright
Platinum Boarder
Platinum Boarder
Posts: 873
Joined: Fri Jan 25, 2008 6:27 pm
Location: Isle of Skye, Scotland

Re:WSWIN Export oddity - one record every 5 minutes, instead

Post by skyewright »

admin wrote:will be changed back to "min1" with the next update.
Thank you. I'll probably wait for that (I have copies of the 1 minute csvs if I need them and at this stage its no problem at all to delete and recreate the data I have in WSWIN itself).

PS. The theory I was testing related to a possible difference in handling of sensor drop out between 'on going' data export and 'rebuild from scratch' export.

A couple of evenings ago a TH sensor dropped out for a few hours[1] and instead of what I seen before with 'built from scratch' files (i.e. 'straight line' repeats of last noted value during drop out - which is perfectly reasonable, except maybe for rainfall) the T and H both recorded in the 'on going' CSV as zero during the dropout.

The test was to see what a fresh 'from scratch' set of CSVs gave for the same times. The result (in the 5 minute CSVs) was 'straight lines' rather than zeros.


[1] Because I am using RFXCOM to pick up multiple sensors transmitting on the same channels, fractional differences in transmit interval mean that inevitably there are occasional short periods when the moment of transmission for two sensors on the same channel happen to drift together. When that happens one or both (depending on relative signal strength?) drop out for a while, then return as the moments of transmission drift apart again.

N.B. This is NOT an RFXCOM fault, it only happens because I'm reading from both WMR200 and WMR928 (including five '3' channel sensors) and thus am doubling up on some channels. If I only had a standard set of sensors the dropouts would not occur (and even with my multiple sensor 'misuse' they only occur rarely).
Post Reply