64958b014b
The original design of invoke and the transport infrastructure relied on the implementation behavior of vtkm::cont types such as ArrayHandle that used an internal shared_ptr to managed state. This allowed passing by value instead of passing by non-const ref when needing to transfer information to the device. As VTK-m adds support for classes that use virtuals the ability to pass by base pointer type allows for us to invoke worklets using a base type without the risk of type slicing. Additional by moving over to a non-const ref Invocation we can update all transports that have 'output' to now be by ref and therefore support types that can't be copied while being 'more' correct.
92 lines
3.7 KiB
C++
92 lines
3.7 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.
|
|
//
|
|
// Copyright 2014 National Technology & Engineering Solutions of Sandia, LLC (NTESS).
|
|
// Copyright 2014 UT-Battelle, LLC.
|
|
// Copyright 2014 Los Alamos National Security.
|
|
//
|
|
// Under the terms of Contract DE-NA0003525 with NTESS,
|
|
// the U.S. Government retains certain rights in this software.
|
|
//
|
|
// Under the terms of Contract DE-AC52-06NA25396 with Los Alamos National
|
|
// Laboratory (LANL), the U.S. Government retains certain rights in
|
|
// this software.
|
|
//============================================================================
|
|
#ifndef vtk_m_worklet_Dispatcher_MapTopology_h
|
|
#define vtk_m_worklet_Dispatcher_MapTopology_h
|
|
|
|
#include <vtkm/TopologyElementTag.h>
|
|
#include <vtkm/cont/DeviceAdapter.h>
|
|
#include <vtkm/worklet/WorkletMapTopology.h>
|
|
#include <vtkm/worklet/internal/DispatcherBase.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace worklet
|
|
{
|
|
|
|
/// \brief Dispatcher for worklets that inherit from \c WorkletMapTopology.
|
|
///
|
|
template <typename WorkletType, typename Device = VTKM_DEFAULT_DEVICE_ADAPTER_TAG>
|
|
class DispatcherMapTopology
|
|
: public vtkm::worklet::internal::DispatcherBase<DispatcherMapTopology<WorkletType, Device>,
|
|
WorkletType,
|
|
vtkm::worklet::detail::WorkletMapTopologyBase>
|
|
{
|
|
using Superclass =
|
|
vtkm::worklet::internal::DispatcherBase<DispatcherMapTopology<WorkletType, Device>,
|
|
WorkletType,
|
|
vtkm::worklet::detail::WorkletMapTopologyBase>;
|
|
using ScatterType = typename Superclass::ScatterType;
|
|
|
|
public:
|
|
// If you get a compile error here about there being no appropriate constructor for ScatterType,
|
|
// then that probably means that the worklet you are trying to execute has defined a custom
|
|
// ScatterType and that you need to create one (because there is no default way to construct
|
|
// the scatter). By convention, worklets that define a custom scatter type usually provide a
|
|
// static method named MakeScatter that constructs a scatter object.
|
|
VTKM_CONT
|
|
DispatcherMapTopology(const WorkletType& worklet = WorkletType(),
|
|
const ScatterType& scatter = ScatterType())
|
|
: Superclass(worklet, scatter)
|
|
{
|
|
}
|
|
|
|
VTKM_CONT
|
|
DispatcherMapTopology(const ScatterType& scatter)
|
|
: Superclass(WorkletType(), scatter)
|
|
{
|
|
}
|
|
|
|
template <typename Invocation>
|
|
VTKM_CONT void DoInvoke(Invocation& invocation) const
|
|
{
|
|
// This is the type for the input domain
|
|
using InputDomainType = typename Invocation::InputDomainType;
|
|
using SchedulingRangeType = typename WorkletType::ToTopologyType;
|
|
|
|
// If you get a compile error on this line, then you have tried to use
|
|
// something that is not a vtkm::cont::CellSet as the input domain to a
|
|
// topology operation (that operates on a cell set connection domain).
|
|
VTKM_IS_CELL_SET(InputDomainType);
|
|
|
|
// We can pull the input domain parameter (the data specifying the input
|
|
// domain) from the invocation object.
|
|
const auto& inputDomain = invocation.GetInputDomain();
|
|
|
|
// Now that we have the input domain, we can extract the range of the
|
|
// scheduling and call BadicInvoke.
|
|
this->BasicInvoke(
|
|
invocation, internal::scheduling_range(inputDomain, SchedulingRangeType{}), Device());
|
|
}
|
|
};
|
|
}
|
|
} // namespace vtkm::worklet
|
|
|
|
#endif //vtk_m_worklet_Dispatcher_MapTopology_h
|