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

[IDD #HXN-593956]: Bad images in the GOES 16 GRB feed?

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 #HXN-593956]: Bad images in the GOES 16 GRB feed?
  • Date: Thu, 22 Oct 2020 10:53:33 -0600
Hi Pete,

We've been having some GRB ingest problems here lately, and these
may be the cause of what you have reported below.  I restarted
ingest processes for our GOES-East and GOES-West systems to see
if the problems would clear.  The GOES-West problem seems to have
cleared up, but I think that the problem was upstream of us as
we were seeing the same thing (lack of CONUS and FullDisk images)
on the machine feeding from SSEC as our own.  The GOES-East problem
has not been solved yet, sorry.

Cheers,

Tom

re:
> I've noticed the past few days there are many gaps/bad data
> sections in the netcdf files from the GOES 16 GRB feed. This
> color visible loop (based on bands 1/2/3) shows some of what
> I'm talking about, there are big chunks of the image that
> appear to be missing for various bands, various times, etc..
> 
> http://dustdevil.aos.wisc.edu/goes16/grb/rgb/conus/goes16_conus_3h.html
> 
> I've checked the admin messages from KNES but haven't seen any discussion of 
> upstream issues.
> 
> Here's a list of a few file sizes on the Unidata thredds server
> (mine at UW-AOS is identical) that shows some unusually small
> file sizes for some of the meso sector images.
> 
> From 
> https://thredds.ucar.edu/thredds/catalog/satellite/goes/east/grb/ABI/Mesoscale-1/Channel13/20201022/catalog.html
> 
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961543245_e20202961543314_c20202961543365.nc 
> 392.2 Kbytes 2020-10-22T15:44:08Z
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961542245_e20202961542314_c20202961542380.nc 
> 391.7 Kbytes 2020-10-22T15:43:13Z
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961541245_e20202961541313_c20202961541373.nc 
> 84.39 Kbytes 2020-10-22T15:41:56Z
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961540274_e20202961540343_c20202961540405.nc 
> 414.9 Kbytes 2020-10-22T15:41:12Z
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961539245_e20202961539314_c20202961539364.nc 
> 400.8 Kbytes 2020-10-22T15:40:08Z
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961538245_e20202961538314_c20202961538359.nc 
> 84.39 Kbytes 2020-10-22T15:38:53Z
> OR_ABI-L1b-RadM1-M6C13_G16_s20202961537245_e20202961537314_c20202961537367.nc 
> 392.3 Kbytes 2020-10-22T15:38:08Z
> 
> Note that most images are ~390 Kbytes, but a few are 84 kBytes. Those are the 
> bad ones.
> 
> Thoughts?

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: HXN-593956
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.