02-06-2019 11:22 AM - edited 02-06-2019 11:23 AM
If the programming technique is to add more and more code (and never delete anything) until the output is as expected, we would get something like that:
(Six scalar booleans to six arrays with one element each to six dynamic data wires, joined into one dynamic data wire and transformed back to a boolean array with six elements. 🐵
03-18-2019 12:53 PM - edited 03-18-2019 01:15 PM
A circuitous odyssey from "array of DBL" to "array of strings" via one long string and some meaningless second format statement:
Could be replaced by a single primitive. 😄
04-09-2019 12:11 AM - edited 04-09-2019 12:12 AM
Worse than the classic bundle cluster to array dance because it is an index array, to bundle cluster, back to array Cha-Cha.
Also, just before this some extra code to take any incoming waveform array and delete is all, so that you can be sure to append new arrays to an empty array.
04-17-2019 01:08 PM
If two functions are near each other (GCD here), it is likely that they can be combined into a single instance. Always worth looking for that possibility:
04-17-2019 01:58 PM
Having a boolean labeled "Start Stop" and some loop termination depending on it set to "stop if true", some set to "continue if true" and some having a "not function" in the wire right before the condition certainly does not result in code that can easily be understood.
05-27-2019 09:28 AM
One might argue that the VI is perfectly fine, no broken run arrow, no race condition, no excessively complicated code, but for lack of a better place I'll discuss it here anyway. 😧
Quote: It's an assignment for my final project, so I am not allowed to share the VI. Hope someone can help anyway."
... and thus I am attaching a completely empty VI and even name it "empty.vi"! 😮
Not sure how much additional information we can glean from it, though... 😄
06-19-2019 05:46 PM
Quite a roundabout way to connect a boolean to a case. Seen here:
/Y
06-20-2019 10:42 PM
@Yamaeda wrote:
Quite a roundabout way to connect a boolean to a case. Seen here:
/Y
It's an If Than else! The construct was once proposed as a new structure years ago... that got shot down. It does not happily work in a dataflow paradigm...... unless you have a vim
08-14-2019 12:52 PM - edited 08-14-2019 02:10 PM
With the belief that the more code you add, the more correct it gets, her's how that'll turn out:
08-15-2019 12:03 PM
If you really want to avoid as many wires and shift registers as you can, a few value property nodes and sequence frames might fit your need. Ouch! (seen here)