Topic: GOES-16 Software Build and Emergency Patch Installation scheduled for July 15, 2019

Date/Time Issued: June 14, 2019 1425 UTC

Product(s) or Data Impacted: All GOES-16 and GOES-17 Level 1b products

Date/Time of Initial Impact: July 15, 2019 1400 UTC

Date/Time of Expected End: N/A

Length of Outage: N/A

M-B

Details/Specifics of Change:

A GOES-16/17 software build (DO.08.00.00) and emergency patch (DO.08.00.01) are planned to go live on July 15, 2019 between 1400-1600 UTC. No data outage will occur when the updates go live. These updates will result in changes to all Level 1b (L1b) products and some Level 2 (L2) products as detailed below. GOES Rebroadcast (GRB) and GOES-R Product Definition and UsersM-bM-^@M-^Y Guide (PUG) impacts and updates are noted.

DO.08.00.00 Content

Algorithm

Title

Summary

GRB Impact

PUG Update

SUVI L1b

SUVI FITS headers: feature requests, and points that require clarification

Add the SUVI FITS BUNIT keyword to the FITS header and map it to the NetCDF variable RAD attribute "units", RAD:units ; Add the SUVI FITS CREATOR keyword to the FITS header and map it to the NetCDF attribute "algorithm_version" ; Add the SUVI FITS RSUN keyword to the FITS header. ; Add the SUVI FITS HGLT_OBS and HGLN_OBS keywords to the FITS header. ; Add the SUVI FITS HEEX_OBS, HEEY_OBS, and HEEZ_OBS keywords to the FITS header

no

yes

SEISS L1b

SEISS Data out of sequence

Data in SEISS files should now be written in time order.

no

no

ABI L2

Fix floating point comparisons to zero with threshold close to zero for L2 science algorithms

Throughout the L2 algorithm code there are numerous floating point comparisons that may be contributing to defects. When floating point numbers are expected to be zero they are not guaranteed to be precisely zero in C++. So, one may not safely compare a floating point number to zero nor, for instance, compare floating point numbers for equality or inequality. To minimize problematic comparisons, algorithm code should make use of a M-bM-^@M-^\close to zero thresholdM-bM-^@M-^] wherever floating point comparisons are needed. This update implements the close to zero threshold.

no

no

SUVI L1b

SUVI FITS Headers Do Not Fully Match PUG

Adds INST_ID to fits product as described in The PUG (Rev E-2, Vol. 3, Table 5.2.1.5.2). PUG also updated to include ORB_SLOT which is in the FITS file but was not in the PUG.

no

yes

SUVI L1b

SUVI Radiometric Metadata Update

Adds BUNIT field and INSTRESP, PHOT_ENG to the SUVI FITS product.

no

yes

ABI L1b

Bad ABI M4 SpaceLook Means

Fixes an issue that putting bad SpaceLook means into the instrument calibration data when in mode 4.

no

no

GLM L1b INR

GLM Event Geolocation Does Not Match Vendor Results

Minor corrections to the GLM event navigation implementation.

no

no

SUVI L1b

SUVI Inst Cal Files output Wavelength as 94, 304 instead of 093, 303

SUVI instrument Calibration files now correctly output as Wavelength 093 and 303 instead of 94 and 304.

no

yes

ABI L1b

ABI CH2 INST-CAL Data Record Number Inconsistency

Within the same timeline, the number of "offset times" records reported in the INST-CAL-DATA files for ABI Channel 2 can differ between data_paths, which represent output for sequential range chunks of channel 2 detectors. This is not nominal for INST-CAL-DATA from the other ABI channels, and is not clear why it would happen for channel 2.

no

no

N/A

The GRB-INFO-STATIC.xml file is missing from the GRB.

The GRB-INFO-STATIC.xml file will now be in GRB. The file had been missing because it was only sending when updated which is very infrequent.

yes (previously missing content)

no

EXIS L1b, SEISS L1b, SUVI L1b, MAG L1b

Eliminate SpWx L1b dependency on APID 384

Space Weather algorithms will now use APID 255 for Orbit and Attitude information instead of ABI APID 384. APID 255 is available when the satellite is not transmitting on X-band and is not dependent on ABI.

no

no

ABI CTP, CPH, DSR

Fill data in MESO cloud products due to discarded NWP data

Resolved several implementation issues that were contributing to fill in the cloud and radiation products.

no

no

ABI L2

Various NCML attributes have incorrect types that do not match their associated parent variable type

