-
Notifications
You must be signed in to change notification settings - Fork 19
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
Add spin-up capabilities for ClimaAtmos
simulations
#3327
Comments
@szy21 , @akshaysridhar : Please edit/add your requirements here. |
Yes, this will be a useful capability to have. Before you get started on it, can you please estimate how long it'll take to build this? |
Would it be easier if we add the capability for reading initial condition from a netcdf file and interpolate? If we do this we won't be constrained by the resolution (both horizontal and vertical). |
ClimaUtilities provides capabilities to accomplish this non-conservatively (using InterpolationsRegridder--multi-linear interpolation), or conservatively with the same vertical levels as the file (using TempestRegridder). |
I think interpolating the state / cache is fine, but I think we should still have a way to compute the local geometry given the types of previous data with the new resolution. This way, we don't have errors in mass/energy transport on restarted simulations. |
The plan is to write the restart data to the new (finer) grid. The restart file will contain all needed information to start the simulation on the finer grid. |
For many climate simulations, it is necessary to run a simulation for multiple turn-over times before a statistically stationary state is reached and a usable start-up condition is achieved. For high resolution simulations, this start-up phase can be expensive. It is generally desirable to start the spin-up simulation at a lower resolution and gradually increase the resolution to the target resolution.
Tasks
Timeline estimate: About 2 weeks (week of 11/11/2024)
cc: @charleskawczynski @cmbengue @tapios
The text was updated successfully, but these errors were encountered: