dlib | Core Dart Extension Library

Use from tensorflow.keras. instead of from keras.

This line: for (top, right, bottom, left), name in zip(faceLocations, faceNames): .

Make sure that top, right, bottom, left values are integer values and not float values. Just print them once to confirm. If they are float values convert them to int using int(). Like this:

MAX_FEATURES argument of AKAZE_create is not a valid argument.

See AKAZE_create documentation:

retval = cv.AKAZE_create( [, descriptor_type[, descriptor_size[, descriptor_channels[, threshold[, nOctaves[, nOctaveLayers[, diffusivity]]]]]]] )

Replace akaze = cv2.AKAZE_create(MAX_FEATURES) with:

Mine also does not have that option! I will share what I found until someone comes with a better answer.

As far as I am aware, LLDB is now the default and only debugger of Android Studio. Therefore it does not appear as an option anymore because it is part of Android Studio.

My references: https://source.android.com/devices/tech/debug/gdb ,it states:

"For app development, see Debug your app instead, which explains how to use the Android Studio GUI (based on LLDB)."

In https://developer.android.com/studio/debug/index for example is stated:

"Native (available only with C/C++ code)Select this debug type if you want to use only LLDB to debug your code."

This page makes many references just to lldb to debug native C++ code. But never mentions gdb anywhere. Just that alone, should somehow let us know that gdb is out of the game.

But digging further:

Interesting is, that if we look at Android Studio release notes webpage at: https://developer.android.com/studio/releases#2-0-0

it is never mentioned that gdb was replaced by lldb or that the option for gdb does not exist anymore.

(But there is some interesting release note from android studio 3.1 that LLDB only works for android studio 4.1 (strange). )

However if we check the Android NDK ( which is used to compile native C++ in android studio) release notes history, at: https://developer.android.com/ndk/downloads/revision_history

it is stated for example at Revision r22b (March 2021) "ndk-gdb now uses lldb as the debugger ".

and at Android NDK, Revision r18b (September 2018) states: "GCC has been removed"!!!!!!!

It would be great to find a webpage/release note information that clearly states what you are asking in regard to Android Studio. It should have been mentioned in the android studio releases notes something like "GDB was replaced by LLDB" or "GDB option was removed". was this note missed by the developers?. I do not know.

As such, I, like you, I am not 100% assured what happened to the GDB option, and when it was removed or if it was really removed.

Btw, i do not understand why it was completely replaced, and not left as an option.(and so called experts i asked also didn't had a definite answer either :)

I used an object tracker to continue locating the eye after drawing a bounding box around it on the first frame.

I created a set width and height bounding box since we can roughly assume that the eye isn't growing or shrinking relative to the camera. When drawing the bounding box for the tracker, we have to include more than just the eye since it would otherwise lose track of the object whenever they blink.

I looked for whether the saturation of the bounded area dropped below a threshold in each frame as a check for whether or not they blinked. The blue box is the bounding box returned by the tracker, the green box is the area I'm cropping and checking the saturation level of.

Here's a graph of the saturation level over the course of the video

You can clearly see the areas where they blinked

Here's a (heavily compressed to make the 2mb limit) gif of the result

Try changing kernels. (Check on the image in the URL for guidance). If your venv is not in the list, you should add it manually. Follow this guide to add your venv

It was the parser also OpenFace doesnt work well with Windows. Tried some Docker stuff but didnt work. Transitioned to dlib and opencv and im making progress.

try this: