Kokkos Variant Name
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 135
- Forks
- 55
- Avg merge
- 4d 16h
- Merged PRs (30d)
- 5
Description
In implementing #615 I noticed that the Kokkos_Lambda variant may be using the Lambda part of its name a little differently than its used in the rest of the suite so filtering on it in the same way may not be what is intended. In the rest of the suite Lambda means an implementation in the baseline programming model that uses a lambda instead of whatever was used in Base. In the case of Kokkos lambda its using the kokkos programming model and kokkos is handling the backend. It might be more consistent with the rest of the suite to call this just Kokkos, or to call it something like Kokkos_Dynamic if Kokkos is dynamically deciding what backend to use based on what hardware is available. For now variant filtering with variants for Lambda will include or exclude Kokkos_Lambda.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review issue #615 and the existing variant-filtering rules for Lambda and Kokkos_Lambda. Determine which naming convention the suite should use and how filtering should treat the variant; done means the naming and filtering behavior have an agreed, consistent definition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100