Re: [weewx-user] DegreeDays accessible by a third-party application

It's not my priority at the moment, but I'll come back to you with my solution Thank you all for your kindness Le mercredi 18 mai 2022 à 22:10:30 UTC+2, charlescu...@gmail.com a écrit : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Wed, 18 May 2022 09:29:08 -0700 (PDT) > PC wrote:

Re: [weewx-user] DegreeDays accessible by a third-party application

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 18 May 2022 09:29:08 -0700 (PDT) PC wrote: > Why make it simple when you can make it complicated!? Well, you could probably lift degree-days (DD) from the so-called NOAA Summary Reports, which are *.txt files under $HTML_ROOT/NOAA. See the

Re: [weewx-user] DegreeDays accessible by a third-party application

Whatever works best for you... On Wed, May 18, 2022 at 11:52 AM PC wrote: > Yes, > but I need these values day after day. > What my old program was doing. > It therefore seems to me that the best solution is to create a specific > table. > I would create it with my old data, then I would read th

Re: [weewx-user] DegreeDays accessible by a third-party application

Yes, but I need these values day after day. What my old program was doing. It therefore seems to me that the best solution is to create a specific table. I would create it with my old data, then I would read the Archive table of the MySQL base of Wewx, to add the new value daily. Le mercredi 18

Re: [weewx-user] DegreeDays accessible by a third-party application

Well, it would be easy enough to create a CSV file using a WeeWX template. It could then be imported into Excel. Something like... #for $month in $year.months #if $month.outTemp.has_data $month.dateTime.format($YM), $month.heatdeg.sum.format($Temp,$NONE,add_label=False), $month.cooldeg.sum.format(

Re: [weewx-user] DegreeDays accessible by a third-party application

" You haven't said what your use case is. It might be quite simple." You are right. My goal is to make statistical comparisons since the start of my surveys (from 2011 with a "View View" and which will be placed in another table). Previously, under Windows 7, I was doing these statistics in VBA m

Re: [weewx-user] DegreeDays accessible by a third-party application

You haven't said what your use case is. It might be quite simple. For example, here is how you would calculate total heating degree-days for this month in Python, using xtype. Most of the complexity is in calculating the starting and stopping times: import time import weewx.manager import weewx.x

Re: [weewx-user] DegreeDays accessible by a third-party application

Yes, I just looked at, it's really too complicated to implement for what I want to do. It would even be easier to calculate him himself! Besides, in French, we say "why make it simple when you can make it complicated!?" It is not complicated to calculate it once a day and store it in a small tab

Re: [weewx-user] DegreeDays accessible by a third-party application

Okay, I don't know this "xtype", I'm going to watch. I already have the difficulty of "binding" 2 tables (see my previous post) One more challenge, it's pleasant! Le mercredi 18 mai 2022 à 18:01:45 UTC+2, tke...@gmail.com a écrit : > Degree-days are calculated on the fly as an xtype >

Re: [weewx-user] DegreeDays accessible by a third-party application

Degree-days are calculated on the fly as an xtype variable. Where do you need them? For example, for a template, the total degree-days for a month could be calculated as $month.heatdeg.sum. If you need access from an outside applic