Hi Gary ... Thanks !!

Also Time of min-max temp still not updated 

On Tuesday, March 8, 2022 at 12:31:21 AM UTC+2 gjr80 wrote:

> > How do you find me...??
> That was not too difficult, your user name sounded very Greek so I looked 
> at the WeeWX user map <http://weewx.com/stations.html> and there are not 
> that many stations in Greece. I knew you were using SDR and there are not 
> that many SDR stations around. Finding clientraw.txt was the clincher.
>
> > 1. I cant change path of clientrraw.txt (always is saved to puplic_html 
> and i want to public_html/WD) even if i edit the rtcr.py
> I still need to finish off documenting the WeeWX-Saratoga options. You can 
> change the location that clientraw.txt is saved using the rtcr_patth 
> setting under [WeewxSaratoga] [[RealtimeClientraw]] in weewx.conf, eg:
>
> [WeewxSaratoga]
>     ....
>     [[RealtimeClientraw]]
>         # Path to clientraw.txt. Can be an absolute or relative path. 
> Relative
>         # paths are relative to HTML_ROOT. Optional, default setting is to 
> use
>         # HTML_ROOT.
>         rtcr_path = /home/weewx/public_html 
>
> Until I finish documenting the options the best source of 
> RealtimeClientraw (the service that WeeWX-Saratoga uses to generate 
> clientraw.txt) is the comments at the top of rtcr.py. I don't recommend 
> editing the rtcr.py code to force things, it is far to easy to break 
> something else, it is a complex service.
>
> > 2. The dewpoint gets value 0 (i attached a screen shot  when i made 
> again the upgrade)
> I have a suspicion this could be related to the gaps I saw in some of your 
> plots, depending on your system dewpoint may be a calculated value and if 
> any of the prerequisites for its calculation are missing it will not be 
> calculated and clientraw.txt will then display it as 0.0.
>
> > 3. When i made a split with python to clientraw.txt to data[174] for 
> example i get 0 value
> It is possible there could be some corner cases that are causing a field 
> to be omitted when clientraw.txt is generated, I would like to think I have 
> hardened the code to prevent this but it is possible. If one field is 
> omitted that shuffles every later field along and they become out of place. 
> If you use a clientraw.txt parser like the one at Saratoga Weather 
> <https://saratoga-weather.org/wdparser.php> it is usually pretty obvious 
> where the omission is. We can work through this one now that you have 
> installed v4.5.1 and WeeWX-Saratoga.
>
> > 4. Sometimes not always the avg_speed gets bigger values than the 
> gust_speed.
> This should not happen, again can work through.
>
> > Probably when you saw my clientraw.txt that is correct was from the 
> weewx-wd and not from Saratoga
> No, was definitely from WeeWX-Saratoga, if you look at the end of the file 
> you will see something like:
>
> 102.9 16:37 06:52 68 !!WS0.3.3!!
>
> The 'WS0.3.3' indicates WeeWX-Saratoga v0.3.3, WeatherDisplay and 
> WeeWX-WD generated clientraw.txt files terminate differently.
>
> > Now that it is raining , i noticed that rain rate and max rain rate have 
> 0.0 value
> OK. I will work through this and the other issues you have raised.
>
> > That's all for now..... :p ......I hope that i didnt inconvenience you
> Not at all, it's can be difficult to write something like 
> RealtimeClientraw and cover all the corner cases so you have to rely on 
> people finding bugs.
>
> 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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/88e288c1-a0c3-4011-a268-c7809f292a3an%40googlegroups.com.

Reply via email to