Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] imx500_object_detection_demo.py: AttributeError: 'NetworkIntrinsics' object has no attribute 'bbox_order' #1163

Open
alexandre-perrin opened this issue Nov 15, 2024 · 1 comment

Comments

@alexandre-perrin
Copy link

alexandre-perrin commented Nov 15, 2024

Describe the bug

Running imx500_object_detection_demo.py on Raspberry Pi 5 with IMX500 camera fails with: AttributeError: 'NetworkIntrinsics' object has no attribute 'bbox_order'

To Reproduce

On Raspberry Pi 5 with AI Camera:
execute the demo script with no parameters:

python imx500_object_detection_demo.py

Expected behaviour

Camera starts and application keeps running without crash.

Console Output, Screenshots

Traceback (most recent call last):
  File "/home/alexandre/aitrios-sdk-edge-app-dev/sample_apps/detection/python/imx500_object_detection_demo.py", line 246, in <module>
    last_results = parse_detections(picam2.capture_metadata())
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/alexandre/aitrios-sdk-edge-app-dev/sample_apps/detection/python/imx500_object_detection_demo.py", line 30, in parse_detections
    bbox_order = intrinsics.bbox_order
                 ^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'NetworkIntrinsics' object has no attribute 'bbox_order'

Hardware :

Raspberry Pi 5 with AI Camera IMX500

Additional context

Current workaround: replace intrinsics.bbox_order with args.bbox_order

@davidplowman
Copy link
Collaborator

Hi, thanks for the report.

I think the problem might just be that we're on the verge of rolling out a new camera software release, so all the code trees have been updated, but the underlying packages didn't quite make it before the weekend.

Perhaps try checking out out the v0.3.22 tag and see if that helps. Hopefully things will go back to normal at the start of next week. Sorry for the inconvenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants