Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MDRangePolicy and tagged evaluators #547

Closed
bathmatt opened this issue Nov 18, 2016 · 2 comments
Closed

MDRangePolicy and tagged evaluators #547

bathmatt opened this issue Nov 18, 2016 · 2 comments
Assignees
Labels
Enhancement Improve existing capability; will potentially require voting

Comments

@bathmatt
Copy link

Is there a way to tag a functor in a MD range policy? I have tried

using range_type = MDRangePolicy< DeviceSpace, Rank<2>, Kokkos::IndexType, Tag >;

then in my functor
operator() (Tag, i,j )...
but that doesn't seem to work.

@dsunder
Copy link
Contributor

dsunder commented Nov 18, 2016

Nathan has a version in a branch on his fork that allows tagging functors…we’re planning on doing a code review next week and pushing the changes to develop.

--Dan

From: bathmatt notifications@github.com
Reply-To: kokkos/kokkos reply@reply.github.com
Date: Friday, November 18, 2016 at 10:16
To: kokkos/kokkos kokkos@noreply.github.com
Subject: [EXTERNAL] [kokkos/kokkos] MDRagePolicy and tagged evaluators (#547)

Is there a way to tag a functor in a MD range policy? I have tried

using range_type = MDRangePolicy< DeviceSpace, Rank<2>, Kokkos::IndexType, Tag >;

then in my functor
operator() (Tag, i,j )...
but that doesn't seem to work.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com//issues/547, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIMHEpGEl4qO5TVOPQsiaIu2XDeJjk9rks5q_d2IgaJpZM4K2t4I.

@mhoemmen mhoemmen changed the title MDRagePolicy and tagged evaluators MDRangePolicy and tagged evaluators Nov 18, 2016
@hcedwar hcedwar added the Enhancement Improve existing capability; will potentially require voting label Jan 11, 2017
@hcedwar hcedwar added this to the Backlog milestone Jan 11, 2017
@hcedwar
Copy link
Contributor

hcedwar commented Jan 11, 2017

related to issue #52

@crtrott crtrott modified the milestones: 2017-April-end, Backlog Mar 22, 2017
@crtrott crtrott closed this as completed Apr 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement Improve existing capability; will potentially require voting
Projects
None yet
Development

No branches or pull requests

5 participants