Comparator actor behaviour ?

Reply to Comparator actor behaviour ? on Mon, 06 Apr 2015 20:43:09 GMT

mark — Mon, 06 Apr 2015 20:43:09 GMT

Dear All,

Well, it seems pretty clear that I need to address this in the actual Comparator actor. The behavior isn't intuitive in the case cited here.

Best,

Mark

Reply to Comparator actor behaviour ? on Sat, 17 Jan 1970 12:44:32 GMT

nZo — Sat, 17 Jan 1970 12:44:32 GMT

@ dusX : I don't know yet how to use javascript but you're caught my attention. I puts me as possible !
@ nick : I return integrate your solution in my rectangle generator and I post the patch right here very soon
@ danshorten : your patch are true but not very stable on result for me . i just keeping searching.

A big thanks to all for your help and your efficiency.

nZo

Reply to Comparator actor behaviour ? on Sun, 05 Apr 2015 20:39:13 GMT

DusX — Sun, 05 Apr 2015 20:39:13 GMT

Ok. Well that's really what it should do... I just hadn't noticed and thought it served the purpose. I will write a version that works.. Using the simultaneous actor to trigger the action.

Reply to Comparator actor behaviour ? on Sun, 05 Apr 2015 14:19:06 GMT

nick — Sun, 05 Apr 2015 14:19:06 GMT

Heres monitor output generated - first set of zeros created by changing value 2 to zero (1 was aready set to 0) - so just one output as only 1 input changed.

Then clicked on trigger value at top once which generates the next two sets, where the intermediate 'incorrect' value appears.

The final two sets of values (where nothing changes) are generated by changing the value of input 1 from 1 to 2

Reply to Comparator actor behaviour ? on Sun, 05 Apr 2015 13:25:37 GMT

DusX — Sun, 05 Apr 2015 13:25:37 GMT

Strange. I expected the js to behave the same. I expected to have to add some logic to require both values be new. ( or like) But I couldn't see any double outputs.

Reply to Comparator actor behaviour ? on Sun, 05 Apr 2015 12:19:37 GMT

nick — Sun, 05 Apr 2015 12:19:37 GMT

I would use this to give single trigger when both are changing 'simultaneously'. The short delay means the intermidaite value gets lost.

The value on the trigger can be adjusted to a longer delay if it is unreliable. The final comparator can be omitted if you just want the value 0 or 1 from the comparison - it is there to recreate the true false triggers.

Nick

93d8f5-simultaneouscomparator.izz

Reply to Comparator actor behaviour ? on Sun, 05 Apr 2015 11:00:00 GMT

nick — Sun, 05 Apr 2015 11:00:00 GMT

This javascript version produces the same behaviour as the comparator actor for me - sending two values from random value actors both triggered from a single actor produces the intermediate result when the first input has changed, and the final result when the second input changes.

Reply to Comparator actor behaviour ? on Sat, 04 Apr 2015 23:22:16 GMT

DusX — Sat, 04 Apr 2015 23:22:16 GMT

@Mark

I was surprised that this worked, since I believed that the Javascript would run each time a value arrives,

but in fact it seems that all values received during the cycle are used. Is this correct?

If so it makes for an easy way to trap incoming values for a synchronized process.

Reply to Comparator actor behaviour ? on Sat, 04 Apr 2015 07:49:57 GMT

danshorten — Sat, 04 Apr 2015 07:49:57 GMT

@DusX

Nice!

Reply to Comparator actor behaviour ? on Sat, 17 Jan 1970 12:43:53 GMT

DusX — Sat, 17 Jan 1970 12:43:53 GMT

A clean fix using Javascript actor.

function debug(printString)
{ if (DebugMode){ print(printString + "\n"); } }

function main() { 
DebugMode = true; 
 op = parseInt(arguments[0]); 
// op 1, lessthan 
// op 2, greaterthan 

in1 = parseFloat(arguments[1]); 
in2 = parseFloat(arguments[2]); 
debug("1= " + in1 + " 2= " + in2);
if (op === 1){ if (in1 < in2) { 
 opOut = 1; 
 debug("out1= " + opOut); 
 }else{
 opOut = 0; 
 debug("out2= " + opOut); 
 } } 
 if (op === 2){ if (in1 > in2) { 
 opOut = 1; 
 debug("out1= " + opOut); 
 }else{
 opOut = 0; debug("out2= " + opOut); 
 } } 
 outVals = [opOut] 
 debug("vals= " + outVals ); 
 return outVals; 
}

The attached file shows how I set this up. The above Javascript goes into the JavaScript actor... its basic and needs expanding, but it works. ( @Michel seems like I can't format the Javascript code anymore.. and HTML view auto extends so you can't make edits.)

Reply to Comparator actor behaviour ? on Fri, 03 Apr 2015 10:33:25 GMT

danshorten — Fri, 03 Apr 2015 10:33:25 GMT

SS of above

Reply to Comparator actor behaviour ? on Fri, 03 Apr 2015 10:32:28 GMT

danshorten — Fri, 03 Apr 2015 10:32:28 GMT

