Hi Gary, yes the LOOP DATA is taken when running weewx directly. (normally I use the daemon process, I don't seem to be able to run the daemon process and the weewx directly at the same time).
For the units I've added an extra column to the table, as there are some variations. Also I've added an extra row for the "REC:" records taken while running weewx directly. The archive data is not from querying the database directly. I have a report that produces this file. *Timestamp* *Wind Gust* *Wind Speed* *Source* *units* *recorded* 2020-02-27 18:27:24 GMT windGust: 0.683510010315 windSpeed: 0.310686368325 LOOP DATA usUnits: 1 weewx direct (stdout) 2020-02-27 18:27:32 GMT windGust: 0.683510010315 windSpeed: 0.310686368325 LOOP DATA usUnits: 1 weewx direct (stdout) 2020-02-27 18:27:40 GMT windGust: 0.683510010315 windSpeed: 0.49709818932 LOOP DATA usUnits: 1 weewx direct (stdout) 2020-02-27 18:27:56 GMT windGust: 0.683510010315 windSpeed: 0.062137273665 LOOP DATA usUnits: 1 weewx direct (stdout) 2020-02-27 18:28:12 GMT windGust: 0.683510010315 windSpeed: 0.12427454733 LOOP DATA usUnits: 1 weewx direct (stdout) 2020-02-27 18:28:27 GMT windGust: 0.683510010315 windSpeed: 0.12427454733 LOOP DATA usUnits: 1 weewx direct (stdout) 27/02/2020 18:29 GMT 4 0.4 CONSOLE km/h visually 27/02/2020 18:28:00 GMT 1.100002734 0.400000994 ARCHIVE km_per_hour(2) (weewx.conf) weewx reports 2020-02-27 18:28:00 GMT windGust: 0.683510010315 windSpeed: 0.295152049909 REC usUnits: 1 weewx direct (stdout) Simon On Friday, February 28, 2020 at 8:48:57 PM UTC, gjr80 wrote: > > Hi, > > Going to need a little more info, in particular units. The LOOP DATA I > presume is taken from the screen when running WeeWX directly? If so what > units are being used, what is the usUnits value? 1, 16 or 17? Likewise the > archive data, what is the usUnits value? If the archive data was obtained > by querying the database the units will be dependent on your database unit > system and may not be the same units displayed on the console or reported > by the weather station driver. Finally what units is your console > displaying? > > Gary > > On Saturday, 29 February 2020 01:48:31 UTC+10, Simon Davies wrote: >> >> Is there a way to determine how the wind (gust and speed) LOOP data is >> converted into the console data and the archive data. Below is a small >> table of data showing LOOP, CONSOLE and ARCHIVE for the same/similar time. >> >> *Timestamp* >> >> *Wind Gust* >> >> *Wind Speed* >> >> *Source* >> >> 2020-02-27 18:27:24 GMT >> >> windGust: 0.683510010315 >> >> windSpeed: 0.310686368325 >> >> LOOP DATA >> >> 2020-02-27 18:27:32 GMT >> >> windGust: 0.683510010315 >> >> windSpeed: 0.310686368325 >> >> LOOP DATA >> >> 2020-02-27 18:27:40 GMT >> >> windGust: 0.683510010315 >> >> windSpeed: 0.49709818932 >> >> LOOP DATA >> >> 2020-02-27 18:27:56 GMT >> >> windGust: 0.683510010315 >> >> windSpeed: 0.062137273665 >> >> LOOP DATA >> >> 2020-02-27 18:28:12 GMT >> >> windGust: 0.683510010315 >> >> windSpeed: 0.12427454733 >> >> LOOP DATA >> >> 2020-02-27 18:28:27 GMT >> >> windGust: 0.683510010315 >> >> windSpeed: 0.12427454733 >> >> LOOP DATA >> >> 27/02/2020 18:29 GMT >> >> 4 >> >> 0.4 >> >> CONSOLE >> >> 27/02/2020 18:28:00 GMT >> >> 1.100002734 >> >> 0.400000994 >> >> ARCHIVE >> >> Weather station (Maplin N23DQ, fineoffset) >> >> The reason for asking is that the display(archive) data is different to >> the console data and I'm trying to understand at what point the error is >> occurring. e.g. between LOOP and console or between console and archive. >> >> >> -- 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/1252c306-1b10-4da1-81f1-9d0e48e00b25%40googlegroups.com.
