Changeset 356 for anr/section-project-description.tex

Timestamp:

Feb 6, 2011, 2:29:09 PM (13 years ago)

Author:

coach

Message:

1ere Pre-release

File:

• anr/section-project-description.tex (modified) (7 diffs)

anr/section-project-description.tex

@@ -16 +16 @@
 %\mbox{}\vspace*{1ex}\\
 \includegraphics[width=1.0\linewidth]{architecture-hls}
-\caption{\label{archi-hls} Software architecture of hardware accellerator synthesis}
+\caption{\label{archi-hls} Software architecture of HAS (hardware Accelerator Synthesis)}
 %\end{figure}\begin{figure}\leavevmode\center
 %\mbox{}\vspace*{1ex}\\
 \includegraphics[width=.65\linewidth]{architecture-hpc}
-\caption{\label{archi-hpc} Performance analysis of a HPC partitionning}
+\caption{\label{archi-hpc} Performance analysis of a HPC partitioning}
 \end{figure}
 %
@@ -59 +59 @@
 accept the same C++ description and on the other hand make possible
 their chaining. The front-end tools read a \xcoach description and generate
-a new \xcoach description that exibits more parallelism or implement
+a new \xcoach description that exhibits more parallelism or implement
 specific instructions for ASIP. The back-end tools read an \xcoach
 description and generate an \xcoachplus description. This is an \xcoach
@@ -70 +70 @@
 In addition to digital system design, HPC requires a supplementary
 partitioning step presented in figure~\ref{archi-hpc}. The designer
-splits the initial application (tag 1) in two parts: one still on the PC and the
+splits the initial application (tag 1) into two parts: one still on the PC and the
 other running in a FPGA plugged on the PCI/X PC bus. The two parts exchange data
 through communication primitives (tag 2) implemented in a library.
@@ -83 +83 @@
     This task relates to the monitoring of the COACH project.
 \item[Task-2: \textit{\Backbone}] This task tackles the fundamental points of the
-        project such as the defintion of the COACH inputs and outputs,
+        project such as the definition of the COACH inputs and outputs,
     the internal formats (i.e. \xcoach and \xcoachplus) and their associated tools, 
         the architectural templates and the design flow.
@@ -96 +96 @@
     High-Level Synthesis of data dominated description and HLS of control
     dominated description.
-    This task contains also the development of a frequency adaptator
+    This task contains also the development of a frequency adapter
     that will allow the coprocessors to meet processor and bus
     frequency constraints.
 \item[Task-6: \textit{PC/FPGA communication middleware}]
     This task pools the features dedicated to HPC. These are mainly the
-    validation of the partitioning (see figure~\ref{archi-hpc}), the sytem drivers for
+    validation of the partitioning (see figure~\ref{archi-hpc}), the system drivers for
     both PC and FPGA-SoC sides, the hardware communication components and
         the support for dynamic partial reconfiguration.
 \item[Task-7: \textit{Industrial demonstrators}]
     This task groups the demonstrators of the COACH project.
-    Most of them are industrial applications that will be developped within
+    Most of them are industrial applications that will be developed within
     the COACH framework.
     Others consist in integrating the COACH framework as a driver of 
@@ -138 +138 @@
 \item $T2$ drives all the tasks ($T3$, $T4$, $T5$, $T6$) and is at the heart of
 the COACH project.
-\item The demonstrators developped in $T7$, of course strongly depend on the achievements 
+\item The demonstrators developed in $T7$, of course strongly depend on the achievements 
 of the previous tasks ($T2$, $T3$, $T4$, $T5$, $T6$).
 \item $T8$ and $T1$ depend on and impact all the other tasks.
@@ -144 +144 @@
 This organisation offers enough robustness to insure the success of the
 project, the only critical task in this chart being $T2$. \label{xcoach-problem}
-However, the partners met 12 times (a one-day meeting per month) during the last year.
-Ten meeting were dedicated to preliminary technical discussions, including a tentative specification
-of {\tt xcoach}. The other meetings were dedicated to the preparation of the present proposal.
+%However, the partners met 12 times (a one-day meeting per month) during the last year.
+%Ten meeting were dedicated to preliminary technical discussions, including a tentative specification
+%of {\tt xcoach}. The other meetings were dedicated to the preparation of the present proposal.
+However, the partners had 10 one-day meetings where a preliminary draft of the
+\xcoach format was defined. This makes this task less critical.