mirror of
https://gitlab.kitware.com/vtk/vtk-m
synced 2024-09-16 17:22:55 +00:00
29c96a24fa
The structured connectivity classes are templated on two tags to determine what 2 incident topological elements are being accessed. Back in the day, these were called the "from" elements and "to" elements, as taken from VTK filter names like `PointDataToCellData`. However, these names were found to be very confusion, and after much debate they have been renamed to the visit element type and the incident element type. Meaning that a worklet is "visiting" elements of a particular type (such as visiting each cell) and can access "incident" elements of a particular type (such as the points incident on the cell). I found a few methods converting flat and logical indices using the old, confusing from/to convention. This changes them to the new convention.
84 lines
2.8 KiB
C++
84 lines
2.8 KiB
C++
//============================================================================
|
|
// Copyright (c) Kitware, Inc.
|
|
// All rights reserved.
|
|
// See LICENSE.txt for details.
|
|
//
|
|
// This software is distributed WITHOUT ANY WARRANTY; without even
|
|
// the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
|
|
// PURPOSE. See the above copyright notice for more information.
|
|
//============================================================================
|
|
#ifndef vtk_m_exec_arg_ThreadIndicesPointNeighborhood_h
|
|
#define vtk_m_exec_arg_ThreadIndicesPointNeighborhood_h
|
|
|
|
#include <vtkm/exec/arg/ThreadIndicesNeighborhood.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace exec
|
|
{
|
|
namespace arg
|
|
{
|
|
/// \brief Container for thread information in a WorkletPointNeighborhood.
|
|
///
|
|
///
|
|
class ThreadIndicesPointNeighborhood : public vtkm::exec::arg::ThreadIndicesNeighborhood
|
|
{
|
|
using Superclass = vtkm::exec::arg::ThreadIndicesNeighborhood;
|
|
|
|
public:
|
|
template <vtkm::IdComponent Dimension>
|
|
VTKM_EXEC ThreadIndicesPointNeighborhood(
|
|
const vtkm::Id3& threadIndex3D,
|
|
vtkm::Id threadIndex1D,
|
|
const vtkm::exec::ConnectivityStructured<vtkm::TopologyElementTagPoint,
|
|
vtkm::TopologyElementTagCell,
|
|
Dimension>& connectivity)
|
|
: Superclass(
|
|
threadIndex1D,
|
|
vtkm::exec::BoundaryState{ threadIndex3D, detail::To3D(connectivity.GetPointDimensions()) })
|
|
{
|
|
}
|
|
|
|
template <vtkm::IdComponent Dimension>
|
|
VTKM_EXEC ThreadIndicesPointNeighborhood(
|
|
const vtkm::Id3& threadIndex3D,
|
|
vtkm::Id threadIndex1D,
|
|
vtkm::Id inputIndex,
|
|
vtkm::IdComponent visitIndex,
|
|
vtkm::Id outputIndex,
|
|
const vtkm::exec::ConnectivityStructured<vtkm::TopologyElementTagPoint,
|
|
vtkm::TopologyElementTagCell,
|
|
Dimension>& connectivity)
|
|
: Superclass(
|
|
threadIndex1D,
|
|
inputIndex,
|
|
visitIndex,
|
|
outputIndex,
|
|
vtkm::exec::BoundaryState{ threadIndex3D, detail::To3D(connectivity.GetPointDimensions()) })
|
|
{
|
|
}
|
|
|
|
template <vtkm::IdComponent Dimension>
|
|
VTKM_EXEC ThreadIndicesPointNeighborhood(
|
|
vtkm::Id threadIndex,
|
|
vtkm::Id inputIndex,
|
|
vtkm::IdComponent visitIndex,
|
|
vtkm::Id outputIndex,
|
|
const vtkm::exec::ConnectivityStructured<vtkm::TopologyElementTagPoint,
|
|
vtkm::TopologyElementTagCell,
|
|
Dimension>& connectivity)
|
|
: Superclass(
|
|
threadIndex,
|
|
inputIndex,
|
|
visitIndex,
|
|
outputIndex,
|
|
vtkm::exec::BoundaryState{ detail::To3D(connectivity.FlatToLogicalVisitIndex(inputIndex)),
|
|
detail::To3D(connectivity.GetPointDimensions()) })
|
|
{
|
|
}
|
|
};
|
|
} // arg
|
|
} // exec
|
|
} // vtkm
|
|
#endif //vtk_m_exec_arg_ThreadIndicesPointNeighborhood_h
|