**HLS Issues from Cristobal through Fay**

1.  Old files on system which were overriding the correct ones in the
    baseline

    a.  This caused a number of different issues from no VTEC to
        incorrect VTEC

    b.  This has been addressed as part of the transition to operational
        MWW

2.  Length of product made for long creation times

    a.  The initial product takes the longest due to no previous text
        being available.

    b.  Different offices/forecasters have different opinions on using
        the headline selector as a means of reducing editing

        i.  Some like to have only what they need once product is
            generated. Others would rather get the output then edit all
            at once. Really a personal preference.

        ii. Some found selector window confusing

    c.  Having a focal point setup the HLS with customizations for your
        area helps tremendously.

        i.  Offices that had the formatter customized had fewer
            complaints internally about the output (or lack thereof).

        ii. It reduces the workload somewhat, especially the Areas
            Affected and tidal/surge output

        iii. Help is available, if needed

    d.  Some offices had a lesson learned to remove Areas Affected and
        Watches/Warnings in the future as they were redundant.

        i.  Even through those are automated in the ER formatter, it
            still adds length to the final product.

    e.  Be cautious using copy/paste

        i.  Make sure copied text is pertinent to segment to which you
            are pasting

            1.  Do not need to add info that is not needed

    f.  Overall, no known customer complaints about product length or
        format

        i.  Even had an accolade from Accuweather about the HLSs in both
            storms

    g.  Due to length and time to create, having more eyes QC and
        running spell check are even more important

3.  All TCVs from NHC are critically important to HLS creation so any
    timeliness or content issues need to be reported to NHC ASAP.

    a.  Do NOT run an HLS with incorrect grids or output will be
        incorrect

        i.  You cannot correct those grids yourself or they will differ
            from "official" TCV and GFE problems will likely result

    b.  Need to be aware of what breakpoints equal what zones in your
        CWA

        i.  That way no surprises when PlotTPCEvents is run

        ii. This information has been gathered and disseminated to all
            offices

    c.  Most issues have been raised to NHC by tropical program manager

4.  Make sure to have a clear internal understanding of who is
    responsible for what grids

    a.  Having multiple forecasters attempting to edit hazard grids
        leads to problems

    b.  NEVER run a hazard procedure like PlotTPCEvents or PltSPCWatches
        when another forecaster has the grid locked

        i.  The procedure will still run in the background and cause
            problems with the hazard grid

        ii. This issue is addressed in OB8.3.1 (late September release)

    c.  Best to have the most experienced grid person(s) editing during
        these events, if possible

5.  Listen to GFE!

    a.  If you have a merge conflict error, FIX it. Otherwise you have
        an incorrect grid which leads to incorrect products and a bad
        hazard grid on the NDFD

6.  NEVER edit a VTEC product outside of GFE

    a.  Text corrections need to be done through the usual method

    b.  Other issues result from incorrect grids. Fix the grids and
        rerun the HLS.