Why did Galileo advance instead of Newton?

Newton had more hang points.


4 Likes

I really don’t know, but on TBA Galileo had 324 hangar points while Newton only had 247.

4 Likes

2 Likes

Headers on the website are wrong. What’s labeled “foul and tech” is actually hanger average.

17 Likes

In addition, I believe TBA has incorrect hanger values listed. Gal and other divisions have over the max 45/match of 225 (45*5).

3 Likes

Added manually:
Galileo: 201
Newton: 151
Who knows why the counts on TBA are wrong but Galileo had more that Newton

1 Like

It’s a known issue on TBA’s end: https://github.com/the-blue-alliance/the-blue-alliance/issues/4444

1 Like

Thanks for filing issues :slight_smile:

This should be fixed now on the TBA side!

Saw this as well - is that even possible across 5 matches though? Even 45*5= 225.

Edit: Hold on it looks like the “Hangar Points” column is just displaying the number of Hangar points from the first match each alliance played during the round robin, not their average hangar score.

Is it really fixed? Now it’s showing that Newton advanced to Finals from 2nd tiebreaker:

1 Like

I did notice that the scoring was very inconsistent towards the end of Auto - the first ~5 seconds of cargo scored in autonomous is scored at Auto rates, since cargo can take a while to process, and I noticed sometimes teams would score 2 and then 4 for cargo that scored just as Teleop started in one of the Round Robin matches. Could have easily been the deciding factor.

try one more time :wink:

I fixed it, broke it, then fixed it again. I do not advise rolling TBA from in-flight wifi at 35,000 ft…

4 Likes

That’s more like it, thanks!

1 Like

If you want to follow the tragedy of my afternoon, here’s the TBA changelog :laughing:

Also a good a time as any: TBA is open source and maintained by volunteers. If you know python and want to help us out maintaining the site, drop me a DM!

5 Likes

That wasn’t me that reported it, actually - I’ve just been following along in the TBA Slack.

+1 for filing issues on GitHub, though. It’s a great way to make TBA maintainers aware. I saw the first acknowledgement 4 minutes (!) after the issue was reported, which is pretty impressive given how busy everyone is during champs.

For anyone who needs links:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.