saintsrobotics / frc2020 Goto Github PK

What seems to have happened is that we are giving the drive method inverted x value (forward-backward input) and inverted rotation. To fix that, the drive motors were inverted. Meaning, that while this isn't a problem when the drivetrain is controlled with joysticks, it's a problem with position tracking. It does not uphold the contract established by our contract with the drivetrain.

Create an implementation of ILogger for Shuffleboard.

I we were to call getDegrees, it wouldn't use the offset.
Also 5 is a magic num

The shooter only starts up to its new set speed only if its setpoint previously was 0. Not sure why this is here. Also may want to remove the SmartDashboard provider before comp.

Due to a change in the logic the tests are failing. Need to update the test data to reflect update.

Define the various strategies that need to be coded for the Autonomous mode part of the game.

Goals

• Investigate multiple options, provide pros and cons for both. Also maybe create a list of needs and wants (like we did during manipulator brainstorming on Sunday)
• Are we able to get SmartDashboard running during the sim?

It doesn't compile, so it should be easy to find the bug

also figure out why driving left does not work

• Check out the odometry classes in WPILib here (ctrl F the page for "odometry")

Criteria:

• integrate with slack
• events can be assigned to members, they can respond

Implement the subsystem to actually control the robot. This task is to have the teleOp method working. Ie

move(x,y,rotation)

the magic number is already in the configs file!

Configure project to be able to write unit tests

1. Enable JUnit
2. Configure Guice

Criteria

• What are the available options?
• What are the pros/cons of each option?
• Ease of use of each option?
• Are the options compatible with FRC 2020 season?

Implement the subsystem to actually control the robot. Assuming the teleOp has been complete the other high level commands can be completed.

Everything except:

• move(x,y,rotation)

and make a habit of adding javadocs when you write stuff in the future

Put a comment in the file

Add an implementation for the Mock drivetrain for testing purposes.

The Mock drivetrain should include a full set of unit tests

Sometimes you just want to refactor some code without adding new functionality. You can use this Issue to assign that PR to this issue. Don't use when adding new features.

Enable the ability to simulate the scheduler running as it would within a game. This should allow better testing (unit) of autonomous code.

Refactor the MockDrive train to support new Nav Commands.