Prepping for finals

[julskast]

Prepping for finals

[julskast]

@harikmenon @lidavidm @j-clap Let me know if this sounds good and if I'm missing anything. Happy to chat through it too.

[Janzert]

With the current architecture submissions need to be closed during the whole finals. It will also require some changes to reopen them just for challenges afterward but it shouldn't be too extensive.

The schedule set on https://halite.io/learn-programming-challenge/contest-rules/ has said 6 full days of games with some ambiguity when the games would stop on the 7th day.

At midnight on January 22nd, we will close submissions and let the final bots play each other for the last week of January. We will announce final winners on January 29th based on the final scores at that point in time and will freeze scores.

3 days might be doable but will probably be tight.

There are a few more steps needed to start the finals, some comments in PR #355 listed a few things. I need to dig out the checklist from last year to make sure there aren't other steps I'm forgetting as well.

[julskast]

@Janzert Thanks for pointing out those rules (which I wrote but just forgot!) Better to follow the original schedule. I knew I didn't want to announce anything on a weekend, so I guess I chose to do Monday instead of Friday.

I'll adjust the above schedule

[Janzert]

Here's a detailed checklist for switching the servers over to running the finals. I can certainly encode the raw sql queries into scripts if desired

• Close submissions
  • First set COMPETITION_OPEN = False in config.py
  • Then restart all coordinators and public api servers
• Wait for all last minute submissions to finish compiling.
  • The query select * from bot where compile_status in ('Uploaded', 'InProgress'); will return any bots still compiling.
• Stop all coordinators.
• Not required but now would be a good time to run a database backup.
  • This will be the final state of the database for the open competition.
• Get the id of the last game played and record it as the last open game.
  • Query select max(id) from game;
  • Set LAST_OPEN_GAME to that id in config.py
• Enable finals pairing
  • Set COMPETITION_FINALS_PAIRING = True in config.py
• Run rating reset
  • from halite/apiserver directory python -m apiserver.scripts.rating_reset
  • that will do a test run and rollback the transaction
  • to commit the reset add --execute option to the end.
• Verify rating reset was successful
  • The leaderboard should show everyone at 0 rating and with mu=25 and sigma=8.333
  • The bot history of each user should show their most recently retired bot as having just been retired with the rating and rank information being their finish in the open competition.
• Restart all public api servers
  • So they pick up the config.py changes.
• Start coordinators back up.
• Congratulations the finals are now running.

[julskast]

1. Nav banners.

Bot submissions close on January 22nd, 11:59 PM ET. Check out the plan for finals.

Submissions for the 2017-2018 are closed. Check out the finals in progress.

The 2017-2018 season has ended. Check out this year's winners!

[julskast]

Play page update:

<div data-v-8c5003f2="" class="panel-body text-center"><h2 data-v-8c5003f2="">SUBMISSIONS HAVE CLOSED</h2> <p data-v-8c5003f2="" style="text-align: center;">The 2017-2018 season of Halite has ended. But you can still<a data-v-8c5003f2="" href="https://api.halite.io/v1/login/github"> sign up </a>to join our newsletter to be the first to know about future competitions.</p></div>

[julskast]

Send challenge modal:
<div data-v-48c46ce0="" class="send-challenge-form"><img data-v-48c46ce0="" src="/assets/images/icon-group.svg" class="ico"> <h2 data-v-48c46ce0="" class="heading">CHALLENGE OTHER PLAYERS</h2> <p data-v-48c46ce0="">The 2017-2018 season of Halite has ended. You can no longer challenge a player through our website. But you can always play Halite locally - read <a href="/learn-programming-challenge/halite-cli-and-tools/">our documentation</a> to learn more.</p> </div>

[julskast]

Account page with hidden fields: