<div class="gmail_quote">On Fri, Sep 9, 2011 at 7:47 AM, Brian J. Murrell <span dir="ltr"><<a href="mailto:brian@interlinx.bc.ca">brian@interlinx.bc.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"> Even with the override and the</div>
schedule 98% good, I am still left with a conflict while there are idle<br>
tuners still available.<br></blockquote><div><br></div><div>In my humble opinion as an end user, any time there are conflicts and idle tuners which could resolve those conflicts, there is a "bug" in the scheduler. It might be the finite state machine (?) that the scheduler uses has a problem or it might be the devs decided the scheduler was "good enough" and it would be very difficult to make it better.</div>
<div><br></div><div>I know nothing of the underlying decision tree the scheduler uses, but it would be neat if it were documented visually in the wiki (SDL anyone?). :-)</div><div><br></div><div>/Brian/</div></div>