·
Hi John,
Thanks for sharing this! I explored the case in GroupMixer, and it highlights an interesting gap in what we currently support.
We can model the 18 players, four rounds, mixed group sizes, pair-repeat restrictions, and the requirement that each player plays in a foursome two or three times. We can also penalize repeated visits to the same tee slot, which, with everyone attending all four rounds, maximizes the total number of distinct slots experienced.
However, we don’t currently have a constraint for “each person must visit at least N different groups,” or an objective that maximizes the minimum individual variety before maximizing the total. So we can’t express your exact benchmark objective.
In exploratory runs of the closely related total-variety model, I found this schedule:
Minimum 2, total 66 in a 5-second run:
http://groupmixer.app/share#gm=br3.G5YJACwK7HZgO8VeTJSxlnsZFA1GSDI7eHPfX3EDjYa9SxhQmBUF-Am-Rxj8v85fEAYjjr4j79u1MxrFglJLTV0o4gdYITq5iT-Nlnc823mVjLM1S19Xx9Rh6fv_93OLGx6KtUq0GHZt8uwjbnF2EUv89uMWM0tEMiV44lAbWT2OG8J8pyunyCNflNb5gr9o-QHGjXhgiALc6G0Pt8PG1_Pquqw_vuoHOjxYQglv4FMMuG9edpkhlX_7fmeXV3epBoa3zfcfG-6HW778ELQzSdeg3RyCC8QuZzvxKPCBKnOIvpwHrMFRoRuJ0NYY4Mz-Plop8AHjaWjBbihVnl59IU5FiiGAkWBenE1CXAXHllv6eE-LtSbdy1ovsCbp38qH3OvRYOXPnNoIu7vHfkJZ7DBLO_R0uHVoaepwloasK2KN9rHlzQ55rcLoJAqQbTma-yP8rEunCm-8p3Gfr0OrX0egIU2YbE6o9j37fxvskyKbXNdefcYVuDInKQpXaU_apveOcTicErtKWVNuB0_FO_PvcompL04BRY7ggmoSz_OAuYu8pdqHDqfVIt58n05H1xHuqBnWrt5c7AxxRbrIELNKqd-mmWioxNm3RcgzQFPjJoT5R8TeQGRbBpDoOdzGLFkLkVq1lOiySdum02xjgwibOm9CuniGs3UMtWIItEnR19j_zDTb4awKoYL_UKp2-l4zP_DUkL02lmoIjA-L9KgvVnLhDxhN-W6VOmPpLHgX40xjKJJe1cRc7wriqhzGhTY96eVEMgBcpGaTJUa90Rt47IjZWIyEHU_0rzH4xI4sm-WQJBwyh5NbSMv-IyzWtNxYe4wc8GzEIC_BgK7ImQbFWimArpzoB3L2KdZJd3ISEp8dcSHHT2SoMuakllwBg7YSY-zNNowsHUny1xJzDGQ8i5xGt0I6oEjV9XO7hCfnkD2qx4RizL1qohoMcRqsIcIPZlg_afZF6Z6aFaK2xJ1KDCGI2ZDvNwFnRNtZNtY5O0cExRgEQqGcBrUZe_tUuA85JHMlkMUNT5VLhIovQksi48R_U8So3D0bpaciZzWyXRlyWzcJkMkFBNOq-etJ5tz_aprP9rWul6m1ggaJNu_PzqZj5KzR_zl8K2f3uqAfXAc
It satisfies the group-size, pair-repeat, and foursome-frequency requirements. With the constraints in our model, this result is preferred over your perfect schedule because the total number of distinct tee slots is higher. According to your constraints, it is a worse schedule because one person only plays at two different tee slots.
Would support for this additional constraint type be interesting for you in practice, or is this mainly out of curiosity? Generally, OR-Tools will work fine for smaller instances like the one you presented, but for large instances, GroupMixers solver approach could produce much better results.
If we ever end up adding support for it, your example would indeed be a valuable benchmark.