force generation of yearly plot

[Andrew Milner]

A stupid question - but is there a way to force generation of yearly plots??  It is my understanding that the yealy plots are only generated perhaps only once per day.  I have modified the format of a yearly plot and want to see the result - but not wait until tomorrow!!  Does deleting the plot force it to be generated on the next report cycle, or only when the yearly's are next due to be generated?

confuzzed

[gjr80]

> Does deleting the plot force it to be generated on the next report cycle

Yes

Gary

[Andrew Milner]

thanks  gary.  Just got an oddity with my local server now ... my public server shows the big images of the plots just fine, but for some reason my local server has an old big image cached and keeps delivering the cached version rather than the new.  fine for small image.  how can i clear or reload the big image delivered when i click on a plot (using bootstrap skin)??  Tried shift/reload - did not work.  Not too bothered as I assume it will correct itself at some stage but am curious!!

Andrew

[gjr80]

Not real flash on bootstrap, but I seem to remember it generated big and little images using the WeeWX image generator so nothing peculiar there, the behaviour should be exactly the same. Deleting all images doesn’t work? Standard WeeWX operation for all reports and images is to regenerate if the report/image file does not exist, irrespective of any other settings.

Gary

[Andrew Milner]

Gary - the images are generated ok by weewx - big and small.  The problem was the serving of the images by the webserver.  Whilst looking around for a solution Edge has magically decided to refresh its cache so now I do not have a problem anyway.  This looks like an issue with the caching that Edge does locally rather than the server.  In fact, using explorer worked just fine for big and small - but anyway, as i say, now even Edge is working fine for big and small.

Oh well, such is life - this just goes into the "life's mysteries" category for now!!!

Andrew

[gjr80]

So the real source of the problem is revealed - Edge - ditched that and any Microsoft based browser years ago.

Gary

[Michi Kaa]

Well, I encountered the exactly same behaviour using Firefox, Ctrl+F5 fixed it. I've never seen this in Edge (most porbably, because I never used Edge :D )

[Andrew Milner]

my problem was that ctrl/f5 gave an updated small image - but not the large image.  how/when edge decided to update the large image remains a mystery!!