Changeset 155

Timestamp:

Feb 15, 2010, 9:57:43 AM (14 years ago)

Author:

coach

Message:

INRIA/COMPSYS -> LIP

Location:

anr

Files:

• anr.tex (modified) (1 diff)
• section-4.4.tex (modified) (7 diffs)
• section-6.1.tex (modified) (3 diffs)
• section-7.tex (modified) (13 diffs)
• task-1.tex (modified) (2 diffs)
• task-2.tex (modified) (5 diffs)
• task-4.tex (modified) (2 diffs)
• task-5.tex (modified) (2 diffs)
• task-6.tex (modified) (6 diffs)

anr/anr.tex

@@ -49 +49 @@
 \def\inria{INRIA\xspace}          \def\Sinria{\Sformat{INRIA}\xspace}
 \def\irisa{INRIA/CAIRN\xspace}    \def\Sirisa{\Sformat{INCN}\xspace}
-\def\lip{INRIA/COMPSYS\xspace}    \def\Slip{\Sformat{INCS}\xspace}
+\def\lip{LIP\xspace}              \def\Slip{\Sformat{LIP}\xspace}
 \def\tima{TIMA\xspace}            \def\Stima{\Sformat{TIMA}\xspace}
 \def\ubs{LAB-STICC\xspace}        \def\Subs{\Sformat{UBS}\xspace}

anr/section-4.4.tex

@@ -11 +11 @@
 %\hspace*{-.6cm}
 %\input{gantt.tex}
-%\caption{\label{gantt}Gantt diagram of delivrables}
+%\caption{\label{gantt}Gantt diagram of deliverables}
 %\end{figure}
 
@@ -17 +17 @@
 \hspace*{-.6cm}\vspace{-1.5cm}
 \input{gantt1.tex}
-\caption{\label{gantt1}Gantt diagram of delivrables (task-1 to task-4)}
+\caption{\label{gantt1}Gantt diagram of deliverables (task-1 to task-4)}
 \end{figure}
 
@@ -23 +23 @@
 \hspace*{-.6cm}\vspace{-1.5cm}
 \input{gantt2.tex}
-\caption{\label{gantt2}Gantt diagram of delivrables (task-5 to task-8)}
+\caption{\label{gantt2}Gantt diagram of deliverables (task-5 to task-8)}
 \end{figure}
 
@@ -29 +29 @@
 Before the final release (T0+36), there are 4 milestones (red lines on the figures) at
 $T0+6$, $T0+12$, $T0+18$ and $T0+24$ that are rendez-vous points of the precedent
-delivrables.
+deliverables.
 \begin{description}
 \item[Milestone 1 ($T0+6$)] Specification of COACH inputs, of the \xcoach format and of
@@ -54 +54 @@
 \end{description}
 This organisation allows to advance globally the project step by step mixing development
-and demonstrator delivrables.
+and demonstrator deliverables.
 Hence, demonstrator feed-back will arrive early and so the risk to point out incompatibility
 at the integration phase is significantly reduced.
@@ -90 +90 @@
 \end{description}
 \parlf
-Finally the list of all the delivrables is presented on figure~\ref{all-delivrables}.
+Finally the list of all the deliverables is presented on figure~\ref{all-delivrables}.
 \begin{figure}\leavevmode\center
 {
@@ -107 +107 @@
 \end{minipage}
 }
-\caption{\label{all-delivrables}All the delivrables}
+\caption{\label{all-delivrables}All the deliverables}
 %\end{scriptsize}
 \end{figure}

anr/section-6.1.tex

@@ -1 +1 @@
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\subsubsection{\inria (CAIRN \& COMPSYS teams)}
+\subsubsection{\inria CAIRN}
 
 Inria, the French national institute for research in computer science
@@ -38 +38 @@
 (joint laboratories such as LIAMA, associated research teams, training
 and internship programs).
-Two \inria project-teams participate to this project.
-\begin{itemize}
-\item CAIRN. The CAIRN group of INRIA Rennes -- Bretagne Atlantique study reconfigurable
+
+The CAIRN group of INRIA Rennes -- Bretagne Atlantique study reconfigurable
 system-on-chip, i.e. hardware systems whose configuration may change before or even during
 execution. To this end, CAIRN has 13 permanent researchers and a variable number of PhD
