source: anr/task-demonstrator.tex @ 382

\label{task-demonstrator}
\begin{taskinfo}
\let\MDS\enable
\let\BULL\enable
\let\THALES\leader
\let\LIP\enable
\end{taskinfo}
%
\begin{objectif}
This task groups the demonstrators of the COACH project.
The demonstrators cover various domains and application types to drive
the specification choices and to check most of the COACH features.
\end{objectif}
%
\begin{workpackage}
%
\subtask{\bull HPC demonstrator}
    The application that \bull proposes is HPC oriented.
    The domain of the application is the treatment of medical images (image noise
    reduction and segmentation or registration).
    Our expectation from the COACH project is to enhance the \bull HPC solutions that
    are currently based on multi-cores and GPUs with fine grain parallelism on FPGA.
    \begin{livrable}
      \itemV{0}{6}{d}{\Sbull}{\bull demonstrator}
        The deliverable is a document that describes the application that will be used as
        demonstrator.
      \itemV{6}{12}{x}{\Sbull}{\bull demonstrator}
        The deliverable is the specification of the demonstrator in COACH input format
        defined in the {\NOVERSuseModelSpecification} deliverable.
      \itemL{12}{36}{d}{\Sbull}{\bull demonstrator}{3:7:10}
        \setMacroInAuxFile{bullAppSpecification}
        Validation of the demonstrator, the deliverable is a document
        describing the result of the experimentations.
    \end{livrable}
%
\subtask{\thales Embedded SoC demonstrator}
    The objective of this sub-task is to specify the \thales application and to develop the
    high level code.  This application is in the domain of surveillance of critical
    infrastructures. The objective is to detect and classify the presence of humans in the
    restricted area. The algorithm is based on the work of Viola and
    Jones~\cite{thales-viola}. It implements in particular a cascade of classifiers
    operating on Haar like features, where simple weak classifiers at the beginning of the
    cascade reject a majority of void sub-windows, before more complex classifiers
    concentrate on potential regions of interest. This application is computation
    intensive and also makes an intensive use of binary decision trees to cascade the
    filters, which makes it a good candidate to assess the COACH platform.
    \\
    Moreover, the higher levels of computing can involve tracking and data fusion between
    several camera streams and some other informations.
    The targeted system will be composed of one camera connected to a PC.
    All the computing part of the application is executed on a FPGA board connected to the
    PC.
    \begin{livrable}
      \itemV{0}{6}{d}{\Sthales}{\thales demonstrator}
        \setMacroInAuxFile{trtAppSpecification}
        This deliverable is a document that specifies the application.
      \itemV{6}{12}{x}{\Sthales}{\thales demonstrator}
        The deliverable is the specification of the demonstrator in COACH input format
        defined in the {\NOVERSuseModelSpecification} deliverable (milestone M2).
      \itemL{12}{27}{x}{\Sthales}{\thales demonstrator}{3:2:2}
        Validation of demonstrator for M4 milestone.
        The deliverable is the specification of the demonstrator in COACH
        milestone M4.
    \end{livrable}
%
\subtask{SPEAR-DE adaptation for COACH}
    \thales will use its internal software environment tool SPEAR DE to describe the
    application. The tool is able to partition and to generate the code for the target. \\
%%%%
%%%% j'avai cru comprendre que ce serait le contraire, et que TRT souhaitait récupérer le
%%%% découpage en processus (D430) comme entrée de SPEAR-DE. Paul
%%%%

    In this task, we will adapt SPEAR DE to generate the application description input of
    COACH framework. We will also describe the three templates of architecture in order to
    be able to partition the application on the architecture.
    \begin{livrable}
      \itemL{6}{27}{x}{\Sthales}{SPEAR-DE adaptation}{6:7:3}
        \setMacroInAuxFile{trtSpearde}
        Adaptation of SPEAR-DE for COACH framework.
        \OtherPartner{0}{12}{\Slip}   {0.5:0.5:0.5}
    \end{livrable}
%
\subtask{\mds use case}
    The goal of the \mds demonstrator will be to experiment and validate the good integration
    of the COACH tools into an industrial SoC design flow for critical systems. This demonstrator will be based on 
    the standard flow defined in the SoCket project and \mds will use a classical SoC platform
    based on the LEON processor and which simulation models are available for free (this will
    facilitate the further dissemination of the demonstrators to external prospects). 
    The required prototypes of IP-XACT generators will be specified and implemented; they will be 
    generic enough or at least customizable in order to be at the basis of the further deployement into 
    actual design flows. The objectives of this demonstrator are the following:
    \begin{itemize}
          \item Validate the IP-XACT packaging of the generated SoC.
          \item Experiment the integration of the generated SoC into the top level
      (TLM or RTL) of a bigger system.
          \item Bring a focus on flow capabilities for requirements traceability
      from system properties, down to sub-systems implementation.
    \end{itemize}
    \begin{livrable}
      \itemV{0}{12}{d}{\Smds}{Use case}
        \setMacroInAuxFile{mdsAppSpecification}
        This deliverable is a document that specifies the demonstrator.
      \itemV{12}{27}{x}{\Smds}{\mds demonstrator}
        This deliverable is the intermediate demonstrator specified in (\mdsAppSpecification).
      \itemL{27}{36}{x}{\Smds}{\mds demonstrator}{6:6:6}
        This deliverable is the final demonstrator specified in (\mdsAppSpecification).
    \end{livrable}
%
\subtask{Evaluation report}
    In this sub-task, \mds, \thales and \bull will evaluate the COACH platform.
    The evaluation points are:
    1) the ability to generate a whole VHDL of an embedded system on FPGA for an application
    mixing control and data flow aspects;
    2) the performance of the generated system in terms of GOPS;
    3) the design time from a high level description.
    \begin{livrable}
      \itemV{18}{27}{d+x}{\Smds}{Evaluation}
        This deliverable written by \Smds, \Sbull and \Sthales is a document
        that synthesizes the results got for the demonstrators
        (\NOVERSbullAppSpecification, \NOVERStrtAppSpecification,
        \NOVERStrtSpearde, \NOVERSmdsAppSpecification)
        using the COACH milestone of T0+18.
      \itemL{27}{36}{d+x}{\Smds}{Evaluation}{0:3:3}
        \OtherPartner{18}{36}{Sbull}{0:4:4.5}
        \OtherPartner{18}{36}{Sthales}{0:4:4.5}
        This deliverable is a document that validates and evaluates the COACH final release
        for the demonstrators.
        %(\NOVERSbullAppSpecification, \NOVERStrtAppSpecification,
        %\NOVERStrtSpearde, \NOVERSmdsAppSpecification).
        The final code of the application demonstrators (\NOVERSbullAppSpecification,
        \NOVERStrtAppSpecification) will be provide.
    \end{livrable}
\end{workpackage}