[Insight-users] MultiResImageRegistration

Lydia Ng lng at insightful . com
Tue, 16 Sep 2003 09:34:42 -0700


This is a multi-part message in MIME format.

------_=_NextPart_001_01C37C70.6E0C95A4
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

There was bug in the pyramid filter that was fixed back in early April
'03.
Does the description in the attached email match your problem?
If so, you will need the current cvs version of ITK.

- Lydia

> -----Original Message-----
> From: Thomas Boettger [mailto:t . boettger at dkfz-heidelberg . de]
> Sent: Tuesday, September 16, 2003 2:07 AM
> To: insight-users at public . kitware . com
> Subject: [Insight-users] MultiResImageRegistration
>=20
> Hello,
>=20
> I am currently playing around with the code from the registration
> examples.
>=20
> When trying to use a slightly modified version of
> MultiResImageRegistration1 (modified image dimension to 3) my program
> crashed in the second level iteration in
> itk::ImageConstIterator.Get(void) called from
> MattesMutualInformation.Initialize().
>=20
> I think the reason was a bad image region size, which I cannot
influence
> because it is determined in the pyramid filter.
>=20
> I found a posting about some bug in this iterator class in this list
> here and want to know if I can still use my ITK 1.2 version or if it
is
> necessary to use the CVS version. If
>=20
> If MultiResImageRegistration works fine with ITK 1.2 what else am I
> doing wrong?
>=20
> Thanks in advance,
> Thomas
>=20
> --
> Dipl.-Inform. Thomas Boettger
> Deutsches Krebsforschungszentrum         (German Cancer Research
Center)
> Div. Medical and Biological Informatics H0100    Tel: (+49) 6221-42
2328
> Im Neuenheimer Feld 280                          Fax: (+49) 6221-42
2345
> D-69120 Heidelberg                            e-mail:
t . boettger at dkfz . de
> Germany
http://www . dkfz . de/mbi/people/thomasb . shtml
>=20
>=20
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk . org
> http://www . itk . org/mailman/listinfo/insight-users

------_=_NextPart_001_01C37C70.6E0C95A4
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit

X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3
Received:  from localhost.localdomain ([172.16.1.251]) by se2kexch01.insightful.com with Microsoft SMTPSVC(5.0.2195.5329); Fri, 4 Apr 2003 12:45:59 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Received:  from ms-smtp-02.nyroc.rr.com (ms-smtp-02.nyroc.rr.com [24.92.226.49]) by localhost.localdomain (8.12.8/8.12.5) with ESMTP id h34KoNA6014587 for <lng at insightful . com>; Fri, 4 Apr 2003 12:50:23 -0800
Received:  from kitware.com (alb-24-194-241-249.nycap.rr.com [24.194.241.249]) by ms-smtp-02.nyroc.rr.com (8.12.5/8.12.2) with ESMTP id h34Kjuep013764; Fri, 4 Apr 2003 15:45:56 -0500 (EST)
content-class: urn:content-classes:message
Subject: Re: [Insight-users] multi resolution registration : problem in pyramid
Date: Fri, 4 Apr 2003 13:45:49 -0700
Message-ID: <3E8DEEFD . 4090206 at kitware . com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Insight-users] multi resolution registration : problem in pyramid
Thread-Index: AcL66zK6G7dB6XiHQn6rUh8MMU+XMw==
From: "Luis Ibanez" <luis . ibanez at kitware . com>
To: "DE CRAENE Mathieu" <decraene at bwh . harvard . edu>
Cc: <insight-users at public . kitware . com>,
	"Lydia Ng" <lng at insightful . com>

Hi Mathieu,


This problem was recently identified by Lydia
from the Purify errors reported in the Dashboard.

The proposed solution involves cropping the fixed image
region to the region covered by the Buffered region.


Regards


   Luis


