I just tried 5.4.9.5 and got a 170 error on the very first detection. I got an email from Ken saying that some things had been fixed in this revision, but the 170 error doesn't seem to be one of them. Back on 5.4.8.2 again.
I just tried 5.4.9.5 and got a 170 error on the very first detection. I got an email from Ken saying that some things had been fixed in this revision, but the 170 error doesn't seem to be one of them. Back on 5.4.8.2 again.
5.4.9.5: I got the same thing. Stopped BI service, removed Dark.pt from the customs model folder, unchecked the use custom models, set the the timing of the extra images sent from 1min (old minimum) to 250 ms, facial recognition turned off and have only seen ONE DeepStack: Server Error 100 since.
So I am not sure if root cause is custom models, time out of 10 extra images at 1 second each, or a combination of both.
I am using dark.pt and didn't shut it off when I had .9 installed. I'm set at 3 images to analyze and still got the 170 error. I didn't run it for more than about two minutes so that's the only error I saw but that was enough. The image was easily in the detectable region. If it had said "nothing found" I would have let it run, but getting an error right out of the box....
I am using dark.pt and didn't shut it off when I had .9 installed. I'm set at 3 images to analyze and still got the 170 error. I didn't run it for more than about two minutes so that's the only error I saw but that was enough. The image was easily in the detectable region. If it had said "nothing found" I would have let it run, but getting an error right out of the box....
If you haven’t lately you might want to try DS without using the dark model. It is triggering a lot better with the internal model than it used to. The images below are from a junk camera in complete darkness using only the IR from the camera.
I had disabled the dark model with 5.4.9.4 due to the number of deepstack errors that I was seeing. I've re-enabled the dark model with 5.4.9.5 and it seems to be working better at first blush. Only one deepstack error so far on the camera that was constantly generating them. I'll have to keep an eye on it and see how it goes.
Still wondering what the Deepstack codes mean. I've seen mostly 100's, with a few 170's, and I think -1 means Deepstack isn't running.
Also noted that static/occupied is still not working consistently.
Update: I ended up turning off custom models again, it was causing Deepstack errors on other cameras and failing to detect properly.
If you haven’t lately you might want to try DS without using the dark model. It is triggering a lot better with the internal model than it used to. The images below are from a junk camera in complete darkness using only the IR from the camera.
