add GPU AMIP runs with albedo from file

[juliasloan25]

Purpose

Builds off of #573 - copies the config file introduced there and adds two new runs based on it, using albedo from static map and temporal map instead of function.

The goal of the runs introduced in this PR is to ensure that the coupled simulation can run in the AMIP setup with both types of file reading. Because of this, the simulation length of these runs is only two timesteps. More complex, physically significant setups will be added to the longruns.

closes #583

Content

• simple AMIP on GPU with bucket albedo from static map (run for 2 timesteps)
• simple AMIP on GPU with bucket albedo from temporal map (run for 2 timesteps)

---

• I have read and checked the items on the review checklist.

[LenkaNovak]

Good idea to bring these in, thank you, @juliasloan25 . I just had some questions on why the runs for the different albedo types have different resolutions (unless they're breaking, we should make these consistent, and I would choose the lowest possible resolution, except the target run).

[LenkaNovak]

Could we mimic the functional albedo resolution config, or do these break for the lower resolution?

Also, I noticed that the temporal albedo slabplanet has a higher resolution than the other two albedo runs. Is it because it was breaking for helem=4?

[juliasloan25]

Good catch! I'll lower them to 4, I think it should be fine.

The temporal albedo slabplanet has a higher h_elem because I copied these from the non-GPU slabplanet runs, where the functional and static map albedo have h_elem: 4 and temporal has h_elem: 6. I'm not sure why this is, and happy to change them all to 4.

[LenkaNovak]

Hmm, maybe it is unstable. 🤔 Worth trying though.

[juliasloan25]

they all work with the lower resolution :)