Hello, I designed a vi to process eye-images and calculate it's center. However i seem to be getting different execution times sometimes 100 ms other times >200ms. I used the flat sequence structure and timers to measure the execution time of the vi . I had some parallel processes and had forced sequential data flow using error terminals.But the problem still remains. I thought that the issue could be due to different input images but executing the same image over and over still shows the same problem. Can anyone tell me what's causing this?

Running code on a Windows system is NEVER deterministic. That being said, designing the code in a way that all memory can be preallocated will be an important step to improve performance. Playing with priorities can also improve things, but you can easily mess up if using priorities in a wrong way. Additionally, running applications in parallel will induce unknown system resource allocation (CPU, memory, interfaces, ...) and therefore lead to increased jitter. If you really have a hard cap for e.g. loop iterations regarding jitter (e.g. must not have a jitter >1us), the only way to address this is moving to RT or maybe even FPGA (depending on the complexity vs. interfaces vs. knowledge/skill). If the determinism is required for hardware IO if not single point (as in control loops), hardware clocked IO and handling data packages in the application is sufficient for 99.99999% of all those applications. Norbert

LabVIEW

varied execution time in image processing

Solved!

Author

Thanks i'll try these out. Sorry for the late reply

Message 11 of 11

(176 Views)

LabVIEW

varied execution time in image processing

Re: varied execution time in image processing