Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time-varying albedo #318

Closed
Tracked by #359
juliasloan25 opened this issue Jun 5, 2023 · 0 comments · Fixed by #394
Closed
Tracked by #359

Time-varying albedo #318

juliasloan25 opened this issue Jun 5, 2023 · 0 comments · Fixed by #394
Assignees
Labels
🍃 leaf Issue coupled to a PR

Comments

@juliasloan25
Copy link
Member

juliasloan25 commented Jun 5, 2023

We currently have the capability to use albedo read in from a file thanks to functionality provided by ClimaLSM. However, the albedo is read only once from the supplied data file, and does not change over time. Here, we want to extend our implementation to read in albedo as it changes over time.

CliMA/ClimaLand.jl#243 implements the necessary functionality in ClimaLSM, and we just have to update to use this new option.

Part of #276
Closed by #394

Relevant Links

  • BulkAlbedoMap definition here
  • MapInfo definition here
  • Albedo artifact files here
    • Bare ground albedo dataset (no time dimension)
    • CESM2 albedo dataset (midmonth dates from 1/15/1850 to 12/15/2014)
    • Both datasets contain variables "lat" (dim. 192), "lon" (dim. 288), and "sw_alb" (dim. lat x lon)
      • Note that our SST and SIC datasets have lat and lon dimensions of 180 and 360, respectively

Other

  • Note that the date range in the CESM2 albedo dataset (1850-2014) is different from the range of our SST and SIC datasets (1870-2022). This is fine for now since we're running shorter-length simulations, but we may need to revisit this when we want to have longer runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🍃 leaf Issue coupled to a PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant