Gen2 common objdet #34
Conversation
…ng mobilenet into this branch to make example usage a bit easier.
It's ultimately to make transfering larger pieces of data off the esp32 easier. By separating metadata and message data we don't have to deal with finding the location of metadata and excluding it from the transmission. It was fine with smaller message because we could fit the entire message in memory and parse it.
| @@ -0,0 +1,33 @@ | |||
| #pragma once | |||
There was a problem hiding this comment.
Oh, good call, I can remove all the old CommonObjDet stuff.
| dai::DetectionNetworkProperties properties; | ||
|
|
||
| public: | ||
| Input input{*this, "in", Input::Type::SReceiver, {{DatatypeEnum::Buffer, true}}}; |
There was a problem hiding this comment.
Should only accept ImgFrame types (as input w&h are required, right?)
Input input{*this, "in", Input::Type::SReceiver, {{DatatypeEnum::ImgFrame, false}}};
|
|
||
| public: | ||
| Input input{*this, "in", Input::Type::SReceiver, {{DatatypeEnum::Buffer, true}}}; | ||
| Output out{*this, "out", Output::Type::MSender, {{DatatypeEnum::Buffer, false}}}; |
There was a problem hiding this comment.
Outputs ImgDetections type:
Output out{*this, "out", Output::Type::MSender, {{DatatypeEnum::ImgDetections, false}}};
There was a problem hiding this comment.
The SPIOut node is expecting DatatypeEnum::Buffer for input though. Can I leave it as DatatypeEnum::Buffer or is there some other way around this?
There was a problem hiding this comment.
SPIOut is expecting Buffer or its descendants (think, derived objects / polymorphism), same as XLinkIn.
Therefore they can both accept any messages.
|
@jonngai One extra request - can you derive |
Hey @themarpe , I set that up but still had to override a number of methods since DetectionNetwork has its own inputs, outputs and properties. Let me know if there's a better way of handling this or if this'll do for the time being. Thanks. |
No description provided.