08-05-2025 09:00 AM - edited 08-05-2025 09:06 AM
I would probably set it to update the graph every n iterations or about once per second so we have something to look at. 😄
08-08-2025 03:12 AM
Yes, I've used nearly zero changes to original implementation (just to measure time spent). I did it in literally in two minutes before running to catch the bus, then left it to process the data overnight. 🙂
But if I try to update every Nth as you suggested (measured on 2M samples, some music and background stuff is running, so, it is a bit slower):
08-11-2025 01:30 PM
I am working on real-time processing on an FPGA, where I have to avoid making any such array.
08-11-2025 02:00 PM
Hi sonisatyam,
@sonisatyam wrote:
I am working on real-time processing on an FPGA, where I have to avoid making any such array.
In the FPGA you don't have an UI and so you don't have any graphs or charts…
Or to put it the other way around: your data display stays in the host VI where you should have enough memory to handle larger arrays!