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

[Datastream #YQH-718299]: Unidata data archive: GOES-16 and -17 IR images from 06Z to 11Z

Hi Dave,

re:
> First, thanks for maintaining a near-real-time data archive as emergency 
> backup for us
> users.

I'm glad that it is useful to you!

re:
> I notice, though, that GOES-17 ABI images for Channels 02 and 13, both CONUS 
> and Full
> Disk in Mode 6, are missing each day from 06Z through 11Z. (I haven’t checked 
> other
> GOES-17  channels or mesoscale images). However, images are present for those 
> hours
> (and only those hours) in Mode 3.

GOES-17 is being run in what NOAA is calling Flex Mode 3 each day from 6-12 
UTC.  I
am including one of their status notifications about this special operation at 
the
end of this reply.

re:
> For example, the Mode 3 image 
> OR_ABI-L1b-RadF-M3C13_G17_s20201050600359_e20201050611138_c20201050611185.nc
> (Full Disk image, Channel 13, GOES 17 at 06Z on April 14, located in directory
> https://atm.ucar.edu/native/satellite/GOES/GRB17/ABI/FullDisk/Channel13/20200414/)
>  is present, but the
> Mode 6 version of the same image is not. The same is true for the hours 07Z 
> through 11Z.

Correct.

re:
> In contrast, the reverse is true—Mode 6 images are present, but Mode 3 images 
> are not--
> for the other 18 hours of the day. The same pattern applies on at least one 
> or two other
> days that I checked.

Correct.

re:
> However, this pattern doesn’t apply to the analogous GOES 16 images—only Mode 
> 6 GOES-16
> images are present in the archive, for all 24 hours of the day.

GOES-16 does not suffer from the same cooling problem that GOES-17 has, so it 
is being
operated in the now standard Mode 6 (but every so often both satellites 
can/will be
operated in Mode 4 which is full disk scanning every 5 minutes and no CONUS or
Mesoscale-[12] scans).

re:
> The same statements above apply to Channel 02 images. (Probably to other 
> channels, too,
> but I haven’t checked—too much eye strain. :-)  )

The same applies to all GOES-17 channels.

re:
> This doesn’t make a lot of sense to me, and it complicates the code for 
> scripts designed
> to download images that are missing from our own archives. Is there a typo 
> somewhere in
> a pqact.conf file at Unidata, or is there intention behind the pattern?

There is no problem with the pattern-action file actions that we are using for 
FILEing
either/both GOES-16/17 images to disk.  GOES-17 is simply being operated in the 
so-called
Flex Mode 3.

Here is the bulk of the NOAA notification regarding of the special operations 
of GOES-17:

"Topic: GOES-17 (GOES-West) ABI Mode 3 Cooling Timeline Implementation

Date/Time Issued:  April 06, 2020 1310Z

Product(s) or Data Impacted: GOES-17  ABI Imagery and Level 2 Products

Date/Time of Initial Impact: April 09, 2020 0600 UTC

Date/Time of Expected End: May 01, 2020 1200 UTC

Length of Event: 6-hours each day from 0600 UTC to 1200 UTC and lasting from
April 09, 2020 through May 01, 2020.  The same timeline will occur seasonally
in operations for four periods each year.  See details below.

 

Details/Specifics of Change: GOES-17 ABI is going to commence seasonal
operational implementation of the Mode 3 Cooling Timeline. The first
implementation of the seasonal Mode 3 Cooling Timeline was from February 26,
2020 through March 01, 2020. The next upcoming implementation starts on
Thursday, April 09, 2020 through Friday, May 01, 2020. The cooling timeline is
implemented to mitigate the number of saturated images resulting from the loop
heat pipe (LHP) temperature regulation anomaly.  The timeline will occur for 6
hours, centered on spacecraft midnight from 0600 UTC to 1200 UTC each day. The
same timeline will occur seasonally in operations for four periods each year. 
The next two full periods in 2020 are given below with subsequent periods for
2021 to be confirmed based on future GOES-17 ABI thermal models:

  • August 12, 2020 - September 01, 2020

  • October 14, 2020 - October 31, 2020

  • Dates for 2021 are yet to be determined, but will be shared prior to
    January, 2021.  

 

The timeline will operate in Mode 3 (“Flex Mode 3” uploaded as timelineID=3)
where GOES-17 ABI will generate a single full disk once per 15 minutes and
generate one mesoscale domain sector each minute. Alternating MESO domains will
be collected one time each per two minute period. The CONUS domain will not be
scanned during the timeline as those periods will be used for cooling.

Full Disk product availability will occur every 15 minutes with timestamps of
HH:00, HH:15, HH:30, and HH:45 (with HH:00 representing data collected from
HH:00 through HH:15 and HH:15 representing data collected from HH:15 through
HH:30, etc.) for each hour from 0600-1200 UTC on April 09, 2020  through May 1,
2020.  Mesoscale domain sector availability will alternate each minute between
the two mesos (e.g. HH:00 for MESO1, HH:01 for MESO2, HH:02 for MESO1, HH:03
for MESO2).  GOES-17 ABI will continue its capability to handle domain sector
requests during the cooling timeline period. Nominal Mode 6 operations will
resume at 1200 UTC on each day of cooling timeline operations.  INR and
radiometric calibration will be maintained throughout the cooling timeline
periods of activation.  The data availability from each distribution service is
provided below in a format of “Distribution Service: Data Availability”.  

----------

AWIPS (Advanced Weather Interactive Processing System):  

  • 15 minute SCMI (Sectorized Cloud and Moisture Imagery) for Full Disk

  • 2 minute SCMI for mesoscale domain sector “MESO1” and “MESO2” 

  • 15 minute SCMI for Alaska sector (subset from Full Disk)

  • 15 minute SCMI for Hawaii sector (subset from Full Disk)

 

GRB (GOES Rebroadcast):  

  • 15 minute L1b Radiances Full Disk

  • 2 minute L1b Radiances for mesoscale domain sector “MESO1” and “MESO2” 

 

PDA (Product & Distribution Access System):

  • 15 minute L1b Radiances Full Disk

  • 2 minute L1b Radiances for mesoscale domain sector “MESO1” and “MESO2”

  • 15 minute Level 2 CMI Full Disk

  • 2 minute Level 2 CMI for mesoscale domain sector “MESO1” and “MESO2” 

  • All other Level 2 (non-CMI) Full Disk and mesoscale domain sector “MESO1”
    and “MESO2” products will be produced but may have varied degradation for
    the duration of the cooling timeline and up to 30 minutes *after* nominal
    Mode 6 resumes.

HRIT/EMWIN (High Resolution Information Transmission / Emergency Managers
Weather Information Network):  30 minute Level 2 CMI Full Disk will be
broadcast at HH:11 and HH:41.  The mesoscale domain sectors “MESO1” and “MESO2”
will be broadcast.  Level 2 non-CMI products will be broadcast during the
defined cooling timeline period, but may have varied degradation for the
duration of the cooling timeline

GNC-A (GEONETCast-Americas):  GNC-A broadcast of 15 minute Level 2 CMI Full
Disk imagery will be distributed at HH:01, HH:16, HH:31, and HH:46.  All Level
2 non-CMI products will not be broadcast during the defined cooling timeline
period.

----------

The GOES-17 ABI Mode 3 cooling timeline implementation is planned to occur
despite Critical Weather Day declaration. These cooling timeline activities are
specific to ABI.  All other GOES-17 spacecraft and instrument (EXIS, GLM,
Magnetometer, SEISS, SUVI) activities will remain nominal for the duration of
the cooling timeline. 

Contact Information for Further Information: ESPC Operations at
address@hidden or 301-817-3880

Web Site(s) for applicable information:

See https://www.ospo.noaa.gov/Operations/messages.html for this and other
satellite related messages.

See GOES-17 ABI performance website at https://www.goes-r.gov/users/
GOES-17-ABI-Performance.html

See https://www.ospo.noaa.gov/Operations/GOES/west/
Mode3G_Cooling_Timeline_G17.html for GOES-17 ABI Cooling Timeline Scan Schedule

Users are encouraged to send an email to address@hidden to report any
unexpected issues with downstream products and services."

I hope that this helps clarify the situation...

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: YQH-718299
Department: Support Datastream
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.