Project

General

Profile

Feature #3802

Define GUI patterns for (non-periodic) timing constraints

Added by Marco Volpe about 1 year ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
08/21/2019
Due date:
% Done:

0%

Estimated time:

Description

Currently, timing constraints get automatically generated from the timing specification.
It should be provided a user interface in the constraint modeling section, where "patterns" are given for specifying which subset of constraints shall be considered in a specific DSE run.
This is similar to what happens for HW property patterns.
We note that this does not apply to periodic constraints, which cannot be deselected and should be considered implicit. Running a schedule synthesis should actually not be allowed in the case when periods are not defined.


Related issues

Related to Bug #3793: In the DSE navigator, timing constraints and energy-related objectives get generated at each run Rejected08/07/2019

History

#1 Updated by Marco Volpe about 1 year ago

  • Related to Bug #3793: In the DSE navigator, timing constraints and energy-related objectives get generated at each run added

#2 Updated by Marco Volpe about 1 year ago

This feature should also provide a solution to Bug #3793, at least for what concerns timing constraints.

#3 Updated by Marco Volpe 12 months ago

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

#4 Updated by Alexander Diewald 8 months ago

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

#5 Updated by Marco Volpe about 2 months ago

  • Assignee changed from Marco Volpe to Johannes Eder

Also available in: Atom PDF