5fa02057ae
Previously, all the ApplyPolicy functions had the same name and used template resolution to figure out which one to use. This was pretty clear at first when there was just one for fields and one for cell sets. But then it grew to several different types, particularly for fields. It was hard to look at the code and figure out which form of ApplyPolicy was being used, and compilers were starting to get confused. Resolve the problem by giving all the methods unique names to make it clear which one you expect to be called.
142 lines
5.1 KiB
C++
142 lines
5.1 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.
|
|
//============================================================================
|
|
|
|
#include <vtkm/filter/FieldMetadata.h>
|
|
#include <vtkm/filter/FilterTraits.h>
|
|
#include <vtkm/filter/PolicyDefault.h>
|
|
|
|
#include <vtkm/filter/internal/ResolveFieldTypeAndExecute.h>
|
|
#include <vtkm/filter/internal/ResolveFieldTypeAndMap.h>
|
|
|
|
#include <vtkm/cont/Error.h>
|
|
#include <vtkm/cont/ErrorBadAllocation.h>
|
|
#include <vtkm/cont/ErrorExecution.h>
|
|
|
|
#include <vtkm/cont/cuda/DeviceAdapterCuda.h>
|
|
#include <vtkm/cont/tbb/DeviceAdapterTBB.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace filter
|
|
{
|
|
|
|
//----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
inline VTKM_CONT FilterDataSetWithField<Derived>::FilterDataSetWithField()
|
|
: OutputFieldName()
|
|
, CoordinateSystemIndex(0)
|
|
, ActiveFieldName()
|
|
, ActiveFieldAssociation(vtkm::cont::Field::Association::ANY)
|
|
, UseCoordinateSystemAsField(false)
|
|
{
|
|
}
|
|
|
|
//----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
inline VTKM_CONT FilterDataSetWithField<Derived>::~FilterDataSetWithField()
|
|
{
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
template <typename DerivedPolicy>
|
|
inline VTKM_CONT vtkm::cont::DataSet FilterDataSetWithField<Derived>::PrepareForExecution(
|
|
const vtkm::cont::DataSet& input,
|
|
const vtkm::filter::PolicyBase<DerivedPolicy>& policy)
|
|
{
|
|
if (this->UseCoordinateSystemAsField)
|
|
{
|
|
// we need to state that the field is actually a coordinate system, so that
|
|
// the filter uses the proper policy to convert the types.
|
|
return this->PrepareForExecution(input, input.GetCoordinateSystem(), policy);
|
|
}
|
|
else
|
|
{
|
|
return this->PrepareForExecution(
|
|
input, input.GetField(this->GetActiveFieldName(), this->GetActiveFieldAssociation()), policy);
|
|
}
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
template <typename DerivedPolicy>
|
|
inline VTKM_CONT vtkm::cont::DataSet FilterDataSetWithField<Derived>::PrepareForExecution(
|
|
const vtkm::cont::DataSet& input,
|
|
const vtkm::cont::Field& field,
|
|
const vtkm::filter::PolicyBase<DerivedPolicy>& policy)
|
|
{
|
|
vtkm::filter::FieldMetadata metaData(field);
|
|
vtkm::cont::DataSet result;
|
|
|
|
vtkm::cont::CastAndCall(
|
|
vtkm::filter::ApplyPolicyFieldActive(field, policy, vtkm::filter::FilterTraits<Derived>()),
|
|
internal::ResolveFieldTypeAndExecute(),
|
|
static_cast<Derived*>(this),
|
|
input,
|
|
metaData,
|
|
policy,
|
|
result);
|
|
return result;
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
template <typename DerivedPolicy>
|
|
inline VTKM_CONT vtkm::cont::DataSet FilterDataSetWithField<Derived>::PrepareForExecution(
|
|
const vtkm::cont::DataSet& input,
|
|
const vtkm::cont::CoordinateSystem& field,
|
|
const vtkm::filter::PolicyBase<DerivedPolicy>& policy)
|
|
{
|
|
//We have a special signature just for CoordinateSystem, so that we can ask
|
|
//the policy for the storage types and value types just for coordinate systems
|
|
vtkm::filter::FieldMetadata metaData(field);
|
|
vtkm::cont::DataSet result;
|
|
|
|
//determine the field type first
|
|
using Traits = vtkm::filter::FilterTraits<Derived>;
|
|
constexpr bool supportsVec3 =
|
|
vtkm::ListContains<typename Traits::InputFieldTypeList, vtkm::Vec3f>::value;
|
|
using supportsCoordinateSystem = std::integral_constant<bool, supportsVec3>;
|
|
vtkm::cont::ConditionalCastAndCall(supportsCoordinateSystem(),
|
|
field,
|
|
internal::ResolveFieldTypeAndExecute(),
|
|
static_cast<Derived*>(this),
|
|
input,
|
|
metaData,
|
|
policy,
|
|
result);
|
|
|
|
return result;
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
template <typename DerivedPolicy>
|
|
inline VTKM_CONT bool FilterDataSetWithField<Derived>::MapFieldOntoOutput(
|
|
vtkm::cont::DataSet& result,
|
|
const vtkm::cont::Field& field,
|
|
const vtkm::filter::PolicyBase<DerivedPolicy>& policy)
|
|
{
|
|
bool valid = false;
|
|
|
|
vtkm::filter::FieldMetadata metaData(field);
|
|
using FunctorType = internal::ResolveFieldTypeAndMap<Derived, DerivedPolicy>;
|
|
FunctorType functor(static_cast<Derived*>(this), result, metaData, policy, valid);
|
|
|
|
vtkm::cont::CastAndCall(vtkm::filter::ApplyPolicyFieldNotActive(field, policy), functor);
|
|
|
|
//the bool valid will be modified by the map algorithm to hold if the
|
|
//mapping occurred or not. If the mapping was good a new field has been
|
|
//added to the result that was passed in.
|
|
return valid;
|
|
}
|
|
}
|
|
}
|