|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Scoring error at Boston.
This seems to have happened several times at Regionals, sometimes due to
human error but I didn't see any hands near the ball chutes in this particular match. Some Regionals posted human scorers at each goal. I haven't looked at the position of the ball detector beams, but if there is a situation where multiple balls only break the beam once, then there could be conditions that would cause a negative count. I wonder what the FMS does when more balls are returned to play than it has counted as scored? |
|
#2
|
|||
|
|||
|
Re: Scoring error at Boston.
Quote:
I'm also curious about how it handles a non-scored ball passing through the return |
|
#3
|
|||
|
|||
|
Re: Scoring error at Boston.
There seemed to be multiple scoring errors In Quarter 4 Match 2 at the Boston Regional:
http://www.thebluealliance.net/tbatv/match/2010ma_qf4m2 If you watch carefully, at 1:25 our alliance scores a goal, making it 4-3 blue alliance. Right after that if you look even closer, you can see that we score another point. Instead of adding another point to our score, 2 points were taken away making the score 3-2, red alliance. The score ended 3-2, but for some reason, the final score ended up 6-3, red alliance. I can't know for sure, since half the time the camera was aimed at our end, but I don't remember seeing the red alliance score 3 uncounted points. The announcer said something about dogma penalties when 3 points were deducted from our score, but I don't know if that's what really cause it. I can't say I'm not a bit disappointed by the results, since from my perspective, we might have actually won that match. If the end score was the result of a field error, then it might have actually prevented my alliance from winning our 2nd match in the quarterfinals, and going on to the semifinals. Last edited by AmoryG : 31-03-2010 at 17:46. |
|
#4
|
||||
|
||||
|
Re: Scoring error at Boston.
At the Virginia regional there were multiple occurrences like this affecting multiple teams, us being one of them. In one match, we scored 6 goals, none of them were counted. Apparently this one specific red goal's ball sensor was especially sensitive and even the slightest touch before it COMPLETELY cleared the goal chute would trip the automatic penalty. This problem caused many delays and eventually they just replaced the sensor altogether. I'm pretty sure in the elimination rounds they were using volunteers to keep track of scores in addition to their automated system, but I think that also may have been due to the ball return sensors malfunctioning and they were actually keeping track of the 11 seconds for the balls to be returned. Oh well, hopefully they have these issues sorted out before the championship.
|
|
#5
|
|||
|
|||
|
Re: Scoring error at Boston.
After watching that autonomous closely several times I agree that only one ball was and should be scored. It's hard to tell if it was an automatic penalty, or if it was a field error.
|
|
#6
|
|||
|
|||
|
Re: Scoring error at Boston.
As far as I've seen, the ONLY penalty (not even DOGMA) that is shown on the live display is the automatic -2 for re-entering the ball counter. In [urlhttp://www.thebluealliance.net/tbatv/match/2010ma_qf4m2]this match[/url], around 1:35 a ball is certainly scored, however it does the 2 point deduction instead of scoring. If it was an HP error, the score would have dropped to 3, since the ball scored would added and offset the -2. However, since a straight -2 was applied, this has to be an error in the counter equipment.
|
|
#7
|
|||
|
|||
|
Re: Scoring error at Boston.
Quote:
You are correct, however, in saying that DOGMA penalties are not assessed in real time. Every one that I've seen has showed up as a penalty after the match. |
|
#8
|
|||
|
|||
|
Re: Scoring error at Boston.
What I saw was a ball scored, bringing score to 3-4. Another ball was scored a few seconds later, which dropped the score to 3-2. There was enough time between the scores that there is no chance this could have been a situation where 2 balls passing through the counter at the same time messes up the system
|
|
#9
|
|||
|
|||
|
Re: Scoring error at Boston.
Quote:
|
|
#10
|
|||
|
|||
|
Re: Scoring error at Boston.
Quote:
Quote:
A properly mounted sensor with bug-free software should never encounter a problem like this. As I've said before, if FIRST is going to base the outcome of matches on the reports of computer software (which I have no intrinsic problems with), they should at least allow the community to see the source code and help ensure that software is error-free. |
|
#11
|
|||||
|
|||||
|
Re: Scoring error at Boston.
The FMS this year isn't reliable at all. Our third quarterfinals match was a 6-6 tie, but the scoreboard showed 8-2 with us losing. We went up to the ref, and they were already changing it, so it didn't end up too badly for us, but still.
|
|
#12
|
|||
|
|||
|
Re: Scoring error at Boston.
The scoring system has some bugs, no doubt. I'm just worried that FIRST will go back to manual scoring next year due to all of the problems. IMO, electronic scoring is the way to go - the availability of a (mostly) accurate real-time score display this year was beneficial for everyone - but the system just needs to have a few kinks worked out.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Error... LARGE error with classmate | Brett Elflord | General Forum | 4 | 18-02-2010 08:15 |
| MPLAB error: Error [1027] unable to locate 'serial_ports.h' | rokenboker | Programming | 10 | 03-09-2009 16:29 |
| Error in code light on, trouble finding error | Bryan Herbst | Programming | 16 | 12-10-2007 21:59 |
| 180:Error: syntax error help! | seanl | Programming | 8 | 04-02-2007 11:31 |
| stupid Array error: Error [1300] stack frame too l | Validius | Programming | 7 | 27-01-2006 10:53 |