LabVIEW Idea Exchange

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

Move Stacked Sequences from the Palette

Status: Completed

Implemented in LabVIEW 2014

There has been a lot of discussion on this but no LabVIEW Idea (that I was able to find). Please move the Stacked Sequences from the Programming Palette to a "retro" or "classic" palette. This is dissuade novices from overusing them

 


Previous wording:

 

There has been a lot of discussion on this but no LabVIEW Idea (that I was able to find).

Retain them for legacy code but please remove them from the Programming Palette

 

Lets vote this in and get rid of Stacked Sequences forever.

I would go so far as to release a patch to remove them from all Installed LabVIEW Versions!

Message Edited by Laura F. on 09-30-2009 03:49 PM
Visualize the Solution

CLA

LabVIEW, LabVIEW FPGA
26 Comments
JÞB
Knight of NI

Just because the subject comes up now and then to not just Move but REMOVE the SSS I took the time to put a test bench together (Source LabVIEW 2013 (13.0f2 x32) on a dual core Win 7 x64 OS.

 

SSSBench.png

 

For those that want to play, thats a snipette created with the CCT.  The Boolean "Fail" indicates the test cases do not yield equivalent data.  If you light that baby up you did something wrong!

 

As suspected, none of the test cases have performance that matches the SSS with Sequence Locals.  A Small surprise: The 1 additional unneeded tunnel the direct SSS-FSS replacement adds (presumably, to maintain the paradigm against possibly executing code parallel to a single frame of a SSS) does have a measurable performance impact of @%2 on my system.  I had expected any performance impact would be in the dirt.

 

So,  Kudos to move the SSS to prevent abuse.  But, lets stop beating up on this hard working node that gets the job done like nothing else!


"Should be" isn't "Is" -Jay
altenbach
Knight of NI

Whatever you have attached above does not appear to be a snippet. Maybe you should start a new thread in the LabVIEW forum for discussing performance issues and attach it there once more.

 

If there are performance differences, it just means that the compiler needs to get smarter. 😄

JÞB
Knight of NI

For once I'm a bit ahead of you ChristianSmiley Very Happy

Check the u-nuggets thread

 

Do we really need to engage R&D's time to write an optomization for spaghetti code?


"Should be" isn't "Is" -Jay
G-Money
NI Employee (retired)
Status changed to: In Development
 
Darren
Proven Zealot
Status changed to: In Beta
 
Darren
Proven Zealot
Status changed to: Completed

Implemented in LabVIEW 2014