Verify grib headers for GEFS (and SFS) products

[WalterKolczynski-NOAA]

What new functionality do you need?

The products for GEFS v13 have largely been built using existing GFS product scripts. However, ensemble GRIB2 files should contain additional header information with the member number. Additionally, make sure the other GRIB header information is correct for GEFS where it differs from GFS (mainly Section 1).

SFS products will similarly need ensemble information and Section 1 changes.

What are the requirements for the new functionality?

GRIB headers for GEFS v13 products should generally be the same as in GEFS v12, save any intentional changes. Any new products should follow the headers from existing products.

GRIB headers for SFS products should similarly use the correct system and ensemble designations.

Acceptance Criteria

This issue is only to verify the header information and catalogue any differences. New issues should be created for each product that needs changes.

Checklist:

• Catalogue any difference between GEFS v12 and GEFS v13 GRIB headers
• Open workflow issues to update header for each affected product
• Resolve all issues by updating header information

Suggest a solution (optional)

No response

[EricSinsky-NOAA]

In the feature/gefs_reforecast branch, we added ensemble header information by adding this to forecast_predet.sh at the end of the FV3_predet function:

    memnum=$(echo "${ENSMEM}" | cut -c2-3)
    if [[ "${ENSMEM}" == "000" ]]; then
      export e1=1
    else
      export e1=3
    fi
    export e2=${memnum}
    export e3=${NMEM_ENS}

This is one of the things we plan to merge back to develop.

[JessicaMeixner-NOAA]

Making a note here that its the GFS grib headers that might actually need a change (unintentionally were the GEFS ones I believe).