Celestial Navigation Plugin Redux

[Gnomon]

[QUOTE=rgleason;1602536]Gnomon

Thank you for checking. They are using different calculation methods... Is there any chance you could make a Test sheet with the information to enter, as NAV has done? We will add it to the end of the documentation for others to use.

Thanks.
Rick[/QUOTE

Pls. see answer as PDF's.
From manual work, via mainframes and PC's all the abreviations changed.
I added an explanation. There is a differnce of about 20 NMi, by year-book-data?
PS
I was to use "Routing" to show differences and had a super total crash, I could start OCPN no longer, reinstalled all from the beginning.
Colors of COP and there text dont match.
Regards
Gnomon

[rgleason]

Gnomon

I was to use "Routing" to show differences and had a super total crash, I could start OCPN no longer, reinstalled all from the beginning.
Colors of COP and there text dont match.

I am very sorry to hear about this crash. Can you explain a little further I am not understanding what part of the program and what you were doing... It may be a bad bug and we want to trace it out. Thank you... sorry about this.

Also "Colors of COP and there text dont match", is this after the crash? I pic would help I think. Sean fixed the entry problem you said. I have not tried the plugin yet.

[Gnomon]

Rick,
to #1
I was making waypoints for DR-point, observed point of conventinal and of the new OCPN celstial calculation methodes and started to make a route to get a report on distances and bearings between these three points.OCPN crashed, error-report window was locked, PC showed no reaction. I switched PC several times on and of, for OCPN this window was still locked, made virus-check, no finding, deinstalled OCPN, PC performed normal, reinstalled OCPN 1931 total from zero. Before checking for virus i ditnot dare to send a report. Now I backup the *.ini file.
I have:
Prozessor Intel(R) Core(TM) i7-3630QM CPU @ 2.40GHz, 2401 MHz, 4 Kern(e), 8 logische(r) Prozessor(en) with sufficent memory. CPU load is max. ca. 15 % on one core.
See via taskmanager. Resourcen monitor is out of order, it showed earlier a jam in handling the stack to the memories (I hope you understand). Charts are handled via a 32 GB SDHC-UHS-I card.
Sorry, I am not fast enough, other issues were mentioned in the forum already.
Greetings
Wolfgang

[NAV]

Originally Posted by Gnomon

[Pls. see answer as PDF's.
From manual work, via mainframes and PC's all the abreviations changed.
I added an explanation. There is a differnce of about 20 NMi, by year-book-data?

Something is wrong. First some questions:
1. What is: Std = + 5 25 ?

2. I assume ZZ means Zulu time (=GMT). Correct?

3. I assume Chr time = GMT time. Correct? Or is Std a correction to be applied to Chr time?

4. If Og = DR position : why is there no Og shown in your pdf, but only Ob (which is 'beobachter ort' = observed position, isn't it?)

5. For all 4 stars 'h' (altitude) is mentioned. Is this the altitude read from the sextant?

[Gnomon]

Rick,
to # 2, colors COP
While editing (2nd time) the four sights, i dared to select other colors, that worked, but in the editor window the former color was still written.
The attached picture shows original colors with correct spec.
I didnot copy a screen with wrong colorspecification.
PS
I still know some problems concerning +-180° LON.
Regards
Wolfgang

[Gnomon]

Originally Posted by NAV

Something is wrong. First some questions:
1. What is: Std = + 5 25 ?
Stand 8des Chronometers) = correction of time
2. I assume ZZ means Zulu time (=GMT). Correct?
Yes
3. I assume Chr time = GMT time. Correct? Or is Std a correction to be applied to Chr time?
Chr = time of chronometer without correction.

4. If Og = DR position : why is there no Og shown in your pdf, but only Ob (which is 'beobachter ort' = observed position, isn't it?)
Og = gegisster Ort was changed to Ob, sorry I was not concentrated.
5. For all 4 stars 'h' (altitude) is mentioned. Is this the altitude read from the sextant?
Yes, Ib = 0

Ps
I will try to scan part of the books.
Regards
Gnomon

[NAV]

Originally Posted by Gnomon

[There is a differnce of about 20 NMi, by year-book-data?

Entering your data in another program (not the plugin) I obtained the following Most Probable Position (almost the same as yours from Fulst/Medau):
Lat 51 10.1 N
Lon 001 39.4 E

Using the plugin I also found almost the same as you did:
Lat 51 24.2 N
Lon 002 13.8 E

I noticed that you didn't mention temperature and air pressure. I used 10 degrees C and 1010 hPa. In the plugin the LOP's were not shifted.

[Gnomon]

NAV,
You are very fast.
Scan of the book is attached.

[NAV]

Originally Posted by Gnomon

Scan of the book is attached.

1. Just to be sure: the year is 1957, is this correct (it's not mentioned in the scan of die Aufgabe)?

2. For Polaris (in the plugin) you entered the wrong eye height: 8 m instead of 9 m.

[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.

[Gnomon]

Originally Posted by NAV

1. Just to be sure: the year is 1957, is this correct (it's not mentioned in the scan of die Aufgabe)?

2. For Polaris (in the plugin) you entered the wrong eye height: 8 m instead of 9 m.

to 1.
In the sixties the book Aufgabe was sold together with the Yearbook 1957, including a selection of tidal data. The set was used in nautical highschools and in courses for hobby-sailors. The leaflet with solutions was kept rather secret and was difficult to get.
to 2.
The influence of 1m difference in eye hight is rather small, I noticed it to late.

to other post:
The input of date is done in a calender-form. So it should be correct. But I do not know the programm.

[rgleason]

NAV and Gnomon, thank you for all your testing, observations and discussion, they are very helpful to further development of a celestial navigation tool we can all use.

When you determine there is an issue or bug, please feel free to add or augment the entries in the Tracker. (YOu can register and login)
This is the Celestial Navigation List:
OpenCPN::Tracker pi - Celestial Navigation: Tasklist

Has this one been fixed?

1440 Bug Report All Medium Fix reversing order Sight entryCan it be closed?

[Gnomon]

NAV and Rick

In the 60ties navigators evaluated LOP's and discardet poor ones. 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.
To check the inputs I took the attached print of the (celestial)xml file.
The colors are infuenced by transparency and the background chart. (Adjustmend of transparency is not yet finished ?)


1440 Bug Report All Medium Fix reversing order Sight entryCan it be closed?
I had one reversing, later it was ok. It is not yet clear.
Best regards
Wolfgang

[rgleason]

Bug: The color name does not change in the menu when the color is changed under properties. This is a small bug that does not affect operation. For the time being just don't change colors.

I will enter this into Tracker to show how it is done. Entered.
FS#1447 : Change color, color name does not change in menu.

Also I am going to close Tracker Item #1440 Fix Reversing order sight entry.

[Gnomon]

Found Yearbook 1989 and exercises.
Selected an easy one with only two stars.
OCPN snapped location by 180 deg wrong. As told by instruction I added DR and got a result
as shown in the pdf. Pictures are includet.