Looming stim triggering issues

[rawanalsubaie]

Hi,

I am trying to set up a looming behaviour paradigm on bonsai, currently I have the workflow successfully detecting an ROI and triggering a looming stimulus. However when I press play to run it, the circle only shows up once and at a very small diameter. I think there might be an issue with the ROI boolean continueing to spit out 'true' so the animation is lagging - I have tried distinct until changed but nothing happens. I'd also like to timestamp when the stimulus comes on and off if possible. I will be merging this workflow with neurophotometrics photometry system, if you have any tips on how best to do that i would appreciate it.

Thanks so much :)

looming_try.zip

[banchan86]

Hmm @rawanalsubaie I identified several problems with the workflow, can you try fixing those first and see how far you get with it?

1. You have two duplicate "tracking" branches - one in the tracker node and the other in the the mouse detecting branch, are they tracking separate objects? Its probably best to simplify the two branches as much as possible since they share some nodes.

2. You probably want to replace the Replay node with a SelectMany, i think its closer to what you want.

3. Avoid using the Zip to tie together the looming stimulus branch and the centroid recording branch (tracker). It's probably outputting far more values than the mouse detected node and Zip is best used for equal number of elements from two sequences (it will wait for one). You probably want to save the centroid separately.

4. I am not sure what the two Booleans and Merge after DistinctUntilChanged is doing, but you should probably delete them as I think they are messing up the logic. If I read it right, the original logic should work (with the rest of the changes). DistinctUntilChanged should output either a True or False, and you have a Condition after mouse detected to trigger a looming sequence on True

[rawanalsubaie]

Hi Shawn,

Thanks for getting back to me.

I was attached a workflow with the boolean logic which I was trying to use to get over my ROI detection issue. The mouse tracker and mouse detected are separate, mouse tracker spits out an x,y coordinated for the mouse in the entire arena and the mouse detected is checking when the mouse is actually in the ROI to trigger the looming stimulus. I can't group my animation into select many the diameter property becomes red and so I can't use it. I've attached the workflow that shows my original problem if you press play, hope this makes a bit more sense?
looming_try (2).zip

thanks again

[rawanalsubaie]

Hi, I fixed it, there was actually something wrong with my stimulus/animation rather than ROI detection. Thank you!
looming_final.zip