Repeated computation of co-occurrence matrix in haralick features
- Dominant language
- Java
- Stars
- 94
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
A question on haralick features.
All haralick features call the `getCooccurenceMatrix` function on the input image. If I want to compute N different haralick features on an image, the same co-occurrence matrix is computed N times. Unfortunately, the computation of this matrix is often the most intensive part of the feature computation. Ideally, this matrix would be precomputed once per image.
Perhaps this can be solved by overloading the `compute` function, adding a signature that takes a `final double[][] matrix`? I am not sure in what interface or class this signature should be defined, however. Or maybe there is a better way :slightly_smiling_face:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the Haralick feature implementations and the getCooccurenceMatrix entry point, then trace how compute is exposed across the relevant interfaces or classes. Define the reuse boundary so one image's co-occurrence matrix is not recomputed for each feature; done means the API supports this without changing feature results and coverage verifies the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-vision, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100