[x] Change my_pid_base.py to basePIDcomponent.py. my_pid_base doesn't really make sense.
[ ] scaled_output calculation is either wrong or poorly named. Comments = clarification
[ ] Setting _has_setpoint to False after each iteration of execute doesn't seem...intuitive. It would make more sense to set to false if error is within a threshold. But I understand you check how close it is in another method.
angle_controller.py
[x] I think it would be neater and easier to implement changes if is_aligned called is_aligned_to(self.setpoint)
[ ] Not so much code specifically as theory, but I wonder if there is a way to get the same values for rotating when standing still as when moving.
auto_align.py
[x] Remove end()
field_centric.py
[x] fwdX and fwdY should be swapped to make sense. cos(X) measures adjacent to, and since an angle of 0 is in the +Y direction, cos should be applied to fwdY.
global_position_controller.py
[x] delete this.
robot.py
[x] I don't think you should invert the X axis. Left is -1 and right is +1 automatically.
[x] move(x, y, rcw) should be move(y, x, rcw)
[x] When setting the gimbal and yaw, the scaling should happen in the setter to make it easier to change each setting in more than one place
my_pid_base.py
my_pid_base.py
tobasePIDcomponent.py
.my_pid_base
doesn't really make sense.scaled_output
calculation is either wrong or poorly named. Comments = clarification_has_setpoint
to False after each iteration ofexecute
doesn't seem...intuitive. It would make more sense to set to false if error is within a threshold. But I understand you check how close it is in another method.angle_controller.py
is_aligned
calledis_aligned_to(self.setpoint)
auto_align.py
end()
field_centric.py
fwdX
andfwdY
should be swapped to make sense. cos(X) measures adjacent to, and since an angle of 0 is in the +Y direction, cos should be applied tofwdY
.global_position_controller.py
robot.py
move(x, y, rcw)
should bemove(y, x, rcw)
swervemodule.py
is_aligned
Add Docstrings