[vtk-developers] vtkImageData, C versus Fortran ordering

[Marcus D. Hanwell]

On Wed, Jul 19, 2017 at 1:28 PM, Andy Bauer <andy.bauer at kitware.com> wrote:

> Couldn't you do things in the same way that the VTK SOA zero-copy array
> was done? That way it's transparent to whatever is using the data array how
> the memory is stored.
>

That felt like it would be way more invasive, and possibly not worth it. We
can just keep doing what we are doing too.

>
> Also, on a side note I'm not a big fan of calling these C vs. Fortran
> ordering as it's more how we traverse the data most efficiently. It looks
> like your most efficient way would be to go through Z fastest, then Y and
> finally X (opposite for current vtkImageData arrays). How about something
> like ZYX vs. XYZ ordering for identifying the difference?
>

It is a commonly used term, and works well when searching. It is the
terminology used by the Python community, Eigen, VisIt even, and so I would
say it is reasonable. I am mainly looking at a mismatch between different
toolkits, but I would say using the same terminology as most other
communities seems reasonable.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20170719/0356932f/attachment.html>