20040113: Impending Unidata-Wisconsin datastream content changes (reply)

>From: "Kevin W. Thomas" <address@hidden>
>Organization: OU/CAPS
>Keywords: 200401131847.i0DIlvp2009298

Kevin,

>I saw the posted message below, however, from what I see, there apparently
>is a problem.  I bring in all GOES10 and GOES12 vis/ir (10.7)/wv (6.5/6.8)
>data.
>
>GOES12 visible...
>Up until, and including the 2215Z data on January 9th, all data times were
>15 minutes past the hour, and arrived typically 25 to 28 minutes past the
>hour, meaning the data was less than 15 minutes old when it arrived.

I just verified this (it was working).  I am at the AMS show in Seattle
right now, so addressing this problem will be a bit of a problem.  I
will try to find out what is failing as soon as possible.

>Starting with 2345Z data on January 9th (nothing between 2215Z and 2345Z)
>all data times are 45 minutes past the hour, however, the arrival times are
>the same as in the past, meaning 25 to 28 minutes.  That makes the data about
>45 minutes old instead of 15 minutes old.  I do not see any "twice-per-hour"
>images.
>
>GOES12 ir...
>Exact same issues with GOES12 visible.
>
>GOES12 wv...
>Exact same issues with GOES12 visible.  The file sizes did increase on Jan 7th
>as advertised.
>
>GOES10...
>Nothing has changed anywhere.  Data times and arrival times are the same.  No
>"twice-per-hour" images.

This definitely was working before.  I will check to see what is going
on.

>My "pqact.conf" entries look like:
>
># Vis (0.65 um)
>MCIDAS ^pnga2area Q1 UV (.*) (.*)_IMG (0.65)um (.*) (........) (....)
>       PIPE    -close
>       /usr/local/ldm/pnga2area -vl logs/ldm-mcidas.log
>       -a etc/SATANNOT
>       -b etc/SATBAND
>       /arpsdata/ldm1/datafiles/sat/goes12vis/goes12vis_\5_\6
>
># WV (6.5 um)
>MCIDAS ^pnga2area Q1 UW (.*) (.*)_IMG (6.5)um (.*) (........) (....)
>       PIPE    -close
>       /usr/local/ldm/pnga2area -vl logs/ldm-mcidas.log
>       -a etc/SATANNOT
>       -b etc/SATBAND
>       /arpsdata/ldm1/datafiles/sat/goes12wv/goes12wv_\5_\6
>
># IR (10.7 um)
>MCIDAS ^pnga2area Q1 UI (.*) (.*)_IMG (10.7)um (.*) (........) (....)
>       PIPE    -close
>       /usr/local/ldm/pnga2area -vl logs/ldm-mcidas.log
>       -a etc/SATANNOT
>       -b etc/SATBAND
>       /arpsdata/ldm1/datafiles/sat/goes12ch4/goes12ch4_\5_\6
># Vis (0.65 um)
>MCIDAS ^pnga2area Q1 U9 (.*) (.*)_IMG (0.65)um (.*) (........) (....)
>       PIPE    -close
>       /usr/local/ldm/pnga2area -vl logs/ldm-mcidas.log
>       -a etc/SATANNOT
>       -b etc/SATBAND
>       /arpsdata/ldm1/datafiles/sat/goes10vis/goes10vis_\5_\6
>
># WV (6.8 um)
>MCIDAS ^pnga2area Q1 UB (.*) (.*)_IMG (6.8)um (.*) (........) (....)
>       PIPE    -close
>       /usr/local/ldm/pnga2area -vl logs/ldm-mcidas.log
>       -a etc/SATANNOT
>       -b etc/SATBAND
>       /arpsdata/ldm1/datafiles/sat/goes10wv/goes10wv_\5_\6
>
># IR (10.7 um)
>MCIDAS ^pnga2area Q1 U5 (.*) (.*)_IMG (10.7)um (.*) (........) (....)
>       PIPE    -close
>       /usr/local/ldm/pnga2area -vl logs/ldm-mcidas.log
>       -a etc/SATANNOT
>       -b etc/SATBAND
>       /arpsdata/ldm1/datafiles/sat/goes10ch4/goes10ch4_\5_\6

The thing that is missing from your pqact.conf file are actions for
the 3.9 um and 13.3/12.0 um images.

I will blast you a note as soon as I find out what is going on.

Sorry for the problems...

Tom