Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

The Macintosh is Xerox technology at its best.

devel / comp.protocols.dicom / Re: DICOM image does not display. "Dicom dataset read failed" error message.

SubjectAuthor
* DICOM image does not display. "Dicom dataset read failed" error message.Howard Mann
`* Re: DICOM image does not display. "Dicom dataset read failed" error message.Narendra Karanam
 `* Re: DICOM image does not display. "Dicom dataset read failed" error message.Howard Mann
  `- Re: DICOM image does not display. "Dicom dataset read failed" error message.David Gobbi

1
DICOM image does not display. "Dicom dataset read failed" error message.

<71046854-bc49-4f5f-aa62-b28a4617683cn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ad4:4ea8:: with SMTP id ed8mr1124974qvb.52.1641847211809;
Mon, 10 Jan 2022 12:40:11 -0800 (PST)
X-Received: by 2002:a37:9ad8:: with SMTP id c207mr1139114qke.662.1641847211633;
Mon, 10 Jan 2022 12:40:11 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Mon, 10 Jan 2022 12:40:11 -0800 (PST)
Injection-Info: google-groups.googlegroups.com; posting-host=24.10.184.23; posting-account=fTym5woAAAB8z2TvxCc_OLj5fNUUE1ig
NNTP-Posting-Host: 24.10.184.23
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <71046854-bc49-4f5f-aa62-b28a4617683cn@googlegroups.com>
Subject: DICOM image does not display. "Dicom dataset read failed" error message.
From: howardm@xmission.com (Howard Mann)
Injection-Date: Mon, 10 Jan 2022 20:40:11 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 20
 by: Howard Mann - Mon, 10 Jan 2022 20:40 UTC

Hi,

I'm trying to view a .dcm image in Osirix.

It does not display anything.

Using Dicom Validator, (in OsiriX) I see the following at the top:

___

(0xe000,0x104f) ? Error - Tag read failed - Implicit VR encoding even though supposed to be explicit
Error - Dicom dataset read failed

___

Any ideas what this means ?

Thanks!

Howard

Re: DICOM image does not display. "Dicom dataset read failed" error message.

<29495582-4b13-4838-9385-4fc01ae60b34n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:a05:622a:1488:: with SMTP id t8mr2329778qtx.61.1641872591809;
Mon, 10 Jan 2022 19:43:11 -0800 (PST)
X-Received: by 2002:ac8:7f12:: with SMTP id f18mr2280703qtk.391.1641872591423;
Mon, 10 Jan 2022 19:43:11 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Mon, 10 Jan 2022 19:43:11 -0800 (PST)
In-Reply-To: <71046854-bc49-4f5f-aa62-b28a4617683cn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=49.205.114.40; posting-account=jFW0rQoAAAD15nfqxNiIpj5ytZzI9EFG
NNTP-Posting-Host: 49.205.114.40
References: <71046854-bc49-4f5f-aa62-b28a4617683cn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <29495582-4b13-4838-9385-4fc01ae60b34n@googlegroups.com>
Subject: Re: DICOM image does not display. "Dicom dataset read failed" error message.
From: nare06@gmail.com (Narendra Karanam)
Injection-Date: Tue, 11 Jan 2022 03:43:11 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 22
 by: Narendra Karanam - Tue, 11 Jan 2022 03:43 UTC

Change preferred syntax to Implicit Little Endian and again. By default probably Osirix might be expecting Explicit Little Endian VR encoding.

On Tuesday, January 11, 2022 at 2:10:13 AM UTC+5:30, how...@xmission.com wrote:
> Hi,
>
> I'm trying to view a .dcm image in Osirix.
>
> It does not display anything.
>
> Using Dicom Validator, (in OsiriX) I see the following at the top:
>
> ___
>
> (0xe000,0x104f) ? Error - Tag read failed - Implicit VR encoding even though supposed to be explicit
> Error - Dicom dataset read failed
>
> ___
>
> Any ideas what this means ?
>
> Thanks!
>
> Howard

Re: DICOM image does not display. "Dicom dataset read failed" error message.

<f4521f98-fc81-4c33-9664-f145fe529311n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:5985:: with SMTP id e5mr1070990qte.58.1641876417651;
Mon, 10 Jan 2022 20:46:57 -0800 (PST)
X-Received: by 2002:a05:6214:2a88:: with SMTP id jr8mr2428488qvb.18.1641876417496;
Mon, 10 Jan 2022 20:46:57 -0800 (PST)
Path: i2pn2.org!rocksolid2!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Mon, 10 Jan 2022 20:46:57 -0800 (PST)
In-Reply-To: <29495582-4b13-4838-9385-4fc01ae60b34n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=24.10.184.23; posting-account=fTym5woAAAB8z2TvxCc_OLj5fNUUE1ig
NNTP-Posting-Host: 24.10.184.23
References: <71046854-bc49-4f5f-aa62-b28a4617683cn@googlegroups.com> <29495582-4b13-4838-9385-4fc01ae60b34n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <f4521f98-fc81-4c33-9664-f145fe529311n@googlegroups.com>
Subject: Re: DICOM image does not display. "Dicom dataset read failed" error message.
From: howardm@xmission.com (Howard Mann)
Injection-Date: Tue, 11 Jan 2022 04:46:57 +0000
Content-Type: text/plain; charset="UTF-8"
Lines: 10
 by: Howard Mann - Tue, 11 Jan 2022 04:46 UTC

On Monday, January 10, 2022 at 8:43:13 PM UTC-7, nar...@gmail.com wrote:
> Change preferred syntax to Implicit Little Endian and again. By default probably Osirix might be expecting Explicit Little Endian VR encoding.
....

I'm afraid I don't know what you mean by "Change preferred syntax to Implicit Little Endian *and again*"

When I inspect the metdata of the file and the TransferSyntaxUID Tag, I see: 1.2.840.10008.1.2.2 [BigEndian Explicit]

A different image file on the same patient has the same Tag value and displays properly.

Howard

Re: DICOM image does not display. "Dicom dataset read failed" error message.

<7a7e83d0-01ad-4533-b0c7-1d25b05f2c9bn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: comp.protocols.dicom
X-Received: by 2002:ac8:5a88:: with SMTP id c8mr5844149qtc.635.1641944478877;
Tue, 11 Jan 2022 15:41:18 -0800 (PST)
X-Received: by 2002:a05:620a:1a9d:: with SMTP id bl29mr4892930qkb.55.1641944478694;
Tue, 11 Jan 2022 15:41:18 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.dicom
Date: Tue, 11 Jan 2022 15:41:18 -0800 (PST)
In-Reply-To: <f4521f98-fc81-4c33-9664-f145fe529311n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=198.48.161.196; posting-account=oJk4vAoAAAAuHqwGdLwYUlL776upyWJ3
NNTP-Posting-Host: 198.48.161.196
References: <71046854-bc49-4f5f-aa62-b28a4617683cn@googlegroups.com>
<29495582-4b13-4838-9385-4fc01ae60b34n@googlegroups.com> <f4521f98-fc81-4c33-9664-f145fe529311n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7a7e83d0-01ad-4533-b0c7-1d25b05f2c9bn@googlegroups.com>
Subject: Re: DICOM image does not display. "Dicom dataset read failed" error message.
From: david.gobbi@gmail.com (David Gobbi)
Injection-Date: Tue, 11 Jan 2022 23:41:18 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 16
 by: David Gobbi - Tue, 11 Jan 2022 23:41 UTC

One of the data elements in that particular file might have an incorrect offset (VL) to the next item. I say this because (0xe000,0x104f) is not a valid tag. No tags in the standard start with 0xe000. However, there is a tag ​(0xfffe, 0xe000) that marks the beginning of an encapsulated item (but that might be a red herring).

The BigEndianExplicit syntax is rare and was retired long ago. Files that use it are either very old, or the files were converted (by accident?) from a different syntax.

If you know where the files originated (maybe a PACS or another OsiriX?), it might be possible to re-export the files as little endian. Or if somebody sent you these files, politely explain the situation and ask them to re-send.

And sometimes glitches in the file's structure can be corrected with a hex editor. On macOS I've used xxd on the command-line. Not fun.

1
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor