Minor bugs?

[Ned]

A couple of niggly little issues I've come across...

I've set my longitude to the nearest minute (42' 00"), but after an indeterminate period Cumulus resets it to 41'60". Yeah, amounts to the same thing I guess - I've given up on correcting it now.

Setting the graphs to display a 48 hour period doesn't work for me - I can only get 12 or 24 hour graphs to work. Is it necessary to restart Cumulus to achieve this?

Cheers

[captzero]

Setting the graphs to display a 48 hour period doesn't work for me

Hi Ned,

To change the graphs display period....

Shut down cumulus.
Open the cumulus.ini file
Look for
[Graphs]
GraphHours=168
Change the value to the amount of hours you want displayed (mine is set to 1 week - 168 hours)
Save the cumulus.ini file and restart Cumulus.

Opening the Display option in the Cumulus console will automatically reset the value back to 12 or 24 hours.

Cheers

[Ned]

Thanks Dan, good info. But I'd still like to be able to change it from 12-24-48 hours on the fly, as my mood dictates

[steve]

I've set my longitude to the nearest minute (42' 00"), but after an indeterminate period Cumulus resets it to 41'60". Yeah, amounts to the same thing I guess - I've given up on correcting it now.

It's a 'feature' of the Delphi 'trunc' function (gives the integer part of a floating point number).

trunc (42.1) = 42
trunc (42.0) = 41

It happens because what looks like 42.0 is actually held internally as 41.99999 or similar. I'll try to find a work around.

Setting the graphs to display a 48 hour period doesn't work for me - I can only get 12 or 24 hour graphs to work. Is it necessary to restart Cumulus to achieve this?

It deliberately doesn't redraw the graphs as it would have to use the data from the logs, so the 1-minute resolution would be lost (unless you were using 1-minute logging). So you can either wait until it's built up 48 hours worth of data, or force it to redraw by restarting. I'll amend the help to make this clear; it needs updating to mention the 48-hour option anyway.

[Ned]

Thanks Steve.
Sorry to hear of you current disillusioned thoughts towards Cumulus - I'm sure the great majority of users feel quite the opposite so please take heart.

[gemini06720]

Steve, how about using decimal numbers (only) for both the latitude and longitude:

- rather than using something like: 48° 47' 48"
- how about using something like this: 48.79674000

This way you will not need to truncate nor round up the values - and those decimal-only values can easily be converted to their 'degrees/minutes/seconds' equivalent.

The decimal value can easily be obtained by navigating Google Earth...

[steve]

Steve, how about using decimal numbers (only) for both the latitude and longitude:

- rather than using something like: 48° 47' 48"
- how about using something like this: 48.79674000

This way you will not need to truncate nor round up the values - and those decimal-only values can easily be converted to their 'degrees/minutes/seconds' equivalent.

That's is how I store them internally; I hit the 'bug' when I convert them for display in DMS or when required by APRS or similar.

I had a look for some other Delphi conversion routines for DMS on the web, and they have the same problem, and some of the web sites with conversion pages also have the same problem (e.g. put 174.7 into them, and they give 174/41/60). I just need to write my own routines instead of relying on dodgy floating point arithmetic...

By the way, Ned, please don't think that this thread is contributing to my demeanour; on the contrary, it's cheered me up - a real bug reported in Cumulus!

[gemini06720]

Steve, look at the source code of this page: Federal Communications Commission: Degrees, Minutes, Seconds and Decimal Degrees Latitude/Longitude Conversions... You might be able to adapt the script into Delphi...

[steve]

Steve, look at the source code of this page: Federal Communications Commission: Degrees, Minutes, Seconds and Decimal Degrees Latitude/Longitude Conversions... You might be able to adapt the script into Delphi...

Hmmm...

dms.png

I've written my own routines, which seem to work in all cases.