opencl question
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 839
- Forks
- 220
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 14
Description
What's the priority for opencl versions of functions? Are we supposed to add them with the non-opencl version? For patches/fixes to functions, we should also patch/fix the opencl version. I know this adds to development debt and I have never touched opencl versions. Is there a way that we can keep track of changes that occur in the non-opencl functions where we probably need to update the opencl version?
In some ways, I think it would be better to have a stan-math-gpu library to keep track off all these changes and keep stan-math as it is. Though this suggestion is a bigger conversation.
@syclik @rok-cesnovar @bob-carpenter @WardBrian
Contributor guide
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
No file, test, or entry point is named. Start by reading the issue discussion and comparing how the repository organizes non-OpenCL and OpenCL function versions; done requires an agreed policy for tracking changes and deciding whether a separate stan-math-gpu library is warranted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100