To use it, enter the number of teams in each group in a division. "Generate" will automatically set up matches so that each team plays all the teams within its group, though it's simple to add or remove matches. It's easy to either intergroup games or single elimination games.
The output is saved automatically for the G&B Assign page, which is used to assign matches with game slots (time/location), but the 'match list' can be copied for use in a spreadsheet or other external scheduling tool.
A "Division" is made up of one or more groups, A-F, with two or more teams per group. A division name/ID is 'U<age><gender>' where age is 8-23, and gender is 'b' or 'g'. The division name/ID is not case sensitive so 'u18b', 'U18b', 'u18B', and 'U18B' are equivalent.
Within the Groups and Brackets software, each division can have a short and long name, so the U-name is not necessarily visible to the public. It is used if a short name is not specified. In tournaments in which the divisions are not age-specific, it's simple to map U-names to other names. For example, U19B can be mapped to 'Varsity' and U18B to 'JV'. 'U20B', 'U19B', and 'U18B' can be mapped to 'EPL', 'La Liga', and 'Bundesliga', or 'Bronze', 'Silver', and 'Gold'. However, this mapping is not set up in Generate Matches.
A group specification consists of a single letter, A-F, optionally followed by the group size, and optionally preceded by a ID number. The group size defaults to the last size specified, or 4 if none has been specified. Every team must be in a group, so if there is only one group in a division, 'A' is used. Examples:
U19B a4 b | Two 4-team groups, A & B |
U19B a4 b3 | A = 4-team group; B = 3-team group |
U19B a5 b | Two 5-team groups, A & B |
U19B A3 B3 C3 | Three 3-team groups, A, B, & C |
U19B a3 b c | Also Three 3-team groups, A, B and C |
U19B a11 | One 11-team group, A |
U19B a11 none | One 11-team group, A, with no matches scheduled |
u19b a4 b c d | Four 4-team groups, A,B,C,D with IDs 1-16 |
This dialog is used to specify the division and the groups within that division, as well as various options. The division is required even though it is not visible in most screen output.
This page looks best with a wide window.
A.1 | A.2 | A.3 | A.4 | ||
---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | 3,0 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | 2,1 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | 1,2 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | 0,3 | |
3 | 3 | 3 | 3 |
Each light green block represents the reverse of a scheduled match. For example, if 'A.1 v A.2' is scheduled, then 'A.2 v A.1' will be light green.
A single row will have the same team on the right side of the match/cell, while a single column will have the same team on the right side of the match/cell.
A.1 | A.2 | A.3 | A.4 | ||
---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | 2,1 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | 3,0 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | 0,2 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | 0,2 | |
3 | 3 | 2 | 2 |
Clicking a scheduled (dark-green) block, will unschedule it. In this grid, 'A.3-A.4' was clicked, so both it and its reverse are white. This indicates that neither A.3-A.4 or A.4-A.3 is scheduled.
A.1 | A.2 | A.3 | A.4 | ||
---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | 2,1 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | 2,0 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | 0,2 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | 0,1 | |
3 | 2 | 2 | 1 |
The last cell in a column shows the number of games that column's team is/will be scheduled to play. In this grid, A.1 is scheduled to play 3 matches, A.2 and A.3 are scheduled for 2 matches and A.4 is scheduled for 1 match.
The Match List is updated any time a change is made to the grid. It will change anytime that a cell is clicked. In many cases, reversing the team order, by clicking on a light green cell, will change the grouping in the match list.
The right list shows the matches after 'A.4-A.3', 'A.3-A.2', and 'A.3-A.1' have been scheduled, replacing 'A.3-A.4', 'A.2-A.3', and 'A.1-A.3'.
The '// 3' at the bottom of the list is the number of clusters. (Scroll)
"Numeric ID", "Group ID", and "Group Relative" are different ways of referring to teams, as shown below. Preceding a group specification with a number will set the ID of the first team in the group. Column and row headers always use group relative notation, but the rest of the cells and the match list will use the specified notation.
The "Split Home/Away" option will balance the number of matches that a team is on the left or right side of a match, assuming a convention that the order of the teams determines which team is "Home". This option is set in the following examples, though there are many ways of balancing this.
The "Prepend Division" option will insert the division ID into the match list. This option is set for the "Group Relative" notation because it is necessary to uniquely identify a specific team if there are more than one division in the tournament. It is not necessary to set this if "Gen Slots" and "Assign" are used to complete tournament construction, because the division information is retained between the pages.
An earlier version of gen_matches allowed team IDs to be set within the parameter spec. These are currently set in the "Teams" section of TD Builder. It's simplest to stick with Group Relative.
A.1 | A.2 | A.3 | A.4 | ||
---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | 2,1 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | 1,2 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | 2,1 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | 1,2 | |
3 | 3 | 3 | 3 |
A.1 | A.2 | A.3 | B.1 | B.2 | B.3 | ||
---|---|---|---|---|---|---|---|
A.1 | 11-12 | 11-13 | 11-21 | 11-22 | 11-23 | 1,1 | |
A.2 | 12-11 | 12-13 | 12-21 | 12-22 | 12-23 | 1,1 | |
A.3 | 13-11 | 13-12 | 13-21 | 13-22 | 13-23 | 1,1 | |
B.1 | 21-11 | 21-12 | 21-13 | 21-22 | 21-23 | 1,1 | |
B.2 | 22-11 | 22-12 | 22-13 | 22-21 | 22-23 | 1,1 | |
B.3 | 23-11 | 23-12 | 23-13 | 23-21 | 23-22 | 1,1 | |
2 | 2 | 2 | 2 | 2 | 2 |
A.1 | A.2 | A.3 | A.4 | A.5 | ||
---|---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | A.1-A.5 | 1,1 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | A.2-A.5 | 1,1 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | A.3-A.5 | 1,1 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | A.4-A.5 | 1,1 | |
A.5 | A.5-A.1 | A.5-A.2 | A.5-A.3 | A.5-A.4 | 1,1 | |
2 | 2 | 2 | 2 | 2 |
This is a 5 team group in which each team plays two other teams. A.1 plays A.2 and A.5, A.2 plays A.1 and A.3, A.3 plays A.2, A.4 plays A.3 and A.5, and A5 plays A.4 and A.1. The schedule started out as an empty schedule, with the games added manually.
A.1 | A.2 | A.3 | A.4 | A.5 | A.6 | ||
---|---|---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | A.1-A.5 | A.1-A.6 | 3,1 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | A.2-A.5 | A.2-A.6 | 3,1 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | A.3-A.5 | A.3-A.6 | 3,1 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | A.4-A.5 | A.4-A.6 | 2,2 | |
A.5 | A.5-A.1 | A.5-A.2 | A.5-A.3 | A.5-A.4 | A.5-A.6 | 0,4 | |
A.6 | A.6-A.1 | A.6-A.2 | A.6-A.3 | A.6-A.4 | A.6-A.5 | 1,3 | |
4 | 4 | 4 | 4 | 4 | 4 |
This is a 6 team group in which each team plays four other teams. 'U18B load' was used to show the matches based on a schedule already in "Groups and Brackets" form. These matches were played in a 2013 Birmingham tournament.
If 'Numeric ID' or 'Group ID' are specified, the actual event IDs are displayed.
A.1 | A.2 | A.3 | A.4 | B.1 | B.2 | B.3 | ||
---|---|---|---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.4 | A-1:B-1 | A-1:B-2 | A-1:B-3 | 1,1 | |
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.4 | A-2:B-1 | A-2:B-2 | A-2:B-3 | 1,2 | |
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.4 | A-3:B-1 | A-3:B-2 | A-3:B-3 | 1,2 | |
A.4 | A.4-A.1 | A.4-A.2 | A.4-A.3 | A-4:B-1 | A-4:B-2 | A-4:B-3 | 2,1 | |
B.1 | B-1:A-1 | B-1:A-2 | B-1:A-3 | B-1:A-4 | B.1-B.2 | B.1-B.3 | 2,1 | |
B.2 | B-2:A-1 | B-2:A-2 | B-2:A-3 | B-2:A-4 | B.2-B.1 | B.2-B.3 | 2,1 | |
B.3 | B-3:A-1 | B-3:A-2 | B-3:A-3 | B-3:A-4 | B.3-B.1 | B.3-B.2 | 1,2 | |
2 | 3 | 3 | 3 | 3 | 3 | 3 |
A-4 and B-3, the last place teams in their groups, played in a consolation game, while A-3 and B-2 played in a wildcard game. The winner of the wild card game played in a semifinal game against the winner of group A, A-1. B-1 and A-2 played in the other semifinal, with the semifinal winners meeting in the final. All games other than the final and the 'A-1 v WC' game are shown as matches in the grid.
A.1 | A.2 | A.3 | A.1 | A.2 | A.3 | ||
---|---|---|---|---|---|---|---|
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.2 | A.1-A.3 | 2,2 | ||
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.1 | A.2-A.3 | 2,2 | ||
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.1 | A.3-A.2 | 2,2 | ||
A.1 | A.1-A.2 | A.1-A.3 | A.1-A.2 | A.1-A.3 | 2,2 | ||
A.2 | A.2-A.1 | A.2-A.3 | A.2-A.1 | A.2-A.3 | 2,2 | ||
A.3 | A.3-A.1 | A.3-A.2 | A.3-A.1 | A.3-A.2 | 2,2 | ||
4 | 4 | 4 | 4 | 4 | 4 |
gen_matches partially supports this configuration. 'U10B A3 A3' was used for this grid and the matches are generated correctly. However swapping scheduled and reverse games, and other scheduling functions are not completely functional.
U19G A5 will generate a list with 4 clusters of 2 matches and 2 clusters with a single match. The last two matches in the list both include 'A.4' so they can't be scheduled together. However, this one has an easy workaround. Setting the Split Home/Away option will generate a match list with 5 clusters of 2 games.
U19G A6 without the Split Home/Away option will generate a match list with a single 3-match cluster and 6 2-match clusters. With Split Home/Away set, U19G A6 will generate with three 3 game clusters and 3 2-match clusters without the Split Home/Away option set. Clicking 'A.2-A.1' (2nd row, 1st column) will reduce that to five 3-match clusters, which is the minimum.
If an
A7 spec is used, with Split Home/Away set, 9 clusters are generated (6 x 3, 3 x 1) .
It's unlikely that any tournament will use a 7 team group in which each team plays
every other in the group, but there is a simple remedy.
Turning off 'Split Home/Away' will generate a match list with 7 clusters of 3 matches,
the minimum.
(
A7 w Home/Away off )
The Match List is updated when a saved match set is loaded, and it can be copied to a spreadsheet for external use, or the match information can be used directly by the 'assign' page. See the gen_tourn_info page to see how gen_matches fits in with other pages to build a tournament.
'Reset' will clear any saved values.
The best way to learn how the Gen Matches page works is to experiment. Please send comments, suggestions, and questions to Tom Konantz