Various ABI L2 NCML attributes are updated to match their associated parent variable type.

no

no

All L0

L0 Archive instrument_id attribute is wrong

instrument_id has been updated to use FM1/FM2 instead of ABI-1. This brings the naming into line with the rest of the GOES-R outputs.

no

no

GLM L1b

GLM Blooming Filter

This adds the Blooming Filter to the suite of false event filters used in the GLM L1b ground processing algorithm to remove false lightning event detections. The blooming filter removes false events which can occur during solar glint and solar intrusion.

no

no

MAG L1b

Spike in MAG EPN data following missing L0/L1a samples

The MAG L1 EPN filter uses data from the previous sample in the calculation. This update adds a check to see if the previous sample is invalid or missing to prevent introducing zero-values into the filter.

no

no

ABI L1b

ABI L1b Sample Outlier File: Metadata Incomplete

This change brings the metadata in the SOF into line with CF conventions and other ABI products.

no

yes

N/A

Incorrect topic names in GRB Recovery create empty products

Fixes an internal issue which was creating empty products sent to PDA.

no

no

SEISS L1b, EXIS L1b, Mag L1b

Update SEISS and EXIS for Leap Seconds

Updates metadata to explicitly say that leap seconds were not used when calculating specific data.

no

no

ABI L1b, GLM L1b

LUT Filenames not Traceable to Metadata - ABI GLM

ABI and GLM metadata will now include the names of the LUTs used in production.

no

yes

GLM L2

GLM L2+ LCFA Product's Yaw Flip Flag is fill

The GLM L2 product will now output the correct yaw flip state. It was previously fill.

no

no

SUVI L1b

SUVI CSYER1 and CSYER2 are out of range

Fixes the CSYER1 and CSYER2 variables and changes the range in the PUGand metadata to -100 to +100 arcseconds.

no

yes

N/A

Retransmitted FTNMs lack Resolution and Geographic Extent

Update the retransmitted file transfer notification messages (FTNMs) to include resolution and the geographic extent needed by PDA.

no

no

SEISS L1b, SUVI L1b, MAG L1b

Reformat SpWx L1b variables with _Unsigned Attribute

Some variables in the L1b netCDF product files use an M-bM-^@M-^\_UnsignedM-bM-^@M-^] attribute. This update changes the variables to native unsigned representations.

yes

yes

SUVI L1b

Errors in L1-SUVI-INR cause SUVI files to remain .tmp files and not get distributed

Fixed an internal GS issue that was producing SUVI tmp files.

no

no

ABI L1b

ABI stars scene effective scan rate calculation

Computes the star effective scan rate from shaft angle telemetry during star verification, replacing the fixed scan rate defined by CDRL 79 parameters. This correction prevents anomalous detections of fast-scan stars from reaching the Kalman Filter.

no

no

N/A

Errors creating CLASS manifest files

There was an error writing files to LZSS. This fixes that issue.

no

no

ABI L1b INR

Kalman incorrectly reads in 2+ element QBoost arrays

Fixes an array issue that was impacting INR.

no

no

M-B

DO.08.00.01 Content

Algorithm

Title

Summary

GRB Impact

PUG Update

ABI L1b

ABI Saturated Internal Cal Target Counts

Update ICT algorithm to properly propagate past gain values when the ICT look data are flagged as bad.

no

no

ABI L1b

Scan does not update ICT gains mid-scene

Process additional ICT looks that occur mid-scene and apply the resultant gains.

no

no

ABI L1b

ABI L1b temperature data quality flag (TDQF)

Corrects the reported temperature and flagging threshold of band 11 to be the MWIR FPM (rather than LWIR as in DO.07.02).

no

no

ABI L1b

ABI Predictive Calibration Algorithm

Implements the Predictive Calibration Algorithm per ABI CDRL 80-3 Rev J.

no

no

M-B


Contact Information for Further Information: Jim McNitt (the GRB User Group Chairman) james.mcnitt@noaa.gov M-Bor ESPC Operations at ESPCOperations@noaa.gov or 301-817-3880

M-B

Web Site(s) for applicable information:

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

M-B

This message was sent to ESPC.Notification@noaa.gov. You have been sent this and other notifications because you have opted in to receive it. If for any reason, you wish to unsubscribe, please contact ESPC Help Desk at ESPCOperations@noaa.gov or (301) 817-3880. Please note: it may take up to two business days to process your unsubscribe request.

^L