Dylan Leothaud
Dylan Leothaud
In my opinion, the current implementation of the simplex scheduling for the `ChainingCyclicProblem` is missing some constraints. The `ChainingCyclicProblem` was made by merging the `ChainingProblem` and the `CyclicProblem`. It was...
Pinging potential reviewers: @jopperm
I am working on a project in which I am adding a transformation that schedules many very similar problems. To improve efficiency, I considered modifying the `Problem` directly rather than...
> Do you need additional APIs there, e.g. to reset the solution properties or so? Scheduling an already scheduled problem overwrites the previous solution data, such as initiation interval or...
> I think I start to understand. Yes, if you want to selectively deactivate edges, I'd also say, model that as a new dependence property in a new sub-problem, but...
> My concern was that these removeXXX() methods would need to be virtual and overridden in every subclass that introduces new properties, in order to remove the entries for the...
> How would you handle passing additional arguments (objective function, cycle time, last op, etc.) to the concrete scheduler? Probably some form of argument forwarding could work. - I don't...
I added a `Scheduler` interface and adapted the existing schedulers and the documentation. If the pull request is accepted, squashing the commits may be a good idea to have a...