#9 GHG Monitor not working

[Michael Foland]

In Products > GHG Monitor, when I go to look at transmitted products, it shows no configuration file loaded. I attempt to save the config, and can't do anything, and when I go to select Load Configuration, nothing pops up. The transmitted products that should show... I created a fake Winter Weather Advisory should "In Theory" should show, but it does not. Not sure what is happening here.

[Mike Romberg]

The whole GHG monitor thing (and other bits that use theVTEC active table) may be broken for a while. Much of that code depends upon products being stored in the AWIPS text database. That won't work now for obvoius reasons. There is no way (and won't be) to actually transmit any products. So, the hooks that the gfe has to look at these will not work. Maybe with practice mode (which I've not even looked at yet) it might work.

I may be able to simulate it at some point in the future.   However, I would like to get the other bits that are not working functional again.   Then maybe look at the whole VTEC thing.

[Michael Foland]

I think that comes with fixing a database because I can transmit and it
saves the product to the product folder. :)

On Mon, Apr 30, 2018, 7:49 PM Mike Romberg romberg@users.sourceforge.net
wrote:

The whole GHG monitor thing (and other bits that use theVTEC active table)
may be broken for a while. Much of that code depends upon products being
stored in the AWIPS text database. That won't work now for obvoius reasons.
There is no way (and won't be) to actually transmit any products. So, the
hooks that the gfe has to look at these will not work. Maybe with practice
mode (which I've not even looked at yet) it might work.

I may be able to simulate it at some point in the future. However, I would like to get the other bits that are not working functional again. Then maybe look at the whole VTEC thing.

---

• [tickets:#9] https://sourceforge.net/p/gfed/tickets/9/ GHG Monitor not
  working*

Status: open
Milestone: 1.0
Labels: Products
Created: Sun Apr 29, 2018 07:31 AM UTC by Michael Foland
Last Updated: Sun Apr 29, 2018 07:31 AM UTC
Owner: nobody

In Products > GHG Monitor, when I go to look at transmitted products, it
shows no configuration file loaded. I attempt to save the config, and can't
do anything, and when I go to select Load Configuration, nothing pops up.
The transmitted products that should show... I created a fake Winter
Weather Advisory should "In Theory" should show, but it does not. Not sure
what is happening here.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/gfed/tickets/9/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Mike Romberg]

The way the whole GHGMonitor/VTEC thing worked in the past was that when you hit "transmit" it copied the product to the transmit directory (which you can see is still working) and then called a script which was part of AWIPS to send it out over the MHS. This script is no longer there and this version of the gfe will never do this again. You can see the error message about the missing script on the terminal window when you press the transmit button.

The VTEC table used by the gfe for things like the GHGMonitor did not update this table at the point the transmit was done.   Instead, the gfe had hooks into the AWIPS MHS and would be notified when a new product arrived over the MHS.   At this point the gfe's VTEC decoder would be run and the VTEC database used by the GHGMonitor would be ubdated.

  This way you knew that the VTEC table showed the state of products that were in fact actually sucessfully transmitted.

    I may be able to wire things up so that this gfe just runs the vtec decoder when you press the transmit button.     It will still not be a "real" transmit.   But should simulate it.   This may not be that difficult to do.   I'll look into it.

[Mike Romberg]

I think I've managed to fix the GHGMonitor's configuration code. And I've also had some sucess with a standin for the AWIPS message handling system (MHS).

I added a blizzard watch (BZ.A) to the hazard grids and then created a WSW product. The VTEC line was in this product. I then pumped this product through the VTECDecoder which worked after I fixed a few python3 bugs. But I did have to tack on a few lines at the top of the product:

248
FNUS75 KBOU 092326
FWSBOU

I think this is an MND header (my memory is foggy).  The AWIPS MHS normally added this header and the VTECDecoder crashes without it.   The one above I copy/pasted blindly from something I found with google.  I have no idea at all if it is right.   But the VTECDecoder did run and did add a BZ.A to the active table.  So, a step in the right direction.

  However the GHGMonitor did not display anything.   I suspect that my header is not 100% correct and that it may be important in the operation of the GHGMonitor.   Do you know of any documentation which describes what these three header lines mean?  It is also possible that certain vtec codes are only valid if inside certain products.   For example is the WSW the correct product to put out a BZ.A?   I have no idea.   A short example of the correct/expected way to put out a vtec related product may help me get this working in a demo mode.

[Michael Foland]

For Blizzard Watch which is BZ.A it would be the Winter Message in the Product Formatter :) The GHG table might reference a database.... That might be the key.

[Michael Foland]

From the get go even in operational mode, I was able to transmit something like that, it's just something in the ghg table not making it show. It said it couldn't find the default config file or something.

[Michael Foland]

Pulled this from an example:
WWUS42 KFFC 051936
WSWFFC

Linked here: https://www.weather.gov/ffc/exampleWSWwarning

The top lines there even the WSW(OFFICE) are the AFOS lines for the product! Try even a high wind watch or something. In the Product Formatter, that's under Non precipitation :)

The 051936 is the issued time in zulu

[Michael Foland]

Those are the MND headers. I found another example to show the meanings for you.

https://www.weather.gov/media/pah/WeatherEducation/3-wxproducts.pdf

[Michael Foland]

Why is the transmit only working in PRACTICE? What if we generate our grids in operational or "simulate" transmit to the local ifps... since it won't go out anywhere public? I just noticed you were working on that!

[Mike Romberg]

I enabled an old testing mode, I'd forgotten about. The transmit button now is marked simulated transmit. This is because it does not actually transmit anything anywhere. What it does do is store the product in products/TEXT and run the VTECDecoder on it to update the active table. This active table in no way reflects "real" vtec codes. It is just updated when this gfe has products which have been "simulated transmitted". It is more straight forward to do this than try to enable the gfe's PRACTICE mode. The gfe should have this simulated trasmit right out of the box with the stock gfeConfig file now.

 I did a very simple test of adding a "winter" type hazard (blowing snow I think) and then transmitting a Hazard > WSW product.   The GHGMonitor then showed an entry for the watch and it's (ghgmonitor) maps updated.   Not extensive testing by any stretch.   But that much works again.

    I've not really tested any of this vtec related functionality since the python3 port.  So, it would not surprise me if there are more bugs scattered around in the code.

[Michael Foland]

I enjoyed it actually saying transmit. try taking the test vtec line out if marked test it should show those. might have todeal with that. the map really should also look at the zones from the product somehow

[Michael Foland]

I likely would post the zone forecast on my personal site since I do make forecasts and know how to

[Mike Romberg]

The basic product -> ghgmonitor seems to be working now. Create new tickets for any specific bugs in it's operation