BreakPoint
Rube Goldberg Code
@AeroSoul wrote:
I am pleased to learn new stuff, but these kind of solutions seem so obvious in hindsight that it makes me feel dumb not to have though of them beforehand😄
This just comes with time and experience. Altenbach is a master a math stuff (among other things) so he knows the places that math, and imaginary numbers work well. Which is why I'm always impressed with him using nodes I've never once used in my 18 years of LabVIEW, to accomplish something. If you ever do something that you think can be improved, post it on the forums. I've done this a few times and gotten multiple alternative ways to do the same thing, picking the one that works the best. I won't do this for every function I write, but I'll do some benchmarks and see what works well.
@VinnyAstro wrote:
@AeroSoul wrote:I have a folder with saved VIs with elegant solutions from this forum, which i may or may not need in the future 😄
Would you care sharing that folder? I'm very curious and interested 🙂
To get the full learning experience, start reading here, and stop when you're here.
Search LabVIEW like a graph! 
@altenbach wrote:
On a side note, the shift register initialization (top) is actually incorrect unless we really (really!?) want to start with an extra point at (0,0) that has nothing to do with any measurement
If we want that extra point, the complex array constant (bottom) could contain an single element of 0+0i and we would resize the container to show two elements to indicate that fact!
@altenbach wrote:
To send 135 bytes to an instrument. Here's what somebody came up with. I doubt it could be made simpler... or could it? 😄
The compiler *should* constant fold that into a constant. Though, that doesn't help the person who has to read that code.
