search

brata-hsdc / brata.masterserver

Behind-the-scenes coordination and support for the HSDC
Apache License 2.0
1 stars 0 forks source link

Provide Game Over Control #49

Open jawaad-ahmad opened 8 years ago

jawaad-ahmad commented 8 years ago

Scoring (Issue #19) will need to know the time at which the event concluded in order to "stop the clock". This was discussed with @ellerychan either last week or the week before.

Issue #19 added an EVENT_CONCLUDED_MSG_TYPE to the piservice models and is using it currently.

This issue is to provide the MS Operator with a control that will post this event into the database exactly once--no need for this to be per station, per user, etc.

Also any operating procedures will need to be updated to mention navigating to and pressing this button at the conclusion of the challenge before scoring is retrieved.

ellerychan commented 8 years ago

Do we also need a marker at the start of the competition? Seems like it might be a good idea, in case there are spurious events caused either by people wandering around scanning QR codes indiscriminantly, or from any setup testing. We can either insert a marker event or delete all the stored events. I think we should be able to do either or both.

jawaad-ahmad commented 8 years ago

Good idea.

Deleting would be simpler and quicker to implement. Plus logic such as the Issue #19 pseudo-code already takes this into account; accounting for the new starting marker won't be difficult, but it will be another change.

If we choose deleting events, the GUI should have sufficient guarding to prevent the operator from accidentally invoking this. Should there be protection to only let this happen one time? Once the games have begun, that's it.

ellerychan commented 8 years ago

Delivered in Pull Request #62