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

Update amip_target_topo_diagedmf.yml #843

Merged
merged 1 commit into from
Jun 7, 2024
Merged

Update amip_target_topo_diagedmf.yml #843

merged 1 commit into from
Jun 7, 2024

Conversation

szy21
Copy link
Member

@szy21 szy21 commented Jun 7, 2024

Purpose

This yaml file will be for the target simulation we want to show at the VESRI meeting. This PR updates the corresponding atmos yaml file, and removes a few redundant configs. We will add more configs (e.g. aerosols) to this file when they are ready.

To-do

Content


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

@szy21 szy21 requested review from juliasloan25 and Sbozzolo June 7, 2024 22:45
@Sbozzolo
Copy link
Member

Sbozzolo commented Jun 7, 2024

Do we want to maybe add every single config here? Including the one in default_config. This would isolate the run from possible changes and one has to "opt-in" changing configurations

@Sbozzolo
Copy link
Member

Sbozzolo commented Jun 7, 2024

Do we want to maybe add every single config here? Including the one in default_config. This would isolate the run from possible changes and one has to "opt-in" changing configurations

Oops, I though this was Atmos. We can do that in atmos (if we want to)

@szy21 szy21 enabled auto-merge June 7, 2024 23:29
@szy21 szy21 merged commit a3bffcb into main Jun 7, 2024
6 checks passed
@juliasloan25 juliasloan25 deleted the szy21-patch-2 branch June 8, 2024 02:40
@juliasloan25
Copy link
Member

Thanks Zhaoyi! Should we change the runs that are output in the coupler table to use this setup too, since this is our target?

@szy21
Copy link
Member Author

szy21 commented Jun 8, 2024

Thanks Zhaoyi! Should we change the runs that are output in the coupler table to use this setup too, since this is our target?

We would probably need to lower the resolution of this run in order to run a multi-year simulation for the VESRI meeting, so I think we can keep the one we have in the coupler table. Which is the config file you are using for the coupler table now?

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.

3 participants