Here's the output from my system (VP2) using a script similar in spirit to that provided by Vince. It's odd that some field's i'd expect, like wind direction, appear to not show up about half the time, but that is probably on my end. But it doesn't appear I am getting any spurious leaf or such readings.
dateTime 930586 ET 930586 rain 930586 rainRate 930586 rxCheckPercent 930586 usUnits 930586 windGust 930586 barometer 930582 inHumidity 930582 inTemp 930582 windSpeed 929949 outTemp 929879 radiation 929878 UV 929876 outHumidity 929874 dewpoint 929850 heatindex 929850 windchill 929231 altimeter 889512 pressure 889512 consBatteryVoltage 764664 txBatteryStatus 764664 windGustDir 609688 windDir 474362 extraHumid1 0 extraHumid2 0 extraTemp1 0 extraTemp2 0 extraTemp3 0 hail 0 hailRate 0 heatingTemp 0 heatingVoltage 0 inTempBatteryStatus 0 leafTemp1 0 leafTemp2 0 leafWet1 0 leafWet2 0 outTempBatteryStatus 0 rainBatteryStatus 0 referenceVoltage 0 soilMoist1 0 soilMoist2 0 soilMoist3 0 soilMoist4 0 soilTemp1 0 soilTemp2 0 soilTemp3 0 soilTemp4 0 supplyVoltage 0 windBatteryStatus 0 On Sat, Oct 16, 2021 at 9:13 AM Vince Skahan <[email protected]> wrote: > Tom - I added a check for the last 12 months and it looks good here for > me. No extra fields in my VP2 db in the last year. > > # this checks a year ago as of this writing > for e in `cat elements`; do echo -n "$e "; echo "select COUNT(*) from > archive where ${e} is not NULL and (dateTime BETWEEN 1602864397 AND > datetime('now', 'localtime') )" | sqlite3 weewx.sdb ; done | grep -v " 0$" > | sort +1nr > > On Saturday, October 16, 2021 at 8:42:25 AM UTC-7 Tom Keffer wrote: > >> I’ll have to check my database when I get home, but if this is >> widespread, we may have to rethink our strategy of checking for data before >> generating a plot. >> >> On Fri, Oct 15, 2021 at 10:12 PM Vince Skahan <[email protected]> wrote: >> >>> On Friday, October 15, 2021 at 7:46:37 PM UTC-7 Tom Keffer wrote: >>> >>>> What triggered all this is that V4.6 figures out what to display on the >>>> basis of what's in the database. It's quite possible lots of Vantage >>>> stations are emitting bogus data for missing sensors, but no one ever >>>> bothered to plot it. I'll have to check my own database when I get home. >>>> >>> >>> Here's mine - wow is there ever some bogus data in there, but I've done >>> things like run weewx-wd for a while (then turned it off) and had a >>> Lacrosse station before switching to a VP2 ages ago, but I see thousands of >>> bogus measurements over the years when I had no soil/leaf/solar sensors >>> ever. >>> >>> I can rerun this limiting it to the last year if needed. >>> >>> ========================================= >>> My db field counts sorted by record count >>> ========================================= >>> dateTime 1437009 >>> barometer 1436996 >>> outTemp 1434802 >>> dewpoint 1434574 >>> outHumidity 1434479 >>> windGust 1423973 >>> windSpeed 1421912 >>> ET 1342089 >>> inHumidity 1342089 >>> inTemp 1342089 >>> rain 1342089 >>> rainRate 1342089 >>> heatindex 1339861 >>> windchill 1339859 >>> rxCheckPercent 1318752 >>> txBatteryStatus 1154921 >>> consBatteryVoltage 1154717 >>> windGustDir 1112577 >>> pressure 1069647 >>> altimeter 1051853 >>> windDir 962745 >>> >>> ======================= >>> (elements with lesser counts) >>> I never had leaf or soil sensors on this station >>> ======================= >>> inDewpoint 170470 >>> maxSolarRad 164396 >>> windrun 164394 >>> cloudbase 164388 >>> humidex 164388 >>> appTemp 164386 >>> extraTemp1 98776 >>> extraTemp2 98776 >>> soilMoist1 88430 >>> soilMoist2 88430 >>> soilMoist3 88430 >>> soilTemp1 65396 >>> soilTemp2 65396 >>> soilTemp3 65396 >>> extraTemp3 3638 >>> extraHumid1 2231 >>> extraHumid2 2231 >>> hail 2231 >>> hailRate 2231 >>> heatingTemp 2231 >>> heatingVoltage 2231 >>> inTempBatteryStatus 2231 >>> leafTemp1 2231 >>> leafTemp2 2231 >>> leafWet1 2231 >>> leafWet2 2231 >>> outTempBatteryStatus 2231 >>> rainBatteryStatus 2231 >>> referenceVoltage 2231 >>> soilMoist4 2231 >>> soilTemp4 2231 >>> supplyVoltage 2231 >>> windBatteryStatus 2231 >>> >>> >>> I did this by making a file called 'elements' from the schema of the >>> archive table with the element names one-per-line, then generated the >>> output by: >>> for e in `cat elements`; do echo -n "$e "; echo "select COUNT(*) >>> from archive where ${e} is not NULL" | sqlite3 weewx.sdb ; done | grep -v >>> " 0$" | sort +1nr > counts >>> >>> >>> -- >>> 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/6bf017e0-c84c-4185-97bb-23cebbf3062an%40googlegroups.com >>> <https://groups.google.com/d/msgid/weewx-development/6bf017e0-c84c-4185-97bb-23cebbf3062an%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- >> -tk >> > -- > 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/1842d45c-8104-4205-8d6c-f20aaa27712bn%40googlegroups.com > <https://groups.google.com/d/msgid/weewx-development/1842d45c-8104-4205-8d6c-f20aaa27712bn%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/CAGVdbe33TnY5HFUpMopX_wXriPrQD23uLfa1uCq4tgPH9HExUQ%40mail.gmail.com.
