Add nonjcb configuration builder

[delippi]

DESCRIPTION OF CHANGES:

• Added a tool (workflow/gen_jedivar_yaml_nonjcb.sh) to build the jedivar.yaml. This is built prior to running the workflow.
• Minor updates to scripts/exrrfs_jedivar.sh for using the preconfigured jedivar.yaml

TESTS CONDUCTED:

Tested on Hera conus 12km retro runs.

ISSUE:

• Generating jedivar yamls #629

[delippi]

@guoqing-noaa, I made a template PR for building the jedivar yaml from the yamls in RDASApp once we sort out the problem with using all the QC filters. I added a tool to generate the yamls (very similar to RDASApp's gen_yaml.sh). I was also wondering if this is supposed to be python instead of bash?

[guoqing-noaa]

@delippi Thanks for developing this.
However, at this moment, we want to track the jedivar.yaml directly from the parm/ directory.
We still have a lot to go on the workflow side and this is not a top priority at the moment. We may revisit this later. Thanks!

[guoqing-noaa]

Any non-runtime utilities will go to the workflow/ush directory

[delippi]

I will move it.

[guoqing-noaa]

The changes here break the existing hybrid settings. i.e. We cannot do pure 3DVAR or pure EnVar after this change.

[delippi]

Do you mean because I removed this part?

- if [[ "${HYB_WGT_ENS}" == "0" ]]; then # pure 3DVAR
-   sed -i '88,113d' ./jedivar.yaml
- elif [[ "${HYB_WGT_STATIC}" == "0" ]]; then # pure 3DEnVar
-   sed -i '46,87d' ./jedivar.yaml
- fi

We will have (and do have in RDASApp) a 3dvar and pure envar template instead of deleting these sections. You would specify this via

basic_config="mpasjedi_hyb3denvar.yaml"

[delippi]

@delippi Thanks for developing this. However, at this moment, we want to track the jedivar.yaml directly from the parm/ directory. We still have a lot to go on the workflow side and this is not a top priority at the moment. We may revisit this later. Thanks!

I figured you would still use that yaml for some time. This is just a draft to get it ready to go when we are ready for it.