Comparator actor behaviour ?

[nZo]

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 ...

[danshorten]

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.

AB

CB

CD

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

[danshorten]

SS of above

[DusX]

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.)

[danshorten]

@DusX

Nice!

[DusX]

@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.

[nick]

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.

[nick]

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

[DusX]

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.

[nick]

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

[DusX]

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.

[nZo]

@ 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

[mark]

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