wviewweather.com

pata · Joined: 27 Oct 2005 Posts: 21 Location: Long Island, NY

I've just noticed a problem with my wunderground wind speed. (KNYFARMI4). Since I upgraded to version 3.1.2 yesterday and now tonight with 3.1.3, my reported wind speed to wunderground is in the hundreds MPH. Where should I check for this problem? With this version (3.1.3) the only file I've modified is images-user.c to add some custom graphs. I've not changed any other files. I'm running on FC3.

Pat

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Very odd since I'm running 3.1.3 too and my WU wind speed looks fine (KTXCOLLI1)...

pata · Joined: 27 Oct 2005 Posts: 21 Location: Long Island, NY

Hi Mark. I've also noticed that the wind direction is always North. This problem seems to have started with 3.1.2 which I installed on Saturday. 3.1.3 did not fix it for me. When I get home tonight, I'll try a fresh install to see if the problem goes away. Is there anything I should check?? Or is there anything different I should do to uninstall/re-install. With 3.1.3, I just did a configure, make and make install. Also, I did upgrade radlib from 2.6.1 to 2.6.2.

Thanks,

Pat

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Always run wviewconfig before starting wview after an upgrade. But I doubt that is your problem...

pata · Joined: 27 Oct 2005 Posts: 21 Location: Long Island, NY

Sorry, I forgot to list that. The sequence I go through is 1) configure 2) make 3) make install and then 4) wviewconfig

Pat

pata · Joined: 27 Oct 2005 Posts: 21 Location: Long Island, NY

Interesting note. I looked at the comma delimited file from wunderground for today and is listed below. It's still showing wview-2.0.0. Does this lead to the conclusion that for some reason the wunderground files did not update? The compile seemed to go smoothly for both 3.1.2 and 3.1.3. Where do the object files get copied to, as I will remove them manually.

Pat

2006-02-06 00:00:04,36.0,1.7,29.54,North,29378,333,0,46,0.08,,,,wview-2.0.0,
2006-02-06 00:30:04,35.5,0.0,29.55,North,29391,220,9,49,0.10,,,,wview-2.0.0,
2006-02-06 01:00:04,35.2,0.0,29.57,North,29406,237,0,49,0.10,,,,wview-2.0.0,
2006-02-06 01:30:04,35.0,0.0,29.59,North,29423,75,2,47,0.09,,,,wview-2.0.0,
2006-02-06 02:00:04,34.7,0.0,29.60,North,29437,258,4,47,0.09,,,,wview-2.0.0,
2006-02-06 02:30:04,34.2,0.0,29.61,North,29447,186,0,48,0.07,,,,wview-2.0.0,
2006-02-06 03:00:04,34.0,0.0,29.61,North,29446,169,0,50,0.10,,,,wview-2.0.0,
2006-02-06 03:30:04,34.0,0.0,29.62,North,29454,55,1,51,0.10,,,,wview-2.0.0,
2006-02-06 04:00:04,34.2,0.0,29.63,North,29464,215,6,50,0.09,,,,wview-2.0.0,
2006-02-06 04:30:05,34.7,0.0,29.63,North,29471,160,1,47,0.09,,,,wview-2.0.0,
2006-02-06 05:00:04,34.7,0.0,29.64,North,29482,64,0,47,0.09,,,,wview-2.0.0,
2006-02-06 05:30:04,34.0,0.0,29.65,North,29485,186,2,49,0.09,,,,wview-2.0.0,
2006-02-06 06:00:04,33.5,0.0,29.65,North,29485,256,2,49,0.10,,,,wview-2.0.0,
2006-02-06 06:30:04,33.2,0.0,29.65,North,29487,193,0,48,0.07,,,,wview-2.0.0,
2006-02-06 07:00:04,32.9,0.0,29.66,North,29500,308,2,50,0.11,,,,wview-2.0.0,
2006-02-06 07:30:04,33.0,0.0,29.68,North,29516,209,0,49,0.10,,,,wview-2.0.0,
2006-02-06 08:00:04,33.5,0.0,29.68,North,29520,247,2,50,0.10,,,,wview-2.0.0,
2006-02-06 08:30:04,34.9,0.0,29.69,North,29525,278,1,45,0.13,,,,wview-2.0.0,
2006-02-06 09:00:04,35.7,0.0,29.69,North,29528,299,0,47,0.11,,,,wview-2.0.0,
2006-02-06 09:30:04,37.0,0.0,29.69,North,29532,306,6,45,0.11,,,,wview-2.0.0,
2006-02-06 10:00:05,37.5,0.0,29.70,North,29535,93,4,41,0.11,,,,wview-2.0.0,
2006-02-06 10:30:05,37.2,0.0,29.70,North,29542,193,6,35,0.14,,,,wview-2.0.0,
2006-02-06 11:00:05,36.2,0.0,29.71,North,29543,352,2,39,0.15,,,,wview-2.0.0,
2006-02-06 11:30:05,38.2,0.0,29.69,North,29530,359,4,36,0.15,,,,wview-2.0.0,
2006-02-06 12:00:05,39.0,0.0,29.70,North,29533,189,4,31,0.13,,,,wview-2.0.0,

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

Typically /usr/local/bin - but that should be OK (check the dates for the wview daemons). The 2.0.0 stamp is not a good thing - make sure when you shutdown wview (always via the start script) that all IPC data is cleaned up (see the UM Troubleshooting section). I do recall you installing a newer version and then "downgrading"...

If you are still having problems, I suggest moving your /etc/wview and /var/wview directories some place safe and then doing a fresh install via "make install-env".

Mark

pata · Joined: 27 Oct 2005 Posts: 21 Location: Long Island, NY

I have resolved this problem. I manually deleted the wview files in '/usr/local/bin'. I then did configure, make, make install and wviewconfig. When I restarted wview, I noticed that the wunderground pid did not start. When I looked at the log file, I could not find the wunderground starting. After re-reading the UM and carefully looking at the output from the wviewconfig, I noticed the warning to run 'configure --enable-wunderground' is a must. I have not been doing this. I re-did the configure with the option, did another make, make install and wviewconfig. When I restarted wview, all is well. The log file now shows wunderground starting normally. I looked at the wunderground page and my data is now normal.

In summary - it is a must to read all instructions and then read them again.

Now if only there were a way to delete the bad records from wunderground . . . Sad

Thanks, Mark, for your support and patience.

Pat

THogland · Joined: 26 Sep 2005 Posts: 33

You *can* have them deleted - e-mail the POC for the personal weather stations. (I had to do this a while back...)

BUT - you need to be able to tell them exactly what values in exactly which data to remove - in my case it was erroneous wind gusts in one day.

obarlow · Posted: Mon Feb 13, 2006 12:22 pm Post subject: Wind in Hundreds MPH

I upgrade to 3.1.4 from 3.1.3 and the wind speed is in hundreds of MPH. I did not re-run wviewconfig (I will from now on). Should I delete the files in /usr/bin and re-install?

Thanks,
Oscar

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

The thing pata missed before was the "--enable-wunderground" argument as part of her configure script invocation, so an old wvwunderd daemon was being used. If you enabled it in the configure, the old one should be copied over in /usr/local/bin (or wherever your prefix is).

Look at the dates of the daemons.

Mark

IslandLife · Joined: 30 Jul 2005 Posts: 58 Location: Guam (USA)

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

wvwunderd.pid - the config file is wvwunder.conf and the executable is wvwunderd - noted on the home page of wview and throughout the manual.

Was Wunderground data ever uploaded? Do you need to copy the wview start script from the distro to your Mac again (as described in the Quick Start Guide for MacOSX)?

Of course your configure actually looks like:
configure --enable-station-vpro --enable-wunderground

If you think all of this is correct, post your startup log - are there entries for wvwunderd?

Mark

IslandLife · Joined: 30 Jul 2005 Posts: 58 Location: Guam (USA)

mteel · Joined: 30 Jun 2005 Posts: 435 Location: Collinsville, TX

What is the output of (from a shell prompt):

ls -al /opt/local/bin/wvwunderd (assuming a prefix of /opt/local)

If it is not there and you configured with --enable-wunderground, then the build must have failed.

If it is there and you have copied the latest start script from the distro (what you described and I referred to earlier), then I am at a loss.

You may need to post your entire startup log if that is in fact the case...

Mark