I had a look as well: two voxels is really an edge case, given the current method it would only give a correct result for number of bins == 1 . But setting the number of bins to at most (number of voxels - 1 ) doesn't really help, it fails e.g. for three voxels. In general thinking a bit about it I came to the conclusion that limiting the number of bins (currently it's _minimum_ 10) would still not yield a correct median.

there is a DerivePointerAlignment option which basically unifies it on a file by file basis, in case there is no agreement. But I agree to Ralf with using the "left" style and put it next to the type

Just observed the same problem with latest "develop" of today.

I found one last hint, about a possible interference with ccache , last try ...

I tried several things again, similar to described above, same situation.

Thanks Hanno. I think @schererj is the original author, so maybe he can comment or we discuss it in the meeting.