-
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
separate precomputed quantities in 3 funcs #2274
Conversation
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.
Thanks! Should we do it for diagnostic edmf as well? (It doesn't have to be in this PR.)
Yes, I can do it in the next one. Just wasn't sure if this is actually helpful or not |
922749b
to
5253b28
Compare
bors r+ |
It's a step in the right direction. Thanks :) |
2274: separate precomputed quantities in 3 funcs r=trontrytel a=trontrytel Following what we discussed `@szy21` , `@Sbozzolo` this PR splits prognostic edmfx precomputed quantities into 3 steps 1) updating environment 2) updating updraft thermo state and BC 3) updating the closures. I'm not sure if it actually makes anything better though. Or if you want to split the individual closures. Co-authored-by: Anna Jaruga <[email protected]>
Build failed: |
bors r+ |
5253b28
to
d45dd3a
Compare
Canceled. |
bors r+ |
2274: separate precomputed quantities in 3 funcs r=trontrytel a=trontrytel Following what we discussed `@szy21` , `@Sbozzolo` this PR splits prognostic edmfx precomputed quantities into 3 steps 1) updating environment 2) updating updraft thermo state and BC 3) updating the closures. I'm not sure if it actually makes anything better though. Or if you want to split the individual closures. 2284: Remove explicit use of CUDA in benchmark_step r=charleskawczynski a=charleskawczynski This PR removes an explicit use of CUDA in `benchmark_step!`, so that we have no direct package loading of CUDA. Co-authored-by: Anna Jaruga <[email protected]> Co-authored-by: Charles Kawczynski <[email protected]>
Build failed (retrying...): |
2274: separate precomputed quantities in 3 funcs r=trontrytel a=trontrytel Following what we discussed `@szy21` , `@Sbozzolo` this PR splits prognostic edmfx precomputed quantities into 3 steps 1) updating environment 2) updating updraft thermo state and BC 3) updating the closures. I'm not sure if it actually makes anything better though. Or if you want to split the individual closures. 2282: Increase job memory for perf jobs and lower allocations r=Sbozzolo a=Sbozzolo Co-authored-by: Anna Jaruga <[email protected]> Co-authored-by: Gabriele Bozzola <[email protected]>
Build failed (retrying...): |
2274: separate precomputed quantities in 3 funcs r=trontrytel a=trontrytel Following what we discussed `@szy21` , `@Sbozzolo` this PR splits prognostic edmfx precomputed quantities into 3 steps 1) updating environment 2) updating updraft thermo state and BC 3) updating the closures. I'm not sure if it actually makes anything better though. Or if you want to split the individual closures. Co-authored-by: Anna Jaruga <[email protected]>
Build failed: |
d45dd3a
to
594c8fd
Compare
bors r+ |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Following what we discussed @szy21 , @Sbozzolo this PR splits prognostic edmfx precomputed quantities into 3 steps
I'm not sure if it actually makes anything better though. Or if you want to split the individual closures.