For loop iteration parallelism

[lucian.grec]

Am I wrong to expect numeric to be 0 when autoindexing an empty array? turns out enabling iteration parallelism outputs a 1 instead.

[GerdW]

Hi Lucian,

this effect seems to be connected with your "last value" output tunnel.

Outputting a default array seems to work correctly… (tested with LV2021)

[MECSO]

yes, I would also expect that.

But personally I don't trust this. If it is possible that there is an empty array at a for loop with auto indexing, I always place the for loop it inside a case structure and wire the selector to the output of array size function, so I can exclude arrays with size 0 and set default values manually.

[santo_13]

Interesting, never noticed this as I always implement a array size-based case structure to execute the content without the for loop in the case of size = 1 for high optimization.

It looks like for loop with iteration parallelism always runs once when auto-iteration enabled.

[crossrulz]

It only happens with "Last Value" tunnels. Auto-indexing are empty as they should.

[crossrulz]

From the LabVIEW Discord: Darren has filed this as Bug 3432120.

[altenbach]

"Lasts value" tunnels would confuse me in a parallel FOR loop, because execution order of iterations is random and there is no predictable "last" in a chronological sense. Of course it is probably defined as the output from iteration N, and maybe the authors made an OBOE. 😄