Change in ArucoDetector return value in 4.13.0.90?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 1k
- Avg merge
- 22h 17m
- Merged PRs (30d)
- 3
Description
Since this morning the following code has started crashing:
corners, ids, rejected = self.ARUCO_DETECTOR.detectMarkers(img)
# ...
if not ids is None:
for i in range(len(ids)):
rv_ids.append(int(ids[I]))
With error
File ".../cwipc/cwipc_util/python/cwipc/registration/multicoarse.py", line 525, in _find_aruco_in_image
rv_ids.append(int(ids[i]))
^^^^^^^^^^^
TypeError: only 0-dimensional arrays can be converted to Python scalars
Has the return value of the ArucoDetector changed?
I have checked the release notes but I couldn't find anything...
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 with cwipc/cwipc_util/python/cwipc/registration/multicoarse.py at _find_aruco_in_image and compare the shape returned by ArucoDetector.detectMarkers across the reported version change. Check the release notes and relevant OpenCV ArUco API behavior; done means the return-value change or regression is identified and its expected handling is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- opencv, python
- Domain
- computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100