Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 830
    • Issues 830
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 232
    • Merge requests 232
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #17906
Closed
Open
Issue created May 22, 2020 by Yohann Bearzi@yohann.bearziDeveloper

`vtkHyperTree` global index refactoring

There are 2 ways to index data in a vtkHyperTree.

  • Explicit indexing: activated by calling SetGlobalIndexFromLocal
  • Implicit indexing: activated by calling SetGlobalIndexStart

If one calls one of those 2 methods, then the getter of the other indexing method crashes because of an assert. The design is flawed: you should be able to instantiate one version or another, and not be able to change its behavior at run-time. The solution to this is to do that by inheritance, having for example a vtkExplicitHyperTree and a vtkImplicitHyperTree implementations inheriting from abstract class vtkHyperTree.

Edited May 22, 2020 by Yohann Bearzi
Assignee
Assign to
Time tracking