Rube Goldberg Code

[BowenM]

I was debugging drivers, and I ran across an icon I didn't quite recognize:

Quickly realized it was actually this:

Found here

[crossrulz]

---

@BowenM wrote:

I was debugging drivers, and I ran across an icon I didn't quite recognize:

Quickly realized it was actually this:

Found here

---

That is from the conversion from the old Merge Errors VI and the new Merge Errors primitive.  I've seen it plenty of times.

[billko]

---

@crossrulz wrote:

---

@BowenM wrote:

I was debugging drivers, and I ran across an icon I didn't quite recognize:

Quickly realized it was actually this:

Found here

---

That is from the conversion from the old Merge Errors VI and the new Merge Errors primitive.  I've seen it plenty of times.

---

So THAT's what that monstrosity is!  Yes, I've seen that in drivers, too.  I never made the connection about the conversion before, probably because no one on our dev team ever used it.  (Except for me; I make extensive use of it.  It's a great way to control dataflow.)

[Kyle97330]

We've all seen rampant abuse of the "Bytes at port" node for Serial communications, but this has to be the most complicated workaround for its problems that I have ever seen:

[Yamaeda]

---

@Kyle97330 wrote:

We've all seen rampant abuse of the "Bytes at port" node for Serial communications, but this has to be the most complicated workaround for its problems that I have ever seen:

---

😲

[altenbach]

So we need to generate an I32 integer that is 2^23.

(seen here)

Some think this needs to be done using higher math using DBL, introducing 3 (!!!) coercion dots. Others think more in binary. 😄 (And the real nerds would probably use logical shift just to obfuscate again)

[crossrulz]

---

@altenbach wrote:

So we need to generate an I32 integer that is 2^23.

(seen here)

Some think this needs to be done using higher math using DBL, introducing 3 (!!!) coercion dots. Others think more in binary. 😄 (And the real nerds would probably use logical shift just to obfuscate again)

---

With constant folding, it probably comes out the same anyways...

And I prefer "geek", as I am one of those who see bunches of bits to be shifted around.

[altenbach]

---

@crossrulz wrote:
And I prefer "geek", as I am one of those who see bunches of bits to be shifted around.

---

Be careful there, they are not the same! The scale by power of two is an arithmetic shift, not a logical shift. The result differs when dealing with negative lower inputs..

[VinnyAstro]

I'm currently taking over an application (that was supposed to be an end product already, and just a new iteration on my part).

Almost the entire code is the definition of Rube Goldberg, I am not extremely experimented in LV, and it makes it really difficult to understand and check the necessity of certain actions.

Here are 2 pictures to illustrate the very nice use of Event structures with parrallel loops but also the consistency in the logic of the development:

This is one of the main loop (yes, One of them) I did "all" the comments, and organized everything to start trying understand what the hell was going on, but the "Buttons and Window Handling" loop is a magnificent use of Event structures. Not really Rude Goldberg, but still pretty funny.

Second one is about the consistency in the dev logic and is part of the "main.vi"

[johntrich1971]

---

@VinnyAstro wrote:

I'm currently taking over an application (that was supposed to be an end product already, and just a new iteration on my part).

Almost the entire code is the definition of Rube Goldberg, I am not extremely experimented in LV, and it makes it really difficult to understand and check the necessity of certain actions.

Here are 2 pictures to illustrate the very nice use of Event structures with parrallel loops but also the consistency in the logic of the development:

This is one of the main loop (yes, One of them) I did "all" the comments, and organized everything to start trying understand what the hell was going on, but the "Buttons and Window Handling" loop is a magnificent use of Event structures. Not really Rude Goldberg, but still pretty funny.

Second one is about the consistency in the dev logic and is part of the "main.vi"

---

The new iteration needed on this code is an entire refactoring of the code base. I'm sorry, but I'm glad this is you and not me that has inherited this code. Not even text on the icons to tell what they do, let alone nice glyphs. Local variables everywhere. Ugh, I'm getting a headache and it's not my project. Good luck.