Change Details

I recently wrote a command-line app for T3 to voxelize RTSTRUCTs as it was as simple as throwing a reference image and an RTSTRUCT at an already existing filter that we use in the Segmentation Utilities. However, eMITK/RTTB also provides a Voxelizer Tool that does the job as well but I wasn't able to activate it so far. We should discuss how to continue and if it is worth having such an app in plain MITK. Options are: # Do nothing, leave it as is. # Push the new command-line app after adding some input checking for increased robustness of the app. # Move (and fix?) the Voxelizer Tool from eMITK/RTTB to MITK.

I recently wrote a command-line app for @norajitr to voxelize RTSTRUCTs as it was as simple as throwing a reference image and an RTSTRUCT at an already existing filter that we use in the Segmentation Utilities. However, eMITK/RTTB also provides a Voxelizer Tool that does the job as well but I wasn't able to activate it so far. We should discuss how to continue and if it is worth having such an app in plain MITK. Options are: # Do nothing, leave it as is. # Push the new command-line app after adding some input checking for increased robustness of the app. # Move (and fix?) the Voxelizer Tool from eMITK/RTTB to MITK.

I recently wrote a command-line app for T3@norajitr to voxelize RTSTRUCTs as it was as simple as throwing a reference image and an RTSTRUCT at an already existing filter that we use in the Segmentation Utilities. However, eMITK/RTTB also provides a Voxelizer Tool that does the job as well but I wasn't able to activate it so far. We should discuss how to continue and if it is worth having such an app in plain MITK. Options are: # Do nothing, leave it as is. # Push the new command-line app after adding some input checking for increased robustness of the app. # Move (and fix?) the Voxelizer Tool from eMITK/RTTB to MITK.