Jason Daming

In [my project](https://github.com/6391-Ursuline-Bearbotics/2022-6391-Swerve-Beta) I already have all of the changes in a separate folder and expect that is what teams will need to do for this year while this solution...

I don't know what our standard is for that. They unit tests should have been created when they were merged.

Are there still things left to be done on this issue?

So what would you do instead encoder counts? The team I am helping wants to dump into the low goal then back up, that is super simple. I see no...

Also a timed multistep auto is already in the base code for LabVIEW. I agree that I wish more teams would progress beyond that style of auto. But I think...

Wasn't this working before? Did something change? Yeah seems like something that upstream should fix?

1) Specify the Falcon 500 as the hardware for the CTRE examples. Here you can probably mention the PWM is using the KOP hardware. 2) Handle inversion in the defining...

I completely agree with 1 2 I think is tricky as advising where that code goes really depends on what it is for and if using command or non command....

I think any and all extra steps here would be a good idea. There are WAY too many people that their trajectory "not working" is entirely due to these issues....

I have seen teams do what is the link above a lot when they get code stuck. I think the best course of action might be to take the: Set...