[313] | 1 | \label{task-demonstrator} |
---|
[291] | 2 | \begin{taskinfo} |
---|
| 3 | \let\MDS\enable |
---|
| 4 | \let\BULL\enable |
---|
| 5 | \let\THALES\leader |
---|
[348] | 6 | \let\LIP\enable |
---|
[291] | 7 | \end{taskinfo} |
---|
| 8 | % |
---|
| 9 | \begin{objectif} |
---|
| 10 | This task groups the demonstrators of the COACH project. |
---|
| 11 | The demonstrators cover various domains and application types to drive |
---|
| 12 | the specification choices and to check most of the COACH features. |
---|
| 13 | \end{objectif} |
---|
| 14 | % |
---|
| 15 | \begin{workpackage} |
---|
| 16 | % |
---|
| 17 | \subtask{\bull HPC demonstrator} |
---|
| 18 | The application that \bull proposes is HPC oriented. |
---|
| 19 | The domain of the application is the treatment of medical images (image noise |
---|
| 20 | reduction and segmentation or registration). |
---|
[381] | 21 | Our expectation from the COACH project is to enhance the \bull HPC solutions that |
---|
[291] | 22 | are currently based on multi-cores and GPUs with fine grain parallelism on FPGA. |
---|
| 23 | \begin{livrable} |
---|
| 24 | \itemV{0}{6}{d}{\Sbull}{\bull demonstrator} |
---|
[381] | 25 | The deliverable is a document that describes the application that will be used as |
---|
[291] | 26 | demonstrator. |
---|
| 27 | \itemV{6}{12}{x}{\Sbull}{\bull demonstrator} |
---|
| 28 | The deliverable is the specification of the demonstrator in COACH input format |
---|
[295] | 29 | defined in the {\NOVERSuseModelSpecification} deliverable. |
---|
[308] | 30 | \itemL{12}{36}{d}{\Sbull}{\bull demonstrator}{3:7:10} |
---|
[291] | 31 | \setMacroInAuxFile{bullAppSpecification} |
---|
| 32 | Validation of the demonstrator, the deliverable is a document |
---|
| 33 | describing the result of the experimentations. |
---|
| 34 | \end{livrable} |
---|
| 35 | % |
---|
| 36 | \subtask{\thales Embedded SoC demonstrator} |
---|
| 37 | The objective of this sub-task is to specify the \thales application and to develop the |
---|
| 38 | high level code. This application is in the domain of surveillance of critical |
---|
| 39 | infrastructures. The objective is to detect and classify the presence of humans in the |
---|
| 40 | restricted area. The algorithm is based on the work of Viola and |
---|
| 41 | Jones~\cite{thales-viola}. It implements in particular a cascade of classifiers |
---|
| 42 | operating on Haar like features, where simple weak classifiers at the beginning of the |
---|
| 43 | cascade reject a majority of void sub-windows, before more complex classifiers |
---|
| 44 | concentrate on potential regions of interest. This application is computation |
---|
| 45 | intensive and also makes an intensive use of binary decision trees to cascade the |
---|
| 46 | filters, which makes it a good candidate to assess the COACH platform. |
---|
| 47 | \\ |
---|
| 48 | Moreover, the higher levels of computing can involve tracking and data fusion between |
---|
| 49 | several camera streams and some other informations. |
---|
| 50 | The targeted system will be composed of one camera connected to a PC. |
---|
| 51 | All the computing part of the application is executed on a FPGA board connected to the |
---|
| 52 | PC. |
---|
| 53 | \begin{livrable} |
---|
| 54 | \itemV{0}{6}{d}{\Sthales}{\thales demonstrator} |
---|
| 55 | \setMacroInAuxFile{trtAppSpecification} |
---|
| 56 | This deliverable is a document that specifies the application. |
---|
[356] | 57 | \itemV{6}{12}{x}{\Sthales}{\thales demonstrator} |
---|
| 58 | The deliverable is the specification of the demonstrator in COACH input format |
---|
| 59 | defined in the {\NOVERSuseModelSpecification} deliverable (milestone M2). |
---|
| 60 | \itemL{12}{27}{x}{\Sthales}{\thales demonstrator}{3:2:2} |
---|
| 61 | Validation of demonstrator for M4 milestone. |
---|
| 62 | The deliverable is the specification of the demonstrator in COACH |
---|
| 63 | milestone M4. |
---|
[291] | 64 | \end{livrable} |
---|
| 65 | % |
---|
| 66 | \subtask{SPEAR-DE adaptation for COACH} |
---|
| 67 | \thales will use its internal software environment tool SPEAR DE to describe the |
---|
| 68 | application. The tool is able to partition and to generate the code for the target. \\ |
---|
[381] | 69 | %%%% |
---|
| 70 | %%%% j'avai cru comprendre que ce serait le contraire, et que TRT souhaitait récupérer le |
---|
| 71 | %%%% découpage en processus (D430) comme entrée de SPEAR-DE. Paul |
---|
| 72 | %%%% |
---|
| 73 | |
---|
[291] | 74 | In this task, we will adapt SPEAR DE to generate the application description input of |
---|
| 75 | COACH framework. We will also describe the three templates of architecture in order to |
---|
| 76 | be able to partition the application on the architecture. |
---|
| 77 | \begin{livrable} |
---|
[356] | 78 | \itemL{6}{27}{x}{\Sthales}{SPEAR-DE adaptation}{6:7:3} |
---|
[291] | 79 | \setMacroInAuxFile{trtSpearde} |
---|
| 80 | Adaptation of SPEAR-DE for COACH framework. |
---|
[367] | 81 | \OtherPartner{0}{12}{\Slip} {0.5:0.5:0.5} |
---|
[291] | 82 | \end{livrable} |
---|
| 83 | % |
---|
[356] | 84 | \subtask{\mds use case} |
---|
[307] | 85 | The goal of the \mds demonstrator will be to experiment and validate the good integration |
---|
| 86 | of the COACH tools into an industrial SoC design flow for critical systems. This demonstrator will be based on |
---|
| 87 | the standard flow defined in the SoCket project and \mds will use a classical SoC platform |
---|
| 88 | based on the LEON processor and which simulation models are available for free (this will |
---|
| 89 | facilitate the further dissemination of the demonstrators to external prospects). |
---|
| 90 | The required prototypes of IP-XACT generators will be specified and implemented; they will be |
---|
| 91 | generic enough or at least customizable in order to be at the basis of the further deployement into |
---|
| 92 | actual design flows. The objectives of this demonstrator are the following: |
---|
[356] | 93 | \begin{itemize} |
---|
| 94 | \item Validate the IP-XACT packaging of the generated SoC. |
---|
| 95 | \item Experiment the integration of the generated SoC into the top level |
---|
| 96 | (TLM or RTL) of a bigger system. |
---|
| 97 | \item Bring a focus on flow capabilities for requirements traceability |
---|
| 98 | from system properties, down to sub-systems implementation. |
---|
| 99 | \end{itemize} |
---|
[291] | 100 | \begin{livrable} |
---|
[308] | 101 | \itemV{0}{12}{d}{\Smds}{Use case} |
---|
[291] | 102 | \setMacroInAuxFile{mdsAppSpecification} |
---|
[307] | 103 | This deliverable is a document that specifies the demonstrator. |
---|
[308] | 104 | \itemV{12}{27}{x}{\Smds}{\mds demonstrator} |
---|
[307] | 105 | This deliverable is the intermediate demonstrator specified in (\mdsAppSpecification). |
---|
[308] | 106 | \itemL{27}{36}{x}{\Smds}{\mds demonstrator}{6:6:6} |
---|
[307] | 107 | This deliverable is the final demonstrator specified in (\mdsAppSpecification). |
---|
[291] | 108 | \end{livrable} |
---|
[356] | 109 | % |
---|
[291] | 110 | \subtask{Evaluation report} |
---|
| 111 | In this sub-task, \mds, \thales and \bull will evaluate the COACH platform. |
---|
| 112 | The evaluation points are: |
---|
| 113 | 1) the ability to generate a whole VHDL of an embedded system on FPGA for an application |
---|
| 114 | mixing control and data flow aspects; |
---|
| 115 | 2) the performance of the generated system in terms of GOPS; |
---|
| 116 | 3) the design time from a high level description. |
---|
| 117 | \begin{livrable} |
---|
[304] | 118 | \itemV{18}{27}{d+x}{\Smds}{Evaluation} |
---|
[300] | 119 | This deliverable written by \Smds, \Sbull and \Sthales is a document |
---|
| 120 | that synthesizes the results got for the demonstrators |
---|
| 121 | (\NOVERSbullAppSpecification, \NOVERStrtAppSpecification, |
---|
| 122 | \NOVERStrtSpearde, \NOVERSmdsAppSpecification) |
---|
| 123 | using the COACH milestone of T0+18. |
---|
[312] | 124 | \itemL{27}{36}{d+x}{\Smds}{Evaluation}{0:3:3} |
---|
[356] | 125 | \OtherPartner{18}{36}{Sbull}{0:4:4.5} |
---|
| 126 | \OtherPartner{18}{36}{Sthales}{0:4:4.5} |
---|
[300] | 127 | This deliverable is a document that validates and evaluates the COACH final release |
---|
| 128 | for the demonstrators. |
---|
| 129 | %(\NOVERSbullAppSpecification, \NOVERStrtAppSpecification, |
---|
| 130 | %\NOVERStrtSpearde, \NOVERSmdsAppSpecification). |
---|
| 131 | The final code of the application demonstrators (\NOVERSbullAppSpecification, |
---|
| 132 | \NOVERStrtAppSpecification) will be provide. |
---|
[291] | 133 | \end{livrable} |
---|
| 134 | \end{workpackage} |
---|