NavList:
A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding
Re: Why Not To Teach Running Fixes
From: Ken Gebhart
Date: 2009 Dec 16, 20:43 -0600
--
NavList message boards: www.fer3.com/arc
Or post by email to: NavList@fer3.com
To , email NavList+@fer3.com
From: Ken Gebhart
Date: 2009 Dec 16, 20:43 -0600
John,
I am finding it difficult to get interested in this discussion because it apparently has no practical value. If you can set up a situation where your thinking gives one RFix, and classical procedure gives a different RFix, then THAT'S something we can chew on.
Ken Gebhart
On Dec 15, 2009, at 10:51 PM, John Karl wrote:
No Frank, It's given (i.e., proposed) that the two vessels start out at P1. But the two tracks, P2 and P4, and RFIX all have errors (uncertainties). Perhaps introducing two vessels makes the discussion too confusing. I'm a bit surprised that no one can agree (or can see) that the standard running fix uses only the perpendicular component of the advance of LOP1, while completely ignoring the component of the estimated track parallel to LOP1. This is easily seen in the figure below, it is central to the construction of the standard running fix, and it depends on absolutely nothing else. The only time that this would make sense is if the navigator had absolutely no idea where she was along LOP1, or that her uncertainty along LOP1 is very large. Usually in practice P1 is an estimated position (call it DR, EP, whatever) whose uncertainty has been reduced to a line by acquiring LOP1, but still retains the uncertainly along LOP1 that it had before acquiring LOP1. This normally is of the order of DR uncertainties. The acquisition of LOP2 reduces this along-LOP1 uncertainty by an amount that depends on the orientation of LOP1 and LOP2. I discuss this in post #11174 and the two figures there.JK<Componets.jpg>--
NavList message boards: www.fer3.com/arc
Or post by email to: NavList@fer3.com
To , email NavList+@fer3.com
NavList message boards: www.fer3.com/arc
Or post by email to: NavList@fer3.com
To , email NavList+@fer3.com