-
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
Remove unused fieldvector #2131
Conversation
bors r+ |
Build failed: |
Why is Fields.bycolumn(axes(Y.c)) do colidx
precipitation_tendency!(p.Yₜ, Y, p, t, colidx, p.precip_model)
end # TODO: Set the diagnostics without computing the tendency. used in the diagnostics? cc @trontrytel . Can we split this into precompute and add a function that adds fluxes so that we can remove |
Not sure why? Not wanting to cache more things and or duplicate the code? I don't have the bandwidth to fix this this week. Feel free to open an issue and tag me on it. I can try getting it done before the next sprint
|
I think we might use it to make sure the precipitation tendency is consistent with the state, as we call |
db15962
to
e604f1a
Compare
I think it's fine to precompute things needed for precipitation tendencies, but the precip tendendencies themselves don't seem to be used in the diagnostics-- Also if they are, then I think we can get them from the integrator? |
@trontrytel, for now, I've just wrapped the tendency updates in |
We calculate col_integrated_rain and col_integrated_snow in |
Sounds good. Apologies it's such a mess over there. It would be great to allocate some time and straighten things up (looking at myself pointedly). The logic we want would be to put |
No problem. I'm just trying to incrementally improve on CliMA/ClimaCore.jl#1467 for now. It's not clear to me how to best structure things, but there's definitely room for improvement. |
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. |
Followup to #2130