Convert Weather Display data to Cumulus?

[TgT]

converter stops if there are NULL entries in logfiles.

Code: Select all

22014lg.txt line 15854: List index out of bounds (0)

If station goes offline WD seems to write NULL next line in logfiles.

[steve]

2014-03-28 15_51_07-C__Users_steve_Downloads_22014lg %281%29.txt - Notepad++.png

Just tidy that line up.

That's the same kind of thing that sometimes happens to Cumulus log files. No coincidence, since WD apparently also uses Delphi.

[TgT]

aha ok.

What about additional data, like sun radiation, sun hours and ET?

all that data is in *lgvantagelog.txt

it would be nice to convert them too?

[steve]

Is that not working then? It seemed to work OK with the data files I was given to try.

[TgT]

oh, i'll stab my friend then! not literally!

it seems only *lg.txt were processed.

[steve]

Are you saying it didn't work? It looks for files called (m)myyyyindoorlog.txt and (m)myyyyvantagelog.txt, in the same folder as the (m)myyyylg.txt file.

[TgT]

No, friend sent only *lg.txt files, but today I got additional *vantagelog.txt ones too and they are processed.


Q: is there a chance to process *lgsun.txt too? sun hours and ET is in there, or thats just not possible?

[steve]

It already does ET from the vantage log. The lgsun file is for daily totals only, and the converter doesn't produce entries for dayfile.txt, so no, that's not possible.

[TgT]

Thanks for clarification.

[gandalf]

I have trouble now the error red light blink. Error at line 10789 of E:\Program Files\Cumulus\data\feb14log.txt : ''0,0'' is not a valid integer value.
I have look at these line with notepad++

line10789 08.02.14;15:52;6,5;87;4,5;3,5;5,4;0,0;0,0;8,8;1006,00;124,5;0,0;0;5,4;6,5;6,5;0;11;0,40;0,00;4,6;0;0,0;0,0;0,0;8,8

there is to much nulls Is these red zero a problem ?

[steve]

It's the 'bearing' and 'average bearing' values that are the problem:

08.02.14;15:52;6,5;87;4,5;3,5;5,4;0,0;0,0;8,8;1006,00;124,5;0,0;0;5,4;6,5;6,5;0;11;0,40;0,00;4,6;0;0,0;0,0;0,0;8,8

Those values should be integers, i.e. they should just be "0". But I don't understand how the converter could have written them like that, it definitely writes them as integers. That line did come from the converter, yes? It seems odd that you are converting WD data from only a couple of months ago - when did you start using Cumulus?

[gandalf]

Hi Steve,

im using Cumulus from April 2014 And i had WD for three years I must than all log files repair in excel cvs.

[steve]

I don't know how those values could have been written like that, the converter definitely uses integers for those. Have you already used Excel to edit the file? That's the kind of change which can happen if you use Excel or similar to edit the log files.

[gandalf]

I have all log files converted from WD to Cumulus. I can send you on your e-mail or send converted one log file feb14log and WD 22014lg. I just converted only in the excel i put sun hours. I have converter v1.3

I have convert these log file and these i got .

line10789 08.02.14;15:52;6,5;87;4,5;3,5;5,4;0,0;0,0;8,8;1006,00;124,5;0,0;0;5,4;6,5;6,5;0;11;0,40;0,00;4,6;0;0,0;0,0;0,0;8,8 old
line10789 08.02.14;15:52;6,5;87;4,5;3,5;5,4;0,0;0,0;8,8;1006,00;124,5;0,0;0;5,4;6,5;6,5;0;11;0,40;0,00;4,6;0;0,0;0,0;0,0;8,8 problems
line10789 08.02.14;15:52;6,5;87;4,5;3,5;5,4;184;0,0;8,8;1006,00;124,5;0,0;0;5,4;6,5;6,5;0;0;0,00;0,00;4,6;0;0,0;184;0,0;8,8 new

[steve]

I have all log files converted from WD to Cumulus. I can send you on your e-mail.

No, please don't do that. I really don't have time to start looking through lots of log files to look for problems, and it's really not reasonable to expect me to do that. If there's a problem with the file that the converter produced before you edited it with Excel, then there's really nothing I can do about it, sorry. I can only tell the computer to write an integer, I can't tell it "no, I really mean it, please write an integer"

The code in the converter which writes the log file entries is exactly the same as the code in Cumulus which writes the log file entries.