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 186
    • Issues 186
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 38
    • Merge requests 38
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • 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
  • !53

Merged
Created Jun 22, 2015 by Robert Maynard@robertmaynardContributor

Allow invocation of worklets to use vtkm::Id3

  • Overview 4
  • Commits 3
  • Changes

@kmorel, @jsmeredith, @dpugmire

This allow invocation of worklets whose input domain is regular connectivity to be scheduled use the DeviceAdapters Schedule(vtkm::Id3) method.

This is just the first step in having efficient 3d scheduling. The next step is to upgrade all the vtkm::exec::arg to support Id3 index's for the load and store methods.

Note: I would love somebody to suggest a better name for GetSchedulingDimensions

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 3dScheduling