# DICOM browser without the count of images

**URL:** https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000
**Category:** Support
**Tags:** dicom
**Created:** [March 21, 2024, 8:07am UTC](https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000 "2024-03-21T08:07:11Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![slicer365](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/slicer365/32/67549_2.png) [@slicer365](https://discourse.slicer.org/u/slicer365)
#### Post date: [March 21, 2024, 8:07am UTC](https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000/1 "2024-03-21T08:07:11Z")

</div>

In the new version,DICOM browser does not show the count of images in a series.

 ![image](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/8/b/8b4cbae4e2bf7056570098da2db8c9e46cb3ec39.png)

---

<div class="post-metadata">

### Author: ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [April 1, 2024, 11:23am UTC](https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000/2 "2024-04-01T11:23:08Z")

</div>

This might be due to the recent database update regarding the visual DICOM browser. What happens if you remove all the data from the database (or start a clean database) and import the patients again?

---

<div class="post-metadata">

### Author: ![chir.set](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/chir.set/32/66982_2.png) [@chir.set](https://discourse.slicer.org/u/chir.set)
#### Post date: [April 1, 2024, 11:29am UTC](https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000/3 "2024-04-01T11:29:01Z")

</div>

> [@slicer365](#):
>
> does not show the count of images in a series

It’s quite [old](https://discourse.slicer.org/t/dicom-browser-does-not-show-the-count-of-images-in-a-series/33506), I guess it’s in the ‘unexplained’ category of event. But it’s good you have highlighted it again.

> [@cpinter](#):
>
> start a clean database

It does not help unfortunately.

---

<div class="post-metadata">

### Author: ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [April 1, 2024, 12:08pm UTC](https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000/4 "2024-04-01T12:08:04Z")

</div>

OK thanks! I will try to debug into this when I have a minute (I’m very busy nowadays but will try).

---

<div class="post-metadata">

### Author: ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)
#### Post date: [April 2, 2024, 12:54pm UTC](https://discourse.slicer.org/t/dicom-browser-without-the-count-of-images/35000/5 "2024-04-02T12:54:10Z")

</div>

> [@chir.set](#):
>
> It’s quite [old](https://discourse.slicer.org/t/dicom-browser-does-not-show-the-count-of-images-in-a-series/33506)

If you take a good look at that thread you’ll see at the bottom that it turned out to be working. Unfortunately I noticed this after wasting a lot of time with looking at older versions. So far my investigation shows that it still worked on Dec 12, 2023 (5.6.1), and it did not work on Jan 15, 2024 (the new visual DICOM browser that I suspected was introduced just after, so it’s not the culprit apparently).

For the attention of developers: I also did some debugging, which shows that the `currentSeriesInstanceUid` variable (element in `this->UpdatedSeriesInstanceUIDs`) is empty string.

> <https://github.com/commontk/CTK/blob/fb72e1aa2b143bb942e6c7cdc5603a676884a80a/Libs/DICOM/Core/ctkDICOMDisplayedFieldGeneratorSeriesImageCountRule.cpp#L89>

By the way it is not just the image count that is broken, but also the series count on the study level. So it is possible that the display field rules do not get access any more to the updated instance UIDs.

I don’t have more time to work on this, but wanted to disclose my findings so far. I think if we find whick commit broke this instance UID access then we have a good chance of fixing this.
