RotaryEncoder only ever sending out 2 threshold events

foxg

I'm working off of a linear treadmill protocol. Anything we've done previously has only needed 2 threshold events, but now I need 4. From what I can tell this should work fine, but I'm getting 2 events and never reaching the third no matter what I do.
I set up my thresholds (lets say [10 20 40 60] arbitrarily, but I've checked they are values that should exist before the lap resets) and added them to the "thresholds" field, and I look for events "RotaryEncoder1_1", "RotaryEncoder1_2", "RotaryEncoder1_3", "RotaryEncoder1_4" to initiate different states. Events "RotaryEncoder1_1" and "RotaryEncoder1_2" trigger as predicted, but then we get stuck in the state that waits for "RotaryEncoder1_3".
I know it's not an issue of crossing the threshold while still in a previous state as I'm manually moving the treadmill quite slowly, and I can see the state transitions occur before I reach where "RotaryEncoder1_3" should be.
Is there anywhere I could be missing changing a 2 to a 4 or something else I should be considering?

Josh

Hello Foxg,

Can you please share the part of your code where you set up the thresholds?
For context, it would also be helpful to have the full protocol file(s). Please send to support@sanworks.io

Thanks,
Josh

foxg

Josh Hi Josh,
Sending the full code to the email, but relevant segments here:

numLocations = 4;
R = RotaryEncoderModule(BpodSystem.ModuleUSB.RotaryEncoder1);
(then proceed to set up rotary encoder)

for i=1:numLocations
locations{1,i} = strcat('RotaryEncoder1_', num2str(i));
end

fixedCue = locations(1); %this is just for clarity
locationStart = locations(2);
locationEnd = locations(3);
randCue = locations(4);

RewardLocationStart = S.GUI.RewardLocation;
RewardLocationEnd = RewardLocationStart + 20;
locationFixed = RewardLocationStart - 10;
locationRand = randi([RewardLocationEnd + 10, 180]); %belt is 186 cm long, should not be issue

Thresholds = round([locationFixed RewardLocationStart RewardLocationEnd locationRand]*Dist2Deg); %where dist2deg is conversion between cms and degrees

R.thresholds = Thresholds;

Then accessing them in the states as so

sma = AddState(sma, 'Name', 'WaitforFixedCue',...
'Timer', 0,...
'StateChangeConditions', {fixedCue, 'FixedCue'},...
'OutputActions', {});

Josh

Hello Foxg,

When you add thresholds beyond the default 2 using R.thresholds = Thresholds, the new thresholds are initially disabled. You have to manually enable them using R.enableThresholds, or using the 'E' command.

In your protocol, you do use the 'E' command (see io.reset), but it first occurs in the final state, so thresholds 3 and 4 are still disabled when the first trial begins.

I hope this helps,
Josh

foxg

Josh Thank you, that was exactly it!