afd394377e
There is a limitation in Windows builds using VS2019 where libraries cannot be
bigger than 4GiB. This is normally not an issue but in `VTKm` due to its strong
template usage libraries can reach that size.
The `VTKm` filter library is can easily reach that size and it will halt the
build
This MR tries to avoid reaching those sizes for now by splitting the filter
library into four smaller libraries.
The proposal scheme is:
It splits vtkm-filter into:
- vtkm-common, Classes that are dependencies of other filter libs.
- vtkm-contour, Contour class and its instantiations.
- vtkm-contour, Gradient class and its instantiations.
- vtkm-extra, Classes other than Contour or Gradient that are
not dependencies.
Signed-off-by: Vicente Adolfo Bolea Sanchez <vicente.bolea@kitware.com>
115 lines
4.0 KiB
C++
115 lines
4.0 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_filter_ExtractGeometry_h
|
|
#define vtk_m_filter_ExtractGeometry_h
|
|
|
|
#include <vtkm/filter/vtkm_filter_common_export.h>
|
|
|
|
#include <vtkm/cont/ImplicitFunctionHandle.h>
|
|
#include <vtkm/filter/FilterDataSet.h>
|
|
#include <vtkm/worklet/ExtractGeometry.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace filter
|
|
{
|
|
|
|
/// \brief Extract a subset of geometry based on an implicit function
|
|
///
|
|
/// Extracts from its input geometry all cells that are either
|
|
/// completely inside or outside of a specified implicit function. Any type of
|
|
/// data can be input to this filter.
|
|
///
|
|
/// To use this filter you must specify an implicit function. You must also
|
|
/// specify whether to extract cells laying inside or outside of the implicit
|
|
/// function. (The inside of an implicit function is the negative values
|
|
/// region.) An option exists to extract cells that are neither inside or
|
|
/// outside (i.e., boundary).
|
|
///
|
|
/// This differs from Clip in that Clip will subdivide boundary cells into new
|
|
/// cells, while this filter will not, producing a more 'crinkly' output.
|
|
///
|
|
class VTKM_ALWAYS_EXPORT ExtractGeometry : public vtkm::filter::FilterDataSet<ExtractGeometry>
|
|
{
|
|
public:
|
|
//currently the ExtractGeometry filter only works on scalar data.
|
|
using SupportedTypes = TypeListScalarAll;
|
|
|
|
VTKM_FILTER_COMMON_EXPORT VTKM_CONT ExtractGeometry();
|
|
|
|
// Set the volume of interest to extract
|
|
void SetImplicitFunction(const vtkm::cont::ImplicitFunctionHandle& func)
|
|
{
|
|
this->Function = func;
|
|
}
|
|
|
|
const vtkm::cont::ImplicitFunctionHandle& GetImplicitFunction() const { return this->Function; }
|
|
|
|
VTKM_CONT
|
|
bool GetExtractInside() { return this->ExtractInside; }
|
|
VTKM_CONT
|
|
void SetExtractInside(bool value) { this->ExtractInside = value; }
|
|
VTKM_CONT
|
|
void ExtractInsideOn() { this->ExtractInside = true; }
|
|
VTKM_CONT
|
|
void ExtractInsideOff() { this->ExtractInside = false; }
|
|
|
|
VTKM_CONT
|
|
bool GetExtractBoundaryCells() { return this->ExtractBoundaryCells; }
|
|
VTKM_CONT
|
|
void SetExtractBoundaryCells(bool value) { this->ExtractBoundaryCells = value; }
|
|
VTKM_CONT
|
|
void ExtractBoundaryCellsOn() { this->ExtractBoundaryCells = true; }
|
|
VTKM_CONT
|
|
void ExtractBoundaryCellsOff() { this->ExtractBoundaryCells = false; }
|
|
|
|
VTKM_CONT
|
|
bool GetExtractOnlyBoundaryCells() { return this->ExtractOnlyBoundaryCells; }
|
|
VTKM_CONT
|
|
void SetExtractOnlyBoundaryCells(bool value) { this->ExtractOnlyBoundaryCells = value; }
|
|
VTKM_CONT
|
|
void ExtractOnlyBoundaryCellsOn() { this->ExtractOnlyBoundaryCells = true; }
|
|
VTKM_CONT
|
|
void ExtractOnlyBoundaryCellsOff() { this->ExtractOnlyBoundaryCells = false; }
|
|
|
|
template <typename DerivedPolicy>
|
|
vtkm::cont::DataSet DoExecute(const vtkm::cont::DataSet& input,
|
|
const vtkm::filter::PolicyBase<DerivedPolicy>& policy);
|
|
|
|
VTKM_FILTER_COMMON_EXPORT VTKM_CONT bool MapFieldOntoOutput(vtkm::cont::DataSet& result,
|
|
const vtkm::cont::Field& field);
|
|
|
|
template <typename DerivedPolicy>
|
|
VTKM_CONT bool MapFieldOntoOutput(vtkm::cont::DataSet& result,
|
|
const vtkm::cont::Field& field,
|
|
vtkm::filter::PolicyBase<DerivedPolicy>)
|
|
{
|
|
return this->MapFieldOntoOutput(result, field);
|
|
}
|
|
|
|
private:
|
|
bool ExtractInside;
|
|
bool ExtractBoundaryCells;
|
|
bool ExtractOnlyBoundaryCells;
|
|
vtkm::cont::ImplicitFunctionHandle Function;
|
|
vtkm::worklet::ExtractGeometry Worklet;
|
|
};
|
|
|
|
#ifndef vtkm_filter_ExtractGeometry_cxx
|
|
VTKM_FILTER_EXPORT_EXECUTE_METHOD(ExtractGeometry);
|
|
#endif
|
|
}
|
|
} // namespace vtkm::filter
|
|
|
|
#include <vtkm/filter/ExtractGeometry.hxx>
|
|
|
|
#endif // vtk_m_filter_ExtractGeometry_h
|