Rube Goldberg Code

[GerdW]

Some honorable mention, seen here:

A typical case of RubeGoldberg (doing the same operation several times as we have to process an array) paired with local variable abuse…

[Ray.R]

The above is a serious abuse of Locals... 

[altenbach]

I am always getting criticized for using complex numbers when dealing with simple 2D geometries. But look at the difference! (seen here)

(No FOR loop, no formula node, no squares, no square roots, no bundle, etc...) 😄

 

[Ray.R]

That's why we always visit this thread.  🙂  Your simplified codes are amazing.  And we all love it..  (Even those who complain, they hide their true love for it).

[JÞB]

Seen Here

Note this is 1 of 3 identicle chunks of code  The CCT errored "Not Enough Memory..." !!! and Create Sub-vi died with too many terminals for the conn pane,  so I had to wash this section through a snipette (which repaced all the redundant write locals with p-noeds and control refs  so, doing the whole thing was a wash.

I'm not sure why the OP avoided an array indicator  but respected the ins and outs he established

We also are treated to a refreshingly safe way of abusing locals (they only perform a redundand write to the terminal) and the classic boolean case structure driven by a miss-selected compare function.  Index array resize must still be missing from Core I and look at all those dots dots dots everywhere some dots!  It must have taken hours to code and wire!

We won't even ask if the OP has seen the plot visibility checkbox (youl'd have to see the rest of the code to get that):smileyvery-happy:

[altenbach]

---

@JÞB wrote:

Seen Here

...

We won't even ask if the OP has seen the plot visibility checkbox (youl'd have to see the rest of the code to get that):smileyvery-happy:

---

Well, the visibility checkbox was not available in LabVIEW 8.x he's using.

What caught my eye is the sequential reading of 60 controls with a 60 frame flat sequence, one frame per terminal, forming the entire delimited string, then turning it into an array with a single element so it is accepted by "write to spreadsheet string". 😄

 

[JÞB]

---

@altenbach wrote:

---

@JÞB wrote:

Seen Here

---

Well, the visibility checkbox was not available in LabVIEW 8.x he's using.

What caught my eye is the sequential reading of 60 controls with a 60 frame flat sequence, one frame per terminal, forming the entire delimited string, the turning it into an array so it is accepted by "write to spreadsheet string". 😄

---

It is a rather "Target Rich" enviornment for an R-G hunt (Like a "what is wrong with this picture" game preserve)

[crossrulz]

---

Jeff·Þ·Bohrer wrote:It is a rather "Target Rich" enviornment for an R-G hunt (Like a "what is wrong with this picture" game preserve)

---

Sounds like a project I inherited many years ago that is being revisited.  I still use some of it to show why you should use shift registers (hint: the BD is 1/8 the size and run in 1/10 the time).

[JÞB]

Hold it---- Thats a Concatinate Strings (with every other element a tab) into a build array into write to spreadsheet

Target rich indeed!

[thoult]

The sheer effort that that would have taken in the first instance is incredible.