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

Issues in running GPU device on MTL iGPU in notebook 261-fast-segment-anything #1817

Closed
1 task done
xiangyang-95 opened this issue Mar 13, 2024 · 4 comments · Fixed by #1850
Closed
1 task done

Issues in running GPU device on MTL iGPU in notebook 261-fast-segment-anything #1817

xiangyang-95 opened this issue Mar 13, 2024 · 4 comments · Fixed by #1850
Assignees
Labels
PSE Escalate to PSE for further investigate support_request

Comments

@xiangyang-95
Copy link

xiangyang-95 commented Mar 13, 2024

Describe the bug
No results are seen when running the notebooks with iGPU on MTL platform. The Inference is done but no bounding box is seen, However, when change the device to CPU, the bounding box results are seen.

Expected behavior
Can see the result when using iGPU to perform inference.

Screenshots

Installation instructions (Please mark the checkbox)

** Environment information **

Additional context

@YuChern-Intel
Copy link

I obtained the same result as you when inferencing with iGPU.

Inferencing on CPU:
CPU

Inferencing on iGPU:
GPU

We'll investigate the issue and update you as soon as possible.

@YuChern-Intel YuChern-Intel added the PSE Escalate to PSE for further investigate label Mar 15, 2024
@avitial avitial self-assigned this Mar 15, 2024
@eaidova
Copy link
Contributor

eaidova commented Mar 19, 2024

@xiangyang-95 could you please try to apply configuration changes proposed in this PR #1829? Fast-Segment-Anything is based on yolov8, it is known limitation that it may requires to disable some optimization for GPU to get accurate result on some platforms

@xiangyang-95
Copy link
Author

@eaidova I am still having the same issue after applying the configurations in the PR.
Based on some tests, I found that when we export the model to a static shape, then it works.
Using a dynamic shape has no detections on the result when the accuracy is high, if the accuracy threshold is tuned down to very low (0.01), the results can be seen.
I also find that the tensor data between the static and dynamic shapes are different as well.

@eaidova
Copy link
Contributor

eaidova commented Mar 26, 2024

@xiangyang-95 thank you for your findings, I updated notebook to use static input shapes

@eaidova eaidova linked a pull request Mar 26, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PSE Escalate to PSE for further investigate support_request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants