Wind Speed/Gust Rounding CWOP

[mcrossley]

I'm not sure what you mean, the current gust is already in both files.

[davepaterson]

Is the entry "wgust":"6.93" the one I should be using? as yes it shows the gust but it seam to be more of a recent than actual.

[hemmits]

Right, I've had a look at this and I'm not sure the Round Wind Speeds is working as intended.

What it is actually doing is... not a lot!
It sets the default number of decimal places for output to zero, so CMX will output rounded values to logs and web tags unless you override the number of decimals in the advanced settings.
It also rounds the mph values sent to WU, WOW, and PWS. But not APRS/CWOP.
And the same rounding for the m/s values sent to Windy.

(which begs another question why did your WU show a max gust of 8.5, it should have been rounded)

The actual values are still decimal values.

What I thought it would do would be to round all your wind speeds to integer values, which would then be used everywhere (except some internal functions which use the raw uncalibrated values).
I would expect the mph values sent to third parties to represent an accurate decimal conversion of your rounded value. So, if you use mph natively, then the rounded value will be sent with zeros as decimals, but if you use km/h, knots etc. then a decimal mph value would be sent so when you convert back to km/h (say) on the third-party web site you should get the integer value back again. The same applies to sending m/s values to Windy.

I had thought I could slip this into the next release, which is almost ready to go, but this complexity means I will not do that until we thrash out what we want CMX to do.

Thanks again for digging into this!

[davepaterson]

Is there a command that can be added to realtimegauges.txt that can show the latest gust?.
"wgust":"<#wgust>", shows a recent peak gust which will go up if the next gust is higher but won't show a lower value until the peak times out. I have tried out these commands : "wglatest":"<#wglatest>",
"wgspeed":"<#wgspeed>", and "wgustnow":"<#wgustnow>", but no value is returned in any of them.

[mcrossley]

No need to guess, the tags are all listed in the wiki - https://www.cumuluswiki.org/a/Full_list_of_Webtags

<#wlatest> is what you want.

[davepaterson]

Thanks Mike, I am using <#wlatest> for the wind and all is OK with it. It's the gusts that I want to work the same as the wind. I looked at the webtags and selected <#RecentWindGust> but it is the same as <#wgust>.
It all showed up because of the lack of wind in the last few days when the gust still had a reading after the wind had gone to zero, both gust methods do go to zero but only after a time out period and don't show lower values of what had been displayed until the high peek times out

[mcrossley]

That's how gust values work. If you want a shorter period, you must change it in the settings. CMX does not support multiple gust intervals.
The standard intervals are normally 10 minutes and 2 minutes.

[mcrossley]

It is a good idea for a couple of new web tags though for average and gust values in a specified interval.

[davepaterson]

That would be good Mark, for my part it's only for my own Dashboard no web site and have added a command that if the wind goes to zero the gust also goes to zero also but would like to see lower than the last peak value

[davepaterson]

Mark it would be good to add a web tag <#wglatest> (or similar) for the gust value without any standard intervals as is <#wlatest> for the wind and will show actual gust values.