GithubHelp home page GithubHelp logo

offseason-2023-bot-1's Introduction

offseason-2023-bot-1's People

Contributors

jordanjcoderman avatar owen756 avatar jonahsnider avatar renovate[bot] avatar jellosmello avatar ryanknj5 avatar lechris07 avatar saikiranra avatar

Watchers

 avatar Max Westwater avatar  avatar

offseason-2023-bot-1's Issues

Add AdvantageKit logging for shoulder

Blocked by:

We should add in some logging to the shoulder subsystem in robotPeriodic(), which records a few values to help debug & tune via AdvantageKit.
The values we probably want to record are:

  • Velocity
  • Angle
  • Goal angle
  • Stator current
  • Applied voltage

Set PID values to 0

In preparation for robot bringup, we should make sure all the PID values for motors are set to 0, so there are no dangerous movements when we first start tuning. Swerve is the exception here, since we know the values for that are tuned properly. Everything else (shoulder, wrist, etc.) should have the PID values set to 0, if they're not already.

Support scoring low on either side automatically

We can only score mid and high from a single side on the robot. We always intake from the side opposite of that.

Because scoring low doesn't require much extension of the superstructure, we can score low from the front or back of the robot.

We should make code that automatically scores on whichever side of the robot is facing toward the grids when scoring low.

So, if you're facing forward and you try scoring low, it should score on the front of the robot.
And if you're facing backwards when you try scoring low, it should score on the back of the robot.

This means that the driver won't need to worry about turning around when doing low node cycles.

Add AdvantageKit logging for wrist

Blocked by #4

We should add in some logging to the wrist subsystem in robotPeriodic(), which records a few values to help debug & tune via AdvantageKit.
The values we probably want to record are:

  • Velocity
  • Angle
  • Goal angle
  • Stator current
  • Applied voltage

Use intake motor velocity to detect game pieces

Now that #3 is finished, we can start implementing some of the more complicated behavior.
For this feature, we want to use the intake motor's velocity to detect when game pieces enter/exit the intake, to help with automation.

Most likely we want to implement this by reading in the motor's velocity, passing it through a linear filter, and then checking if it is below/above a threshold.

We wrote very similar code to this on Spike which used the motor's current, but that was less reliable than using the sensor velocity.

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.


Warning

Renovate failed to look up the following dependencies: Failed to look up maven package org.junit.jupiter:junit-jupiter-api, Failed to look up maven package org.junit.jupiter:junit-jupiter-params, Failed to look up maven package org.junit.jupiter:junit-jupiter-engine, Failed to look up maven package org.littletonrobotics.akit.junction:junction-autolog.

Files affected: build.gradle


Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

github-actions
.github/workflows/ci.yml
  • actions/checkout v4
  • actions/setup-java v3
  • gradle/wrapper-validation-action v1
  • actions/checkout v4
  • actions/setup-java v3
  • gradle/wrapper-validation-action v1
gradle
settings.gradle
build.gradle
  • edu.wpi.first.GradleRIO 2023.4.3
  • com.peterabeles.gversion 1.10.2
  • com.diffplug.spotless 6.22.0
  • org.junit.jupiter:junit-jupiter-api 5.8.2
  • org.junit.jupiter:junit-jupiter-params 5.8.2
  • org.junit.jupiter:junit-jupiter-engine 5.8.2
  • org.littletonrobotics.akit.junction:junction-autolog 2.0.0
gradle-wrapper
gradle/wrapper/gradle-wrapper.properties
  • gradle 8.4

  • Check this box to trigger a request for Renovate to run again on this repository

Add AdvantageKit logging for intake

Blocked by:

We should add in some logging to the intake subsystem in robotPeriodic(), which records a few values to help debug & tune via AdvantageKit.
The values we probably want to record are:

  • Velocity
  • Goal IntakeState
  • Held game piece
  • Stator current
  • Applied voltage

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.