# DWIConvert: no input volume not allowed for lossy conversion from NIFTI FSL to nrrd

**URL:** <https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650>\
**Category:** Support\
**Created:** [December 12, 2017, 2:47pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650 "2017-12-12T14:47:37Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![vsivan](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vsivan](https://discourse.slicer.org/u/vsivan)\
**Post date:** [December 12, 2017, 2:47pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/1 "2017-12-12T14:47:37Z")

</div>

Hello,

I am able to run DWI Convert for FSL to NRRD conversion with no input volume by selecting allow lossy conversion on DWIConvert 4.7.1. When I run DWI Convert with the same parameters in version 4.8.0, I get the following error:

```auto
Diffusion-weighted DICOM Import (DWIConvert) standard error:

W: DcmItem: Length of element (0300,d7ec) is odd
E: DcmElement: Unknown Tag & Data (0300,d7ec) larger (3855987813) than remaining bytes in file
W: DcmItem: Dataset not in ascending tag order, at element (0300,d7ec)
W: DcmItem: Length of element (8b1f,0808) is odd
E: DcmElement: Unknown Tag & Data (8b1f,0808) larger (1512397297) than remaining bytes in file
W: DcmItem: Length of element (8b1f,0808) is odd
E: DcmElement: Unknown Tag & Data (8b1f,0808) larger (1512500603) than remaining bytes in file
W: DcmItem: Length of element (0300,d7ec) is odd
E: DcmElement: Unknown Tag & Data (0300,d7ec) larger (3855987813) than remaining bytes in file
W: DcmItem: Dataset not in ascending tag order, at element (0300,d7ec)
W: DcmItem: Length of element (0300,d9ec) is odd
E: DcmElement: Unknown Tag & Data (0300,d9ec) larger (3520476281) than remaining bytes in file
W: DcmItem: Dataset not in ascending tag order, at element (0300,d9ec)
W: DcmItem: Length of element (0300,d7ec) is odd
E: DcmElement: Unknown Tag & Data (0300,d7ec) larger (1737862245) than remaining bytes in file
W: DcmItem: Dataset not in ascending tag order, at element (0300,d7ec)
W: DcmItem: Length of element (6600,c139) is odd
E: DcmElement: Unknown Tag & Data (6600,c139) larger (63459087) than remaining bytes in file
Error: no DICOMfiles found in inputDirectory: .
Unable to create converter!

```

Is a workaround to carry out the conversion in the newer version?

Thanks.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [December 12, 2017, 3:08pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/2 "2017-12-12T15:08:29Z")

</div>

It looks like the module is trying to run in DICOM-\>NRRD mode. Can you please send a screenshot of the options you selected? (please blank out any confidential information)

---

<div class="post-metadata">

**Author:** ![vsivan](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vsivan](https://discourse.slicer.org/u/vsivan)\
**Post date:** [December 12, 2017, 3:47pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/3 "2017-12-12T15:47:21Z")

</div>

Here’s the screenshot for the newer version (4.8.0):

 ![Screenshot from 2017-12-12 10-46-12](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/7/d7d9757930735af79c0fe8dc07df93cfb0ddc9e9.png)

EDIT: it is not apparent from the screenshot, but allowLossyConversion has been selected

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [December 12, 2017, 8:11pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/4 "2017-12-12T20:11:19Z")

</div>

Ok, looks like an issue which I already fixed. So please try the [nightly](http://download.slicer.org/) and let me know if it still doesn’t work. See here for details:

[https://issues.slicer.org/view.php?id=4463](https://issues.slicer.org/view.php?id=4463)

---

<div class="post-metadata">

**Author:** ![vsivan](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vsivan](https://discourse.slicer.org/u/vsivan)\
**Post date:** [December 12, 2017, 8:21pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/5 "2017-12-12T20:21:46Z")

</div>

Hi Isaiah,

Thanks! I am currently working with a build of Slicer that needs this fix. Do you know if there is a way to get it onto the build of Slicer, without having to rebuild everything?

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [December 12, 2017, 8:51pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/6 "2017-12-12T20:51:11Z")

</div>

Your screenshot says 2017-10-11, but if you are indeed on 4.8 then I think [this branch](https://github.com/Slicer/BRAINSTools/tree/slicer-2017-11-29-v4.7.1-42ac3c3) should build cleanly. So do something like:

- `cd SuperBuild/BRAINSTools`
- `git fetch origin`
- `git checkout slicer-2017-11-29-v4.7.1-42ac3c3`
- `cd SuperBuild/Slicer-build`
- `make` (or ninja, MSBuild, etc.)

(note that BRAINSTools is an “external module”, so it has a source tree under `SuperBuild/BRAINSTools`, but actually builds under `Slicer-build` – it does not have a `BRAINSTools-build` tree like most other external projects)

---

<div class="post-metadata">

**Author:** ![vsivan](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vsivan](https://discourse.slicer.org/u/vsivan)\
**Post date:** [December 12, 2017, 9:27pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/7 "2017-12-12T21:27:55Z")

</div>

Hi Isaiah,

Apologies, but I might have been unclear. I am working with a Slicer 4.7 build. When I said “4.8”, I was referring to the version that appeared in the DWIConvert XML file.

```auto
<?xml version="1.0" encoding="utf-8"?> 
<executable> 
  <category>Diffusion.Import and Export</category> 
  <title>Diffusion-weighted DICOM Import (DWIConvert)</title> 
  <description><![CDATA[Converts diffusion weighted MR images in DICOM series into NRRD format for analysis in Slicer. This program has been tested on only a limited subset of DTI DICOM formats available from Siemens, GE, and Philips scanners. Work in progress to support DICOM multi-frame data. The program parses DICOM header to extract necessary information about measurement frame, diffusion weighting directions, b-values, etc, and write out a NRRD image. For non-diffusion weighted DICOM images, it loads in an entire DICOM series and writes out a single dicom volume in a .nhdr/.raw pair.]]></description> 
  <version>4.8.0</version> 

```

Given this, what would you suggest I do for getting the build to work on the Slicer version 4.7 build.

Thank you.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [December 12, 2017, 9:37pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/8 "2017-12-12T21:37:28Z")

</div>

> [@vsivan](#):
>
> what would you suggest I do for getting the build to work on the Slicer version 4.7 build.

Update to current trunk 😉

There was about one year worth of BRAINSTools updates pulled in to Slicer close to when 4.8 was released, so those changes I linked are not likely to apply cleanly. Plus there are probably ITK updates required as well. Figuring out inter-dependencies could easily take more than the two hours it will require to update Slicer+dependencies to current trunk (on any relatively recent 2+ core computer).

Between 2017-10-11 and current trunk I don’t there are any significant API changes affecting your own code, if that is the concern.

---

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/ihnorton/32/9_2.png) [@ihnorton](https://discourse.slicer.org/u/ihnorton)\
**Post date:** [December 12, 2017, 9:47pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/9 "2017-12-12T21:47:07Z")

</div>

Hmm, actually the BRAINSTools update was in September, so you might be able to get away with pulling the changes as I indicated.

[https://github.com/Slicer/Slicer/commit/160cff9f8881f9c6f054abbc490e0d64057fcf09#diff-88b37dcc9267d819b6fabff68a8e5290](https://github.com/Slicer/Slicer/commit/160cff9f8881f9c6f054abbc490e0d64057fcf09#diff-88b37dcc9267d819b6fabff68a8e5290)

---

<div class="post-metadata">

**Author:** ![vsivan](https://avatars.discourse-cdn.com/v4/letter/v/edb3f5/32.png) [@vsivan](https://discourse.slicer.org/u/vsivan)\
**Post date:** [December 12, 2017, 10:02pm UTC](https://discourse.slicer.org/t/dwiconvert-no-input-volume-not-allowed-for-lossy-conversion-from-nifti-fsl-to-nrrd/1650/10 "2017-12-12T22:02:56Z")

</div>

Okay, I will try that first. Otherwise, I’ll rebuild Slicer as you suggested. Thanks, Isaiah!