![]() |
Pedestal Delays
At the Southfield District Event (MI) there were a few cases where the delay between an alliance clearing the field of balls and the pedestal being lit to allow the inbounder to grab the next ball.
I'm wondering if this was observed at other events, and how it was handled. In one of our matches we had a 40 sec delay, and, because the delay wasn't explicitly observed during the match, it took a number of visits with the referees before we were granted a replay of the match. Here is the video of the match: https://www.youtube.com/watch?v=vv-QUKZLWUQ At 1:00 (video time) you see the last red auto-ball cleared from the field. At 1:45, you see the human player return with our first cycle ball. For about 40 seconds, the pedestal was not lit. You cannot see the pedestal in the video, however the problem is quite obvious. While I'm generally against 'video reviews' of penalties and such during a match, I'm wondering if an exception should be allowed for cases such as this; where clear video evidence of a field/match fault exists that can be correlated with events observed on the field (supposedly, the ref marked the field as cleared shortly after the last ball was scored, but some delay caused the pedestal to not light). I saw that in some cases even small delays often had a big impact on match flow, (where a robot sits and waits for a new ball as the old ball is cleared, but gives up after some delay to go defend, then ends up being late for the inbounder). I would expect these smaller delays will diminish over time as the refs get more experienced with the game; but there are some interesting situations introduced by the 'human' factor in the game. |
Re: Pedestal Delays
Since this was experienced so much for all teams, the refs should have given a verbal go ahead to teams to take the ball. Rather than have to replay the matches. Would have helped the event stay on time. I hope they have this fixed for the next week of events.
|
Re: Pedestal Delays
Hopefully an operator can describe how this works. It has to be manually turned on, I don't see how it can be automated.
We had an incident at MAR Mount Olive. Another team human player already had a ball ready to load a robot. When I turned around our human player had taken a ball off the pedestal. As coach I chased after him before he threw it onto the field and returned it to the pedestal. Here is where it becomes a blur. When I returned it to the pedestal the light was on. At the end of the game the head ref approached me and I described the above. We were accessed a 50 point penalty but we had lost and didn't change the outcome of the match. Without proof I couldn't contest it. Our human player is special education, so I started to doubt having him as the human player. I felt bad about this because in a later match, I watched him, he would NOT touch the ball until the pedestal lit. He is a great human player. In a later match (not us) there was a field fault because that same pedestal light did not turn off. My theory is that in our match, once the first ball was taken, another ball was placed on it while it was still lit, but I can not prove it. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
So basically, this appears to be a software issue, and hopefully will be fixed in time for week 2. |
Re: Pedestal Delays
Is it my imagination, or is the audience actually yelling "NEW BALL" for those 40 seconds?
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
I also noticed there were some cases where the pedestal was lit (with no ball on it) when it shouldn't have been. I assumed I just forgot the conditions for it being lit. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
-Danny |
Re: Pedestal Delays
One of our matches the pedestal did not light up after autonomous so our coach was waving and shouting that it was not being lit. It was great that he made a commotion to get attention to it and the match was stopped and we restarted. But I agree, there is a delay with the pedestals and it has to be fixed. Albeit, it is a Week 1 so there are bound to be problems and FIRST will probably work out more of the kinks for Week 2.
|
Re: Pedestal Delays
Quote:
If the pedestal doesn't light up after autonomous, double-check that all your auto balls are off of the field. If they are, then the ref may have been asleep (or hit the wrong button and had to undo it, which kind of stinks). I agree with tanmaker--the ref panels are slow, their connections are slow... (The head ref I worked with this weekend had a number of complaints about the head ref panel, including delays and lack of ability to see what everybody else was putting in.) When I would put in starting balls, it could take several seconds to register after a touch, and sometimes it would unregister randomly. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
We were far from an edge case. There were a lot of very frayed nerves across many teams, and I'm frankly proud of everyone for their handling of it. Still, I hope FIRST understand objectively how big an affect this has. It literally changed alliance selection (the matches involved captains and those who would have been in a captain seed), and directly affects MAR rankings, at first glance by ~10% for some teams. Refs shouldn't be burdened with these kinds of calls. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
It was also frustrating for our mentors refereeing since it's so hard to keep score and ref simultaneously. It was difficult for me at times to keep calm when there were one or two assists not being counted during a cycle, or multiple cycles, but you can't blame the refs or get angry at them. They just have way too much on their plate.
The most frustrating part of all is when you consider that all the teams devote hours and hours of their time to make their robot work, and spend so much of their funds to enter a competition; then they waste $300 to $500 in entry cost on a match where the loss was not the fault of any of the teams, but rather the field. We also had delays with declaring dead balls at IE. On one our matches, the ball was stuck in our robot towards the beginning of the match, and the ball was not declared dead until up to around 30-40 seconds after we signaled that it was no good for play, and finally the match had to be restarted because of this. We also had another match that started perfectly; the autonomous shots went in, and we were far ahead, until I started wondering why our human players weren't inbounding after the first cycle. What was the problem? The pedestal would not light at all, and there was a rematch, and then the pedestal was delayed, and then we had to do another rematch the next day. |
Re: Pedestal Delays
Quote:
Now I feel like a chump for not arguing the pedestal foul. First of all, the confusion altered the outcome of the game in some way. This was really a rematch situation and I should have protested it, assuming there is a way to do that. I did tell them that the light was on so that should have been enough. The game is better than I first thought but we need smooth play and not these glitches. |
Re: Pedestal Delays
Quote:
For future reference: Have a pre-college student on the drive team stand in the referee question box. That is the way to ask questions/clarifications/point out issues. For something like the pedestal issue, it's important to let the nearest referee/FTA know DURING the match. The precedent at Mt. O was that the pedestal not lighting up correctly was an arena fault, and several matches in qualifications were replayed because of this. That's what Alliance 2 contested in the QFs, and one of the affected matches in the series was replayed. (QF 3-2 and 3-3 were both affected by pedestal issues, but since we didn't make it known in 2 -during- the match, it was not replayed. We made the field crew aware of it in 3, and QF 3-3 was replayed for that arena fault, overturning the series.) |
Re: Pedestal Delays
Quote:
As for having a student go to the question box... our alliances always pulled the control boards and left the field immediately. We had 2 instances of us winning in qualification and then an upset re-score occurring minutes after. We were half way back to the pits. I don't know what to do. I'm half way leaning to have the whole darned alliance stay put, arms crossed until the final scoring happens and then go as a unit (pre-college only) to the question box to at least get an explanation. That seems rather extreme. I will say I was really really hoping for real time scoring this year and I am not getting it. |
Re: Pedestal Delays
Quote:
With all of these replays and scores changing after their displayed, I offer a suggestion: Show the score to the drive teams first. Then let them try to plead with what they may. After all things are finally worked out, then put them on the screen for the rest of the audience and the webcast to see. It would make it so much less dramatic. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
Realistically, you send one of your drivers/human player to the question box. That's probably fine 99% of the time, since they presumably know the rules and what happened during the match, but it does mean you're down a drive team member for moving the robot. In the past I've had the driver in charge of the controls hang back if I thought there might be a problem, while I the other driver and human player handle the robot. |
Re: Pedestal Delays
At CIR (Central Illinois Regional) we had the same issue in the finals, it was frustrating. I hope at Wisconsin they have it fixed.
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
Again, I don't think it's ever really a problem getting a student in the question box and handling the robot, but you are limited to the drive team and have to get in the habit of having someone stay behind to ask questions if need be. It's not really problem but if you aren't planning for it it can be. Quote:
|
Re: Pedestal Delays
A related issue at Hatboro-Horsham was a ball going out of play (commonly over the goal, not through it) and it never being returned to play by field crew. Then the refs/pedestal operator know there is supposed to be a ball in play while there is none.
All I can say is this will get better at week 2 and 3 competitions. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Yes, the whole alliance should be concerned... but that doesn't mean you have to overwhelm the head ref with people. A persons natural reaction to facing a gang of upset people is defensive - you're less likely to get what you want if you send a bunch of people up there all at once to yammer at the head ref. The alliance should work on clearing out the field like they're supposed to, quickly and efficiently, so the next match can start like it's supposed to. If they are all concerned, they can respectfully wait by the exit from the arena to hear the result from the one well spoken student who went up to the question box. Trust me, the ref will see that the entire alliance is waiting for the answer, but he won't feel a need to immediately go on the defensive.
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Judging from the Israeli webcast, it looks like they may have fixed the bug that dealt with the Pedestal lights.
|
Re: Pedestal Delays
Quote:
Then the pedestal problem kicked in in the rematch. |
Re: Pedestal Delays
This is simple... There is a problem. FIRST needs to fix it. Please and thank you. ::rtm::
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
http://www.usfirst.org/roboticsprogr...-Week-1-Review
Frank Mentions it today in the blog post, it is fixed. |
Re: Pedestal Delays
I will believe it when I see it. If we get a dead pedestal like our district mates 1676 (see above), my alliance is going to take that ball and deal with the consequences later.
Now if they can only get rid of these outrageous re-scores. We play to the real time score and we think we are good with a 10 point lead... the boom... the final score has them winning by 30 points. I'm not going to be comfortable with anything less than a 50 point lead from now on. We must count the scores in our heads (along with everything else we need to do) and be prepared to challenge. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
The Israeli regional was much better in this aspect.
There was only one REALLY bad issue I recall... the Red Alliance scored a goal in one of the Qualification Matches, and the volunteer still hadn't put a ball on the pedestal (he had a long time to do it - since the start of the cycle, but he forgot I guess). Anyway, the pedestal got lit .. but since there was no ball on it, he FORBADE the HP to take a ball from the ground next to the pedestal, and wasted a minute and a half before the refs fianlly noticed and allowed the HP to take the ball. Luckily, Red still won because of 100 foul points... I will say however, that it was the only incident I saw which was a real issue. Pedestals nearly always lit up within 5 seconds of a cycle completing. In fact, I don't recall a time where it was more than 5 seconds... :) |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
More importantly, neither the team update nor the blog prevent a head ref from deciding that a 30 second pedestal delay is not worth a foghorn/replay. Personally, this was my major Week 1 problem. Heck, it doesn't say anything about handling a 2:19 second pedestal delay. As long as such a devastating failure mode is theoretically possible (which is always--remember the 2011 minibot towers?), I'd like official guidance on how to handle it. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
1. Fouls 2. A last second cycle input 3. The very few times where a cycle was inputted incorrectly (which, to me at least, only happened once). To say that a significant amount of unexplained extra points showed up on the board after the match is absolutely wrong. And if an alliance is scoring a ball every 15 seconds? That makes it even harder for the refs. Speaking with fellow refs, 99% of the time there was a delay (even as small as 3 seconds) in putting in the livescore was to just last minute check to make sure everything is right. Would you rather us rush to input scores and mess them up? (which I admittedly did once, but noticed it and ensured the score was corrected). |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
Quote:
Volunteering at an event will really open your eyes to how things work. ;) |
Re: Pedestal Delays
Quote:
Week 1 refs were just as frustrated as teams were. The delay in tablets and the FMS affected them just as much as the teams did. The good news from all of this is that a lot of issues have been fixed and the game and competition will only get better as the weeks pass. I'm sorry that some teams only had one shot during a week 1 regional, but they should all (minus rookies) be aware that week 1 will not go perfectly, or even smoothly most of the time. |
Re: Pedestal Delays
Quote:
This is my third year and I finally have a couple of students I think are hooked on robotics. Their reaction? They'd play a third venue if we could afford it. To me that is a win we've never had before. In the spirit of FRC lets let this go and hope for improvements on week 2. |
Re: Pedestal Delays
Quote:
|
Re: Pedestal Delays
There were several issues like this at the palmetto regional. ALL the teams and the outstanding head ref handled each case with GP. If the delay possibly affected the outcome of the match, the match was replayed.
|
Re: Pedestal Delays
Quote:
Best of luck! |
| All times are GMT -5. The time now is 21:25. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi