[47] | 1 | \begin{taskinfo} |
---|
| 2 | \let\UPMC\leader |
---|
| 3 | \let\ALL\enable |
---|
| 4 | \end{taskinfo} |
---|
| 5 | % |
---|
| 6 | \begin{objectif} |
---|
[49] | 7 | This task relies to the diffusion of the project results. |
---|
| 8 | The objective is to ensure the COACH dissemination by publishing on a public WEB site all |
---|
| 9 | the information that a COACH user requires. |
---|
| 10 | The main information features are: |
---|
| 11 | \begin{itemize} |
---|
| 12 | \item The COACH releases (milestones and final release) and their associated installation manuals. |
---|
| 13 | \item The COACH user reference manual. |
---|
| 14 | \item The user manual of the various tools. |
---|
| 15 | \item A COACH tutorial. |
---|
| 16 | \item The conference publication. |
---|
| 17 | \item A user wiki. |
---|
| 18 | \end{itemize} |
---|
[47] | 19 | \end{objectif} |
---|
| 20 | % |
---|
[52] | 21 | \begin{workpackage} |
---|
[49] | 22 | \item This \ST relies to the management of the WEB site and to the distribution of |
---|
| 23 | the COACH releases. |
---|
[47] | 24 | \begin{livrable} |
---|
[52] | 25 | \itemV{0}{6}{d}{\Supmc}{dissemination WEB site} |
---|
[49] | 26 | This deliverable consists firstly in providing a WEB site (name, HTTP server |
---|
| 27 | setup, wiki) and secondly in defining the site map and finally in writting and |
---|
| 28 | installing the pages. |
---|
[52] | 29 | \itemL{6}{36}{}{\Supmc}{dissemination WEB site}{1:.5:.5} |
---|
[49] | 30 | This deliverable corresponds to the standard management of a WEB site (modifying, |
---|
| 31 | adding, suppressing, replacing pages). |
---|
| 32 | Especialy the user reference manuals provided in the other tasks will be published |
---|
| 33 | in this site. The published articles will be also be installed in this site. |
---|
[52] | 34 | \itemL{6}{36}{}{\Supmc}{release handling}{1:.5:.5} |
---|
[49] | 35 | This deliverable deals with the elaboration of the COACH software milestones and |
---|
| 36 | final releases with their installation manuals and to publish then into the WEB |
---|
| 37 | site. |
---|
[47] | 38 | \end{livrable} |
---|
[49] | 39 | \item This \ST consists of making a COACH tutorial and to publish it on the public WEB |
---|
| 40 | site. The tutorial example will also be used as reference demonstrator of the |
---|
| 41 | framework. |
---|
| 42 | The application of this tutorial can be a Motion JPEG application, or an application |
---|
| 43 | that draws in 3D (under open GL) a simulation of a meteor cloud attracted by a sun and |
---|
| 44 | planets, or a database management system. |
---|
| 45 | \begin{livrable} |
---|
[52] | 46 | \itemV{0}{6}{x}{\Supmc}{tutorial specification} |
---|
[49] | 47 | Choice of the application and its implementation as a C/C++ program. |
---|
[52] | 48 | \itemV{6}{12}{d+x}{\Supmc}{tutorial} |
---|
[49] | 49 | The application is split into two communicating parts, the PC part and FPGA-SoC part. |
---|
| 50 | Using the features the T0+12 milestone provides, |
---|
| 51 | the tutorial describes how this efficient partionning was obtained. |
---|
| 52 | The FPGA-SoC part is described as communicating task graph. The tutorial also describes |
---|
| 53 | how a promising task graph can be obtained. |
---|
[52] | 54 | \itemV{18}{24}{d}{\Supmc}{tutorial} |
---|
[49] | 55 | This tutorial shows how a task can be migrated to coprocessor using HAS tools and |
---|
| 56 | how FPGA-SoC can be generated and run to FPGA. This for HAS tools and and |
---|
| 57 | architectural template available in T0+24 milestone. |
---|
[52] | 58 | \itemL{30}{36}{d}{\Supmc}{tutorial}{2:1:1} |
---|
[49] | 59 | The final release of the tutorial. |
---|
[47] | 60 | \end{livrable} |
---|
| 61 | \end{workpackage} |
---|