justadudewhohacks / justadudewhohacks/opencv4nodejs

trainAutoAsync

Open
#606 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
5.1k
Forks
826
PR merge metrics
No merged PRs in 30d

Description

I have a docker image based on justadudewhohacks/opencv-nodejs:node9-opencv3.4.1-contrib

While CPU profiling my Node.JS app in my container, I found a lot of time being spent on trainAutoAsync and it's not directly from my code. So far I can't determine what's calling it and wondering if you can shed any light on this since I'm not doing any ML with this code. I also can't think of anything I'm doing that I'd expect to be calling an MLTrain() function.

https://justadudewhohacks.github.io/opencv4nodejs/docs/SVM/#trainAuto

Thanks in advance for any insight.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the profiler entry for trainAutoAsync in the opencv4nodejs bindings and the SVM trainAuto documentation linked in the issue. Check how MLTrain() could be reached from the reported Node.js application and Docker image, then document the caller or reproduction that explains the unexpected work.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, opencv
Domain
computer-vision
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.