FIRST please fix....

[pntbll1313]

Originally Posted by engunneer

Off topic: that blue human player went just a bit out of his box...

Sorry to derail the thread but there are no rules that say he can't go outside of his box per G39. As long as he is in contact with the human player area he started in, I can't find any rule that he is breaking. Unless you're saying he lifts his left foot every once in a while and loses contact. You may be right about that.

G39
During the MATCH, TEAMS must remain in contact with the area of the FIELD (ALLIANCE STATION or HUMAN
PLAYER AREA) in which they started the MATCH. Exceptions will be granted for inadvertent, momentary, and
inconsequential infractions and in cases concerning safety.

[Tom Bottiglieri]

Here are some DS logs from matches where this happened to us. Q92 and QF1-1 at SVR.

I've also attached a log from team 118, who saw the same bug at Alamo.

[Tom Line]

I'm glad Greg was there to see it and record info on it. We were all questioning what would happen if they were unable to fix the bug - indefinite replays or just let the defective matches stand? Yikes!

I am ALSO very glad that Marjie Jenkins took the microphone and called out booing after the the second replay was announced. It doesn't matter which team in particular, but I hope the mentors on that particular team have a long talk about gracious professionalism with their members. I'm sure their students would have felt differently had they been on the other side of the field glitch.

I believe Greg grabbed our DS logs as well - we had actually shown him some earlier when he was looking at the field networking.

[Zebra_Fact_Man]

Originally Posted by Tom Line

I am ALSO very glad that Marjie Jenkins took the microphone and called out booing after the the second replay was announced. It doesn't matter which team in particular, but I hope the mentors on that particular team have a long talk about gracious professionalism with their members. I'm sure their students would have felt differently had they been on the other side of the field glitch.

I'm pretty sure no one individual team was responsible for the booing, but rather a collective disappointment from a large portion of the audience. It wasn't directed toward the teams or the staff, but rather HQ itself.

I fully understand that everyone involved with FIRST gets nothing in return for sacrificing their time to make this a possibility except for the satisfaction of helping a lot of students, and I am eternally grateful each of their services. This couldn't be done without them. I myself am a volunteer, both within my own teams and at the events. But come on guys, it's week 7 already! FRC is a product that we all buy into and expect to work, and this kind of problem this late in the season is simply unacceptable. Chances are it had nothing to do with any of the volunteer staff on site; they're just doing their job the best they can. Maybe it's just because I'm getting old enough to finally noticing these problems, or maybe this is actually new, but while all the foot soldiers plod along at each event doing their jobs excellently, quality from the top of the organization seems to have declined.

I'm not mad at the GDC for some of the questionable decisions they made this year regarding the unnecessarily large responsibility allocated to the refs, or some of the penalty values (or the refs for enforcing these penalties), or even the large push toward heavy defense or 1 game-piece games, but this kind of technical failure bothers me greatly.

Keep in mind I have no horse in this race (I was completely unaffected by any of these technical failures and my teams were eliminated from Championship contention weeks ago). I just feel bad for all the alliances including MSC QF 1-1 that have gotten screwed by the the field system we were given to use. I'm just frustrated that while all the other teams are doing their best and working their darnedest, considering the pedestal lights, the hot goal timing, match length discrepancy, and now this, the FMS we were given doesn't seem to be fully debugged before being released to us for use.

disagree with me or not, these are my individual feelings. I don't know any of the facts, so I may be entirely in left field. Thank you event-staff FMS guys for working your butts off to get it fixed. You guys are troopers. This kind of problem is WAY over my level of understanding.

[Jon Stratis]

Originally Posted by Tom Bottiglieri

Here are some DS logs from matches where this happened to us. Q92 and QF1-1 at SVR.

I've also attached a log from team 118, who saw the same bug at Alamo.

We saw this exact same issue at North Star! There were two matches where our autonomous drove forward, put down our arm in order to shoot, and just stopped. We spent half a day trying to figure it out, and the only thing I could see were gaps in autonomous that looked exactly like that - with no apparent cause. It seemed to "fix itself" after those two matches and never happened again, so we pretty much forgot about it.

[Joe Ross]

If you think you were affected by this issue, please run the following tool against your DS Logs: http://www.chiefdelphi.com/forums/sh...67#post1373367

It should be much faster then manually looking at log files and much better then guessing from video evidence.

[johnr]

It would have affected everyone in the match at MSC but it only affected red alliance because their auton was based on time and not sensors. Well, something like that.