PR #48 Autos testing (autos to develop) #48
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
chainlynx/2024_Season!48
Loading…
Reference in a new issue
No description provided.
Delete branch "autos"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Trello: https://trello.com/c/l6zWx5QX/115-pr-48-autos-testing-autos-to-develop
@ -0,0 +1,38 @@package frc.robot.commands;This println should be removed once testing is done.
This switch case could be a bit more efficient, such as declaring a
desiredAnglevariable at the top, then assigning it within the switch case, and afterwards callingm_shooter.setAngle(desiredAngle);This debug println should be removed.
Duplicate variable declaration (Although I already commented this on another branch)
This is a duplicate of the already existing
stop()methodShould this be in RobotConstants?
Why are these here, and what are they communicating? Should these static fractions be in RobotConstants and/or used elsewhere in the code?
Everybody has their repo saved in a different place, and please use the newer java.nio.file.Path API for relative file access, but note this will not work if the code is packaged like a jar.
There has got to be a better way of doing this, pathplanner already uses Jackson to parse their json and I highly recommend you do that as well.
This entire class will never work at runtime, and seems very unneeded.
If the starting pose is required, there seems to be an already existing method in pathplanner that allows you to do this.
this was fixed in another branch
it is in another branch
If only that method was easy to find in the API...
I'll move back to robot container. It was initially moved to drivetrain to set an initial pose for the auto but that's done internally within path planner.
use swerve drive kinematics to update every time method is called and don't rely on periodic not being overrun
uses local kinematics object now
Hmm why make another kinematics object?
I recommend putting this into an array and using that instead with a for loop as it'll be cleaner.
Advise renaming this for clarity
View command line instructions
Manual merge helper
Use this merge commit message when completing the merge manually.
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.