Beta Test / Technical

[blubaju]

Originally Posted by phiggins

Dave,

Re:
Multi-core CPU question and crashes

...

I am running XP Home on an Acer computer that has an Intel Atom N270 processor that I believe is NOT a Dual core cpu.
...
Paul

"Silverthorne (N270 & N280) uses a single core, but has HyperThreading on board to allow it to appear to the host OS as two cores."

Never mind what you think that you have,
what does your XP think it has? ;-)

more serious:
are the crashes restricted to the mobile c2d or "c2d wannabe" processors?

[jonasaberg]

In the second post in this thread VikingSailor describe how to use drwtsn32 to create an info file for use in debugging craches.

How can we organise the sending of these in some way?

VikingSailor (Dave) ask for the dump file to be sent by email to him, but at the same time it makes sence that bdbcat(Dave) gets them.

Solutions?

/Jonas

[cagney]

Jonas

I think that was a mistake by "VikingSailor" who normally signs his posts "Paul". So... all crash reports should go to Dave/bdcat.

Thomas

[Viking Sailor]

Sorry All,

The post on how to use drwtsn32 was intended as a repost of Dave's (bdcat) post. Looking back I can see that I didn't make that as clear as I could have. Anyway, please send the dump files to Dave. BTW, no one ever sent me a dump file.

Paul

[idpnd]

NB Theres a bug report in a separate thread on here, don't miss it..

[sinbad7]

Dave..

Why does i take so long before an AIS target shows GREEN? The attached screendump from the arrival of the Oasis of the Seas in the Solent today shows only ONE green target of about 50 within the map borders. What are the actual conditions for a target to turn green? I have waited 20 min but still YELLOW?

[ChuckSK]

Setting the affinity to 1 cpu eliminated the crashes I was seeing.

Started with affinity set to 1: ran 6 hours.
Changed to affinity set to 2 cpus: crashed in 40 minutes.
Restarted with affinity set to 1: ran 12 hours.

Running vista home premium on a dual core cpu.



Chuck

[GPS-Marco]

Hello,

I'm experiencing some problem in using BSB maps that cross the 180° meridian. The problem is that even if the chart border is shown fine, if you click to center the chart, it will not become available.

Making some tests I saw that sometimes there are some small parts of the chart where OCPN give the same chart as available and then is able to show the chart.

I've 4 pictures. First is the border of NZ14605 (calibrated by myself). As you can see the chart, even if the screen is centered on the chart, is not considered available. If I click on the lower-left corner, the chart become available and this is shown in the second picture. As you can see, the border is distorted! So there must be a mismatch in the function that calculates which chart is available at a given lat/long or something like that.

I made a second test with a chart crossing 180° longitude downloaded from NOAA (chart 16012); you can download it by yourself:

User's Agreement

Same problem: the borders are shown fine but the map is not available. There is only a litte area in the lower part were the map is available and if you click there the map appears (but if you leave that area the map become unavailable again)

I guess this is an OCPN (v134) bug in handling chart borders of BSB maps crossing 180° longitude.

Ciao, Marco.

[cagney]

Marco

16012: Most likely a bad geo referencing from NOAA:s side. Look at the orange colored bar, OpenCPN:s way of complaining. I have the same result as you when testing.
NZ14605: Check your own template file. I have done that chart myself, no problem. I have also done more charts in this area across the 180:th meridian and am fairly confident in saying that OpenCPN now handles this OK.

Thomas

[GPS-Marco]

Originally Posted by cagney

Marco

16012: Most likely a bad geo referencing from NOAA:s side. Look at the orange colored bar, OpenCPN:s way of complaining. I have the same result as you when testing.
NZ14605: Check your own template file. I have done that chart myself, no problem. I have also done more charts in this area across the 180:th meridian and am fairly confident in saying that OpenCPN now handles this OK.

Thomas

Hi. Can you send me the header of your NZ14605? This is mine.

! Created by mc2bsbh-0.00.01 - Use at your own risk!
! BSBHDR::CED/SE=2007,RE=143,ED=2008
VER/2.0
BSB/NA=New Zeland to Fiji and Samoa Islands
    NU=NZ14605 (INT605),RA=8458,12783,DU=331.927
KNP/SC=3500000,GD=WGS84,PR=MERCATOR
    PP=-22.5,PI=UNKNOWN,SP=UNKNOWN,SK=0.0
    UN=METERS,SD=LAT,DX=267.83,DY=267.83
REF/1,1708,1520,-10.0,175.0
REF/2,3443,1519,-10.0,180.0
REF/3,1707,3286,-15.0,175.0
REF/4,3444,3287,-15.0,180.0
REF/5,1707,5097,-20.0,175.0
REF/6,1707,6966,-25.0,175.0
REF/7,1708,8914,-30.0,175.0
REF/8,1707,10964,-35.0,175.0
REF/9,3445,10964,-35.0,180.0
REF/10,3444,8914,-30.0,180.0
REF/11,3443,6965,-25.0,180.0
REF/12,3443,5096,-20.0,180.0
REF/13,5180,1519,-10.0,-175.0
REF/14,5180,3287,-15.0,-175.0
REF/15,5181,5097,-20.0,-175.0
REF/16,5180,6965,-25.0,-175.0
REF/17,5180,8914,-30.0,-175.0
REF/18,5180,10965,-35.0,-175.0
REF/19,6916,8913,-30.0,-170.0
REF/20,6917,6965,-25.0,-170.0
REF/21,6917,5096,-20.0,-170.0
REF/22,6917,3286,-15.0,-170.0
REF/23,6916,1519,-10.0,-170.0
REF/24,517,10964,-35.0,171.571666666667
REF/25,1707,12221,-37.923333333333,175.0
REF/26,3443,12220,-37.923333333333,180.0
REF/27,7957,646,-7.5,-167.0
PLY/1,-7.5,171.572
PLY/2,-35.75,171.572
PLY/3,-35.75,173.35
PLY/4,-37.92,173.35
PLY/5,-37.92,-171.0
PLY/6,-33.15,-171.0
PLY/7,-33.15,-167.0
PLY/8,-7.5,-167.0
DTM/0,0

It is anyway strange the fact that the red border changes when I select the corner of NZ chart. Maybe something in handling charts whith complex (not rectangular) border...

Ciao, Marco.

[cagney]

Marco, here you go:

!Copyright note valid for charts based on NZ chart images.
!"Sourced from Land Information New Zealand data. Crown Copyright Reserved."
VER/3.0
BSB/NA=NZ14605
NU=55,RA=8458,12783,DU=300
KNP/SC=3500000,GD=WGS84,PR=MERCATOR
PP=-22.500,PI=UNKNOWN,SP=UNKNOWN,SK=0.0
UN=METERS,SD=LAT,DX=000,DY=000
CED/SE=2009,RE=12,ED=10/10/2009
OST/1
REF/1,516,12220,-37.923333333333,171.571666666667
REF/2,516,647,-7.500000,171.571666666667
REF/3,7957,647,-7.500000,-167.00000
REF/4,7957,12220,-37.923333333333,-167.00000
REF/5,1708,647,-7.500000,175.00000
REF/6,3444,647,-7.500000,180.00000
REF/7,5179,647,-7.500000,-175.00000
REF/8,6916,647,-7.500000,-170.00000
REF/9,7957,1519,-10.00000,-167.00000
REF/10,6916,1519,-10.00000,-170.00000
REF/11,5179,1519,-10.00000,-175.00000
REF/12,3444,1519,-10.00000,180.00000
REF/13,1708,1519,-10.00000,175.00000
REF/14,516,1519,-10.00000,171.571666
REF/15,516,3286,-15.00000,171.571666
REF/16,1708,3286,-15.00000,175.00000
REF/17,3444,3286,-15.00000,180.00000
REF/18,5179,3286,-15.00000,-175.00000
REF/19,6916,3286,-15.00000,-170.00000
REF/20,7957,3286,-15.00000,-167.00000
REF/21,7957,5097,-20.00000,-167.00000
REF/22,6916,5097,-20.00000,-170.00000
REF/23,5179,5097,-20.00000,-175.00000
REF/24,3444,5097,-20.00000,180.00000
REF/24,1708,5097,-20.00000,175.00000
REF/26,516,5097,-20.00000,171.571666
REF/27,516,6966,-25.00000,171.571666
REF/28,1708,6966,-25.00000,175.00000
REF/29,3444,6966,-25.00000,180.00000
REF/30,5179,6966,-25.00000,-175.00000
REF/31,6916,6966,-25.00000,-170.00000
REF/32,7957,6966,-25.00000,-167.00000
REF/33,7957,8914,-30.00000,-167.00000
REF/34,6916,8914,-30.00000,-170.00000
REF/35,5179,8914,-30.00000,-175.00000
REF/36,3444,8914,-30.00000,180.00000
REF/37,1708,8914,-30.00000,175.00000
REF/38,516,8914,-30.00000,171.571666
REF/39,516,10964,-35.00000,171.571666
REF/40,1708,10964,-35.00000,175.00000
REF/41,3444,10964,-35.00000,180.00000
REF/42,5179,10964,-35.00000,-175.00000
REF/43,6916,10964,-35.00000,-170.00000
REF/44,7957,10964,-35.00000,-167.00000
REF/45,6916,12220,-37.923333333333,-170.00000
REF/46,5179,12220,-37.923333333333,-175.00000
REF/47,3444,12220,-37.923333333333,180.00000
REF/48,1708,12220,-37.923333333333,175.00000
PLY/1,-37.92333,171.571666
PLY/2,-7.500000,171.571666
PLY/3,-7.500000,-167.00000
PLY/4,-37.923333,-167.00000
IFM/7

This method with REF:s and PLY: works, and you need quite a few REF:s with a 1:3,500,000 scale chart. I don't use MapCal, all tweaked by hand....... with a little help from a test program I wrote.

Thomas

[GPS-Marco]

Thomas, I used your header: OK
Then I replaced into your header your PLYs(4 points) with my PLYs(8 points): Not OK.

I guess the problem is in handling non rectangular borders (on maps crossing 180 longitude).

Have a look.

Ciao, Marco.

P.S. about using MapCal, I had to make some manual corrections since it only allowed me to use East longitudes (175, 180, 185, 190) otherwise it complains of a coordinate swap. Than I changed 190 with -170 and so on by hand directly in the CHARTCAL.DIR... Ciao.

[dehem]

Hi,
New to openCPN, haven't take the time to read all posts. These bugs may have been reported before. Running version 1.3.4 under windows XP:

-crash (reproducable easily): execute openCPN, activate track icon, right click on my boat and delete track several time. After a couple delete accepted, openCPN crashes.

-happens sometimes: loosing wheel-zoom control. Will send detail if I understand exactly in what situations.

-crash (once): openCPN crashed when GPS (garmin) was shutdown. retried but did not recrash.

-map search algorithm bug or normal (?): took me sometime to understand why I could not get all map details of my CM93 library. Here's my understanding (maybe wrong) after visiting the logfile. My CM93 maps are divided into regions. Each region has a sub-directory (at least in my CM93 version). But each subdirectory also include large scale maps of other regions. I only get the detailed maps (small scale) for the first subdirectory visited by openCPN. for other regions, openCPN finds a large scale map in this first directory and will not look for more detailed maps (other levels letters) into other subdirectories (the ones specific to the other regions). Of course, I can change my chart directory definitions when I explore a different region to get the detailed map, but I would think this should be managed by openCPN.

Other than that, looks like an excellent software so far,
Thank you

[cagney]

Marco

I agree with your conclusion. When I straightened out the PLY-line at the bottom of your chart, changing nothing else in your calibration, just drawing it between the corners of the chart, using your derived values, the chart was alright.
This is a bug in the program, low priority, easy to avoid.
Dave another mole to whack in the 0/180 - marathon, if/when you feel like it.

Thomas

[Ptizef]

Dehem wrote :
"-happens sometimes: loosing wheel-zoom control. Will send detail if I understand exactly in what situations."
For me under vista , it happens each time I click on the opencpn tab or on the desk button to put the desk at the forefront
after that , wheel-zooming and hot keys are deactivated

Jean Pierre