DSP Robotics Support

Hi,
I've tried using the green queue primitive for a sensitive project that needs a decent accuracy but couldn't perform a full control on it. So wondered maybe Ruby can be the answer. The Ruby module should actually do a very simple task:
Receive a given array and push each of the indexes forward whenever it gets triggered. For instance, if the array is

4
5
7
9
13

It will output the integer 4 on the first trigger, then output the integer 5 on the second trigger, then 7 and so on until the array ends. Array's end should cause it stop pushing anything until a "reset" trigger received.

Any ideas?

Hey,
This does, I think, what you're asking for



No Ruby there though...

Here is a better version in Green Primitives than the first one I uploaded.

kortezzzz wrote:Hi,
I've tried using the green queue primitive for a sensitive project that needs a decent accuracy but couldn't perform a full control on it. So wondered maybe Ruby can be the answer. The Ruby module should actually do a very simple task:
Receive a given array and push each of the indexes forward whenever it gets triggered. For instance, if the array is

4
5
7
9
13

It will output the integer 4 on the first trigger, then output the integer 5 on the second trigger, then 7 and so on until the array ends. Array's end should cause it stop pushing anything until a "reset" trigger received.

Any ideas?

That's called 'fifo' and describes a buffer that holds a certain number of data and spits out the oldest first ( "First In First Out" )

Here's an example in Ruby.

Guys, Thanks you so much for the beautiful examples This is classic "straight to toolbox" must have module.
Although tula's ruby one is the most elegant solution and probably the most CPU saver, I really loved the functionality of tiffy's and tektoog's green solution. So I made another progress and added to tektoog's one's trog's ruby counter which allows up\down option. Hope you like it

Hey,
Good add
I think it can still be optimized a bit
check this one, notes are in there



Take care,
TekTooG

tektoog wrote:I think it can still be optimized a bit
check this one, notes are in there

Thanks Tektoog