cancel
Showing results for 
Search instead for 
Did you mean: 
Reply

Rube Goldberg Code

Re: Rube Goldberg Code

I would say it probably never makes a real difference, but one could of course try to design some very detailed benchmarks. Seems difficult.

 

 

If the code to be timed is gigantic and contains many parallel code paths (i.e. many "clumps"), there might still be cases where the "ticker" execution gets delayed if everything is in the same frame because so many other things need to happen in parallel. I have no idea if the compiler would set certain priorities and if "high resolution relative seconds" is prioritized or not.

 

Out of habit, I probably would keep using the three-frame flat sequence, just because it neatly separates the benchmarkee from the benchmarker. Smiley Very Happy


LabVIEW Champion Do more with less code and in less time
Message 2031 of 2,038
(423 Views)

Re: Rube Goldberg Code

(Seen here)

 

To generate a list of filenames with incrementing suffix, we of course have this function (which gets expensive if the folder already contains a lot of files, different story).

 

Assuming we want to roll our own, we could do this: (guess what would happen if e.g. "# of digits" = 0 when we call/run it! Smiley Surprised)

 

Generate File Name.JPG

 

 

Or we could of course just do the following. Seems easier. Smiley Surprised

(Personally, I would even omit the +1, because ABCDEF0000000000.xls is a perfectly good file name, but that's just me Smiley Very Happy)

 

MakeFileNames.png

 


LabVIEW Champion Do more with less code and in less time
0 Kudos
Message 2032 of 2,038
(371 Views)

Re: Rube Goldberg Code

Is dynamic data really the solution for everything? Smiley Surprised

 

Some think so!

 

Of course we cannot wire a 2D array of DBL to a "Cursor.posX" property node for good reason, because there is no conceivable way this would make sense in any scenario. LabVIEW of course will break the wire.

 

To avoid the broken wire, all we need is convert the 2D array to dynamic data right? No broken wire>>> No problem! Smiley Very Happy (This is about as effective as fixing low oil pressure by putting electrical tape over the indicator light.)

 

42.png


LabVIEW Champion Do more with less code and in less time
0 Kudos
Message 2033 of 2,038
(260 Views)

Re: Rube Goldberg Code

Another one of these dynamic data monstrosities (see here)

 

rubeg.png

 

(If you are a dynamic data expert, feel free to help the guy out. I am out!)


LabVIEW Champion Do more with less code and in less time
0 Kudos
Message 2034 of 2,038
(205 Views)

Re: Rube Goldberg Code


@altenbach wrote:

 

 

(If you are a dynamic data expert, feel free to help the guy out. I am out!)


Dynamic Data is just whatever is convenient for it to be at that time right? /s

Matt J
National Instruments | CLA
0 Kudos
Message 2035 of 2,038
(201 Views)

Re: Rube Goldberg Code


@Jacobson wrote:

@altenbach

Dynamic Data is just whatever is convenient for it to be at that time right? /s


OTOH, dynamic data is always inconvenient for the programmer Smiley Very Happy


LabVIEW Champion Do more with less code and in less time
Message 2036 of 2,038
(196 Views)

Re: Rube Goldberg Code


@Jacobson wrote:

@altenbach wrote:

 

 

(If you are a dynamic data expert, feel free to help the guy out. I am out!)


Dynamic Data is just whatever is convenient for it to be at that time right? /s


That depends on what "Data" can be...in NI's definition and what that configuration wizard will supportSmiley Very Happy

0 Kudos
Message 2037 of 2,038
(180 Views)
Highlighted

Re: Rube Goldberg Code


@altenbach wrote:

@Jacobson wrote:

@altenbach

Dynamic Data is just whatever is convenient for it to be at that time right? /s


OTOH, dynamic data is always inconvenient for the programmer Smiley Very Happy


Now I finally know why it's called dynamic data. It switches from convenient to inconvenient dynamically.

 

Almost never back though Smiley Wink.

Message 2038 of 2,038
(152 Views)