- Timestamp:
- Feb 15, 2010, 9:57:43 AM (15 years ago)
- Location:
- anr
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/anr.tex
r150 r155 49 49 \def\inria{INRIA\xspace} \def\Sinria{\Sformat{INRIA}\xspace} 50 50 \def\irisa{INRIA/CAIRN\xspace} \def\Sirisa{\Sformat{INCN}\xspace} 51 \def\lip{ INRIA/COMPSYS\xspace} \def\Slip{\Sformat{INCS}\xspace}51 \def\lip{LIP\xspace} \def\Slip{\Sformat{LIP}\xspace} 52 52 \def\tima{TIMA\xspace} \def\Stima{\Sformat{TIMA}\xspace} 53 53 \def\ubs{LAB-STICC\xspace} \def\Subs{\Sformat{UBS}\xspace} -
anr/section-4.4.tex
r149 r155 11 11 %\hspace*{-.6cm} 12 12 %\input{gantt.tex} 13 %\caption{\label{gantt}Gantt diagram of deliv rables}13 %\caption{\label{gantt}Gantt diagram of deliverables} 14 14 %\end{figure} 15 15 … … 17 17 \hspace*{-.6cm}\vspace{-1.5cm} 18 18 \input{gantt1.tex} 19 \caption{\label{gantt1}Gantt diagram of deliv rables (task-1 to task-4)}19 \caption{\label{gantt1}Gantt diagram of deliverables (task-1 to task-4)} 20 20 \end{figure} 21 21 … … 23 23 \hspace*{-.6cm}\vspace{-1.5cm} 24 24 \input{gantt2.tex} 25 \caption{\label{gantt2}Gantt diagram of deliv rables (task-5 to task-8)}25 \caption{\label{gantt2}Gantt diagram of deliverables (task-5 to task-8)} 26 26 \end{figure} 27 27 … … 29 29 Before the final release (T0+36), there are 4 milestones (red lines on the figures) at 30 30 $T0+6$, $T0+12$, $T0+18$ and $T0+24$ that are rendez-vous points of the precedent 31 deliv rables.31 deliverables. 32 32 \begin{description} 33 33 \item[Milestone 1 ($T0+6$)] Specification of COACH inputs, of the \xcoach format and of … … 54 54 \end{description} 55 55 This organisation allows to advance globally the project step by step mixing development 56 and demonstrator deliv rables.56 and demonstrator deliverables. 57 57 Hence, demonstrator feed-back will arrive early and so the risk to point out incompatibility 58 58 at the integration phase is significantly reduced. … … 90 90 \end{description} 91 91 \parlf 92 Finally the list of all the deliv rables is presented on figure~\ref{all-delivrables}.92 Finally the list of all the deliverables is presented on figure~\ref{all-delivrables}. 93 93 \begin{figure}\leavevmode\center 94 94 { … … 107 107 \end{minipage} 108 108 } 109 \caption{\label{all-delivrables}All the deliv rables}109 \caption{\label{all-delivrables}All the deliverables} 110 110 %\end{scriptsize} 111 111 \end{figure} -
anr/section-6.1.tex
r142 r155 1 1 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 2 \subsubsection{\inria (CAIRN \& COMPSYS teams)}2 \subsubsection{\inria CAIRN} 3 3 4 4 Inria, the French national institute for research in computer science … … 38 38 (joint laboratories such as LIAMA, associated research teams, training 39 39 and internship programs). 40 Two \inria project-teams participate to this project. 41 \begin{itemize} 42 \item CAIRN. The CAIRN group of INRIA Rennes -- Bretagne Atlantique study reconfigurable 40 41 The CAIRN group of INRIA Rennes -- Bretagne Atlantique study reconfigurable 43 42 system-on-chip, i.e. hardware systems whose configuration may change before or even during 44 43 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. 50 49 CAIRN is a joint team with CNRS, INSA of Rennes, University of Rennes 1 and ENS Cachan. 51 \item COMPSYS. The Compsys group of Ecole Normale Sup\'erieure de Lyon is a project-team 50 51 \subsubsection{ENS Lyon LIP/Compsys} 52 The Compsys group of Ecole Normale Sup\'erieure de Lyon is a project-team 52 53 of INRIA Rh\^one-Alpes and a part of Laboratoire de l'Informatique du 53 54 Parall\'elisme (LIP), UMR 5668 of CNRS. It has four permanent researchers 54 55 and a variable number of PhD students and post-docs. Its field of 55 56 expertise is compilation for embedded system, optimizing compilers 56 and automatic parallelization. It has authored or contributed to 57 and automatic parallelization. Its members were among the initiators 58 of the polyhedral model for automatic parallelization and program 59 optimization generally. It has authored or contributed to 57 60 several well known libraries for linear programming, polyhedra manipulation 58 61 and optimization in general. It has strong industrial cooperations, notably 59 62 with ST Microelectronics and \thales. 60 \end{itemize}61 63 62 64 -
anr/section-7.tex
r152 r155 6 6 \begin{figure}\leavevmode\center 7 7 \input{table_inria_cairn_full.tex} 8 \caption{\label{ress-detail-irisa}Man power in $mm$ for the deliv rables of \irisa.}8 \caption{\label{ress-detail-irisa}Man power in $mm$ for the deliverables of \irisa.} 9 9 \end{figure} 10 10 \begin{description} … … 19 19 20 20 The table below summarizes the manpower by tasks for both permanent and non-permanent 21 personnels. The detail by deliv rables is given in figure~\ref{ress-detail-irisa}.21 personnels. The detail by deliverables is given in figure~\ref{ress-detail-irisa}. 22 22 The non-permanent personnels costs represent \mustbecompleted{??\%} of the personnal 23 23 costs. The requested funding for non permanent personnels is 100\% of … … 43 43 No specific equipment acquisition. 44 44 \item [Personnel costs] 45 The faculty members involved in the project are a professor at ENS45 The faculty members involved in the project are an emeritus professor at ENS 46 46 Lyon (Paul Feautrier) and a research associate (CR2) at INRIA 47 47 Rh\^one-Alpes (Christophe Alias). The non-permanent personal required … … 52 52 techniques and to produce a working implementation. 53 53 54 The table below summarizes the man power by deliv rables and tasks for both permanent and54 The table below summarizes the man power by deliverables and tasks for both permanent and 55 55 non-permanent personnels. 56 56 The non-permanent personnels costs represent \mustbecompleted{??\%} of the personnal … … 75 75 \begin{figure}\leavevmode\center 76 76 \input{table_tima_full.tex} 77 \caption{\label{ress-detail-tima}Man power in $mm$ for the deliv rables of \tima.}77 \caption{\label{ress-detail-tima}Man power in $mm$ for the deliverables of \tima.} 78 78 \end{figure} 79 79 \begin{description} … … 97 97 98 98 The table below sumarizes the man power by task for both permanent and non-permanent 99 personnels. The detail by deliv rables is given in figure~\ref{ress-detail-tima}.99 personnels. The detail by deliverables is given in figure~\ref{ress-detail-tima}. 100 100 The requested funding for personnels represent 50\% of the total personnal costs. 101 101 The requested funding for non permanent personnels is 85\% of the total ANR … … 117 117 \begin{figure}\leavevmode\center 118 118 \input{table_ubs_full.tex} 119 \caption{\label{ress-detail-ubs}Man power in $mm$ for the deliv rables of \ubs.}119 \caption{\label{ress-detail-ubs}Man power in $mm$ for the deliverables of \ubs.} 120 120 \end{figure} 121 121 … … 131 131 132 132 The table below sumarizes the man power by task for both permanent and non-permanent 133 personnels. The detail by deliv rables is given in figure~\ref {ress-detail-ubs}.133 personnels. The detail by deliverables is given in figure~\ref {ress-detail-ubs}. 134 134 The non-permanent personnels costs represent 50\% of the personnal costs. 135 135 The requested funding for non permanent personnels is about 83\% of the total ANR … … 152 152 \begin{figure}\leavevmode\center 153 153 \input{table_upmc_full.tex} 154 \caption{\label{ress-detail-upmc}Man power in $mm$ for the deliv rables of \upmc.}154 \caption{\label{ress-detail-upmc}Man power in $mm$ for the deliverables of \upmc.} 155 155 \end{figure} 156 156 \begin{description} … … 166 166 for senior researchers (post-doc or research engineers). 167 167 The table below sumarizes the man power by task for both permanent and non-permanent 168 personnels. The detail by deliv rables is given in figure~\ref{ress-detail-upmc}.168 personnels. The detail by deliverables is given in figure~\ref{ress-detail-upmc}. 169 169 The non-permanent personnels costs represent 50\% of the personnal costs. 170 170 The requested funding for non permanent personnels is 79\% of the total ANR … … 187 187 \begin{figure}\leavevmode\center 188 188 \input{table_xilinx_full.tex} 189 \caption{\label{ress-detail-xilinx}Man power in $mm$ for the deliv rables of \xilinx.}189 \caption{\label{ress-detail-xilinx}Man power in $mm$ for the deliverables of \xilinx.} 190 190 \end{figure} 191 191 \begin{description} … … 194 194 \item[Personnel costs] 195 195 \xilinx employees involved in the project are permanent Software Engineers. 196 The detail by deliv rables is given in figure~\ref{ress-detail-xilinx} and196 The detail by deliverables is given in figure~\ref{ress-detail-xilinx} and 197 197 a sumary by task in the following table. 198 198 \begin{center}\input{table_xilinx_short.tex}\end{center} … … 267 267 A permanent engineer will be assigned on average 1/3 time for 268 268 all the duration of the project. 269 The table below shows the estimated manpower cost in months for the deliv rables.269 The table below shows the estimated manpower cost in months for the deliverables. 270 270 \begin{center}\input{table_navtel_full.tex}\end{center} 271 271 \item[Subcontracting] -
anr/task-1.tex
r152 r155 23 23 This document contains the general description of the framework, the design flow and the 24 24 description of the architectural templates. 25 It refers to the HAS specification (deliv rable {\specHasManual}) and26 to the CSG specifcation (deliv rable \specCsgManual) for the COACH input25 It refers to the HAS specification (deliverable {\specHasManual}) and 26 to the CSG specifcation (deliverable \specCsgManual) for the COACH input 27 27 descriptions. 28 28 \itemL{6}{12}{d}{\Supmc}{COACH specification}{1:0:0} \setMacroInAuxFile{specGenManual} 29 The final version of the {\specGenManualI} deliv rable updated with the \mustbecompleted{FIXME:: first ?}29 The final version of the {\specGenManualI} deliverable updated with the \mustbecompleted{FIXME:: first ?} 30 30 feed-backs of the demonstrator \STs. 31 31 \itemV{0}{6}{d}{\Stima}{CSG specification} \setMacroInAuxFile{specCsgManualI} … … 38 38 synthesis. 39 39 \itemL{6}{12}{d}{\Stima}{CSG specification}{1:0:0} \setMacroInAuxFile{specCsgManual} 40 The final version of the {\specGenManualI} deliv rable updated with the \mustbecompleted{FIXME:: first ?}40 The final version of the {\specGenManualI} deliverable updated with the \mustbecompleted{FIXME:: first ?} 41 41 feed-backs of the demonstrator \STs. 42 42 \itemV{0}{6}{d}{\Subs}{HAS specification} \setMacroInAuxFile{specHasManualI} 43 43 The first version of the HAS (Hardware Accelerator Synthesis) specification. 44 44 It specifies how tasks must be written (C/C++ subset) and how 45 communication schemes defined in the {\specCsgManual} deliv rable must be described for45 communication schemes defined in the {\specCsgManual} deliverable must be described for 46 46 coprocessor synthesis. 47 47 \itemL{6}{12}{d}{\Subs}{HAS specification}{1:0:0} \setMacroInAuxFile{specHasManual} 48 The final version of the {\specGenManualI} deliv rable updated with the \mustbecompleted{FIXME:: first ?}48 The final version of the {\specGenManualI} deliverable updated with the \mustbecompleted{FIXME:: first ?} 49 49 feed-backs of the demonstrator \STs. 50 50 \end{livrable} -
anr/task-2.tex
r154 r155 21 21 \item the specification of enhanced communication schemes and their sofware and hardware implementations. 22 22 \end{itemize} 23 This task being based on the SocLib platform, a first release will be deliv rableat $T0+12$23 This task being based on the SocLib platform, a first release will be delivered at $T0+12$ 24 24 to allow the demonstrators to start working. 25 25 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} 71 71 The synthesizable VHDL description of the MWMR component corresponding to the 72 SystemC module of the former deliv rable (\csgXilinxSystemC).72 SystemC module of the former deliverable (\csgXilinxSystemC). 73 73 \itemL{24}{27}{d}{\Sxilinx}{\xilinx RTL optimisation (3)}{0:0:1.5} 74 74 This deliverable consists in optimizing the MWMR VHDL description (deliverable … … 83 83 \itemL{18}{24}{h}{\Sirisa}{\altera architecture}{6:6:0} 84 84 The synthesizable VHDL description of the MWMR component corresponding to the 85 SystemC module of the former deliv rable (\csgAlteraSystemC);85 SystemC module of the former deliverable (\csgAlteraSystemC); 86 86 \itemV{6}{12}{d}{\Subs}{UBS communication adapter} 87 87 \setMacroInAuxFile{gautCOMMoptimization} … … 102 102 \subtask This \ST consists of the configuration of the SocLib MUTEKH and DNA operating 103 103 system and the development of drivers for the hardware architectural templates 104 and enhanced communication schemes defined in \novers{\specCsgManual} deliv rable.104 and enhanced communication schemes defined in \novers{\specCsgManual} deliverable. 105 105 For the \altera and \xilinx architectural templates, the OSs must also be ported on 106 106 the NIOS2 and MICROBLAZE processors. 107 107 \begin{livrable} 108 108 \itemV{6}{8}{x}{\Supmc}{MUTEKH OS} 109 The drivers required for the first CSG milestone (deliv rable \csgCoachArch).109 The drivers required for the first CSG milestone (deliverable \csgCoachArch). 110 110 \itemV{8}{18}{x}{\Supmc}{MUTEKH 0S} 111 111 The drivers required for the second CSG milestone ({\csgPrototypingOnly}). … … 115 115 Porting of MUTEKH OS on the NIOS2 and MICROBLAZE processors. 116 116 \itemV{6}{8}{x}{\Stima}{DNA OS} 117 The drivers required for the first CSG milestone (deliv rable \csgCoachArch).117 The drivers required for the first CSG milestone (deliverable \csgCoachArch). 118 118 \itemV{8}{18}{x}{\Stima}{DNA 0S} 119 119 The drivers required for the second CSG milestone ({\csgPrototypingOnly}). -
anr/task-4.tex
r143 r155 70 70 and also supports new constraints and objectives defined in 71 71 \mustbecompleted{FIXME:USB utilise une macro svp: \ST1-1} 72 \mustbecompleted{FIXME:UBS: quel deliv rable ??}.72 \mustbecompleted{FIXME:UBS: quel deliverable ??}. 73 73 \itemV{6}{18}{d}{\Subs}{Design Space Exploration}{0:0:0} 74 74 \mustbecompleted{FIXME:UBS GAUT enhancement 3 serait peut-etre meilleur} … … 78 78 \itemL{18}{30}{x}{\Subs}{Design Space Exploration}{0:0:0} 79 79 Release of the GAUT software that supports the features defined in 80 \mustbecompleted{FIXME:UBS: macro ????} deliv rable.80 \mustbecompleted{FIXME:UBS: macro ????} deliverable. 81 81 \end{livrable} 82 82 \subtask In FPGA-SoC, the frequency is given by the processor(s) and the system BUS. The coprocessors -
anr/task-5.tex
r154 r155 53 53 \itemL{6}{12}{x}{\Supmc}{HPC partionning helper}{1:0:0} 54 54 \setMacroInAuxFile{hpcCommHelper} 55 A library implementing the communication API defined in the {\hpcCommApi} deliv rable.55 A library implementing the communication API defined in the {\hpcCommApi} deliverable. 56 56 This library is dedicated to help the end-user to partition an applicattion for 57 57 HPC. … … 109 109 \xilinx will work with \tima in order to better take into account during 110 110 partitioning decisions specific constraints due to partial reconfiguration process. 111 The deliv rable is a document describing the \xilinx specific constraints.111 The deliverable is a document describing the \xilinx specific constraints. 112 112 \end{livrable} 113 113 %\item This \ST is the delivery of 2 PCI/X \mustbecompleted{FIXME: Stratix4} FPGA board -
anr/task-6.tex
r146 r155 52 52 \itemV{0}{6}{d}{\Sthales}{\thales demonstrator (step 1)} 53 53 \setMacroInAuxFile{trtAppSpecification} 54 This deliv rable is a document that specifies the application.54 This deliverable is a document that specifies the application. 55 55 \itemL{6}{12}{x}{\Sthales}{\thales demonstrator (step 1)}{4:0:0} 56 This deliv rable is the code of the application spcecified former57 deliv rable (\trtAppSpecification).56 This deliverable is the code of the application spcecified former 57 deliverable (\trtAppSpecification). 58 58 \end{livrable} 59 59 … … 76 76 \begin{livrable} 77 77 \itemV{18}{24}{d+x}{\Sthales}{\thales demonstrator (step 2)} 78 This deliv rable is a document describing the result got for the application78 This deliverable is a document describing the result got for the application 79 79 (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+18. 80 80 The updated code of the application will be also provide. 81 81 \itemV{24}{30}{d+x}{\Sthales}{\thales demonstrator (step 2)} 82 This deliv rable is a document describing the result got for the application82 This deliverable is a document describing the result got for the application 83 83 (\trtAppSpecification) with SPEAR-DE (\trtSpearde) using COACH milestone of T0+24. 84 84 The updated code of the application will be also provide. 85 85 \itemL{30}{36}{d+x}{\Sthales}{\thales demonstrator (step 2)}{0:5:5} 86 This deliv rable is a document that validates and evaluates COACH (final release)86 This deliverable is a document that validates and evaluates COACH (final release) 87 87 for the \thales demonstrators (\trtAppSpecification). 88 88 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 113 113 generate the SoC architecture. 114 This deliv rable is a document that describes this architecture.114 This deliverable is a document that describes this architecture. 115 115 \itemL{6}{18}{h}{\Szied}{eFPGA/VCI component}{3.6:3.6:0} 116 116 FLEXRAS has to adapt the eFPGA interface to connect it to the VCI bus. 117 This deliv rable is a VHDL description.117 This deliverable is a VHDL description. 118 118 % \itemL{12}{18}{x}{\Szied}{bitstream loader port}{0:3.6:0} 119 119 % Port of the bitstream loader to the MUTEKH operating system. … … 122 122 throught a basic application. 123 123 This applicattion will containt 3 communicating tasks under the COACH format specified 124 in {\novers{\specGenManual}} deliv rable.124 in {\novers{\specGenManual}} deliverable. 125 125 The first one is a hardware task generated by the HAS tools and transformed into 126 126 a bit stream by the \zied tools. … … 129 129 The third is a software task that communicates with the hw task for testing it. 130 130 \itemL{24}{30}{x}{\Szied}{eFPGA characterisation}{0:0:2.4} 131 This deliv rable is a file under the format defined by the delivrable131 This deliverable is a file under the format defined by the deliverable 132 132 {\specMacroCell} that characterizes the eFPGA. This will allow the COACH HLS tools 133 133 to take into account the eFPGA delays. 134 134 \itemL{30}{36}{d}{\Szied}{\zied evaluation}{0:0:3.6} 135 This deliv rable is a document that describes the tests, the validation and the135 This deliverable is a document that describes the tests, the validation and the 136 136 evaluation of COACH with the \zied architecture and tools. 137 137 \end{livrable} … … 162 162 \itemL{18}{36}{d}{\Snavtel}{\navtel evaluation}{0:2:4} 163 163 \navtel will test the COACH HLS tools on the processing units that are described 164 in the {\navtelSpecification} deliv rable.164 in the {\navtelSpecification} deliverable. 165 165 A document will be written that describes the results obtained taking into 166 166 account: 1) the performance in terms of space, 2) the performance in terms of
Note: See TracChangeset
for help on using the changeset viewer.