964ef29e06
There was a case where a VTK-m exception was caught and then used in a logging message. That is fine, but if VTK-m logging is turned off, that code is removed and the exception variable goes unused. There was a time when it was common to have logging turned off in VTK-m, but now it is almost always on. There is one old-style dashboard that has logging turned off and is giving a warning about this variable not being used. It went unnoticed because the dashboard was down at the time. This should fix the issue.
83 lines
2.7 KiB
C++
83 lines
2.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.
|
|
//============================================================================
|
|
|
|
#include <vtkm/filter/FieldMetadata.h>
|
|
#include <vtkm/filter/FilterTraits.h>
|
|
#include <vtkm/filter/PolicyDefault.h>
|
|
|
|
#include <vtkm/cont/ErrorBadType.h>
|
|
#include <vtkm/cont/Logging.h>
|
|
|
|
#include <vtkm/filter/internal/ResolveFieldTypeAndExecute.h>
|
|
#include <vtkm/filter/internal/ResolveFieldTypeAndMap.h>
|
|
|
|
namespace vtkm
|
|
{
|
|
namespace filter
|
|
{
|
|
|
|
//----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
inline VTKM_CONT FilterDataSet<Derived>::FilterDataSet()
|
|
: CoordinateSystemIndex(0)
|
|
{
|
|
}
|
|
|
|
//----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
inline VTKM_CONT FilterDataSet<Derived>::~FilterDataSet()
|
|
{
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
template <typename DerivedPolicy>
|
|
inline VTKM_CONT vtkm::cont::DataSet FilterDataSet<Derived>::PrepareForExecution(
|
|
const vtkm::cont::DataSet& input,
|
|
vtkm::filter::PolicyBase<DerivedPolicy> policy)
|
|
{
|
|
return (static_cast<Derived*>(this))->DoExecute(input, policy);
|
|
}
|
|
|
|
//-----------------------------------------------------------------------------
|
|
template <typename Derived>
|
|
template <typename DerivedPolicy>
|
|
inline VTKM_CONT bool FilterDataSet<Derived>::MapFieldOntoOutput(
|
|
vtkm::cont::DataSet& result,
|
|
const vtkm::cont::Field& field,
|
|
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);
|
|
|
|
try
|
|
{
|
|
vtkm::cont::CastAndCall(vtkm::filter::ApplyPolicyFieldNotActive(field, policy), functor);
|
|
}
|
|
catch (vtkm::cont::ErrorBadType& error)
|
|
{
|
|
VTKM_LOG_S(vtkm::cont::LogLevel::Warn,
|
|
"Failed to map field " << field.GetName()
|
|
<< " because it is an unknown type. Cast error:\n"
|
|
<< error.GetMessage());
|
|
(void)error; // Suppress unused error message if logging is turned off.
|
|
}
|
|
|
|
//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;
|
|
}
|
|
}
|
|
}
|