Cumulus Support

After seeing this thread I looked for and found my Data Log Viewer, and then I also found like Piero-

Selecting the dayfile.txt it appears to have the correct data for each day but the headings text is for the MonYYlog.txt file. There are 46 columns but only the first 26 have headings text and the last 20 do not.

Selecting the MonYYlog.txt file shows the 26 column headings text for the monthly log file and applicable/correct data below that, but also 20 more columns which have no headings text but some data in some lines. From reviewing this additional data it looks like paired data which appears to be column 27 to 46 of the dayfile.txt.

Checking the MonthYYlog.txt and dayfile.txt in my Cumulus data folder they all seem correct.

It appears that the Data Log Viewer is picking up some information from both the MonYYlog.txt and dayfile.txt files showing additional data in MonYYlog and incorrect/missing headings text in dayfile. Looking at Piero's screen shot the data would seem correct for dayfile.txt if you replaced the shown heading text with the actual headings text for the dayfile.txt file.

As noted above not all lines in the Data Log Viewer's MonYYlog have data, and since I expect it is the additional data from columns 27 to 40 of the dayfile but not all that additional data was captured in earlier versions of Cumulus and the missing data was not found/populated when using the dayfile editor. I have not been able to correlate the additional data shown in MonYYlog to a specific dayfile entry.

Sorry for being so long and perhaps difficult to understand, but wanted to share what I have found in this little investigation

Paul

Piero wrote:Please note that the display error only occurs loading the dayfile.txt, alltimelog and may13log have no problems.

Ah, you didn't make that clear. The data log viewer is only for the monthly logs. That's why the heading contains the fields for the monthly logs. There is a separate viewer/editor for dayfile.txt. The data log viewer will let you load any file you want into it, with unpredictable results if the file isn't actually a monthly log file.

In fact, I discovered another strange thing: opening the alltime.txt file multiple times will get different results, sometimes it is correct and sometimes it is not (see attached).
Paul, have you tried to edit the dayfile.txt as I described at the beginning of the thread?
Do you happen the same thing in that case?
Steve, it seems the two things could be related, do not you think?

As Steve said in his last post, the log file viewer is only meant for viewing the monthly log files. Using it to open any other file is not valid.

The data log viewer is only for the monthly logs. That's why the heading contains the fields for the monthly logs. There is a separate viewer/editor for dayfile.txt. The data log viewer will let you load any file you want into it, with unpredictable results if the file isn't actually a monthly log file.

Thanks Steve for clarifying. I should have known that as I have used the Dayfile editor in the past, and maybe also the Data Log viewer each for their own uses, but I jumped the gun last night after Piero's post. Sorry for any unnecessary comment

Paul

I apologize too, I did not know. I seemed to recognize a problem similar to what I described in post #1.
But the fact that the log file viewer, used improperly, read the same file in two different ways might not lead to the solution of the post #1? Maybe I say banalities, but my impression is that sometimes, for some strange reason, the log files are loaded in a strange way, at least in my case. Now my cumulus is installed in c: \, but I once again read the dayfile.txt with the internal editor and get on screen the same problem of the post #1.
It is possible that only happens to me?

Piero wrote:Now my cumulus is installed in c: \, but I once again read the dayfile.txt with the internal editor and get on screen the same problem of the post #1.
It is possible that only happens to me?

It appears so. I tried to reproduce the problem using your settings, and could not. I could load dayfile.txt into the editor, and edit it, without any problems.

Ok, so it is. Maybe sooner or later I'll find out the reason .. However, without intervene on the log files, everything works very well. Thanks Steve for your punctual and professional assistance

I was stumbling around this morning peeking into things (curiosity killed the cat?) and came upon some really odd data when I looked at some of the data files. I was all set to report my data logs being all cattywompus when I did a little search... Thanks for the help!!!....this answered my questions before I even had a chance to ask it!!!...now that is support!!!!

Ed