Hi LV_Pro, good to see I've got the pro's on board!
I included example data in the example vis - there's a constant array of waveforms that it'll process and plot each of in turn. The first two should plot fine, the third will give NaN. There's a popup between each plot, so you can click 'cancel' to stop execution and see what values were last used. I've also got the manual FFT to stop execution as soon as it generates an NaN reading. I'm afraid you'll have to be a bit patient - as it only seems to happen on some datasets I've included real data, but the manual FFT takes a while to process it.
@GerdW, thanks also for helping. I've looked at the dataset, and there are indicators that trace through to check what data is going where - the waveform contains an array of doubles containing no NaN's; that passes into two nested For loops, (at least in my manual version) and it's on the innermost for loop that it goes to get the first array value and gets 'NaN' instead of the actual data.
As for the race condition in the manual version ... Other than debugging indicators the whole thing only uses a single set of inputs and outputs, so I don't see where there would be race conditions in the operation? (I did however just realise I forgot to wire up that sequence structure - that was going to be to ensure the cluster output is written to last for reading internal state values at the time it first reads NaN. Perhaps you meant that?)
