Cumulus Support

After my weather and solar logging computer died the other day I lost a bit of data, I have not yet tried to extract anything from the HD (no time ATM), so I grabbed everything from my last backup on the 28th, installed Cumulus on this computer and downloaded the station, which didn't go back to the 28th, so there was a gap. After I remembered I had to stop the computer from sleeping, and edited and re-downloaded the latest data, I found I had a couple of duplicated days 30/5 and 1/6, and no 28th May. I removed the duplicates and thought up some reasonable approximations to put into a new line on the 28th.
There had been no error messages about the duplicates and missing day, but after I'd done the above editing in OpenOffice, I get this error:
3/06/2015 22:11:06 : Error plotting charts at line 1860 of dayfile.txt: List index out of bounds (6)
3/06/2015 22:11:06 : Please correct the error by editing dayfile.txt

+ same error repeated up to line 1987

Line 1860 was not one I edited, it was back in January, and it looks normal to me. I opened it in the Cumulus dayfile editor, and I still cant see any obvious problem. I cant find any reference to what (6) might refer to, so have come to a dead end, and have to ask for help on this one.

Below is the apparently good line 1859 and bad 1860, I hope someone can point out the error for me.

25/01/15 26 11 12:41:00 20.6 06:38:00 33.2 16:25:00 1002.44 17:03:00 1007.05 08:06:00 0 09:00:00 0 26.4 62 10 05:00:00 40 16:27:00 82 06:33:00 4.88 7.6 35.3 16:25:00 36.4 16:09:00 21.1 05:09:00 0 09:00:00 20.6 06:38:00 21.5 13:29:00 15.6 01:57:00 11 0 8.1 1346 13:26:00 16 13:15:00
26/01/15 31 9 16:59:00 19.3 05:27:00 32.8 11:41:00 1005.05 14:57:00 1008.91 00:40:00 0 09:00:00 0.4 23.4 66.9 13 12:49:00 48 11:41:00 91 13:24:00 4.17 6.3 37.5 11:39:00 37.6 11:39:00 21.2 05:27:00 0.4 13:21:00 19.3 05:27:00 23.8 13:31:00 15.5 03:34:00 10 0 5.1 1406 13:22:00 15.5 13:22:00

EDIT: I just noticed my 30 day Temp min/max/average, rain and solar radiation graphs are blank, which is no doubt related to the above error.

Thanks!

Editing in OpenOffice has apparently screwed up the formatting. The lines should be comma-separated - you might get away with space separated but it may have done other things to the formatting. I can't tell what the problem is from what you've posted, it would be better if you zipped up the file and attached it.

Edit: The timestamps have seconds, which is also likely to cause a problem.

steve wrote:Editing in OpenOffice has apparently screwed up the formatting.

Can I draw your attention to https://cumulus.hosiene.co.uk/viewtopic.p ... pen+office - there I show a screen shot (Posted: 28 Dec 2012 18:26) of what options to select or not select so Apache Open Office (or Libre Office) 'Calc' spreadsheet does not alter the data on a Cumulus log file.
In terms of line numbers with editors, any editor that involves opening and saving the whole file is editing all lines if it transforms the format as Steve points out for timestamps. So it is not just the lines where you change something.

steve wrote:The timestamps have seconds, which is also likely to cause a problem.

In his FAQ http://wiki.sandaysoft.com/a/FAQ#Error_ ... line....22 Steve says use a good text editor, that should be taken as a hint to treat all 'columns' as text, and in Important Rules on http://wiki.sandaysoft.com/a/Dayfile.tx ... de_Cumulus, it stresses turn off date recognition, and tells you the required time format.

Thanks for the replies, but after a computer hibernate overnight and re-starting Cumulus this morning, the problem seems to have vanished, without me doiung anything! No errors on startup. All I still had to do is remove the ridiculous 19 hours of sunshine from June 2nd- which was there before I edited the file, I used dayfile editor for that. The 30 day logs all display correctly now too

BTW, OpenOffice didn't mess with the formatting, the spaces instead of commas was only an artifact of copying from the spreadsheet, rather than from notepad or other text editor.

So whatever the problem was last night, it seems it went away by itself.