Cumulus Support

I have data back to Feb 2010.
When editing all-time records the logfile only show data back to 2013.
This is due by the Mxdiag file the following: (starting at line 362 in the Mxdiag file)
"2022-10-30 14:48:56.858 GetAllTimeRecLogFile: Processing log file - data\Feb10log.txt
2022-10-30 14:48:56.861 Error parsing log file record: Input string was not in a correct format.
2022-10-30 14:48:56.861 Log record: 11-02-10,10:56,30.7,53,20.0,5.0,7.2,259,0.0,0.0,1014.5,1.2,25.4,56,7.2,30.7,32.7,,,,,33.4,,,,,,33.0,38.1
2022-10-30 14:48:56.861 GetRecordsLogFile: Error at line 1 of data\Feb10log.txt : Input string was not in a correct format.
2022-10-30 14:48:56.861 Please edit the file to correct the error
2022-10-30 14:48:56.861 GetAllTimeRecLogFile: Finished processing log file - data\Feb10log.txt
2022-10-30 14:48:56.861 GetAllTimeRecLogFile: Processing log file - data\Mar10log.txt
2022-10-30 14:48:56.865 Error parsing log file record: Input string was not in a correct format.
2022-10-30 14:48:56.865 Log record: 01-03-10,00:03,14.8,76,10.5,4.9,13.3,142,0.0,0.0,1023.9,0.6,22.5,50,12.2,14.8,14.8,,,,,14.1,,,,,,11.3,16.3
2022-10-30 14:48:56.865 GetRecordsLogFile: Error at line 1 of data\Mar10log.txt : Input string was not in a correct format.
2022-10-30 14:48:56.865 Please edit the file to correct the error"
First correct log file Apr 2013.
This data was from Cumulus 1

If I make new dayfile.txt (deleting old one first) using createmissing.exe, the dayfile.txt when loaded in the All Time records have dates from 10th Feb 2010, I can use these to check records.
Enclosed a screen dump and the Mxdiag file.
It is not a problem as the fix is just to use the dayfile provided it is correct. Don't want to recreate it to check data in the future.

I think you need to compare your more recent "good" and 2010 older "bad" monthly log files in a text editor like Notepad or Notepad++, don't use Excel.
CumulusMX Start Date looks OK (11th February 2010).
The date, time, decimal & list separators look OK.
Check you don't have a header row in the first line of the log file.
Check the format of the data fields ie. number of decimal places.
Look for any odd characters particularly at the end of the rows.
Check file format is UTF-8 without BOM.

If you post a sample of a good monthly log file we can help with the compare.

The error is because you have blank entries. CMX does not allow blanks. You do not have to have all the fields (they have been added to over the years), but if you have values in later fields then the previous fields all need a value as well - it can be some dummy value if you like.

Not ideal, but it is the way it was coded, I'll create a ToDo to change that in some future release.

Thanks Mark for the reply
I have edited each monthly log that is causing the error.
Using notepad every instance of ,, was replaced with ,0,
This enabled the correct checking of records.
As mentioned in my previous post I deleted the dayfile.txt and then ran createmissing, the program read the log files which had ,, that is before editing the log files
The new dayfile.txt had all day entries from all the log files, even the ones with the incorrect format .
After correction of the log files, in the "All Times Record Editor", the "Dayfile Values" match (nearly always) the "Logfile Value".

With your help are data files are corrected.

It is very wet in Melbourne, in October our rainfall was 235mm, with the October average 65mm, previous high rainfall for any month was back in 2010 165mm.

That's good, CreateMissing is a newer code base than CMX, The change required in CMX doesn't look too difficult, so it may get done sooner rather than later.