Had a flight this morning so spent 15 mins doing a quick inelegant but reliable patched solution to your problem.

The thing is you are changing the numbers in your comparator one at a time giving you 3 combinations of numbers.

Ie you start with numbers A & B and end with C & D giving you the following sequence of changes.

So of course you get a true/false outcome for each combination.

By ignoring the changes and then simply comparing the final pair you will get what I think it is you are after.

First solution that came to mind is patched and attached.

Hope it helps.

Dan

BTW: in the patch trigger delay 2a and 2b need to be longer than trigger delay 1 but don’t need to be the values I have set. (the process needs at least .2 seconds to complete though i.e. min vals of 0.2 & 0.4 – on my laptop anyway)

I have also set initialize values for the toggles and gates.

6aee35-random-comparator-solution.izz

Reply to Comparator actor behaviour ? on Sat, 17 Jan 1970 12:34:01 GMT

nZo — Sat, 17 Jan 1970 12:34:01 GMT

Thanks Mark for detailed explanation.

Actor's behavior seems logical. Process execution speed did not allow me to see what happens, look like both result.

perhaps made on a dev code a short delay before analyse theses values for case 2 values put in on same (relative) time ...

Reply to Comparator actor behaviour ? on Sun, 29 Mar 2015 15:00:37 GMT

DusX — Sun, 29 Mar 2015 15:00:37 GMT

I have been using Javascript to pack and unpack from JSON strings.

Reply to Comparator actor behaviour ? on Sun, 29 Mar 2015 14:40:09 GMT

Stephane_Morisse — Sun, 29 Mar 2015 14:40:09 GMT

Coming from Max, that was right what I imagined. So now my question is : is there an actor that can do what [pack] or [pak] objects do in Max ?

Reply to Comparator actor behaviour ? on Sun, 29 Mar 2015 14:24:32 GMT

mark — Sun, 29 Mar 2015 14:24:32 GMT

Dear nZo,

You are generating two random numbers. They come in one at a time. So imagine that the Comparator has these two values and is set to greater than (>)

Now you generate two random numbers. The first random number is 3.2 and so it arrives at value1

3.2

at this moment, the output if false (0) and the 'false' output triggers

Now the next random number comes (for value2) and it is 1.8, so now we have

3.2

1.8

and the result of the comparison is true the 'true' output triggers.

Does that help you to understand what's happening?

I can see however that this is confusing. I will file a bug report on this topic and make sure we look into it.

Best Wishes,

Mark

Reply to Comparator actor behaviour ? on Sun, 29 Mar 2015 14:06:14 GMT

nZo — Sun, 29 Mar 2015 14:06:14 GMT

sure it's a solution to have only one result but the logical result sometimes is wrong because this state change on new true / false trigger. You have a 0 and quickly a 1, it's not stable output.

exemple : put 2 value ( ie 35 and 56) to create a rectangle. I need a true when value 1 < value 2 (ie to choose rectangle horz or vert move according to shape dimension). Who use comparator actor to make this ?

Reply to Comparator actor behaviour ? on Sat, 17 Jan 1970 12:33:50 GMT

vanakaru — Sat, 17 Jan 1970 12:33:50 GMT

Out of curiosity I tried this as well. I have no idea for the purpose of this.

It seems that there are both true and false triggered sometimes. However Comparator output value will be either 1 or 0 and correct to equation(as far I can tell). - 1=true 0=false. You can use this output instead. Like add one more comparator that will compare first ones output with 0 or 1 and get true /false trigger.

Reply to Comparator actor behaviour ? on Sun, 29 Mar 2015 09:59:11 GMT

Skulpture — Sun, 29 Mar 2015 09:59:11 GMT

Isadora does process actors from top to bottom so it will have a slight delay.

Reply to Comparator actor behaviour ? on Sat, 17 Jan 1970 12:33:38 GMT

nZo — Sat, 17 Jan 1970 12:33:38 GMT

What do you say with placing actors spatially ? I don't find mark's tutorial which way is it ?

Reply to Comparator actor behaviour ? on Sun, 29 Mar 2015 07:45:50 GMT

Stephane_Morisse — Sun, 29 Mar 2015 07:45:50 GMT

Speaking of which... I think I remember a tutorial from Mark speaking about the order of operation but is there, like in Max, a way to clearly define the order by placing the actors spatially ?

Reply to Comparator actor behaviour ? on Sat, 17 Jan 1970 12:33:36 GMT

nZo — Sat, 17 Jan 1970 12:33:36 GMT

thanks so much for your help !

i m try this but generate 2 times trigger. Everytime a new value input is detect. 2 True trigger or 2 false trigger and already sometime true and false quickly (test with 0,2 second delay to 0,6)

comparator actor use a AND logical operator result .... very strange

Reply to Comparator actor behaviour ? on Sat, 28 Mar 2015 23:29:10 GMT

Skulpture — Sat, 28 Mar 2015 23:29:10 GMT

It could be that the top toggle will change milliseconds before the bottom one. And if it is greater than the second number it will trigger.

Maybe add a very short trigger delay on the second random trigger.