bug Dumb Open G Question

[ASTDan]

Hello,

Am I crazy ? I can't get this to work right. Why isn't my 0 column sorted?

Please help answer what I hope is a dumb question.

Thanks

Dan

[jdunham]

QUOTE (ASTDan @ Apr 17 2008, 03:52 PM)

Am I crazy ? I can't get this to work right. Why isn't my 0 column sorted?

It's sorting in alphabetical order, not numerical.

"0", "10", "5" is in correct alphabetical order.

Do you owe me a beer?

[ASTDan]

1 Beer :beer: as ordered. Don't drink it to fast.

Hmmmm. This complicates things. The string array I am actually using has text and numbers, but the first column will always be numeric. Is there an easy way to do this? Right now I am playing around with the pointer array that is coming out of the Sort 2D VI.

Dan

This is what I came up with quick and dirty

[Jim Kring]

QUOTE (ASTDan @ Apr 17 2008, 04:13 PM)

1 Beer :beer: as ordered. Don't drink it to fast.

Hmmmm. This complicates things. The string array I am actually using has text and numbers, but the first column will always be numeric. Is there an easy way to do this? Right now I am playing around with the pointer array that is coming out of the Sort 2D VI.

Dan

This is what I came up with quick and dirty

Hi Dan,

Your solution looks OK to me and I'm happy to see that you're using OpenG One suggestion: for the reordering operation, I would use the OpenG "Reorder Array" function, as shown below:

Download File:post-17-1208478378.vi

Cheers,

-Jim

[ASTDan]

Thanks Jim!

Just the tip I was looking for.

I am a big open G fan. I tell all my friends about it.

Have a beer on me. :beer:

Dan

[Jim Kring]

Dan,

Glad that works for you.

Thanks for spreading the OpenG love

Cheers :beer:

-Jim

[rkanders]

There is a bug in Delete Elements from 2D Array __ogtk.vi where rows are deleted when colums are selected and vice versa.

Reinis

QUOTE (Jim Kring @ Apr 18 2008, 11:34 AM)

Dan,

Glad that works for you.

Thanks for spreading the OpenG love

Cheers :beer:

-Jim

[crelf]

QUOTE (rkanders @ Apr 18 2008, 10:51 PM)

There is a bug in Delete Elements from 2D Array __ogtk.vi where rows are deleted when colums are selected and vice versa.

Please show us an example.

[Jim Kring]

QUOTE (rkanders @ Apr 18 2008, 07:51 PM)

There is a bug in Delete Elements from 2D Array __ogtk.vi where rows are deleted when colums are selected and vice versa.

Hi Reinis,

Thanks for the feedback.

Regarding the issue you mentioned, I cannot reproduce it. As crelf mentioned, it would be very helpful to include an example that demonstrates the bug and tests the actual results against your expected results. This will help us determine whether we can reproduce what you are seeing and whether what you are seeing is actually a bug.

Also, for future reference, the best place to report OpenG bugs is on the OpenG forums, here:

http://www.openg.org >> Report a Bug

Thanks,

-Jim

[rkanders]

Well, the bug is in the deleted elements array. Only first element is returned.

Reinis

QUOTE (Jim Kring @ Apr 21 2008, 01:48 PM)

Hi Reinis,

Thanks for the feedback.

Regarding the issue you mentioned, I cannot reproduce it. As crelf mentioned, it would be very helpful to include an example that demonstrates the bug and tests the actual results against your expected results. This will help us determine whether we can reproduce what you are seeing and whether what you are seeing is actually a bug.

Also, for future reference, the best place to report OpenG bugs is on the OpenG forums, here:

http://www.openg.org >> Report a Bug

Thanks,

-Jim

[LAVA 1.0 Content]

It seems that this bug is resolved by Commit #758 by Dafemac, and is covered by Unit Test #

1:

I am changing it's state to 'Closed'

Ton

[paulmw]

I don't think the bug described above concerning the "Delete Elements from 2D Array " has been fixed. It still returns the wrong deleted elements. The test case posted by Ton is a bad test case due to the nature of the bug. It does not catch the error. I've attached an example that demonstrates error.

Thanks,

Paul

http://sourceforge.n...435&atid=466832

Delete elements from 2D array.vi

Edited August 8, 2011 by paulmw

[Ton Plomp]

I agree that this bug hasn't been fixed. However I cannot put my finger on the actual bug.

Changing the number of input columns is of influence of the bug.

Ton

[paulmw]

I believe the bug is derived by the mismatch in the case structure's state and the enum value being passed to the reorder 2d array. See attached pic.

[jgcode]

I believe the bug is derived by the mismatch in the case structure's state and the enum value being passed to the reorder 2d array. See attached pic.

You can track this bug here: ID: 3390029