Project

General

Profile

Feature #3690

Feature #3689: Extend the DseML to enable expressions to specifiy non-existing elements and attributes

Extend the DseML for VariablePropertyLiterals and a generic Property Lookup method for binding functions of two elements

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

Status:
Rejected
Priority:
High
Category:
-
Start date:
03/21/2019
Due date:
% Done:

60%

Estimated time:
5.00 h

Description

  • Add a "VariablePropertyLiteral" to enable specifying non-existing attributes of model elements.
  • Add a generic binding function to specify lookups of properties of one model element from another one.
test_dse (1).af3_23 (199 KB) test_dse (1).af3_23 Marco Volpe, 02/21/2020 07:34 PM

Related issues

Related to Change Request #3472: Scheduling Formalizatio: Clarify / cleanup StartTimeDummy and DurationDummyRejected07/05/2018

Blocks Feature #3667: Move the schedule latency minimization to a patternNew03/06/2019

Precedes Change Request #3551: In the formulation of a scheduling problem, replace ResourceAllocations with Tasks and SignalsNew04/30/201904/30/2019

History

#1 Updated by Alexander Diewald over 1 year ago

  • Parent task set to #3689

#2 Updated by Alexander Diewald over 1 year ago

  • Status changed from New to In Progress

#3 Updated by Alexander Diewald over 1 year ago

  • Assignee changed from Alexander Diewald to Marco Volpe
  • % Done changed from 0 to 30

As discussed in the JF.

#4 Updated by Alexander Diewald over 1 year ago

#5 Updated by Johannes Eder over 1 year ago

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

#6 Updated by Simon Barner over 1 year ago

  • Related to Change Request #3472: Scheduling Formalizatio: Clarify / cleanup StartTimeDummy and DurationDummy added

#7 Updated by Alexander Diewald over 1 year ago

  • Assignee changed from Marco Volpe to Alexander Diewald
  • Target version changed from AF3 2.16 RC1 (Feature Freeze) to Team Programming July 2nd 2019

#8 Updated by Alexander Diewald about 1 year ago

  • Target version changed from Team Programming July 2nd 2019 to AF3 2.16 RC1 (Feature Freeze)

#9 Updated by Alexander Diewald about 1 year ago

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

#10 Updated by Alexander Diewald 12 months ago

  • Related to Change Request #3551: In the formulation of a scheduling problem, replace ResourceAllocations with Tasks and Signals added

#11 Updated by Alexander Diewald 12 months ago

  • Related to deleted (Change Request #3551: In the formulation of a scheduling problem, replace ResourceAllocations with Tasks and Signals)

#12 Updated by Alexander Diewald 12 months ago

  • Precedes Change Request #3551: In the formulation of a scheduling problem, replace ResourceAllocations with Tasks and Signals added

#13 Updated by Alexander Diewald 11 months ago

  • Priority changed from Normal to High

#14 Updated by Alexander Diewald 9 months ago

  • Blocks Feature #3667: Move the schedule latency minimization to a pattern added

#15 Updated by Alexander Diewald 8 months ago

  • Assignee changed from Alexander Diewald to Marco Volpe
  • % Done changed from 30 to 60

The functional style ModelElementPropertyLiterals are done now and can be reviewed. They are now named IPropertyLiterals --> ArithmeticPropertyLiteral / BooleanPropertyLiteral.

As discussed before, I'd ask you to review this one for an intermediate merge such that this branch does not diverge again.
MR: https://git.fortiss.org/af3/af3/merge_requests/278

Please review the code as-is and define some Objective(s) and Constraint(s) and execute both the task mapping and scheduling. Please also import one of your old models (with objectives/constraints defined) to verify that the migrator is operating correctly.
Thanks!

#16 Updated by Marco Volpe 7 months ago

Tested and reviewed. It seems to work fine. I also tried on some old model.
Only found problems in importing models where some timing constraint is defined by using StartTimeDummy or DurationDummy variables, e.g., the enclosed one.
But maybe we can live with that.

#17 Updated by Marco Volpe 7 months ago

  • Assignee changed from Marco Volpe to Alexander Diewald

#18 Updated by Alexander Diewald 7 months ago

Thanks! The intermediate merge is done.

The StartTimeDummy and DurationDummy annotations were just stubs to denote the variable parameters to be explored. They are constructed on-the-fly when launching an exploration and do not even have an assigned value after exploration. Hence, they only appear in the DseML formulation that is saved with the solutions, but they do not provide any value there such that we can just ignore them.

#19 Updated by Alexander Diewald 6 months ago

#20 Updated by Alexander Diewald 6 months ago

  • Status changed from In Progress to Rejected

Also available in: Atom PDF