----------------------------------
DE CRAENE Mathieu wrote:
> Hi all !
>=20
> I'm  encountering a problem with the =
MultiResolutionImageRegistrationMethod. At the last registration level, =
I get (on certain images) a seg fault. Trying to debug, I have displayed =
the fixed image region and called the PrintSelf of the fixed Image at =
each level. Here is what I get :=20
>=20
> 1. BEFORE REGISTRATION
>=20
> Registration : Fixed Image Region : ImageRegion (0xbffff928)
>   Dimension: 3
>   Index: [50, 80, 0]
>   Size: [150, 96, 19]
>=20
> Registration : Fixed Image : Image (0x816a9b8)
>   Reference Count: 3
>   Modified Time: 237
>   Debug: Off
>   Observers:=20
>     none
>   Source: (0x815a7d8)=20
>   Source output index: 0
>   Release Data: Off
>   Data Released: False
>   Global Release Data: Off
>   PipelineMTime: 234
>   UpdateTime: 239
>   LastRequestedRegionWasOutsideOfTheBufferedRegion: 1
>   LargestPossibleRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 19]
>   BufferedRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 19]
>   RequestedRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 19]
>   Origin: [-109.57, -219.141, -45]
>   Spacing: [0.859375, 1.71875, 5]
>   PixelContainer: ImportImageContainer (0x815a848)
>   Reference Count: 2
>   Modified Time: 238
>   Debug: Off
>   Observers:=20
>     none
>   Pointer: 0x815a874
>   Container manages memory: true
>   Size: 1245184
>   Capacity: 1245184
>=20
> 2. FIRST REGISTRATION LEVEL
>=20
> FIXED IMAGE REGION : ImageRegion (0xbffff430)
>   Dimension: 3
>   Index: [25, 40, 0]
>   Size: [75, 48, 9]
>=20
>=20
> Image (0x81497d0)
>   Reference Count: 3
>   Modified Time: 292
>   Debug: Off
>   Observers:=20
>     none
>   Source: (0x8148f90)=20
>   Source output index: 0
>   Release Data: Off
>   Data Released: False
>   Global Release Data: Off
>   PipelineMTime: 252
>   UpdateTime: 443
>   LastRequestedRegionWasOutsideOfTheBufferedRegion: 0
>   LargestPossibleRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [128, 128, 9]
>   BufferedRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [128, 128, 9]
>   RequestedRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [128, 128, 9]
>   Origin: [-109.57, -219.141, -45]
>   Spacing: [1.71875, 3.4375, 10]
>   PixelContainer: ImportImageContainer (0x81498b8)
>   Reference Count: 2
>   Modified Time: 293
>   Debug: Off
>   Observers:=20
>     none
>   Pointer: 0x81498e4
>   Container manages memory: true
>   Size: 147456
>   Capacity: 147456
>=20
> 3. SECOND (FULL RESOLUTION) REGISTRATION LEVEL
>=20
> FIXED IMAGE REGION : ImageRegion (0xbffff430)
>   Dimension: 3
>   Index: [50, 80, 0]
>   Size: [150, 96, 19]
>=20
>=20
> Image (0x8149938)
>   Reference Count: 3
>   Modified Time: 370
>   Debug: Off
>   Observers:=20
>     none
>   Source: (0x8148f90)=20
>   Source output index: 1
>   Release Data: Off
>   Data Released: False
>   Global Release Data: Off
>   PipelineMTime: 252
>   UpdateTime: 444
>   LastRequestedRegionWasOutsideOfTheBufferedRegion: 0
>   LargestPossibleRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 19]
>   BufferedRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 18] >>>>>>>>>>>>>>>> ???????????????
>   RequestedRegion:=20
>     Dimension: 3
>     Index: [0, 0, 0]
>     Size: [256, 256, 18] >>>>>>>>>>>>>>>> ???????????????
>   Origin: [-109.57, -219.141, -45]
>   Spacing: [0.859375, 1.71875, 5]
>   PixelContainer: ImportImageContainer (0x8149a20)
>   Reference Count: 2
>   Modified Time: 371
>   Debug: Off
>   Observers:=20
>     none
>   Pointer: 0x8149a4c
>   Container manages memory: true
>   Size: 1179648
>   Capacity: 1179648
>=20
> It seems that at the last (full resolution) registration level, the =
buffered region differed from the fixed image region. I'm using the =
MattesMutualInformationMetric... So it seems that when the metric =
computes the maximum and the minimum of the region (to compute the size =
of bins), the metric tries to reach voxels outside the bufferd region... =
which could explain the segmentation fault.
>=20
> I don't understand why this problem appears only at the full =
registration level and why the full resolution image in the pyramid is =
not identical to the (fixed) image I passed to the =
MultiResolutionImageMethod.
>=20
> Any suggestion or comments are welcome !!
>=20
> Thanks for your help,
> Math.
> ----------------------------
> Mathieu De Craene
> Brigham and Womens Hospital
> Surgical Planning Laboratory=09
> L1 - room 050
> 75 Francis Street
> Boston MA 02115
> decraene at bwh . harvard . edu
> _______________________________________________
> Insight-users mailing list
> Insight-users at public . kitware . com
> http://public . kitware . com/mailman/listinfo/insight-users
>=20






------_=_NextPart_001_01C37C70.6E0C95A4--