Epic: add Land component support

[forsyth2]

• Add task for e3sm_to_cmip #133, Add task for ILAMB #134 / ILAMB task revision #230
• Support ILAMB on other machines #229 / ILAMB for Compy #247, ILAMB for Cori #253
• Change ilamb_run task name #263 / Change ilamb task name #272
• Refactor global_time_series #288 / Refactor coupled_global plots #294
• Refactor coupled_global.py #389 (supports Add BGC global mean analysis #365)

Priority order below:

(1) Configuration changes:

• [Feature]: Global average for land component #531 / Test climo and ts for land variables #533 / Sample land NCO configuration #545
• [Feature]: Add new E3SM Diags set -- lat_lon_land #518
• Errors when running iLAMB #507

(2) Global time series:

• Add global_time_series plot parameters to the cfg #399 / Generic plotting for global time series #400 (supports Add BGC global mean analysis #365)

(3) Land campaign:

• [Feature]: Add land-specific plots to global time series #532 (duplicate/expansion of Add BGC global mean analysis #365?) (supports Make a land campaign configuration #151)
• Make a land campaign configuration #151
• E3SM_diag preprocess for land variables #489 (user question -- solution is to create a land configuration -- i.e., Make a land campaign configuration #151)

(4) Tech debt:

• Make e3sm_to_cmip its own task #467 / Make e3sm_to_cmip task #496
• Make an independent package for Global Time Series #398 (not necessary, or even likely, but certainly useful)

Also see https://acme-climate.atlassian.net/wiki/spaces/EIDMG/pages/3476979729/zppy+New+Feature+Requests

[chengzhuzhang]

@forsyth2 I will follow up with the land group about priorities. But at this stage, what we should do is to understand what capabilities we can already support, or can implement relatively straightforwardly. And come up with an example configuration and provide to land group as an prototype. The initial list as follows:

Initial list:

• Time-series and climatology for land variables
• e3sm_diags model vs model task for lat_lon_land [need to add additional variables]
• global averaged time series for land variables
• overview time-series plot for land variables
• ilamb [only a default setting is supported right now, with limited variables enabled]
• I think above capabilities are built, but there was not a configuration file that including these tasks with a land forcus. A campaign configuration file for land group will be ideal.
• E3sm_to_cmip (as a prerequisite for running ilamb), only support land variables that we publish to CMIP, we need to add additional variable converters for supporting ilamb.

[forsyth2]

@chengzhuzhang I'm trying to determine what is left to do on this "epic". Merging #400 closed out #399. From what I can tell, I think implementing #151 (adding a land template cfg) would essentially close out this epic. The only other thing that might need doing is #507 (adding more sets for the [ilamb] task or maybe adding variable converters in the e3sm_to_cmip package).

Details, for reference

I'm looking at the overview slides from https://acme-climate.atlassian.net/wiki/spaces/IPD/pages/4083056669/2024-01-19+zppy-Land+integration+meeting, checking for unresolved issues.

• Errors when running iLAMB #507:
  • Should the [ilamb] section of the zppy cfg have a sets parameter like E3SM Diags does? It looks like ILAMB is just picking up everything from the land_ts and atm_ts.
  • So, is the solution just to include more sets for ILAMB in the Land campaign cfg (Make a land campaign configuration #151)?
  • Or do variable converters need to be added in e3sm_to_cmip?
• [Feature]: Add land-specific plots to global time series #532 (expansion of Add BGC global mean analysis #365)
  • Once Add global_time_series plot parameters to the cfg #399 (PR Generic plotting for global time series #400) is finished, this would, in theory, simply require adding all the
    variables that we want plotted to the new Land Campaign configuration file (Make a land campaign configuration #151)
  • So, this can probably be done as part of Make a land campaign configuration #151.
• E3SM_diag preprocess for land variables #489 (user question -- solution is to create a land configuration -- i.e., Make a land campaign configuration #151)