feat: Add Puara TouchArrayGestureDetector processor

[yrevash]

Implements an Avendish wrapper for puara_gestures::TouchArrayGestureDetector.

• Takes a std::vector representing touch strip states as input.
• Outputs total/top/middle/bottom touch averages, and total brush/rub intensities.
• Internal puara-gestures parameters (maxBlobs, touchSizeEdge, leaky integrator settings) currently use library defaults.
• Includes CMake integration.

Note: A safety check for empty input arrays is included in the wrapper. Discussion point: whether the underlying library is robust enough to handle this, potentially simplifying the wrapper.

[yrevash]

Hi @jcelerier and @edumeneses
I've added an initial implementation for the TouchArrayGestureDetector.

Current Implementation:

• It takes a std::vector as the 'Touch Array' input.

• It outputs totalTouchAverage, topTouchAverage, middleTouchAverage, bottomTouchAverage, totalBrush, and totalRub as floats.

• The template parameters maxNumBlobs and touchSizeEdge for the underlying puara_gestures::TouchArrayGestureDetector are currently fixed at compile-time in the wrapper (to TAGD_MAX_BLOBS = 3 and TAGD_TOUCH_SIZE_EDGE = 2).

• The leaky integrator parameters within the internal Brush and Rub objects currently use their defaults from the puara-gestures library, as there isn't an easy way to configure them externally without modifying puara-gestures/brushRub.h. I've added placeholder input ports for these in the .hpp if we decide to pursue making them configurable.

Testing:
I've been using the Arraygen node in SCORE to generate test arrays, which works well for static inputs. Simulating continuous movement for brush/rub requires manually changing Arraygen's expression for now.

Please let me know your thoughts on this initial version and any further changes or expansions you'd like to see

[jcelerier]

Code looks good! @edumeneses what do you think? I'd be curious to see an example of how one would use it in practice, do we have a device we can try it with?

Otherwise sensors2osc also supports multitouch

[edumeneses]

This is a descriptor particular to touch arrays, e.g., the T-Stick or devices using the Trill touch sensors. I'm not sure it's really generalizable, but it could be interesting to explore possibilities with normalized arrays

[jcelerier]

I see, so yeah Sensors2OSC should allow to try it :)

[yrevash]

Hey @jcelerier, let me know of any changes, or if we should move with a merge.

[jcelerier]

I'd mark this as const auto& instead

[yrevash]

Hey @jcelerier ,

"Regarding the const auto& suggestion for current_touch_array_data (renamed to touch_data):

When I applied const auto&, touch_data.data() returns a const int*. However, the TouchArrayGestureDetector::update function is defined as

void update(int* touchArray, int touchSize)

The compiler threw an error: Cannot initialise a parameter of type 'int *' with an rvalue of type 'const value_type *' (aka 'const int *').

This is C++'s const-correctness preventing me from passing const data to a function that could potentially modify it (because it expects a non-const int*).

Therefore, the most const-correct solution would be to update the TouchArrayGestureDetector::update signature in puara/descriptors/touchArrayGestureDetector.h to:

void update(const int* touchArray, int touchSize);

Should I proceed with this change and commit? Or should I keep the default implementation as it is.

[yrevash]

Hey @jcelerier,

As I mentioned, I think modifying ToughArrayGestures.h is a valid option as TouchArrayGestureDetector::update function does not modify the touchArray data it receives. It only reads from it (via arrayAverage and blobDetector.detect1D).

Thus, it would be a good choice to change the call from

--> void update(int* touchArray, int touchSize)

to this

--> void update(const int* touchArray, int touchSize);

[jcelerier]

ideally we'd use std::span

[jcelerier]

not really necessary - you could rename the array "touch" and then do "touch.size()" throughout, it's not going to have any performance impact due to inlining

[yrevash]

Hey @jcelerier, Requested Review, much more importantly, the part

When I applied const auto&, touch_data.data() returns a const int*. However, the TouchArrayGestureDetector::update function is defined as

void update(int touchArray, int touchSize)*

**The compiler threw an error: Cannot initialise a parameter of type 'int ' with an rvalue of type 'const value_type ' (aka 'const int ').
This is C++'s const-correctness preventing me from passing const data to a function that could potentially modify it (because it expects a non-const int).

Therefore, the most correct solution would be to update the TouchArrayGestureDetector::update signature in puara/descriptors/touchArrayGestureDetector.h to:

_void update(const int touchArray, int touchSize);_*