Worlds is sadly done with.
Preserve your amazing autonomous and driver control programming forever !
As I do every year, I would like any teams that think their programing may help future generations to send me the code or (preferably) a link to a git repo I can fork, I will add to a github organization as I have done in previous years. The code can be programmed using any development system, not just VEXcode, as long as I can create a git repo for it (so blocks programs may be difficult to archive). FYI, the names of these old archives actually have nothing to do with what we now call VEXcode, I started setting these up years before we event though of that.
code from the past four years is here
Our code is at:
Driver control is nothing fancy at all, but our auton was pretty cool
Never had the opportunity to actually code my autonomous, so I tended to use an auton from our last robot iteration (Not shown in the code as I removed it, as I do not want to show a bad example of an autonomous). The rest of the code is quite well-built, and there are moments where functions become reliable enough where I just decide to compress a function into one line of code. There are both good and bad coding practices in this code, but I’m just posting it for the sake of it
3674RRobot-2020-03-13T18-34-05.zip (11.0 KB)
It’s not as documented as I would’ve liked, but here is my code archive for the season. Some of the code (primarily my copycat and pure pursuit code) isn’t well-tested, and I was never able to use copycat, odometry, or pure pursuit for competition. Anyways, happy coding!
For my first year of coding, things went decently well. The code isn’t very good, but it’s also not terrible.
My code for this year can be found here.
I am most proud of my interface code (all in the interface.hpp in the DawgOsProg folder with my main bot code) that provided a ton of utility to our team. I am terrible with coding conventions and doing stuff 100% efficiently/correctly, but imo it worked fairly well and made my life way easier. I would also be willing to talk to other teams about how it was done, so feel free to message me.
(All for PROS btw)
SQL’s code for our 24in robot is here:
And the 15in robot code here:
Nothing particularly fancy or complicated in there, but some interesting code for drive speed and lift presets in the 15in repo.
Nothing especially interesting, but our controller screen stuff was pretty neat.
I also adore the function we used for our stacking macro
Some cool stuff in the works on branches too (but not that cool)
Nothing much. Very messy. I guess my splash screen gif stuff was kinda cool.
Thanks to those who posted links so far, keep them coming.
This years collection so far is here.
Not the most interesting code in the world, but it comes with a cool GUI?
Thanks, what’s your team number @JoshJ ?
oh oops, my team number is 23218A
20610N Nebula’s code from the past 2 years.
Using okapilib PID chassis and LVGL for a custom screen.
PROS 2 and 3 code for team 11872A. The V5 code is pretty rough since we upgraded a few weeks before states, so nothing is object-oriented.
Sorry for the lack of documentation and how messy it is. It seemed to work pretty well throughout this season though.
Hey, might as well throw mine in. Nothing particularly new to vex, but I’ve got lots of fancy C++ stuff to make it look clean. Also got a nice and overly complicated auton selector that I think looks pretty good.