Extend list scheduler to include cyclic scheduling

When the list scheduler is active it will go time step by time step and assign potential operations.

However, apart from the ability to schedule outputs cyclically added in !472 (merged) the scheduling of operations is entirely non-cyclical.

I see two simple ways to address this:

1. Add ability for user to specify a certain schedule time and if the scheduler is unable to satisfy it while adhering to the resource constraints an attempt at cyclic scheduling will be attempted for the operations after the schedule time.

2. Add ability for user to specify that they want to schedule for

   T_{min}
   . Where
   T_{min}
   must (at least for now) be at least >= highest operation latency. When the current_time of the list scheduler reaches that it will attempt to wrap around the next operations.

If both algorithms fail they should inform the user to relax some constraint.

I suggest that I start with 1. and then consider 2.

added Scheduling label

assigned to @simbj106

changed the description

changed title from Extend list scheduler to include cyclic schedule to Extend list scheduler to include cyclic scheduling

mentioned in issue #301 (closed)

mentioned in merge request !478 (merged)

closed with merge request !478 (merged)