LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Large Arrays and Memory

Solved!
Go to solution
Solution
Accepted by topic author Valerie77

Valerie,

 

Here is a quick image of how to start to use the method I described above.  This would be expanded to the six shift registers you have.

 

Lynn

 

21285i97CB5CB13590CDDB

0 Kudos
Message 11 of 14
(1,254 Views)

Ok I will work with it.  Thanks for the help 🙂

0 Kudos
Message 12 of 14
(1,246 Views)

To the veterans out there...is this form more or less desirable from a memory standpoint than code with multiple cluster arrays shown above?  Seems like X data are saved fewer times in this implementation, but perhaps there is an overhead associated with the build cluster of arrays and build array of clusters operations in each loop that offset these savings.  (Oops, forget to increment the index).

21297iAFD90A156013BDC7

0 Kudos
Message 13 of 14
(1,236 Views)

@Houligan I can bet money on that the build cluster inside the loop makes a new array, thus a data copy. It must be better to work directly with the clustered arrays.

 

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 14 of 14
(1,233 Views)