Feature request: specify output name for file in transformix/elastix

[Svdvoort]

Currently, when running elastix/transformix it is only possible to specify the output directory, and not specifically the output name.
For example, from elastix the output files will always be named TransformParameters.0.txt and from transformix result.nii.gz.

Especially for transformix it would be nice to be able to specify the output file name.
I often have the situation where I need to apply the same transformation to multiple images (for example different MR modalities). In this case, I either have to create a new directory per image just to save the transformed image or have to write a wrapper around transformix to rename the output file before a new run.

Could a flag be added to elastix/transformix to specify the output filename directly?

For example:

transformix -tp TransformParameters.0.txt -out /home/user/ -filename T1 original_scan.nii.gz

If the filename flag is not provided, elastix/transformix can use the current default behavior (in this case, writing the file as result.nii.gz), not breaking any existing functionality.

[N-Dekker]

Interesting suggestion, thanks!

Note that in Python you can already achieve this, when using ITKElastix https://github.com/InsightSoftwareConsortium/ITKElastix

[N-Dekker]

As far as I can see, the default is "output-directory/result.mhd", looking at:

elastix/Core/Kernel/elxElastixTemplate.hxx

Lines 385 to 389 in 0a1e90f

	/** Create a name for the final result. */
	std::string resultImageFormat = "mhd";
	this->GetConfiguration()->ReadParameter(resultImageFormat, "ResultImageFormat", 0, false);
	std::ostringstream makeFileName;
	makeFileName << this->GetConfiguration()->GetCommandLineArgument("-out") << "result." << resultImageFormat;

I guess the proposal is to allow specifying a path relative to the output directory, right? Or would it be relative to the current working directory?

Of course, it should then also allow specifying an absolute path, either starting with a (back) slash, or a drive letter, followed by colon and (back) slash. Right?

But then, would it entirely ignore the "ResultImageFormat" parameter from the parameter file?

If the directory of the specified file path would be non-existing, would it be OK for transformix to just fail? Or should it try to create the directory?

[Svdvoort]

In my opinion it can be much simpler than this. Although specifying additional paths would be nice, in principle I think it's fine to store everything just in the output directory.
However, the file will always be called result. , and it would be nice to change the "result" part since the image format can already be changed. It could be a flag, but also just a parameter in the parameter file, just like the ResultImageFormat is.

That way instead of always saving a file as result. it can be something like .

This allows for a bit more flexibility and clarity when saving transformed images.

[N-Dekker]

@Svdvoort Can you please check if the "ResultImageName" parameter implemented with pull request #776 commit b581b92 works the way you had in mind?