1. Portable and Predictable Performance on Heterogeneous Embedded Manycores (ARTEMIS 295440) ARTEMIS Project Review 28 nd October 2014 Multimedia Demonstrator (Presented by: Raúl Santos de la Cámara – HI Iberia) 2014-10-28ARTEMIS PaPP Revie4 20131

2. Contents 1.Overview Motivation 2.Results Multimedia Demonstrator Architecture Development pipeline / Usage of PaPP results Live demonstration Conclusions & next steps Variability demonstration Industry rationale Video Demonstration Conclusions & next steps 3.Q+A 22014-10-28ARTEMIS PaPP Revie4 2013

3. 1. Overview – motivation Topic: Field surveillance by end-users Based on a HI Iberia product. Typically Police Officers, First responders. Also related: access control, other applications. Key benefits: Using low cost COTS sensors  smartphones. Using in-device preliminary processing. Combined: low cost solution for law enforcement stakeholders. Role of PaPP technology: Leverage on multi-core mobile solutions for processing power, energy efficiency. Provide portability: among COTS Android devices, potential extension to dedicated HW. Enable adaptability in resources usage (energy/battery) 32014-10-28ARTEMIS PaPP Revie4 2013

4. 2. Architecture Based on commercial product running Android OS Extended by PaPP middleware Key roles of device: Video analytics in device (e.g., face, license plate recognition) Maximize expressivity of data sent to server (semantics) Efficiently stream video (tradeoff with battery life) 42014-10-28ARTEMIS PaPP Revie4 2013

5. 2. Architecture 5 Adaptability manager is a C/C++ asset as the OpenCV ffmpeg libraries which interacts with the processes launching the video processing stages- Adaptability manager CV 2014-10-28ARTEMIS PaPP Revie4 2013

6. 2. Energy adaptability Energy efficiency is one of the key industrial requirements in this demonstrator. Real system runs on the mobile device battery during real life events, e.g., was used during the proclamation of King Philip VI last June (duration was well over 4 hours). Thus, for real applications  device must optimize the usage of energy. Strategies: less processing, reduced fps, smaller work resolution, switch to different algorithms. In this demo: fine tuning of OpenCV stage, disabling energy expensive optimizations 62014-10-28ARTEMIS PaPP Revie4 2013

7. 2. Live demo Demo on ARM commercial device 72014-10-28ARTEMIS PaPP Revie4 2013

8. 2. Conclusions Use case for energy adaptability has been integrated in the demonstrator. Current implementation yields ~20% improvement in battery-drain tests. Integration of PaPP-enabled elements with regular development toolchains (i.e., the Android SDK) has been improved. Using lower level APIs (e.g., reading battery levels). Some basic tests were done for x86 architecture (not using the Android GUI) with good results Also integrated with the variability modelling demonstrator (WP3) Code has been streamlined, will be easier to share in the next iteration with the technology providers e.g. to implement parallelization. 82014-10-28ARTEMIS PaPP Revie4 2013

9. 2. Next steps Emphasis on task-based parallelization to improve the performance. Consider portability to other hardware and tests on other architectures for comparisons (x86). Extend the modelling approach. E.g., performance predictability. Add better tracing and instrumentation. 92014-10-28ARTEMIS PaPP Revie4 2013

10. 2. Variability demonstrator The HIB WP6 demonstrator is based on a product for mobile surveillance. Problem: the product needs to be customized for each client. This leads to very intensive refactoring work for the development team. The solution presented in this demonstrator is the use of variability modelling to semi-automatically create variants (e.g., customized pieces of software complying with a set of requirements). 102014-10-28ARTEMIS PaPP Revie4 2013

11. 2. Variability demonstrator Fit in PaPP objectives: Establish links with the rest of high level modelling (e.g. introduce performance metrics, adaptability in the variability models). Link variability with the code generation for the toolchain: different adaptability options require different assets which must be managed at design level. Improve developer efficiency. 112014-10-28ARTEMIS PaPP Revie4 2013

12. 2. Variability demonstrator Current software production process: 1.The business units discuss with the customer. 2.Requirements are informally gathered and passed on to the product owner (systems designer). 3.Product owner checks if the options in the requirements are compatible, generates a modification request for the development team. 4.Developers change the code manually, generate a customized variant. 122014-10-28ARTEMIS PaPP Revie4 2013

13. 2. Variability demonstrator Desired software production process: 1.Business units interview the customer. 2.Requirements are collected in a semi-structured manner (e.g., standardized Excel file). 3.Requirements are loaded into the variability management system and constraints are automatically checked. The product owner is only required in case of violations. 4.Variability manager generates a summary build configuration and test cases. 5.Configuration is used by the development team and test cases are run to check final compliance. 132014-10-28ARTEMIS PaPP Revie4 2013

14. 2. Variability demonstrator The variability management software for Y2 has been PLUM by Tecnalia (proprietary). Plan is to transition to open sourced related tools. 142014-10-28ARTEMIS PaPP Revie4 2013

15. 2. Live demo Video on variability 152014-10-28ARTEMIS PaPP Revie4 2013

16. 2. Variability demonstrator Future steps Transition to open source modelling tools. Better integration with the rest of the PaPP modelling framework (e.g., incorporation of performance metrics to the variability modelling). Better coverage of the application model (WP6 demonstrator). 162014-10-28ARTEMIS PaPP Revie4 2013

17. WP6 Q+A 17 Thanks for the attention! 2014-10-28ARTEMIS PaPP Review 2014