Unexpected aggregate comparison behaviour when using cluster or array inputs

[Worle]

Is this a bug, feature or user incompetence? It has just caused a bug which took me a long time to find.

It appears that when using a greater than or less than comparison with cluster inputs and the comparison node set to 'compare aggregates' it only returns the result of the first element rather than doing an 'and' on all the individual element comparisons.

The equals/not equals comparisons do not have this behaviour.

Is this expected behaviour or not? I can't find anything in the help documentation detailing this.

[altenbach · Accepted solution]

I think it is documented here.

If you want a specific behavior, do a "compare elements" followed by "AND array elements" or "OR array elements" on the boolean output, depending on the desired result.

[altenbach]

On a related note, also have a look at this old post.

[mcduff]

---

@altenbach wrote:

On a related note, also have a look at this old post.

---

Besides being amazed by your ability to reduce code size to postage stamps, extremely impressed how you can recall a post from 10 years ago.

[Worle]

I suppose I am just surprised at what I consider a very unintuitive behaviour.