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

Clean up surface_fluxes.c #31

Open
tbohn opened this issue Aug 2, 2013 · 5 comments
Open

Clean up surface_fluxes.c #31

tbohn opened this issue Aug 2, 2013 · 5 comments

Comments

@tbohn
Copy link
Contributor

tbohn commented Aug 2, 2013

Currently the logic accounting for a) iteration between surface and canopy temperature solutions, b) snow step vs model step, and c) distributed precip results in a confusing mess of data structures and loops. This makes adding features and preventing bugs more difficult than otherwise.

@bartnijssen
Copy link
Member

This will partially be cleaned by removing the DIST_PREC option (Issue #22). Any further cleanup will have to wait.

@bartnijssen bartnijssen added this to the 5.0 milestone Mar 27, 2014
@jhamman
Copy link
Member

jhamman commented Dec 8, 2014

@tbohn - now that we've removed the DIST_PREC code and gone ahead with the other cleanup tasks (#162), do you think there is anything else to do here? If this will be part of the 5.0 release, we need to come up with a path forward for how to clean up surface_fluxes.c.

@tbohn
Copy link
Contributor Author

tbohn commented Dec 8, 2014

I'll need some time to think about this... Can we discuss later this week?

On Sun, Dec 7, 2014 at 5:08 PM, Joe Hamman notifications@github.com wrote:

@tbohn https://github.com/tbohn - now that we've removed the DIST_PREC
code and gone ahead with the other cleanup tasks (#162
#162), do you think there is
anything else to do here? If this will be part of the 5.0 release, we need
to come up with a path forward for how to clean up surface_fluxes.c.


Reply to this email directly or view it on GitHub
#31 (comment).

@jhamman
Copy link
Member

jhamman commented Aug 1, 2015

@bartnijssen and @tbohn - is something that we think is going to happen for 5.0? It has been idle for 8 months or so now?

@bartnijssen
Copy link
Member

@jhamman : I am going to move this to "someday". Any change in the iteration sequence is likely to change the answer, something that we don't want as part of 5.0. I'll leave it to @tbohn to take a look and see what change he thinks would be worthwhile for a later milestone

@bartnijssen bartnijssen modified the milestones: someday, 5.0 Aug 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants