-
Notifications
You must be signed in to change notification settings - Fork 0
Auto Chooser #21
Comments
@Jamdan2 Are the |
@will-hou: I think the best solution is to write one single function that generates all possible autonomous paths, and takes in the constraints as parameters. It would be redundant to write several functions that perform almost the exact same routines, besides changing a few numbers. And should delay be a |
I agree, a function to generate all possible paths would be the most ideal because we wouldn't waste time generating them during auto. However, this is very different to how we're currently doing it. All of our paths are generated on-the-fly atm using the robot's true movements (in the x- and y- directions) and its true heading. This make them more resistant to any changes due to how the robot differs mechanically. Of course, this does mean wasting ~1-2 seconds of autonomous (even though path generation is only supposed to take around 35 ms). I think as long as we can complete our auto sequence within 15 seconds, there's no reason I can see to not to stick with on-the-fly path generation. It would definitely save a lot of time tuning with pre-generated values that may differ on the practice and competition robots. |
Oh and yes, the delay could be a |
The sendy is working so now we can get on this |
The Driveteam should be able to select which auto path to run before a match without pushing any code. We could probably do this we several dropdown
SendableChoosers
in the ShuffleBoard:We could then use all of these constraints to figure out what paths we should run. I'm not sure what the most efficient way to do this would be though. Since most of the current paths we have are generated during the auto period, we could just write a command for each path group (which is how things are set up in the
autonomous
branch currently). It would work, but it feels kinda icky. Any ideas here?The text was updated successfully, but these errors were encountered: