enforcing tile computation order
A while ago I wrote an operator to 'regionalize' an image, ie. identify regions of uniform value in the source image...
But I did a pretty poor job of dealing with regions that cross tile boundaries :-( The easiest way to fix the problems, and avoid artefacts on tile boundaries, is to impose an order to the computation of tiles. But what is the best way to do this ?
I'd rather not mess with TileScheduler if I don't have to (looks scary in there). I was thinking it might be OK to use java.util.concurrent classes within my OpImage class to impose an order, e.g. when tile X, Y is requested a blocking queue ensures that all prior (spatially) tiles are computed and cached first.
Does this sound reasonable ? Is there an easier way ?
Very grateful for any tips