| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Signed-off-by: Limin Wang <lance.lmwang@gmail.com>
|
| |
|
|
| |
Signed-off-by: Ting Fu <ting.fu@intel.com>
|
| |
|
|
| |
Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Different function type of model requires different parameters, for
example, object detection detects lots of objects (cat/dog/...) in
the frame, and classifcation needs to know which object (cat or dog)
it is going to classify.
The current interface needs to add a new function with more parameters
to support new requirement, with this change, we can just add a new
struct (for example DNNExecClassifyParams) based on DNNExecBaseParams,
and so we can continue to use the current interface execute_model just
with params changed.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
So the backend knows the usage of model is for frame processing,
detect, classify, etc. Each function type has different behavior
in backend when handling the input/output data of the model.
Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
|
|
|
Signed-off-by: Guo, Yejun <yejun.guo@intel.com>
|
