You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 6, 2024. It is now read-only.
The thing we want to know is whether the programmer is in a 'mostly read' or a 'mostly write' mode. In the former, we should switch to reading after each write so as to minimize subsequent read latency, but that's sub-optimal if we're in the latter, as write()s will be shut out as read transitions are made.
So: idea: API enhancements to learn this? API enhancements for writing to both motors' power and then assume we're always in the former?
More thought needed.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Here are the timing measurements for switching from read to write:
http://ftcforum.usfirst.org/showthread.php?4948-EasyLegacyMotorController&p=18465&viewfull=1#post18465
The thing we want to know is whether the programmer is in a 'mostly read' or a 'mostly write' mode. In the former, we should switch to reading after each write so as to minimize subsequent read latency, but that's sub-optimal if we're in the latter, as write()s will be shut out as read transitions are made.
So: idea: API enhancements to learn this? API enhancements for writing to both motors' power and then assume we're always in the former?
More thought needed.
The text was updated successfully, but these errors were encountered: