Best way to get available cheetah variables

[Hyrules Hyrules]

Hi,

I`ve been playing with the Cheetah generator and I have generated some files with it without any real problem but my main question

is what would be the best way to get the available variables in the report generator ? I went through the documentation finding most of my answers but

some variables are not documented (understandable because each station is different) so I was wondering if anybody has any insight

about this. Is my only option digging through the driver ?

Thanks

[vince]

Does http://www.weewx.com/docs/customizing.htm#report_options help any ?

It has the archive types, aggregations, and units sections.  You could probably put together a list from the combination of those. 

[Hyrules Hyrules]

 Thanks but no. I`ve already went though all the documentation of weewx and some stuff is not really documented. For example : I have a Davis Vantage Pro 2 and the stormRain variable is proper to that station. So is the stormStart but I cannot get it to work if I use $current.stormStart the generator output ?'stormStart'? so either i'm not using it properly or there is a bug in the driver. The station has also a forecast variable which is forecastIcon but I have to guess the values of the forecast because it is a float number.

[vince]

On Friday, September 27, 2019 at 4:08:04 PM UTC-7, Hyrules Hyrules wrote:

 Thanks but no. I`ve already went though all the documentation of weewx and some stuff is not really documented. For example : I have a Davis Vantage Pro 2 and the stormRain variable is proper to that station. So is the stormStart but I cannot get it to work if I use $current.stormStart the generator output ?'stormStart'? so either i'm not using it properly or there is a bug in the driver. The station has also a forecast variable which is forecastIcon but I have to guess the values of the forecast because it is a float number.

I think you might have to actually work a little more unfortunately.

Is the value you're looking for in the  archive table schema ?   Is it in the LOOP schema ?   What does your driver sources say ? The code always wins.

A quick read of vantage.py says it's in the LOOP packet but not in the archive packet, so you need to tweak your config files a bit.  Do a google search of the group archives for "Vantage stormStart".  There are a few threads for that one in particular.

Do some more digging.  The previous threads have the gory details.

 

[Hyrules Hyrules]

Yes i have actually started doing exactly that. Thanks for the info and help

[gjr80]

Unfortunately there is no single link (largely because the answer is 'it depends'). Firstly, the Archive Types appendix in the Customisation Guide will tell you what fields you have in your archive (provided you are using the default schema, if not then adjust accordingly). Secondly, the Tags section and the Aggregation types appendix, both in the Customisation Guide, give you details on what tags and aggregates you can use. The third corner of the triangle is what data is actually coming off your station. If you have a station that is documented in the Hardware Guide it is a little easier, you can refer to the station data section for your station (eg Vantage station data) and see what fields are available in archive records and loop packets. Generally speaking, if your station supports a given field, archive fields will be available through the tag system but loop fields may not (software record generation being one exception).

If your station is not documented in the Hardware Guide then you need to do a little sleuthing to find out what your station/driver emits, sometimes the author has documented this, other times it is in the comments at the start of the driver file other times you need to analyses the driver code yourself.

Hope this helps.

As for your stormStart problem, this has been an issue and will be fixed in the 4.0 release.

Gary  

[Hyrules Hyrules]

as usual thanks Gary. I'm getting eager to see version 4.

[Thomas Keffer]

One thing you could try is run your station from the command line, then see what it prints on the console under REC. Those are the observation types available to a report. 

-tk

On Sat, Sep 28, 2019 at 6:57 AM Hyrules Hyrules <hyr...@gmail.com> wrote:

as usual thanks Gary. I'm getting eager to see version 4.

--
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 weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/b9f84940-1ea9-49e2-bd41-5388bd4b7715%40googlegroups.com.

[Hyrules Hyrules]

How would I proceed in the command line with bash $variable ?

[Thomas Keffer]

I think we are misunderstanding each other. Run weewxd directly from the command line. You will see it print something like:

LOOP:   2019-09-30 14:15:16 PDT (1569878116) altimeter: 30.111448577506454, appTemp: 47.3810153041827, barometer: 30.134, cloudbase: 3098.3094040726965, consBatteryVoltage: 4.66, dateTime: 1569878116, dayET: 0.024, dayRain: 0.01, dewpoint: 40.14743862208014, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, extraTemp1: 55.0, forecastIcon: 6, forecastRule: 44, heatindex: 50.7, humidex: 50.7, inDewpoint: 51.18513133422766, inHumidity: 52.0, insideAlarm: 0, inTemp: 69.6, leafWet4: 0.0, maxSolarRad: 623.4938707469452, monthET: 3.26, monthRain: 1.87, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 50.7, pressure: 29.366959084199284, radiation: 264.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, rel_pressure: 130.13400000000001, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.84, stormStart: 1569567600, sunrise: 1569852288.0, sunset: 1569896208.0, txBatteryStatus: 0, usUnits: 1, UV: 1.8, windchill: 50.7, windDir: 117.0, windGust: 3.0, windGustDir: 111.0, windSpeed: 2.0, windSpeed10: 2.0, yearET: 33.03, yearRain: 24.02
REC:    2019-09-30 14:15:00 PDT (1569878100) altimeter: 30.109449512890514, appTemp: 47.82575954019759, barometer: 30.132, cloudbase: 3097.2480835555257, consBatteryVoltage: 4.66, dateTime: 1569878100, dayET: 0.024, dayRain: 0.01, dewpoint: 40.05210843235569, ET: 0.0, extraAlarm1: 0.0, extraAlarm2: 0.0, extraAlarm3: 0.0, extraAlarm4: 0.0, extraAlarm5: 0.0, extraAlarm6: 0.0, extraAlarm7: 0.0, extraAlarm8: 0.0, extraTemp1: 55.0, forecastIcon: 6.0, forecastRule: 44, heatindex: 50.6, highOutTemp: 50.7, highRadiation: 271.0, highUV: 1.9, humidex: 50.6, inDewpoint: 51.277374524999615, inHumidity: 52.0, insideAlarm: 0.0, inTemp: 69.7, interval: 5, leafWet4: 0.0, lowOutTemp: 50.5, maxSolarRad: 623.7943092832924, monthET: 3.26, monthRain: 1.87, outHumidity: 67.0, outsideAlarm1: 0.0, outsideAlarm2: 0.0, outTemp: 50.6, pressure: 29.36500061429528, radiation: 267.0, rain: 0.0, rainAlarm: 0.0, rainRate: 0.0, rel_pressure: 130.132, rxCheckPercent: 99.08333333333333, soilLeafAlarm1: 0.0, soilLeafAlarm2: 0.0, soilLeafAlarm3: 0.0, soilLeafAlarm4: 0.0, stormRain: 0.84, stormStart: 1569567600.0, sunrise: 1569852288.0, sunset: 1569896208.0, txBatteryStatus: 0, usUnits: 1, UV: 1.9, windchill: 50.6, windDir: 67.5, windGust: 3.0, windGustDir: 67.5, windrun: 0.08333333333333333, windSpeed: 1.0, windSpeed10: 1.0, yearET: 33.03, yearRain: 24.02
LOOP:   2019-09-30 14:15:17 PDT (1569878117) altimeter: 30.111448577506454, appTemp: 47.3810153041827, barometer: 30.134, cloudbase: 3098.3094040726965, consBatteryVoltage: 4.66, dateTime: 1569878117, dayET: 0.024, dayRain: 0.01, dewpoint: 40.14743862208014, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0, extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0, extraAlarm8: 0, extraTemp1: 55.0, forecastIcon: 6, forecastRule: 44, heatindex: 50.7, humidex: 50.7, inDewpoint: 51.18513133422766, inHumidity: 52.0, insideAlarm: 0, inTemp: 69.6, leafWet4: 0.0, maxSolarRad: 623.4750447378664, monthET: 3.26, monthRain: 1.87, outHumidity: 67.0, outsideAlarm1: 0, outsideAlarm2: 0, outTemp: 50.7, pressure: 29.366959084199284, radiation: 264.0, rain: 0.0, rainAlarm: 0, rainRate: 0.0, rel_pressure: 130.13400000000001, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0, soilLeafAlarm4: 0, stormRain: 0.84, stormStart: 1569567600, sunrise: 1569852288.0, sunset: 1569896208.0, txBatteryStatus: 0, usUnits: 1, UV: 1.8, windchill: 50.7, windDir: 117.0, windGust: 3.0, windGustDir: 111.0, windSpeed: 2.0, windSpeed10: 2.0, yearET: 33.03, yearRain: 24.02

Most of the print out will be LOOP packets, but every few minutes (depending on your chosen archive interval), there will be an archive record, marked by REC (highlighted in the example above). The non-None observation types are the ones you have to work with.

-tk

On Mon, Sep 30, 2019 at 12:49 PM Hyrules Hyrules <hyr...@gmail.com> wrote:

How would I proceed in the command line with bash $variable ?

--

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 weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/972145ed-35b8-4c2b-94e2-744299a6e980%40googlegroups.com.

[Hyrules Hyrules]

Got it thanks.