-
Notifications
You must be signed in to change notification settings - Fork 22
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
Pose estimator - invalid output #148
Comments
Hello @GiTackers First it looks l that docker in the camera doesn't have the application image. |
OK, the problem was that there was no more space left on the device: solved with a larger sd card. But, now, another question.
Any idea about it? Thank you very much in advance. |
|
Good morning and thank you for your response! Yes, the firmware is the latest one (11.4.63), and keypoints/confidences are the same without or with person in the scene. Without person it prints: Key points: [[0.29087663 0.4014917 ] With person it prints: Key points: [[0.29087663 0.4014917 ] So, the same output. Any idea about it? Thank you very much in advance. |
Hello everyone. We even reset the camera and reinstall all over again but the same problem happens. Any idea about it? Thank you very much in advance. |
Hi @GiTackers We are going to look into this. |
Hello Corallo and thank you for your response. Yes, we are using example as it is, without changes: we followed this https://github.com/AxisCommunications/acap-computer-vision-sdk-examples/tree/main/pose-estimator-with-flask. Only one thing. Even if in the live stream resolution (width x height) is 2592x1944, in the flask video stream it appears as part of that full image, it shows just the central region: that is, full height but width reduced (equally to both right and left). We don't know if this behaviour is intentional. Thank you very much in advance. |
@GiTackers In the mean time, as a work around you can try with an older firmware that doesn't have this issue: If latency is not an issue and you need to use the latest firmware, another workaround is to switch to CPU for running the inference (change configuration file on the docker compose up command). Regarding the resolution, the model takes in in put a squared aspect ratio. To avoid distortion in the image we are cutting only the central part of it. Another option would be to pad the height and obtain the same result without loosing the view area. |
Hello Corallo and thank you for your response. We installed that firmware (11.0.89), but it's incompatible with Docker ACAP. Following the guide, at the start, giving the command ssh root@$DEVICE_IP 'command -v containerd >/dev/null 2>&1 && echo Compatible with Docker ACAP || echo Not compatible with Docker ACAP' returns "Not compatible with Docker ACAP". In fact, in the "App" section of the camera, flagging the "Docker Daemon" returns "Unable to start". Thank you very much in advance. |
This is unfortunate... I am afraid there's only 11.2 that has both docker daemon and doesn't have this issue with the model. In the meantime, we are investigating the issue to see if we can solve it for a future firmware release. |
Hello Corallo, just as information: after ticket, they send us P1468-LE_11.2.68 firmware. Using this bin, it works. Thank you very much. |
Glad that worked, we'll keep this issue open until we solve it for future firmware |
This issue should be solved in the next firmware release 11.6 |
The issue is fixed in 11.6 |
Hello everyone.
We have a P1467-LE camera. We're trying example 'pose-estimator-with-flask', but when we execute
docker-compose --tlsverify --host tcp://$DEVICE_IP:$DOCKER_PORT --env-file ./config/env.$ARCH.$CHIP up
it returns
Error response from daemon: pull access denied for acap4-pose-estimator-python, repository does not exist or may require 'docker login': denied: requested access to the resource is denied
and, in the camera log, we find:
2023-06-19T17:36:33.498+02:00 axis-b8a44f82b9a9 [ INFO ] dockerdwrapper[12194]: time="2023-06-19T17:36:33.496465080+02:00" level=error msg="Not continuing with pull after error: errors:\ndenied: requested access to the resource is denied\nunauthorized: authentication required\n"
2023-06-19T17:36:33.498+02:00 axis-b8a44f82b9a9 [ INFO ] dockerdwrapper[12194]: time="2023-06-19T17:36:33.496587200+02:00" level=info msg="Ignoring extra error returned from registry: unauthorized: authentication required"
2023-06-19T17:36:33.607+02:00 axis-b8a44f82b9a9 [ INFO ] dockerdwrapper[12194]: time="2023-06-19T17:36:33.606334960+02:00" level=warning msg="error aborting content ingest" digest="sha256:3fda7495b281a86f22bccae769d752db33a9e89af264570a1853b107390599a6" error="context canceled" remote="docker.io/axisecp/acap-runtime:1.2.0-aarch64-containerized"
2023-06-19T17:36:33.607+02:00 axis-b8a44f82b9a9 [ INFO ] dockerdwrapper[12194]: time="2023-06-19T17:36:33.606507960+02:00" level=warning msg="Error persisting manifest" digest="sha256:3fda7495b281a86f22bccae769d752db33a9e89af264570a1853b107390599a6" error="error writing manifest to content store: failed to send write: EOF: unknown"
Any idea about it?
Thank you very much in advance.
The text was updated successfully, but these errors were encountered: