You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here are some of the ideas for improvement and feature requests beyond #9:
Conditional variations (just what we talked about in the last meeting)
Generate an overview CSV file: It's currently hard to determine which alternatives were chosen for each variation. However, this information is of course known at runtime so it could just be stored as a single CSV file while generating
New variation type: Data Operations. The approach for data flow analysis allows the modeling of characteristics (already possible to create variations) but also defines manipulations of data labels (can be seen in the graphical editor in usage models and SEFFs). This could be another interesting point to vary. They are at least saved in the .aird file, e.g., here in line 6654, 6662 etc.: https://github.com/FluidTrust/CaseStudies/blob/main/casestudies/PortCaseStudy/representations.aird They are contained in the SEFF-Elements inside the repository
Optimizing performance: An option to parallelize the generation would be interesting, however this might conflict with some eclipse internal magic
The text was updated successfully, but these errors were encountered:
Here are some of the ideas for improvement and feature requests beyond #9:
They are at least saved in theThey are contained in the SEFF-Elements inside the repository.aird
file, e.g., here in line 6654, 6662 etc.: https://github.com/FluidTrust/CaseStudies/blob/main/casestudies/PortCaseStudy/representations.airdThe text was updated successfully, but these errors were encountered: