Quote:
Originally Posted by Greg McKaskle
I think the thing I'm missing is what your overall goal is, autotuning perhaps?
If you take the nested loop I posted and after the inner loop, where the label Save to disk, etc. is located, and you put your code to analyze the data and recompute the coefficients, then have them update the local variables before the next loop runs. Then change so that the Run button controlling the case turns into some logic for how often you want to run or simply to run every iteration and control how often the outer loop runs.
Greg McKaskle
|
Yes, the goal is autotuning, but I think that is irrelevant with respect to the simple problem I'm facing.
In the simplest terms, what I want is to run a for loop for a number of times,
without blocking execution of the rest of the code (hence, a flat sequence doesn't work) and, after that loop is finished, run a different loop, again without blocking execution.
I need to have data dependency between the two for loops, but not for each iteration, only when the loop has completely finished. I'm thinking a state machine that changes state comparing the current iteration count with the desired number of iterations, should work. Will it or will it not work, or is there a better way?