Changeset 287

Timestamp:

Dec 6, 2010, 5:26:44 PM (14 years ago)

Author:

coach

Message:

MAJ après réunion de travail Ivan, Magillem
Liste des livrables

Location:

anr

Files:

• section-4.1.tex (modified) (1 diff)
• task-1.tex (modified) (2 diffs)
• task-4.tex (modified) (1 diff)
• task-5.tex (modified) (5 diffs)
• task-7.tex (modified) (3 diffs)

anr/section-4.1.tex

@@ -9 +9 @@
 \mbox{}\vspace*{1ex}\\
 \includegraphics[width=.8\linewidth]{architecture-hpc}
-\caption{\label{archi-hpc} Software architecture of HPC}
+\caption{\label{archi-hpc} Performance analysis of a HPC partitionning}
 \end{figure}
 %

anr/task-1.tex

@@ -5 +5 @@
 %
 \begin{objectif}
-This task deals with the main features of digital systems.
-Its objectives are the specification of the designer input, the
+The objectives of this task are the specification of the designer input, the
 definition of the hardware architectural templates and of all the features
 that the HAS tools will share.
+An other objective is the specification of the framework used to facilitate the 
+exploitation and the integration of the core engine into an industrial flow.
 \end{objectif}
 %
 \begin{workpackage}
 \subtask{Specification of the COACH environment}
-    This \ST specifies the COACH environment for the system designer. In this
-    \ST the COACH framework is a black box. The deliverables are documents 
-    specifying: how to feed COACH (the inputs), how to use COACH (use model),
-    what is generated (the outputs).
+    This \ST specifies the global COACH environment for the system designer:
+    the core engine which is seen as a black box associated
+    with a configuration framework based on Eclipse.
+    This framework will be integated into Magillem tool suite.
+    The deliverables specify 
+    how to feed COACH (the inputs),
+    how to use COACH (use model),
+    what is generated (the outputs)
+    and  how the Magillem framework iteracts with the core engine.
     \begin{livrable}
     \itemV{0}{6}{d}{\Supmc}{Use model specification}
-        This document describes the use modle of COACH. It will be a cooperative work.
+        This document describes the use model of COACH. It will be a cooperative work.
         Its main parts are:
         \begin{description}
           \item[General overview] (\Supmc)
-          \item[CSG specification] (\Stima)
-            Here the COACH System Generator Generator is specified:
+          \item[CSG specification] (\Stima):
+            here the COACH System Generator Generator is specified:
             how the task graph is described, the communication schemes and
             its associated API (Application  Programming Interface).
@@ -31 +37 @@
             Nevertheless, these basic schemes will be enhanced to allow more efficient
             synthesis.
-          \item[HAS specification] (\Subs)
-            This part focuses to the Hardware Accelerator Synthesis.
+          \item[HAS specification] (\Subs):
+            this part focuses to the Hardware Accelerator Synthesis.
             It specifies how tasks must be written (C/C++ subset) and how
             communication schemes must be described for coprocessor synthesis.
+          \item[Magillem framework specification] (\Smds):
+            this part specifies the fonctionnalities enabling the interactions between
+            Magillem and the core engine.
         \end{description}
     \itemL{6}{12}{d}{\Supmc}{Use model specification}{3:0:0}

anr/task-4.tex

@@ -43 +43 @@
         Release of the GAUT software that is able to read \xcoach format and to write \xcoachplus format.
     \end{livrable}
+%
+\subtask{Adapting HAS tools to the COACH communication schemes}
+    \begin{livrable}
+    \itemL{12}{18}{x}{\Supmc}{UGH update for COACH communications}{0:2:4.0}
+        Release of the UGH software that interprets the API of task communication.
+    \itemL{12}{18}{x}{\Subs}{GAUT update for COACH communications}{0:2:4.0}
+        Release of the GAUT software that interprets the API of task communication.
+    \end{livrable}
 
 \subtask{Coprocessor frequency adaptation}

anr/task-5.tex

@@ -11 +11 @@
 %
 \begin{objectif}
-This task pools the features dedicated to HPC system design. It is described on
-figures~\ref{coach-flow} and \ref{archi-hpc}. It consists in
+This task deals with the COACH HPC feature that consists in accelerating an existing
+application running on a PC by migrating critical parts into a SoC implemented on an
+FPGA plugged to the PC PCI/X bus (figures~\ref{coach-flow} and \ref{archi-hpc}).
+It consists in:
 \begin{itemize}
-\item Providing a software tool that helps the HPC designer to find a good partition of the initial application
-    (figure~\ref{archi-hpc}).
-\item specification of the communication schemes between the software part running on the PC and the
+\item Specification and implementation of the communication schemes between the software part running on the PC and the
 FPGA-SoC.
-\item Implementing the communication scheme at all levels: partition help, software
-implementation both on the PC and in the operating system of the FPGA-SoC, hardware.
-%\item Providing support for dynamic partial reconfiguration of \xilinx FPGA in order
-%to optimize FPGA ressource usage.
+\item Providing a performance analysis tool helping user in the HPC partitionning (figure~\ref{archi-hpc}).
+\item Providing support for configuration of the FPGA in order to set up the HPC environement.
 \end{itemize}
 
@@ -34 +32 @@
 \begin{workpackage}
   \subtask{Implementation of API between PC and FPGA-SoC}
