Historical data

[nitrx]

Steve thanks for the great update A lot of things are possible I think.

I wondered why the 'historical data' go back for 'only' seven days <#RecentOutsideTemp d=365> will not work I see (a year back) is this done on purpose ?

[steve]

I wondered why the 'historical data' go back for 'only' seven days <#RecentOutsideTemp d=365> will not work I see (a year back) is this done on purpose ?

Mainly for performance reasons - memory usage and startup speed. I thought 7 days was a useful period that wouldn't impact much on either. Loading in a year's worth of data would require getting on for 100MB of RAM and slow the startup considerably.

[nitrx]

I wondered why the 'historical data' go back for 'only' seven days <#RecentOutsideTemp d=365> will not work I see (a year back) is this done on purpose ?

Mainly for performance reasons - memory usage and startup speed. I thought 7 days was a useful period that wouldn't impact much on either. Loading in a year's worth of data would require getting on for 100MB of RAM and slow the startup considerably.

That's a fair reason, I asked it because I would use it as temperature (andso-on) last year.

[steve]

If I ever get around to adding an SQL database, that sort of thing should hopefully be possible, as it shouldn't then be necessary to load it all into memory to get reasonable searching speed. Not that I have any figures to back that up...

[Matt.j5b]

Great feature Steve, very useful.

One question Steve, does the data for this feature all come from Cumulus software (including from the logger?) and not rely on the state of updating my site and will still work fine if say I pick 24 hrs and my site my offline at that 24 hrs ago. I ask this as I don't always update my site so I wondering if the usage of these tag would work fine in this way.

[steve]

One question Steve, does the data for this feature all come from Cumulus software (including from the logger?)

Yes. It doesn't rely in any way on anything that has previously been uploaded to your web site.

The way it works is: at start up it loads into memory the last 7 days worth of data from the monthly log file(s). It then adds any logger data that it downloads to that. Then it adds a new entry once a minute while it's running, all the time deleting from the list any data that's more than a week old. When it processes a web tag, it searches the list looking for the nearest entry to that specified by the web tag parameters.

[Matt.j5b]

Thats sounds good. Thanks for your reply Steve. You have been busy, its a great feature.