search

rcrum003 / HiveControl

Alternative software for use with HiveTool suite of software.
GNU General Public License v2.0
25 stars 13 forks source link

Beecounter - Not that accurate #41

Open rcrum003 opened 8 years ago

rcrum003 commented 8 years ago

In testing, the in/out numbers always tend to be the same... While the IN count will increase when bee comes in, the out counter will also get increased a little later..

So at best, we have in/out as one number, but can't differentiate between IN or OUT.

FYI, this code is very much alpha....

NapaOgden commented 8 years ago

Would there be merit in exposing some of the key variables to the users?

rcrum003 commented 8 years ago

Yes, that is in the TODO list.

On May 26, 2016, at 10:46 AM, NapaOgden notifications@github.com wrote:

Would there be merit in exposing some of the key variables to the users?

— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/rcrum003/HiveControl/issues/41#issuecomment-221892601

jhaltd commented 4 years ago

Has the code progressed much since "FYI, this code is very much alpha..." in 2016? I've had the camera pointed directly at the hive since Saturday and so far it's only counted 18 in and 7 out. Now, granted it's a young hive (package this year) but the bees coming in and out of the hive are non-stop. I'd say the hive is thriving.

jhaltd commented 4 years ago

Today's results - 3 bees out, 1 in. Sitting by the hive right now I must have seen 20 - 30 bees coming in. So I guess I know the answer - the code hasn't changed since 2016, still essentially non-functional.

rcrum003 commented 4 years ago

It is functional, but the tunnel has to be very exact and you need to set the in xy and the out xy.

I did run this code for about 3 years before I rebuilt my research hives. We list it as alpha code because you really need to understand vision processing to understand how to modify and we don’t have the resources to teach the world how to use this code.

We also started playing with IR gate sensors instead but the cost and complexity to build was beyond most DIY.’ers

Sent from my iPad

On May 19, 2020, at 6:02 PM, jhaltd notifications@github.com wrote:

 Today's results - 3 bees out, 1 in. Sitting by the hive right now I must have seen 20 - 30 bees coming in. So I guess I know the answer - the code hasn't changed since 2016, still essentially non-functional.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

jhaltd commented 4 years ago

Looking at this again - the Dashboard Flights screen says 23 In and 9 Out today. However, the annotated frame.jpg is labeled 1971 In and 1440 Out. Why is this information not flowing through to the Dashboard's Flights screen?

rcrum003 commented 4 years ago

The picture just shows flights of all time. When the scripts run, it calculates what the old number was and new to figure out rate per interval.

On May 31, 2020, at 11:11 PM, jhaltd notifications@github.com wrote:

 Looking at this again - the Dashboard Flights screen says 23 In and 9 Out today. However, the annotated frame.jpg is labeled 1971 In and 1440 Out. Why is this information not flowing through to the Dashboard's Flights screen?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

jhaltd commented 4 years ago

So the image shows a cumulative number of flights? Not sure what the point of that is, but regardless the number is wrong. Yesterday the image said 1971 bees in, and today it says 3977 which should mean that 2006 bees entered. The dashboard's graph says 11 bees entered... Similarly, yesterday the image said out was 1440, and today it says 3514 indicating that 2074 bees left the hive. The dashboard's graph says that the total number of bees leaving was 17.