7eaedfe84b
A large portion of the VTK-m filters are now compiled into the vtkm_filter library. These pre-built filters now don't include the respective hxx file to remove the amount of template instantiation users do. To verify that this removal reduces compiler memory ( and maybe time) I profiled the compiler while it building filter tests in debug mode. Here is a selection of results: ``` CleanGrid 10.25s => 9.01s, 901MB => 795MB ExternalFaces 13.40s => 5.96s, 1122MB => 744MB ExtractStructured 4.69s => 4.75s, 492MB => 492MB GradientExplicit 22.97s => 5.88s, 1296MB => 740MB ```
81 lines
2.8 KiB
C++
81 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_filter_Threshold_h
|
|
#define vtk_m_filter_Threshold_h
|
|
|
|
#include <vtkm/filter/vtkm_filter_common_export.h>
|
|
|
|
#include <vtkm/filter/FilterDataSetWithField.h>
|
|
#include <vtkm/worklet/Threshold.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace filter
|
|
{
|
|
|
|
/// \brief Extracts cells where scalar value in cell satisfies threshold criterion
|
|
///
|
|
/// Extracts all cells from any dataset type that
|
|
/// satisfy a threshold criterion. A cell satisfies the criterion if the
|
|
/// scalar value of every point or cell satisfies the criterion. The
|
|
/// criterion takes the form of between two values. The output of this
|
|
/// filter is an permutation of the input dataset.
|
|
///
|
|
/// You can threshold either on point or cell fields
|
|
class VTKM_FILTER_COMMON_EXPORT Threshold : public vtkm::filter::FilterDataSetWithField<Threshold>
|
|
{
|
|
public:
|
|
using SupportedTypes = vtkm::TypeListScalarAll;
|
|
|
|
VTKM_CONT
|
|
void SetLowerThreshold(vtkm::Float64 value) { this->LowerValue = value; }
|
|
VTKM_CONT
|
|
void SetUpperThreshold(vtkm::Float64 value) { this->UpperValue = value; }
|
|
|
|
VTKM_CONT
|
|
vtkm::Float64 GetLowerThreshold() const { return this->LowerValue; }
|
|
VTKM_CONT
|
|
vtkm::Float64 GetUpperThreshold() const { return this->UpperValue; }
|
|
|
|
template <typename T, typename StorageType, typename DerivedPolicy>
|
|
VTKM_CONT vtkm::cont::DataSet DoExecute(const vtkm::cont::DataSet& input,
|
|
const vtkm::cont::ArrayHandle<T, StorageType>& field,
|
|
const vtkm::filter::FieldMetadata& fieldMeta,
|
|
vtkm::filter::PolicyBase<DerivedPolicy> policy);
|
|
|
|
//Map a new field onto the resulting dataset after running the filter
|
|
//this call is only valid after DoExecute is called
|
|
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:
|
|
double LowerValue = 0;
|
|
double UpperValue = 0;
|
|
vtkm::worklet::Threshold Worklet;
|
|
};
|
|
|
|
#ifndef vtkm_filter_Threshold_cxx
|
|
VTKM_FILTER_COMMON_EXPORT_EXECUTE_METHOD(Threshold);
|
|
#endif
|
|
}
|
|
} // namespace vtkm::filter
|
|
|
|
#include <vtkm/filter/Threshold.hxx>
|
|
|
|
#endif // vtk_m_filter_Threshold_h
|