Changeset 136


Ignore:
Timestamp:
Feb 13, 2010, 9:41:56 PM (14 years ago)
Author:
coach
Message:

IA: added Indusrial Interest sub section

File:
1 edited

Legend:

Unmodified
Added
Removed
  • anr/section-5.tex

    r134 r136  
    4848
    4949This general approach is supported by a large number of SMEs, as demonstrated by the "letters
    50 of interest" that have been collected during the preparation of the project :
     50of interest" that have been collected during the preparation of the project and presented
     51in annexe~\ref{lettre-soutien}.
     52
     53\subsection{Indusrial Interest in COACH}
     54
     55\subsubsection*{Partner: \textit{\bull}}
     56The team of \bull participating to the COACH project is from the Server Development
     57Department who is in charge of developing hardware for open servers (e.g. NovaScale) and
     58HPC solutions. The main expectation from COACH is to derive a new component (fine-grain
     59FPGA parallelism) to add to existing Bull HPC solutions.
     60
     61\subsubsection*{Partner: \textit{\xilinx}}
     62Computing power potential of our FPGA architectures
     63growing very quickly on one side, and complexity of designs implemented
     64using our FPGAs dramatically increasing on the other side, it is very
     65interesting for us to get high level design methodologies progressing
     66quickly and targetting our FPGAs in the most possible efficient way.
     67\parlf
     68\xilinx goal is to get COACH to generate bitstream optimized as much as possible for
     69\xilinx FPGAs in order to both, validate the methodology on our FPGA families, and ease
     70future work of our customers.
     71
     72\subsubsection*{Partner: \textit{\thales}}
     73\noindent
     74\thales has two main reasons to use the COACH platform:
     75\begin{itemize}
     76  \item The huge increase of the complexity of the systems in particular by their
     77  heterogeneity, raises the issues of design cost and time in the same proportion. The
     78  divisions need a design tool which supports the implementation of the applications from
     79  algorithm description to the executable code on platforms composed of several general
     80  purpose processors and dedicated IPs.
     81  \item The applications are more and more complex and adaptable to the environment which
     82  leads to a mixture of control aspects and data stream computing aspects. A new approach
     83  is necessary to be able to describe this type of application and manage the high level
     84  synthesis of system embedding control and data flow aspects.
     85\end{itemize}
     86\parlf
     87TRT (Thales Research and Technology) has the mission to assess and de-risk the emerging
     88technologies in its domains of expertise. Specifically in COACH, the studied technology is
     89a method and associated tools to make the bridge between application capture at system
     90level and the implementation on heterogeneous distributed computing architectures. The
     91main stake for Thales behind this is the future design process that will be applied to its
     92system teams in the future for the computation-intensive sensor applications. In a context
     93of very instable market of tools for parallel programming, it is important to experiment
     94and demonstrate the candidate technologies.
     95\\
     96In its role of internal dissemination, TRT will make the demonstration of the full design
     97flow within Thales, and will keep available a platform to later evaluate additional
     98applications coming from the Business Units.
     99\\
     100The COACH platform will be used in the new \thales products in which the algorithms are more
     101and more dependent of the environment and have to permanently adapt their behavior in
     102varying environments. The target markets are the critical infrastructures security and
     103border monitoring.
     104
     105\subsubsection*{Partner: \textit{\zied}}
     106
     107\zied is developing a new architecture for embedded system. Our interest in using COACH
     108are:
     109\begin{itemize}
     110  \item firstly, to validate our new architecture by emulating it with COACH.
     111  \item Secondly, to use this emulator and the COACH potential to quickly setup
     112  demonstrator to our customer.
     113\end{itemize}
     114
     115\subsubsection*{Partner: \textit{\navtel}}
     116\navtel has a platform for high performence computation based on ARM processor and FPGAs
     117that embedde coprocessors. Currently, the coprocessors are handmade and their designs
     118constitute an important part of our product cost. We have try free HLS tools to diminish
     119them but the quality of the generated designs was not sufficient to be useable.
     120So our interest in COACH is mainly the HLS tools.
     121
     122\subsubsection*{Industrial supports}
     123The following SMEs demonstrate interest to the COACH project (see the "letters of
     124interest" in annexe~\ref{lettre-soutien}) and will follow the COACH evolution and will
     125evaluate it:
    51126\begin{itemize}
    52127\item \mustbecompleted{Entreprise 1}
     
    57132
    58133\subsection{Management of Intellectual Property}
    59 
    60134A global consortium agreement will be defined during the first six monts of the project.
    61135As already stated, the COACH project has been prepared during one year by a monthly meeting
Note: See TracChangeset for help on using the changeset viewer.