Skip to content

Serendipity cells with 64-bit point data slice; VTK's three-axis extent on flat curvilinear grids - #350

Merged
berkgeveci merged 1 commit into
Kitware:mainfrom
berkgeveci:dataset/vtk-test-small-fixes
Nov 5, 2026
Merged

berkgeveci merged 1 commit into
Kitware:mainfrom
berkgeveci:dataset/vtk-test-small-fixes

Conversation

@berkgeveci

Copy link
Copy Markdown
Collaborator

Two small fixes found by running VTK's own Python tests with Tack's algorithms in place of VTK's filters.

  • Serendipity cells with 64-bit integer point data (quad8, hex20, wedge15): slicing or contouring them failed with 'Device' object has no attribute 'supports_f64' -- _serendipity.full_values passed the topology's device where _float_type takes a backend (it asks only for 64-bit integers). VTK's cutter.py (cuttertest.vtu's node numbers).
  • extract_extent of a flat curvilinear grid refused VTK's three-axis extent and rates: VTK always writes three, and only an image's or rectilinear grid's coordinates said which axis is flat. A curvilinear grid's flat axis is now the one whose pair is (0, 0), as VTK writes it (else the first two). VTK's NetCDFCF2DBounds.py.

Tested: a slice of each serendipity cell with a 64-bit point field (failed before), and flat curvilinear grids in the xz and xy planes against vtkExtractGrid. Files touched 202 passed; quick tier 3040 passed.

🤖 Generated with Claude Code

…nt on flat curvilinear grids

Slicing or contouring a quad8, hex20 or wedge15 carrying a 64-bit integer point
field failed: the field's full values asked a device for what a backend has.
extract_extent of a flat curvilinear grid refused VTK's three-axis extent and
rates; the flat axis is the one whose pair is (0, 0). Found running VTK's
cutter.py and NetCDFCF2DBounds.py on Tack.
@berkgeveci
berkgeveci merged commit 28b5a08 into Kitware:main Nov 5, 2026
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant