Subject: Administrative: Status of GOES-16 SUVI L1b data, Issued: --000000000000959f13056bc658c1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable *Topic: Status of GOES-16 SUVI L1b DataDate/Time Issued: May 9, 2018 1400 UTCProduct(s) or Data Impacted: GOES-16 SUVI L1b DataDate/Time of Initial Impact: May 4, 2018 at 2000 UTCDate/Time of Expected End: N/ALength of Event: N/ADetails/Specifics of Change: The GOES-R Peer Stakeholder - Product Validation Review (PS-PVR) for Solar Ultraviolet Imager (SUVI) Extreme Ultraviolet Imagery (EUV) L1b Provisional Maturity was held on May 4, 2018. As a result of this review, NOAA has confirmed that the SUVI L1b data are at Provisional Validation Maturity as of May 4, 2018. PDA users who have pending subscriptions for these products may now request those subscriptions to be approved by emailing PDA_DHS@noaa.gov . Please include your PDA user group name and the specific subscription name. SUVI data consist of solar images is six extreme-ultraviolet passbands =E2=80=94 94 =C3=85, 131 =C3=85, 171 =C3=85, = 195 =C3=85, 284 =C3=85, and 304 =C3=85 =E2=80=94 with a variety of exposure times and filters in place to ensure e= ach image set captures the full dynamic range of solar phenomena. SUVI images have a pixel resolution of 1280=C3=971280 pixels, each with an angular resolution of 2.5 arcsec per pixel, for a total field of view of 53.3 arcmin square. Some corners of each passband are obscured by instrumental vignetting. SUVI files come in two varieties: netCDF and Flexible Image Transport System (FITS). In both cases, image metadata provide the image navigation information necessary to locate and orient the Sun with respect to well-known astronomical coordinate systems. For both file formats, these metadata follow the World Coordinate System (https://fits.gsfc.nasa.gov/fits_wcs.html ) conventions for FITS files. Users who are unfamiliar with these conventions are highly encouraged to review =E2=80=9CCoordinate Systems for Solar Image Data=E2=80=9D (Thompson,= 2006), which is linked from this page. Images are reported in units of radiance (W/m2 str-1), but care must be taken to handle the data array appropriately. In netCDF files, users should be sure to apply the =E2=80=98scale_factor=E2=80= =99 and =E2=80=98add_offset=E2=80=99 attributes. In FITS files, users should apply = the BSCALE and BZERO FITS keywords following the standard convention for each file format. Some FITS and netCDF readers may apply these corrections by default. Provisional validation means: - Validation activities are ongoing and the general research community is now encouraged to participate.- Severe algorithm anomalies are identified and under analysis. Solutions to anomalies are in development and testing.- Incremental product improvements may still be occurring.- Product performance has been demonstrated through analysis of a small number of independent measurements obtained from other sun-observing EUV instruments.- Product analysis is sufficient to establish product performance relative to expectations.- Documentation of product performance exists that includes recommended remediation strategies for all anomalies and weaknesses. Any algorithm changes associated with severe anomalies have been documented, implemented, and tested.- Testing has been fully documented; and- Product is ready for operational use and for use in comprehensive cal/val activities and product optimization. Users of the GOES-16 SUVI L1b data bear responsibility for inspecting the data and understanding the known caveats prior to use. Below is the list of caveats that have been identified and are under analysis. Solutions are in development and testing: 1. No SUVI L1b data prior to declaration of Provisional Maturity should be used. NCEI will reprocess and release the early mission data using the Provisional Maturity algorithm and look-up tables.2. Some metadata entries in SUVI L1b files may be incorrect or incomplete. The BUNIT keyword specifying image units is not present in SUVI FITS products. Image observation times and other time/date fields such as the DATE-OBS keyword are missing from SUVI L1b FITS products on the first of every month. The EFF_AREA keyword does not include the effect of the camera quantum efficiency on the instrumental effective area.3. The location of Sun center specified by the CRPIX1 and CRPIX2 keywords could be erroneous in the event of special SUVI operations. Users should validate that this information is correct before performing calculations that require accurate information in these fields.4. Spikes in the images resulting from particle impacts with the SUVI camera can, in some cases, cause significant contamination in the radiometric signal. These problems have a particularly pronounced effect on the in aggregate radiometric metadata fields in short exposures images.5. Bad pixels are not presently fully tracked and repaired in SUVI images, users may encounter negative valued pixels or NANs in the image array. Note also that the bad pixel table (or Data Quality Flag) in SUVI L1b files is not presently representative of either the location or correction of these bad or patched pixels. It should not be used.6. The GOES-16 platform location presently is specified in Earth-Centered Earth-Fixed (ECEF) coordinates by the OBSGEO-X, -Y, and -Z keywords. Users requiring platform location in heliocentric coordinate systems can refer to Hapgood (1992; http://dx.doi.org/10.1016/0032-0633(92)90012-D ) for information on coordinate conversions.7. Some users may encounter compatibility issues between some netCDF readers and FITS standard keywords that include a hyphen such as DATE-OBS when they appear in the netCDF version of SUVI L1b files. Users are encouraged to contact NCEI to report such problems and for guidance on possible workarounds. Users are encouraged to contact the GOES-R SUVI team in the event they have questions or encounter difficulties with SUVI files. The NCEI website provides additional information and access to SUVI L1b files https://doi.org/10.7289/V5FT8J93 . Contact for further information: Kathryn Mozer at kathryn.mozer@noaa.gov . NCEI contacts for specific information on the SUVI L1b data:Dan Seaton daniel.seaton@noaa.gov Jonathan Darnel jonathan.darnel@noaa.gov Margaret Tilton margaret.tilton@noaa.gov 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. * --000000000000959f13056bc658c1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Topic: S= tatus of GOES-16 SUVI L1b Data

Date/Time Issu= ed: May 9, 2018= 1400 UTC

Product(s) or Data Impacted: GOES-16 SUVI L1b Data<= /p>

Date/Time of Initial Impact: May 4, 2018 at 2000 UTC

= Date/Time of Expected End: =C2=A0N/A

Length of Event: =C2=A0N/A


Details/Specifics of Change: The GOES-R Peer Stakeholder - Product Validation Review= (PS-PVR) for Solar Ultraviolet Imager (SUVI) Extreme Ultraviolet Imagery (= EUV) L1b Provisional Maturity was held on May 4, 2018. As a result of this = review, NOAA has confirmed that the SUVI L1b data are at Provisional Valida= tion Maturity as of May 4, 2018. PDA users who have pending subscriptions for these p= roducts may now request those subscriptions to be approved by emailing PDA_DHS@noaa.gov= . Plea= se include your PDA user group name and the specific subscription name.

=C2=A0

SUVI data consis= t of solar images is six extreme-ultraviolet passbands =E2=80=94 94 =C3=85,= 131 =C3=85, 171 =C3=85, 195 =C3=85, 284 =C3=85, and 304 =C3=85 =E2=80=94 w= ith a variety of exposure times and filters in place to ensure each image s= et captures the full dynamic range of solar phenomena. SUVI images have a p= ixel resolution of 1280=C3=971280 pixels, each with an angular resolution o= f 2.5 arcsec per pixel, for a total field of view of 53.3 arcmin square. So= me corners of each passband are obscured by instrumental vignetting.=

=C2=A0

SUVI files come in= two varieties: netCDF and Flexible Image Transport System (FITS). In both = cases, image metadata provide the image navigation information necessary to= locate and orient the Sun with respect to well-known astronomical coordina= te systems. For both file formats, these metadata follow the World Coordina= te System (https://fits.gsfc.nasa.gov/fits_wcs.html) conventions for FITS files. Users = who are unfamiliar with these conventions are highly encouraged to review = =E2=80=9CCoordinate Systems for Solar Image Data=E2=80=9D (Thompson, 2006),= which is linked from this page.

Images are reported in units of radiance (W/m2 str-1),= but care must be taken to handle the data array appropriately. In netCDF f= iles, users should be sure to apply the =E2=80=98scale_factor=E2=80=99 and = =E2=80=98add_offset=E2=80=99 attributes. In FITS files, users should apply = the BSCALE and BZERO FITS keywords following the standard convention for ea= ch file format. Some FITS and netCDF readers may apply these corrections by= default.

Provisional validat= ion means:

=C2=A0

  • Validation activities= are ongoing and the general research community is now encouraged to partic= ipate.

  • Severe algorithm anomalies are identi= fied and under analysis. Solutions to anomalies are in development and test= ing.

  • Incremental product improvements may st= ill be occurring.

  • Product performance has be= en demonstrated through analysis of a small number of independent measureme= nts obtained from other sun-observing EUV instruments.

  • <= p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;ba= ckground-color:rgb(255,255,255)">Product analysis is sufficient to establish product performance = relative to expectations.

  • Documentation of p= roduct performance exists that includes recommended remediation strategies = for all anomalies and weaknesses. Any algorithm changes associated with sev= ere anomalies have been documented, implemented, and tested.

  • Testing has been fully documented; and

  • =

    Product is ready for operational use and for use in comprehensi= ve cal/val activities and product optimization.

=C2=A0

Users o= f the GOES-16 SUVI L1b data bear responsibility for inspecting the data and= understanding the known caveats prior to use. Below is the list of caveats= that have been identified and are under analysis. Solutions are in develop= ment and testing:

=C2=A0

  • No SUVI L1b = data prior to declaration of Provisional Maturity should be used. NCEI will= reprocess and release the early mission data using the Provisional Maturit= y algorithm and look-up tables.

  • Some met= adata entries in SUVI L1b files may be incorrect or incomplete. The BUNIT k= eyword specifying image units is not present in SUVI FITS products. Image o= bservation times and other time/date fields such as the DATE-OBS keyword ar= e missing from SUVI L1b FITS products on the first of every month. The EFF_= AREA keyword does not include the effect of the camera quantum efficiency o= n the instrumental effective area.

  • The lo= cation of Sun center specified by the CRPIX1 and CRPIX2 keywords could be e= rroneous in the event of special SUVI operations. Users should validate tha= t this information is correct before performing calculations that require a= ccurate information in these fields.

  • Sp= ikes in the images resulting from particle impacts with the SUVI camera can= , in some cases, cause significant contamination in the radiometric signal.= These problems have a particularly pronounced effect on the in aggregate r= adiometric metadata fields in short exposures images.

  • Bad pixels are not presently fully tracked and repaired in SUV= I images, users may encounter negative valued pixels or NANs in the image a= rray. Note also that the bad pixel table (or Data Quality Flag) in SUVI L1b= files is not presently representative of either the location or correction= of these bad or patched pixels. It should not be used.

  • The GOES-16 platform location presently is specified in Eart= h-Centered Earth-Fixed (ECEF) coordinates by the OBSGEO-X, -Y, and -Z keywo= rds. Users requiring platform location in heliocentric coordinate systems c= an refer to Hapgood (1992; http://dx.doi.org/10.1016/0032-0633(92)900= 12-D) for i= nformation on coordinate conversions.

  • So= me users may encounter compatibility issues between some netCDF readers and= FITS standard keywords that include a hyphen such as DATE-OBS when they ap= pear in the netCDF version of SUVI L1b files. Users are encouraged to conta= ct NCEI to report such problems and for guidance on possible workarounds.

    • =C2= =A0

    Users are encouraged to contact the GO= ES-R SUVI team in the event they have questions or encounter difficulties w= ith SUVI files. The NCEI website provides additional information and access= to SUVI L1b files https://doi.org/10.7289/V5FT8J93.

    =C2=A0

    Contact = for further information: Kathryn Mozer at kathryn.mozer@noaa.gov.

    =C2=A0

    NCEI contacts for specific information = on the SUVI L1b data:

    Dan Seaton daniel.seaton@noaa.gov

    Jonathan Darnel jonathan.darnel@noaa.gov

    Margaret Tilton margaret.tilton@noaa.gov

    =C2=A0

    This message was sent to ESPC.Notification@noaa.gov. You have been sent this and oth= er 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 bus= iness days to process your unsubscribe request.

    =C2=A0
    --000000000000959f13056bc658c1--