@@ -49 +48 @@
 exploration of the interaction between algorithms and architectures.
 CAIRN is a joint team with CNRS, INSA of Rennes, University of Rennes 1 and ENS Cachan.
-\item COMPSYS. The Compsys group of Ecole Normale Sup\'erieure de Lyon is a project-team
+
+\subsubsection{ENS Lyon LIP/Compsys}
+The Compsys group of Ecole Normale Sup\'erieure de Lyon is a project-team
 of INRIA Rh\^one-Alpes and a part of Laboratoire de l'Informatique du
 Parall\'elisme (LIP), UMR 5668 of CNRS. It has four permanent researchers
 and a variable number of PhD students and post-docs. Its field of
 expertise is compilation for embedded system, optimizing compilers
-and automatic parallelization. It  has authored or contributed to
+and automatic parallelization. Its members were among the initiators
+of the polyhedral model for automatic parallelization and program
+optimization generally. It  has authored or contributed to
 several well known libraries for linear programming, polyhedra manipulation
 and optimization in general. It has strong industrial cooperations, notably
 with ST Microelectronics and \thales.
-\end{itemize}
 
 

anr/section-7.tex

@@ -6 +6 @@
 \begin{figure}\leavevmode\center
 \input{table_inria_cairn_full.tex}
-\caption{\label{ress-detail-irisa}Man power in $mm$ for the delivrables of \irisa.}
+\caption{\label{ress-detail-irisa}Man power in $mm$ for the deliverables of \irisa.}
 \end{figure}
 \begin{description}
@@ -19 +19 @@
 
 The table below summarizes the manpower by tasks for both permanent and non-permanent
-personnels. The detail by delivrables is given in figure~\ref{ress-detail-irisa}.
+personnels. The detail by deliverables is given in figure~\ref{ress-detail-irisa}.
 The non-permanent personnels costs represent \mustbecompleted{??\%} of the personnal
 costs. The requested funding for non permanent personnels is 100\% of
@@ -43 +43 @@
 No specific equipment acquisition. 
 \item [Personnel costs]
-The faculty members involved in the project are a professor at ENS
+The faculty members involved in the project are an emeritus professor at ENS
 Lyon (Paul Feautrier) and a research associate (CR2) at INRIA
 Rh\^one-Alpes (Christophe Alias). The non-permanent personal required
@@ -52 +52 @@
 techniques and to produce a working implementation.
 
-The table below summarizes the man power by delivrables and tasks for both permanent and
+The table below summarizes the man power by deliverables and tasks for both permanent and
 non-permanent personnels.
 The non-permanent personnels costs represent \mustbecompleted{??\%} of the personnal
@@ -75 +75 @@
 \begin{figure}\leavevmode\center
 \input{table_tima_full.tex}
-\caption{\label{ress-detail-tima}Man power in $mm$ for the delivrables of \tima.}
+\caption{\label{ress-detail-tima}Man power in $mm$ for the deliverables of \tima.}
 \end{figure}
 \begin{description}
@@ -97 +97 @@
 
 The table below sumarizes the man power by task for both permanent and non-permanent
-personnels. The detail by delivrables is given in figure~\ref{ress-detail-tima}.
+personnels. The detail by deliverables is given in figure~\ref{ress-detail-tima}.
 The requested funding for personnels represent 50\% of the total personnal costs.
 The requested funding for non permanent personnels is 85\% of the total ANR
@@ -117 +117 @@
 \begin{figure}\leavevmode\center
 \input{table_ubs_full.tex}
-\caption{\label{ress-detail-ubs}Man power in $mm$ for the delivrables of \ubs.}
+\caption{\label{ress-detail-ubs}Man power in $mm$ for the deliverables of \ubs.}
 \end{figure}
 
@@ -131 +131 @@
 
 The table below sumarizes the man power by task for both permanent and non-permanent
-personnels. The detail by delivrables is given in figure~\ref {ress-detail-ubs}.
+personnels. The detail by deliverables is given in figure~\ref {ress-detail-ubs}.
 The non-permanent personnels costs represent 50\% of the personnal costs.
 The requested funding for non permanent personnels is about 83\% of the total ANR
