[ gpsdrive ] No developer question, but a question about an older version of gpsdrive

[Thomas Schönhütl]

Hi Sascha, hi all,

Sascha Silbe wrote:
> On Sun, Nov 04, 2007 at 01:05:26AM +0100, Thomas Schönhütl wrote:
>
> #define ROUTEREACH 
> (((1/600)*groundspeed*groundspeed+(1/20)*groundspeed+(25/3))*groundspeed/(3600*milesconv)) 
>
>
> #define ROUTEREACH 
> (((1/42000)*groundspeed*groundspeed*groundspeed-(1/280)*groundspeed*groundspeed+(44/105)*groundspeed)*groundspeed/(3600*milesconv)) 
>
>
>> - I doubled the ROUTEREACH and recompiled gpsdrive
>> - then I did the same run and now the result was nearly PERFECT!!!
> In the SVN version, current.groundspeed is a floating-point number. 
> Perhaps it's an integer in the older version? In that case the cubic 
> part could overflow, giving you nonsense as result. You could try 
> writing "(double)" (including the parentheses, but not the quotation 
> marks) before each "groundspeed".
> You could also add a printf() call to output groundspeed and 
> ROUTEREACH, so we could should whether it's in the calculation or 
> somewhere else.
>
> CU Sascha

the second definition

#define ROUTEREACH 
(((1/42000)*groundspeed*groundspeed*groundspeed-(1/280)*groundspeed*groundspeed+(44/105)*groundspeed)*groundspeed/(3600*milesconv)) 



compiles without errors, but at the moment the first waypoint of the 
given route is reached, there is NO speechoutput and the cursor and the 
little cross, which normally moves to the next waypoint, they both stay 
at the first waypoint. No next waypoint, no speechoutput.

I tried it in the current version of GpsDrive and my older version (both 
variants, with and without (double)). Only the first waypoint, no 
speechoutput, no second waypoint.

Sascha, please could you create another definition with these facts:

30 km/h --> 15*groundspeed/3600
100 km/h --> 45*groundspeed/3600

I want to test this variant with the weak Libretto. I think sometimes if 
the map changes, the next waypoint is anounced and then the speechoutput 
shall be given, there are up to 10 seconds delay to reality.

Thank you for your efforts,

Thomas.