That's where I'm heading.

rainRate calculations would continue to just happen because they are in the
default weewx.conf that comes with WeeWX (and have been for a long time).

But, they shouldn't crash the system.

-tk

On Sat, Mar 7, 2020 at 10:37 AM mwall <[email protected]> wrote:

>
>
> On Saturday, March 7, 2020 at 1:32:46 PM UTC-5, Tom Keffer wrote:
>>
>> This is probably being caused by the "rainRate" calculator. The default
>> is to calculate 'rainRate', despite you not having it listed in
>> [[Calculations]].
>>
>> What to do?
>>
>>    1. We could remove rainRate from the defaults, and require it to be
>>    listed in [[Calculations]]. In fact, we could remove *all* defaults.
>>    2. Or, we could catch the exception and swallow it.
>>    3. Or, both.
>>
>> I'm inclined to go with option #3.
>>
>
> what provides the best out-of-box experience, i.e.,
>
> 1) rainRate just works without having to configure it
> 2) rain/rainRate failures do not happen if someone has a schema with no
> rain/rainRate in it
>
> this pattern probably applies to every other derived calculation as well...
>
> (sorry i am not fully up to speed on all the changes to StdCalculate)
>
> m
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-development" 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-development/ab218adc-e5ec-421f-89c5-9cc66fbd3383%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-development/ab218adc-e5ec-421f-89c5-9cc66fbd3383%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-development" 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-development/CAPq0zEDnSM6N9D0%2B%3DEmvC7yWDOJKFroQ5hBMuYvZYqUO_3X55w%40mail.gmail.com.

Reply via email to