[[[daychill]]]
plot_type = bar
[[[[chillHours]]]]
aggregate_type = cumulative
aggregate_interval = hour
That's what I have in the Seasons skin.conf. The way WeeWX is passing that
to my xType is calling get_aggregate for one hour blocks. I'm not sure if
there was a simpler way to do it, but I was able to get it to work using
genBatchRecords and iterating through it as a generator.
For the utah method, each record outTemp has to be compared to a scale that
gives differing chill hour multipliers. That may be why the complexity is
needed? I dunno.
I went through and changed everything to chillTime. One thing I don't know
if how to set the default for chillTime to hours. Like you said, the image
generator is doing everything in seconds. I think I know how I can rig it,
but I'm guessing there's a right way to do it.
Here's the code as it stands, if anyone could take a look through it I'd be
grateful. In particular, anything commented with ###*** needs attention
https://github.com/lordratner/weewx_chillHours/blob/main/chillTime.py
On Friday, January 21, 2022 at 7:56:40 PM UTC-6 [email protected] wrote:
> On Fri, Jan 21, 2022 at 4:27 PM Seth Ratner <[email protected]> wrote:
>
>> Also, the "one hour apart" thing was because a chart was pulling chill
>> hour accumulation for a day on an hourly interval. The Utah method can
>> actually subtract chill hours, so hourly changes wont necessarily be in
>> hour increments.
>
>
> I see. Why don't you start by just providing "get_aggregate()". The
> plotting engine should be smart enough to figure out how to chop a plot for
> a day into a cumulative plot on one hour increments.
>
> -tk
>
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/0909723f-28b9-446a-916f-0f646b66fc6cn%40googlegroups.com.
