camu.select / select issue

[christophertrapani]

Hi all — as you might've seen in my long message on the IRCAM Forum I'm delving into selection.

I'm noticing the following with mubu.knn and wonder if it is a bug or intended.

new patch loaded, 3 columns sent, followed by select message with 3 values then "gettarget": first time, the results look as intended

second time, three new column values are sent, but camu.select (or mubu.knn?) retains the initial three values.

Is this expected behavior? Is there a clear command I should insert? Patch below; Thanks

———

----------begin_max5_patcher----------
468.3ocyUssahCCD84juhQ9sUJMJ14Rg9qTUsxDrnoahcjuzkUU8eu1iCpkR
nPEUnUHFzLdBGeN9LNujlPVo1JLD3N3dHI4kzjDrTnPxTdBYfussmav1HCBi
guQPxhqYEasX8BXuO6VejaaerSt42ZQqMhSSdQFzPCwE0gHikW.OL8.R2Pmr
WXQzXSE6ViXnV8zMzZx6cpb1csRmpFKY+2nHhFg.ODV40zzPH6LoYqZXPHsG
PSV9u9BpUtXIRHLThwhiwM5LbqbdtU7CR.5WRfkW19m8ys++jOat8ZUdcFPK
qhdnlusUp4p3jN1.Sqp2MHMPMz.2lAFQumYPQNq1GBeoYvFO9bsOdFdtnLTw
91xvs+WHCTfAkWfLr7BUAVY0UQGjh+5g6.YXvsxk+GoD7q2pziNCrVXZ0mjw
wKRo0m3lz4lVmmuUGiu8cF+AvQ9cOs.2B95xO+pEjEg56KPFkS2tClIKI7NQ
7BgsSxscJ4G5gF6Y1ifyEG7P+pfT30VWGf7+Gkm.G+Ee94sCOw3iiOKzlolQ
H7l2mT5P5hLLsSFSqwTs34tc8iFGBW68oVuI0owsEYaSbvhLnVKzRWGZGSCj
yCINXH49aGF4QdfyOoul9FfV90Oj
-----------end_max5_patcher-----------

[diemoschwarz]

yes, works as intended. Only the chosen columns have non zero weights.

[christophertrapani]

But in a patch where columnas and weights are being set independently, if I change weights to > 0., I can have a "phantom" target value that I cannot control or systematically clear, which (when often changing weights and columns) can be problematic.

…

On Fri, May 5, 2023 at 2:25 PM diemo ***@***.***> wrote: yes, works as intended. Only the chosen columns have non zero weights. — Reply to this email directly, view it on GitHub <#88 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIRYDC7MK6L4SXB4XSO3N4LXETWTDANCNFSM6AAAAAAXVYBEUU> . You are receiving this because you authored the thread.Message ID: ***@***.***>