If a new type appears in the data stream, a new "scalar" accumulator will
automatically be created for it. When it comes time to extract a datum for
a new record, the average will be used by default. If you don't like that,
then you can specify a different "extractor."

You can suggest some changes here (or, better, in weewx-development), or
submit a PR on GitHub.

-tk

On Thu, Nov 12, 2020 at 11:21 AM Earl Baugh <[email protected]> wrote:

> Tom & Vince,
>
> All very helpful info!  It aligns with what I was thinking so far.  This
> wiki page on accumulators was very informative.
>
> Still got a couple questions -- I see Lightning Strikes as an
> accumulator.  But nothing for Noise_Count and Disturber_Count.
> I'd expect those were accumulators but I don't see anything that would
> feed into them.
>
> I could, I guess, add new records for Noise and Disturber and then
> accumulate them into the _Count fields... it seems like
> there is a gap here in what I see.
>
> Thoughts?
>
> And how might I give inputs on some data that I'd like to suggest be added
> to the "main-line" rather than things just in
> my copy.   Other other feature suggestions?
>
> Earl
>
> On Sat, Nov 7, 2020 at 6:04 PM Tom Keffer <[email protected]> wrote:
>
>> Generally, the way WeeWX handles extensive types (such as rain, ET,
>> energy, etc.), is that it's the amount of "stuff" seen during the
>> observation period. So, in this case, for LOOP packets, it's the number of
>> strikes detected since the last LOOP packet. For archive records, it's the
>> number of strikes detected during the archive period.
>>
>> The latter will be calculated automatically by the accumulators. See the
>> wiki article *Accumulators
>> <https://github.com/weewx/weewx/wiki/Accumulators>* for how accumulators
>> work. In particular, note that the default type of extractor for
>> lightning_strike_count is 'sum'. That means, the value in the record
>> will be filled in with the sum of all values seen in the LOOP packets over
>> the archive period, in other words, the total number of lightning strikes.
>>
>> Hope that helps.
>>
>> -tk
>>
>> On Sat, Nov 7, 2020 at 2:00 PM Earl Baugh <[email protected]> wrote:
>>
>>>
>>> On Nov 7, 2020, at 4:47 PM, vince <[email protected]> wrote:
>>>
>>> 
>>> On Friday, November 6, 2020 at 10:53:12 AM UTC-8, Earl Baugh wrote:
>>>>
>>>> I see in the weewx db schema that there are:
>>>>
>>>>  'lightning_distance',        'REAL'
>>>>  'lightning_disturber_count', 'REAL'
>>>>  'lightning_energy',          'REAL'
>>>>  'lightning_noise_count',     'REAL'
>>>>  'lightning_strike_count',    'REAL'
>>>>
>>>> [...]
>>>>
>>>
>>>
>>>> But how do I post a noise or disturber record?   That isn't clear.
>>>> Given I just see a count, I'm not sure what kind of data would be needed to
>>>> cause that to increment.
>>>>
>>>>
>>> Some gear has noise+disturber info available.  Some do not.
>>>
>>> All those elements are available if you choose to use them.
>>> But they're not mandatory.
>>>
>>> You can use them, or ignore them, or use the available fiels in the db
>>> for other uses (count every time your nest doorbell triggers and call it a
>>> disturber event :-)
>>>
>>>
>>>
>>>> I'm assuming weewx updates the strike count based on the new lightning
>>>> record.  But that's a guess...  is that guess accurate?
>>>>
>>>>
>>> Not in the least.   Your extension/service/driver would have to monitor
>>> some sensor and choose to save it in those elements in the db.
>>>
>>> It's all up to the software developer who writes the extension or
>>> service or driver or however you chose to read the sensor's available
>>> measurements and get them into the db.   After that weewx can handle the
>>> graphing and db querying etc. kind of heavy lifting for you, but you kinda
>>> have to do the low-level stuff to get the sensor info into the db.
>>>
>>>
>>> Well in this case, I’m the SW developer :-) ( it’s my day job as well
>>> ).  I’m just trying to understand the thoughts behind the “count” fields.
>>> I have access to disturber and noise events.
>>>
>>> Would it make sense to post an event that has a value of 1 for count
>>> every time?   By the name, I was thinking that this was a running total, or
>>> number that occurred since last report.
>>>
>>> I’ve added a number of extra fields to my DB already (different
>>> pollution gases, uSieverts — have a Geiger counter feeding data :-)  ) So
>>> I’m extending already, but trying to understand existing fields expected
>>> purpose. Most skins, etc. have very useful behavior already, so trying to
>>> leverage as much as possible.    Aside from battery slots ( won’t ever use
>>> those, have everything on live power) I’m slowly trying to see what I can
>>> fill in. That’s been part of the fun.
>>>
>>> Earl
>>>
>>>
>>> --
>>> 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/A39AB5D9-146C-4E44-8F99-97F72976B5CE%40baugh.org
>>> <https://groups.google.com/d/msgid/weewx-user/A39AB5D9-146C-4E44-8F99-97F72976B5CE%40baugh.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/O6A9fEFcnOc/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> [email protected].
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEDLCa5SRJQp5L4r7QuCeUFW-CXYjvZoEakcb8TWU%2B0Eow%40mail.gmail.com
>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEDLCa5SRJQp5L4r7QuCeUFW-CXYjvZoEakcb8TWU%2B0Eow%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> 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/CAAucK2Uzj9PfPfEpqZk6U-1m8h1hVEUoWGAk4nBYxaY0qa1BYg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAAucK2Uzj9PfPfEpqZk6U-1m8h1hVEUoWGAk4nBYxaY0qa1BYg%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAPq0zEDKERxOSwAHFYqNSq_%3DFTotZRSEOVN%2B3MiGgFqbscdFSQ%40mail.gmail.com.

Reply via email to