1 | \begin{taskinfo} |
---|
2 | \let\BULL\enable |
---|
3 | \let\THALES\leader |
---|
4 | \let\NAVTEL\enable |
---|
5 | \let\ZIED\enable |
---|
6 | \end{taskinfo} |
---|
7 | % |
---|
8 | \begin{objectif} |
---|
9 | This task groups the demonstrators of the COACH project. |
---|
10 | The demonstrators cover various domains and application types to drive |
---|
11 | the specification choices and to check most of the COACH features. |
---|
12 | \end{objectif} |
---|
13 | % |
---|
14 | \begin{workpackage} |
---|
15 | \subtask{\bull HPC demonstrator} |
---|
16 | The application that \bull proposes is HPC oriented. |
---|
17 | The domain of the application is the treatment of medical images (image noise |
---|
18 | reduction and segmentation or registration). |
---|
19 | Our expectation from COACH project is to enhance the \bull HPC solutions that |
---|
20 | are currently based on multi-cores and GPUs with fine grain parallelism on FPGA. |
---|
21 | \begin{livrable} |
---|
22 | \itemV{0}{6}{d}{\Sbull}{\bull demonstrator} |
---|
23 | The deliverable is a document that describes the application that will be use as |
---|
24 | demonstrator. |
---|
25 | \itemV{6}{12}{x}{\Sbull}{\bull demonstrator} |
---|
26 | The deliverable is the specification of the demonstrator in COACH input format |
---|
27 | defined in the \novers{\useModelSpecification} deliverable. |
---|
28 | \itemL{12}{36}{d}{\Sbull}{\bull demonstrator}{2:6:10} |
---|
29 | Validation of the demonstrator, the deliverable is a document |
---|
30 | describing the result of the experimentations. |
---|
31 | \end{livrable} |
---|
32 | |
---|
33 | \subtask{\TRT Embedded SoC demonstrator} |
---|
34 | The objective of this sub-task is to specify the \TRT application and to develop the |
---|
35 | high level code. This application is in the domain of surveillance of critical |
---|
36 | infrastructures. The objective is to detect and classify the presence of humans in the |
---|
37 | restricted area. The algorithm is based on the work of Viola and |
---|
38 | Jones~\cite{thales-viola}. It implements in particular a cascade of classifiers |
---|
39 | operating on Haar like features, where simple weak classifiers at the beginning of the |
---|
40 | cascade reject a majority of void sub-windows, before more complex classifiers |
---|
41 | concentrate on potential regions of interest. This application is computation |
---|
42 | intensive and also makes an intensive use of binary decision trees to cascade the |
---|
43 | filters, which makes it a good candidate to assess the COACH platform. |
---|
44 | \\ |
---|
45 | Moreover, the higher levels of computing can involve tracking and data fusion between |
---|
46 | several camera streams and some other informations. |
---|
47 | The targeted system will be composed of one camera connected to a PC. |
---|
48 | All the computing part of the application is executed on a FPGA board connected to the |
---|
49 | PC. |
---|
50 | \begin{livrable} |
---|
51 | \itemV{0}{6}{d}{\Sthales}{\thales demonstrator (step 1)} |
---|
52 | \setMacroInAuxFile{trtAppSpecification} |
---|
53 | This deliverable is a document that specifies the application. |
---|
54 | \itemL{6}{12}{x}{\Sthales}{\thales demonstrator (step 1)}{4:0:0} |
---|
55 | This deliverable is the code of the application specified former |
---|
56 | deliverable (\trtAppSpecification). |
---|
57 | \end{livrable} |
---|
58 | |
---|
59 | \subtask{SPEAR-DE adaptation for COACH} |
---|
60 | \TRT will use its internal software environment tool SPEAR DE to describe the |
---|
61 | application. The tool is able to partition and to generate the code for the target. \\ |
---|
62 | In this task, we will adapt SPEAR DE to generate the application description input of |
---|
63 | COACH framework. We will also describe the three templates of architecture in order to |
---|
64 | be able to partition the application on the architecture. |
---|
65 | \begin{livrable} |
---|
66 | \itemL{6}{18}{x}{\Sthales}{SPEAR-DE adaptation}{6:7:0} |
---|
67 | \setMacroInAuxFile{trtSpearde} |
---|
68 | Adaptation of SPEAR-DE for COACH framework. |
---|
69 | \end{livrable} |
---|
70 | |
---|
71 | \subtask{\mds use case} |
---|
72 | \mds will use ................. |
---|
73 | \begin{livrable} |
---|
74 | \itemL{6}{18}{x}{\Smds}{Use case}{6:7:0} |
---|
75 | \setMacroInAuxFile{trtSpearde} |
---|
76 | Adaptation of SPEAR-DE for COACH framework. |
---|
77 | \end{livrable} |
---|
78 | |
---|
79 | \subtask{Evaluation report} |
---|
80 | % FIXME: AJOUTER une evaluation de BULL ET MDS |
---|
81 | In this sub-task, \TRT will evaluate the COACH platform. In particular, \TRT will verify |
---|
82 | its ability to generate a whole VHDL of an embedded system on FPGA for an application |
---|
83 | mixing control and data flow aspects. \TRT will evaluate the performance of the |
---|
84 | generated system in terms of GOPS, and the design time from a high level description. |
---|
85 | \begin{livrable} |
---|
86 | \itemV{18}{24}{d+x}{\Sthales}{\thales demonstrator (step 2)} |
---|
87 | This deliverable is a document describing the result got for the application |
---|
88 | (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+18. |
---|
89 | The updated code of the application will be also provide. |
---|
90 | \itemV{24}{30}{d+x}{\Sthales}{\thales demonstrator (step 2)} |
---|
91 | This deliverable is a document describing the result got for the application |
---|
92 | (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+24. |
---|
93 | The updated code of the application will be also provide. |
---|
94 | \itemL{30}{36}{d+x}{\Sthales}{\thales demonstrator (step 2)}{0:5:5} |
---|
95 | This deliverable is a document that validates and evaluates COACH (final release) |
---|
96 | for the \thales demonstrators (\trtAppSpecification). |
---|
97 | The updated code of the application will be also provide. |
---|
98 | \end{livrable} |
---|
99 | |
---|
100 | \end{workpackage} |
---|