Project

General

Profile

Feature #3708

Feature #3258: Hardware Platform Exploration

Feature #3707: Platform exploration for the Hierarchical Platform

Exploration of ExecutionUnit numbers as a variance-based exploration

Added by Alexander Diewald over 1 year ago. Updated 10 months ago.

Status:
In Progress
Priority:
High
Category:
-
Target version:
Start date:
04/10/2019
Due date:
% Done:

80%

Estimated time:
30.00 h

Description

Goal

Vary the number of ExecutionUnits that are used as deployment targets for the task mapping. Here, only ExecutionUnit numbers shall be available that are also present in variants of target (COTS) processors.

ACC-SafetyReq-Platform.af3_23 (1.23 MB) ACC-SafetyReq-Platform.af3_23 Alexander Diewald, 04/23/2019 04:04 PM

History

#1 Updated by Alexander Diewald over 1 year ago

Initial non-yet operational version is uploaded.

#2 Updated by Alexander Diewald over 1 year ago

  • Status changed from New to Resolved
  • Assignee changed from Alexander Diewald to Simon Barner

#3 Updated by Alexander Diewald over 1 year ago

Added example model.

Also, one change (bug fix) was not committed in the kernel ( :/ ):
https://git.fortiss.org/af3/kernel/merge_requests/51

#4 Updated by Alexander Diewald over 1 year ago

  • % Done changed from 0 to 100

Mismerge from before is fixed now.

#5 Updated by Simon Barner over 1 year ago

The merge requests for the af3 and kernel repositories have been merged. For exploration.alg, the following problems remain

  • When using the DSE configuration saved in the provided example, the exploration does not terminate. However, when manually forcing the exploration to stop, the solution has already been found and can be exported.
  • Defining a new DSE configuration now requires Core s to be modeled (since these are the only admissible task->HW allocation targets. However, the presence of cores confuses the platform exploration that currently expects that Tile s have been imported.
  • Bonus level: Is it possible to set the name of the exported solutions according the type of the (major) synthesized artifacts, i.e. "Platform 0", "Platform 1" instead of "Solution 0" as it is already the case of the SMT-based exploration?

#6 Updated by Simon Barner over 1 year ago

  • Status changed from Resolved to Feedback
  • Assignee changed from Simon Barner to Alexander Diewald
  • % Done changed from 100 to 80

#7 Updated by Alexander Diewald about 1 year ago

  • Status changed from Feedback to In Progress
  • Target version changed from AF3 2.16 RC1 (Feature Freeze) to AF3 2.17 (Feature Freeze)

#8 Updated by Alexander Diewald about 1 year ago

  • Priority changed from Normal to High

#9 Updated by Alexander Diewald 10 months ago

  • Target version changed from AF3 2.17 (Feature Freeze) to Backlog

Also available in: Atom PDF