ISR Tournament seems stuck

The current ISR Tournament seems to be stuck. Is it? If so, can someone enlighten us with what is wrong? Is it just the time difference?

They literally are half way around the world. Its basically night time for them. Check back to the stream at midnight. They will be playing.

16 Likes

I’m not sure what the issue is, but they had all 6 robots on the field for match 34, waited for awhile, ran a couple of test matches and then all 6 robots left the field. If I had to guess, they ran into some field issue and decided to play the final two matches scheduled for today, first thing tomorrow.

I wish I knew what they ran into. We play our first match Friday. Fore warned is fore armed…

1 Like

Current word is that the blue port had their counters incorrectly done, so balls were not counting correctly all day.

As for matches not happening right now, its literally in Israel. Matches arent going to happen at 1am their time.

7 Likes

I just heard that FMS crashed. Can’t be sure how reliable that is, but the source is pretty good.

Sorry @MikLast didn’t see your post till I had already posted.

That should mean replaying every close match that Blue lost (or won not sure how they were miscounting).

Matches start tomrrow at 2020-02-25T06:15:00Z (thanks again to cool CD features).

Yes, a team counted their scored Power Cells in the match and it didn’t match the official score. So the field crew checked that and indeed saw that the sensors didn’t work as expected.
The fix didn’t take too long, but it’s going to be interesting tomorrow to see who’s gonna get a rematch.

7 Likes

Someone suggested counting and verifying the power cells scored in the blue port via the archived livestream.

Sound very cumbersome… but it might work.

While there was the instance of having HQ look at the scoreboard at T=0 to settle Montreal 2018, Section 11.2 of the manual is pretty clear: “No event personnel, including the Head REFEREE, will review video, photos, artistic renderings, etc. of any MATCH, from any source, under any circumstances.”

1 Like

The right thing to do is redoing all of the quals that have been played… But the costs would be very high and the (logistic, manpower) hassle for US FIRST and FIRST Israel would be huge.

That’s also a problem becuase on Wedenesday-Thursday, ISR District Event #2 happens.

1 Like

Whatever the issue is, it doesn’t seem too lopsided towards one alliance or another. Red alliance has won 15 with an average winning margin of 38.9, and blue has won 17 with an average winning margin of 29.5. One tie. Red has scored 2270 points total and blue 2189 points total. Maybe the problem hasn’t been happening all day.

1 Like

I think that rule allows HQ, who may not be considered “event personnel” to review match videos.

If I was FIRST, I’d be reviewing matches to determine how many matches likely are affected by this. I’m not sure how off the sensors were but it’s very possible there are just a handful of matches to be replayed.

Reviewing 33 matches in ~9 hours is pretty easy…

11 Likes

From what I hear, the issue with the counters has been fixed. Nothing is going to be done regarding the matches that have been played already.

Because I’m still bitter about witnessing obvious field scoring issues a few years ago and being told “if it wasn’t your match, why do you care”, I watched each of the 33 matches and compared blue alliance scoring on TBA based on what I counted while watching. Since it’s impossible to differentiate inner or outer port, I just lumped them all together. Two matches (4 and 9) had their stream cut out and thus excluded. While I did my best, I certainly cannot promise this to be 100% accurate – hopefully better than 81% though!

Good news: Only two matches (12 and 22) had their outcome affected.
Bad news: Field scoring missed over 19% of all blue port scoring, likely affecting tiebreakers.
Interesting (and potentially worrisome) new: Field scoring got progressively worse as the day progressed. It was 95% accurate over first 17 matches but only 65% over last 14. (I guess I assumed it was just calibrated wrong but that doesn’t seem to be the case).

I really really hope they assign a volunteer to just manually keep track of the scoring to confirm accuracy.

Match # Auto Tele Final Score Diff Auto (actual) Tele (actual) Auto Diff Tele Diff
1 0 0 -12 0 0 0 0
2 0 4 23 0 4 0 0
3 0 0 -26 0 0 0 0
5 6 13 11 6 13 0 0
6 3 1 5 3 1 0 0
7 6 12 92 6 12 0 0
8 2 11 91 2 11 0 0
10 3 2 -74 3 2 0 0
11 0 3 -10 0 3 0 0
12 3 3 0 4 4 -1 -1
13 1 5 28 3 7 -2 -2
14 3 3 11 3 3 0 0
15 3 7 27 3 7 0 0
16 3 8 15 3 8 0 0
17 3 3 -5 3 3 0 0
18 0 0 -37 0 0 0 0
19 0 1 2 0 1 0 0
20 2 4 18 2 6 0 -2
21 2 2 -23 2 6 0 -4
22 5 2 -2 7 3 -2 -1
23 3 2 35 3 5 0 -3
24 0 0 -26 0 0 0 0
25 2 3 20 3 4 -1 -1
26 5 3 7 5 4 0 -1
27 3 10 -36 7 13 -4 -3
28 0 5 2 0 9 0 -4
29 1 1 -68 3 1 -2 0
30 0 3 -71 0 3 0 0
31 1 0 -97 1 0 0 0
32 1 1 -82 3 2 -2 -1
33 3 3 75 4 7 -1 -4
49 Likes

Assuming that all of the missed balls were outer port shots, it looks like Q12 cost 3 ranks to team 2096. They’re currently in 6th and should be 3rd. 6230 is artificially down a full 10 ranks, from 12 to 22.

(If my math is right)

6 Likes

It seems that 2096 was a surrogate in match 12, so it wouldn’t matter to them anyways in the rankings. 6230, however, was robbed of a quite significant couple of ranking points.

2 Likes

Did you check the red alliance scoring also? I wonder if it’s an issue with the scoring system in general or if it was specific to the blue alliance.

I only checked blue since that was the reported issue and it looked like they were only testing the blue goal at the end of the day. I am curious if red was also having issues.