![]() |
disablity score
well i am at ucf regionals and we are doing pretty good after the first day but i want to raise a issue we where in first place and then we had to devasting matches first match we where paired with 267 that had snappd there shaft earlier and so we los that mach but mostly from are fault cause of are ai but then we dropped to third and we where paired with a team that doesnt have a working robot so they didnt bring it out and so we where taking on the first place team and the 5th place team by are selves and we did good the score was a spread of 16 point spread 41 to 57 if we could of knocked the one team off the top of the ramp we would of won but see we where over powered and coulend handle them both i mean we did pretty good at it but if we had another working robot we would of win so i am just wandering wouldnt it be good a idea to add like a disablity score if a team doesnt show up just for the team that showed up cause i mean we could of win if we had someone helping us and becasue of that match we dropped to 7th so i think there should be some rule like that cause it just really hurt are score what is your thoughts on that
|
At Cheasapeake, we had a few matches, that i saw where it was 1vs2 and the 1 alliance still won
|
Lol... this must be your first year doing FIRST.
Realize around 105% of the game is luck... for example, the team in the pit next to us came to competition with a frame of aluminum extrusion, worked on it, competed in 2 qualifying, and was seeded 10th. The game is not fair in the sense that a perfectly working robot will not always win. A half working robot may somehow get to the top. A great team may be deprived of a worthy victory. That is why in FIRST, the most important things aren't the victories but the accomplishments outside the competition. Winning or losing the competition means nothing; your robot may be perfect or it may be a box with wheels but with luck anything can happen. The real award comes with recognition from fellow teams and being happy yourself of what you did. |
I'd love to help and read it, but without periods or capitalization I'm just so confused.:confused:
|
actually this is my third year i guess its just really fustrating when you are ranked 1 and you get screwed over like that and its not all luck that is what is called stratgey i dont know what regionals you went to but if you watch any of ucf its mostly skill if you look at the teams there and see some of the matches its skill
|
Ryan: My advice to you is "have fun." In all honesty, the semi-random match pairings often give good teams "bad" partners. It happens, it's life.
FIRST isn't all about winning. If you've had a good experience even in your losses then you are still coming out ahead in my opinion. |
You're in 7th place- I wouldn't complain if I were you. 34 other teams at UCF would like to be in your position.
About this disability thing- I believe there was something like this before.. called the placebo.. I don't know the details (as I've only been around for the past 3 years)- could someone fill in the gaps for me- thanks |
FIRST has tried a few times to make a broken robot "useful." I wasn't around for the placebo year, but last year, a dead robot was worth 10 points (as long as it doesnt' leave scoring zone).
2 years ago, the infamous "Stretcher" was enacted. The stretcher was basically a 40" x 40" square. (i think, I don't know exact dimensions) If your alliance mate could drag the stretcher (which was a wood base on casters with PVC pipe to "grab") your dead bot could be worth 10 pts to the alliance. This year, if your mate is dead, you have a dead mate. Its rough, but it will happen to probably everyone at least once. |
o i remeber the stretcher it was the worst no one would drag it but i mean its just so fustrating i need to go outside and screamm
|
There is something you can do. If you see a team with a broken bot do everything you can to help fix it. Some people think teams make a point of helping other teams just to impress judges and get awards. The truth is they do it to prevent the situation you faced today. If a team is struggling make sure they have everything they need to fix there bot. Having handicaps and the such would just add more fuel to the fire when it comes to all these debates.
pleaseuseatleastaminimumamountofperiodsandcapitals Good Luck Tommarow. |
Quote:
Cory |
Teamwork
The main concept of FIRST is teamwork...
You and your partner needs to work together to accomplish the task. What I have noticed this year is more battlebots and less teamwork. I am sorry if I am lecturing, but we need to remember that one of the purposes of FIRST is TEAMWORK . Have fun and make friends, but work together and learn. |
Heh heh.
Some match at MMR, 2002. 93's partner never started. 93 is sitting back home with their dead partner, and the alliance needs a few more points to win. There's a goal sittiing just outside of the scoring zone. With 9 seconds left, 93 rushes out to the middle of the field, nudges the goal into scoring zone and rushes back to home. The 93 alliance wins. First match on Einstein, Nationals 2002. 93 and some other team up against two regional champions. 93's partner's battery disconnects in the middle of the field. The 93 alliance wins. Do your best, take a chance. See how your next match partner is doing half an hour before you will be paired up. If they need help, do your best to get them running. If your partner isn't running by match time, don't freak out - it's not unheard of for a team to win in a 1v2 situation. And, like Gadget and a few others have said before, keep in mind that it's about the experience, not about winning. - Katie |
Quote:
I think he was upset that his alliance lost after their partner broke/was disabled. That's all I can fathom. |
hey guys sorry i dont put commas and periods it takes to long, but i will try now. ya well we finished third overall. which was nice, we lost in the semifinals. we where teamed up with us (710) 267, 710. they where awesome great partners just not are day
|
| All times are GMT -5. The time now is 19:26. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi