Slow Report Generation after Upgrade from 4.10.2 to 5..0

[mh081...@gmail.com]

Hi,

After Updating from 4.10.2 to 5.0.0 Report generation seems to be very slow with Belchertown Reports.

Before Update, it runs in 1.59 seconds after approx. 133 seconds. I don't know from which this come. During runtime, one Python Process takes 100% CPU

Here are some Logs:

With 4.10.2
Jan 14 00:05:17 wetter weewx[1711685] INFO weewx.manager: Added record 2024-01-14 00:05:00 CET (1705187100) to database 'weewx.sdb'
Jan 14 00:05:17 wetter weewx[1711685] INFO weewx.manager: Added record 2024-01-14 00:05:00 CET (1705187100) to daily summary in 'weewx.sdb'
Jan 14 00:05:18 wetter weewx[1711685] INFO weewx.restx: PWSWeather: Published record 2024-01-14 00:05:00 CET (1705187100)
Jan 14 00:05:18 wetter weewx[1711685] INFO weewx.restx: Wunderground-PWS: Published record 2024-01-14 00:05:00 CET (1705187100)
Jan 14 00:05:18 wetter weewx[1711685] INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 0.71 seconds
Jan 14 00:05:18 wetter weewx[1711685] INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 0.29 seconds
Jan 14 00:05:18 wetter weewx[1711685] INFO weewx.reportengine: Copied 0 files to /var/www/html/weewx
Jan 14 00:05:20 wetter weewx[1711685] INFO weewx.cheetahgenerator: Generated 12 files for report Belchertown in 1.59 seconds
Jan 14 00:05:20 wetter weewx[1711685] INFO weewx.reportengine: Copied 3 files to /var/www/html

after weewx 5.0

Jan 15 16:20:17 wetter weewxd[1530]: INFO weewx.manager: Added record 2024-01-15 16:20:00 CET (1705332000) to database 'weewx.sdb'
Jan 15 16:20:17 wetter weewxd[1530]: INFO weewx.manager: Added record 2024-01-15 16:20:00 CET (1705332000) to daily summary in 'weewx.sdb'
Jan 15 16:20:17 wetter weewxd[1530]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-15 16:20:00 CET (1705332000)
Jan 15 16:20:18 wetter weewxd[1530]: INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 0.53 seconds
Jan 15 16:20:18 wetter weewxd[1530]: INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 0.28 seconds
Jan 15 16:20:18 wetter weewxd[1530]: INFO weewx.reportengine: Copied 0 files to /var/www/html/weewx
Jan 15 16:20:18 wetter weewxd[1530]: INFO weewx.restx: PWSWeather: Published record 2024-01-15 16:20:00 CET (1705332000)
Jan 15 16:21:01 wetter CRON[12091]: (root) CMD (/root/get_picture_camera1.sh >/dev/null 2>&1)
Jan 15 16:21:01 wetter CRON[12094]: (root) CMD (/root/get_picture_webcam.sh >/dev/null 2>&1)
Jan 15 16:21:01 wetter CRON[12093]: (root) CMD (/root/get_picture_camera2.sh >/dev/null 2>&1)
Jan 15 16:22:01 wetter CRON[12139]: (root) CMD (/root/get_picture_camera1.sh >/dev/null 2>&1)
Jan 15 16:22:01 wetter CRON[12140]: (root) CMD (/root/get_picture_webcam.sh >/dev/null 2>&1)
Jan 15 16:22:01 wetter CRON[12138]: (root) CMD (/root/get_picture_camera2.sh >/dev/null 2>&1)
Jan 15 16:22:31 wetter weewxd[1530]: INFO weewx.cheetahgenerator: Generated 12 files for report Belchertown in 133.14 seconds
Jan 15 16:22:31 wetter weewxd[1530]: INFO weewx.reportengine: Copied 3 files to /var/www/html

with debug=1 i see

Jan 15 16:45:17 wetter weewxd[12965]: INFO weewx.manager: Added record 2024-01-15 16:45:00 CET (1705333500) to database 'weewx.sdb'
Jan 15 16:45:17 wetter weewxd[12965]: INFO weewx.manager: Added record 2024-01-15 16:45:00 CET (1705333500) to daily summary in 'weewx.sdb'
Jan 15 16:45:18 wetter weewxd[12965]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-15 16:45:00 CET (1705333500)
Jan 15 16:45:18 wetter weewxd[12965]: INFO weewx.restx: PWSWeather: Published record 2024-01-15 16:45:00 CET (1705333500)
Jan 15 16:45:18 wetter weewxd[12965]: INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 1.13 seconds
Jan 15 16:45:19 wetter weewxd[12965]: INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 0.34 seconds
Jan 15 16:45:19 wetter weewxd[12965]: INFO weewx.reportengine: Copied 5 files to /var/www/html/weewx
Jan 15 16:45:19 wetter weewxd[12965]: INFO user.belchertown: version 1.3.1
Jan 15 16:46:01 wetter CRON[13306]: (root) CMD (/root/get_picture_camera2.sh >/dev/null 2>&1)
Jan 15 16:46:01 wetter CRON[13305]: (root) CMD (/root/get_picture_camera1.sh >/dev/null 2>&1)
Jan 15 16:46:01 wetter CRON[13307]: (root) CMD (/root/get_picture_webcam.sh >/dev/null 2>&1)
Jan 15 16:47:01 wetter CRON[13357]: (root) CMD (/root/get_picture_camera1.sh >/dev/null 2>&1)
Jan 15 16:47:01 wetter CRON[13358]: (root) CMD (/root/get_picture_camera2.sh >/dev/null 2>&1)
Jan 15 16:47:01 wetter CRON[13360]: (root) CMD (/root/get_picture_webcam.sh >/dev/null 2>&1)
Jan 15 16:47:31 wetter weewxd[12965]: INFO weewx.cheetahgenerator: Generated 12 files for report Belchertown in 132.16 seconds
Jan 15 16:47:31 wetter weewxd[12965]: INFO weewx.reportengine: Copied 40 files to /var/www/html

[Tom Keffer]

We have seen this before. The problem turned out to be the use of synthetic types. 

For example, if ET is not in your database, V5 will calculate it on the fly, which can be slow. V4.10 would just return the tag.

To find the culprit, you'll have to first isolate the template that is causing the problem, then start deleting tags until you see a difference in runtime. Slow, but it will work.

Or, it's possible it's something else. Let us know what you find.

-tk

--
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/c18f5ddb-c2a9-4ba5-bfd2-31c7b4af03a5n%40googlegroups.com.

[mh081...@gmail.com]

Ok thanks so far. I will analyze further.

[Karen K]

@Tom: May be, you want to have a look into the belchertown.py file. It contains a lot of SQL queries, that do not use the normal way to access the WeeWX database. They are used to get several alltime statistics and other aggregations. Could there be some reason?

[Tom Keffer]

I don't really want to debug Pat's file. It's huge and, as you say, does things in a very non-standard way. I was hoping someone more familiar with it (Pat?) could take a look.

On Thu, Jan 18, 2024 at 5:23 AM Karen K <kk44...@gmail.com> wrote:

@Tom: May be, you want to have a look into the belchertown.py file. It contains a lot of SQL queries, that do not use the normal way to access the WeeWX database. They are used to get several alltime statistics and other aggregations. Could there be some reason?

--

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/bbb39ec1-5663-4c39-856d-94d3b43ed650n%40googlegroups.com.

[vince]

Tom - can you point us to where 'synthetic types' are documented in layman's terms so we know how to look for them ?

The pattern so far seems to be (a) Belchertown and (b) certain drivers that might not have complete measurement sets.   I see Acurite and Interceptor in a couple reports if I remember correctly.

I did a post yesterday with some timings for v5 pip + 'unaltered' Belchertown on a pi3+ vs 17+ years of old (vp2) and a little new (simulator) data that showed that v5+Belchertown seem to work ok if you have relatively complete data in the db.  I have to guess the systems having problems have something that is now being calculated in v5 that wasn't calculated before (maybe ET or something solar?) but that's just a guess.

Can the problem reporters point us to a working website so we can see their Belchertown web pages etc. ?

[bell...@gmail.com]

Vince,

Does this help?

http://www.weewx.com/docs/5.0/reference/weewx-options/stdwxcalculate/
rich

[vince]

Dunno.  Tom uses the term 'synthetic' but that is not in any docs I can find.  I can find it only twice in some tests buried in the git repo.

[Tom Keffer]

Sorry. "Synthetic" isn't the best word.

What I mean are plots and statistics of derived types, such as ET or, for some hardware, windchill. In previous versions of WeeWX they were not first class citizens. For example, only types that appeared in the database could be plotted. Now if there's an xtype formula for them, they can be plotted. But, that can take a lot of processing power.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a31666f3-a1bf-4323-aad3-f29dafd17bb8n%40googlegroups.com.

[vince]

Thanks. So how do the victims know where they are inducing that new issue or how they can disable the new behavior if theywere happy in v4? Would a feature flag be possible ?

[vince]

Followup on this one - If the original poster can check to see if their database uses the old original (small) wview schema that would likely help.  Easiest way is to look to see how many elements are in the database. One way to see how many elements you have in your db would be:

• cp weewx.sdb /var/tmp/test.sdb
• echo "select count(*) from pragma_table_info('archive');" | sqlite3 /var/tmp/test.sdb
  • (my db with the extended schema returns "114" as the count)
  • (a db with the original wview schema returns "52" as the count)

Switching to the extended schema is a bit of work and takes some time.  The details are documented at http://www.weewx.com/docs/5.0/custom/database/ with the procedure for how to switch to the new bigger schema in http://www.weewx.com/docs/5.0/custom/database/#reconfigure-using-new-schema - but be CAREFUL doing this and ALWAYS work off a copy of your db so if anything happens you can revert to a known good db.   I've done it so many years ago at this point that I'll have to defer to others for pitfalls and how they do it, but the links above are how the current docs recommend doing so.

Short description to the original Belchertown problem reporters - check your db schema.  Hopefully that's the pattern of which systems will need to take action.

[Richard Whitcombe]

In my case with the same problem, im NOT using the extended schema - it returns 52.

[mh081...@gmail.com]

Hi,

as you wish. I have no extra/extended schema in my database.

#####

root@wetter:~# echo "select count(*) from pragma_table_info('archive');" | sqlite3 /var/tmp/test.sdb
52

#####

[mh081...@gmail.com]

Hi,

as i read in the other posts about this Problem i doing now following.

weectl database add-column appTemp
weectl database add-column cloudbase
weectl database add-column visibility
weectl database add-column windrun
weectl database add-column cloud_cover
weectl database add-column aqi

weectl database calc-missing

Answer all wit 'y'

Now it seems that the Problem was solved. Belchertown Reports was generated in about 6 seconds. Thanks @vince for your right direction.

##############################

Jan 19 11:09:50 wetter weewxd[293936]: INFO weewx.engine: Loading station type Vantage (weewx.drivers.vantage)
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: StdConvert target unit is 0x1
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Archive will use data binding wx_binding
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Record generation will be attempted in 'hardware'
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: Using archive interval of 300 seconds (specified by hardware)
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: StationRegistry: Registration not requested.
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: Data for station IMECKLEN47 will be posted
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Data for station MHROSTOCK will be posted
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: CWOP: Posting not enabled.
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: WOW: Posting not enabled.
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.restx: AWEKAS: Posting not enabled.
Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: service version is 0.23
Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: binding to ['archive', 'loop']
Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: topic is weather
Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: desired unit system is METRIC
Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: data will be uploaded to mqtt://pi:x...@gw.martenhinrichs.de:8883/
Jan 19 11:09:53 wetter weewxd[293936]: INFO user.mqtt: network encryption/authentication will be attempted
Jan 19 11:09:53 wetter weewxd[293936]: INFO weewx.engine: 'pyephem' detected, extended almanac data is available
Jan 19 11:09:53 wetter weewxd[293936]: INFO __main__: Starting up weewx version 5.0.0
Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Clock error is 2.69 seconds (positive is fast)
Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.engine: Using binding 'wx_binding' to database 'weewx.sdb'
Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Starting backfill of daily summaries
Jan 19 11:09:54 wetter weewxd[293936]: INFO weewx.manager: Daily summaries up to date
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.wxxtypes: Type beaufort has been deprecated. Use unit beaufort instead.
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 10:50:00 CET (1705657800) to database 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 10:50:00 CET (1705657800) to daily summary in 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 10:55:00 CET (1705658100) to database 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 10:55:00 CET (1705658100) to daily summary in 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 11:00:00 CET (1705658400) to database 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 11:00:00 CET (1705658400) to daily summary in 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Published record 2024-01-19 10:50:00 CET (1705657800)
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 11:05:00 CET (1705658700) to database 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 11:05:00 CET (1705658700) to daily summary in 'weewx.sdb'
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.engine: Starting main packet loop.
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Published record 2024-01-19 10:55:00 CET (1705658100)
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Published record 2024-01-19 11:00:00 CET (1705658400)
Jan 19 11:09:56 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-19 10:50:00 CET (1705657800)
Jan 19 11:09:57 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-19 10:55:00 CET (1705658100)
Jan 19 11:09:57 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Published record 2024-01-19 11:05:00 CET (1705658700)
Jan 19 11:09:57 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-19 11:00:00 CET (1705658400)
Jan 19 11:09:57 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-19 11:05:00 CET (1705658700)
Jan 19 11:10:01 wetter CRON[293953]: (root) CMD (/root/get_picture_camera1.sh >/dev/null 2>&1)
Jan 19 11:10:01 wetter CRON[293954]: (root) CMD (/root/get_picture_webcam.sh >/dev/null 2>&1)
Jan 19 11:10:01 wetter CRON[293956]: (root) CMD (/root/get_picture_camera2.sh >/dev/null 2>&1)
Jan 19 11:10:17 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 11:10:00 CET (1705659000) to database 'weewx.sdb'
Jan 19 11:10:17 wetter weewxd[293936]: INFO weewx.manager: Added record 2024-01-19 11:10:00 CET (1705659000) to daily summary in 'weewx.sdb'
Jan 19 11:10:18 wetter weewxd[293936]: INFO weewx.restx: Wunderground-PWS: Published record 2024-01-19 11:10:00 CET (1705659000)
Jan 19 11:10:18 wetter weewxd[293936]: INFO weewx.restx: PWSWeather: Published record 2024-01-19 11:10:00 CET (1705659000)
Jan 19 11:10:19 wetter weewxd[293936]: INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 0.99 seconds
Jan 19 11:10:20 wetter weewxd[293936]: INFO weewx.imagegenerator: Generated 30 images for report SeasonsReport in 1.42 seconds
Jan 19 11:10:20 wetter weewxd[293936]: INFO weewx.reportengine: Copied 5 files to /var/www/html/weewx
Jan 19 11:10:20 wetter weewxd[293936]: INFO user.belchertown: version 1.3.1
Jan 19 11:10:23 wetter weewxd[293936]: INFO user.belchertown: New forecast file downloaded to /var/www/html/json/forecast.json
Jan 19 11:10:26 wetter weewxd[293936]: INFO weewx.cheetahgenerator: Generated 12 files for report Belchertown in 6.25 seconds
Jan 19 11:10:26 wetter weewxd[293936]: INFO weewx.reportengine: Copied 40 files to /var/www/html

#######################################################################################################

[Richard Whitcombe]

I just did AppTemperature but its working for me.

Although i dont think i use any of the other columns as my station doesnt provide it.

Missing data calculations took about 8 minutes for 7 years of data on a Pi4.

[Cameron D]

On Friday 19 January 2024 at 4:37:05 am UTC+10 vince wrote:

The pattern so far seems to be (a) Belchertown and (b) certain drivers that might not have complete measurement sets.   I see Acurite and Interceptor in a couple reports if I remember correctly.

 No, it is any skin that tries to plot the derived parameters - the common factor is if they are not in the DB. I reported the same with the default standard Seasons skin.

[vince]

Just a quick followup re: how long it takes to reconfigure things to the new default extended schema using Blaine's db as a test...

Rather than grow old(er) trying it on a pi3+ again, I threw compute on it and did the updates in a vagrant/Parallels vm on a m1 mac mini.

weectl station reconfigure

(answer y - takes 35 secs to do this step)

mv weewx.sdb weewx.sdb.keepme

mv weewx.sdb_new weewx.sdb

weectl database rebuild-daily

(answer y - takes 88 secs to do this step)

And done.  About 3 minutes end to end on a m1 mac mini.  Pretty cool.

Initial startup and subsequent report runs were blazing fast and Belchertown worked fine.

You gotta love throwing compute at problems....

Geez these are fast.  Initial creation of a zillion NOAA files in just a few seconds.

Next runs in a fraction of a second.  Wow the m1 chip is fast.

2024-01-19T10:50:15.235599-08:00 deb12pip weewxd[3084]: INFO weewx.manager: Added record 2024-01-19 10:50:00 PST (1705690200) to database 'weewx.sdb'
2024-01-19T10:50:15.246551-08:00 deb12pip weewxd[3084]: INFO weewx.manager: Added record 2024-01-19 10:50:00 PST (1705690200) to daily summary in 'weewx.sdb'
2024-01-19T10:50:18.956902-08:00 deb12pip weewxd[3084]: INFO weewx.cheetahgenerator: Generated 128 files for report SeasonsReport in 3.67 seconds
2024-01-19T10:50:19.630892-08:00 deb12pip weewxd[3084]: INFO weewx.imagegenerator: Generated 60 images for report SeasonsReport in 0.67 seconds
2024-01-19T10:50:19.631922-08:00 deb12pip weewxd[3084]: INFO weewx.reportengine: Copied 5 files to /home/vagrant/weewx-data/public_html
2024-01-19T10:50:19.636177-08:00 deb12pip weewxd[3084]: INFO user.belchertown: version 1.3.1
2024-01-19T10:50:25.326411-08:00 deb12pip weewxd[3084]: INFO weewx.cheetahgenerator: Generated 132 files for report Belchertown in 5.69 seconds
2024-01-19T10:50:25.329042-08:00 deb12pip weewxd[3084]: INFO weewx.reportengine: Copied 40 files to /home/vagrant/weewx-data/public_html/belchertown

2024-01-19T10:55:15.234969-08:00 deb12pip weewxd[3084]: INFO weewx.manager: Added record 2024-01-19 10:55:00 PST (1705690500) to database 'weewx.sdb'
2024-01-19T10:55:15.244564-08:00 deb12pip weewxd[3084]: INFO weewx.manager: Added record 2024-01-19 10:55:00 PST (1705690500) to daily summary in 'weewx.sdb'
2024-01-19T10:55:15.412840-08:00 deb12pip weewxd[3084]: INFO weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 0.15 seconds
2024-01-19T10:55:15.507428-08:00 deb12pip weewxd[3084]: INFO weewx.imagegenerator: Generated 15 images for report SeasonsReport in 0.09 seconds
2024-01-19T10:55:15.507714-08:00 deb12pip weewxd[3084]: INFO weewx.reportengine: Copied 0 files to /home/vagrant/weewx-data/public_html
2024-01-19T10:55:15.794254-08:00 deb12pip weewxd[3084]: INFO weewx.cheetahgenerator: Generated 12 files for report Belchertown in 0.28 seconds
2024-01-19T10:55:15.794966-08:00 deb12pip weewxd[3084]: INFO weewx.reportengine: Copied 3 files to /home/vagrant/weewx-data/public_html/belchertown

[Richard Whitcombe]

Actually follow up that ive only just noticed.

Since performing this fix ive lost the "Feels like" temperature display on my skin on all pages.

[Tom Keffer]

Richard, you're going to have to give us more information than this. The only reference to "feels like" that I can find in the Belchertown skin has been commented out. Where are you seeing this?

--
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/768238c2-f5ff-4efc-9e34-7ac2bbc490a4n%40googlegroups.com.

[Colin Larsen]

I guess he means this "feels like" which as far as I know is a derived/calculated field in the skin

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEAtK9FVeuO4qztKS_xD%2B_QdzdhRFuM%3DotnjgU1w5%3DwuNQ%40mail.gmail.com.

[vince]

In index.html.tmpl......

            #if $current.appTemp.has_data
             <div class="feelslike">$obs.label.feels_like: $current.appTemp</div><!-- AJAX -->
            #end if

So he has no current appTemp value apparently.

[bell...@gmail.com]

Any’ skin is an over generalization. It depends what the skin is doing with calculated/synthetic observations. On a pi 3B+ and Blaine’s db (seems to be the defacto test data), WeeWX-JAS took approximately 24 minutes to generate charts with appTemp on its first run. On its second run, approximately 60 seconds.

Without appTemp, run one took approximately 5 1/2 minutes and run two took approximately 50 seconds.

The first run is when WeeWX-JAS pulls historical data. After that it just pulls recent/changing data for the appropriate aggregate interval. So in both cases on a new day, a new aggregate interval starts and therefore more data/processing would occur. I think it would still complete in a typical 300 second archive period.

For reference:
Run one with appTemp
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 02:43:05 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:07:08 PM EST

Run two with appTemp
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 03:07:27 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:08:27 PM EST

Run one without appTemp.
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 03:12:57 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:18:29 PM EST

Run two without appTemp.
~/small-schema.weewx-data $ date; python3 ~/weewx/src/weectl.py report run jas --config ~/small-schema.weewx-data/report.conf; date
Sat 20 Jan 2024 03:18:41 PM EST
Using configuration file /home/pi/small-schema.weewx-data/report.conf
The following reports will be run: jas
Generating as of last timestamp in the database.
Done.
Sat 20 Jan 2024 03:19:30 PM EST

rich

[Richard Whitcombe]

Just woke up so delayed reply but yep thats exactly the case.

From index.html.tmpl:

 <div class="col-sm-6">

                                        #if $current.appTemp.has_data
                                        <div class="feelslike">$obs.label.feels_like: $current.appTemp</div><!-- AJAX -->
                                        #end if

Previously this would display the "feels like" temperature below the current temperature.  Now theres simply nothing shown which suggests no data.

I cant remember if it appeared on v5 but before i fixed the database by adding AppTemp and calc-missing though.

Can see how this could more be a skin problem than weewx related though so might not be applicable to this group.

[Tom Keffer]

Make sure that appTemp appears in the [StdWXCalculate] section of your weewx.conf:

[StdWXCalculate]
    [[Calculations]]
        ...
        appTemp = prefer_hardware

Also, try running weewxd from the command line and see if appTemp is printed in the LOOP packets and archive records.  

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a8626fc1-0033-4dc6-8eae-5f595c21999an%40googlegroups.com.