Open Corsair-63 opened 1 year ago
Exchanged laptop and computer for working with decimal "."
I've entered a full swing (test) with maximum deviation of -3.0 degress and what I get is the following deviation chart:
uhhhhhh, where is the error??
I've done a double check with my deviation spreadsheet and interpolating values to adhere to same values calculated by the plugin and I got some differences: deviation table created with plugin:
calculated by deviation spreadsheet with data entered (same as plugin with interpolation), there was one error in previous picture, but the results were the same:
calculation result with spreadsheet:
Another thing, about items coming and going in the dropdown menu of Method. sometimes it shows "bearing from route" but quickly disappeared and tries to show the new menu with more items, I say that because of the items in the translation files. when you click on it sometimes is difficult to leave it on Bearing and continuos try to exchange either blank either "bearing from route" but when you deploy it only available three options "Bearing, Sun Bearing & Sun Bearing with shadow line".
Reproduces error on calculation in plugin.
see attached file txt, remove that extension, and leave as xml. deviation_data.xml.txt
you cannot leave the compass course as 0 when done by bearing, it makes a strange calculation of coefficients.
if you set the compass course as true bearing it makes the correct calculation and agreed with spreadsheet for adjusting compass.
you can now check that these datas are the same as the spreadsheet.
Squeezing mi poor old brain, it makes all sense such behavior, because what you need to know is the deviation at that course, I mean with a true course e.g. of 045 you have a compass bearing of 234 and a true bearing of for example of 237, with this you get a deviation of x degrees but at the course of 45. and same for other with different bearings to distant objects. normal practice in adjusting fields that you swing the ship and sometimes you have limited landmarks.
I'm doing the test on board (windows 11 latest patch ARM64). decimal setup as "," used attached deviation data and not calculating the deviation. deviation_data.xml.txt on all step if click in update, shown deviation as "nan" and no trustable graph, when click OK, O crashes.
exchanged system to decimal "." and plugin works and displayed the correct deviation curve, still if edit one of the values after click ok it crashes.
Carmelo, we are going to have to wait and see if Dirk can fix this. Sometimes he is at sea. Thanks for the testing.
Hi all,
windows 11 Pro version 22621.2361 (x64) OCPN 5.8.4-0 Deviation 0.1.12.0
started testing first at home, later I'll test in my boat today either tomorrow. (Today I have entered in the sixties decade ;-) )
1 - starting well, now data is displayed as per regional settings in computer, so all data I could read and enter with decimal "," and no crash of O (only first time). 2 - regarding num. 1, when I type the decimal in the nun pad it does nothing, so I must enter the decimals with the "," in the normal keyboard. 3 - I still see a lot of expression not translated when all then are in Crowdin (Spanish) 4 - I've to double check something with Bearing when set the course to 000, because if you set bearing as adjustment and you take compass bearing and true bearing the deviation is taken from those inputs irrespective of the course, which is relevant when using "right-hand bearing" (Marcación). 5 - deviation is shown in input windows always as "nan" supposed to show the value calculated or having a button to click after the value inputs of "calculate" and show the calculated deviation.
6 - there is an input error, I cannot send a screenshot because O crashes, when click on add one deviation, the above screen appears in my case as "magnetic variation" "000.2" when entered data at the end it exchanges to "2,0" as per screenshot. Now I'm not able to do it again because O crashes. as far as I understand I cannot assure how is made the calculation with 0.2 or 2. I've been able to recover the screenshot of the problem via the Crash-report in O folder.
it happened when click on add another deviation and click on WinSnap to make a screenshot of the event, just click on "capture" a region of the screen and O crashed immediately. I've done a new entry without doing any screenshot with Winsnap x64 and there were no O crash.