Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Debug is human, de-fix divine.


devel / comp.protocols.dicom / Re: DICOM: calculated slice position is different from the DICOM header

SubjectAuthor
o DICOM: calculated slice position is different from the DICOM headerKatie Somerville

1
Re: DICOM: calculated slice position is different from the DICOM header

<3f41e30b-3ac7-4bc7-aba3-904edfde5147n@googlegroups.com>

  copy mid

https://www.novabbs.com/devel/article-flat.php?id=10344&group=comp.protocols.dicom#10344

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:7f0b:0:b0:2e0:e49:e785 with SMTP id f11-20020ac87f0b000000b002e00e49e785mr6367494qtk.424.1646957721777;
Thu, 10 Mar 2022 16:15:21 -0800 (PST)
X-Received: by 2002:a05:6214:2a8f:b0:435:e90e:4cee with SMTP id
jr15-20020a0562142a8f00b00435e90e4ceemr4541632qvb.76.1646957721551; Thu, 10
Mar 2022 16:15:21 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Thu, 10 Mar 2022 16:15:21 -0800 (PST)
In-Reply-To: <55ca92d9-ef66-4f54-87c8-f5fa18eb75ba@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=216.10.173.157; posting-account=f75n1goAAACi7r4I3NDx-SFjeUeqPJiW
NNTP-Posting-Host: 216.10.173.157
References: <0c86fa73-8828-4b59-b703-bb900d21aaec@googlegroups.com> <55ca92d9-ef66-4f54-87c8-f5fa18eb75ba@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3f41e30b-3ac7-4bc7-aba3-904edfde5147n@googlegroups.com>
Subject: Re: DICOM: calculated slice position is different from the DICOM header
From: klynn010...@gmail.com (Katie Somerville)
Injection-Date: Fri, 11 Mar 2022 00:15:21 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Katie Somerville - Fri, 11 Mar 2022 00:15 UTC

On Sunday, October 23, 2016 at 10:09:14 AM UTC-4, c.w.c...@gmail.com wrote:
> Hi Luca,
>
> I assume you mean Slice location as Slice position does not exist, Slice location has an open definition as it is the distance to a unspecified point, with this you could get differences. Even the one you describe I would say.
>
> Secondly why do you calculate the slice position if you have the image position?
>
> Regards,
> Wim
> On Friday, October 21, 2016 at 8:49:17 PM UTC+5:30, Luca Pamparana wrote:
> > I am implementing a method to spatially sort DICOM slices in a volume. The way I am doing it is to sort by the position along the slice normal. This is computed as:
> >
> > slice_normal = [0, 0, 0]
> > dir_cosines = ds[0x0020, 0x0037] # Direction cosines
> > slice_normal[0] = dir_cosines[1] * dir_cosines[5] - dir_cosines[2] * dir_cosines[4]
> > slice_normal[1] = dir_cosines[2] * dir_cosines[3] - dir_cosines[0] * dir_cosines[5]
> > slice_normal[2] = dir_cosines[0] * dir_cosines[4] - dir_cosines[1] * dir_cosines[3]
> >
> > image_pos = ds[0x0020, 0x0032] # IPP
> > distance_along_normal = 0
> > for i in range(len(slice_normal)):
> > distance_along_normal += slice_normal[i] * image_pos[i]
> >
> > Now this value distance_along_normal should be equal to the slice position, except in my case it has the opposite sign. So the slice ordering seems to be reversed than what it should be. So, I must need to take something else into account to correctly compute the slice position.
> >
> > Any ideas?
nmgngnnmgfngbh6bthngg

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor