addQuantize and addDequantize in th_final_initialize of anamoly detection submitter_implemented.cpp
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 479
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Would it be possible to receive an explanation on towards why these functions are being used in the th_final_initialize function. From what I can see, they only run a check and are never used anymore. I ask because I am having some trouble importing the files needed for them to work onto my project. The issue being that adding all the source files needed for those functions makes me go over my memory requirements.
Basically, are these functions/checks essential to the project or would I be able to leave them out?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading th_final_initialize in submitter_implemented.cpp and tracing the uses of addQuantize and addDequantize, including the source files they require. Document whether these checks are essential and whether they can be omitted under the reported memory constraints, with enough detail for users to make that choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, machine-learning
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100