Closed nmcglo closed 5 years ago
Jonathan Jenkins:
Thankfully ended up being easier to implement than expected (though with a bit of magic to distinguish a combined "new msg+schedule next" event from a "schedule next" event. No problems seen from anyone, so in it goes.
Jonathan Jenkins:
Status changed to closed
Original Issue Author: Jonathan Jenkins Original Issue ID: 51 Original Issue URL: https://xgitlab.cels.anl.gov/codes/codes/issues/51
Currently, the event flow is
If the queue is empty, then the event separating the sched_new and the sched_next functions is unnecessary. Less events is better.