Skip to content

Frisbeebot #56

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

Closed

Conversation

BerkeSinanYetkin
Copy link
Contributor

#49 again

seems like wpilib2023 changed a lot of methods' names. Also updated those in the other examples.

@BerkeSinanYetkin
Copy link
Contributor Author

Do the tests run in 2022 wpilib?

@BerkeSinanYetkin
Copy link
Contributor Author

Do the tests run in 2022 wpilib?

I believe this might be the problem, the ramsete example doesn't fail on my computer

@BerkeSinanYetkin
Copy link
Contributor Author

BerkeSinanYetkin commented Dec 18, 2022

Frisbeebot's setDistancePerPulse methods and romi's pyntcore imports fail the tests on my machine. Though Frisbeebot works as intended in simulation. Should I add it to ignored tests? Have no idea why romi doesn't work, can't figure it out.

@megarubber
Copy link
Contributor

megarubber commented Dec 18, 2022

Do the tests run in 2022 wpilib?

Hey @BerkeSinanYetkin, have you tried to update from 2022 to 2023 beta?
I also had this problem when I converted the armbotoffboard example.

pip install --pre robotpy

@BerkeSinanYetkin
Copy link
Contributor Author

BerkeSinanYetkin commented Dec 18, 2022

Do the tests run in 2022 wpilib?

Hey @BerkeSinanYetkin, have you tried to update from 2022 to 2023 beta? I also had this problem when I converted the armbotoffboard example.

pip install --pre robotpy

I did update to the beta, After I did that and wrote the frisbeebot example; the tests didn't like the other examples, so I changed them to work with 2023 and now the test on github don't approve my changes, but my machine which runs the beta do approve them when i run "run_tests.sh" on my terminal.

driveCartesian's gyro argument and wpilib.SpeedControllerGroup's name have changed to Rotation2d and MotorControllerGroup iirc, there might be other changes too.

EDIT: I forgot to say, in the original wpilib c++/java examples; they do it with methods that were added in the 2023. So if we want #49 to happen, we need to use robotpy 2023.

@virtuald
Copy link
Member

Hey, I'm going to fix the 2023-beta branch and merge that into main momentarily. Then you can work off that.

@virtuald
Copy link
Member

Ok, I've merged the 2023-beta branch into main, and the tests all pass. Please rebase this branch off of the current main, update to the latest beta (robotpy 2023.0.0b7), and all should be well. Sorry for the confusion!

If you're having issues rebasing your branch, then let me know and we can figure something out.

@BerkeSinanYetkin
Copy link
Contributor Author

Ok, I've merged the 2023-beta branch into main, and the tests all pass. Please rebase this branch off of the current main, update to the latest beta (robotpy 2023.0.0b7), and all should be well. Sorry for the confusion!

If you're having issues rebasing your branch, then let me know and we can figure something out.

AFAIK you can't change which branch you want to merge from, so i'm closing this pr and creating a new one.

@virtuald
Copy link
Member

You can force push over your existing branch after you rebase. But sure, whatever works for you.

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

Successfully merging this pull request may close these issues.

4 participants