Cumulus Support

I found this in the FAQ , and it's just my problem that coming with the new 1.9.1 version.
On previus version 1.9 when I closed shortly Cumulus also take some minutes to end, but now take hours and then I've to close from task manager.

I closed Cumulus, the 'please wait' form appeared, but Cumulus didn't close, even after several minutes
If you've closed Cumulus shortly after it has downloaded a lot of data from the logger, it can take a while for the logging thread to get everything written away to disk, and Cumulus won't close until this has completed. However, in some circumstances, there seems to be a situation where Cumulus will never close, so you will need to close it with task manager. If you think you know what conditions cause this to happen, please let me know.

Please zip up the diags folder and attach it.

here the diags, Steve

You're trying to close it shortly after starting it, and it's still sending the logger entries to Weather Underground, so all of the uploads which haven't been processed yet have to time out, and this takes a long time. You need to give it chance to finish doing the uploads; I suppose there really ought to be an indication that it's still doing the WU upload, and also possbly prevent itself being closed.

yes probaly it is but previous version workets quite different, because after some minutes closed it anyway.
Please can I go back to 1.9 whitout lost data?

Loris58 wrote:yes probaly it is but previous version workets quite different, because after some minutes closed it anyway.
Please can I go back to 1.9 whitout lost data?

I don't understand why you would want to do that, when the problem is that you're not waiting long enough for the WU update to complete, and the simple circumvention is to give it enough time to update. Why not just turn off WU updating if you're not bothered about allowing it to do all of the updates?

The previous version closed because it didn't have the WU 'catch up' facility, so there would be large gaps in your WU data. You can go back to 1.9.0 if you wish, but bear in mind that I can only give support for the latest version.

Steve look, last time I let Cumulus open for quit an our before close it then I let my pc on for several ours
but a the end I must close Cumulus by task manager, so why.

I can't see anywhere in the diags files where you let it run for an hour before closing it:

17/04/2011 09.55.43.625 . Cumulus 1.9.1 Build 989 startup
17/04/2011 10.32.46.468 . MainForm.FormClose

17/04/2011 10.33.07.828 . Cumulus 1.9.1 Build 989 startup
17/04/2011 10.34.00.453 . MainForm.FormClose

22/04/2011 00.37.04.562 . Cumulus 1.9.1 Build 989 startup
22/04/2011 00.43.33.969 . MainForm.FormClose

The one above is one where it was still updating WU; it had done 54 updates which had only taken about a minute. It still had over 1200 to do when you closed it, causing the problem - all of the 1200 would have to time out. You closed it immediately after the 'please wait' form closed, not after an hour.

22/04/2011 01.02.36.766 . Cumulus 1.9.1 Build 989 startup
22/04/2011 01.03.27.422 . MainForm.FormClose

22/04/2011 01.07.57.672 . Cumulus 1.9.1 Build 989 startup
22/04/2011 01.08.17.484 . MainForm.FormClose

23/04/2011 07.24.04.312 . Cumulus 1.9.1 Build 989 startup
23/04/2011 07.28.52.296 . MainForm.FormClose

The one above is another where you closed it immediately after the 'please wait' form had closed, while it was still updating WU. It had done 112 updates and had about 200 to go; it would have completed those in 2 or 3 minutes.

23/04/2011 08.49.16.468 . Cumulus 1.9.1 Build 989 startup
23/04/2011 08.49.57.109 . MainForm.FormClose

24/04/2011 06.54.34.453 . Cumulus 1.9.1 Build 989 startup
24/04/2011 06.58.54.343 . MainForm.FormClose

Again, you closed it immediately after the 'please wait' form had closed, while it was updating WU. It had done 136 updates and had another 130 updates to go.

24/04/2011 07.21.56.375 . Cumulus 1.9.1 Build 989 startup
24/04/2011 07.42.32.984 . MainForm can close

So in no cases had Cumulus been running for an hour before you tried to close it. In almost every case, you closed it immediately after it had finished downloading the data from the logger.

It seems that the way you use Cumulus is that you only run it occasionally, and only long enough to download the data from the logger. This means that with 1.9.0, you would have never had any WU updates at all. With 1.9.1, if you leave it for long enough, you will get a full set of WU updates. If you're not interested in WU updates, as it seems you're not, then you can avoid the problem you're seeing with 1.9.1 simply by turning WU off. If you go back to 1.9.0 that's what you'll effectively get anyway.

Ok Steve, I'm sorry I'm not understood how Cumulus works with WU
Please sorry again

Loris

Loris58 wrote:Ok Steve, I'm sorry I'm not understood how Cumulus works with WU

I'm not saying that this isn't an issue - it is, it shouldn't be like this, and I need to do something about it to stop it taking hours to close (if at all) when someone uses it in the way that you do (e.g. put a warning that it's still updating WU, and possibly make the 'catch up' facility optional).

I've put three changes into the next release:

1. Make 'catch up' optional.
2. Put an indicator on the main window to show when 'catch up' is happening
3. Make sure that Cumulus aborts 'catch up' (so closes quicker) if it's closed while it's happening.