clean up layout specification when running UFSDA ATM var and ensda apps

[RussTreadon-NOAA]

What new functionality do you need?

Two items related to layout variables for UFSDA ATM variational and local ensemble apps are addressed in this issue.

First, UFSDA ATM variational and local ensemble apps do not specify layout_x and layout_y in the same was as UFSDA Aerosol and Land DA. A consistent approach should be used across all UFSDA apps. This issue documents the moving of layout_x and layout_y from config.atmanl and config.atmensanl to defaults.yaml. This brings all four UFSDA apps into consistency with regards to how these variables are set.

Second, the UFSDA ATM variational app has the option to use the GSI static-B. Processing of the GSI static-B is a function of variables layout_gsi_b and layout_gsib_y. Currently these variables are hardwired in GDASApp parm files. GDASApp issue #680 removes this restriction by adding variables layout_gsib_x and layout_gsib_y. This g-w issue add variables layout_gsib_x and layout_gsib_y to atmanlrun section of parm/config/gfs/config.resources. This allows users to more easily control the layout used to process the GSI static-B.

What are the requirements for the new functionality?

1. The layout for UFSDA ATM variational and local ensemble apps are consistent with the approach used for UFSDA aerosol and land apps.
2. The layout for GSI static-B is set in the g-w configuration along with changes from 1.

Acceptance Criteria

UFSDA ATM variational and local ensemble apps correctly run with layout configurations set in g-w config files.

Suggest a solution (optional)

No response

[RussTreadon-NOAA]

Work for this development will be done in RussTreadon-NOAA/global-workflow:feature/gsibec.

[RussTreadon-NOAA]

config.atmanl and config.atmensanl set layout_x and layout_y. config.resources also sets layout_x and layout_y for jobs atmanlrun and atmensanl. This is dangerous. We should not set the same variables in two locations.

config.aeroanl and config.landanl do not set layout_x and layout_y. Both allow config.resources to set these layout variables. This approach is preferable.

Another nice feature of config.aeroanl and config.landanl is that both set io_layout_x and io_layout_y via templated variables defined in yaml/defaults.yaml. Currently, config.atmanl and config.atmensanl hardwire io_layout_x and io_layout_y to fixed values. It's best to have a consistent approach for UFSDA apps.

Update config.atmanl, config.atmensanl, and config.resources to be consistent with aero and land approaches. Done at 01bbfee.

[RussTreadon-NOAA]

While atmanlrun uses {layout_x, layout_y} and, optionally, {layout_gsib_x, layout_gsib_y}, the run job accesses these variables via the yaml file created by atmanlinit. Setting the layout variables only in the atmanlrun section of config.resources is not correct. Both sets of layout variables need to be defined in atmanlinit.

We also need {layout_x, layout_y} in atmanlrun. These variables are used to define npe_atmanlrun and npe_atmanlrun_gfs.

The above changes to config.resources were committed at ad5e723.