Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions changelog.d/flying-edges.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
### Changed

- `contour` of a structured grid of solid cells -- an image, a rectilinear or a
curvilinear grid -- with a point field goes by flying edges, as VTK's
`vtkFlyingEdges3D`: crossings counted along the grid's rows, numbered by a
scan and written once, with no per-corner arrays and no sort. The triangles,
points and carried values are the general path's, bit for bit, up to their
order. On an 11M-cell image at ten values (CPU, M1 Max) the peak above the
input fell from 2.24 to 0.32 GB and the time from 259 to 219 ms; on an
80M-cell image at two values, from 1.32 to 0.30 GB and 346 to 263 ms (#316).
Hidden and refined cells (an AMR box's) are left out in place: before, the
rest were extracted into unstructured cells first. A 2D structured grid's
contour lines go by flying edges too, the same lines as the general path,
their orientation included: on a 4096^2 image at ten values the peak above
the input fell from 14.1 to 0.18 GB, at one value from 2.01 to 0.02 GB and
from 53 to 33 ms.
- `slice` of an image or a rectilinear grid by a `Plane` (`slice_plane`) goes
by a plane cutter, as VTK's `vtkFlyingEdgesPlaneCutter`: flying edges over
each row's stretch near the plane, found from the plane's equation, the
distance computed where it is read. Only the cells near the plane are
visited and nothing is stored for the others; the output is the general
path's, bit for bit, up to its order. A plane through a 432^3 image (80M
cells, CPU, M1 Max) took 177 ms and 0.71 GB above the input; it takes 14 ms
and 0.03 GB. A curvilinear grid's planes visit every row, the distance still
computed where read (a 256^3 grid: 47 to 7 ms), and hidden and refined cells
are left out in place (an image of 256^3 with a tenth refined: 116 ms and
1.49 GB to 12 ms and 0.01 GB).
4 changes: 2 additions & 2 deletions docs/vis-guide/reference/algorithms.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,9 +92,9 @@ New datasets of pieces of cells, with points made on their edges.

| Algorithm | Gives | Takes | VTK | Viskores |
|---|---|---|---|---|
| [`contour`](#tack.dataset.algorithms.contour.contour) | isosurfaces, isolines or points of a field, one level or several | dataset | vtkContourFilter | Contour |
| [`contour`](#tack.dataset.algorithms.contour.contour) | isosurfaces, isolines or points of a field, one level or several | dataset | vtkContourFilter, vtkFlyingEdges3D | Contour, ContourFlyingEdges |
| [`slice`](#tack.dataset.algorithms.slice.slice) | where an implicit function is zero (or a level) | dataset | vtkCutter | Slice |
| [`slice_plane`](#tack.dataset.algorithms.slice.slice_plane) | a plane's cut, or parallel planes | dataset | vtkCutter | Slice |
| [`slice_plane`](#tack.dataset.algorithms.slice.slice_plane) | a plane's cut, or parallel planes | dataset | vtkCutter, vtkFlyingEdgesPlaneCutter | Slice |
| [`clip`](#tack.dataset.algorithms.clip.clip) | the part above (or below) a field's level or inside an implicit function | dataset | vtkTableBasedClipDataSet | ClipWithField, ClipWithImplicitFunction |

::: tack.dataset.algorithms.contour.contour
Expand Down
Loading
Loading