merge main from practise field to working. #28
No reviewers
Labels
No labels
Minor
Non-Trivial
Trivial
bug
daily
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
bug
documentation
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ironriders/ReefScape-PostSeason!28
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "main"
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?
@ -197,1 +186,3 @@*** <p>* Does this by setting the {@linkEither a comment or a better variable name would be helpful here. I know that L4 is the elevator position / coral position, but the usage of this variable is confusing. Why is it set to false in several places in the code, but then when trying to set L4 the first time does it set it to true here?
@ -197,1 +186,3 @@*** <p>* Does this by setting the {@linkIt's keeping track of if it has already moved the coral piece up I think. I agree it's not super helpful
yea i would add a comment here but dont have a functioning laptop rn. It is basically so that canceling going to L4 will not boost the coral in the intake twice, where boosting it is moving it up slightly
-------- Original Message --------
On Wednesday, 10/15/25 at 16:59 Carl Anderson @.***> wrote:
@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();All the extra indenting here makes it even more difficult to read. I'm generally in favor of 4 space indents, this went from 6 spaces to 8 spaces.
@ -197,1 +186,3 @@*** <p>* Does this by setting the {@linkFixed in #27
@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();Does the comment above even make sense now that there's an enum instead?
@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();This was a mistake any should be fixed in #27
yea i hit format at the practice field and it did that
-------- Original Message --------
On Wednesday, 10/15/25 at 17:03 Carl Anderson @.***> wrote:
@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();fixed in #27
@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();Please just put a newline after
{and align all these comments to the same amount of indent.@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();I think all the formatting weirdness should be fixed in #27
@ -58,3 +51,2 @@public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();public final TargetingCommands targetingCommands = targetingSubsystem.getCommands();public final TargetingSubsystem targetingSubsystem = new TargetingSubsystem();It probably added some of it's own, but that whole branch is for formatting fixes
@ -34,15 +32,17 @@ public class DriveConstants {public static final double ROTATION_CONTROL_EXPONENT = 3.0;public static final double ROTATION_CONTROL_DEADBAND = 0.8;Can probably remove the
TODOhere yeah?@ -34,15 +32,17 @@ public class DriveConstants {public static final double ROTATION_CONTROL_EXPONENT = 3.0;public static final double ROTATION_CONTROL_DEADBAND = 0.8;Fixed but not yet commited
@ -104,4 +109,4 @@* @param rotation Desired rotation in radians per second.* @param fieldRelative If not field relative, the robot will move relative to* its own rotation.*/Even better is if you assign the false to something that lets me know what it represents.
@ -104,4 +109,4 @@* @param rotation Desired rotation in radians per second.* @param fieldRelative If not field relative, the robot will move relative to* its own rotation.*/Even better is if you add some newlines:
@ -104,4 +109,4 @@* @param rotation Desired rotation in radians per second.* @param fieldRelative If not field relative, the robot will move relative to* its own rotation.*/Fixed in #27, to be clear I'm fixing these as you go, you're not wasting your time
Please do not merge until I say otherwise. I'm on my phone so I can't actually block it
Magic number
9I just noticed this - you should use it in the method above.
Yeah what Carl said. Just replace this with a constant and put it in drive constants
I won't approve this until the rotation inversion is fixed, but other than that it should be good to merge. The rest of my comments aside from that one were mainly nit picks and it should be fine to merge without addressing them.
Just a nit pick, but this probably should be a constant so that if this code reused the magic number 9 doesn't cause issues if their gyro isn't on CAN ID 9
@ -34,15 +32,17 @@ public class DriveConstants {public static final double ROTATION_CONTROL_EXPONENT = 3.0;public static final double ROTATION_CONTROL_DEADBAND = 0.8;Just wanted to check that the SWERVE_DRIVE_MAX_SPEED = 6 and SWERVE_MAXIMUM_ANGULAR_VELOCITY = Math.PI * 2.5 are values based on the design and limitations of the robot not random numbers based off the idea that bigger number goes faster. I don't know if would cause any issues with YAGSL, but path planner does warn that setting those values in the path planner config can cause issues.
@ -104,4 +109,4 @@* @param rotation Desired rotation in radians per second.* @param fieldRelative If not field relative, the robot will move relative to* its own rotation.*/Usually when the controls are inverted that is because the negatives signs that dictate the inversion for the translation were reversed. I don't think we want to invert the rotation with the translation because rotation should be constant no matter if the odometry gets messed up.
If rotation were to be inverted that means that the negative sign that controls the inversion of rotation in the robot container file should get swapped.
swerveDrive.drive(translation.times(invertStatus ? -1 : 1), rotation * , fieldRelative, false)
those numbers are somewhat arbitrary, but william said they would be fine
-------- Original Message --------
On Wednesday, 10/15/25 at 23:07 Ryan Elbert @.***> wrote:
william wanted the rotation to not invert and i think it is set up like that but cant check
-------- Original Message --------
On Thursday, 10/16/25 at 10:54 isabelle901 @.***> wrote:
@ -34,15 +32,17 @@ public class DriveConstants {public static final double ROTATION_CONTROL_EXPONENT = 3.0;public static final double ROTATION_CONTROL_DEADBAND = 0.8;They are somewhat arbitrary, but there isn't a good way to determine them without testing we don't have time fore
Pr ready
I really like the idea of a Debug vs. Release mindset in terms of publishing/printing. It is a common industry standard. For my own edification does the dashboard allow filtering out these debug publishes?
yea they are placed in a separate folder in the selectior. in too tried to explain better sorry
-------- Original Message --------
On Friday, 10/17/25 at 20:51 devonshire @.***> wrote:
Sorta. It's not great but it helps
Working at pits
Please convert to an issue. I don't have the energy and i want this branch ready by comp
Please convert to an issue. I don't have the energy and i want this branch ready by comp
@ -104,4 +109,4 @@* @param rotation Desired rotation in radians per second.* @param fieldRelative If not field relative, the robot will move relative to* its own rotation.*/Please convert to an issue. I don't have the energy and i want this branch ready by comp. This does look like it could affect functionality, but it was working fine I think,
Please convert to an issue. I don't have the energy and i want this branch ready by comp.