Skip to content
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

12/14 testing plan #38

Open
phlogiston1 opened this issue Dec 11, 2023 · 1 comment
Open

12/14 testing plan #38

phlogiston1 opened this issue Dec 11, 2023 · 1 comment
Assignees
Labels
needs-robot can only be done with robot access
Milestone

Comments

@phlogiston1
Copy link
Contributor

SET UP FIELD AREA FOR TESTING:

  1. 3 planar apriltags under blackboards
  2. tape mark at 0,0, and other misc. points on the field
  3. zone in midfield for pathplanner avoidance, marked w tape
  4. robot waypoint boxes for test paths

THINGS TO TEST/MAKE IN CODE

  1. limelight odometry & telemetry
    1. setup offsets in limelight
    2. Code to find apriltag positions from known field points (will make issue for this)
    3. Rough stdevs for estimation
    4. Debug vision issues and get LL telemetry working
  2. Improve wheel odometry w more accurate wheel radius fudging (will make issue to make code for this)
  3. 3d odometry (maybe - not priority)
  4. Retune if weight added
    1. tune angle pids
    2. tune linear pids
    3. retune drive mode constants - mainly rate limiters and position correction iters
@phlogiston1 phlogiston1 self-assigned this Dec 11, 2023
@phlogiston1 phlogiston1 added the needs-robot can only be done with robot access label Dec 11, 2023
@phlogiston1 phlogiston1 added this to the Release milestone Dec 11, 2023
@phlogiston1
Copy link
Contributor Author

didn't happen, moving to whenever we meet next

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-robot can only be done with robot access
Projects
None yet
Development

No branches or pull requests

1 participant