@Sonia: I associated the issue to Kent. Can you work with him on that ?

@kent: The issue is targeted for 4.4 .. is it something you will have time to address. If not we all add it to the backlog.

Sure, I am happy to. Farukh can help with the debugging of the module. I have sent her a link to the bug report. Thanks!

I have never actually used DWIConvert from the Slicer GUI. Some observations:

The "Output Directory" parameter specifies the directory in which the NRRD file will be written. In general, this is a useless parameter; it makes more sense to put the full path in the output NRRD filename. "Output Directory" is there because it was there when I started work on DWIConvert and never changed or removed it.

If you do specify the full path for a NRRD filename, then specify OutputDirectory, then the write will probably fail, e.g. on our network if I saved on our network, if "Output Filename" is

/raid0/homes/kent/test.nrrd

If I mistakenly specified "Output Directory" as /raid0/homes/kent, then DWIConvert would try to write /raid0/homes/kent/raid0/homes/kent/test.nrrd which will fail.

I don't know if anyone else has mentioned this yet, but "File->Save As..." in Slicer has nothing to do with the DWIConvert program. I don't even know what it can save though I imagine it's the current MRML scene, not the NRRD file.

I can fix DWIConvert if someone can tell me what's actually needed. Take away the "Output Directory" parameter?

@Kent: Thanks for the detailed report. To clarify, using "Save as" in Slicer you can save either the whole scene or any file independently.

@Sonia, Farukh: Can you work with Kent and the Slice community to define which parameter makes sense and if anybody is using this "mysterious" parameters.

Thanks and have a good weekend,
Jc

Fixed in r23468
See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=2346