source: anr/task-demonstrator.tex @ 338

Last change on this file since 338 was 334, checked in by coach, 14 years ago

Christophe's modifs

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