It’s best to leave forecast.py alone and pass max_events as an arg when using
that variable.
For example, to change max_events to 100 in the tides.html.tmpl template that
ships with the extension:
Change:
#set $tides = $forecast.xtides()
to:
#set $tides = $forecast.xtides(max_events=100)
> On
In forecast.py under def xtides there is a max_events = 45. Changing that
to a higher number has sorted my problem, however you may well tell me that
could upset something.
Phil
On Thu, 4 Jun 2020, 16:10 Phil Owers, wrote:
> Hi Mathew
> Sorry I need your help again
> Im trying to display at
Hi Mathew
Sorry I need your help again
Im trying to display at least 3 months of tide time data
Jun 4 15:32:12 raspberrypi weewx[9290] INFO user.forecast: MainThread:
XTide: forecast version 3.4.0b1
Jun 4 15:32:12 raspberrypi weewx[9290] INFO user.forecast: MainThread:
XTide: interval=86400
On Wednesday, June 3, 2020 at 5:07:35 AM UTC-4, Phil Owers wrote:
>
>
> Where should this go please as Im changing the values in forecast.py where
> I couldn't find DURATION
> Sorry to be a pain
>
no pain at all! we just need a common reference frame.
when you make changes to weewx, most of
Took a while for the penny to drop but now realise they go in the
weewx.conf file.
Still cant display more than 12 days with the previous method but using the
following method
#set $periods = $forecast.weather_periods('XTide', max_events=50)
#for $period in $periods
$period.event_ts
>From the logs
Jun 3 00:05:16 raspberrypi weewx[15036] INFO user.forecast: MainThread:
XTide: forecast version 3.4.0b1
Jun 3 00:05:16 raspberrypi weewx[15036] INFO user.forecast: MainThread:
XTide: interval=1728000 max_age=2419200 location='Cromer, England'
duration=3456000
Jun 3 00:10:15
On Tuesday, June 2, 2020 at 7:51:11 PM UTC-4, Phil Owers wrote:
>
> By changing the interval and deleting the database I can now change whats
> displayed
> Interval = 86400 displays jun3 to jun4
> Interval = 864000 gives a display of Jun3rd to Jun14
> However changing the interval to anything
Thanks Mathew
By changing the interval and deleting the database I can now change whats
displayed
Interval = 86400 displays jun3 to jun4
Interval = 864000 gives a display of Jun3rd to Jun14
However changing the interval to anything higher say 20 days (1728000)
makes no difference and I did
On Tuesday, June 2, 2020 at 4:04:30 PM UTC-4, Phil Owers wrote:
>
> Whatever I change It still only displays 12 days
>
what does the log say?
exactly what configuration are you using?
you might want to stop weewx, delete the forecast database, then start weewx
if you just keep restarting
Whatever I change It still only displays 12 days
Any help will be appreciated
Thanks Phil
On Tuesday, June 2, 2020 at 1:18:55 PM UTC+1, Phil Owers wrote:
>
> Hi
> Using the tide.html.tmpl that is associated with weewx-forecast-master.zip
> it displays 12 days ish of tide times
> Im trying to
Sorry I had set the interval to 86400.
On Tuesday, June 2, 2020 at 1:18:55 PM UTC+1, Phil Owers wrote:
>
> Hi
> Using the tide.html.tmpl that is associated with weewx-forecast-master.zip
> it displays 12 days ish of tide times
> Im trying to increase this to a month or even longer. The times in
Thanks for the quick reply
Ive checked that Im using
#set $tides = $forecast.xtides
#if len($tides) > 0
#for $tide in $tides
$tide.event_ts $tide.hilo $tide.offset
#end for
and the interval and duration are set to the default
Ive check that in the forecast.sdb has tide times that go to June28
hi phil,
there are two parts to the answer:
1) how far into the future should the forecast go
2) how much of that forecast should be shown
for the first part, the default is 28 days. if you want a longer forecast,
change the 'duration' parameter. these are the parameters that control the
Thanks Matt for all of your donated labors for the weewx community; it is
very much appreciated!
When you've time, one other forecast request; i.e.
[Forecast]
[[*needed_fixes*]]
- WU new API keys and commands - already mentioned
- *NWS new Point-n-Click product*
The old
Many thanks. I give it a try and await the updated version.
> On 2019-04 -14, at 18:44, mwall wrote:
>
> please use forecast.py version 3.4.0rc2, not 3.4.0rc1.
>
> https://groups.google.com/group/weewx-user/attach/639775dd1c899/forecast-3.4.0rc2.py
>
> if that link does not work, you can
please use forecast.py version 3.4.0rc2, not 3.4.0rc1.
https://groups.google.com/group/weewx-user/attach/639775dd1c899/forecast-3.4.0rc2.py
if that link does not work, you can find 3.4.0rc2 in this thread in a
posting made 05apr2019:
Apr 14 09:39:34 cmpweewx weewx[31848]: engine: Initializing weewx version
3.9.1
Apr 14 09:39:34 cmpweewx weewx[31848]: engine: Using Python 2.7.13
(default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
Apr 14 09:39:34 cmpweewx weewx[31848]: engine: Platform
p.s. I replaced the harmonics file with the most recent version. I didn't
expect it to make a difference and apparently, it didn't:
Apr 13 11:30:15 cmpweewx weewx[21000]: forecast: XTideThread: XTide:
generating tides from 2019-04-13 00:00:00 EDT (1555128000) to 2019-05-11
00:00:00 EDT
Appreciate your prompt reply. Not sure what you mean by stack trace.
Here's the log:
Apr 13 10:15:15 cmpweewx weewx[21000]: manager: Added record 2019-04-13
10:15:00 EDT (1555164900) to database 'weewx.sdb'
Apr 13 10:15:15 cmpweewx weewx[21000]: manager: Added record 2019-04-13
10:15:00 EDT
the only way we can work magic is if you provide more information.
what does the log say (more explicitly, we need to see the stack trace from
the 'forecast failure')?
what location?
which version of harmonics?
m
--
You received this message because you are subscribed to the Google Groups
20 matches
Mail list logo
