Rube Goldberg Code

[JÞB]

---

@altenbach wrote:

---

@JÞB wrote:
I would bet a kudos here and wherever AQ responds that , that right there is a default error ring backsaved for previous version;)   

---

Really? There is a more proper error constant in the other case structure to the right. Back-saving would have affected both. I also have never seen a default error constant where the error is TRUE.

---

Not if only 1 was backsaved. Bear in mind, there is no LabVIEW for Android viewer. But, I'll double down 2 kudos!

[JÞB]

---

@altenbach wrote:

---

@JÞB wrote:
I would bet a kudos here and wherever AQ responds that , that right there is a default error ring backsaved for previous version;)   

---

Really? There is a more proper error constant in the other case structure to the right. Back-saving would have affected both. I also have never seen a default error constant where the error is TRUE.

---

Yeah,  really 

Its nearly too obvious for the thi@ thread !

Danm shame  though  

[altenbach]

Yes, this is only the tip of the iceberg!

(more here)

[paul_cardinale]

I came across this many years ago.

It took me a long time to figure out what it does.  It takes a floating point number in the range of 0 - 100 (which represents a duty cycle) and scales it )linearly) to an integer in the range of 0 - 1200.  So it's the same as this:

[wiebe@CARYA]

---

@altenbach wrote:

Yes, this is only the tip of the iceberg!

---

The tip of the Goldberg?

[altenbach]

(seen here)

I have obviously a serious problem trying to fit data to a single exponential. I am sure you can immediately see what I am doing wrong after studying a picture of the context help; 😄

(Similar: My car does not work, please fix! Here's a picture of the glossy sales brochure!)

[GerdW]

(seen here)

[altenbach]

I am scratching my head for an hour but I still have that nagging feeling that this code fragment could be simplified.

(seen here)

[Gregory]

For something so simple I would just use an expression node 😄

[altenbach]

---

@Gregory wrote:

For something so simple I would just use an expression node 😄

---

This seems to act like the "always copy" function because it creates a new buffer allocation. Except for very rare cases, these decisions should be left to the compiler.