Thanks. I meant that I should add it, but now I don't have to. I found the list in accum.py.
Thanks again. On Monday, May 22, 2017 at 10:55:00 AM UTC-4, Tom Keffer wrote: > > Added min, max, and count extractors. Commit 64dd684 > <https://github.com/weewx/weewx/commit/64dd68465278e22cdd91b957706e547d79950724>. > > To appear in v3.7.2. > > -tk > > On Mon, May 22, 2017 at 7:30 AM, Thomas Keffer <[email protected] > <javascript:>> wrote: > >> There is no 'low' extractor, but one could certainly be added. >> >> -tk >> >> On Sun, May 21, 2017 at 7:50 PM, Craig Thom <[email protected] >> <javascript:>> wrote: >> >>> OK, so for the low value maybe I need to add a "low" accumulator type to >>> accum.py, and then I can use >>> >>> [Accumulator] >>> [[distance]] >>> extractor = low >>> >>> But it won't be any time soon. I need to get my eclipse hardware and >>> software sorted first. Only three months to go. >>> >>> >>> On Saturday, May 20, 2017 at 6:34:27 AM UTC-4, Craig Thom wrote: >>>> >>>> It appears that the "distance" value archived is the average of the >>>> values from each loop packet. Since that value appears to be whatever the >>>> last distance was, even if that was a month ago, I don't think this is a >>>> useful number. Here's an example: >>>> >>>> The value reported at the start of the archive interval is 15. >>>> There are, just for example, twenty packet loops in this interval. >>>> There is a strike with a distance of 1 just before the loop packet. >>>> The archive would then show 1 strike at a distance if 14.3. >>>> >>>> I would rather see "distance" be the minimum value for the interval. >>>> >>>> An alternative would be to make "distance" be the average for the >>>> strikes in the interval, but this would require two things: >>>> Only counting the packets in which strikes_total changes, and >>>> weighting the values by the number of strikes per loop packet >>>> (strikes_total delta). >>>> >>>> So, I think I see how to do the minimum. I could add a column >>>> "distanceMinimum", add self._mimimums, and write functions >>>> _calculate_minimum(self, pkt) and _calculate_minimums(label, newtotal, >>>> oldtotal). >>>> >>>> Would that be the best way? >>>> >>>> Average distance per strike looks a lot trickier, since the values in >>>> some look packets wouldn't count, and the values of some would count more >>>> than others, and the distance value need not change for it to be useful. >>>> >>> -- >>> 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] <javascript:>. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- 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]. For more options, visit https://groups.google.com/d/optout.
