Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I believe this is somehow the culprit of the overrun #67

Open
DavidDePauw1 opened this issue Mar 20, 2024 · 1 comment
Open

I believe this is somehow the culprit of the overrun #67

DavidDePauw1 opened this issue Mar 20, 2024 · 1 comment

Comments

@DavidDePauw1
Copy link

next = Commands.sequence(travelToPoint, trackPointCmd);

@nab138 I searched both this repo and oxplorer, and this is the only instance of using a sequence command that I can find. I remember that a sequential group execute step was taking about half a second from the data of one of the overruns, so I'm guessing one of these commands is causing the issue. Do we need to travel to the nearest point on the shooting zone? Can we simplify this by removing this sequence and just having the bot travel to a point while checking if it is currently in the zone instead?

@nab138
Copy link
Collaborator

nab138 commented Mar 20, 2024

The updated code is on the LEDs branch, I believe I am doing that aleeady

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants