CustomLogs as module

[Dador]

But I assume the axis worked

Yes, thank you

[AndyKF650]

Hi Hans

I am just trying out the new windrun webtags in customlogs. The recent charts is working and I expect the Daily chart will creak into fgear once some data is received.

My issue is the units showing on both the realtime panel and the chart axis both of which show distance in "km" rather than "miles" which I use. Is this something that I can change or does it require your special touch?

[HansR]

I am just trying out the new windrun webtags in customlogs. The recent charts is working and I expect the Daily chart will creak into fgear once some data is received.

My issue is the units showing on both the realtime panel and the chart axis both of which show distance in "km" rather than "miles" which I use. Is this something that I can change or does it require your special touch?

Hi Andy,

Your YADR report on the Windrun also has km as distance.
At other site which use, Mph for the windspeed, it does show mi, so... . I'll look into this.

[HansR]

Aha... bug. Will be fixed next release (not sure when but asap)

[AndyKF650]

Hi Hans

Hummm When I look at CMX the windrun is shown in miles but as you say on CUtils the only distance unit is km, a European measurement!, and has been overlooked by me. When I look at the units used on for example the userreports it shows the distance unit as km per the following

2023-11-21 18:45:02.065 Information According to Inifile Info => Error: True, Warning: True, Info: True, Verbose: False,
2023-11-21 18:45:02.078 CumulusUtils Initial: Shutting down the default listener
2023-11-21 18:45:02.089 CUstrings[xx].ini : CUstringsEN.ini looked for.
2023-11-21 18:45:02.103 CumulusUtils version: 6.21.5
2023-11-21 18:45:02.104 CuSupport constructor : Unit Wind (m/s, mph, km/h, kts): mph
2023-11-21 18:45:02.104 CuSupport constructor : Unit Pressure (mb,hPa,inHg): hPa
2023-11-21 18:45:02.104 CuSupport constructor : Unit Rain (mm,in): mm
2023-11-21 18:45:02.105 CuSupport constructor : Unit T (C,F): °C
2023-11-21 18:45:02.105 CuSupport constructor : Unit Distance (m, mi, km, kn): km
2023-11-21 18:45:02.106 CuSupport constructor : Unit Height (m, ft): ft
2023-11-21 18:45:02.123 InetSupport: Constructor start
2023-11-21 18:45:02.145 CumulusUtils : ----------------------------
2023-11-21 18:45:02.146 CumulusUtils : Entering Main
2023-11-21 18:45:02.149 HelpTexts Contructor: start
2023-11-21 18:45:02.201 Information HelpTexts Contructor: stop
2023-11-21 18:45:02.202 Checking Mono Version on Linux/Unix
2023-11-21 18:45:02.206 Information StartProcess mono -V
2023-11-21 18:45:02.231 Information StartProcess mono: output=Mono JIT compiler version 6.12.0.200 (tarball Tue Jul 11 21:54:54 UTC 2023)
2023-11-21 18:45:02.232 Information StartProcess mono: output=Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
2023-11-21 18:45:02.232 Information StartProcess mono: output= TLS: __thread
2023-11-21 18:45:02.232 Information StartProcess mono: output= SIGSEGV: normal
2023-11-21 18:45:02.232 Information StartProcess mono: output= Notifications: epoll
2023-11-21 18:45:02.232 Information StartProcess mono: output= Architecture: armel,vfp+hard
2023-11-21 18:45:02.232 Information StartProcess mono: output= Disabled: none
2023-11-21 18:45:02.232 Information StartProcess mono: output= Misc: softdebug
2023-11-21 18:45:02.232 Information StartProcess mono: output= Interpreter: yes
2023-11-21 18:45:02.232 Information StartProcess mono: output= LLVM: yes(610)
2023-11-21 18:45:02.232 Information StartProcess mono: output= Suspend: preemptive
2023-11-21 18:45:02.232 Information StartProcess mono: output= GC: sgen (concurrent by default)
2023-11-21 18:45:02.243 CheckMonoVersion: detected MONO major version: 6 (Mono JIT compiler version 6.12.0.200 (tarball Tue Jul 11 21:54:54 UTC 2023))
2023-11-21 18:45:02.303 CommandLineArgs : starting
2023-11-21 18:45:02.303 CommandLineArgs : handling arg: userreports

I noticed that CMX has my wind speed in "mph" as does the above extract which to my mine should imply the use of "mi" as a distance unit

[HansR]

Yes, the problem is technical in the sense that CMX - from where I take the units - does not know the unit for Distance in the units spec and in addition when the windspeed is m/s the distance must be in km. I recently made a change and overlooked this implication. But it's clear now.

[AndyKF650]

Hi Hans

I have just looked at this again and there is a webtag <#windrununits> which I suppose should be part of the solution.

[HansR]

Andy,
What I said above: it is a bug, You can't solve it.

[Dador]

Hans,

I started writing down the <#snowdepth> tag and drawing it.
Unfortunately, something is wrong with the calculation, because the drawing looks as if the values ​​were adding up.

https://pogodarybnik.pl/customcharts.htm -> layer "Opady" -> <#snowdepth>=pokrywa śnieżna.

[HansR]

Hans,

I started writing down the <#snowdepth> tag and drawing it.
Unfortunately, something is wrong with the calculation, because the drawing looks as if the values ​​were adding up.

https://pogodarybnik.pl/customcharts.htm -> layer "Opady" -> <#snowdepth>=pokrywa śnieżna.

Hi,

I see the chart as below. What is wrong with it? I believe the snow layer values come from the diary (enetered by you?). I don't think there is automated snow depth registration.

And in addition : CUtils does no calculation here. If you think the values are wrong (check the CustomLog file, could you post it here?). Cutils does definitely not add up these values.

Schermafbeelding 2023-11-27 224255.png

[Dador]

Below is a snippet of my customlogs.txt

Code: Select all

27-11-23;22:40;-0,2;88;-2,0;-0,9;-0,2;-0,2;-0,2;-3,4;-1,8;-1,0;-1,8;-2,2;-0,1;88;-1,8;-0,4;-0,3;91;-1,6;1,7;1,7;2,8;5,0;0;217;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,4;1
27-11-23;22:45;-0,3;88;-2,1;-1,0;-0,3;-0,3;-0,3;-3,6;-2,0;-1,0;-2,0;-2,8;-0,2;88;-1,9;-0,4;-0,3;91;-1,6;1,7;1,7;2,8;5,0;0;217;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,6;1
27-11-23;22:50;-0,3;88;-2,1;-1,0;-0,3;-0,3;-0,3;-3,7;-2,2;-1,0;-2,2;-2,8;-0,2;88;-1,9;-0,4;-0,3;91;-1,6;1,7;1,7;2,8;5,0;0;217;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,5;1
27-11-23;22:55;-0,4;89;-2,0;-1,0;-0,4;-0,4;-0,4;-3,8;-2,5;-1,0;-2,5;-3,3;-0,2;89;-1,8;-0,4;-0,3;92;-1,4;1,7;1,7;2,8;5,0;0;198;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,5;1
27-11-23;23:00;-0,4;89;-2,0;-1,0;-0,4;-0,4;-0,4;-3,8;-2,5;-1,0;-2,5;-3,3;-0,2;89;-1,8;-0,5;-0,4;92;-1,5;1,7;1,7;2,8;5,0;0;198;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,5;1
27-11-23;23:05;-0,5;89;-2,1;-1,1;-0,5;-0,5;-0,5;-3,9;-2,5;-1,0;-2,5;-3,3;-0,3;89;-1,9;-0,6;-0,4;92;-1,5;1,7;1,7;2,8;5,0;0;198;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,5;1
27-11-23;23:10;-0,5;90;-1,9;-1,0;-0,5;-0,5;-0,5;-4,0;-2,8;-1,0;-2,8;-3,3;-0,3;89;-1,9;-0,6;-0,5;92;-1,6;1,7;1,7;2,8;5,0;0;179;0,0;0,0;0,0;0,0;82,2;648,6;0,0;5,0;0;741,71;1699,7;1,5;1

The last value is <#snowdepth>. As you can see, it is constant, because I tend to check the lid once a day, in the morning.
For me, the column chart should be "1" in each time frame, but it looks like a sum or something else.

Unless I'm thinking wrongly.

EDIT:
Ok,
in fact, I'm misinterpreting the chart
Everything is OK on Cutils' side.

[HansR]

Below is a snippet of my customlogs.txt

[...]

I seriously have my doubt you posted the correct log: the chart has 8 variables and the log has many more. I suspect you posted the Extra Sensors Log (ExtraLog202311.txt)

EDIT:
Ok,
in fact, I'm misinterpreting the chart
Everything is OK on Cutils' side.

Ah... OK... skipping the rest

[Dador]

Hans,

in parallel with the custom interval logs file, I create a daily file similar to the original dayfile.txt. However, there are fields with dates that cutils ignores (very well!), but at the same time it does not create a drawing.

My question is.
Is it possible for cutils to still ignore prohibited tags but allow drawing of allowed ones?

Below is an example of what it looks like in practice. This means that allowed tags are intertwined with prohibited ones, but as a result, the charts are not generated at all.

Code: Select all

2024-01-23 10:45:19.071 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#wgustTM>
2024-01-23 10:45:19.071 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#bearingTM>
2024-01-23 10:45:19.071 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#TwgustTM>
2024-01-23 10:45:19.071 Warning Constructor CustomLogs: Not a valid Webtag TwgustTM used in Custom log dayfile_cvp
2024-01-23 10:45:19.072 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#tempTL>
2024-01-23 10:45:19.072 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#TtempTL>
2024-01-23 10:45:19.072 Warning Constructor CustomLogs: Not a valid Webtag TtempTL used in Custom log dayfile_cvp
2024-01-23 10:45:19.072 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#tempTH>
2024-01-23 10:45:19.072 Information Constructor CustomLogs: handling Custom log dayfile_cvp - Webtag <#TtempTH>
2024-01-23 10:45:19.072 Warning Constructor CustomLogs: Not a valid Webtag TtempTH used in Custom log dayfile_cvp

[HansR]

My question is.
Is it possible for cutils to still ignore prohibited tags but allow drawing of allowed ones?

Hi,

The list of custom logs only has the valid tags in it and is created during initialisation so invalid webtags are simply skipped. It should create the chart with only the plottable webtags as far as I can see.

1. Could you post CutilsCharts.def AFTER you run CUtils with command CustomLogs?
2. Could you post the complete logfile?
3. What is your setting of UserModificationCustomLogsCharts

[Dador]

Thanks for the quick response and, to some extent, tips.

I studied the log files and it turned out that I was using empty fields that Cutils does not recognize (it must be zero - "0").
Now I remember that there was already a discussion about this topic. I forgot about that
I will write it loud and clear.

THE DATA MUST CONTAIN VALUES AND CANNOT BE EMPTY FIELDS.

REMEMBER!!!