Changes between Version 11 and Version 12 of projectstructure

Timestamp:

Jun 16, 2008, 4:27:09 PM (17 years ago)

Author:

fpecheux

Comment:

--

projectstructure

@@ -52 +52 @@
 This work-package is dedicated to online diagnosis. It aims at building and managing a database of  relevant cartographies of the MP2SoC from the Distributed Raw Event Tables elaborated in WP1. In ADAM, a cartography for a given event type is called an Architecture Instant Map (AIM). An AIM is a collection of relevant events extracted from DRET or newly aggregate and computed events with their exact physical locations and characteristics at a given time. 
 
-In other terms, WP2 exploits the local information found in the Distributed Raw Event Tables (DRET) as an entry point to compute efficient data structures that can be used appropriately during the next phase, constrained remapping. Maintaining at all times a database of AIMs, called AIM Consolidated Database, and their corresponding histories can be of great interest in order to perform multi-criteria mapping and optimization. 
+In other terms, WP2 exploits the local information found in the Distributed Raw Event Tables (DRET) as an entry point to compute efficient data structures that can be used appropriately during the next phase, constrained remapping. Maintaining at all times a database of AIMs, called AIM Consolidated Database, and their corresponding histories can be of great interest in order to perform multi-criteria mapping and optimization.
+
+This work-package is composed of four tasks, 2a to 2d. All these tasks collaborate to define the interoperable AIM database and its access mechanisms (task 2d). More precisely, Task 2a is responsible for performing statistical analysis on raw or historized events. Task 2b is responsible for triggering actions when a set of events matches a certain condition, and task 2c defines one of these actions, online functional/structural testing. When dealing with fault detection, this work-package performs intrusive monitoring in the form of functional/structural test to determine with optimal accuracy the deficient hardware resources. 
+
+[[BR]]
+|| '''Task  2.a''' :  Statistical analysis Task manager : '''LIRMM''' Partners : LIRMM 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.
+|| T0+12 → T0+24||
+|| Status : '''not achieved yet'''|| 
+
+