@@ -152 +152 @@
 \begin{figure}\leavevmode\center
 \input{table_upmc_full.tex}
-\caption{\label{ress-detail-upmc}Man power in $mm$ for the delivrables of \upmc.}
+\caption{\label{ress-detail-upmc}Man power in $mm$ for the deliverables of \upmc.}
 \end{figure}
 \begin{description}
@@ -166 +166 @@
     for senior researchers (post-doc or research engineers).
     The table below sumarizes the man power by task for both permanent  and non-permanent
-    personnels. The detail by delivrables is given in figure~\ref{ress-detail-upmc}.
+    personnels. The detail by deliverables is given in figure~\ref{ress-detail-upmc}.
     The non-permanent personnels costs represent 50\% of the personnal costs.
     The requested funding for non permanent personnels is 79\% of the total ANR
@@ -187 +187 @@
 \begin{figure}\leavevmode\center
 \input{table_xilinx_full.tex}
-\caption{\label{ress-detail-xilinx}Man power in $mm$ for the delivrables of \xilinx.}
+\caption{\label{ress-detail-xilinx}Man power in $mm$ for the deliverables of \xilinx.}
 \end{figure}
 \begin{description}
@@ -194 +194 @@
 \item[Personnel costs]
     \xilinx employees involved in the project are permanent Software Engineers.
-    The detail by delivrables is given in figure~\ref{ress-detail-xilinx} and
+    The detail by deliverables is given in figure~\ref{ress-detail-xilinx} and
     a sumary by task in the following table.
     \begin{center}\input{table_xilinx_short.tex}\end{center}
@@ -267 +267 @@
     A permanent engineer will be assigned on average 1/3 time for
         all the duration of the project.
-    The table below shows the estimated manpower cost in months for the delivrables.
+    The table below shows the estimated manpower cost in months for the deliverables.
     \begin{center}\input{table_navtel_full.tex}\end{center}
 \item[Subcontracting]

anr/task-1.tex

@@ -23 +23 @@
         This document contains the general description of the framework, the design flow and the
         description of the architectural templates.
-        It refers to the HAS specification (delivrable {\specHasManual}) and 
-        to the CSG specifcation (delivrable \specCsgManual) for the COACH input
+        It refers to the HAS specification (deliverable {\specHasManual}) and 
+        to the CSG specifcation (deliverable \specCsgManual) for the COACH input
         descriptions.
     \itemL{6}{12}{d}{\Supmc}{COACH specification}{1:0:0} \setMacroInAuxFile{specGenManual}
-        The final version of the {\specGenManualI} delivrable updated with the \mustbecompleted{FIXME:: first ?}
+        The final version of the {\specGenManualI} deliverable updated with the \mustbecompleted{FIXME:: first ?}
             feed-backs of the demonstrator \STs.
     \itemV{0}{6}{d}{\Stima}{CSG specification} \setMacroInAuxFile{specCsgManualI}
@@ -38 +38 @@
         synthesis.
     \itemL{6}{12}{d}{\Stima}{CSG specification}{1:0:0} \setMacroInAuxFile{specCsgManual}
-        The final version of the {\specGenManualI} delivrable updated with the \mustbecompleted{FIXME:: first ?}
+        The final version of the {\specGenManualI} deliverable updated with the \mustbecompleted{FIXME:: first ?}
             feed-backs of the demonstrator \STs.
     \itemV{0}{6}{d}{\Subs}{HAS specification} \setMacroInAuxFile{specHasManualI}
         The first version of the HAS (Hardware Accelerator Synthesis) specification.
         It specifies how tasks must be written (C/C++ subset) and how
-        communication schemes defined in the {\specCsgManual} delivrable must be described for
+        communication schemes defined in the {\specCsgManual} deliverable must be described for
         coprocessor synthesis.
     \itemL{6}{12}{d}{\Subs}{HAS specification}{1:0:0} \setMacroInAuxFile{specHasManual}
-        The final version of the {\specGenManualI} delivrable updated with the \mustbecompleted{FIXME:: first ?}
+        The final version of the {\specGenManualI} deliverable updated with the \mustbecompleted{FIXME:: first ?}
             feed-backs of the demonstrator \STs.
     \end{livrable}

