Tips for Disabling ML5 Posenet

Question

Tips for Disabling ML5 Posenet

Looking to halt Posenet after completing app task

    private sketch(p: any) {
        p.setup = () => {
            this.poseNet = ml5.poseNet(p.createCapture(p.VIDEO), {
                outputStride: 8
            });
            this.poseNet.on('pose', (results) => {
                //DO SOMETHING WITH results[0]
            });
        };
    }

Tried setting different variables to null without success

    StopKI() {
        // Terminate PoseNet when done
        this.p5 = null;
        this.poseNet = null;
        console.log('KI stopped');
    }

javascript typescript p5.js ml5.js

Answer 1

Answer №1

When the posenet detects activity in the video element, removing the video element may cause the detections and callbacks to cease functioning.

const video = document.getElementById("video");
video.remove();

The detection function in the source code continues to call itself as long as the video element exists.

async multiPose(inputOr, cb) {
  if (this.video) {
    return tf.nextFrame().then(() => this.multiPose());
  }
}

Removing the video element could potentially end the repetitive loop. No other more elegant solution is evident in the source code 😎

UPDATE

I have discovered that the poseNet.on(...) event listener can be deactivated by using RemoveListener and passing the same callback function. This method appears effective in the online P5 web editor:

// store the pose event callback in a variable
callback = function(results) {
    poses = results;
}

// begin listening for pose detection events
poseNet.on('pose', callback);

// cease listening for pose detection events by removing the event listener
poseNet.removeListener('pose', callback);

Answer 2

When the posenet detects activity in the video element, removing the video element may cause the detections and callbacks to cease functioning.

const video = document.getElementById("video");
video.remove();

The detection function in the source code continues to call itself as long as the video element exists.

async multiPose(inputOr, cb) {
  if (this.video) {
    return tf.nextFrame().then(() => this.multiPose());
  }
}

Removing the video element could potentially end the repetitive loop. No other more elegant solution is evident in the source code 😎

UPDATE

I have discovered that the poseNet.on(...) event listener can be deactivated by using RemoveListener and passing the same callback function. This method appears effective in the online P5 web editor:

// store the pose event callback in a variable
callback = function(results) {
    poses = results;
}

// begin listening for pose detection events
poseNet.on('pose', callback);

// cease listening for pose detection events by removing the event listener
poseNet.removeListener('pose', callback);

Tips for Disabling ML5 Posenet

Answer №1

Similar questions

Leveraging the power of jQuery Validation in conjunction with Bootbox

The jQuery $.change function is not functioning properly when used with a cloned select element

angularjs controller cross-validation for forms

Struggling to make the controller karma test pass

Unable to extract property from object in context due to its undefined status

"Trouble with server communication: data array not being passed to hbs

Attempting to modify the background color of an iFrame in Internet Explorer

Implementing a conditional chaining function in TypeScript

Use the class type or any of its derived classes rather than an object of the class itself

encountering a problem with iterating through a JSON array

Tips for ensuring an animation is triggered only after Angular has fully initialized

Does modifying data from an AngularJS service update the original data within the service?

Conceal the sidebar menu by clicking anywhere outside of the menu bar or the designated button

React JS - Building a dynamic multi-tiered dropdown navigation system

Calculate the quantity of rows within a specific div container

Chrome fails the karma tests while phantomjs passes them

Ensuring the child div's height does not overflow beyond the parent div

Tips for preventing redundant function calls to a prop within a ReactJS component

Having difficulties including the Stack Overflow website within an iframe

In TypeScript, an interface property necessitates another property to be valid