Re: [Xastir] Wx Alerts
On Jun 20, 2008, at 19:12, Tom Russo wrote: Chip, what are the time stamps on your wx_alert log files? Sorry, been out of touch for a couple of days ... Jun 20 for current log file, Jun 20 for the first rotate file, Apr 12 for the next, and Feb 29 for the oldest. -- Chip ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
I haven't run wxalert -> RF in some time. There were several people complaining about the traffic on THEIR QUIET channel, plus there were several relays not configured properly in the area and even with one hop request sent out, the messages were bounced all over the place many times. Just try and gate all messages from one WX stn and monitor from there. 73 from 807, Richard, N6NKO Curt, WE7U wrote: On Fri, 20 Jun 2008, Tom Russo wrote: Bleah. That seems like a bad idea to me, given that other log files are meant to be just that. It was the first step in making it possible to have Xastir shut down or crash and being able to start it up with the same info on the screen. Sorry you don't like it. Actually, another possibility is that since the actual value of "relatively current" is "15 days" as hard-coded in util.c's "load_wx_alerts_from_log_working_sub", that these ancient alerts are still just considered relative current. It's because there's a 1 to 31 day entry in the weather alerts, so we split the difference and go 15 back only, if possible. There may be holes in the logic as you pointed out, like if weather alerts aren't coming in regularly, there may be both old and new alerts in the same log file. It should skip any log files that have an old timestamp. I've noticed some odd changes in wx alert behavior lately --- most notably, while I *AM* configured to gate WX alerts from net to RF (because our local Igate went down and there is now nobody else doing so in this region), Xastir NEVER gates them anymore, and it used to. I don't igate, so haven't noticed that. It's possible I or someone else broke that quite a while back. I don't think that part of the code has been worked on in some months, but the Changelog should say. ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Fri, 20 Jun 2008, Tom Russo wrote: > Bleah. That seems like a bad idea to me, given that other log files are > meant to be just that. It was the first step in making it possible to have Xastir shut down or crash and being able to start it up with the same info on the screen. Sorry you don't like it. > Actually, another possibility is that since the actual value of "relatively > current" is "15 days" as hard-coded in util.c's > "load_wx_alerts_from_log_working_sub", that these ancient alerts are still > just considered relative current. It's because there's a 1 to 31 day entry in the weather alerts, so we split the difference and go 15 back only, if possible. There may be holes in the logic as you pointed out, like if weather alerts aren't coming in regularly, there may be both old and new alerts in the same log file. It should skip any log files that have an old timestamp. > I've noticed some odd changes in wx alert behavior lately --- most notably, > while I *AM* configured to gate WX alerts from net to RF (because our local > Igate went down and there is now nobody else doing so in this region), Xastir > NEVER gates them anymore, and it used to. I don't igate, so haven't noticed that. It's possible I or someone else broke that quite a while back. I don't think that part of the code has been worked on in some months, but the Changelog should say. -- Curt, WE7U. archer at eskimo dot com http://www.eskimo.com/~archer Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Fri, Jun 20, 2008 at 03:40:32PM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, 20 Jun 2008, Tom Russo wrote: > > > I'm real confused by this. The log files aren't supposed to be read in > > automatically on restart. > > util.c: > > // Restore weather alerts so that we have a clear picture of the > // current state. Do this before we start the interfaces. Only > // reload if the log files datestamps are relatively current. Bleah. That seems like a bad idea to me, given that other log files are meant to be just that. I would never have assumed that simply enabling logging would also mean that the logs were sucked in upon restart. But it does mean that Chip should be able to clear out ancient alerts by removing the log files. And it does suggest that the checking of timestamps is busted. Since the files get rotated after a while, it's possible that their timestamps are being changed by the rotation process, thereby making them appear "relatively current" when they're in fact ancient. I don't think most systems change the date stamp if you just rename a file (that doesn't happen on any system I have access to), but perhaps that's the key on Chip's system? Chip, what are the time stamps on your wx_alert log files? > // Check timestamps on each file in turn. If relatively > // current, read them in the correct order: Actually, another possibility is that since the actual value of "relatively current" is "15 days" as hard-coded in util.c's "load_wx_alerts_from_log_working_sub", that these ancient alerts are still just considered relative current. I've noticed some odd changes in wx alert behavior lately --- most notably, while I *AM* configured to gate WX alerts from net to RF (because our local Igate went down and there is now nobody else doing so in this region), Xastir NEVER gates them anymore, and it used to. I don't know if this is a change in xastir or some subtle change in the alert text that leads xastir to not recognize it as something it is supposed to gate --- when I turn on debugging it seems to claim that it does not find the name in my nws-stations.txt file (even though that IS there). Perhaps this is related, and somehow the deletion isn't being processed right? But I can't replicate the behavior Chip's seeing, as I have seen that alerts get expired properly on all of my stations. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "It's so simple to be wise: just think of something stupid to say and then don't say it." --- Sam Levinson ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Fri, 20 Jun 2008, Tom Russo wrote:
> I'm real confused by this. The log files aren't supposed to be read in
> automatically on restart.
util.c:
// Restore weather alerts so that we have a clear picture of the
// current state. Do this before we start the interfaces. Only
// reload if the log files datestamps are relatively current.
//
// Check timestamps on each file in turn. If relatively
// current, read them in the correct order:
// wx_alert.log.3
// wx_alert.log.2
// wx_alert.log.1
// wx.alert.log
//
void load_wx_alerts_from_log(void) {
I guess that last part of the comment answers the question I had.
--
Curt, WE7U. archer at eskimo dot com
http://www.eskimo.com/~archer
Lotto: A tax on people who are bad at math. - unknown
Windows: Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me: I picked the coordinate system!"
___
Xastir mailing list
Xastir@xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Fri, Jun 20, 2008 at 03:31:20PM -0700, we recorded a bogon-computron collision of the <[EMAIL PROTECTED]> flavor, containing: > On Fri, 20 Jun 2008, Chip Griffin wrote: > > > I haven't tried that yet, but if I quit and restart Xastir a whole bunch of > > expired weather alerts appear. I understand reading in the log file, but > > shouldn't it automatically filter out or otherwise dispense with ones that > > are > > expired??? > > It tries to, but as I recall there's not enough date information in > the packets. Xastir has to make judgement calls whether it's a > future alert, and expired alert, or a present alert. > > I suppose we could check timestamps on the log files to determine > whether they're too old and we shouldn't read them in at all. I'm > not sure whether we do that now: I'd have to look at the code. > > If you don't run Xastir often and it doesn't check the timestamps on > those logfiles, the best option would be to turn off "WX Alert > Logging". I'm real confused by this. The log files aren't supposed to be read in automatically on restart. They're LOGS not saved state. You can pull them in by selecting an option in the File menu, but it's not supposed to happen without your specifically taking action to do it. This sounds like something else fishy. I'm not aware of anything that is supposed to save WX alerts between runs. They're supposed to be processed on receipt only. -- Tom RussoKM5VY SAR502 DM64ux http://www.swcp.com/~russo/ Tijeras, NM QRPL#1592 K2#398 SOC#236 AHTB#1 http://kevan.org/brain.cgi?DDTNM "It's so simple to be wise: just think of something stupid to say and then don't say it." --- Sam Levinson ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Fri, 20 Jun 2008, Chip Griffin wrote: > I haven't tried that yet, but if I quit and restart Xastir a whole bunch of > expired weather alerts appear. I understand reading in the log file, but > shouldn't it automatically filter out or otherwise dispense with ones that are > expired??? It tries to, but as I recall there's not enough date information in the packets. Xastir has to make judgement calls whether it's a future alert, and expired alert, or a present alert. I suppose we could check timestamps on the log files to determine whether they're too old and we shouldn't read them in at all. I'm not sure whether we do that now: I'd have to look at the code. If you don't run Xastir often and it doesn't check the timestamps on those logfiles, the best option would be to turn off "WX Alert Logging". -- Curt, WE7U. archer at eskimo dot com http://www.eskimo.com/~archer Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Jun 20, 2008, at 00:42, Curt, WE7U wrote: On Thu, 19 Jun 2008, Chip Griffin wrote: Where are weather alerts stored? ~/.xastir/logs/wx_alert.log* Got it. What would cause some to be loaded and not go away? I don't know. It could be a bug in Xastir, or perhaps somebody replayed a log that sent them out again or they're otherwise being transmitted after they expired. Kill Xastir, remove those files, and restart. If they appear again sometime soon, somebody is sending them out. I haven't tried that yet, but if I quit and restart Xastir a whole bunch of expired weather alerts appear. I understand reading in the log file, but shouldn't it automatically filter out or otherwise dispense with ones that are expired??? 73, --de Chip (N1MIE) FN41bn ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
On Thu, 19 Jun 2008, Chip Griffin wrote: > Where are weather alerts stored? ~/.xastir/logs/wx_alert.log* > What would cause some to be loaded and not go > away? I don't know. It could be a bug in Xastir, or perhaps somebody replayed a log that sent them out again or they're otherwise being transmitted after they expired. Kill Xastir, remove those files, and restart. If they appear again sometime soon, somebody is sending them out. -- Curt, WE7U. archer at eskimo dot com http://www.eskimo.com/~archer Lotto: A tax on people who are bad at math. - unknown Windows: Microsoft's tax on computer illiterates. - WE7U. The world DOES revolve around me: I picked the coordinate system!" ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
I had a telecon late last week where we were told that several NWS servers were recently compromised and had to recertify before coming back online. I'll contact the appropriate folks and see if I can mirror the data for them. Also, there's a real big effort in NWS to fix problems with their geospatial accuracy and precision. Curt, you'd love some of the discussions on position ambiguity. I've pulled out some of our old e-mails on the topic and paraphrased them to help kickstart the solutions... gerry David Flood wrote: Doing a quick nose around their web site it looks like they shut down http access to those files because I get a page that mentions security. So we may have to use ftp instead once we figure out where they moved them to. Dave KD7MYC -Original Message- From: Dana Rawding <[EMAIL PROTECTED]> Sent: Nov 12, 2007 7:02 PM It appears that the script is currently broken as the following files are no longer available on the weather.gov server: http://www.weather.gov/geodata/catalog/wsom/data/oz15de04.zip http://www.weather.gov/geodata/catalog/wsom/data/fz17ap07.zip http://www.weather.gov/geodata/catalog/wsom/data/mz30nv06.zip http://www.weather.gov/geodata/catalog/wsom/data/z_11mr07.zip ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir -- Gerry Creager -- [EMAIL PROTECTED] Texas Mesonet -- AATLT, Texas A&M University Cell: 979.229.5301 Office: 979.862.3982 FAX: 979.862.3983 Office: 1700 Research Parkway Ste 160, TAMU, College Station, TX 77843 ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
Doing a quick nose around their web site it looks like they shut down http access to those files because I get a page that mentions security. So we may have to use ftp instead once we figure out where they moved them to. Dave KD7MYC -Original Message- >From: Dana Rawding <[EMAIL PROTECTED]> >Sent: Nov 12, 2007 7:02 PM >It appears that the script is currently broken as the >following files are no longer available on the weather.gov server: > >http://www.weather.gov/geodata/catalog/wsom/data/oz15de04.zip >http://www.weather.gov/geodata/catalog/wsom/data/fz17ap07.zip >http://www.weather.gov/geodata/catalog/wsom/data/mz30nv06.zip >http://www.weather.gov/geodata/catalog/wsom/data/z_11mr07.zip ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Re: [Xastir] Wx Alerts
When you built Xastir on the Leopard machine did you run the get- NWSdata script. It appears that the script is currently broken as the following files are no longer available on the weather.gov server: http://www.weather.gov/geodata/catalog/wsom/data/oz15de04.zip http://www.weather.gov/geodata/catalog/wsom/data/fz17ap07.zip http://www.weather.gov/geodata/catalog/wsom/data/mz30nv06.zip http://www.weather.gov/geodata/catalog/wsom/data/z_11mr07.zip Not an OS X problem. Dana N1OFZ On Nov 11, 2007, at 6:19 PM, Chip Griffin wrote: I noticed an oddity. I have two machines that run Xastir full-time. On one I am currently showing a Freeze alert for Suffolk County on Long Island (this is the Mac PPC Mini, running OS X 10.4.10 and Xastir v1.9.1 with Imagemagick, libProj, GeoTiff, GDAL/OGR, Shapelib, PCRE, dbfawk, map caching, rtree and libcurl. On the other machine the alert is notably absent. I'm curious why I'm not seeing the alerts (it is in the weather alert window and it is an icon on the map, just not the county highlighting. This is a Mac Intel Mini running OS X 10.5 and Xastir v1.9.2 with GPSMan, Graphicsmagick, libProj, GeoTiff, Shapelib, PCRE, dbfawk, map caching, rtree, and libcurl. (Xastir details via the "about" window.) What I see different is: Mini PPCMini Intel v1.9.1 v1.9.2 ImageMagick GraphicsMagick - GPSMan GDAL/OGR- Other things appear to be the same. I thought maybe it was due to the newer config (the Intel Mini with Leopard) not having the XBM files, but I see those are in both locations. I was watching the PPC and noticed it was loading a shapefile with name 'z_10fe06.shp' that I wasn't seeing on the Intel machine. So I searched and couldn't find that file. I found it in the Counties directory on the PPC machine. I noticed the list of shape (and other) files was a bit shorter on the Intel machine. So I copied the files over between the two. I'm wondering where they came from and why I had so many on the PPC machine that weren't on the Intel machine. With a quit and restart of Xastir I am now seeing the alert, so I am certain it is related to the missing county shape file. See the below output for more details of which files were there (not overwritten) and which had to be copied from the older machine. 73, --de Chip (N1MIE) FN41bn /usr/local/share/xastir/Counties/c_16mr06.dbf not overwritten /usr/local/share/xastir/Counties/c_16mr06.shp not overwritten /usr/local/share/xastir/Counties/c_16mr06.shx not overwritten fz10mr06.dbf -> /usr/local/share/xastir/Counties/fz10mr06.dbf fz10mr06.shp -> /usr/local/share/xastir/Counties/fz10mr06.shp fz10mr06.shx -> /usr/local/share/xastir/Counties/fz10mr06.shx /usr/local/share/xastir/Counties/fz24my06.dbf not overwritten /usr/local/share/xastir/Counties/fz24my06.shp not overwritten /usr/local/share/xastir/Counties/fz24my06.shx not overwritten /usr/local/share/xastir/Counties/hz28au04.dbf not overwritten /usr/local/share/xastir/Counties/hz28au04.shp not overwritten /usr/local/share/xastir/Counties/hz28au04.shx not overwritten mz10ja06.dbf -> /usr/local/share/xastir/Counties/mz10ja06.dbf mz10ja06.shp -> /usr/local/share/xastir/Counties/mz10ja06.shp mz10ja06.shx -> /usr/local/share/xastir/Counties/mz10ja06.shx /usr/local/share/xastir/Counties/oz15de04.dbf not overwritten /usr/local/share/xastir/Counties/oz15de04.shp not overwritten /usr/local/share/xastir/Counties/oz15de04.shx not overwritten ta14ja03.dbf -> /usr/local/share/xastir/Counties/ta14ja03.dbf ta14ja03.shp -> /usr/local/share/xastir/Counties/ta14ja03.shp ta14ja03.shx -> /usr/local/share/xastir/Counties/ta14ja03.shx tw14ja03.dbf -> /usr/local/share/xastir/Counties/tw14ja03.dbf tw14ja03.shp -> /usr/local/share/xastir/Counties/tw14ja03.shp tw14ja03.shx -> /usr/local/share/xastir/Counties/tw14ja03.shx w_28fe06.dbf -> /usr/local/share/xastir/Counties/w_28fe06.dbf w_28fe06.shp -> /usr/local/share/xastir/Counties/w_28fe06.shp w_28fe06.shx -> /usr/local/share/xastir/Counties/w_28fe06.shx z_10fe06.dbf -> /usr/local/share/xastir/Counties/z_10fe06.dbf z_10fe06.shp -> /usr/local/share/xastir/Counties/z_10fe06.shp z_10fe06.shx -> /usr/local/share/xastir/Counties/z_10fe06.shx z_12fe06.dbf -> /usr/local/share/xastir/Counties/z_12fe06.dbf z_12fe06.shp -> /usr/local/share/xastir/Counties/z_12fe06.shp z_12fe06.shx -> /usr/local/share/xastir/Counties/z_12fe06.shx z_14fe06.dbf -> /usr/local/share/xastir/Counties/z_14fe06.dbf z_14fe06.shp -> /usr/local/share/xastir/Counties/z_14fe06.shp z_14fe06.shx -> /usr/local/share/xastir/Counties/z_14fe06.shx z_16mr06.dbf -> /usr/local/share/xastir/Counties/z_16mr06.dbf z_16mr06.shp -> /usr/local/share/xastir/Counties/z_16mr06.shp z_16mr06.shx -> /usr/local/share/xastir/Counties/z_16mr06.shx ___ Xastir mailing list Xastir@xastir.org http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir _
