grid[n*(i-1)+[j][k] := (x mod n^2) + 1;

[Pollux]

Hello,

I'm at my job and is boring today, so I'm trying to implement the basic sudoku-generating algorithm that I found here, hoping that in the near future I will build a sudoku-solving algorithm in LabView.

I don't know how could I implement in LabView the line in the title.

Can anyone help? :worship:

[LAVA 1.0 Content]

QUOTE (Pollux @ Aug 6 2008, 03:39 AM)

Hello,

I'm at my job and is boring today, so I'm trying to implement the basic sudoku-generating algorithm that I found here, hoping that in the near future I will build a sudoku-solving algorithm in LabView.

I don't know how could I implement in LabView the line in the title.

Can anyone help? :worship:

There is something called a "Formaula Node" under "Programming->structure->FormaulaNode".u can use this implement the logic.

U can directly

QUOTE (Pollux @ Aug 6 2008, 03:39 AM)

Hello,

I'm at my job and is boring today, so I'm trying to implement the basic sudoku-generating algorithm that I found

here

, hoping that in the near future I will build a sudoku-solving algorithm in LabView.

I don't know how could I implement in LabView the line in the title.

Can anyone help? :worship:

There is something called a "Formula Node" under "Programming->structure->FormulaNode".u can use this implement the logic.

U can directly use it....

[Pollux]

QUOTE (guruthilak@yahoo.com @ Aug 6 2008, 01:47 PM)

There is something called a "Formaula Node" under "Programming->structure->FormaulaNode".u can use this implement the logic.

U can directly

There is something called a "Formula Node" under "Programming->structure->FormulaNode".u can use this implement the logic.

U can directly use it....

Of course I knew that, but Chuck Norris dislikes Formula Nodes and I don't want to mess around with him.

I found my way around. :thumbup:

http://lavag.org/old_files/monthly_08_2008/post-10966-1218025612.jpg' target="_blank">

[Neville D]

QUOTE (Pollux @ Aug 6 2008, 05:27 AM)

http://lavag.org/old_files/monthly_08_2008/post-10966-1218025612.jpg' target="_blank">

Reading and writing to arrays as local variable copies will affect performance, readability and introduce race condition bugs.

Use shift registers or stretch the wires out..

Neville.

[Pollux]

QUOTE (Neville D @ Aug 6 2008, 07:20 PM)

Reading and writing to arrays as local variable copies will affect performance, readability and introduce race condition bugs.

Use shift registers or stretch the wires out..

Neville.

Thank you for the advice.

Actualy I use this type of assignement in bigger projects.

This type of assignement is this to be avoided only for the arrays, or is the same thing for scalar type variables?

That's way I like small examples like this. I get all kind of tips.

[Neville D]

QUOTE (Pollux @ Aug 6 2008, 11:57 AM)

This type of assignement is this to be avoided only for the arrays, or is the same thing for scalar type variables?

That's way I like small examples like this. I get all kind of tips.

Using it for Arrays will affect performance, since every local variable of an array will make a separate copy of the array. Also, reading and writing locals switches to the user interface thread.

Scalar variables might still cause race conditions when a write might accidentally trample a read operation.

Overall: use wires where you can. Its easier to read, will give best performance, and not cause race conditions.

Locals are OK, if for example you are reading vals from an ini file and initializing a bunch of controls on the front panel once. If doing anything in a loop, avoid them.

Also don't try to get around that by reading or writing to the "value" property of a control or indicator. That is even slower than using locals. Again a "one off" use is fine.

Neville.

Neville.