Build 963 observations

[RayProudfoot]

Hi Steve,

Build 963 has been running for over 30 minutes and not a single WU update error has been logged. Thanks for sorting that out.

The diagnostics file shows these entries...

21/11/2010 11:50:00.892 : Writing todayfile, LastUpdateTime = 21/11/2010 11:50:00 raindaystart = 26.7199993133545
21/11/2010 11:50:53.033 : Writing todayfile, LastUpdateTime = 21/11/2010 11:50:00 raindaystart = 26.7199993133545
21/11/2010 11:55:00.095 : Writing todayfile, LastUpdateTime = 21/11/2010 11:55:00 raindaystart = 26.7199993133545
21/11/2010 12:00:00.627 : Writing todayfile, LastUpdateTime = 21/11/2010 12:00:00 raindaystart = 26.7199993133545
21/11/2010 12:01:52.877 : Writing todayfile, LastUpdateTime = 21/11/2010 12:00:00 raindaystart = 26.7199993133545
21/11/2010 12:05:00.892 : Writing todayfile, LastUpdateTime = 21/11/2010 12:05:00 raindaystart = 26.7199993133545
21/11/2010 12:05:33.377 : Writing todayfile, LastUpdateTime = 21/11/2010 12:05:00 raindaystart = 26.7199993133545
21/11/2010 12:05:33.392 : Writing todayfile, LastUpdateTime = 21/11/2010 12:05:00 raindaystart = 26.7199993133545
21/11/2010 12:10:00.220 : Writing todayfile, LastUpdateTime = 21/11/2010 12:10:00 raindaystart = 26.7199993133545
21/11/2010 12:15:00.502 : Writing todayfile, LastUpdateTime = 21/11/2010 12:15:00 raindaystart = 26.7199993133545
21/11/2010 12:16:54.064 : Writing todayfile, LastUpdateTime = 21/11/2010 12:15:00 raindaystart = 26.7199993133545
21/11/2010 12:17:53.923 : Writing todayfile, LastUpdateTime = 21/11/2010 12:15:00 raindaystart = 26.7199993133545
21/11/2010 12:20:00.189 : Writing todayfile, LastUpdateTime = 21/11/2010 12:20:00 raindaystart = 26.7199993133545
21/11/2010 12:25:00.408 : Writing todayfile, LastUpdateTime = 21/11/2010 12:25:00 raindaystart = 26.7199993133545

How often should today.ini be written to? As you can see there are up to three writes for the same time on more than one occasion. Clearly it's only a minor issue but I felt I should report it.

[steve]

How often should today.ini be written to?

When Cumulus closes
When an entry is added to the log files
When the day rollover occurs
Whenever one of today's highs or lows is exceeded

I can't see the writes at the same time that you're referring to, but these are quite close:

21/11/2010 12:05:33.377
21/11/2010 12:05:33.392

But I can't see anything there indicative of a problem. If you're talking about the 'last update time', that's the time that the log file was last written to.

[RayProudfoot]

Hi Steve,

I suppose the whole point of the diagnosis file is to log everything that happens inside Cumulus even if it doesn't appear to make sense to me as a user.

If you're happy that there's no duplication of writes and that Cumulus is working as intended that's fine by me.

[steve]

I suppose the whole point of the diagnosis file is to log everything that happens inside Cumulus even if it doesn't appear to make sense to me as a user.

What I'd like to do is separate out the diagnostic stuff that is useful to a user and stuff that (in the main) only makes sense to me. The problematic build 963 was a step in that direction. If there was less technical 'chaff' in the diags files, maybe more people would be disposed to actually look at them, as you and a few others do.

[RayProudfoot]

That's a job for a warm summer evening, sitting outside with a cool beer.

For even the less technically minded a search for the word 'error' in the diagnostics file should suffice. No errors = no problems.

[DaveNZ]

That's a job for a warm summer evening, sitting outside with a cool beer.

Isn't summer about 1 day long where Steve lives

[steve]

Isn't summer about 1 day long where Steve lives

What is this "summer" of which you speak?