Changes between Version 16 and Version 17 of projectstructure


Ignore:
Timestamp:
Jun 16, 2008, 4:33:37 PM (16 years ago)
Author:
fpecheux
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • projectstructure

    v16 v17  
    6161|| Status : '''not achieved yet'''||
    6262[[BR]]
    63 || '''Task  2.b''' :  Hard/Soft alert triggering, Task manager : '''LIP6''', Partners : '''ALL'''. Among the remapping strategies that will later be presented in WP3; some, or a sequence of those applied over time may have hardly predictable effects on application performance. In order to keep track of mid- or long-term consequences of those remapping decisions, a statistical analysis of the DRET and AIM databases will be performed. These information may later help refining the decision-taking policy when, for instance, a previous task migration order led to a worst global solution.
     63|| '''Task  2.b''' :  Hard/Soft alert triggering, Task manager : '''LIP6''', Partners : '''ALL'''. This task is dedicated to the appropriate exploitation of the formatted events available in the tables of the DRET, filled by all the mechanisms studied in WP1. Exploitation covers Boolean computing on events, ordering, classifying, filtering, accumulating, mean-value calculation, and finally triggering of an appropriate action.
     64This task intends to identify how to write these second level instrumentation threads (with respect to the first level instrumentation threads studied in WP1) that are designed to be the reactive part of the online monitoring, for they decide to trigger the next step or not. Next step can either be further analysis through test (2c) or direct remapping (WP3).
    6465|| T0+6 → T0+24||
    65 || Status : '''not achieved yet'''||
     66|| Status : '''not achieved yet'''||
     67[[BR]]
     68|| '''Task  2.c''' :  Functional/structural test, Task manager : LIP6, Partners : LIP6. Among the remapping strategies that will later be presented in WP3; some, or a sequence of those applied over time may have hardly predictable effects on application performance. In order to keep track of mid- or long-term consequences of those remapping decisions, a statistical analysis of the DRET and AIM databases will be performed. These information may later help refining the decision-taking policy when, for instance, a previous task migration order led to a worst global solution.
     69|| T0+6 → T0+24||
     70|| Status : '''not achieved yet'''|| 
    6671