Suspect bug <#RecentUV>

[nossis]

I have found a problem with my version of Cumulus (1.9.4 build 1085)
I have created a big long webpage for the recent history as half hourly observations. (Even managed to get some small amount of JScript processing to convert the bearing to words direction eg NNW, thanks to the cumulus forum for the tips)
Part of this contains the webtag <#RecentUV> the issue is with a previous readings for that webtag, for example say <#RecentUV h=2 m=30> (2 hours and 30 min ago)
My process of events is as follows:
Cumulus processes the file and stores it locally (on my computer and not pushed to FTP every 10 minutes) Cumulus is set to update all web pages every 10min.
Cumulus toolbox then uploads it just after the half hour or hour time throughout the day. This way I get a half hourly obs page with the obs done at the right times. (not every 10 min)
What I have found is that when I manually choose "web update" in cumulus, the <#RecentUV h=2 m=30> gives the same data as <#RecentSolarRad h=2 m=30>
Now if I let Cumulus process automatically, it appears to work. That is, it shows the UV index value correctly.

Here is what I have found.
Checked the realtime data files and all looks Ok.
Cumulus graphs show fine. All other webtags related to UV index yield expected data.
If I run a test to a text file using Cumulus and just a sample spread of RecentUV times it gives the same result of showing the Solar Rad data values. When manually doing web update.
After letting it run for a while automatically (as described above), and getting good UV expected values, as soon as I choose Web update all the good UV index values are wiped and replaced with the solar Rad values.
Here is my test files output here
http://members.iinet.net.au/~nossis/wea ... output.txt

Here is the text file used to generate it the test
http://members.iinet.net.au/~nossis/wea ... s_test.txt

Here is my test obs page
http://members.iinet.net.au/~nossis/weather/obs.htm

To me the issue lies in how Cumulus is processing the web tag as everything else appears and behaves as excepted. And in saying that it is only when a "click on web update" is undertaken. If let it run normally as scheduled, then it shows good values. (well it did today until I ran a manual update and then in converted all my good values back to bad ones again)

So... looking forward to finding out if the issue is just with me or if it is in fact a replicable problem.

[steve]

The code which processes web files (and hence web tags) is exactly the same whether it's invoked from the periodic timer or from the 'web update' menu item, so the bug isn't dependent on that, it's dependent on how the data for the recent UV value was stored, i.e. whether it came from the data logs at start up, or whether it was stored while Cumulus was running:

The bug is in the code which pre-loads the recent UV values from the data logs when Cumulus starts up; it puts the solar radiation value in twice, instead of putting the UV value in. I'll fix this in the next build - thanks for the report.

Steve

[nossis]

Hi Steve,

Thanks for the update.
Your support on a free product is once again sensational!
Have a top day!

[fchern]

Hi Barry - Would you be willing to share the HTML template for the Observations page? I'd really like to implement that.

Thanks,
Frank

[nossis]

UPDATE 30/1/14
Have also now added further to the observation page and learn't a bit more java coding. Figured out how to do apparent temp calcs. Thanks to this post for the source of the java code https://cumulus.hosiene.co.uk/viewtopic.p ... r+pressure
Wind speed and gust is sorted thanks to Steve for the latest build v1.9.4 b1088.
Updated the attached template file, freely use it and modify it to suit your needs.

UPDATE 23/1/14
Have now also added the recent UV since Steve has graciously fixed this webtag
New observeT.htm source file uploaded.


Ah sorry for the delay in getting back to this one... Sure can share!
I am quite sure there are better ways of doing this but for what it is worth...
The trick for me was to get it to only show at 30 minute intervals when I have a regular upload of 10 minutes from Cumulus. My solution was to use Cumulus Toolbox to do the upload, just after Cumulus has processed it. The other odd thing I found was that I had to set recent values webtags to not at for example 30 minutes past but 31minutes past. Then it gave me the right time stamp of 30 minutes on or past the hour.

The other thing I wanted was to show the wind direction as a word abbreviation (example NNW) and not a degree value. A bit of java code helped here from another source (in the script credit given)

Have attached my whole page for you.
The observations part of it is from about line 38 through to line 2465.
Since Steve has fixed the "recent UV" webtag bug (latest beta build 1086) A big thanks to Steve for this one. I am also keen to add that back in as well. Will repost my new page then too.
You will also need to setup a link to the new observation page on all your other pages. Mine is at line 22

So how mine works. Every 10 minutes Cumulus processes the file only. Tick the process box only.

Source file C:\cumulus\web\observeT.htm
Output file C:\cumulus\web\observe.htm

So this will process the file every 10 minutes as I had set my Cumulus software to do.
Using Cumulus toolbox I have a window of time from the turn of the hour, or 30 minutes past, and roughly 10 minutes after that to upload prior to Cumulus doing the next process of the file. (remember it processes every 10 minutes)
I have set Cumulus toolbox to upload it at 1 min past the half hour, or hour. That is to give it a bit of time for cumulus to process prior to uploading. So to set this up I added 48 jobs in toolbox to upload. (24 hours in a day x 2 for 30 minute intervals)

In toolbox
Source file C:\cumulus\web\observe.htm (or observe.htmtmp)
Target file observe.htm (as I had already setup toolbox to upload by default to the my weather folder at the website end.)

Just as I was typing this I realised a much easier method, use a batch file to FTP it and get it to run as a Windows scheduled task. This way you only have to create one script and get the Windows task to repeat the schedule. (I have done similar to upload my timelapse webcam stuff) Google gave me that answer on how to set that up. From a bath file I call a text file that has the FTP commands.

What I don’t like about it, in its current form, is that the dividers (24 hours) don’t follow the turn of midnight. I am not that clever to figure that one out (well... yet anyway). But at least it serves the purpose.
I also added a bit to the CSS script to the weatherstyle.css file

a:hover {
text-decoration: none;
color: #e2e2e2;
}

This makes the row highlight when hovering over it, bit easier to read when you’re looking for data in the list.

Hope at least some of it is useful.