- Timestamp:
- Feb 10, 2011, 7:23:52 PM (14 years ago)
- Location:
- anr
- Files:
-
- 2 added
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
anr/annexe-autre-participation.tex
r362 r364 24 24 \begin{autreprojettabular} 25 25 \autreprojettabularentry 26 {2}{Greiner}{4} 27 {Tsar, CATRENE, 400 k\euro} 28 {Tera Scale ARchitecture} 29 {\makebox{Huy-Nam} Nguyen (Bull)} 30 {04/01/2008 05/31/2011} 31 \autreprojettabularentry 32 {7}{Nguyen}{8} 33 {Tsar, CATRENE, 695 k\euro} 34 {Tera Scale ARchitecture} 35 {\makebox{Huy-Nam} Nguyen (Bull)} 36 {04/01/2008 05/31/2011} 26 {1}{Avot}{6} 27 {BDREAMS, MEDEA+, 306 k\euro} 28 {Design Refinement of Embedded Analogue and Mixed Signal Systems} 29 {\makebox{Serge Scotti} (STM)} 30 {01/06/2008 31//05/2012} 31 %\autreprojettabularentry 32 % {1}{Lucas}{6} 33 % {SoCKeT, DGCIS, 320 k\euro} 34 % {SoC toolKit for critical Embedded sysTems} 35 % {\makebox{Vincent LEFFTZ} (Astrium)} 36 % {01/06/2008 30/09/2012} 37 %\autreprojettabularentry 38 % {2}{Greiner}{4} 39 % {Tsar, CATRENE, 400 k\euro} 40 % {Tera Scale ARchitecture} 41 % {\makebox{Huy-Nam} Nguyen (Bull)} 42 % {04/01/2008 05/31/2011} 43 %\autreprojettabularentry 44 % {7}{Nguyen}{8} 45 % {Tsar, CATRENE, 695 k\euro} 46 % {Tera Scale ARchitecture} 47 % {\makebox{Huy-Nam} Nguyen (Bull)} 48 % {04/01/2008 05/31/2011} 49 %\autreprojettabularentry 50 % {3}{Coussy}{3} 51 % {SoCKeT, FUI, 177 k\euro} 52 % {SoC toolKit for critical Embedded sysTems} 53 % {\makebox{Vincent LEFFTZ} (Astrium)} 54 % {01/06/2008 31/12/2011} 37 55 \autreprojettabularentry 38 56 {5}{P\'etrot}{3} … … 41 59 {\makebox{Dominique} Marron (STMicroelectronics)} 42 60 {01/02/2009 31/01/2012} 43 \autreprojettabularentry44 {5}{P\'etrot}{3}45 {SoftSoC, MEDEA+, 500 k\euro}46 {Software for SoC}47 {\makebox{Anne-Marie} Foulliard (Thales Communications)}48 {1/03/2008 28/02/2011}61 %\autreprojettabularentry 62 % {5}{P\'etrot}{3} 63 % {SoftSoC, MEDEA+, 500 k\euro} 64 % {Software for SoC} 65 % {\makebox{Anne-Marie} Foulliard (Thales Communications)} 66 % {1/03/2008 28/02/2011} 49 67 \autreprojettabularentry 50 68 {5}{P\'etrot}{3} … … 54 72 {01/03/2009 28/02/2012} 55 73 \autreprojettabularentry 56 {5}{Muller}{4} 57 {iGlance, CATRENE, 550 k\euro} 58 {Interactive Genius Look At Numerous Contemporary Events} 59 {\makebox{Michel} Imbert (STMicroelectronics)} 60 {01/07/2008 30/06/2011} 61 \autreprojettabularentry 62 {8}{Lemonier}{3} 63 {FORFOR, ANR Arpege, 305 k\euro} 64 {\mustbecompleted{TITRE (TRT)}} 65 {\makebox{Muller} (LEAT)} 66 {01/01/2008 31/12/2010} 67 \autreprojettabularentry 68 {8}{Lemonier}{4} 69 {FREIA, ANR Arpege, 280 k\euro} 70 {\mustbecompleted{TITRE (TRT)}} 71 {\makebox{Blondeau} (Amines)} 72 {01/01/2008 31/12/2010} 74 {6}{Derrien}{5} 75 {BioWic, ANR Arpege, 136 k\euro} 76 {Hardware acceleration of bioinformatic algorithms} 77 {\makebox{Dominique Lavenier} (IRISA)} 78 {01/01/2009 31/12/2011} 79 %\autreprojettabularentry 80 % {5}{Muller}{4} 81 % {iGlance, CATRENE, 550 k\euro} 82 % {Interactive Genius Look At Numerous Contemporary Events} 83 % {\makebox{Michel} Imbert (STMicroelectronics)} 84 % {01/07/2008 30/06/2011} 85 %\autreprojettabularentry 86 % {8}{Lemonier}{3} 87 % {FORFOR, ANR Arpege, 305 k\euro} 88 % {\mustbecompleted{TITRE (TRT)}} 89 % {\makebox{Muller} (LEAT)} 90 % {01/01/2008 31/12/2010} 91 %\autreprojettabularentry 92 % {8}{Lemonier}{4} 93 % {FREIA, ANR Arpege, 280 k\euro} 94 % {\mustbecompleted{TITRE (TRT)}} 95 % {\makebox{Blondeau} (Amines)} 96 % {01/01/2008 31/12/2010} 73 97 \autreprojettabularentry 74 98 {8}{Lemonier}{3} … … 89 113 {\makebox{Fr\'ed\'eric Thomas} (OBEO)} 90 114 {01/01/2010 31/12/2012} 91 \autreprojettabularentry92 {6}{Derrien}{5}93 {BioWic, ANR Arpege, 136 k\euro}94 {Hardware acceleration of bioinformatic algorithms}95 {\makebox{Dominique Lavenier} (IRISA)}96 {01/01/2009 31/12/2011}97 \autreprojettabularentry98 {3}{Coussy}{3}99 {SoCKeT, FUI, 177 k\euro}100 {SoC toolKit for critical Embedded sysTems}101 {\makebox{Coordinator Vincent LEFFTZ} (Astrium)}102 {01/06/2008 31/12/2011}103 115 \end{autreprojettabular} 104 116 % -
anr/section-1.tex
r357 r364 1 The market of digital systems is about 4,600 M\$ today and is estimated to 5,600 M\$ in 2012. However the ever growing applications complexity involves integration of heterogeneous technologies and requires the design of complex Multi-Processors System on Chip (MPSoC). During the last decade, the use of ASICs (Application Specific Integrated Circuits) appeared to be more and more reserved to high volume markets, because the design and fabrication costs of such components exploded, due to increasing NRE (Non Recurring-Engineering) costs. Fortunately, FPGA (Field Programmable Gate Array) components, such as the Virtex6 family from XILINX or the Stratix4 family from ALTERA, can nowadays implement a complete MPSoC with multiple processors and several dedicated coprocessors for a few Keuros per device. 1 % 2 The market of digital systems is about 4,600 M\$ today and is estimated to 5,600 M\$ in 2012. However the ever growing applications complexity involves integration of heterogeneous technologies and requires the design of complex Multi-Processors System on Chip (MPSoC). During the last decade, the use of ASICs appeared to be more and more reserved to high volume markets, because the design and fabrication costs of such components exploded, due to increasing NRE (Non Recurring-Engineering) costs. Fortunately, recent FPGA components, such as the Virtex5-6 family from XILINX or the Stratix4 family from ALTERA, can nowadays implement a complete MPSoC with multiple processors and several dedicated coprocessors for a few Keuros per device. 2 3 \parlf 3 Many applications are initially captured algorithmically in High-Level Languages (HLLs) such as C/C++. This has led to growing interest in tools that can provide an implementation path directly from HLLs to hardware. Thus, Electronic System Level (ESL) design methodologies (Virtual Prototyping, Co-design, High-Level Synthesis...) are now mature and allow the automation of a system-level design flow. Unfortunately, ESL tool development today has primarily focused on the design of hardwired devices i.e. ASICs and ASSPs (Application Specific Standard Product). However, the increasing sophistication of FPGAs has accelerated the need for FPGA-based ESL design methodologies. ESL methodologies hold the promise of streamlining the design approach by accepting designs written in C/C++ language and implementing the function straight into FPGA. Coupling FPGA technologies and ESL methodologies will allow both Small and Medium Enterprise and major companies to design innovative devices and to enter new, low and medium volume markets. Furthermore, today there is an increasing industrial interest to IC that integrates both hardwired CPU cores or MPSoC and a configurable area (FPGA) such as Intel-ATOM E600C. Probably in few years, such chips will become current and even standard general purpose CPU cores will contains a configurable area making explode the low and medium volume markets of digital systems. COACHâs objective is to provide an integrated design flow for the design of multi-processors digital systems targeting FPGA devices. It will be dedicated to system/software designers, and hide as much as possible the hardware characteristics to the end-user. COACH will mainly target three kinds of digital systems: 1/ Embedded and autonomous application such as personal digital assistants (PDA), ambient computing components, or wireless sensor networks, 2/ PCI-E extension boards connected to a PC to accelerate a specific application, it is the domain of High-Performance Computing (HPC) and High-Speed Signal Processing, 3/ Sub-system application for generating an IP to a larger system. The COACH open-source environment will integrate several hardware and software technologies: 4 Many applications are initially captured algorithmically in High-Level Languages (HLLs) such as C/C++. This has led to growing interest in tools that can provide an implementation path directly from HLLs to hardware. Thus, Electronic System Level (ESL) design methodologies (Virtual Prototyping, Co-design, High-Level Synthesis...) are now mature and allow the automation of a system-level design flow. Unfortunately, ESL tool development today has primarily focused on the design of hardwired devices i.e. ASICs and ASSPs (Application Specific Standard Product). However, the increasing sophistication of FPGAs has accelerated the need for FPGA-based ESL design methodologies. ESL methodologies hold the promise of streamlining the design approach by accepting designs written in C/C++ language and implementing the function straight into FPGA. Coupling FPGA technologies and ESL methodologies will allow both SMES and major companies to design innovative devices and to enter new, low and medium volume markets. Furthermore, today there is an increasing industrial interest to IC that integrates both hardwired CPU cores or MPSoC and a configurable area (FPGA) such as Intel-ATOM E600C. In few years, such chips will surely currently used in embedded systems and even standard general purpose CPU cores will contains a configurable area making explode the low and medium volume markets of digital systems. 5 \parlf 6 COACH is aligned with this long term vision, which requires an integrated design flow for the digital multiprocessors systems, targeting FPGAs and dedicated to the system and software designers; this project donât intend to solve all related issues, but aims at specifying and implementing innovative technological elements of the required tool chain. It will be dedicated to system/software designers, and hide as much as possible the hardware characteristics to the end-user. COACH will mainly target three kinds of digital systems: 1/ Embedded and autonomous application (personal digital assistants , ambient computing components, wireless sensor networks) 2/ mixed systems (CPU + FPGA extension boards) to accelerate a specific application answering High-Performance Computing (HPC) and High-Speed Signal Processing needs, 3/ Sub-system IP to be integrating into a larger system. 7 \\ 8 The COACH open-source environment will integrate several hardware and software technologies: 4 9 % 5 10 \begin{itemize} 6 \item Design Space Exploration by allowing to describe an application as a process network i.e. a set of tasks communicating through FIFO channels and to map the application on a shared-memory, MPSoC architecture .7 \item H ardware Accelerators Synthesis by allowing the automatic generation of hardware accelerators when required8 \item Platform based design: three architectural templates will be provided (free-generic and ALTERA and XILINXâs IPs based) .9 \item Hardware/Software communication middleware by implementing an homogeneous HW/SW communication infrastructure and communication APIs (Application Programming Interface), that will be used for communications between software tasks running on embedded processors and dedicated hardware coprocessors.10 \item I nteraction with the industrial world: the framework will be open to the industrial world by using IP-XACT standard for describing the components of the architectural template and by providing the IP-XACT description of the generated MPSoC.11 \item Design Space Exploration by allowing to describe an application as a process network i.e. a set of tasks communicating through FIFO channels and to map the application on a shared-memory, MPSoC architecture 12 \item High Level Synthesis of hardware accelerators 13 \item Platform based design: three architectural templates will be provided (free-generic and ALTERA and XILINXâs IPs based) 14 \item Hardware/Software communication middleware by implementing an homogeneous HW/SW communication infrastructure and communication APIs, that will be used for communications between software tasks running on embedded processors and dedicated hardware coprocessors 15 \item IP based design: using IP-XACT standard for describing the components of the architectural template and by providing the IP-XACT description of the generated MPSoC 11 16 \end{itemize} 12 17 % 13 \mustbecompleted{LIST NON A JOUR} 14 The major FPGA companies (\xilinx and \altera) have expressed their interest for 15 this project. 16 Finally, the COACH project is already supported by a large number of SMEs, as demonstrated by the 17 "letters of interest" (see Annex B), that have been collected during the preparation of the project : 18 ADACSYS, MDS, INPIXAL, CAMKA System, ATEME, ALSIM, SILICOMP-AQL, 19 ABOUND Logic, EADS-ASTRIUM. 18 Finally,a large number of SMEs and large companies, (see "letters of interest" Annex \ref{lettre-soutien}), 19 have expressed their interest for this project: 20 \altera, FLEXRAS, INPIXAL, CAMKA System, RENESAS Design, 21 \mustbecompleted{ ADACSYS, ATEME, ALSIM, SILICOMP-AQL, ABOUND Logic, EADS-ASTRIUM.}.\\ 22 \altera, a major FPGA company provides FPGA cards to the project. 23 These companies are either FPGA providers (engaged to collaborate by delivering FPGA board to partners), 24 design houses, EDA companies, or system integrators. 25 This heterogeneity of actors show the strong added value brought by the COACH platform. 20 26 21 %% % les objectifs globaux,22 %% The market of digital systems is about 4,600 M\$ today and is estimated to23 %% 5,600 M\$ in 2012. However the ever growing application complexity involves24 %% integration of heterogeneous technologies and requires the design of25 %% complex Multi-Processors System on Chip (MPSoC).26 %% \\27 %% During the last decade, the use of ASICs (Application Specific28 %% Integrated Circuits) appeared to be more and more reserved to high volume markets, because29 %% the design and fabrication costs of such components exploded, due to increasing NRE (Non30 %% Recurring-Engineering) costs.31 %% Fortunately, FPGA (Field Programmable Gate Array) components, such as the32 %% Virtex6 family from \xilinx or the Stratix4 family from \altera, can nowadays33 %% implement a complete MPSoC with multiple processors and several dedicated34 %% coprocessors for a few Keuros per device.35 %% \\36 %% Many applications are initially captured37 %% algorithmically in High-Level Languages (HLLs) such as C/C++. This has led to growing interest38 %% in tools that can provide an implementation path directly from HLLs to hardware.39 %% Thus, Electronic System Level (ESL) design methodologies (Virtual Prototyping,40 %% Co-design, High-Level Synthesis...) are now mature and allow the automation of41 %% a system-level design flow. Unfortunately, ESL tool development to date has primarily focused42 %% on the design of hard-wired devices i.e. ASICs and ASSPs (Application Specific Standard Product).43 %% However, the increasing sophistication of FPGAs has accelerated the need for FPGA-based ESL design44 %% methodologies. ESL methodologies hold the promise of streamlining the design approach by accepting45 %% designs written in the C/C++ language and implementing the function directly into FPGA.46 %% We believe that coupling FPGA technologies and ESL methodologies47 %% will allow both SMEs (Small and Medium Enterprise) and major companies to design innovative48 %% devices and to enter new, low and medium volume markets.49 %% Furthermore, today there is an increasing industrial interest into IC50 %% that integrates both hardwired CPU cores or MPSoC and a configurable area (FPGA)51 %% such as the ATOM E600C chip (Intel).52 %% In few a years, one can expect that such chips will become current. Even standard53 %% general purpose CPU cores will contains a configurable area54 %% bringing an explosion in low and medium volume markets.55 %% \parlf56 %% The objective of COACH is to provide an integrated design flow for the design of57 %% multi-processors digital systems targeting FPGA devices.58 %% It will be dedicated to system/software designers, and hide as much as possible59 %% the hardware characteristics to the end-user.60 %% COACH will mainly target three kinds of digital systems:61 %% 1) embedded and autonomous application such as personal digital assistants (PDA),62 %% ambient computing components, or wireless sensor networks (WSN);63 %% 2) PCI/E extension boards connected to a PC to accelerate a specific application,64 %% it is the domain of High-Performance Computing (HPC) and High-Speed Signal Processing (HSSP);65 %% 3) sub-system application for generating an IP to a larger system.66 %% \parlf67 %% %verrous scientifiques et techniques68 %% The COACH environment will integrate several hardware and software technologies:69 %% \begin{description}70 %% \item[Design Space Exploration:]71 %% The COACH environment will allow to describe an application as a process72 %% network i.e. a set of tasks communicating through FIFO channels.73 %% COACH will allow to map the application on a shared-memory, MPSoC architecture.74 %% It will permit to easily explore the design space to help the system designer75 %% to define the proper hardware/software partitioning of the application.76 %% For each point in the design space, metrics such as throughput, latency, power77 %% consumption, silicon area, memory allocation and data locality will be provided.78 %% \item[Hardware Accelerators Synthesis (HAS):]79 %% COACH will allow the automatic generation of hardware accelerators when required.80 %% Hence, High-Level Synthesis (HLS) tools, Application Specific Instruction Processor81 %% (ASIP) design environments and source-level transformation tools (loop transformations82 %% and memory optimization) will be provided.83 %% This will allow further exploration of the micro-architectural design space.84 %% HLS tools are sensitive to the coding style of the input specification and the domain85 %% they target (control vs. data dominated).86 %% The HLS tools of COACH will support a common language and coding style to avoid87 %% re-engineering by the designer.88 %% \item[Platform based design:]89 %% COACH will handle both \altera and \xilinx FPGA devices.90 %% COACH will define architectural templates that can be customized by adding91 %% dedicated coprocessors and ASIPs and by fixing template parameters such as92 %% the number of embedded processors, the number and size of embedded memory banks93 %% or the embedded operating system.94 %% However, the specification of the application will be independent of both the95 %% architectural template and the target FPGA device.96 %% Basically, the following three architectural templates will be provided:97 %% \begin{enumerate}98 %% \item A Neutral architectural template based on the SoCLib IP core library and the99 %% VCI/OCP communication infrastructure.100 %% \item An \altera architectural template based on the \altera IP core library, the101 %% AVALON system bus and the NIOS processor.102 %% \item A \xilinx architectural template based on the \xilinx IP core library,103 %% the \xilinxbus system bus and the \xilinxcpu processor.104 %% \end{enumerate}105 %% \item[Hardware/Software communication middleware:]106 %% COACH will implement an homogeneous HW/SW communication infrastructure and107 %% communication APIs (Application Programming Interface), that will be used for108 %% communications between software tasks running on embedded processors and109 %% dedicated hardware coprocessors.110 %% \item[Interaction with the industrial world:]111 %% COACH will not be a closed framework but it will be opened to the industrial112 %% world by using the IP-XACT format \cite{IP-XACT-08} for describing the components of the113 %% architectural template and by providing the IP-XACT description of the generated MPSoC.114 %% This should facilitate the enhancement of the architectural template with IP and the115 %% integration of the IP produced by COACH in larger design.116 %% \end{description}117 %% %From the end user point of view, the specification of the application will be118 %% %independant from both the architectural template and from the selected FPGA119 %% %family.120 %% \parlf121 %% % le programme de travail122 %% %The COACH project targets fundamental issues related to design methodologies for123 %% %digital systems by providing estimation, exploration and design tools targeting both124 %% %performance and power optimization at all the abstraction levels of the flow (system,125 %% %architecture, algorithm and logic).126 %% To reach this ambitious goal, the project will rely on the experience and the127 %% %complementariness128 %% synergy of the partners in the following domains:129 %% Operating system and communication middleware (\tima, \upmc),130 %% MPSoC architectures (\tima, \ubs, \upmc),131 %% ASIP architectures (\inria),132 %% High Level Synthesis (\tima, \ubs, \upmc), and compilation (\lip),133 %% HPC (\bull, \thales, \lip), tools integration in IP-XACT flow (\mds).134 %% \\135 %% The COACH project does not start from scratch.136 %% It relies137 %% on the Magillem industrial platform for the integration into IP-XACT flows,138 %% on the SoCLib platform~\cite{soclib} for prototyping and operating systems (DNA/OS),139 %% on the GAUT~\cite{gaut08} and UGH~\cite{ugh08} tools for HLS,140 %% on the ROMA~\cite{roma, RAFFIN:2010:INRIA-00539874:1} project for ASIP,141 %% on the SYNTOL~\cite{syntol} and BEE~\cite{bee} tools for source-level analysis and142 %% transformations,143 %% and on the \xilinx and \altera IP core libraries.144 %% Finally it will use the \xilinx and \altera logic and physical synthesis tools145 %% to generate the FPGA configuration bitstreams.146 %% %The main development steps of the COACH project are:147 %% %\begin{enumerate}148 %% % \item Definition of the end user inputs:149 %% % The coarse grain parallelism of the application will be described as a communicating150 %% % task graph, each task being described in C language.151 %% % Similarly the architectural templates with their parameters and the design constraints152 %% % will be specified.153 %% % \item Definition of an internal format for representing task.154 %% % \item Development of the GCC pluggin for generating the internal format of a155 %% % C task.156 %% % \item Adaptation of the existing HAS tools (BEE, SYNTOL, UGH, GAUT) to read and write157 %% % the internal format. This will allow to swap from one tool to another one, and to158 %% % chain them if necessary.159 %% % \item Modification of the DSX tool (Design Space eXplorer) of the SocLib160 %% % platform to generate the bitstream for the various FPGA families and architectural161 %% % templates.162 %% % \item Development of new tools such as ASIP compiler, HPC design environment and163 %% % dynamic reconfiguration of FPGA devices.164 %% %\end{enumerate}165 %% \parlf166 %% The role of the industrial partners \bull, \thales and \mds is to provide167 %% real use cases to benchmark the COACH design environment and to analyze the designer productivity168 %% improvements.169 %% \parlf170 %% The COACH project will deliver an open and freely distributed infrastructure.171 %% The architectural templates and most of the software tools will be distributed under the172 %% GPL-like license.173 %% The VHDL synthesizable models for the neutral architectural template174 %% will also be freely available for non commercial use.175 %% For industrial exploitation the technology providers are ready to propose commercial licenses,176 %% directly to the end user, or through a third party.177 %% \parlf178 %% \mustbecompleted{LIST NON A JOUR}179 %% The major FPGA companies (\xilinx and \altera) have expressed their interest for180 %% this project.181 %% Finally, the COACH project is already supported by a large number of SMEs, as demonstrated by the182 %% "letters of interest" (see Annex B), that have been collected during the preparation of the project :183 %% ADACSYS, MDS, INPIXAL, CAMKA System, ATEME, ALSIM, SILICOMP-AQL,184 %% ABOUND Logic, EADS-ASTRIUM.185 %% -
anr/section-consortium-desc.tex
r361 r364 27 27 The approach to the use of the tools of industrials are: 28 28 IP-XACT and industrial flow integration (\mds), 29 HPC (\bull) and 30 \mustbecompleted{XXX "par MAGILEM ou TRT"} (\thales). 29 HPC (\bull) and IP integration in SoC design flow (\mds, \thales). 31 30 \thales will represent the FPGA users, \bull the HPC users, and \mds the SoC integrators. 32 31 -
anr/section-consortium-people.tex
r363 r364 70 70 71 71 \peopletabularentry{\mds} 72 \CO & Vaumorin & Emannuel & \SPM & ESL & 20& Task: \TL{1}, \mustbecompleted{X, Y}, \TL{8}\\\hline73 \ME & Spasevski & Cyril & CTO & EDA & 6 & Task: \mustbecompleted{X, Y}\\\hline74 \ME & Guntz & St\'ephane & \VPENG & EDA & 6 & Task: \mustbecompleted{X, Y}\\\hline75 \ME & Lucas & Ronan & R\&D Engineer & Codesign & 9 & Task: \mustbecompleted{X, Y}\\\hline76 \ME & Olivier & Garry & R\&D Engineer & \SW & 9 & Task: \mustbecompleted{X, Y}\\\hline72 \CO & Vaumorin & Emannuel & \SPM & ESL & 20& Task: \TL{1}, 7, \TL{8}\\\hline 73 \ME & Spasevski & Cyril & CTO & EDA & 6 & Task: 2, 7 \\\hline 74 \ME & Guntz & St\'ephane & \VPENG & EDA & 6 & Task: 7 \\\hline 75 \ME & Lucas & Ronan & R\&D Engineer & Codesign & 9 & Task: 3, 7 \\\hline 76 \ME & Olivier & Garry & R\&D Engineer & \SW & 9 & Task: 3, 7 \\\hline 77 77 %\end{peopletabular}\begin{peopletabular} 78 78 \peopletabularentry{\upmc} -
anr/section-dissemination.tex
r361 r364 168 168 \letterOfInterest{FlexRAS Technologies}{lettres-2011/Flexras.pdf}, 169 169 \letterOfInterest{INPIXAL}{lettres-2011/Inpixal.jpg}, 170 \letterOfInterest{CAMKA System}{lettres-2011/Camka.pdf}, 171 \letterOfInterest{RENESAS Design}{lettres-2011/Renesas.jpg}, 170 172 %\letterOfInterest{ADACSYS}{lettres-2011/Coach_ADACSYS_lettre_interet}, 171 %\letterOfInterest{CAMKA System}{lettres-2011/CAMKA-System.pdf},172 173 %\letterOfInterest{ATEME}{lettres-2011/ATEME.pdf}, 173 174 %\letterOfInterest{ALSIM Simulateur}{lettres-2011/Alsim.pdf}, -
anr/section-position.tex
r358 r364 185 185 quality and reducing the design time and the cost of synthesised cryptographic devices. 186 186 % 187 COACH will contribute to enhance the safety in design of critical system for two main reasons: 188 \begin{itemize} 189 \item by providing a way to automate the mapping of application onto MPSoC 190 architecture; code generators of the tool chain will be subject to 191 certification. 192 \item by relaying on design flow defined by SoCKET, which is dedicated to 193 safety of critical systems, COACH will benefit from features related to 194 requirements traceability. 195 \end{itemize} 196 % 187 197 \subsubsection*{European and international positioning} 188 198 % -
anr/section-project-description.tex
r356 r364 142 142 \item $T8$ and $T1$ depend on and impact all the other tasks. 143 143 \end{itemize} 144 This organisation offers enough robustness to insure the success of the 145 project, the only critical task in this chart being $T2$. \label{xcoach-problem} 146 %However, the partners met 12 times (a one-day meeting per month) during the last year. 147 %Ten meeting were dedicated to preliminary technical discussions, including a tentative specification 148 %of {\tt xcoach}. The other meetings were dedicated to the preparation of the present proposal. 149 However, the partners had 10 one-day meetings where a preliminary draft of the 150 \xcoach format was defined. This makes this task less critical. 144 %This organisation offers enough robustness to insure the success of the 145 %project, the only critical task in this chart being $T2$. \label{xcoach-problem} 146 %%However, the partners met 12 times (a one-day meeting per month) during the last year. 147 %%Ten meeting were dedicated to preliminary technical discussions, including a tentative specification 148 %%of {\tt xcoach}. The other meetings were dedicated to the preparation of the present proposal. 149 %However, the partners had 10 one-day meetings where a preliminary draft of the 150 %\xcoach format was defined. This makes this task less critical. 151 This project has been shaped with this chart in order to minimize the technical 152 risk: the task $T2$ handles the major technical issues to be solved and as it is 153 planned at the beginning of the project we will be able to react fast and take 154 decisions for possible workaround and enable the continuation of the work with 155 other tasks. Nevertheless, we are confident because upfront to this project, 156 academic partners are already working close togother and know well each other's 157 technologies, and also a lot of face to face meeting are planned at the 158 beginning of the project in task $T2$ in order to define the \xcoach format which is 159 the corner stone of the COACH platform. 151 160 -
anr/section-ressources.tex
r363 r364 56 56 \ifx\cont\tmp\def\cont{None.}\else\def\cont{% 57 57 The costs justified by internal invoicing procedures are evaluated 58 to #5\%of the total requested ANR funding.}\fi58 to \textbf{#5\%} of the total requested ANR funding.}\fi 59 59 \cont 60 60 %\item[Other working costs] None … … 81 81 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 82 82 83 The global effort is 358\hommemois (\hommemoislong),83 The global effort is \mustbecompleted{XXXXXXXX 358} \hommemois (\hommemoislong), 84 84 the part of academic partners is 236 \hommemois (66\% of the global effort) 85 85 and the part of the industrial partners is 122 \hommemois (\textbf{34\%} of the … … 100 100 annexe~\ref{table-livrables-mds} (page \pageref{table-livrables-mds}). 101 101 and a summary by task in the following table. 102 \mustbecompleted{\\MDS: Vous n'etes dans aucuns projets annexe 7.3 ?}103 102 } 104 103 {2} 105 104 {} 106 %107 % \begin{description}108 % \item[Equipment]109 % No specific equipment acquisition is required for this project.110 % \item[Personnel costs]111 % \mds employees involved in the project are permanent managers, engineers and PhD graduates.112 % The man power detail in \hommemois by deliverables is given in113 % annexe~\ref{table-livrables-mds} (page \pageref{table-livrables-mds}).114 % and a sumary by task in the following table.115 % \begin{center}\input{table_mds_short.tex}\end{center}116 % \item[Subcontracting]117 % No subcontracting costs.118 % \item[Travel]119 % The travel costs are associated to project meeting as well as participation to120 % conferences. The travel costs are estimated to 2\% of the total requested ANR funding.121 % \item[Expenses for inward billing] none122 % \item[Other working costs] none123 % \end{description}124 105 125 106 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 133 114 }} 134 115 {8}{3.5} 135 %136 % \begin{description}137 % \item[Equipment]138 % In order to validate the COACH design flow, \upmc will buy FPGA development139 % boards (especially 1 PCI/E FPGA \xilinx board).140 % The cost for these boards is estimated to 6 k\euro (4\% of the total ANR funding).141 % \item[Personnel costs]142 % The permanent personnels involved in the project are professors or assistant143 % professors (Alain Greiner and Ivan Aug\'e).144 % All non permanent personnel costs are estimated in \hommemois for senior researchers145 % (post-doc or research engineers).146 % The table below sumarizes the man power by tasks in \hommemois for both permanent and147 % non-permanent personnels.148 % The detail by deliverables is given in annexe~\ref{table-livrables-upmc} (page \pageref{table-livrables-upmc}).149 % The non-permanent personnels costs (24 \hommemois) represent 46\% of the personnal costs.150 % The requested funding for non permanent personnels is 79\% of the total ANR151 % requested funding.152 % \begin{center}\input{table_upmc_short.tex}\end{center}153 % \item[Subcontracting]154 % No subcontracting costs.155 % \item[Travel]156 % The travel costs are associated to management and coordination meeting as157 % well as participation to conferences. The travel costs are estimated158 % to 10\% of the total requested ANR funding.159 % \item[Expenses for inward billing]160 % The costs justified by internal invoicing procedures are evaluated to 4\%161 % of the total requested ANR funding.162 % \end{description}163 116 164 117 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 168 121 {ubs} 169 122 {} 170 {{\ubs}{48}{24}{Philippe COUSSY, Cyrille CHAVET and Dominique HELLER}{8 4}{123 {{\ubs}{48}{24}{Philippe COUSSY, Cyrille CHAVET and Dominique HELLER}{85}{ 171 124 We are looking for profiles with strong informatic skills, good knowledge 172 125 in computer architecture and advanced digital design. 173 \mustbecompleted{\\UBS: ./gantt < anr.gant\\174 \t WARNING: ubs :D511 probleme sur l'an 1 (in table=7.0, in gantt=6.0 \\175 \t ERROR: ubs :D840 probleme sur l'an 1 (in table=0.5, in gantt=0.0}176 126 }} 177 {11}{4} 178 179 % \begin {description} 180 % \item [Equipment] 181 % In order to validate the design flow project, the Lab-STICC laboratory will buy FPGA 182 % development boards. The cost for these FPGA boards is estimated to 3\% of the total 183 % ANR funding. 184 % \item [Personnel costs] 185 % The faculty members involved in the project are associate professors (Philippe COUSSY, 186 % Cyrille CHAVET) or research engineers (Dominique HELLER). All non-permanent personnel 187 % costs are estimated in \hommemois for senior researchers (post-doc or research 188 % engineers). 189 % \parlf 190 % The table below summarizes the man power in \hommemois by tasks for both permanent and 191 % non-permanent personnels. The detail by deliverables is given in 192 % annexe~\ref{table-livrables-usb} (page \pageref{table-livrables-usb}). 193 % The non-permanent personnels costs represent 50\% of the personnel costs. 194 % The requested funding for non permanent personnels is about 83\% of the total ANR 195 % requested funding. 196 % \begin{center}\input{table_ubs_short.tex}\end{center} 197 % \item [Subcontracting] 198 % No subcontracting costs. 199 % \item [Travel] 200 % The travel costs are associated to management and meeting as well as participation to 201 % conferences. The travel costs are estimated to 10\% of the total requested ANR funding. 202 % \item [Expenses for inward billing] 203 % The costs justified by internal invoicing procedures are evaluated to 4\% of the total 204 % requested ANR funding. 205 % \end {description} 127 {12}{4} 128 206 129 207 130 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 209 132 \ressourcesForAcademic 210 133 {inria_compsys}{} 211 {{\lip}{46}{21}{Christophe Alias and Paul Feautrier}{ \mustbecompleted{100}}{134 {{\lip}{46}{21}{Christophe Alias and Paul Feautrier}{82}{ 212 135 \\We are looking for a candidate with both theoretical and 213 136 practical skills, that will be able to get a sufficient … … 219 142 }} 220 143 {12}{4} 221 %222 % \begin{description}223 % \item [Equipment]224 % No specific equipment acquisition. The costs for depreciation of225 % workstations is evaluated to 4\% of the total requested ANR funding.226 % \item [Personnel costs] The faculty members involved in the project227 % are Christophe Alias (INRIA researcher) and Paul Feautrier (emeritus228 % professor at ENS-Lyon). The non-permanent personel required is a229 % post-doc that will work on FIFO construction, then on extensions of230 % process construction and memory optimization to non-polyhedral231 % loops. We are looking for a candidate with both theoretical and232 % practical skills, that will be able to get a sufficient233 % understanding of the polyhedral techniques to produce a working234 % implementation.235 % \parlf236 % The table below summarizes the \hommemois by tasks for both permanent237 % and non-permanent personnels.238 % Annexe~\ref{table-livrables-lip} (page \pageref{table-livrables-lip})239 % details this table at the deliverable level.240 % The effort of permanent personnels represents 61\% of241 % the total effort. The non-permanent personnels costs represents242 % 52\% of the personal costs. The requested funding for non permanent243 % personnels is 100\% of the total ANR requested244 % funding.245 % \begin{center}\input{table_inria_compsys_short.tex}\end{center}246 % \item [Subcontracting]247 % No subcontracting costs.248 % \item [Travel]249 % The travel costs are associated to project meeting as well as250 % participation to conferences. The travel costs are estimated to 20\%251 % of the total requested ANR funding.252 % \item [Expenses for inward billing]253 % The costs justified by internal invoicing procedures are evaluated254 % to 4\% of the total requested ANR funding.255 % \end{description}256 144 257 145 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 264 152 }} 265 153 {10}{4} 266 %267 % \begin{description}268 % \item [Equipment]269 % No specific equipment acquisition.270 % \item [Personnel costs]271 % The permanent personnels involved in the project are professor and associate professor272 % (Fr\'ed\'eric P\'etrot and Olivier Muller).273 % The non permanent personnels are Phd students and post-doc researchers.274 % Related costs are estimated in \hommemois.275 % One phd student (Adrien Prost-Boucle), funded by the French ministry of research, will276 % be working on the project.277 % One 100\% funded phd student will be hired in September 2011.278 % A post-doc researcher will be hired at the end of 2012 for one year.279 % The PhD student will mainly work on the evolution of UGH HLS tool. Thus, we are looking280 % for a profile with strong informatic skills and good knowledge in computer architecture.281 % The post-doc will mainly work on HPC. The required profile282 % will be more oriented on computer architecture and advanced digital design.283 % \parlf284 % The table below summarizes the man power in \hommemois by tasks for both permanent and285 % non-permanent personnels. The detail by deliverables is given in286 % annexe~\ref{table-livrables-tima} (page \pageref{table-livrables-tima}).287 % The effort of permanent personnels represents 50\% of the total effort.288 % The requested funding for non permanent personnels is 86\% of the total ANR requested289 % funding.290 % \begin{center}\input{table_tima_short.tex}\end{center}291 % \item [Subcontracting]292 % No subcontracting costs.293 % \item [Travel]294 % The travel costs are associated to project meeting as well as participation to295 % conferences. The travel costs are estimated to 10\% of the total requested ANR funding.296 % \item [Expenses for inward billing]297 % The costs justified by internal invoicing procedures are evaluated to 4\% of the total298 % requested ANR funding.299 % \end{description}300 154 301 155 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 308 162 }} 309 163 {10}{4} 310 %311 % \begin{description}312 % \item [Equipment]313 % No specific equipment acquisition.314 % \item [Personnel costs] The faculty members involved in the project315 % are François Charot (INRIA researcher) and Steven Derrien (associate316 % professor).317 % The non-permanent personal required is a PhD318 % student that will mainly work on ASIP generation. We are looking for319 % a profile with strong informatic skills and good knowledge in320 % computer architecture.321 % \parlf322 % The table below summarizes the manpower in \hommemois by tasks for both permanent and323 % non-permanent personnels. The detail by deliverables is given in324 % annexe~\ref{table-livrables-inria} (page \pageref{table-livrables-inria}).325 % The non-permanent personnels costs represent {48\%} of the personnal326 % costs. The requested funding for non permanent personnels is 100\% of327 % the total ANR requested funding.328 % \begin{center}\input{table_inria_cairn_short.tex}\end{center}329 % \item [Subcontracting]330 % No subcontracting costs.331 % \item [Travel]332 % The travel costs are associated to project meeting as well as participation to333 % conferences. The travel costs are estimated to {7,5\%} of the total334 % requested ANR funding.335 % \item [Expenses for inward billing]336 % The costs justified by internal invoicing procedures are evaluated to 4\% of the total337 % requested ANR funding.338 % \end{description}339 164 340 165 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% … … 353 178 and an engineer for 27 \hommemois.} 354 179 {10}{5} 355 356 % \begin{description}357 % \item[Equipment]358 % Acquisition of a FPGA development board will represent the main equipment cost for359 % Bull in COACH. It is estimated at about 5\% (tbc) of the total funding.360 % \item[Personnel costs]361 % A permanent engineer will be assigned full time to the project for a duration of 36362 % months as shown in the table below that summarizes the man power in \hommemois.363 % The detail by deliverables is given in364 % annexe~\ref{table-livrables-bull} (page \pageref{table-livrables-bull}).365 % \begin{center}\input{table_bull_short.tex}\end{center}366 % \item[Subcontracting]367 % No subcontracting costs.368 % \item[Travel]369 % Application of a standard 10\% of the total funding to travel costs.370 % \item[Expenses for inward billing]371 % Costs justified by inward billing are estimated to about 5\% of the total funding.372 % \item[Other working costs] none373 % \end{description}374 375 180 376 181 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -
anr/task-dissemination.tex
r356 r364 84 84 \OtherPartner{12}{36}{\Slip} {0:1:1} 85 85 \OtherPartner{12}{36}{\Stima} {0:1:1} 86 \OtherPartner{12}{36}{\Subs} { .5:1:1}86 \OtherPartner{12}{36}{\Subs} {0:1:1.5} 87 87 \OtherPartner{12}{36}{\Supmc} {0:1:1} 88 88 \OtherPartner{12}{36}{\Sbull} {0:.5:.5}
Note: See TracChangeset
for help on using the changeset viewer.