Shuenhoy/vtk-m
1
0
Fork 0
mirror of https://gitlab.kitware.com/vtk/vtk-m synced 2024-09-08 13:23:51 +00:00
Code Issues 2 Actions Packages Projects Releases Wiki Activity
33 Commits 9 Branches 24 Tags 36 MiB
C++ 95.1%
CMake 3.2%
Cuda 0.5%
Python 0.4%
Shell 0.3%
Other 0.5%
7d769a8f4a
Go to file
Kenneth Moreland 7d769a8f4a Add classes to manage point coordinates. 
Each type of point coordinates has its own class with the name
PointCoordinates*. Currently there is a PointCoordiantesArray that contains
an ArrayHandle holding the point coordinates and a PointCoordinatesUniform
that takes the standard extent, origin, and spacing for a uniform rectilinear
grid and defines point coordiantes for that. Creating new PointCoordinates
arrays is pretty easy, and we will almost definitely add more. For example,
we should have an elevation version that takes uniform coordinates for
a 2D grid and then an elevation in the third dimension. We can probably
also use a basic composite point coordinates that can build them from
other coordinates.

There is also a DynamicPointCoordinates class that polymorphically stores
an instance of a PointCoordinates class. It has a CastAndCall method that
behaves like DynamicArrayHandle; it can call a functor with an array handle
(possible implicit) that holds the point coordinates.
2014-05-15 13:41:45 -06:00
CMake Properly name the VTKm CMakeFiles. 2014-02-11 14:56:03 -05:00
docs revise the header guard naming convention to not conflict with macro names. 2014-03-07 10:22:36 -05:00
vtkm Add classes to manage point coordinates. 2014-05-15 13:41:45 -06:00
CMakeLists.txt Add in the basic CMake Infrastructure required for vtkm. 2014-02-10 15:00:17 -05:00
LICENSE.txt Add a license to vtkm. 2014-02-10 15:00:17 -05:00
README.md Initial commit. 2014-02-04 15:08:03 -05:00

README.md

Welcome to vtkm design and hackathon.

Resources:

EAVL: https://github.com/jsmeredith/EAVL DAX: https://github.com/Kitware/DaxToolkit