Parrallel testing using rentrant VIs with Funtional Globals

[glennjammin]

I belive that in order to run a vi in parallel in teststand you must make it reentrant.

My problem is that one of my VIs uses a functional global and I don't want it to effect the other VIs ran for the other test sockets.

What is the best way to handle funtional globals in a parallel or batch process model?

Also is there a way to have Teststand handle whether or not the VI is reentrant?

[Flamboyant]

make the functional global also re-entrant

[glennjammin]

Making the Funtional Global reentrant won't work since it will just creat a copy every time it is called.

[James_D · Accepted solution]

Greetings,

The difficulty here is that you're basically looking for a way to limit the scope of a global variable. What if you converted your functional global variable from a single value, to an array? You could then index based on what test instance you're working on. Essentially you'd still be talking to the same global variable, but you'd have uniqueness in the index of the array. How does that sound? 😄

[glennjammin]

Here is an example of the solution:

Functional Global:

[Flamboyant]

I think you missed the attachment

[glennjammin]

Here they are

Funtional Global VI:

Reentrant VI