bi-aidetection
bi-aidetection copied to clipboard
VorlonCD
Future of DeepQuest and DeepStack?
@VorlonCD Just curious if anyone here has thought about the ominous absence of the deepquest folks and the future of DeepStack viability. They haven't had a release in a long time, their website hasn't had much revision in a long time and from this post, they don't seem too interested in sales requests. https://forum.deepstack.cc/t/is-deepquest-dead/431
I'm just wondering with all of these wonderful changes, how difficult would it be to pivot this work over to another AI engine?
Most likely it wouldn't be that hard to use a different engine, and I do want to provide that ability at some point.
If anyone wants to research to find the best ones that would be great! Or even implement!
I took a quick look a while back.... Don't remember if any of these can run fully locally or not, but I think there is a free or low cost option for most.
Sighthound ImageAI AWS Rekognition Google AutoML
Andrew, I agree it doesn't look very promising, but I'm still hopeful they'll release it open-sourced as promised.
From the information on their website, the two Deepstack developers, Moses and John, are brothers from Nigera and since early 2020 appear as "Software Engineers at Microsoft." It seems like their priorities have shifted, but they're both still active online and provide their contact info on the website. Not sure if there's any point to reach out and ask for an update (I've tagged them below), but they both seem very nice. :)
Developed and Maintained by Moses Olafenwa and John Olafenwa, brothers, creators of TorchFusion, Authors of Introduction to Deep Computer Vision and creators of DeepStack AI Server.
Moses Olafenwa Email: [email protected] Website: http://olafenwamoses.me Twitter: @OlafenwaMoses Medium: @guymodscientist Facebook: moses.olafenwa Github: @OlafenwaMoses
John Olafenwa Email: [email protected] Website: https://john.aicommons.science Twitter: @johnolafenwa Medium: @johnolafenwa Facebook: olafenwajohn Github: @johnolafenwa
Hello @AndrewHoover @aesterling @VorlonCD
Thanks for bringing this up and it is exciting to see how DeepStack is being used. We truly haven't done much development as we would have wanted to in recent times. It took a bit of settling down for us into our new job. Apologies for the pause in recent times.
We are planning on stabilising the development and would have new releases in coming weeks with significant improvements. The project is not abandoned and a lot is coming on it soon.
Please bear with us. Thanks
@johnolafenwa That's great news and can't wait to hear more. Hope you're doing well and thanks again for the incredible tools. Appreciate the fast response!
Excellent!!! Thank you so much for the response @johnolafenwa ! I'm not sure how much you anticipated that DeepStack would be used in the hobbyist / maker community but projects like this one that @GentlePumpkin and @VorlonCD have developed have allowed an huge step forward in automation and functionality by bridging DeepStack to our projects.
@VorlonCD @AndrewHoover @aesterling To add to what @johnolafenwa said, the maker and open source community has really inspired us to pursue and continually developing DeepStack to serve the community in new ways, considering the wealth of tools and ecosystem built on top of its capabilities.
These are the reasons why we will open source the project to accelerate further development as well as open the door for more applications and impact.
Out of curiosity, can you guys please tell us why the delay?
Sure we all have day jobs and that is a really valid argument but I am not quite sure yet why uploading the source code to github should be a challenge.
Please illuminate me as I am here to learn, not b*tch at you.
@githubDiversity That's a good question. Sure, we could just open source the current codebase, however we have been developing a new version of DeepStack that is significantly faster and more stable than the existing version of DeepStack, it is source for this that we are releasing soon. FYI, before this weekend ends, we shall release the CPU version as it is completed, and the gpu version the next week. The codebase will be made public before November ends. In the meantime, this new releases coming up will require purchasing no activation, with all features free perpetually.
Also, we are planning a lot more than just releasing the source code. We are making significant efforts to setup a stable dev community, proper documentation and a strong ecosystem similar to what we have for projects like kubernetes.
Hi, any idea when you will be releasing the beta for the Pi? I just can't get the alpha to work. I must have installed it over 20 times on different machines with new sd cards. It reports the positions of the object back in the wrong place. If the object is at the top it moves it down and if it's near the bottom it moves it up. Left and right are ok.
Hello @Tinbum1 , the current pi version has a number of issues. The beta will be docker based as we are switching to supporting DeepStack only on docker. I can't give a definite time for when this will be released, but it will out before the end of the year. This will likely be a November release.
@johnolafenwa Many thanks for the prompt reply. That's great, can't wait so I can get my power consumption down! Love the work you've done, thank you,.
Hello @VorlonCD @githubDiversity @aesterling @AndrewHoover @Tinbum1 @classObject
We have just released update to the cpu version and will follow up soon with the gpu version. run
deepquestai/deepstack:latest
or
deepquestai/deepstack:cpu-x4-beta
The new update is so much faster and a lot more accurate.
Would love to know your feedbacks here on on the forum https://forum.deepstack.cc on this new release
I can't say enough how much this conversation here has contributed to our energy. Thank you all
@OlafenwaMoses Would deepquestai/deepstack:latest be for running this on Docker? I am using the windows version is why I am asking. thanks.
@balucanb This is for running on Docker. Note that we are switching to docker only for all deepstack editions, the windows version has been discontinued. Note that the docker version runs on windows as well. Should you have any challenges running the docker version, please let us know.
Thanks! I assumed that was the answer. No clue how to use Docker, looks very confusing to me! I am sure I will have questions. Will the current windows version stop working completely or is it just not being updated anymore? Thanks again.
@balucanb all the instructions are on the first page of the AITool forum thread.
@johnolafenwa Thanks for the update! I'm seeing a dramatic speed increase. My response times have gone from an average of 630ms down to an average of 230ms.
Mines gone from about 1000 to 210ms but coming back as bad request in AITool so will have to investigate that. Got http status code '400' in 241ms: Bad Request|81414|1||24 Empty string returned from HTTP post.|81415|1||24
@Tinbum1 In the previous versions of DeepStack, all requests returned 200 | Success. In this new version, we have improved error reporting. Images that are not able to be processed possibly due to sending a corrupt file or a file that is not an image will return 400 | Bad Request. I recognize this is a breaking change and existing integrations will need to take this into account.
Can you share the input you sent that returned this?
I am excited to here about the speed increase being experienced. This has been a top priority for us
@johnolafenwa Thanks for the reply, I'm afraid I only use AITool and only know a bit about computing so will have to find out how to do that.
@Tinbum1 @johnolafenwa DeepStack seems to be returning a 400 Bad Request if it does not detect any objects in the image. I changed the exposure on an image that worked until it was so dark there were no detections. It returned a Bad Request. Your image returns a bad request for me as well.
@classObject Well figured out. I've just put some images in my input folder from this morning and they were processed without any problem.
The speed increase is excellent, so thank you @johnolafenwa!
But, I too am getting 400 Bad Request errors from Deepstack. Is that something that @VorlonCD can adjust AI Tool to handle? Or is there something else that needs to change?
Ok, this version of AITOOL will ignore BadRequest error 400 and ASSUME it means 'false alert' for NOW, but this really should be fixed on the Deepstack side since we DO want to know when an actual error happens and not ignore it.
@OlafenwaMoses the JSON response should be sent rather than error, but with no 'prediction' objects in the case of no predictions being found. Like it did before. Error 400 is great for bad image or other unexpected error.
THANK YOU for your hard work on this project, its amazing to use to prevent false security camera alerts!
Thanks @classObject @Tinbum1 @VorlonCD
Returning error on no detection is not by design, this is a bug. I have confirmed this on our side too. This would be fixed and a new update will be released soonest.
Hello everyone, the issue with no detections has been fixed. Run
deepquestai/deepstack:latest
or
deepquestai/deepstack:cpu-x5-beta
If any further bugs are encountered, would love to know and address it as soon as possible