Discussion: Boggs Mountain A-Meet Courses on RouteGadget

All Boggs Mountain A-Meet courses (Long & Middle) are now available on RouteGadget. Visit http://baoc.org/wiki/RouteGadget for introduction or go directly to http://baoc.org/gadget/cgi/reitti.cgi to draw your route.

To see other RouteGadget events worldwide, visit http://www.routegadget.net

Happy Routes,
Tapio

There's still no word on what transpired to cause the Red course on Saturday to be voided (I wasn't there). Looking at WinSplits, Sharon Crawford, perhaps the most technically capable person on Red, had problems with Controls 6 and 15; other people also had problems with these, which leads me to hypothesize the issue lay with one of these two. Both of these locations were used in prior years; and both were used on Blue that day, which was not protested nor thrown out, nor did Blue runners seem to have undue trouble with these controls...

Two controls were switched. E.g., control #XYZ was at point 10, it should have been at point 13, and vice versa (or that was the case on blue, I think red just had one control that was wrong. They were juxtaposed on blue.)

There was a protest, which was upheld, on Red, but none on Blue, so those results stand.

The problem was with control 9. It had the wrong control number. It was listed as 114, but was actually 117. (I may have that backwards.) Both 114 and 117 were on the Blue course, and on the Blue course were very far apart, and not consecutive controls. No one protested on the Blue course, because Blue runners apparently immediately recognized that the control numbers were just switched. But only one of the two numbers was on the Red course. Some runners on Red found the correct control location, saw the control number, believed they found the wrong control, and then spent varying amounts of time hunting for a non-existent control. Some probably did not notice the control number was wrong, and punched and moved on. Some may have been confident that the number was wrong, and punched and moved on. I understand that the pre-runner spotted the problem, but I heard was not able to return in time to get it fixed before the first real starter, and so it was not fixed on the course, so everyone had the same condition on the course. Earlier runners knew nothing about it. Word spread in dribs in drabs. Before about halfway through the start window, people had heard there was something wrong with control numbers on Red. By the time I started, I had heard specifically that 114 and 117 were switched. So people were competing with different states of knowledge. By the time I returned (which as usual was very, very late), one or more early runners had already protested (not sure who), and the jury had assembled. Jury made right decision seems to me. There was no way to sort it out. There was both a physical problem that affected results, and there were different states of knowledge with competitors. Good courses, well-designed and well-set, except for this one thing. It's a bummer how one little thing can affect so much good work. There was a lot of good work, and stuff happens.

Sharon was one of the last starters and made the correction on her clue sheet. Thus, the incorrect control number did not affect her.

Routes finally posted. Thanks for a fun event!