The RangeAnimation seems to not receiving inputs from MemberSelector, instead using default value

[chiyu1203]

Dear Bonsai team,

I really hope to ask some meaningful questions. However, I have been stuck in this procedure for a while.
Therefore, any suggestions is welcome.
I want to present moving stimuli (either moving right or left) on either side of the screen (either on the left side or right side).
Hence there are 4 default conditions, left stim moving to further left, left stim moving toward right, right stim moving to further right, right stim moving toward left.
I also hope to make the stim stationary in the first 2 second (when it is present) and then start moving, so do that I use Concat method to link two DrawCircles modules (one stationary followed by moving one). To create the moving stim, I externalize the location property of DrawCircle and used RangeAnimation to control the location. I used a hacky way to deliver these parameters: sending the parameters for RangeBegin and RangeEnd with SubscribeSubject. The SubscribeSubject receives the parameters about the initial and end location of the stim from a csv file.

I thought this would work, but it turned out that it seems that RangeAnimation is not using the initial location parameter (the end location parameters was fine). Instead, it used the value in RangeAnimations MISC. Hence, what showed up in the monitor is that in half of the condition when the value in RangeAnimations MISC does not match with SubscribeSubject´s value, the stim would appear and disapear on one side of the screen (as expected, due to the first DrawCircle for stationary stim). The moving stim now appears from the other side of the screen and go all the way across the monitor to the RangeEnd´s designed End location.
Does anyone know what might cause this performance?
Below I have attached this workflow. Please feel free to let me know if you have any thought.

sweeploom.zip

Best Regards

Chi-Yu

[chiyu1203]

Hello, just an update to say that I fixed the problem. So it sounds like MemberSelector can only send one output. So what I did is instead of linking MemberSelector to multiple PropertyMappings, I created separate SubscribeSubject-MemberSelector modules for each PropertyMappings.