Thanks! I’m such an OnShape noob…
Your 2023 ‘Auto Scoring’ came to mind as something that would be super useful in this game (although thats useful in most games haha).
Did you specifically build it so that it would solve for the rotation first?
I haven’t peered through the code yet but it looks like theres a case where the DriveToPose solves its rotation first before proceeding. Makes sense to me as the problem becomes much more complex trying to understand if you have enough space to rotate before hitting the scoring platforms
Linked a timestamp where it appears to occur:
EDIT:
actually this example is a little better as it looks like you spin before correcting your translation component of the targeted pose
Our 2023 auto scoring started correcting rotation and translation simultaneously, so there wasn’t any kind of sequencing. I think the effect you’re seeing is a combination of the fact that 1) correcting rotation is much faster than translation so it tends to finish first and 2) speed desaturation for the modules will tend to limit translational speed first rather rotational speed.
ah okay, glad you said that because before I saw your reply I was inspecting your code and couldn’t figure out how it was doing that!
Understood! Thanks for the reply!
We are thinking about possibly in our auto scoring using something that’ll help converge on the rotation target first, depending on how close we need to get to the reef