Extend blue noise dithering from 2D patterns to 4D patterns
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 32/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- cpp
- Domain
- computer-graphics
Research direction
No files, tests, or entry points are named. Start by locating the existing 2D spatial blue-noise dithering and Z-Order dithering implementations, then study how the primary-sample-space patterns are optimized and evaluated. Done means extending the blue-noise properties across all four dimensions without degrading 2D quality or within-pixel convergence.
Written by the indexing model from the issue text.
Description
For each 4D pattern in primary sample space, currently only the first 2 dimensions have spatial blue noise dithering between pixels. Ideally the blue noise properties would be present across the whole 4D pattern. This shortcoming was identified after user testing and gathering feedback, with clearly sub-par results shown.
Z-Order dithering was tested, which does stratify across all 4 dimensions. However, this method is not progressive. First attempts to make the method progressive were not successful as these lead to a reduction in quality of the original sample pattern and its convergence rate within a pixel.
Based on this, we believe the best approach is to continue using a priori / offline optimization approach, but extend this to optimize across 4D. Given the additional constraints on the optimization process, it's expected that a naive approach will reduce the quality of the results for 2D. So further exploration is required.
- Dominant language
- C++
- Stars
- 106
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from AcademySoftwareFoundation/openqmc
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 57/100
AcademySoftwareFoundation/openqmc#117 · 2 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
AcademySoftwareFoundation/openqmc#100 · 2 comments ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Add C-ABI to provide an ABI stable interface and improve compatibilityPossibly taken @joshbainbridge claimed this 138 days ago. Openenhancement
AcademySoftwareFoundation/openqmc#87 · 1 assignee ·
All issues in AcademySoftwareFoundation/openqmc
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
google/tensorstore#306 ·
-
comp-formats
Difficulty 2/5 Half a day Newbie friendliness 64/100
ClickHouse/ClickHouse#131694 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ETSInitiative/PETSIRD#243 ·
Maintainers usually reply within 1 day
-
[BUG][Ascend][AscendC] Scalar FP8 arithmetic stored to UB emits ".data" on a float and fails deviceOpenascend bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 2 days
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day