-
Notifications
You must be signed in to change notification settings - Fork 5
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 atmos to table #817
add atmos to table #817
Conversation
412a3da
to
e3db73a
Compare
28642f2
to
ad61a8c
Compare
dz_top: 3000.0 | ||
h_elem: 30 | ||
moist: equil | ||
output_default_diagnostics: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe in a next PR we can switch the diagnostics on for our target jobs? We need to include them if the table has to be representative of realistic runs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Our goal for the table was not to include diagnostics, since that isn’t included in the performance goals we have. If we’re interested in understanding how long “real runs” will take, I can also add a run with diagnostics
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The performance goals should include IO: at the end, we want to look at the output.
test/component_model_tests/climaatmos_standalone/atmos_driver.jl
Outdated
Show resolved
Hide resolved
ad61a8c
to
a5c88d9
Compare
a5c88d9
to
b011d91
Compare
Purpose
closes #778
benchmark pipeline build: https://buildkite.com/clima/climacoupler-cpu-gpu-benchmarks/builds/164
Content