what can cause something to cook 27 times per frame???

I have a network (whose channels originate from a touch pipe in) that is cooked 27 times per frame. I can see this happening even if I just step frame forward by one frame (and it comes up in the perf mon)

what can cause something (including the touch in) to cook 27 frames in one frame?

I would think some infinite recursion maybe ? (the originating pipe only cooks once per frame btw) but why would infinite recursion affect a pipe in (I know for sure that anything possibly using those channels uses them from later on in the network.

please help!
thanks,
dani

One more note - this is the way I can get it to cook once per frame (but still losing time on implementing this trick, although it overall is less than the time I lose cooking 27 times):

to simplify, let’s say I have

TOUCHIN->NULL->SELECT->OTHERS

I know that nothing else in touch uses the channels before SELECT.

I have then a text DAT set on CHOP change monitoring the value changes of NULL, and it contains:
opset -l 0 SELECT
opset -l 1 SELECT

this makes the entire network cook once instead of 27 times.

this is nuts… now in another process I found a chop cooking 4 times (and taking a long time each - it’s an Out chop so I’m not sure why it would take that long)

d