How do I exit a loop?

I have the loop set up to e.g. 20 iterations.
Let us say I find the result I want at iteration 5..

How do I most efficiently "exit" the loop so I don't waste time on another 15 iterations?

I know we can't do a real exit yet, so it has to be a creative solution

Some process is repeated/looped. At any iteration the result of that process may be acceptable as result and the loop should "stop" and return that.

I have tried using the accumulated value in a threshold to check if the acc. value is good enough and if so bypass the process and use the accumulated value. But that is slow as hell.. as if the full process is always rendered

HELP.

Vlad? FF Devs? Anyone?

Sorry that I can help on this, but I wonder if there could be possible in some way to make a LUA script that could manually add each iteration by pressing a key, so each time you press that key, another new iteration is added, until you get the result wanted, or instead of a key, a click from mouse button. Maybe I am telling a silly thing, as I do not if this would be possible

Quote

Indigo Ray wrote: I don't think that test works. For every iteration, you call get_sample(Accumulated) once to check the threshold, and then certain pixels again for the High input. This is less efficient than not having the threshold check in the first place. For example, try replacing the threshold with a blend component. Now, Accumulated is called only once (for the Foreground input). The blend is faster.

The whole point is to reuse the accumulated sample from previous iteration for the remaining iterations.

The Accumulated components initial value is an invalid one, forcing the Low input of the threshold to be called. When (and if) a value is produced that is above the threshold i.e. a valid sample, the high input, i.e. the accumulated value, will be returned. With that in mind, take a look at the filter or the attached image.

I'm starting to think something is broken with the loop or the threshold or the combination..

IIRC the blend will always fetch both background and foreground, regardless of the opacity setting (I have to retest this.. it was a long time ago I checked last). So this will not work. That it performs better compared to the threshold is because something weird, yet unexplained is going on - a nasty bug I fear.