When you watch the video at the 7:17 timestamp, the front tyres are moving faster than the ground under them. This can easily happen with rear (powered) tyres (i.e., “burning rubber”, “peeling out”, etc.). But how can the front tyres go faster than the ground is making them move?
That’s a great point. I think I am of the mind that it doesn’t need fixing. I also do not like penalties after the race. So just let it be. If once a year a team figures out a way to exploit this, then so be it.
I thought it gave an interesting twist too. I guess I would feel different if I wasn’t a RB fan. Hard to say.
One other possibility comes to mind. What if there are no rule changes, but instead if the stewards think a team might try to take advantage of this, they decide at race time to hold their ruling disclosure until after the race?
It is for a middle school robotics team (FIRST Lego League if you have ever heard of it). No, I don’t have some burning desire to get rid of the merges. I was mostly woried that we were doing something wrong. We definitely do not have any branches. We really just use github to have a safe place to store our code and so that all of the laptops can have all of the code from all of the teammates.
For sure I don’t want to add any complexity. I think that since from their end it looks like it is doing exactly what they think it does (i.e., I upload my code with a push, and I get everyone else’s code with a pull), there’s definitely no need to fix a non-problem.
Another famous one… bookstores make a lot of people need to poop. https://www.buzzfeed.com/farrahpenn/urge-to-poop-in-bookstore-mariko-aoki-phenomenon