-    This \ST deals with the COACH HPC feature that consists in accelerating an existing
-    application running on a PC by migrating critical parts into a SoC implemented on an
-    FPGA plugged to the PC PCI/X bus.
-    The main steps and components of this \ST are:
-    \begin{itemize}
-      \item The definition of the communication middleware as a software API (Application
-        Programing Interface) between the application part running on the PC and the
-        application part running on the FPGA-SoC.
-      \item A software for helping the end-user to partition applications (figure~\ref{archi-hpc}).
-        This software is a library implementing the communication API with features to profile
-        the partitioned application.
-      \item The implementation of the communication API on the both sides (PC part and FPGA-SoC).
-    \end{itemize}
     \begin{livrable}
       \itemL{0}{6}{d}{\Sbull}{HPC communication API}{3:0:0}
@@ -73 +58 @@
 
 \subtask{SystemC model of the PCI/X}
-    This \ST deals with the implementation of hardware and SystemC modules
+    This \ST deals with the implementation of SystemC modules
     required by the neutral architectural template for using the PCI/X IP of \altera and \xilinx.
     \begin{livrable}
@@ -88 +73 @@
     \end{livrable}
 
-% \subtask This \ST consists in integrating dynamic partial reconfiguration of \xilinx FPGA in the CSG design flow.
+\subtask{HPC environment set up}
+
 % It also includes appropriate SoC-FPGA OS drivers and a modification of the profiling library.
-%     \begin{livrable}
-%     \itemL{24}{36}{x}{\Supmc}{CSG support for \ganttlf reconfiguration}{0:0:2}
-%         Modification of the CSG software to support statically reconfigurable tasks.
+     \begin{livrable}
+     \itemL{24}{36}{x}{\Stima}{Support for HPC environment set up}{0:0:2}
+      Modification of the CSG software to set-up the HPC environement: Bitsream loader.
+     \end{livrable}
 %     \itemL{18}{36}{x}{\Stima}{CSG module for \ganttlf dynamic reconfiguration}{0:4:12}
 %               This livrable is a CSG module allowing to partition the task graph along
@@ -118 +105 @@
 % %   \begin{livrable}
 % %   \itemL{0}{6}{m}{\Saltera}{HPC development boards}{0:0:0} Two PCI/X FPGA boards.
-% %   \end{livrable}
 \end{workpackage}

anr/task-7.tex

@@ -20 +20 @@
 %
 \begin{workpackage}
-  \subtask{\mustbecompleted{TITLE}} This \ST relates to the management of the WEB site and to the distribution of
-    the COACH releases.
+  \subtask{Distribution of COACH releases}
     \begin{livrable}
-      \itemV{0}{6}{d}{\Supmc}{Dissemination WEB site}
-        This deliverable consists firstly in providing a WEB site (name, HTTP server
-        setup, wiki) and secondly in defining the site map and finally in writting and
-        installing the pages.
-      \itemL{6}{36}{d}{\Supmc}{Dissemination WEB site}{1:.5:.5}
-        This deliverable corresponds to the standard management of a WEB site (modifying,
-        adding, suppressing, replacing pages).
-        Especialy the user reference manuals provided in the other tasks will be published
-        on this site. The published articles will be also be installed in this site.
-      \itemL{6}{36}{d+x}{\Supmc}{Release handling}{1:.5:.5}
+      \itemL{6}{36}{d+x}{\Supmc}{Open source release}{1:.5:.5}
+        \OtherPartner{12}{36}{\Stima}{0:2:1}
         This deliverable deals with the elaboration of the COACH software milestones and
         final releases with their installation manuals and to publish then into the WEB
         site.
-      \OtherPartner{12}{36}{\Stima}{0:2:1}
+      \itemL{6}{36}{d+x}{\Smds}{Commercial release}{1:.5:.5}
+        This deliverable deals with the elaboration of a release of COACH integrated
+        into the Magillem environment.
     \end{livrable}
-  \subtask{\mustbecompleted{TITLE}}
+  \subtask{Tutorial}
     \label{subtask-tutorial}
     This \ST consists of making a COACH tutorial and to publish it on the public WEB
@@ -54 +47 @@
         how a promising task graph can be obtained.
     \itemV{18}{24}{d}{\Supmc}{Tutorial}
+        \OtherPartner{12}{36}{\Smds}{0:2:2}
         This tutorial shows how a task can be migrated to coprocessor using HAS tools and
         how FPGA-SoC can be generated and run to FPGA. This for HAS tools and and
-        architectural template available in T0+24 milestone.
+        architectural template available in T0+24 milestone.\\
+        A part (written by \Smds) will be dedicated to the integration of COACH generated IP
+        into an IP-XACT based design flow (such as SOCKET).
     \itemL{30}{36}{d}{\Supmc}{Tutorial}{2:1:1}
         The final release of the tutorial.
     \end{livrable}
-  \subtask{\mustbecompleted{TITLE}}  
+  \subtask{Reference user manuals}  
     This \ST consists of making the COACH user reference manuals.
     They will be published on the public WEB site.
@@ -74 +70 @@
                 the COACH project. 
       \OtherPartner{12}{36}{\Subs}{0:2:2}
+    \itemL{18}{36}{d}{\Smds}{Magillem framework user manual}{0:1:1}
+        This user manual describes how to use COACH within the IP-XACT based Magillem tool suite.
    \end{livrable}
 \end{workpackage}