[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #JFQ-559665]: GOES-17 on DIFAX feed stopped

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDD #JFQ-559665]: GOES-17 on DIFAX feed stopped
  • Date: Thu, 21 Feb 2019 13:53:05 -0700
Hi Carl,

re:
> We suddenly started having problems receiving GOES-17 data from the DIFAX
> feed around 1445Z Feb 19th. Since then we've only gotten a couple of
> passes. It looks like there is recent data in the LDM queue so the problem
> is likely ours, but I just wanted to check whether something changed on
> your end around that time?  Just getting grasping at straws right now.

The most likely thing is that GOES-17 has been operating in Mode 6
recently, so your LDM pattern-action file action(s) may not be
processing the products if they are overly constrained.

For reference, representative LDM/IDD Product IDs taken from a snapshot
a few minutes ago are:

/data/cspp-geo/WEST/OR_ABI-L1b-RadC-M6C14_G17_s20190522016196_e20190522018569_c20190522019011.nc
/data/cspp-geo/WEST/OR_ABI-L1b-RadF-M6C14_G17_s20190522010341_e20190522019407_c20190522019461.nc
/data/cspp-geo/WEST/OR_ABI-L1b-RadM1-M6C03_G17_s20190522018275_e20190522018332_c20190522018367.nc
/data/cspp-geo/WEST/OR_ABI-L1b-RadM2-M6C08_G17_s20190522014575_e20190522015032_c20190522015071.nc

The part of the Product ID that indicates the satellite's operating mode
is the M6 just after the coverage part:

RadC-M6
RadF-M6
RadM1-M6
RadM2-M6

If your pattern-action file action(s) specify a particular mode like mode 3/M3,
then they will not match the Product IDs when the satellite is operating
in mode 6.  The same thing will be true when the satellite is operated
in mode 4, but when that is the case, there will be no CONUS or Mesoscale
scans.

Here is a quick overview of the ABI images that are to be sent in
the three modes that either/both GOES-16 and GOES-17 can be operated
in:

Mode 3:
CONUS       - every 5 minutes
Full Disk   - every 15 minutes
Mesoscale-1 - either every minute or every 30 seconds
Mesoscale-2 - either every minute or every 30 seconds

NB: if one of the Mesoscale sectors is issued every 30 seconds,
the other Mesoscale sector will stop being sent

Mode 4:
Full Disk   - every 5 minutes

Mode 6:
CONUS       - every 5 minutes
Full Disk   - every 10 minutes
Mesoscale-1 - either every minute or every 30 seconds
Mesoscale-2 - either every minute or every 30 seconds

NB: if one of the Mesoscale sectors is issued every 30 seconds,
the other Mesoscale sector will stop being sent

Please check your LDM pattern-action file action(s) to see if
the extended regular expression is overly constrained to a
particular operating mode of the satellite.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: JFQ-559665
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.