|
MayaFlux 1.0.0
Digital-First Multimedia Processing Framework
|
Composed context: caller-supplied data for whichever intents need it, consulted after a VisionQuery's resolved sequences have run. More...
#include <VisionInsight.hpp>
Collaboration diagram for MayaFlux::Kinesis::Vision::VisionAnalysisContext:Public Attributes | |
| std::optional< BoundingBox > | detect_features_bounds |
| std::optional< TrackObjectsContext > | track_objects |
Composed context: caller-supplied data for whichever intents need it, consulted after a VisionQuery's resolved sequences have run.
detect_features_bounds stands alone rather than in its own named struct like TrackObjectsContext: Keypoint has no persistent identity to grow a second field around the way TrackResult does, so a bare bounds value is the whole story.
FindElements/DetectEdges/EstimateMotion/MeasureAppearance have no field here: FindElements's contours are already complete with nothing left for the caller to supply, and the other three have no concrete caller-suppliable need identified yet.
Definition at line 49 of file VisionInsight.hpp.