Conversation
…to subsystems/intake
…to subsystems/superstructure
…to subsystems/spindexer
…to subsystems/intake
…to subsystems/superstructure
…per interface in the class
…ethod to vision for use in LEDs Previously there were flags within the LED subsystem for whether cameras were dead. I forgot to actually set the values so it didn't do anything. Now, there is a new method in Vision that checks if a camera is dead. Additionally, I noticed that the limelight+photonvision template was good but for VisionConstants the data for the camera was scattered everywhere so I consolidated it into an array of records called CameraData. This stores the camera name, camera offset to the robot, and the standard deviation factor
|
|
FEAT: Replace usage of Field2d with logging poses as outputs.
…eal hardware behavior
…into feat/consistent-sims
* REFACTOR: Initial refactor, still many changes and polish needed * REFACTOR: Make naming of settings interfaces consistent and use static import of constants file in subsystems, move tuner constants into swerve folder * REFACTOR: Implement new constants based naming and formatting convention Rename nested constants interfaces across every subsystem's constants files so every nested interface name is globally unique and prefixed with its subsystem, per the IO-refactor naming convention that I suggested. * FIX: Ensure that TalonFX motors CANBus matches the ones from the original tribecbot * REFACTOR: Change "<Subsystem>Ids" to "<Subsystem>DeviceIds" * REFACTOR: Pluralize motor configuration interfaces + TurretSoftwareLimits interface --------- Co-authored-by: aidenzhang21345 <aidenzhang211@gmail.com>
…into feat/consistent-sims
Rename Hardware Interfaces
* feat: Drive input processors, sotm, fotm, and regular drive commands * feat: add all button bindings, added additional commands to vision, leds, and drive * REFACTOR: Cleanup LED state handling - deleted LEDApplyState command as its unused (use the one in LED.java instead) - Moved additional subsystem-derived LED states into LEDDefaultCommand - Remove redundant LED state commands from RobotContainer bindings where the state can be inferred from subsystem state in LEDDefaultCommand - Re-added LED state for outtaking - Only use LED overrides when necessary when subsystem state can't be derived, or when an actual override is wanted such as stop rollers LED state --------- Co-authored-by: Faizaan-J <125227430+Faizaan-J@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Drive, Vision, Handoff, Spindexer, Shooter, Turret, Hood, Intake, and LEDs
NO AUTONS