Celestial Navigation Plugin Redux

[Gnomon]

Sorry, attachement was lost.

[rgleason]

Gnomon and NAV, what do you think? Should this become an entry in Tracker?
Thanks.

[NAV]

Originally Posted by NAV

Remarks on plugin:
1. Once data are entered and accepted, it's still not possible to change this later, e.g. when input errors are made.
2. Dates entered as e.g. 1957-08-04 (august 4, 1957) is changed by plugin after restart to 1957-04-08 (april 8, 1957). Must be related to different standards in date notation in US and Europe, I think.

Although a few days ago I definitely experienced both above mentioned problems, today these are gone. Don't ask me why ...

[NAV]

Originally Posted by Gnomon

In the 60ties navigators evaluated LOP's and discardet poor ones.

Disregarding COP's is also possible in the plugin. Just switch the 'eye' on or off in the first column.

Originally Posted by Gnomon

I sketched the LOP's following the printed solutions and found the LOP of Polaris too far S. The difference is ca. 2 miles and not 20.

In the plugin I don't see the difference you mention between Polaris included or disregarded (or I don't understand what you mean).

Polaris included:
Lat 51 24.2 N
Lon 002 13.8 E

Polaris disregarded:
Lat 51 25.0 N
Lon 002 14.0 E

[NAV]

Originally Posted by rgleason

Gnomon and NAV, what do you think? Should this become an entry in Tracker?
Thanks.

The position differences found between the results of the plugin and those of other systems are very large. This should be a priority 1 to solve.

[Gnomon]

NAV and Rick,
1. Eye
I believe that the eye is only switching the COP but not influencing the calculation. This point may be closed in the tracker.
2. LOP Polaris
Sorry, I was to short. I made a rough sketch on paper. The triangel of the 3 LOPs without Polaris was pretty small. The LOP of Polaris would move the Position by less than 2 miles. This is not includet in my printouts, the sketch was made in a hurry and canaps I will not scanned.
3. Order of data
I am using a notebook with mousepad and paralell a bluetooth mouse. Sometimes the curser is jumping away. I am not shure why, perhaps I touch the pad without noticing it.
I should disable the pad.
4. Testing
Next tests will be
- Sun with Moon
- 2 Planets
- more than two bodies with (Versegelung), means timedelay between sights with ship sailing
5. Opinion
The 20miles difference is not caused by the gone years. I should search for comments on perbetual almanacs.

Sorry, in younger years my English was more fluent.
Wolfgang

[Gnomon]

Alarm off !!
Greetings from the navy of Kaiser Wilhelm,
ZZ is in 24 h format but
Chr (chronometer) has pointers and is in 12 h format.
Shift all to 0!
Test with sun low-limb and moon upper limb shows only small difference to solutions.
Its raining, but pls give me some time.
Excuse and thanks
Wolfgang

[NAV]

Originally Posted by NAV

Although a few days ago I definitely experienced both above mentioned problems, today these are gone. Don't ask me why ...

And the problem regarding the dates (switch of month and day) is back again. I started OpenCPN and after opening the plugin it showed april 8 as dates instead of august 4.

Deactivating, and then activitating and starting the plugin brings the dates back to the correct values.

[NAV]

Originally Posted by rgleason

Has this one been fixed?
1440 Bug Report All Medium Fix reversing order Sight entryCan it be closed?

This problem is showing again too. It seems to happen after applying a change to an earlier input.

[Gnomon]

Hereby sun and moon.
Text and screencopies in one pdf.
I closed OPCN unintendet. After reopening moon was lower limb (difference is not big)

[rgleason]

NAV
I thought I had entered this in tracker. Did you close it?

Remarks on plugin:
1. Once data are entered and accepted, it's still not possible to change this later, e.g. when input errors are made.
2. Dates entered as e.g. 1957-08-04 (august 4, 1957) is changed by plugin after restart to 1957-04-08 (april 8, 1957). Must be related to different standards in date notation in US and Europe, I think.

Although a few days ago I definitely experienced both above mentioned problems, today these are gone. Don't ask me why ...

Weird, can't find it...even closed ones. GNomon please feel free to add comments to Tracker Items, it will help us keep Issue items and particulars together.

[rgleason]

FS#1440 : Fix reversing order Sight entry



Reopened and your comment added.

[rgleason]

And the problem regarding the dates (switch of month and day) is back again. I started OpenCPN and after opening the plugin it showed april 8 as dates instead of august 4.

Deactivating, and then activitating and starting the plugin brings the dates back to the correct values.

I think this one needs to be entered into Tracker and explained with some examples.

[rgleason]

Alarm off !!
Greetings from the navy of Kaiser Wilhelm,
ZZ is in 24 h format but
Chr (chronometer) has pointers and is in 12 h format.
Shift all to 0!
Test with sun low-limb and moon upper limb shows only small difference to solutions.

Great. Thanks.

[rgleason]

Yes, The plugin does have an "Eye" feature which turns the COP off and initiates a recalculation of the "fix" (the red cross hairs). I stand corrected. And will change that tracker entry and close it.

See screen shots below. I added a spurious "Sun" fix, left that on and found the red cross "fix" offset to the right. Then successively turned off sights until there were only two sights. Each time the "fix" was recalculated.