View Single Post
Old 12-24-10, 03:47 PM   #5597
Sammi79
XO
 
Join Date: Jan 2010
Location: Penzance
Posts: 428
Downloads: 272
Uploads: 0
Default

Quote:
Originally Posted by TheDarkWraith View Post
Revamped the user options regarding real navigation:

######################################### Real Navigation ############################################
# the error (expressed as decimal) for the Navigator's calculation of current position (fix) using celestial navigation (used in real navigation only). This is the max error in meters. It will be used as the -min value and max value of a random function
# below is an float value only! (in meters)
NavCelestialMaxCalcFixError = 5000.0

# the minimum time it takes the Navigator to calculate the current position (fix)
# below is in seconds
NavCelestialCalcFixMinTime = 900.0

# the maximum time it takes the Navigator to calculate the current position (fix)
# below is in seconds
NavCelestialCalcFixMaxTime = 2700.0

# does navigator show position on the maps after he calculates current position (plots a new navigation fix)?
# change below to either True or False
NavShowPositionOnMapsAfterCalc = True

# if NavShowPositionOnMapsAfterCalc enabled, how long does the navigator show the calculated position on the map?
# below in seconds
NavShowPositionOnMapsAfterCalcTime = 20.0

# the error (expressed as decimal) for the Navigator's calculation of current position (fix) using dead-reckoning (used in real navigation only). This is the max error in meters. It will be used as the -min value and max value of a random function
# below is an float value only! (in meters)
NavDeadReckoningMaxCalcFixError = 1000.0

# minimum time it takes Navigator to plot position based on dead-reckoning
# below is a float value only! (in seconds)
NavDeadReckoningMinCalcTime = 15.0

# maximum time it takes Navigator to plot position based on dead-reckoning
# below is a float value only! (in seconds)
NavDeadReckoningMaxCalcTime = 60.0

How do those look
Lookin' good mate one thing though, re yellow highlight above, how is the max error scaled, 0% at 0hr(since last fix), 50% at 12hrs etc? If it was scaled with distance travelled instead I.e. 0% @ 0km, 50% @ 50km etc it would make more sense. If you don't move then your next dead reckoning error should be 0. Of course I realise this involves more math to find the distance between fixes (or more correctly between real locations at time of fixes) and may be more trouble than it is worth. Also, can the scale exend the maximum error? - 500% @ 500km
Sammi79 is offline   Reply With Quote