BriceJohnson wrote:
I don't believe we can necessarily go backwards in terms of undoing the changes we did to the computers/AX Ware (we need the new classes/update PAX indices), but we will get it fixed. Sometimes these bugs are the cost of progress, lets give THSCCIT a chance to work it out. They seem to be making changes for the better.
Firstly, let me state I am not an AXware expert, in fact I barely know how to use it, and most of my experience has come from clicking on things and seeing what they do.

That said, the issues with registration/class errors and runs not showing up are strictly AXware issues, and should have nothing to do with with the new laptop, new OS, or any of the file sharing changes we've made. That's akin to parking your car in a different garage and the engine stops working, thinking the garage caused it.

It's unlikely that the new version of AXware has bugs in it, but it is possible. Do we have a support contract with them, i.e. could we call them for tech support? The new PAX indexes should be unrelated as well.
I'd like to get a hold of the laptops soon to work on some of this. Mary, can you bring them to the meeting on Wednesday? Also, I'd love to have a pow-wow with the resident AXware expert. Would that be Stephen W., or someone else/additional?
The new class results report sucks, and we should definitely go back to the old style. Maybe the old report is available in some other menu? Must experiment more there...
Gwen Baake wrote:
I talked with Matt a little yesterday about the course. It was a blast to drive, but a quick count of over 380 cone calls...not counting DNFs that usually involve cones, is probably a little high. The biggest, and most simple fix to that course would have been to "flip" the C-box. I assume the box was put there to encourage drivers to slow down after what was a pretty long "peddle to the metal" section. The problem is that we mere mortals always think that we can squeeze through that last element and nail the finish. ('Cause we're silly and want to defy physics.) So, we always need to look at a safe exit to that type of element, realizing that drivers are going to break late, etc. Flipping the box would have pointed cars away from the center of the runway and into to grass. When designing courses it's always a good idea to point cars away from each other in areas where the cars are most unsettled.
I do apologize for the dangerous situation created by the C-box, and the subsequent overlap delay required to make it safe. Designing courses is definitely a work in progress at least for me, and I welcome any and all suggestions/criticisms. Gwen had an EXCELLENT point with flipping the C-box, that would have been perfect! Now as for the high number of cones, what exactly caused that, do you think? Too tight of a course? Were there particular elements that were hit a lot?
Let me also say thanks for the encouragement and kind words said about the course, I think it came out pretty good considering it was my second one. Much kudos to Marcus, Matt, and James for their help setting it up. But as you'd expect, I am of course looking back now at the many ways it could be improved (just like my driving...)!
_________________
2015-2017 President
2014 Track VP
2013 Autox VP
2002 Subaru WRX [dd]
2002 Honda S2000 STR #3 (retired...for now)
1992 Acura Integra ChumpCar #118 (retired)
2004 Toyota 4Runner V8http://beastmoderacing.com