Cruisers Forum
 


Join CruisersForum Today

Reply
 
Thread Tools Rate Thread Display Modes
Old 01-02-2014, 07:27   #136
NAV
Registered User

Join Date: Sep 2010
Location: Netherlands
Posts: 424
Re: Celestial Navigation Plugin Redux

I now see that the refraction is calculated according to the Bennett formula, as stated in Meeus' Astronomical Algorithms, where the abbreviation Ho is used for the apparent altitude. Confusing indeed.
__________________

__________________
NAV is offline   Reply With Quote
Old 01-02-2014, 10:57   #137
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

I'm going to be trying to use this plugin so I do have an interest in getting it easy and understandable with respect to the way the books treat these measurements.

Quote:

1.
ObservedAltitude = Measurement - IndexCorrection - EyeHeightCorrection - RefractionCorrection - LimbCorrection
2. CorrectedAltitude = ObservedAltitude - ParallaxCorrection

... what is called CorrectedAltitude in the plugin, is called Observed Altitude by Bowditch and Admiralty

Plugin.............Bowditch...............Admiralt y..............Dutch
Measurement..sextant alt (Hs).......sextant alt (Hs).......instrumentshoogte (Hi)
-.......................-..............................-..............................gemeten hoogte (Hg) [=sextant alt corrected for index corr only]
-.......................apparent alt (Ha)....apparent alt (H).......'apparent alt' (Ha)
ObservedAlt.....-..............................-...............................-
CorrectedAlt.....observed alt (Ho)...observed alt (Ho).....ware hoogte (Hw)

NAV what would you like to see?
1. Change the Plugin name for "2. Corrected Altitude" to "2. Observed Altittude"? (Hs)
2. What does "
1. ObservedAltitude = Measurement - IndexCorrection ." become? Apparent Altitude? (Ho)?
3. Where does Eye height correction go then?

I hope changing this stuff around does not screw up the programming, because sean probably has routines and variables named a certain way...etc.

I think the entry and interface should be similar to the standard hanc calcs, but if there is any obvious shortcut or improvement to the process because of the computer tables, I would not be s slave to the format!
---Just who am I to be talking here! Don't program and am just learning.


__________________

__________________
rgleason is online now   Reply With Quote
Old 01-02-2014, 10:59   #138
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

Quote:
I now see that the refraction is calculated according to the Bennett formula, as stated in Meeus' Astronomical Algorithms, where the abbreviation Ho is used for the apparent altitude. Confusing indeed.
Sorry NAV you just lost me here. Can you explain a little what the problem is and what Bennett formulat is .

Maybe if you put out the process for calculating that Bowditch uses, and compared it to the entries in Cel_Nav, we could see what is needed, reduced to a few simple changes? Hopefully...
__________________
rgleason is online now   Reply With Quote
Old 01-02-2014, 11:17   #139
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

It would be great if the suggestions were a list of changes that could be added to Tracker, under the Celestial_Navagation_pi project. I understand you are going through the plugin step by step and explaining which is also great for all of us.
Thank you
__________________
rgleason is online now   Reply With Quote
Old 02-02-2014, 00:51   #140
NAV
Registered User

Join Date: Sep 2010
Location: Netherlands
Posts: 424
Re: Celestial Navigation Plugin Redux

Quote:
Originally Posted by rgleason View Post
Can you explain a little what the problem is and what Bennett formulat is .
No problem at all with this refraction formula from Bennett. However, the abbreviation Ho as used in this formula (in Astronomical Algorithms) for apparent altitude is confusing because the standard abbreviation for 'apparent altitude' is Ha (or H by The Admiralty). Ho is normally used for 'observed altitude'.

This formula is suitable for all altitudes between 0 and 90 degrees. The formulas used in Bowditch and by The Admiralty are suitable for altitudes between 15 and 90 degrees (that's why in nautical astro navigation you shouldn't use heavenly bodies with altitudes < 15 degrees.

In the plugin also a second formula for refraction is used. I haven't looked into that one already.
__________________
NAV is offline   Reply With Quote
Old 02-02-2014, 01:12   #141
NAV
Registered User

Join Date: Sep 2010
Location: Netherlands
Posts: 424
Re: Celestial Navigation Plugin Redux

Quote:
Originally Posted by rgleason View Post
NAV what would you like to see?
1. Change the Plugin name for "2. Corrected Altitude" to "2. Observed Altittude"? (Hs)
2. What does "
1. ObservedAltitude = Measurement - IndexCorrection ." become? Apparent Altitude? (Ho)?
3. Where does Eye height correction go then?

The standard is:
Apparent altitude Ha = sextant altitude corrected for index correction and dip
Observed altitude Ho =Apparent altitude corrected for refraction, parallax and semi-diameter

The plugin uses (as shown in the Calculations window):
ObservedAltitude = Measurement - IndexCorrection - EyeHeightCorrection - RefractionCorrection - LimbCorrection
CorrectedAltitude = ObservedAltitude - ParallaxCorrection

(Note: EyeHeigtcorrection = dip, Measurement = sextant altitude)

The possible problem I see (but perhaps I'm overlooking something and Sean can explain) is that the refraction calculation should be a function of the 'apparent altitude', in the plugin refraction seems to be a function of the sextant altitude in these lines of code: double Ha = m_Measurement - m_EyeHeightCorrection; and double x = tan(M_PI/180 * m_Measurement + 4.848e-2*(M_PI/180) / (tan(M_PI/180 * m_Measurement) + .028)); (to keep in mind: I'm not a programmer, too ...).

Secondly, generally I would stick to the naming conventions and calculation procedures as used in Bowditch.
__________________
NAV is offline   Reply With Quote
Old 12-02-2014, 08:25   #142
NAV
Registered User

Join Date: Sep 2010
Location: Netherlands
Posts: 424
Re: Celestial Navigation Plugin Redux

Sean updated some of the code. I'd like to continue testing. Can somebody compile a new Windows version for me?
__________________
NAV is offline   Reply With Quote
Old 12-02-2014, 15:02   #143
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

NAV
I can recompile later tonight or in the morning. Thanks for alerting me. Did not realize Sean was back with a computer.
__________________
rgleason is online now   Reply With Quote
Old 12-02-2014, 16:27   #144
Registered User
 
neworleansrich's Avatar

Join Date: Jan 2014
Posts: 47
Re: Celestial Navigation Plugin Redux

Maybe its just too much rum lately, but I could not get a working version of the OpenCPN Celestial Navigation Plugin installed. Could someone post an idiot proof set of instructions on where to download the most current version and how to get it installed. Thanks
__________________
neworleansrich is offline   Reply With Quote
Old 13-02-2014, 06:42   #145
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

NAV, the current git did not compile and Sean will be making some changes to fix internal file reference problems.

Neworleansrich
Look at Opencpn Beta File thingie, further up in this thread. There you can download the current working celestial nav. Remember that celestial nav requires a DATA directory. Read the Readme file about Celestial Nav in File thingie.
__________________
rgleason is online now   Reply With Quote
Old 13-02-2014, 17:02   #146
Registered User
 
boat_alexandra's Avatar

Join Date: Aug 2009
Location: North Carolina
Boat: bristol 27
Posts: 2,720
Re: Celestial Navigation Plugin Redux

gah, my email server is down
__________________
boat_alexandra is offline   Reply With Quote
Old 14-02-2014, 11:00   #147
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

Sean Depagnier's Plugins
__________________
rgleason is online now   Reply With Quote
Old 15-02-2014, 09:00   #148
NAV
Registered User

Join Date: Sep 2010
Location: Netherlands
Posts: 424
Re: Celestial Navigation Plugin Redux

Three more observations:

1. In the plugin, eye height (h) can only be entered in whole meters (m). For more accuracy and easier checking against example data in The Nautical Almanac and The Admiralty Manual of Navigation, I suggest to offer the possibility to enter eye height in meters with one decimal (m.m).

2. Dip in the plugin is calculated by the formula 1'.753*SQRT(h). Both the Admiralty Manual of Navigation and the Nautical Almanac use 1'.758*SQRT (h). I suggest to use this last formula.

3. The Nautical Almanac uses a standard atmosphere for the calculation of refraction (Temperature=10 degrees Celsius and Pressure=1010 hPa). I suggest to set the default values in the plugin accordingly.
__________________
NAV is offline   Reply With Quote
Old 15-02-2014, 09:10   #149
Registered User
 
rgleason's Avatar

Join Date: Mar 2012
Location: Boston, MA
Boat: 1981 Bristol 32 Sloop
Posts: 8,259
Re: Celestial Navigation Plugin Redux

Thanks very much NAV for your suggestions. Otherwise how are things looking to you?
__________________
rgleason is online now   Reply With Quote
Old 15-02-2014, 10:19   #150
NAV
Registered User

Join Date: Sep 2010
Location: Netherlands
Posts: 424
Re: Celestial Navigation Plugin Redux

Quote:
Originally Posted by rgleason View Post
Otherwise how are things looking to you?
Well, things look fine, I guess. But checking goes slow when example data cannot (yet?) be entered with same accuracy and when - partly - slightly different formulas are used. A difference of 1' in altitude is relatively large in astronomical positioning, so while checking I try to establish the cause of differences > 0.1' I see (that's 0.00167 degrees).

This brings me to a fourth suggestion:
Although calculations are probably done to full precision, for the presentation of data 3, 4 or 5 decimal figures are used. I suggest to make that 4 decimal figures for all values in degrees. For presentation of minutes (angular) 1 decimal should be sufficient.

Question for Sean: will the POT-file be updated too?
__________________

__________________
NAV is offline   Reply With Quote
Reply

Tags
celestial navigation, navigation

Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Logbook Konni for OpenCPN konni OpenCPN 823 07-06-2017 09:32
Google Earth Plugin r.fairman OpenCPN 417 15-02-2015 11:15
GRIB Weather Mark Ward OpenCPN 26 12-02-2012 21:33
Route Properties, Missing Functions James Baines OpenCPN 13 13-07-2011 04:31


Our Communities

Our communities encompass many different hobbies and interests, but each one is built on friendly, intelligent membership.

» More about our Communities

Automotive Communities

Our Automotive communities encompass many different makes and models. From U.S. domestics to European Saloons.

» More about our Automotive Communities

Marine Communities

Our Marine websites focus on Cruising and Sailing Vessels, including forums and the largest cruising Wiki project on the web today.

» More about our Marine Communities


Copyright 2002- Social Knowledge, LLC All Rights Reserved.

All times are GMT -7. The time now is 03:46.


Google+
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Social Knowledge Networks
Powered by vBulletin® Version 3.8.8 Beta 1
Copyright ©2000 - 2017, vBulletin Solutions, Inc.

ShowCase vBulletin Plugins by Drive Thru Online, Inc.