Transfering a boolean signal out of a while loop after every iteration

[KFod]

I am using a "Mask and Limit" to produce boolean signals based on data being collected. Inside the loop, this will obviously produce a boolean with every iteration. However, I need this boolean signal to be available outside of the loop with every iteration as well. Is there a way to make this constant stream of booleans available outside of the loop?

Thank you in advance.

[palanivel]

You can use variable if your program won't create racing conditions....
if not use notifier /functional global/ queues To update to outside loop..

[mikeporter]

This is what you would use a producer-consumer design pattern for. Here is a good place to start.

http://www.notatamelion.com/2014/10/07/build-a-proper-labview-produceconsumer-pattern/

Mike...

[KFod]

As a side question, would having an indicator inside the loop passing the continuous booleans to a local variable outside the loop work? Or, even better, notifiers?

[mikeporter]

Local variables "work" in the sense that they would pass out the data, but would cause a bunch of other problems like race conditions, catching transitions, etc. Notifiers would be a (small) step in the right direction, but they have other limitations.

What I try to do in the post I cited (and the ones following) was to walk you through the process of looking at options and deciding what you really need for your application

Mike...

[palanivel]

Addition to mike post ...
In case of local variables there is chance that previous iteration value can be taken for process in the outside loop....

So it's better to use notifier, which will wait for new value to process the outside loop...

[mikeporter]

While local variables can allow you to process the same data multiple times, notifiers create the potential of missing data updates all together. If a notification is sent and you don't read it before a second one is sent, the second notification will overwrite the first and you lose the data contained in the first notification.

Mike...

[palanivel]

Agree with your point @mike

[natasftw]

You're looking for the word "queue."  Let the notifiers go.

[mikeporter]

The problem with queues is that if you want the rest of the application to be event-driven, queues don't integrate well. You often end up needing to poll the queue which defeats one of the main reasons to use an event-driven structure in the first place -- efficiency.

Mike...