FiM Midland:
Swerve-13
Tank-19
Other-7
1 Like
Arizona West: 14 Swerve, 26 Tank, 2 Other (Mecanum).
Playoff matches: 13 Swerve, 10 Tank, 1 Other. 1 backup robot called in (Tank).
2 Likes
There’s a flaw in this data collection. There is a difference between kit bot and someone that went to the trouble of building a tank drive. It would be interesting to see if we going to create a class of swerve vs. kit over time.
David
2 Likes
There are a lot of ways to split up the “tank” division between kit bots, custom 6wd/8wd/Xwd, kit bots with different wheels, kit frames with different gearboxes, shifters, omnis, etc. There is a vast spectrum of different tank drivetrain approaches, some KOP derived and others completely custom.
This data survey is simple: Tank, Swerve, Other. It doesn’t need to be more detailed than that; the drivetrain type is the interesting metric being followed here.
4 Likes
So one thing I have been thinking about is multiple event teams skewing data. So since Tallahassee is done we have every Florida team’s drive train.
So for Florida the count was:
38 - Tank
23 - Swerve
7 - Mecanum
2- H-Drive
This might be more useful at the end of the season since I feel teams attending multiple events (outside of the district system) are more likely to have more money thus make the investment into swerve and we may not get a feel for the true representation of number of teams with each drivetrain.
1 Like
This data collection initially started in The Fall of the House of Tank Drive. At that point I was really mostly looking to get minimally biased data on swerve v. tank. You’re right that this data isn’t super specific. However, it ultimately gets down to the goal of seeing how many teams are using tank v swerve. Also, the more specific information I try and include the fewer events I’ll actually get data for. Finally, I think it could actually get somewhat difficult to set a hard boundary between what is a KOP vs. custom drivetrain. (The Andymark wheel upgrades to go to 8 wheels or change wheel diameter probably count, but the mecanum wheel upgrade is pretty clearly not tank so can it be KOP but not tank?) Generally I think it’s easier to quantify the end result hitting the carpet than the manufacturing method. I fully support you going and trying to seperate that yourself and all of the data I have* is either in this thread, the thread I linked above, or the spreadsheet which I’ve been sporadically uploading here (I’ll put together a current data post tonight). I recognize that this data is a very low resolution view, but to me it was more important to get a low resolution view of as many events as possible rather than looking at fewer events in more detail.
*I only seperated North Shore data to the three categories, but if you want it in more detail I’m happy to put that together for you.
Funny thing about that. @jdunston94 has been working on putting together some stuff through the TBA API to build up a spreadsheet by team and get more accurate percentages. Unfortunately, something like that really requires automation to be able to pull all of that data. One of us will probably reach out at some point on this thread to get data by team from those who have it, but if you are able to send it now that would be great.
Thanks for the data.
Data Time!
Here’s the current season data:
And Here’s Week 4:
Also DCMP (Note that the team numbers are pulled from the game manual since teams aren’t in TBA yet):
Israel has generally been more swerve heavy than average. I suspect that the District Champs numbers will go down as more are filled in, although it also seems likely that most DCMPs will be higher than their district average. (I should add in averages for the districts).
FIM Troy 1
Swerve - 19
Tank - 22
Mecanum - 1
1 Like
I should have a preliminary sheet up in the next day or so. We were competing at west michigan this weekend so I ran out of time to pull it together. Once the form is together, I can start getting peoples team data in. Per blue alliance, there are 3325 teams competing this year.
1 Like
FiM Lakeview 1:
Swerve 18
Tank 20
Mecanum 2
1 Like
@jdunston94 has a spreadsheet together and I’m filling in drivetrain type by team, so if anyone has data by team and hasn’t posted it here yet, please post it in this thread.
I’ve filled in with all the data on CD. Here’s the current summary page:
This probably won’t be the final page, I just made it quickly to get a general idea of the data for now. I’m not going to be posting this spreadsheet yet.
I’m still looking for data on most teams so if anyone has data with individual team numbers please send it to me.
@MARS_James Do you by any chance have data for Florida teams you can send me?
Beyond this, do you want like specific team numbers associated with each drive because I do have that as well as how well they did in the tournaments.
Just tell me what you need and I can provide it (most likely)
I’d like specific team numbers with drive trains. jdunston94 built a spreadsheet that should take care of everything else.
Thank you!
1 Like
This is quite telling on the future of FRC. I think new teams are going to keep with KoP tanks for the foreseeable future…until swerve reaches the masses in affordability. Motors can’t be helped…those are going to be what they are price wise. and with the cost of the combo motor setup ranging from $76 for NEO and NEO550 on MAXSwerve, and $96 (2 NEO)-$420 (2 Falcons) per corner…I don’t thing tanks are going away for a bit. Then add in the about $300 per module…and encoders…the price is what is going to keep the Tanks around. MAXSwerve has the best intro price per corner total. Then there’s the wheel/tread cost for both.
Of course the coding for new teams for both with SDS and similar having the steepest learning curve…while MAXSwerve having a steep learning curve…not as bad as SDS with the cheat they provide for alignment. Which MAY interest new/newer teams to swerve.
Ventura County Regional:
Swerve - 25
Tank - 19
Mecanum - 2
1 Like
Thank you! Do you by any chance have data by team you could send me? I’m trying to collect that as well where possible to be able to compensate for multi-event teams