OptiX 8.1 Code Differences
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.4k
- Forks
- 249
- PR merge metrics
- No merged PRs in 30d
Description
@LegNeato I've installed OptiX 8.1. After generating the code, there are significant differences compared to the current code. I'm wondering if it's still necessary to maintain a ray tracing sub project within the main CUDA project. Alternatively, should I consider moving it to a dedicated "rust-optix" project so that we can focus more on the relevant issues?
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
Start by comparing the OptiX 8.1 generated code with the current ray-tracing code and reviewing how that subproject fits within the main CUDA project. Determine whether the ray-tracing work should remain in rust-cuda or move to a dedicated rust-optix project; done means the project structure decision and its scope are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100