Welcome to the NavList Message Boards.

NavList:

A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding

Compose Your Message

Message:αβγ
Message:abc
Add Images & Files
    Name or NavList Code:
    Email:
       
    Reply
    Re: Lat/Lon by "Noon Sun" & The Noon Fix PROVE IT
    From: Brad Morris
    Date: 2009 Apr 29, 08:57 -0400

    Hi Jim

     

    I am a bit disappointed that you would use regression analysis.  Typically this is a least squares fit, but I am uncertain as to your exact methodology.

     

    Perhaps I misunderstood.  I thought your method was a mark-1 eyeball method.  

     

    Dave Walden has shown that a least squares curve fit provides a reasonable determination of latitude and longitude.  

     

    If regression analysis is required for each line on either side of LAN, then there is no inherent advantage over a curve fit. 

     

    Please Jim, just try another case.  This test we have devised is tough, agreed.  That was the intent.  Imagine the poor navigator who has lost his electronics

    and now wants to obtain a noon fix.  Will he sit down to manually perform a least squares fit (linear or curve)?  I think not!

     

    Best Regards

    Brad

     

     

    From: NavList@fer3.com [mailto:NavList@fer3.com] On Behalf Of James N Wilson
    Sent: Tuesday, April 28, 2009 8:33 PM
    To: NavList@fer3.com
    Subject: [NavList 8092] Re: Lat/Lon by "Noon Sun" & The Noon Fix PROVE IT

     

    George:

     

    I'll attach my results from your first data set. To do more, I would have to automate it, since I'm lazy. Rather than prolong this event, I fudged and used regression analysis to fit lines through your data. The scatter was beyond what my eyeballs could handle.

     

    The results are:  Lat, 56°12.2'N, Lo, 9°53.6'W.

     

    As I examine the plot, I realize that I have committed the sin of extrapolation,

    i. e., the intersection of the lines is outside of the data range. In this case, I should have used data over a longer period. That should have moved the time of LAN a bit earlier. If I use the plot from my Navigation paper, the time difference between maximum altitude and LAN is 4m50s. That moves LAN earlier by 15s, consistent with the above.

     

    I enjoyed the learning, and I got quite a bit of that.

     

    Jim Wilson




    ____________________________________________________________
    Shop now at www.ftd.com/16714



    "Confidentiality and Privilege Notice
    The information transmitted by this electronic mail (and any attachments) is being sent by or on behalf of Tactronics; it is intended for the exclusive use of the addressee named above and may constitute information that is privileged or confidential or otherwise legally exempt from disclosure. If you are not the addressee or an employee or agent responsible for delivering this message to same, you are not authorized to retain, read, copy or disseminate this electronic mail (or any attachments) or any part thereof. If you have received this electronic mail (and any attachments) in error, please call us immediately and send written confirmation that same has been deleted from your system. Thank you."

    --~--~---------~--~----~------------~-------~--~----~
    Navigation List archive: www.fer3.com/arc
    To post, email NavList@fer3.com
    To , email NavList-@fer3.com
    -~----------~----~----~----~------~----~------~--~---

       
    Reply
    Browse Files

    Drop Files

    NavList

    What is NavList?

    Get a NavList ID Code

    Name:
    (please, no nicknames or handles)
    Email:
    Do you want to receive all group messages by email?
    Yes No

    A NavList ID Code guarantees your identity in NavList posts and allows faster posting of messages.

    Retrieve a NavList ID Code

    Enter the email address associated with your NavList messages. Your NavList code will be emailed to you immediately.
    Email:

    Email Settings

    NavList ID Code:

    Custom Index

    Subject:
    Author:
    Start date: (yyyymm dd)
    End date: (yyyymm dd)

    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site