I am puzzled why a problem with May data has not been identified before as we are now in September. Is it because you don't have a
C:\Cumulus\ReportsNOAAYR2022 file, and this is first time you have tried to view/generate that report, or because you have recently edited
C:\Cumulus\data\Μαϊ22log.txt? Do you remember if you were having any issues with Cumulus on 1 May 2022? Those are the only reasons that spring to my mind as possibilities.
Do you still, one week later, have this problem? Please try again. Cumulus should have tried to update the September line of that report at every rollover since you posted in the forum.
I am assuming that you are using Cumulus 1.9.4, build 1099 from looking at the file path for the file
C:\Cumulus\data\Μαϊ22log.txt and the number of fields per line. The
View menu of Cumulus 1 has an option to view the NOAA Annual report. Your post says that was what you were doing when you saw the error? I suspect not, as
Viewing should merely access the
C:\Cumulus\Reports\NOAAYR2022 report; without any access to any data files. What actually happens when you try to VIEW the report? Maybe your problem is that the report does not exist or it stops with April 2022? If the report file does exist, can you attach it to a reply to this post.
If the report is missing, can you regenerate the report. Perhaps you were trying to do a regenerate when you saw the error? For a regenerate, Cumulus would need to read all data files relating to the year required. Can you try to regenerate the NOAA annual report now, to see whether Cumulus still says there is a fault with the May 2022 file. To help me (who uses MX now) can you can describe what selections you make in Cumulus to do a regenerate; to see if the error still exists or attach an annotated screen shot (see
https://cumuluswiki.org/a/Screen_capture) if that is easier for you.
What tool did you use to look at
C:\Cumulus\data\Μαϊ22log.txt file? Are you sure that file is still same as it was when you got the error? It may be whatever tool you used has changed something, perhaps the encoding used by the file. I opened that May 2022 file in Libre Office Calc to see if it looked right. I also read it using the Bless Hex editor to confirm there were no extra characters within the file that did not appear in a normal text view. I checked positions of commas and semicolons, and checked what characters appeared at start and end of the first few lines. Both tools suggest to me that there is nothing wrong with that first line in the area near the average wind speed 12.2 value (or indeed in a a few spot checks I made of other parts of the file). That is why I am suggesting you try to regenerate the annual report. If you still get an error relating to May 2022 file, then in your next post also attach the April 2022 file, so a working file can be compared with the failing file.
If when you try to regenerate the NOAA annual report you do see the same error message, then could you also zip up the files in
C:\Cumulus\diags and attach that zip to your reply. It is possible that some further useful information gets logged in one of the files in that directory when any NOAA report action fails (there should be a message at each rollover when the annual report is updated, as well as a message when you try to regenerate the report). It is possible you need to turn diagnostics on, please see
https://cumuluswiki.org/a/Category:Diagnostics, if you do turn debugging on, turn it off again soon afterwards as explained on same page of documentation.
If you do still see that same error,
you could make a copy of the May 2022 file, delete the first line from original file, type in manually the first line again (reading each character individually from the copy of the file) and then save the original file now it once again has all lines. I can't see why replacing the line would make any difference, but it might be worth trying.
. So, I don't understand what might have gone wrong and I receive this message. Do you 
? 