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

refactor surface albedo calculation #2787

Merged
merged 1 commit into from
Mar 14, 2024
Merged

refactor surface albedo calculation #2787

merged 1 commit into from
Mar 14, 2024

Conversation

szy21
Copy link
Member

@szy21 szy21 commented Mar 13, 2024

Purpose

To-do

Content


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

@szy21 szy21 force-pushed the zs/surface_albedo branch 2 times, most recently from 355b309 to 8fb10f7 Compare March 13, 2024 22:09
@szy21 szy21 requested a review from dennisYatunin March 13, 2024 22:09
@szy21
Copy link
Member Author

szy21 commented Mar 13, 2024

I'll revert the pipeline change after testing.

@szy21 szy21 force-pushed the zs/surface_albedo branch from 0beba07 to ff07b43 Compare March 14, 2024 00:19
@szy21 szy21 enabled auto-merge March 14, 2024 00:21
@szy21 szy21 added this pull request to the merge queue Mar 14, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 14, 2024
@szy21 szy21 added this pull request to the merge queue Mar 14, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Mar 14, 2024
@szy21
Copy link
Member Author

szy21 commented Mar 14, 2024

cc @LenkaNovak in case this affects coupler

@szy21 szy21 added this pull request to the merge queue Mar 14, 2024
Merged via the queue into main with commit 9b203a7 Mar 14, 2024
11 checks passed
@szy21 szy21 deleted the zs/surface_albedo branch March 14, 2024 06:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants