72cd0107ee
The version of `Filter::Execute` that takes a policy as an argument is now deprecated. Filters are now able to specify their own fields and types, which is often why you want to customize the policy for an execution. The other reason is that you are compiling VTK-m into some other source that uses a particular types of storage. However, there is now a mechanism in the CMake configuration to allow you to provide a header that customizes the "default" types used in filters. This is a much more convenient way to compile filters for specific types. One thing that filters were not able to do was to customize what cell sets they allowed using. This allows filters to self-select what types of cell sets they support (beyond simply just structured or unstructured). To support this, the lists `SupportedCellSets`, `SupportedStructuredCellSets`, and `SupportedUnstructuredCellSets` have been added to `Filter`. When you apply a policy to a cell set, you now have to also provide the filter.
71 lines
2.1 KiB
C++
71 lines
2.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.
|
|
//============================================================================
|
|
#define vtkm_filter_ExternalFaces_cxx
|
|
#include <vtkm/filter/ExternalFaces.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace filter
|
|
{
|
|
|
|
//-----------------------------------------------------------------------------
|
|
ExternalFaces::ExternalFaces()
|
|
: vtkm::filter::FilterDataSet<ExternalFaces>()
|
|
, CompactPoints(false)
|
|
, Worklet()
|
|
{
|
|
this->SetPassPolyData(true);
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
vtkm::cont::DataSet ExternalFaces::GenerateOutput(const vtkm::cont::DataSet& input,
|
|
vtkm::cont::CellSetExplicit<>& outCellSet)
|
|
{
|
|
//This section of ExternalFaces is independent of any input so we can build it
|
|
//into the vtkm_filter library
|
|
|
|
//3. Check the fields of the dataset to see what kinds of fields are present so
|
|
// we can free the cell mapping array if it won't be needed.
|
|
const vtkm::Id numFields = input.GetNumberOfFields();
|
|
bool hasCellFields = false;
|
|
for (vtkm::Id fieldIdx = 0; fieldIdx < numFields && !hasCellFields; ++fieldIdx)
|
|
{
|
|
auto f = input.GetField(fieldIdx);
|
|
hasCellFields = f.IsFieldCell();
|
|
}
|
|
|
|
if (!hasCellFields)
|
|
{
|
|
this->Worklet.ReleaseCellMapArrays();
|
|
}
|
|
|
|
//4. create the output dataset
|
|
vtkm::cont::DataSet output;
|
|
output.SetCellSet(outCellSet);
|
|
output.AddCoordinateSystem(input.GetCoordinateSystem(this->GetActiveCoordinateSystemIndex()));
|
|
|
|
if (this->CompactPoints)
|
|
{
|
|
this->Compactor.SetCompactPointFields(true);
|
|
this->Compactor.SetMergePoints(false);
|
|
return this->Compactor.Execute(output);
|
|
}
|
|
else
|
|
{
|
|
return output;
|
|
}
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
VTKM_FILTER_INSTANTIATE_EXECUTE_METHOD(ExternalFaces);
|
|
}
|
|
}
|