# MRI to US contour propagation module

**URL:** <https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122>\
**Category:** Support\
**Tags:** registration\
**Created:** [December 17, 2020, 9:19pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122 "2020-12-17T21:19:10Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![erpoul](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@erpoul](https://discourse.slicer.org/u/erpoul)\
**Post date:** [December 17, 2020, 9:19pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/1 "2020-12-17T21:19:10Z")

</div>

Hi,  
I am trying to install the new version of 3D slicer with the Mri to US contour proagation module, but it seems the module doesn’t work well in the new version 4.11.20200930. I have installed Slicer RT and the Segment registration module as well as the Slicer prostate module (manually). I am able to register the volume but I get errors when I want to export the Dicom or calculate de similarity. It seems its not showing the hierarchy name of the patients. I have joinded the error logs. I also used the same data as we first validated it. My 2017 version is still working very well.

Here are the log files :

> **[Meet Google Drive – One place for all your files](https://accounts.google.com/ServiceLogin?service=wise&passive=1209600&continue=https:%2F%2Fdrive.google.com%2Ffile%2Fd%2F1PusLN520AcmPCwF0h00m6836vGQDJwwD%2Fview?usp%3Dsharing&followup=https:%2F%2Fdrive.google.com%2Ffile%2Fd%2F1PusLN520AcmPCwF0h00m6836vGQDJwwD%2Fview?usp%3Dsharing)**

Thank you

Best regards

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 17, 2020, 9:20pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/2 "2020-12-17T21:20:05Z")

</div>

Could you please try with latest Slicer Preview Release, too?

---

<div class="post-metadata">

**Author:** ![erpoul](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@erpoul](https://discourse.slicer.org/u/erpoul)\
**Post date:** [December 18, 2020, 1:04pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/3 "2020-12-18T13:04:30Z")

</div>

It is worst with 4.13.0-2020-12-17, this time when loading the US volume it actually split the volume in multiple volume of 1 slice.  
[CRITICAL][Stream] 18.12.2020 07:58:39 [] (unknown:0) - W: OperatorsName (0008,1070) absent in RTSeriesModule (type 2)

[CRITICAL][Stream] 18.12.2020 07:58:40 [] (unknown:0) - W: OperatorsName (0008,1070) absent in RTSeriesModule (type 2)

[WARNING][Python] 18.12.2020 07:59:06 [Python] (C:\Users\erpoul\AppData\Local\NA-MIC\Slicer 4.13.0-2020-12-17\lib\Slicer-4.13\qt-scripted-modules\DICOMLib\DICOMBrowser.py:602) - Warning in DICOM plugin Image sequence when examining loadable 1: US Oncentra Prostate Image Series [0]: Image spacing may need to be calibrated for accurate size measurements.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [December 18, 2020, 6:51pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/4 "2020-12-18T18:51:49Z")

</div>

Could you share a 3D ultrasound volume in DICOM format (anonymized or image of a phantom) so that we can create a rule that allows loading as 3D volume?

The other issue is probably due to a recent Slicer API update. We’ll fix this soon.

---

<div class="post-metadata">

**Author:** ![erpoul](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@erpoul](https://discourse.slicer.org/u/erpoul)\
**Post date:** [December 21, 2020, 3:00pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/5 "2020-12-21T15:00:16Z")

</div>

Data sent to you privately, however I think a reference dataset was left with the module to test, I sent you the exact data that were used for the initial release.

---

<div class="post-metadata">

**Author:** ![erpoul](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@erpoul](https://discourse.slicer.org/u/erpoul)\
**Post date:** [June 11, 2021, 9:14pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/6 "2021-06-11T21:14:11Z")

</div>

Is the bug resolve in a specific version ?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [June 11, 2021, 9:37pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/7 "2021-06-11T21:37:07Z")

</div>

Please test with the latest Slicer Preview Release an let us know if you find any issues.

---

<div class="post-metadata">

**Author:** ![erpoul](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@erpoul](https://discourse.slicer.org/u/erpoul)\
**Post date:** [June 16, 2021, 1:21pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/8 "2021-06-16T13:21:29Z")

</div>

This time no major bug that prevent from actually using the registration button, however the registration is not performed, only the prealignement is performed … There is no affine nor deformable transform after the registration. 4.13.0-2021-06-14 r29960 / f3899b2 was installed. Just for fun I have calculated also similarity indices from the button and only the Dice table appear, the Hausdorff is not possible to get … The testing was done with the testing data I sent you.

---

<div class="post-metadata">

**Author:** ![erpoul](https://avatars.discourse-cdn.com/v4/letter/e/f08c70/32.png) [@erpoul](https://discourse.slicer.org/u/erpoul)\
**Post date:** [June 16, 2021, 3:34pm UTC](https://discourse.slicer.org/t/mri-to-us-contour-propagation-module/15122/9 "2021-06-16T15:34:41Z")

</div>

Finally it still create a problem as I did a mistake and used an older version with 4.13.0-2021-06-14 r29960 / f3899b2 it doesn’t work…

log file sent to you