Use time-varying albedo in bucket

[juliasloan25]

Purpose

Closes #318

Edit: The interface for ClimaLSM.Bucket.BulkAlbedoTemporal needed to change for compatibility with the coupler. This change has been made in CliMA/ClimaLand.jl#300. ClimaLSM.jl has made an additional patch release for this change, bringing it up to v0.3.1.

To Do

The changes made here will be similar to those made in #202 for reading in albedo from a constant map

• Use ClimaLSM v0.3.0 v0.3.1
• Add option in cli_options.jl
  • Change type from Bool to String
• Add case for temporal map albedo in bucket_init.jl
• Update buildkite runs to use String albedo_type option
• Add test for this case in buildkite

---

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

[LenkaNovak]

LGTM, thanks Julia! Buildkite output looks good, but I noticed that the logging doesn't display the run command log (apparently the limit was exceeded). From your local runs, is it obvious why that is? (e.g., lots of warning messages?)

[juliasloan25]

LGTM, thanks Julia! Buildkite output looks good, but I noticed that the logging doesn't display the run command log (apparently the limit was exceeded). From your local runs, is it obvious why that is? (e.g., lots of warning messages?)

@LenkaNovak I've actually been getting a failed process error when I run our driver locally. It happens in rll_mesh when land_fraction is being created. This used to happen sporadically, but recently (for the last few months), it happens every time. I can try running it on the cluster, but it would also be nice to figure out why this happens locally.

[valeriabarra]

LGTM, thanks Julia! Buildkite output looks good, but I noticed that the logging doesn't display the run command log (apparently the limit was exceeded). From your local runs, is it obvious why that is? (e.g., lots of warning messages?)

@LenkaNovak I've actually been getting a failed process error when I run our driver locally. It happens in rll_mesh when land_fraction is being created. This used to happen sporadically, but recently (for the last few months), it happens every time. I can try running it on the cluster, but it would also be nice to figure out why this happens locally.

Is it the same as these failures that I've seen in my other up_deps.jl PR?

[juliasloan25]

LGTM, thanks Julia! Buildkite output looks good, but I noticed that the logging doesn't display the run command log (apparently the limit was exceeded). From your local runs, is it obvious why that is? (e.g., lots of warning messages?)

@LenkaNovak I've actually been getting a failed process error when I run our driver locally. It happens in rll_mesh when land_fraction is being created. This used to happen sporadically, but recently (for the last few months), it happens every time. I can try running it on the cluster, but it would also be nice to figure out why this happens locally.

Is it the same as these failures that I've seen in my other up_deps.jl PR?

It's similar, but it's a different TempestRemap call that's failing. Here are some screenshots of the error and stacktrace:

[LenkaNovak]

LGTM, thank you, @juliasloan25 !

[juliasloan25]

bors r+

[bors]

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• buildkite/climacoupler-ci
• ci 1.8 - macOS-latest
• ci 1.8 - ubuntu-latest
• ci 1.8 - windows-latest
• docbuild
• format