Adding a gefs_arch task to GEFS workflow

[AntonMFernando-NOAA]

Description

• The gefs_arch task is not generated during the execution of the workflow setup scripts. It is only created when do_extractvars is set to true, with do_extractvars being false by default. This pull request ensures that the gefs_arch task will be created in the workflow regardless of the value of do_extractvars.

  Resolves The GEFS workflow does not create a gefs_arch task #3151

Type of change

• Bug fix (fixes something broken)
• New feature (adds functionality)
• Maintenance (code refactor, clean-up, new CI test, etc.)

Change characteristics

• Is this a breaking change (a change in existing functionality)? NO
• Does this change require a documentation update? NO
• Does this change require an update to any of the following submodules? NO (If YES, please add a link to any PRs that are pending.)

How has this been tested?

• CI test on HERCULES and HERA

Checklist

• Any dependent changes have been merged and published
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have documented my code, including function, input, and output descriptions
• My changes generate no new warnings
• New and existing tests pass with my changes
• This change is covered by an existing CI test or a new one has been added
• Any new scripts have been added to the .github/CODEOWNERS file with owners
• I have made corresponding changes to the system documentation if necessary

[WalterKolczynski-NOAA]

It's coming back to me why we only had the archive task when extract_vars is on: the archive job doesn't do much for GEFS right now when extract_vars is off (well, now it may archive the expdir). If you look at parm/archive/master_gefs.yaml.j2, all of the non-expdir included lists are extracted ones. There is a parm/archive/gefs_arcdir.yaml.j2, but it doesn't seem to be included anywhere.

I think to complete this, we need the following:

• The inclusion of the extracted files need to be hidden behind the DO_EXTRACTVARS flag (it should be failing right now if it is off)
• The gefs_arcdir file needs to be included when extract vars is off

@DavidHuber-NOAA @EricSinsky-NOAA please let me know if I'm incorrect here.

[DavidHuber-NOAA]

@WalterKolczynski-NOAA Yes, I think you are correct. There would need to be an if-block around

global-workflow/parm/archive/master_gefs.yaml.j2

Lines 7 to 12 in f1afac9

	{% filter indent(width=4) %}
	{% include "gefs_extracted_atmos.yaml.j2" %}
	{% include "gefs_extracted_ocean.yaml.j2" %}
	{% include "gefs_extracted_ice.yaml.j2" %}
	{% include "gefs_extracted_wave.yaml.j2" %}
	{% endfilter %}

[EricSinsky-NOAA]

To make things more simple, I believe we can remove the gefs_extracted* yaml files and only use gefs_arcdir.yaml.j2. The only place these gefs_extracted* yaml files are needed are in the feature/gefs_reforecast branch. I do not believe they are needed in develop if we use gefs_arcdir.yaml.j2.