Changeset 381 for anr


Ignore:
Timestamp:
Feb 16, 2011, 2:49:16 PM (14 years ago)
Author:
coach
Message:

minor modifs + une question sur ST 7-3

M anr/task-demonstrator.tex
M anr/task-backbone.tex
M anr/task-management.tex

Location:
anr
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • anr/task-backbone.tex

    r341 r381  
    3838            synthesis.
    3939          \item[HAS specification] (\Subs):
    40             this part focuses to the Hardware Accelerator Synthesis.
     40            this part focuses on the Hardware Accelerator Synthesis.
    4141            It specifies how tasks must be written (C/C++ subset) and how
    4242            communication schemes must be described for coprocessor synthesis.
  • anr/task-demonstrator.tex

    r367 r381  
    1919    The domain of the application is the treatment of medical images (image noise
    2020    reduction and segmentation or registration).
    21     Our expectation from COACH project is to enhance the \bull HPC solutions that
     21    Our expectation from the COACH project is to enhance the \bull HPC solutions that
    2222    are currently based on multi-cores and GPUs with fine grain parallelism on FPGA.
    2323    \begin{livrable}
    2424      \itemV{0}{6}{d}{\Sbull}{\bull demonstrator}
    25         The deliverable is a document that describes the application that will be use as
     25        The deliverable is a document that describes the application that will be used as
    2626        demonstrator.
    2727      \itemV{6}{12}{x}{\Sbull}{\bull demonstrator}
     
    6767    \thales will use its internal software environment tool SPEAR DE to describe the
    6868    application. The tool is able to partition and to generate the code for the target. \\
     69%%%%
     70%%%% j'avai cru comprendre que ce serait le contraire, et que TRT souhaitait récupérer le
     71%%%% découpage en processus (D430) comme entrée de SPEAR-DE. Paul
     72%%%%
     73
    6974    In this task, we will adapt SPEAR DE to generate the application description input of
    7075    COACH framework. We will also describe the three templates of architecture in order to
  • anr/task-management.tex

    r347 r381  
    3737        \OtherPartner{0}{36}{\Sbull}  {.5:.5:.5}%
    3838        Project management at the partner level. It includes mainly the progress
    39         monitoring, the record keeping the participation to the project meetings
     39        monitoring, the record keeping, the participation to the project meetings
    4040        and the communication with the project leader and the other partners.
    4141    \end{livrable}
Note: See TracChangeset for help on using the changeset viewer.