Changeset 132 for anr


Ignore:
Timestamp:
Feb 11, 2010, 4:39:19 PM (15 years ago)
Author:
coach
Message:

Minor modifications

Location:
anr
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • anr/section-4.1.tex

    r126 r132  
    5151\xcoach generated by a plugin into the GNU C compiler (GCC).
    5252This allows on the one hand to insure that all the tools will
    53 accept the same C++ description and on the other hand to make possible
     53accept the same C++ description and on the other hand make possible
    5454their chaining. The front-end tools read a \xcoach description and generate
    5555a new \xcoach description that exibits more parallelism or implement
    56 specific instructions for ASIP. The back-end tools read a \xcoach
    57 description and generate a \xcoachplus description. This is a \xcoach
    58 description anotated with hardware information (scheduling, binding) required by
     56specific instructions for ASIP. The back-end tools read an \xcoach
     57description and generate an \xcoachplus description. This is an \xcoach
     58description annotated with hardware information (scheduling, binding) required by
    5959the VHDL and systemC drivers.
    6060Furthermore, the back-end tools uses a macro-cell library (functional and memory
    … …  
    7171\parlf
    7272The project is split into 8 tasks numbered from 1 to 8. There are described
    73 bellow and detailled in section \ref{task-description}.
     73below and detailled in section \ref{task-description}.
    7474\begin{description}
    7575\item[Task-1: \textit{Project management}]
    76     This task relies to the monitoring of the COACH project.
     76    This task relates to the monitoring of the COACH project.
    7777\item[Task-2: \textit{\Backbone}] This task tackles the fundamental points of the
    7878        project such as the defintion of the COACH inputs and outputs,
    … …  
    8080    the design flow.
    8181\item[task-3: \textit{System generation}] This task addresses the prototyping and
    82     the generation of digital system. Apart from HAS that belong to the task 3
     82    the generation of digital system. Apart from HAS that belong to task 3
    8383    and 4, its components are those presented figure~\ref{archi-csg}
    8484    (e.g.  \verb!CSG!, operating systems).
    … …  
    9393    frequency.
    9494\item[Task-6: \textit{PC/FPGA communication middleware}]
    95     This task pools the features dedicated to HPC. The main are the
     95    This task pools the features dedicated to HPC. These are mainly the
    9696    partitioning validation (see figure~\ref{archi-hpc}), the sytem drivers for
    9797    both PC and FPGA-SoC sides, the hardware communication components and
    … …  
    9999\item[Task-7: \textit{Industrial demonstrators}]
    100100    This task groups the demonstrators of the COACH project.
    101     Most of them are industrial applications that will be developped with the COACH
    102     framework.
    103     Others consist in integrating COACH framework as a driver of industrial proprietary
    104     design tools.
     101    Most of them are industrial applications that will be developped within
     102    the COACH framework.
     103    Others consist in integrating the COACH framework as a driver of
     104    industrial proprietary design tools.
    105105\item{Task 8: \textit{Dissemination}}
    106     This task relies to the diffusion of the project results.
     106    This task concerns the diffusion of the project results.
    107107    It mainly consists of the production of 4 COACH releases (\verb!T0+12!, \verb!T0+18!,
    108108    \verb!T0+24! and \verb!T0+36!)
    109     and the publication on a WEB site of a tutorial.
     109    and the publication of a tutorial on a WEB site.
    110110\end{description}
    111111%
    … …  
    117117Figure~\ref{dependence-task} presents the tasks dependencies.
    118118"$T_N \longrightarrow T_M$" means that $T_N$ impacts the $T_M$.
    119 The more bold is the arrow, the more important is the impact.
     119The more bold the arrow, the more important is the impact.
    120120The graph shows:
    121121\begin{itemize}
    122 \item Even that $T4$ and $T5$ functionalities are complementary, their
    123 developments are independent (thanks to \xcoach internal format).
     122\item Notwithstanding that $T4$ and $T5$ functionalities are complementary,
     123their developments are independent (thanks to the \xcoach internal format).
    124124\item $T3$ slightly depends on $T4$ and $T5$. Indeed, $T3$ may works
    125 without $T4$ and $T5$ if we limit to digital systems without hardware
    126 accellerators.
    127 \item $T3$ strongly impacts $T6$ but, $T3$ does not depend at all on
    128 $T6$. So demonstrators ($T7$) of embedded system would not be impacted if
     125without $T4$ and $T5$ if we limit ourselves to digital systems without hardware
     126accelerators.
     127\item $T3$ strongly impacts $T6$ but $T3$ does not depend at all on
     128$T6$. Hence demonstrators ($T7$) of embedded system would not be impacted if
    129129$T6$ would fail. 
    130 \item $T2$ drives all the tasks ($T3$, $T4$, $T5$, $T6$) at the heart of
     130\item $T2$ drives all the tasks ($T3$, $T4$, $T5$, $T6$) and is at the heart of
    131131the COACH project.
    132 \item The demonstrators developped in $T7$, of course, strongly depends on the achievements
     132\item The demonstrators developped in $T7$, of course strongly depends on the achievements
    133133of the previous tasks ($T2$, $T3$, $T4$, $T5$, $T6$).
    134134\item $T8$ and $T1$ respectively depends on and impacts all the other tasks.

  • anr/section-4.2.tex

    r126 r132  
    2020
    2121\item[Management of knowledge, Intellectual Property Right (IPR) and Results Exploitation]
    22 The partners will have to work under the eventual NDA constraints.
     22The partners will have to work under eventual NDA constraints.
    2323Prior Intellectual Property remains property of the concerned partners.
    2424The exploitation of the results obtained in the project and by each partner involved in the consortium will
    25 follow the rules written the articles of the Consortium Agreement accepted and signed by
     25follow the rules written in the articles of the Consortium Agreement accepted and signed by
    2626each partner at most 6 months after the project kick-off.
    2727To manage the exploitation and dissemination plan within the project, six
    … …  
    3232will have to identify namely (and with their address, phone, fax and e-mail):
    3333\begin{itemize}
    34   \item The financial and administrative person authorized and the legal person authorized
    35 or at least the scientific and technical.
    36   \item A complete and detailed list will be communicated to each partner and to public
    37   Authority.
     34  \item The financial and administrative person authorized and the legal
     35person authorized or at least the scientific and technical.
     36
     37  \item A complete and detailed list will be communicated to each partner and to the public Authority.
    3838  \item Mailing lists used by the partners for the day to day communication.
    3939\end{itemize}
    … …  
    6060For this project format and size, a 12 months review by ANR, based on a yearly progress
    6161report incorporating milestones reports and deliverables, seems optimum.
    62 The internal consortium meetings will be six monthly, including a kick-off meeting at the
    63 start of the project, in our eyes the most important of all, as it phases the partners for
    64 the start of the project on.
     62The internal consortium meetings will be every six months, including a kick-off meeting at the
     63start of the project, in our eyes the most important of all, as it phases the partners for the start of the project.
    6564\end{description}

  • anr/section-4.4.tex

    r126 r132  
    6363        Partners have to agree on a convenient exchange format for all tools involved.
    6464        Because all the HAS tools rely on it, the \xcoach format specification is a
    65     crucial step. There are no work-arround but as mentionned in
     65    crucial step. There are no work-around but as mentionned in
    6666    section~\ref{xcoach-problem} (page~\pageref{xcoach-problem}) the five academic partners have worked on it
    67         for a full year and a first document already exists.
     67        for a full year and a preliminary document already exists.
    6868%\item[\xcoachplus format (\novers{\specXcoachDoc},
    6969%      \novers{\specXcoachToSystemC}, \novers{\specXcoachToVhdl})]

  • anr/section-6.1.tex

    r123 r132  
    134134more than 400 researchers, under the umbrella of the CNRS (Centre National de la Recherche Scientifique).
    135135The \og System on Chip \fg Department of LIP6 consists of  80 people, including 40 PHD students.
    136 The research focus on CAD tools and methods for VLSI and System on Chip design.
     136The research focuses on CAD tools and methods for VLSI and System on Chip design.
    137137\parlf
    138138The annual budget is about 3 M{\texteuro}, and 1.5 M{\texteuro} are from research contracts.
    … …  
    161161\xilinx is the world leader in the domain of programmable logic circuits (FPGA).
    162162\xilinx develops on one hand several FPGA architectures (CoolRunner, Spartan and Virtex
    163 families) and in the other hand a software solution allowing exploiting the
     163families) and on the other hand a software solution allowing exploiting the
    164164characteristics of these FPGA.
    165165\parlf
    … …  
    228228
    229229Thales is international, but Europe-centered. Research \& Development activities are
    230 disseminated, and corporate Research and Technology is concentrated in Centres in France,
     230disseminated, and corporate Research and Technology is concentrated in Centers in France,
    231231the United Kingdom and the Netherlands.
    232 The R\&T in Thales emphasizes more particularly on critical information systems,
     232The R\&T in Thales is focused mostly on critical information systems,
    233233processing, control and cognitive systems, and autonomous systems.
    234234
    … …  
    303303For manufacturing and industrialization, \navtel works with ISO certified partners.
    304304The company clients include the CNES, ThalÚs Alenia Space, ThalÚs Communication, EADS,
    305 Eutelsat, AIRBUS, Schlumberger. \navtel participates from the R\&D phase through to the
     305Eutelsat, AIRBUS, Schlumberger. \navtel participates from the R\&D phase up to the
    306306system delivery.
    307307

  • anr/section-6.2.tex

    r119 r132  
    22Université Pierre et Marie Curie.
    33Alain Greiner is the initiator and the main architect of the SoCLib project.
    4 This ANR plat-form for virtual prototyping of MPSoCs involved 6 industrial companies
     4This ANR platform for virtual prototyping of MPSoCs involved 6 industrial companies
    55(including ST Microelectronics and Thales) and ten academic laboratories
    66(5 of them are involved in the Coach project).
    … …  
    1616From 1986 to 1990, he worked for the french BULL company, as team leader,
    1717in charge of designing the Basic Processing Unit for the BULL
    18 DPS7000 computer, the most powerfull mainframe from the family.
     18DPS7000 computer, the most powerfull mainframe of the family.
    1919\item
    2020In 1990, Alain Greiner joined UPMC, as Professor and became the head of the
    21 MASI laboratory in 1994. From 2000, he was the head of the Hardware Department
     21MASI laboratory in 1994. From 2000, he was head of the Hardware Department
    2222of the LIP6 laboratory.
    2323\item
Note: See TracChangeset for help on using the changeset viewer.