Currently the resulting Schedule is simply wrapped in an Option context regardless of what happened during scheduling. It would be nice to have better (read: more informative) error reporting.
For instance:
Distinguish between invalid inputs (e.g. r=0 or empty p) and infeasible solutions
Distinguish internal errors produced by the scheduling algorithms (e.g. BnB search encounters partial solution but there are no remaining tasks)
Note that the latter case (internal errors) might be relevant for algorithm debugging but probably are not relevant to users.
Currently the resulting
Scheduleis simply wrapped in anOptioncontext regardless of what happened during scheduling. It would be nice to have better (read: more informative) error reporting.For instance:
r=0or emptyp) and infeasible solutionsNote that the latter case (internal errors) might be relevant for algorithm debugging but probably are not relevant to users.