VTK/Supporting Arrays With Arbitrary Memory Layouts: Difference between revisions
From KitwarePublic
< VTK
Jump to navigationJump to search
(Created page with "in progress") |
No edit summary |
||
Line 1: | Line 1: | ||
in | =Background= | ||
Not too long ago, the notion of [[VTK/InSituDataStructures|Mapped Arrays]] was introduced in VTK. The main objective behind these was to add support to handle data arrays with arbitrary memory layouts in VTK. This motivation was to support in-situ data processing use-cases without having to ''deep-copy'' arrays from simulation datastructures to VTK's memory layout when the simulation used different memory layout that VTK's. |
Revision as of 17:49, 6 July 2015
Background
Not too long ago, the notion of Mapped Arrays was introduced in VTK. The main objective behind these was to add support to handle data arrays with arbitrary memory layouts in VTK. This motivation was to support in-situ data processing use-cases without having to deep-copy arrays from simulation datastructures to VTK's memory layout when the simulation used different memory layout that VTK's.