Vince Knight

> It's up to you -- I don't mind running a cron job every night if there's interest. The main thing would be to make sure we're notified so that...

Cool. As you say, it's not exactly a problem if we're running the tournament more than once :) I was talking about updating the data here: https://zenodo.org/record/49557#.VxlIgFQrKkA It's a shame...

Cool :+1: I must have forgotten you already did it :) Refactoring sounds good. :+1:

FYI, I'm doing the fingerprints (both default and versus short run time) on the fingerprints repo but again that's (literally) taking weeks :)

After our chat today, I took another look and reminded myself about the issue and the manual step we had to use in 2017. I'd suggest you change this at...

> Another thought struck me: This affects the consistency optimisation, so it needs to be addressed here. The approach I'd suggest would be to always ensure a consistent order of...

FWIW, my suggestion would be the following workflow: Have a database of some sort with events and slots (outside of the scheduler, I'm guessing an sql database?). A script that...

> A code review should be done to assess whether some of the routines should be moved or refactored - in particular potentially useful general-purpose routines for converting to/from numpy...