Nl date format also rwong for newest tags ?

[nitrx]

I get strange values well I don't get values between jan 1st and after installing the build 958, The yearrecords should be almost the same as alltime records becaus I'm running cumulus since late december 2009

screenhot (this year records) and dayfile.txt included

[steve]

I suspect this is similar to the US date format problem, but a result of your dd-mm-yy date format (with dashes). I'm changing the way I convert the dates in the next build.

[nitrx]

Just installed the 959 build I deleted the year.ini and monht.ini the results here stay the same I've dases in the date I just saw the post of https://cumulus.hosiene.co.uk/viewtopic.p ... 5&start=10 synewave it seems his data are also stuck on january first (The alltime record are fine by the way but they are read from alltime.ini I suppose)

[steve]

Look in the diags log for errors.

[nitrx]

Found an error just on januari first but cannot find it in the dayfile

Code: Select all

2-11-2010 12:46:36.075 : Error reading Dayfile around line 14: '' is not a valid floating point value

I attach the error.log and dayfile.txt perhaps I missed something

[steve]

You have the same problem as Paul in the other thread:

01-01-10;7,8;35;10:35;-6,6;23:48;0,0;13:33;996,9;04:08;1008,8;23:54;0,0;00:00;0,0;-1,6;99,3;;

[nitrx]

Soory didn't see it, so there's no solution BTW the field Max Wind Avg with time was supported on jan 28 2010 so everybody who started with cumulus before this date should have the same error ??

[steve]

Soory didn't see it, so there's no solution

Edit the file to remove the extra semicolon

BTW the field Max Wind Avg with time was supported on jan 28 2010 so everybody who started with cumulus before this date should have the same error ??

Not at all - I don't have the problem, for example. Cumulus doesn't do it; you've presumably edited the file with something that's added the extra semicolon.

[Synewave]

Steve,

My dayfile seems to use commas, not semi colons.

01/02/10,13.0,225,13:37,0.0,02:52,7.9,12:37,1007.2,00:15,1016.4,18:22,3.6,10:54,0.3,3.6,101.5,,
02/02/10,21.3,315,15:32,3.3,00:00,8.7,12:56,1002.3,15:43,1015.4,00:04,3.6,16:47,0.9,7.2,250.2,18.2,10:07

Should I just edit the file without Cumulus running and delete the last comma from the offending lines or both final commas?

[steve]

My dayfile seems to use commas, not semi colons.

They use funny characters instead of commas in some parts of the world.

Should I just edit the file without Cumulus running and delete the last comma from the offending lines or both final commas?

Yes - and good point; I hadn't twigged that there are actually two extra separators - you should remove both.

[bnwrx]

So I deleted both month and year .ini files and now this.
This looks fine, but the year.ini file does not?

[steve]

So I deleted both month and year .ini files and now this.
This looks fine, but the year.ini file does not?

I suppose I could have made a mistake in my revised code; it's hard for me to test.

Any errors in the diags file?

[bnwrx]

Looking now.....

[steve]

02/11/10 14:10:35.646 : Error reading Dayfile around line 348: '10/1/31 31:1:0.0' is not a valid date and time

[nitrx]

I'm gettig further but..

Code: Select all

2-11-2010 14:57:37.959 : Error reading Dayfile around line 38: '10-1-25 25:1:0,0' is not a valid date and time

sorry bothering you