Add jdetnet_voc network and make it the default - jdetnet_voc is trained with more object categories than original jdetnet. Make jdetnet_voc the default in the ssd example. User can still use command line options to run the original jdetnet network. - MCT-1091
Add option to specify object classes list file - so that user can specify a different object classes list file without re-compiling the application. - MCT-1081
mcbench: Multicore benchmark with minimal overhead - Add required models, input test vectors and platform specific scripts - Add inference configuration files for multicore benchmarking - Rename input files to indicate multiple frames and add more inference configurations, covered in regression scripts (MCT-1075)
Simplify API for multiple contexts 1. Simplify context API in ExecutionObject. Replace context_id variants to multiple existing APIs with these two APIs: bool AcquireAndRunContext(uint32_t& context_idx, int frame_idx, const IODeviceArgInfo& in, const IODeviceArgInfo& out); bool WaitAndReleaseContext(uint32_t context_idx); 2. The timing methods for host execution in EOPs and EOs: * GetProcessTimeInMilliSeconds() * GetHostProcessTimeInMilliSeconds() are no longer accurate with multiple contexts and pipelining. Replace these methods and replace with a generic timestamp based approach. There is a single API call to enable time stamps in an application: //! Enable time stamp generation for TIDL API events bool EnableTimeStamps(const std::string& file = "timestamp.log", size_t num_frames=32); If this method is called before TIDL API frame processing, the API will generate timestamps for events corresponding to each frame (e.g. EOP::ProcessFrameStartAsync, EOP::ProcessFrameWait, etc.). These timestamps are then written to file when the user's application completes. A separate script is used for post-processing the time stamps and generating data for the user. (MCT-1073, MCT-1074)
Updates to User's Guide and related examples Changes: * Overview chapter, includes a Terminology section. * Section on different use cases in the "Using the API" chapter. * Updated the Examples chapter to reflect new examples and AM5749 benchmarking. * Added the two_eo_per_frame_opt example to illustrate double buffering. (MCT-1043)
Video input option and document update - mp4/avi/mov as pre-recorded video input - camera as live video input, let user choose video input port # - refactor examples code - bookkeep each EO's device/host time inside EOP since EO could be shared - documentation update on 650MHz EVE - documentation on video inputs and output - MCT-1015