Cumulus Support

Thank you Mark

Just tracking down why my January 2001 report only shows the 31st.
Tried deleting and creating again and it’s the same. All data in the files is present. May be a data field error causing it. Think I’ll scan through it to check.

Thanks

Martyn

So i'm trying to look at the data for one specific month where I cant create a full NOAA report.

With diagnostics turned on I have run the re-create report for September 2000, which doesn't complete, and presents gthe following.


The diagnostics show:
2023-05-08 13:28:12.478 Creating NOAA monthly report
2023-05-08 13:28:12.496 Error at line 1, column 1, value '00:15' of data/Sep00log.txt : System.ArgumentOutOfRangeException: Year, Month, and Day parameters describe an un-representable DateTime.
at System.DateTime.DateToTicks (System.Int32 year, System.Int32 month, System.Int32 day) [0x0006c] in <de882a77e7c14f8ba5d298093dde82b2>:0
at System.DateTime..ctor (System.Int32 year, System.Int32 month, System.Int32 day, System.Int32 hour, System.Int32 minute, System.Int32 second) [0x00000] in <de882a77e7c14f8ba5d298093dde82b2>:0
at CumulusMX.NOAA.CreateMonthlyReport (System.DateTime thedate) [0x008dd] in <0731ed9dc26e46bdb951344b2c20e54f>:0
2023-05-08 13:28:12.497 Please edit the file to correct the error
2023-05-08 13:28:12.499 Saving monthly NOAA report as Reports/NOAAMO0900.txt

(Ignore the -6553 values these were consistent with the output of my Weather Monitor 2. Other months with this are fine)

I would appreciate a pointer in the right direction as I can't see any error at 00:15

Thanks

Martyn

It's the year, month and day that is causing a problem - that's what the error says. Although 01/09/00 looks okay to me. Perhaps a Y2K problem?

It's the year, month and day that is causing a problem - that's what the error says. Although 01/09/00 looks okay to me. Perhaps a Y2K problem?

Well, if it is year, month and day in that sequense, then 01/09/00 does not look ok.

All my records to date are in the format dd,mm,yy.

I do wonder if it is a Y2K issue (although January 2001 shows the same error).

Kind regards

Martyn

@sutne: you're sharp but that's not it.
@freddie: it says it is the date, but my eye says something different (the date looks good)

@Nottub: my twopence worth: the field of Rainfall rate has an irrational value: -6553.6
My guess is that CMX detects an error in that line and give the date (erroneously) as the field. Mark will have the definite say of course but you could start changing that value to 0.0 in the first line (or 2 or 3) and then see which line it claims the error to be in.

Nottub wrote: ↑Mon 08 May 2023 1:57 pm All my records to date are in the format dd,mm,yy.

???? you mean dd/mm/yy I assume

Nottub wrote: ↑Mon 08 May 2023 1:57 pm I do wonder if it is a Y2K issue (although January 2001 shows the same error).

I don't think it will be if you're seeing the same error with later dates.

Are all your records consistently dd/mm/yy?

HansR wrote: ↑Mon 08 May 2023 1:59 pm

Nottub wrote: ↑Mon 08 May 2023 1:57 pm All my records to date are in the format dd,mm,yy.

???? you mean dd/mm/yy I assume

Yes dd/mm/yy.

HansR wrote: ↑Mon 08 May 2023 1:59 pm @sutne: you're sharp but that's not it.
@freddie: it says it is the date, but my eye says something different (the date looks good)

@Nottub: my twopence worth: the field of Rainfall rate has an irrational value: -6553.6
My guess is that CMX detects an error in that line and give the date (erroneously) as the field. Mark will have the definite say of course but you could start changing that value to 0.0 in the first line (or 2 or 3) and then see which line it claims the error to be in.

I'll try it, although all my reords up to the change to the Vantage Pro in 2021 have the same values as this wasn't part of the WM2 functionality.

Thanks

Martyn

HansR wrote: ↑Mon 08 May 2023 1:59 pm @sutne: you're sharp but that's not it.
@freddie: it says it is the date, but my eye says something different (the date looks good)

@Nottub: my twopence worth: the field of Rainfall rate has an irrational value: -6553.6
My guess is that CMX detects an error in that line and give the date (erroneously) as the field. Mark will have the definite say of course but you could start changing that value to 0.0 in the first line (or 2 or 3) and then see which line it claims the error to be in.

Changed the first three rainfall rates to '0' and still 00:15 is highlighted as an error.


Kind regards
Martyn

The format of the rainrate must be 0.0 (not sure if that causes an error)

HansR wrote: ↑Mon 08 May 2023 2:25 pm The format of the rainrate must be 0.0 (not sure if that causes an error)

Changed to 0.0 and still 00:15 is highlighted.

I'll keep looking.

Martyn

Have you checked the data files for non-printable characters? Open them in a decent editor like notepad++ and you should be able to see.

True