Skip to content

GitLab

  • Menu
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 739
    • Issues 739
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 199
    • Merge requests 199
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

An update will be applied May 24th, between 12PM and 1PM EDT (UTC -400). The site may be slow during that time.

  • VTK
  • VTKVTK
  • Issues
  • #17565

Closed
Open
Created Apr 02, 2019 by Lutz Hofmann@lhofmannContributor

numpy_to_vtk converts unsigned long into unsigned long long

I'm not sure if this is intended behavior:

from vtkmodules.vtkCommonCore import vtkUnsignedLongArray
from vtkmodules.util.numpy_support import vtk_to_numpy, numpy_to_vtk

print(numpy_to_vtk(vtk_to_numpy(vtk.vtkUnsignedLongArray())))  # prints vtkUnsignedLongLongArray

Looking at numpy_support.py, get_vtk_to_numpy_typemap depends on the system's data type sizes, but get_vtk_array_type does not.

Assignee
Assign to
Time tracking