Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK-m VTK-m
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 194
    • Issues 194
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTK-mVTK-m
  • Merge requests
  • !758

Make VirtualObjectCache more generic

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Kenneth Moreland requested to merge kmorel/vtk-m:generic-virtual-object-transfer into master May 04, 2017
  • Overview 4
  • Commits 2
  • Pipelines 2
  • Changes 20

Rather than require every implementation of a DeviceAdapter to implement their own version of VirtualObjectCache, make a generic version that leverages the already existing ArrayManagerExecution to transfer data to the device.

These changes implicitly require the ArrayManagerExecution to provide an ArrayPortal for the execution environment that returns a reference from the Get method (so long as the ArrayPortal for the control environment does the same thing). So far this has been straightforward to implement.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: generic-virtual-object-transfer