Cumulus Support

Posted: **Mon 16 Oct 2023 10:39 am**

While charting webtag values I made a DAILY CustomLog with the following webtags:

<#avgtemp> <#windAvg> <#rmidnight> <#ET>

A DAILY CustomLog creates a log with the momentane values of a webtag (as far as I understood from a previous communication here). Now, I get the following values on 15/10 so that means (values reported in the night of 15 to 16 october at midnight):

Code: Select all

Logfile entry: 15-10-23;7,6 0,0 0,0 0,98
<#avgtemp> = 7.6
<#windAvg> = 0.0 
<#rmidnight> = 0.0
<#ET> = 0.98 (reported a 1.0)

As far as I understand this these values represent:

The average of the temperature on the 15th
The average of the windspeed on the 15th
The rain since midnight for the 15th (so starting midnight 14/15 to midnight 15/16
Evapotranspiration for the whole of the 15th

Obviously there is an error somewhere as 1) is correct but 2) and 3) definitely are not (should be some number for wind and 8.9 for the rain. 4) ET is correct for the 15th.

So, apparently some values already report a value for the 16th (have been reset already?) and some report correctly for the 15th.
Do I see this correct or is there another interpretation?

Posted: **Mon 16 Oct 2023 11:05 am**

Two effects here.

Rain since midnight was being reset before the EOD processing - fixed for next release.

Wind average is falling foul of some web tag logic, because this value is calculated on the fly when required rather than returning a stored variable value.

First problem is that the time of course is after roll-over, so it would attempt to calculate the value for the wrong day.
But the value is set to zero for a short period after rollover to avoid "silly" values due to the very small numbers involved - average over 0.01 seconds for instance.

I'll have to think about how to resolve average wind speed issue!

Posted: **Mon 16 Oct 2023 11:13 am**

OK, Thnx.

Cumulus Support

strange Webtag values

strange Webtag values

Re: strange Webtag values

Re: strange Webtag values