The updated code keeps track of the reward in frames/cycles instead of time and is accurate for reward intervals that are a multiple of 1/fps, but works for all intervals. For example, if fps is 120Hz, you can accurately use reward intervals that are a multiple of .025s.
The updated code keeps track of the reward in frames/cycles instead of time and is accurate for reward intervals that are a multiple of 1/fps, but works for all intervals. For example, if fps is 120Hz, you can accurately use reward intervals that are a multiple of .025s.