BUG in LabVIEW 6.0.i (Array Subset)

[wiebe@CARYA]

Hi,

There's a bug in LabVIEW 6.0.i!

To make this bug visible, follow the next steps:

1 Create a 2D array constand of integers (I used I32, but it doesn't
matter).
2 Fill it with some values (e.g. 20X20 values).
3 Use Array Subset to pick the first index and length 4 (e.g. Array index=0,
Length=4,Array index=0, Length=4).

If you create an indicator, you'll get a 4X4 2D array.

4 Create another 2D array of dubbles. Fill it 3X3.
5 Multiply the result (the dubbles on the bottom of the multiply, the
integers below).

This results in a 3X3 2D array, as expected.

6 Insert a convert to dubble between the integer array and the Array Subset.

This still works fine.

7 Place a case structure around the integer array. It doesn
't matter if the
convert is in or out of the case.

The result is a 4X4 2D array, not a 3X3 2D array! Remove the convertion, and
it works fine. Switch the top and bottom of the multiply, and it works fine.
Remove the case, works fine...


Is this a bug, or what? It can produce some really unexpected results, and
it has in our case...

Wiebe Walstra.

--
AIR technical Automation
www.air.nl

[ej]

I see what you are talking about. Looks like a bug to me, too. Also
if you place the Array Subset in a case statement instead of around the
interger array and set it to the opposite case your final array created
has the number of elements as your interger array.

The only work around that seems successful is to place the convert
function *after* the Array Subset function.

eric

In article <972653638.6885.0.pluto.d4ee054f@news.demon.nl>,
"AIR Tech. Autom." wrote:
> Hi,
>
> There's a bug in LabVIEW 6.0.i!
>
> To make this bug visible, follow the next steps:
>
> 1 Create a 2D array constand of integers (I used I32, but it doesn't
> matter).
> 2 Fill it with some values (e.g. 20X20 values).
> 3 Use Array Subset to pick the first index and length 4 (e.g. Array
ind
ex=0,
> Length=4,Array index=0, Length=4).
>
> If you create an indicator, you'll get a 4X4 2D array.
>
> 4 Create another 2D array of dubbles. Fill it 3X3.
> 5 Multiply the result (the dubbles on the bottom of the multiply, the
> integers below).
>
> This results in a 3X3 2D array, as expected.
>
> 6 Insert a convert to dubble between the integer array and the Array
Subset.
>
> This still works fine.
>
> 7 Place a case structure around the integer array. It doesn't matter
if the
> convert is in or out of the case.
>
> The result is a 4X4 2D array, not a 3X3 2D array! Remove the
convertion, and
> it works fine. Switch the top and bottom of the multiply, and it
works fine.
> Remove the case, works fine...
>
> Is this a bug, or what? It can produce some really unexpected
results, and
> it has in our case...
>
> Wiebe Walstra.
>
> --
> AIR technical Automation
> www.air.nl
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.

[greenman_11_11@my-deja.com]

Yep, looks like a bug!


In article <972653638.6885.0.pluto.d4ee054f@news.demon.nl>,
"AIR Tech. Autom." wrote:
> Hi,
>
> There's a bug in LabVIEW 6.0.i!
>
> To make this bug visible, follow the next steps:
>
> 1 Create a 2D array constand of integers (I used I32, but it doesn't
> matter).
> 2 Fill it with some values (e.g. 20X20 values).
> 3 Use Array Subset to pick the first index and length 4 (e.g. Array
index=0,
> Length=4,Array index=0, Length=4).
>
> If you create an indicator, you'll get a 4X4 2D array.
>
> 4 Create another 2D array of dubbles. Fill it 3X3.
> 5 Multiply the result (the dubbles on the bottom of the multiply, the
> integers below).
>
> This results in a 3X3 2D array, as expected.
>
> 6 Insert a convert to dubble be
tween the integer array and the Array
Subset.
>
> This still works fine.
>
> 7 Place a case structure around the integer array. It doesn't matter
if the
> convert is in or out of the case.
>
> The result is a 4X4 2D array, not a 3X3 2D array! Remove the
convertion, and
> it works fine. Switch the top and bottom of the multiply, and it
works fine.
> Remove the case, works fine...
>
> Is this a bug, or what? It can produce some really unexpected
results, and
> it has in our case...
>
> Wiebe Walstra.
>
> --
> AIR technical Automation
> www.air.nl
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.