-
Notifications
You must be signed in to change notification settings - Fork 30
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
Deepstack model error #38
Comments
maybe needs to investigate it its a compatible-bug between models trained on older yolo versions? see -> ultralytics/yolov5#5234 (comment) |
I am wondering if this is the same issue where it's trying to use Yolo6 and I need to figure out how to make it use yolo5 |
Okay.... I just looked into this more.. the OpenLogo detector is working fine for me. I suspect that this is an issue where it cannot properly convert whatever image type you are working with into the one that Deepstack expects. Where are you getting your image data? Do you know if it's just normal RGB data or maybe has an Alpha channel or something? Can you share an image file? |
maybe an interference with some models from my config?
|
i have to have yolo5 in the config, config (now openlogo as deepstack-type):
|
i test with the image from the openlogo-site, but still that error |
testimage still not work. TESTIMAGE: |
I get the same failure of the doods deepstack models no matter what image I use. *doods2 (tensorflow model) -> success Occasionally the error is different, so maybe there is more than one issue here. Most of the time I get the error in my original post
but on some images I get the same error ozett has just reported in several posts
Here's one of my example images |
Soooo this is interesting... It appears to be some sort of collision with having a pytorch detector enabled along with the deepstack detector. If I disable pytorch the logo detector works fine. That gives me something reproducible to look into at least. |
I can confirm that deepstack models fail to load if I remove pytorch from my configuration.
|
Are you able to share a model? |
My deepstack/dark model is based on the pt file that can be downloaded here: https://github.com/OlafenwaMoses/DeepStack_ExDark/releases/tag/v1 Given that I do get it to work with the deepstack server, I assume the file I downloaded is complete and intact. But here's my local copy as well: |
Okay, I think I fixed part of the issue. It was missing some of the deepstack trainer files it needed to start the dark model. I pushed an image if you want to try that. The issue still remains if you also load the latest yolo model as well, it will print the other error about mismatched tensor sizes. I am still trying to figure that one out. |
The new image works as advertised. As long as I don't load up pytorch, both my deepstack based models now work without errors so that's big step in the right direction. |
i got the downloaded openlogo.pt model to work so i assume, i could be working like yolo5 in the doods2-envrionment . without changing the model.pt file. but maybe that hint helps you |
Okay, I hacked together something. I don't love it but it works. It basically tries the new model way of doing it and if fails it reverts back to the old way. It shouldn't add too much delay. Let me know if it works for you. |
works with openlogo config only.... not with more config-options like normal -> #38 (comment) Toggle the Error-Report
|
I had to fix an issue with no detections but it seems to work fine for me with this config
Make sure you don't have the yolo source files sitting around anywhere, especially in your models directory as it can inadvertently import that. |
So this is interesting... If you load pytorch/yolo before deepstack models, it will fail. If you load deepstack models first, it works fine... |
i will try this order, seems doable |
Thank you! That works for me too (as long as the config order is correct). I'll consider this issue closed, even if this is only a temporary fix till you find a solution you like better. |
log-output: Toggle the Error-Report
|
a bigger image, that dont work @themoment some github failures? |
sometimes its working, but somehow i miss the marked image in the response. |
@ozett make sure you are pulling the latest image. I made a change that should fix the NoneType error you see. @JustinGeorgi it should automatically reorder the detectors so you don't need to worry about the order you put in your config. |
i will try next 60 minutes... thx. (great news!) |
flow is running, needs fine-tuning and for croping the region i need to provide region-coordinates for detections of x,y,w,h and cant fiddle it right TESTIMAGE |
figured it out, activated lost memory. |
Okay, closing this issue. |
Love the new rewrite! I'd been using v1 for some time and just moved over to v2 container recently. Great stuff!
The recent addition of the deepstack models does not seem to be working. I see in issue #28 after it was closed that there's a report that trying to get a deepstack model working resulted in a error. I'm getting the same error with two different .pt models
Error:
Both of the models work with the deepstack service itself, and doods properly reports the labels embedded in the models
so the models seem intact.
My config for the two models is minimal:
do I need more than that or is there some issue with the deepstack integration at the moment?
The text was updated successfully, but these errors were encountered: