Add ISSM HISTORY, Restarts, and BCs

[agstub]

The purpose of this Draft PR is to (1) add new variables from ISSM (Ice-Sheet and Sea-Level System Model) to HISTORY, and deal with BCs files (prefixed ISSM*.*) and restarts (issm_internal_rst).

• GEOSldas_HIST.rc: Added a new collection tavg24_1d_issm_Nt (Tile-space,Daily,Time-Averaged,Single-level,ISSM Diagnostics) for mesh tile space with variables (ICESURF, ICETHICK, ICEVX, ICEVY).
• GEOSldas_HIST.rc: Added three ISSM outputs (ICESURF, ICETHICK, ICEVEL) and one ISSM input (ICESMB) to landice gridded collection (tavg24_2d_glac_Nx).
• In lenkf_j_template.py: move ISSM_MESH.nc to rc_out, copy ISSM* files from input to scratch directory, and move issm_internal_checkpoint files to restart directory.
• In ldas.py: link ISSM BCs and restarts, add ISSM restart/checkpoint filenames (issm_internal_rst/issm_internal_checkpoint) to configuration.
• Update CHANGELOG.md

Current restrictions:
Running ISSM is not supported with zoom-in and Restart type 2. For the latter, we currently have no way of mapping between restarts for different ISSM BCs. Specifying these options results in an error/exit in ldas.py

For restart type M, issm_internal_rst will be bootstrapped from what is stored in the input files (i.e. ice surface, thickness, etc. associated with the BCs). This is a convenient way to generate an ISSM restart.

Related issues and PRs

• Original issue: GEOSldas+ISSM on Discover GEOSldas#853
• Add ISSM ice sheet model GridComp to Landice GEOSgcm_GridComp#1203

[weiyuan-jiang]

The variables in the same collection should have the same tile or gridded space. We have discussion that ISSM should have output in mesh-like space. So ICEEL should not be in this collection

[agstub]

The variables in the same collection should have the same tile or gridded space. We have discussion that ISSM should have output in mesh-like space. So ICEEL should not be in this collection

That makes sense! Should I make new collections for ISSM outputs (mesh tile collection and gridded collection)? Will we still want to save a gridded version of ice elevation @lcandre2 ?

[lcandre2]

The variables in the same collection should have the same tile or gridded space. We have discussion that ISSM should have output in mesh-like space. So ICEEL should not be in this collection

That makes sense! Should I make new collections for ISSM outputs (mesh tile collection and gridded collection)? Will we still want to save a gridded version of ice elevation @lcandre2 ?

I would say that for standard ISSM outputs (elevation, ice velocity, ice discharge, perhaps a few others) it would be good to have both a tile and gridded collection.

[github-actions]

This PR is being prevented from merging because you have added one of our blocking labels: Contingent - DNA, Needs Lead Approval, Contingent -- Do Not Approve. You'll need to remove it before this PR can be merged.

[biljanaorescanin]

This PR was tested, it is zero diff for all tests.

More details on summary here: GEOS-ESM/GEOSgcm_GridComp#1203 (comment)

[biljanaorescanin]

@lcandre2 and @gmao-rreichle we will wait on your approval for this merge. Since it anyways needs GEOSgcm_GridComp to go in first. I will leave Do Not Approve label until then.

[lcandre2]

Looks fine by me.