Poorly Run Event Stories

[dxu46]

I actually haven't seen any of the events I'm going to describe, but my friends' attitudes can say something.
Thermo - Apparently the ES didn't time the temperature things, so when a device reached its prediction teams could just fake it and say x minutes elapsed.
Disease - same test as last year
Experimental Design - college students who (apparently) look completely clueless, don't know much about event
Solar System - tested non-rules topics
Crime Busters - not sure what my friend said, but it was not good
Chem Lab - kind of oblivious ES

Definitely more - If anyone lives in neighboring states and is a grad, MO needs some serious help.

[knightmoves]

Ok, so MO states was today and my first event was CodeBusters. We got to the room at like 8:50 (first event starts at 9), but THE ES DIDN'T COME UNTIL FIFTEEN MINUTES LATER. So it was around 9:15 when the test started. AND THEY ENDED THE TEST AT 10!!!!!! The test was sooo super easy, but we only got 45 minutes to do the test, but had we had the remaining 5 minutes, I could've finished that 700 point hill cipher that I was working on.

Once the ES showed up late, the best thing to do is to finish on time, and then give the same time to the teams in the other slots. Giving everyone 45 minutes (or even 40 minutes) to do the test is the least bad thing you can do at that point. Having one event running late messes up everyone's schedule (as you discovered).

[linzhiyan]

Ok, so MO states was today and my first event was CodeBusters. We got to the room at like 8:50 (first event starts at 9), but THE ES DIDN'T COME UNTIL FIFTEEN MINUTES LATER. So it was around 9:15 when the test started. AND THEY ENDED THE TEST AT 10!!!!!! The test was sooo super easy, but we only got 45 minutes to do the test, but had we had the remaining 5 minutes, I could've finished that 700 point hill cipher that I was working on.

Once the ES showed up late, the best thing to do is to finish on time, and then give the same time to the teams in the other slots. Giving everyone 45 minutes (or even 40 minutes) to do the test is the least bad thing you can do at that point. Having one event running late messes up everyone's schedule (as you discovered).

Nono, everyone else got fifty minutes... it was just the first group that got 45... -_-

[knightmoves]

Nono, everyone else got fifty minutes... it was just the first group that got 45... -_-

[TheChiScientist]

Definitely more - If anyone lives in neighboring states and is a grad, MO needs some serious help.

Where is MO states even held? If it's near the IL border I could possibly help out...

[dxu46]

Definitely more - If anyone lives in neighboring states and is a grad, MO needs some serious help.

Where is MO states even held? If it's near the IL border I could possibly help out...

It's in the middle of Missouri, south of Columbia. If you could help, that'd be great.

[jaspattack]

Fossils at MO states was super weird too. The proctor didn't care about it at all and even though the event was run as stations, people were just going wherever they wanted. She also gave us 15 extra minutes for some reason, even though the event started on time. It wasn't like, awful, but it was just weird. All my other events were cool though.

[farmerjoe279]

In MO Thermo, one of the students had to help the judge proctor because he didn't know how to proctor the event properly. You had to scoop hot water using the same beaker you put in your thermo box with you hands (press F for burned fingers and hands).

[Frost0125]

This was at NC states, in an Nc- only event called Amazing Mech. In this event, there are two 25 parts. The first part is stations in which we troubleshoot circuits built with an Arduino Uno on a program called Tinker Circuits. Second part, we have a list of 20-25 circuits. All are worth the same amount of points. The goal is to build as many circuits as possible on Tinker Circuits with the time given.

1) The room number we were given didn’t exist, so we had to find the new room
2) not enough chairs so half of us were kneeling on the floor
3) They lost the paper of circuits for the second half of the event. They ended up having to project 14 out of 25 questions on the board. We only had access to these 14 questions the entire time.
4) we only got 15 mins for the second half versus the 25 we were supposed to get
5) They lost the password to the SO tinker circuits account, so we all had to use our personal ones. Thankfully no one cheated that I knew of
6) When we complete a circuit in the second half the supervisor initial and put how much time we have left when we completed the circuit. They put the actual time. This nullified the tiebreaker, which was who completed the first circuit first.

So that was a fun event, but we tried our best.

[linzhiyan]

Nono, everyone else got fifty minutes... it was just the first group that got 45... -_-

AHHHHHHH WE GOT SEVENTH WITH THE FIVE MINUTES CUT OFF. With the extra 5 minutes, we probably could have medalled ahhhhhhhh ksdhfgsdjhgvfmndsbfdasj