![shift registers labview shift registers labview](https://i.stack.imgur.com/fzOOu.png)
I tried to benchmark this (LV8.6) by taking an "AE" who had two "actions" (true and false) and each action was to invert the current state.
#Shift registers labview free
Nevertheless, feel free to submit it as a suggestion. Honestly, a feedback node stands out more to me on the diagram than two separate nodes would, especially if the feedback nodes are consistently placed between diagrams. All of these factors together make functional globals very obvious in my code.Īs for your feature suggestion, I really don't see enough of a difference between your mockups and uninitialized shift registers. And when I use Feedback Nodes to store data in the functional global, the feedback nodes are always at the very top of the diagram. They also have different colored icons to set them apart on block diagrams. Yair: All of my functional globals have "FG" in their VI name, and I typically keep them all in the same folder when developing an app. As the data sets get larger, the loop overhead becomes a smaller and smaller part of the overall execution time. This lends credence to my earlier assertion that the main performance benefit has to do with eliminating loop overhead. Jim: I'm still seeing very slight performance gains with the Feedback Node when dealing with large data sets, but I see the gain become smaller as the data set gets larger. I think I'll try using this method a bit to see how it works out and then I'll be able to tell. And to be honest, the loop doesn't take up THAT much space. This might simply be a matter of conventions, but I get the distinct feeling that it isn't and that you would REALLY need to get used to that notation before you find it natural. When you have to start figuring out how it works and when, it's easier to just use where it's much clearer (to me) which data is being used, when it's initialized, etc.
![shift registers labview shift registers labview](http://1.bp.blogspot.com/--iw0v0cIfc0/TZt82z6XfLI/AAAAAAAAAEM/orurwN3GomA/s1600/timer.png)
I don't really use the way you posted for a simple reason - I find the loop method to be more readable. This is essentially a buffer which is held inside a single case of a case structure. The ability to place it inside a structure and initialize it from several layers out. To be fair, this may have been around in 7.0 too, but I'm not sure.Ģ.
#Shift registers labview code
When it's pointing to the right, code which uses it usually becomes much more readable. I didn't use it in 7.0 where it was still immature, but in 8.6 I use it all the time, mainly due to two improvements:ġ.