Atropine 1.2.3

Discussion and announcements relating to unofficial Countdown competitions, held online or in real life. Observation, discussion, reflection, and other stuff ending in -ion.
Post Reply
User avatar
Graeme Cole
Series 65 Champion
Posts: 2054
Joined: Tue Jul 06, 2010 9:59 pm

Atropine 1.2.3

Post by Graeme Cole »

If you're involved in the running of co-events, this is likely to be of interest to you. If you aren't, it's less likely.

Version 1.2.3 of everyone's favourite Python-based co-event administration tool is out now. It can be found at the usual place: https://greem.uk/atropine/

New features since last year's version 1.2.2 include:
  • Display options profiles. Don't like that the name-to-table-index supplants the traditional fixture display when there are 36 or more players? Fed up with having to switch that off in every tourney you run? Now you can save all the display options to a named profile visible to every tourney in your Atropine installation. When you create a new tourney, you can select the profile you want.
  • Newbies. Quite a few events now ensure every table has at least one non-newbie in the first round, even if it's random in every other respect. But you no longer need to implement this by repeatedly generating new fixtures until you get a set that works - just mark the relevant players as newbies and the Random Fixture Generator will do the rest.
  • Variations on the Swiss fixture generator. The Swiss fixture generator page now has a couple more options on it, as a result of the Co-event suggestion box thread and general popular demand elsewhere.
    • One is a checkbox which will cause the generator to match players only on their win counts rather than their standings position. After that it's random. This is the "Draw Against Someone On The Same Number Of Wins" method. As always, this is subject to other constraints such as avoiding rematches. A couple of predictable questions about details are answered here.
    • The other is a drop-down box to specify whether to consider all previous rounds (the default) or only the most recent round. This implements the so-called "Pot Draw" method.
    • These are both off by default. If you ignore them you'll still get the classic "draw against someone near me in the standings table" method.
  • Other miscellaneous improvements:
    • When a fixture generator presents you with a list of fixtures to accept, it also shows each player's win-loss record so you can more easily verify that the fixtures have been generated how you wanted.
    • Some small performance and interface improvements.
    • Atropine no longer relies on the deprecated "cgi" module, scheduled for removal in Python 3.13. For this reason, if you're still using Atropine 1.2.2 or earlier, eventually that will stop working for you when you upgrade your Python installation.
If anyone finds any major issues with it then let me know. Such problems will be fixed in a swift 1.2.4 release if necessary.

Account management on the co-event live broadcast thing

This is about the thing without a satisfactory name whereby Atropine can upload score updates for an event to a page on greem.uk (recent example).

Some of you - mostly co-event organisers - have accounts for this sometimes-used feature. You can now manage that account at https://greem.uk/coliveadmin. This allows you to see all your tourneys, make them public or private, and change your password, without having to run Atropine.

If you're involved in organising or running co-events and you want an account to use Atropine's live broadcast updates thing, you can ask me and I'll give you a magic link that creates your account and allows you to choose a password. This also applies if you have an account but you've forgotten your password - I can now generate you a link to reset it.
JackHurst
Series 63 Champion
Posts: 2049
Joined: Tue Jan 20, 2009 8:40 pm

Re: Atropine 1.2.3

Post by JackHurst »

Nice work Graeme!

Does this mean for a single tournament, it is now possible to upload results from separate machines?

Use case: You are at a Bristol style event with 2N players, and you want to minimize waiting time between rounds by having 2 (or more) people inputting results.
User avatar
Graeme Cole
Series 65 Champion
Posts: 2054
Joined: Tue Jul 06, 2010 9:59 pm

Re: Atropine 1.2.3

Post by Graeme Cole »

JackHurst wrote: Mon Apr 15, 2024 2:49 pm Nice work Graeme!

Does this mean for a single tournament, it is now possible to upload results from separate machines?

Use case: You are at a Bristol style event with 2N players, and you want to minimize waiting time between rounds by having 2 (or more) people inputting results.
No. The only change to the broadcast feature is that you can now manage your account on a web page.

The broadcast feature only transfers information from the laptop administering the tourney to the website, not the other way round. Every upload replaces the old tourney state with the new tourney state, so if you tried this with two people submitting to the same tourney online, you'd just keep overwriting each other's scores.
User avatar
Graeme Cole
Series 65 Champion
Posts: 2054
Joined: Tue Jul 06, 2010 9:59 pm

Re: Atropine 1.2.4

Post by Graeme Cole »

There's a new version of Atropine (1.2.4), with not enough changes to need its own new thread.

The only substantial change is to how the fixtures are displayed to everyone when they're announced. It used to show the name-to-table-number index, rather than the full fixture list, if there were 36 or more players. This made it easier to find your table, but on the other hand, it also concealed who's Player 1/Player 2 at a Bristol-style two-players-to-a-table event.

So, as of 1.2.4, the default behaviour (configurable in Display Setup) is to show the full fixture list if there are two players to a table, regardless of how many players there are.
Post Reply