SUBSIM Radio Room Forums - View Single Post

Sammi79 · 12-24-10, 04:43 PM

@ TDW

Right, bear with me I'm wishing I was more articulate...

Say the default max dead reckoning error (set in useroptions.py) = 1000.0 (meters float) as it is currently.

Scaling the error depends on distance travelled since last fix. So say 1km travelled = 0.01 (1%) of default error = 10 meters. 10km travelled = 0.10 (10%) of default error = 100 meters. Using this scale, at 100km travelled, error = 1000 meters (1.0 or 100% of default error)

can it then extend the error? I.e. 500km travelled = 1000.0 x 5.00 (500%) = 5000.0 meter.

This is how I think it should work, the default error does not need to change as the scale does the work. maybe instead of setting the default error in useroptions.py the scale (per km) would be a more usefull value - 0.01 per km to start with then maybe increased a little if after 100km, 1km error seems too small.

[Edit : Having reread your previous post regarding the variables :

(default max error float) = 1000.0 - unchangeable only used by game.
(scale per km %) = 0.01 - configurable in options.

As I look at it now there would be no true maximum error for dead reckoning, the further you travel, the bigger the possible error will be. Until that is you get a new celestial fix to start from.]

Is this making sense or am I just confusing the issue?

Regards,
Sam.

12-24-10, 04:43 PM	#5600
Sammi79 XO Join Date: Jan 2010 Location: Penzance Posts: 428 Downloads: 272 Uploads: 0	@ TDW Right, bear with me I'm wishing I was more articulate... Say the default max dead reckoning error (set in useroptions.py) = 1000.0 (meters float) as it is currently. Scaling the error depends on distance travelled since last fix. So say 1km travelled = 0.01 (1%) of default error = 10 meters. 10km travelled = 0.10 (10%) of default error = 100 meters. Using this scale, at 100km travelled, error = 1000 meters (1.0 or 100% of default error) can it then extend the error? I.e. 500km travelled = 1000.0 x 5.00 (500%) = 5000.0 meter. This is how I think it should work, the default error does not need to change as the scale does the work. maybe instead of setting the default error in useroptions.py the scale (per km) would be a more usefull value - 0.01 per km to start with then maybe increased a little if after 100km, 1km error seems too small. [Edit : Having reread your previous post regarding the variables : (default max error float) = 1000.0 - unchangeable only used by game. (scale per km %) = 0.01 - configurable in options. As I look at it now there would be no true maximum error for dead reckoning, the further you travel, the bigger the possible error will be. Until that is you get a new celestial fix to start from.] Is this making sense or am I just confusing the issue? Regards, Sam. Last edited by Sammi79; 12-24-10 at 05:03 PM.