LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Populating Array

Try something like this.

 

Build Array.png

 

Testing for exact equality on doubles can fail since each value may be represented slightly different but be very, very, very close to each other.

 

Also, I am not sure if the above logic is exactly what you are looking for but the concepts I illustrated apply your questions.



Mark Yedinak
Certified LabVIEW Architect
LabVIEW Champion

"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot
Message 11 of 14
(464 Views)

Hi Mark,

Thanks a lot for the illustration. I was wondering what you did for the false case. 

0 Kudos
Message 12 of 14
(440 Views)

For the false case I would want to skip over it and not change the output array. Like break and jump to the next index. 
But if I just leave the false case empty and the tunnel unwired, I would get the broken run arrow unless I choose to use default if unwired.
Just wondering how I could wire up the false case to skip to the next index in the for loop. 

0 Kudos
Message 13 of 14
(433 Views)

@Ghoster wrote:

For the false case I would want to skip over it and not change the output array. Like break and jump to the next index. 
But if I just leave the false case empty and the tunnel unwired, I would get the broken run arrow unless I choose to use default if unwired.
Just wondering how I could wire up the false case to skip to the next index in the for loop. 


If you are using Mark's setup, just pass the array straight through (input tunnel to output tunnel).  That way, you keep the value the same and keep it in the shift register.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 14 of 14
(427 Views)