User engelm has pushed new remote branch:

bug-17752-border-consideration-in-thickslice-mode

User engelm has pushed new remote branch:

bug-17752-border-consideration-in-thickslice-mode-master

I don't have much experience in thick slice rendering but did you consider the approach where you just consider the existing slices, hence diminishing the amount of slices when you move to the border of the image. This would avoid the fact the some slices (or many if the sliceThickness is high) look the same.

If yes, why is the propsed approach of advantage?

We thought about the approach you have proposed. The 'problem' is that the user defines how many slices he wants to display using the thick-slice mode. If you simply reduce the number of visible slices at the border of the image, it's no longer what the user defined.

That's why we decided to use the approach I have described in the wiki.

The thing is, I have not found any other application that offers the possibility to simply display images using a thick-slice mode. Thick-slicing is usually only offered as reconstruction in workstations or PACS systems and creates new series.
Thus it's not easy to say how other applications handle the image-borders in thick-slice mode.

It would be interesting to know how the workstations handle the border case during reconstruction. They must have a similar problem.

The average user probably does not think about the border case when defining the number of slices so I still think there is some room for interpretation.

@Markus Did you come across a standard way for handling the border case when rendering thick slices?

I don't have any objections to the proposed solution per se. Having the decision process documented here was my main intention.

Updating target milestone to upcoming release

Updating target milestone.

The approach sound very intuitive to me with a user in mind who changes either the TS slider or the axes sliders. We should definitely merge but for this release it's too late unfortunately. I increased the importance so the feature request is more visible in our priority list.