set up new activity budget analyses, at this time the _odesolver one has been thoroughly checked for bugs. It uses the odesolver to trace Tb through time rather than using the midpoint for the hour and assuming constant conditions, but it does assume you are always starting off at the beginning of the hour for a given calc (e.g. for heating or for cooling).

Have written code to compute foraging distance, radius and time, and to make activity plots