anr/task-2.tex

@@ -21 +21 @@
 \item the specification of enhanced communication schemes and their sofware and hardware implementations.
 \end{itemize}
-This task being based on the SocLib platform, a first release will be delivrable at $T0+12$
+This task being based on the SocLib platform, a first release will be delivered at $T0+12$
 to allow the demonstrators to start working.
 This release will include the standard communication schemes (base on SocLib MWMR component)
@@ -70 +70 @@
     \itemL{18}{24}{h}{\Stima}{\xilinx architecture}{9:9:0}
         The synthesizable VHDL description of the MWMR component corresponding to the
-        SystemC module of the former delivrable (\csgXilinxSystemC).
+        SystemC module of the former deliverable (\csgXilinxSystemC).
     \itemL{24}{27}{d}{\Sxilinx}{\xilinx RTL optimisation (3)}{0:0:1.5}
        This deliverable consists in optimizing the MWMR VHDL description (deliverable
@@ -83 +83 @@
     \itemL{18}{24}{h}{\Sirisa}{\altera architecture}{6:6:0}
         The synthesizable VHDL description of the MWMR component corresponding to the
-        SystemC module of the former delivrable (\csgAlteraSystemC);
+        SystemC module of the former deliverable (\csgAlteraSystemC);
     \itemV{6}{12}{d}{\Subs}{UBS communication adapter}
        \setMacroInAuxFile{gautCOMMoptimization}
@@ -102 +102 @@
 \subtask This \ST consists of the configuration of the SocLib MUTEKH and DNA operating
     system and the development of drivers for the hardware architectural templates
-    and enhanced communication schemes defined in \novers{\specCsgManual} delivrable.
+    and enhanced communication schemes defined in \novers{\specCsgManual} deliverable.
     For the \altera and \xilinx architectural templates, the OSs must also be ported on
     the NIOS2 and MICROBLAZE processors.
     \begin{livrable}
     \itemV{6}{8}{x}{\Supmc}{MUTEKH OS}
-        The drivers required for the first CSG milestone (delivrable \csgCoachArch).
+        The drivers required for the first CSG milestone (deliverable \csgCoachArch).
     \itemV{8}{18}{x}{\Supmc}{MUTEKH 0S}
         The drivers required for the second CSG milestone ({\csgPrototypingOnly}).
@@ -115 +115 @@
         Porting of MUTEKH OS on the NIOS2 and MICROBLAZE processors.
     \itemV{6}{8}{x}{\Stima}{DNA OS}
-        The drivers required for the first CSG milestone (delivrable \csgCoachArch).
+        The drivers required for the first CSG milestone (deliverable \csgCoachArch).
     \itemV{8}{18}{x}{\Stima}{DNA 0S}
         The drivers required for the second CSG milestone ({\csgPrototypingOnly}).

anr/task-4.tex

@@ -70 +70 @@
         and also supports new constraints and objectives defined in
         \mustbecompleted{FIXME:USB utilise une macro svp: \ST1-1}
-        \mustbecompleted{FIXME:UBS: quel delivrable ??}.
+        \mustbecompleted{FIXME:UBS: quel deliverable ??}.
     \itemV{6}{18}{d}{\Subs}{Design Space Exploration}{0:0:0}
         \mustbecompleted{FIXME:UBS  GAUT enhancement 3 serait peut-etre meilleur}
@@ -78 +78 @@
     \itemL{18}{30}{x}{\Subs}{Design Space Exploration}{0:0:0}
         Release of the GAUT software that supports the features defined in
-        \mustbecompleted{FIXME:UBS: macro ????} delivrable.
+        \mustbecompleted{FIXME:UBS: macro ????} deliverable.
     \end{livrable}
 \subtask In FPGA-SoC, the frequency is given by the processor(s) and the system BUS. The coprocessors

anr/task-5.tex

@@ -53 +53 @@
       \itemL{6}{12}{x}{\Supmc}{HPC partionning helper}{1:0:0}
         \setMacroInAuxFile{hpcCommHelper}
-        A library implementing the communication API defined in the {\hpcCommApi} delivrable.
+        A library implementing the communication API defined in the {\hpcCommApi} deliverable.
         This library is dedicated to help the end-user to partition an applicattion for
         HPC.
@@ -109 +109 @@
         \xilinx will work with \tima in order to better take into account during
         partitioning decisions specific constraints due to partial reconfiguration process.
-        The delivrable is a document describing the \xilinx specific constraints.
+        The deliverable is a document describing the \xilinx specific constraints.
     \end{livrable}
 %\item This \ST is the delivery of 2 PCI/X \mustbecompleted{FIXME: Stratix4} FPGA board

anr/task-6.tex

@@ -52 +52 @@
       \itemV{0}{6}{d}{\Sthales}{\thales demonstrator (step 1)}
         \setMacroInAuxFile{trtAppSpecification}
-        This delivrable is a document that specifies the application.
+        This deliverable is a document that specifies the application.
       \itemL{6}{12}{x}{\Sthales}{\thales demonstrator (step 1)}{4:0:0}
-        This delivrable is the code of the application spcecified former
-        delivrable (\trtAppSpecification).
+        This deliverable is the code of the application spcecified former
+        deliverable (\trtAppSpecification).
     \end{livrable}
 
@@ -76 +76 @@
     \begin{livrable}
       \itemV{18}{24}{d+x}{\Sthales}{\thales demonstrator (step 2)}
-        This delivrable is a document describing the result got for the application
+        This deliverable is a document describing the result got for the application
         (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+18.
         The updated code of the application will be also provide.
       \itemV{24}{30}{d+x}{\Sthales}{\thales demonstrator (step 2)}
-        This delivrable is a document describing the result got for the application
+        This deliverable is a document describing the result got for the application
         (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+24.
         The updated code of the application will be also provide.
       \itemL{30}{36}{d+x}{\Sthales}{\thales demonstrator (step 2)}{0:5:5}
-        This delivrable is a document that validates and evaluates COACH (final release)
+        This deliverable is a document that validates and evaluates COACH (final release)
         for the \thales demonstrators (\trtAppSpecification).
         The updated code of the application will be also provide.
@@ -112 +112 @@
         FLEXRAS will use IPs provided by LIP6 (vhdl models of SoCLIB) and its eFPGA IP to
         generate the SoC architecture.
-        This delivrable is a document that describes this architecture.
+        This deliverable is a document that describes this architecture.
       \itemL{6}{18}{h}{\Szied}{eFPGA/VCI component}{3.6:3.6:0}
         FLEXRAS has to adapt the eFPGA interface to connect it to the VCI bus.
-        This delivrable is a VHDL description.
+        This deliverable is a VHDL description.
 %      \itemL{12}{18}{x}{\Szied}{bitstream loader port}{0:3.6:0}
 %        Port of the bitstream loader to the MUTEKH operating system.
@@ -122 +122 @@
         throught a basic application.
         This applicattion will containt 3 communicating tasks under the COACH format specified
-        in {\novers{\specGenManual}} delivrable.
+        in {\novers{\specGenManual}} deliverable.
         The first one is a hardware task generated by the HAS tools and transformed into
         a bit stream by the \zied tools.
@@ -129 +129 @@
         The third is a software task that communicates with the hw task for testing it.
       \itemL{24}{30}{x}{\Szied}{eFPGA characterisation}{0:0:2.4}
-        This delivrable is a file under the format defined by the delivrable
+        This deliverable is a file under the format defined by the deliverable
         {\specMacroCell} that characterizes the eFPGA. This will allow the COACH HLS tools
         to take into account the eFPGA delays.
       \itemL{30}{36}{d}{\Szied}{\zied evaluation}{0:0:3.6}
-        This delivrable is a document that describes the tests, the validation and the
+        This deliverable is a document that describes the tests, the validation and the
         evaluation of COACH with the \zied architecture and tools.
     \end{livrable}
@@ -162 +162 @@
     \itemL{18}{36}{d}{\Snavtel}{\navtel evaluation}{0:2:4}
                 \navtel will test the COACH HLS tools on the processing units that are described
-        in the {\navtelSpecification} delivrable.
+        in the {\navtelSpecification} deliverable.
                 A document will be written that describes the results obtained taking into
         account: 1) the performance in terms of space, 2) the performance in terms of