Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 4072
  • 3541
  • 3838
  • safety_functions
  • 3690
  • backup
7 results
Search by author
  • Any Author
  • Andreas Bayha Andreas Bayha bayha
  • Konstantin Blaschke Konstantin Blaschke blaschke
  • Sebastian Bergemann Sebastian Bergemann bergemann
  • Simon Barner Simon Barner barner
  • Tarik Terzimehic Tarik Terzimehic terzimehic
  • Tiziano Munaro Tiziano Munaro munaro
6 authors
  1. Nov 22, 2019
  3. Nov 19, 2019
    • Alexander Diewald's avatar
      Fixup the guice feature dependency resolution · 3307b671
      Alexander Diewald authored 
      
* Previous implementation was broken and only worked for the mapping +
  scheduling configuration.
* Produced types are no longer explicitly exposed by D3SEModules as they
  would bind to the inputs of these modules. Instead a D3SEInjector
  wrapper is responsible for obtaining the Feature-annotated artifacts.
* Inputs of D3SEModules don't need to specify @Genotyped or
  @InputArtifact annotations anymore that cause a fix type binding and
  conflict with the dynamic feature selection. Instead, these
  annotations are bound by the configuration phase.
* Creates and Decodes annotations are removed as they are no longer
  needed.

Signed-off-by: default avatarAlexander Diewald <diewald@fortiss.org>
      3307b671
  5. Nov 01, 2019
  7. Oct 18, 2019
  9. Oct 15, 2019
    • Alexander Diewald's avatar
      D3SE: Enable dependencies between exploration features · 73722a06
      Alexander Diewald authored 
      
* IExplorationFeatures can now declare their predecessors and
  successors by priorTo() and after() statements.
* All creator and decoder modules are now d3se modules that are private
  guice modules.
* The d3se modules mark every generated output with their containing
  features as an annotation. This allows the same type to be provided
  by different modules. The coupling of feature-annotated artifacts is
  done by a feature dependency graph and the module config phase from
  guice.
* Within d3se modules, only the artifacts are visible (no need to reason
  about their origin --> handled when declaring the feature).
* IExplorationFeatures are pluggable and can be en-/disabled subject to
  a system's needs.

Signed-off-by: default avatarAlexander Diewald <diewald@fortiss.org>
      73722a06
  11. Sep 19, 2019
  13. Sep 18, 2019
  15. Sep 17, 2019
  17. Sep 15, 2019
  19. Sep 13, 2019
  21. Sep 12, 2019
  23. Sep 11, 2019
  25. Sep 10, 2019
  27. Sep 09, 2019
  29. Sep 08, 2019
  31. Sep 07, 2019
  33. Sep 06, 2019
  35. Sep 05, 2019