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

Specify year range for e3sm_to_cmip in ts #558

Merged
merged 1 commit into from
Mar 2, 2024

Conversation

chengzhuzhang
Copy link
Collaborator

To address potential problem documented here: #549 (comment)

@chengzhuzhang
Copy link
Collaborator Author

Hey @forsyth2, it is great news that the tests are all passing with the new e3sm_to_cmip release. However, I still think we should consider to use specified years for e3sm_to_cmip as discussed earlier. Do you think we should add this fix along the new rc?

@forsyth2
Copy link
Collaborator

forsyth2 commented Mar 1, 2024

@chengzhuzhang Yes, I can implement that for the RC.

@forsyth2
Copy link
Collaborator

forsyth2 commented Mar 1, 2024

@chengzhuzhang Oh sorry, I thought this was an issue, not a PR. I will test this fix too.

@chengzhuzhang
Copy link
Collaborator Author

@chengzhuzhang Oh sorry, I thought this was an issue, not a PR. I will test this fix too.

Thank you!

@forsyth2
Copy link
Collaborator

forsyth2 commented Mar 2, 2024

All tests pass, merging.

@forsyth2 forsyth2 merged commit 4db3e24 into main Mar 2, 2024
4 checks passed
@forsyth2 forsyth2 deleted the explicit_year_range_for_e3sm_to_cmip branch March 2, 2024 02:15
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