Shuenhoy/vtk-m
1
0
Fork 0
mirror of https://gitlab.kitware.com/vtk/vtk-m synced 2024-09-08 13:23:51 +00:00
Code Issues 2 Actions Packages Projects Releases Wiki Activity
81522be6f7
vtk-m/vtkm/rendering/raytracing/MeshConnectivityContainers.cxx

174 lines
5.5 KiB
C++
Raw Normal View History

adding more ray tracing files
2018-09-11 02:51:45 +00:00
//============================================================================
// Copyright (c) Kitware, Inc.
// All rights reserved.
// See LICENSE.txt for details.
conslidate the license statement
2019-04-15 23:24:21 +00:00
//
adding more ray tracing files
2018-09-11 02:51:45 +00:00
// 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 <sstream>
#include <vtkm/CellShape.h>
#include <vtkm/cont/ErrorBadValue.h>
#include <vtkm/cont/Timer.h>
#include <vtkm/cont/internal/DeviceAdapterListHelpers.h>
#include <vtkm/rendering/raytracing/BoundingVolumeHierarchy.h>
#include <vtkm/rendering/raytracing/Logger.h>
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
#include <vtkm/rendering/raytracing/MeshConnectivity.h>
adding more ray tracing files
2018-09-11 02:51:45 +00:00
#include <vtkm/rendering/raytracing/MeshConnectivityContainers.h>
#include <vtkm/rendering/raytracing/Ray.h>
#include <vtkm/rendering/raytracing/TriangleIntersector.h>
namespace vtkm
{
namespace rendering
{
namespace raytracing
{
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivityContainer::MeshConnectivityContainer(){};
MeshConnectivityContainer::~MeshConnectivityContainer(){};
adding more ray tracing files
2018-09-11 02:51:45 +00:00
template <typename T>
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
VTKM_CONT void MeshConnectivityContainer::FindEntryImpl(Ray<T>& rays)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
bool getCellIndex = true;
Intersector.SetUseWaterTight(true);
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
Intersector.IntersectRays(rays, getCellIndex);
}
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
void MeshConnectivityContainer::FindEntry(Ray<vtkm::Float32>& rays)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
this->FindEntryImpl(rays);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
void MeshConnectivityContainer::FindEntry(Ray<vtkm::Float64>& rays)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
this->FindEntryImpl(rays);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
VTKM_CONT
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivityContainerUnstructured::MeshConnectivityContainerUnstructured(
const vtkm::cont::CellSetExplicit<>& cellset,
const vtkm::cont::CoordinateSystem& coords,
const IdHandle& faceConn,
const IdHandle& faceOffsets,
const Id4Handle& triangles)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
: FaceConnectivity(faceConn)
, FaceOffsets(faceOffsets)
, Cellset(cellset)
, Coords(coords)
{
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
this->Triangles = triangles;
adding more ray tracing files
2018-09-11 02:51:45 +00:00
//
// Grab the cell arrays
//
CellConn =
Refactor topology mappings to clarify meaning. The `From` and `To` nomenclature for topology mapping has been confusing for both users and developers, especially at lower levels where the intention of mapping attributes from one element to another is easily conflated with the concept of mapping indices (which maps in the exact opposite direction). These identifiers have been renamed to `VisitTopology` and `IncidentTopology` to clarify the direction of the mapping. The order in which these template parameters are specified for `WorkletMapTopology` have also been reversed, since eventually there may be more than one `IncidentTopology`, and having `IncidentTopology` at the end will allow us to replace it with a variadic template parameter pack in the future. Other implementation details supporting these worklets, include `Fetch` tags, `Connectivity` classes, and methods on the various `CellSet` classes (such as `PrepareForInput` have also reversed their template arguments. These will need to be cautiously updated. The convenience implementations of `WorkletMapTopology` have been renamed for clarity as follows: ``` WorkletMapPointToCell --> WorkletVisitCellsWithPoints WorkletMapCellToPoint --> WorkletVisitPointsWithCells ``` The `ControlSignature` tags have been renamed as follows: ``` FieldInTo --> FieldInVisit FieldInFrom --> FieldInMap FromCount --> IncidentElementCount FromIndices --> IncidentElementIndices ```
2019-07-30 16:53:51 +00:00
Cellset.GetConnectivityArray(vtkm::TopologyElementTagCell(), vtkm::TopologyElementTagPoint());
adding more ray tracing files
2018-09-11 02:51:45 +00:00
CellOffsets =
Refactor CellSetExplicit to remove NumIndices. See #408 for details.
2019-08-30 17:04:17 +00:00
Cellset.GetOffsetsArray(vtkm::TopologyElementTagCell(), vtkm::TopologyElementTagPoint());
Refactor topology mappings to clarify meaning. The `From` and `To` nomenclature for topology mapping has been confusing for both users and developers, especially at lower levels where the intention of mapping attributes from one element to another is easily conflated with the concept of mapping indices (which maps in the exact opposite direction). These identifiers have been renamed to `VisitTopology` and `IncidentTopology` to clarify the direction of the mapping. The order in which these template parameters are specified for `WorkletMapTopology` have also been reversed, since eventually there may be more than one `IncidentTopology`, and having `IncidentTopology` at the end will allow us to replace it with a variadic template parameter pack in the future. Other implementation details supporting these worklets, include `Fetch` tags, `Connectivity` classes, and methods on the various `CellSet` classes (such as `PrepareForInput` have also reversed their template arguments. These will need to be cautiously updated. The convenience implementations of `WorkletMapTopology` have been renamed for clarity as follows: ``` WorkletMapPointToCell --> WorkletVisitCellsWithPoints WorkletMapCellToPoint --> WorkletVisitPointsWithCells ``` The `ControlSignature` tags have been renamed as follows: ``` FieldInTo --> FieldInVisit FieldInFrom --> FieldInMap FromCount --> IncidentElementCount FromIndices --> IncidentElementIndices ```
2019-07-30 16:53:51 +00:00
Shapes = Cellset.GetShapesArray(vtkm::TopologyElementTagCell(), vtkm::TopologyElementTagPoint());
adding more ray tracing files
2018-09-11 02:51:45 +00:00
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
Intersector.SetData(Coords, Triangles);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivityContainerUnstructured::~MeshConnectivityContainerUnstructured(){};
adding more ray tracing files
2018-09-11 02:51:45 +00:00
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivity MeshConnectivityContainerUnstructured::PrepareForExecution(
vtkm::cont::DeviceAdapterId deviceId,
vtkm::cont::Token& token) const
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
return MeshConnectivity(this->FaceConnectivity,
this->FaceOffsets,
this->CellConn,
this->CellOffsets,
this->Shapes,
deviceId,
token);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
VTKM_CONT
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivityContainerSingleType::MeshConnectivityContainerSingleType(
adding more ray tracing files
2018-09-11 02:51:45 +00:00
const vtkm::cont::CellSetSingleType<>& cellset,
const vtkm::cont::CoordinateSystem& coords,
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
const IdHandle& faceConn,
const Id4Handle& triangles)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
: FaceConnectivity(faceConn)
, Coords(coords)
, Cellset(cellset)
{
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
this->Triangles = triangles;
adding more ray tracing files
2018-09-11 02:51:45 +00:00
this->Intersector.SetUseWaterTight(true);
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->CellConnectivity =
Refactor topology mappings to clarify meaning. The `From` and `To` nomenclature for topology mapping has been confusing for both users and developers, especially at lower levels where the intention of mapping attributes from one element to another is easily conflated with the concept of mapping indices (which maps in the exact opposite direction). These identifiers have been renamed to `VisitTopology` and `IncidentTopology` to clarify the direction of the mapping. The order in which these template parameters are specified for `WorkletMapTopology` have also been reversed, since eventually there may be more than one `IncidentTopology`, and having `IncidentTopology` at the end will allow us to replace it with a variadic template parameter pack in the future. Other implementation details supporting these worklets, include `Fetch` tags, `Connectivity` classes, and methods on the various `CellSet` classes (such as `PrepareForInput` have also reversed their template arguments. These will need to be cautiously updated. The convenience implementations of `WorkletMapTopology` have been renamed for clarity as follows: ``` WorkletMapPointToCell --> WorkletVisitCellsWithPoints WorkletMapCellToPoint --> WorkletVisitPointsWithCells ``` The `ControlSignature` tags have been renamed as follows: ``` FieldInTo --> FieldInVisit FieldInFrom --> FieldInMap FromCount --> IncidentElementCount FromIndices --> IncidentElementIndices ```
2019-07-30 16:53:51 +00:00
Cellset.GetConnectivityArray(vtkm::TopologyElementTagCell(), vtkm::TopologyElementTagPoint());
adding more ray tracing files
2018-09-11 02:51:45 +00:00
vtkm::cont::ArrayHandleConstant<vtkm::UInt8> shapes =
Refactor topology mappings to clarify meaning. The `From` and `To` nomenclature for topology mapping has been confusing for both users and developers, especially at lower levels where the intention of mapping attributes from one element to another is easily conflated with the concept of mapping indices (which maps in the exact opposite direction). These identifiers have been renamed to `VisitTopology` and `IncidentTopology` to clarify the direction of the mapping. The order in which these template parameters are specified for `WorkletMapTopology` have also been reversed, since eventually there may be more than one `IncidentTopology`, and having `IncidentTopology` at the end will allow us to replace it with a variadic template parameter pack in the future. Other implementation details supporting these worklets, include `Fetch` tags, `Connectivity` classes, and methods on the various `CellSet` classes (such as `PrepareForInput` have also reversed their template arguments. These will need to be cautiously updated. The convenience implementations of `WorkletMapTopology` have been renamed for clarity as follows: ``` WorkletMapPointToCell --> WorkletVisitCellsWithPoints WorkletMapCellToPoint --> WorkletVisitPointsWithCells ``` The `ControlSignature` tags have been renamed as follows: ``` FieldInTo --> FieldInVisit FieldInFrom --> FieldInMap FromCount --> IncidentElementCount FromIndices --> IncidentElementIndices ```
2019-07-30 16:53:51 +00:00
Cellset.GetShapesArray(vtkm::TopologyElementTagCell(), vtkm::TopologyElementTagPoint());
adding more ray tracing files
2018-09-11 02:51:45 +00:00
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->ShapeId = shapes.ReadPortal().Get(0);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
CellTables tables;
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->NumIndices = tables.FaceLookUp(tables.CellTypeLookUp(ShapeId), 2);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
if (this->NumIndices == 0)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
std::stringstream message;
message << "Unstructured Mesh Connecitity Single type Error: unsupported cell type: ";
message << ShapeId;
throw vtkm::cont::ErrorBadValue(message.str());
}
vtkm::Id start = 0;
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->NumFaces = tables.FaceLookUp(tables.CellTypeLookUp(this->ShapeId), 1);
vtkm::Id numCells = this->CellConnectivity.ReadPortal().GetNumberOfValues();
this->CellOffsets =
vtkm::cont::make_ArrayHandleCounting<vtkm::Id>(start, this->NumIndices, numCells);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
Logger* logger = Logger::GetInstance();
logger->OpenLogEntry("mesh_conn_construction");
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->Intersector.SetData(Coords, Triangles);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivity MeshConnectivityContainerSingleType::PrepareForExecution(
vtkm::cont::DeviceAdapterId deviceId,
vtkm::cont::Token& token) const
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
return MeshConnectivity(this->FaceConnectivity,
this->CellConnectivity,
this->CellOffsets,
this->ShapeId,
this->NumIndices,
this->NumFaces,
deviceId,
token);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivityContainerStructured::MeshConnectivityContainerStructured(
const vtkm::cont::CellSetStructured<3>& cellset,
const vtkm::cont::CoordinateSystem& coords,
const Id4Handle& triangles)
adding more ray tracing files
2018-09-11 02:51:45 +00:00
: Coords(coords)
, Cellset(cellset)
{
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->Triangles = triangles;
this->Intersector.SetUseWaterTight(true);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
this->PointDims = this->Cellset.GetPointDimensions();
this->CellDims = this->Cellset.GetCellDimensions();
adding more ray tracing files
2018-09-11 02:51:45 +00:00
updates to the connectivity tracer
2018-10-30 14:46:42 +00:00
this->Intersector.SetData(Coords, Triangles);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
MeshConnectivity MeshConnectivityContainerStructured::PrepareForExecution(
vtkm::cont::DeviceAdapterId,
vtkm::cont::Token&) const
adding more ray tracing files
2018-09-11 02:51:45 +00:00
{
Remove virtual methods from MeshConnectivity in rendering Virtual methods were used in the `MeshConnectivity` classes for the internal ray casting system. However, using virtual methods in the execution environment is being deprecated. This change replaces the virtual object with an object containing a `Variant`. The `Variant` holds one of the supported mesh connectivities and selects the correct one at runtime rather than jumping into a virtual method.
2021-04-09 17:05:22 +00:00
return MeshConnectivity(CellDims, PointDims);
adding more ray tracing files
2018-09-11 02:51:45 +00:00
}
}
}
} //namespace vtkm::rendering::raytracing
Reference in New Issue Copy Permalink