I forgot to add context for this function in the notebook.
Every Spring, the partner asks when it will get warm. Until I wrote the code, the best I could do was to say that it did not get warm until after my birthday, which occurs in late April
I wrote an early version of this function to answer the question. I expanded it into a package so that I could look at other cities, partly to see if it would make sense to move there.
I made the package into a function to submit to the Function repository, but the curators think this is too limited for general inclusion, so I submit it for the community.
The code can be easily modified to show things like when it gets cold (for skiers, perhaps), or other recurring temperature patterns.
I think that this sort of thing is what WL is best at: creating custom code to answer specific questions. In the dark ages, when I started to code, there were no commercial programs, and you had to write code for everything, so pretty much all programs were of this type. The code in the notebook here, is more complex to deal with different latitudes, etc. but the original code took about 20 minutes to write, and served to answer the quite personal question we had to answer.
