-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Weird lateral ramp logger plot? #4
Comments
This plot exposes a limitation of the robot model. The additional friction dynamics when strafing cannot be captured by a single multiplier but require an additional offset at least. On the bright side, this was just as broken in previous versions of Road Runner, and feedback can make up some of the difference. |
In this case, is it better to use the regression line similar to what's shown in the screenshot or to exclude the flat portion at the beginning? |
Theoretically you should remove the flat portion, though I don't expect it to make a big difference in the overall fit because the line must still pass through the origin. |
I think we're wrapping too much into lateralInPerTick. The name suggests that it is a direct ratio between the inches and ticks of the encoder (either deadwheels or drive encoders). However, that's not how it's being used here and that makes the code significantly less readable. Instead I suggest we use lateralInPerTick in the way the name suggests (defaulting to inPerTick when using deadwheels), and 2 new variables that are tuned by lateralRampLogger, lateralKs, and lateralKv. Thoughts? |
Robot Setup: Mecanum Drive with Three Deadwheeel Localizer
Beacuse of the difference between (kS_forward, kV_forward) and (kS_lateral, kV_lateral), the ramp logger regression plot is not ideal. Any suggestion on that?
The text was updated successfully, but these errors were encountered: