Using itk::VectorImage instead of itk::Image<Vector<...
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- computer-vision
Research direction
Start by locating the uses of itk::Image and itk::Dream3DImage that restrict vector components to dimensions 2 and 3. Trace the related image-processing entry points and tests, then define the scope and validation needed for itk::VectorImage to support arbitrary vector dimensions.
Written by the indexing model from the issue text.
Description
Using itk::VectorImage instead of itk::Image (and the corresponding itk::Dream3DImage) with vector components would allow to not hardcode the number of dimension for vectors, and therefore not limit the user to a small number of vector images that can be processed (currently only vectors of dimension 2 and 3 are accepted).
- Dominant language
- C++
- Stars
- 4
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
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.
More from BlueQuartzSoftware/ITKImageProcessing
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
enhancement
BlueQuartzSoftware/ITKImageProcessing#156 · 1 assignee ·
-
enhancement
BlueQuartzSoftware/ITKImageProcessing#155 · 3 assignees ·
-
BlueQuartzSoftware/ITKImageProcessing#154 · 1 assignee ·
All issues in BlueQuartzSoftware/ITKImageProcessing
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
duckdb/duckdb-wasm#2258 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
objectionary/eo-graphs#75 ·
-
Coarray integration tests carry no LABELS, so run_tests.py silently skips them under every backend Opencoarray
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
FISCO-BCOS/FISCO-BCOS#5642 ·