NavList:

   

Reply

My thanks to Dr. Kolbe for copying to NAV-L his note to me and my
reply.

The best explanation I can come up with is a horizon that was about
1.3 to 1.4 degrees too low.  That seems a little odd to me; it's a
rather large error.  My errors usually turn out to be on the order of
a few minutes in altitude and a few seconds in timing.  Trying to
adjust the timing in some reasonable interval (e.g., ten or thirty
minutes) doesn't work any better than trying to make another star fit
the sights listed in my work sheets.  So, barring divine intervention,
whose intent, by definition, is unknowable [s], that leaves a fumbled
horizon as the most likely explantion.  As I said, I'm not entirely
comfortable with that but I can't think of a better explanation.
Nonetheless I think this discussion has been instructive for the list
readership and helpful for me.

Rick
S/V One With The Wind, Baba 35

P.S.  In wrapping up this topic, I should also credit Starpath's
latest addition to their StarPilot program: a sight analyzer function.
It takes a series of sights and draws a line representing a trend
analysis of those sights.  It makes outlaying data easy to spot and
confirms the overall quality of a shot series.  I applied it to the
three rounds of sights taken on the morning of the 22nd and found some
minor discrepencies but, aforementioned gross errors aside, that was
it.  Check http://www.starpath.com for an interesting description of
this function and its use with StarPilot.

   

Reply