Weewx was rejecting readings around minus 24% (yes, -24%) because they were
outside my QC settings in StdQC of 0% to 100%. It's a problem with the
humidity sensor when the humidity is extreme.
It did this for about a day, while we had a lot of fog and rain.
I widened out the QC limits
[StdQC]
[[MinMax]]
...
outHumidity = -30, 100
and it stopped erroring on outHumidity. There were a couple on dewpointTL
after that:
Feb 26 10:31:18 weewx[23716]: rtgdthread: **** Traceback (most recent call
last):
Feb 26 10:31:18 weewx[23716]: rtgdthread: **** File
"/usr/share/weewx/user/rtgd.py", line 851, in process_packet
Feb 26 10:31:18 weewx[23716]: rtgdthread: **** data = self.calculate(
cached_packet)
Feb 26 10:31:18 weewx[23716]: rtgdthread: **** File
"/usr/share/weewx/user/rtgd.py", line 1022, in calculate
Feb 26 10:31:18 weewx[23716]: rtgdthread: **** dewpointTL = min(i for i
in [dewpointL_loop, dewpointTL] if i is not None)
Feb 26 10:31:18 weewx[23716]: rtgdthread: **** ValueError: min() arg is an
empty sequence
On Sunday, 26 February 2017 14:27:46 UTC-4, gjr80 wrote:
>
> Could you give me some more details Bill. There is a bug in the code if
> that error is being thrown, irrespective of what is going on with
> outHumidity. That trace is telling me there is no outHumidty information
> for the entire day (to 10:26am) which seems odd. When you say weeWX is
> rejecting your data is that due to a QC setting or is your driver just not
> emitting outHumidity? Just want to understand what is going on so I can
> harden up the code.
>
> Gary
>
--
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.
