Trackinfo: /* Lanes */

2026-10-10T23:56:59Z

Lanes

← Older revision		Revision as of 23:56, 10 October 2026
Line 123:		Line 123:
	The number should represent the actual capacity used for that round, not necessarily the total physical lanes at the venue.		The number should represent the actual capacity used for that round, not necessarily the total physical lanes at the venue.

	For example, a nine-lane facility may intentionally use only eight lanes in a particular championship round.		For example, a nine-lane facility may intentionally use only eight lanes in a particular championship round. If you are running a distance with waterfall starts and multiple alleys, you might even put a few dozen.

	== To next/final ==		== To next/final ==

Trackinfo at 22:23, 9 September 2026

2026-09-09T22:23:11Z

← Older revision		Revision as of 22:23, 9 September 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Rounds}}		{{DISPLAYTITLE:Rounds}}

	The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built.		The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built. If you don't have rounds, you shouldn't see this page.

	It operates at the '''GDE''' level — Gender, Division, Event — so different divisions or genders in the same event may use different round structures when necessary.		It operates at the '''GDE''' level — Gender, Division, Event — so different divisions or genders in the same event may use different round structures when necessary to pare down to a final.

	~~The~~ page also ~~records~~ anticipated participant counts ~~used~~ to calculate heats and advancement.		Before you have any entrants, the page also allows you to place anticipated participant counts so you can make the plan to calculate heats and advancement.

	== Who should use this page? ==		== Who should use this page? ==

Trackinfo: /* See also */

2026-08-07T10:20:08Z

Trackinfo: Created page with "{{DISPLAYTITLE:Rounds}} The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built. It operates at the '''GDE''' level — Gender, Division, Event — so different divisions or genders in the same event may use different round structures when necessary. The page also records anticipated participant counts used to calculate heats and advancement. == Who should use this page? == Use the Rounds page when a meet requires mo..."

2026-08-07T09:40:15Z

Created page with "{{DISPLAYTITLE:Rounds}} The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built. It operates at the '''GDE''' level — Gender, Division, Event — so different divisions or genders in the same event may use different round structures when necessary. The page also records anticipated participant counts used to calculate heats and advancement. == Who should use this page? == Use the Rounds page when a meet requires mo..."

New page

{{DISPLAYTITLE:Rounds}}

The '''Rounds''' page defines how athletes advance through qualifying rounds before the schedule is built.

It operates at the '''GDE''' level — Gender, Division, Event — so different divisions or genders in the same event may use different round structures when necessary.

The page also records anticipated participant counts used to calculate heats and advancement.

== Who should use this page? ==

Use the Rounds page when a meet requires more detailed advancement planning than can be handled by the simplified [[Participants]] page.

This may include:

* Preliminary rounds
* Quarterfinals
* Semifinals
* Finals
* Different advancement patterns by division
* Field-event qualifying rounds
* Large championship meets
* Combined-event traveling groups

A meet that conducts every event as a single final may need very little work on this page.

== GDE round planning ==

Each row represents one Gender/Division/Event combination.

For example:

* 100 — Girls — 11–12
* 100 — Boys — 11–12
* Long Jump — Girls — 13–14

This allows the Meet Director to configure each competition group independently.

Rows are identified as:

* '''Track'''
* '''Field'''
* '''Combined'''

The available controls differ by type.

== Entries ==

Enter the anticipated number of athletes for the row.

These anticipated numbers are used to estimate the number of heats and the size of later rounds.

They are planning values and may later be replaced by actual entries.

== Track-event round planning ==

Track rows allow one through four rounds.

Current choices are:

* '''1 Final'''
* '''2 Prelim/Final'''
* '''3 Prelim/Semi/Final'''
* '''4 rounds'''

== 1 Final ==

The event is conducted as a single round.

There is no advancement calculation.

== 2 Prelim/Final ==

Athletes compete in preliminary heats and qualifying athletes advance directly to the final.

The principal settings are:

* Entries
* Lanes
* To next/final
* Q per heat

Torunit calculates the remaining lowercase '''q''' qualifiers.

== 3 Prelim/Semi/Final ==

Athletes advance:

# Preliminary round
# Semifinal
# Final

Additional semifinal controls appear.

These include:

* Semi → Final target
* Semi Q / heat

== 4 rounds ==

A four-round event adds an additional intermediate round.

The current page exposes:

* Preliminary
* Quarterfinal
* Semifinal
* Final

Additional controls include:

* Quarter → Semi target
* Quarter Q / heat
* Semi → Final target
* Semi Q / heat

== Lanes ==

Enter the usable lane or heat capacity for that GDE.

Torunit uses this number to calculate the number of heats.

The number should represent the actual capacity used for that round, not necessarily the total physical lanes at the venue.

For example, a nine-lane facility may intentionally use only eight lanes in a particular championship round.

== To next/final ==

Enter the total number of athletes who should advance from the current round.

In a two-round event this is the number advancing from preliminary heats to the final.

In a three- or four-round event it represents the target for the next stage.

Additional target fields appear for the later stages.

== Q — automatic qualifiers ==

Capital '''Q''' represents automatic qualification by finishing place.

Enter the number of automatic qualifiers from each heat.

Example:

<code>3 Q per heat</code>

means that the first three qualifying athletes from each heat advance automatically.

== q — time qualifiers ==

Lowercase '''q''' represents athletes who advance by time rather than by automatic place.

Torunit calculates the required number of lowercase q qualifiers from:

* Number of heats
* Q per heat
* Total advancement target

Example:

If there are three heats and:

<code>2 Q per heat</code>

then six athletes advance automatically.

If the target is eight qualifiers, Torunit calculates:

<code>2 q</code>

additional qualifiers by time.

== Advancement checker ==

Torunit checks the round mathematics as values are entered.

The checker can identify conditions such as:

* Trying to advance more athletes than entered the round
* Automatic Q places producing more qualifiers than the target
* Q per heat exceeding the number of lanes

When the values are valid, the row displays a summary describing:

* Number of heats
* Q per heat
* Number of lowercase q qualifiers

When the values are invalid, the row displays an error message.

Example:

<code>3 Q × 4 heats = 12 automatic qualifiers, but only 8 advance</code>

The advancement settings should be corrected before the meet schedule is considered complete.

== Quarterfinal settings ==

Four-round events expose a separate Quarterfinal advancement section.

=== Quarter → Semi target ===

Enter the number of athletes who should advance from the quarterfinal to the semifinal.

=== Quarter Q / heat ===

Enter the number of automatic qualifiers per quarterfinal heat.

Torunit then checks the advancement calculation for that stage.

== Semifinal settings ==

Three- and four-round events expose semifinal advancement controls.

=== Semi → Final target ===

Enter the number of athletes who should advance from the semifinal into the final.

=== Semi Q / heat ===

Enter the number of automatic qualifiers per semifinal heat.

Torunit checks the resulting automatic and time qualification totals.

== Field-event rounds ==

Field rows use a different competition model than track heats.

Current choices are:

* '''1 Final'''
* '''2 Qual/Final'''

=== 1 Final ===

All entered athletes proceed directly to the final competition.

=== 2 Qual/Final ===

A qualifying competition is conducted before the final.

The field-event row provides settings for:

* Anticipated entries
* Number qualifying to the final
* Number receiving the final three attempts
* Automatic qualifying mark

== Number qualifying to final ==

Enter the number of athletes who should advance from the qualifying round into the final competition.

This is the field-event equivalent of the advancement target.

== Number receiving final three attempts ==

Enter the number of athletes who should receive the final three attempts.

This may differ from the total number initially advancing into the final competition depending on the meet's field-event format.

== Field Q mark ==

Enter an automatic qualifying mark when the competition uses one.

An athlete achieving the automatic Q mark qualifies according to the meet's field-event advancement rules.

The mark should be entered using the format expected by Torunit for that event.

== Combined events ==

Combined-event rows are treated differently from ordinary track and field rows.

A combined-event row records a single anticipated participant count.

The athletes remain together through the chain of component disciplines.

The separate rounds columns are therefore not used in the same way as ordinary track or field events.

== Traveling groups ==

Combined-event divisions may be organized into '''Traveling Groups'''.

A traveling group allows multiple combined-event GDEs to move through the component facilities together.

This is useful when several small combined-event divisions can share the same sequence of stations.

The current design aims for groups near approximately 16 athletes per shared station.

=== Form Traveling Group ===

Check two or more combined-event rows and select:

'''＋ Form Traveling Group'''

Torunit assigns those rows to a common traveling group.

Each group is identified by a color and a label such as:

* Group A
* Group B
* Group C

A summary displays:

* Number of GDEs in the group
* Total anticipated athletes
* Relationship to the approximate 16-athlete target

=== Group size guidance ===

The current interface provides guidance such as:

* '''room to add more'''
* '''good — near target'''
* '''over 16 → engine splits into flights'''

This is planning guidance rather than a competition rule.

=== Add another row to an existing group ===

If the checked rows contain exactly one existing traveling group, newly selected combined-event rows are added to that group.

=== Ungroup Checked ===

Select combined-event rows and choose '''Ungroup Checked''' to remove them from their traveling groups.

=== Release one division ===

A row may also be removed individually from its traveling group using the × next to the group badge.

== Row selection ==

Each GDE row contains a checkbox.

The checkboxes are used by the bulk-copy and traveling-group tools.

Shift-click may be used to select a continuous range of rows.

== Copy checked row to same event ==

Check exactly one source row.

Select:

'''Copy checked row to same event'''

Torunit copies the source settings to the other GDE rows for that same event.

This is useful when several divisions should use identical round rules.

== Copy first checked to checked ==

Check two or more rows.

The first checked row becomes the source.

Select:

'''Copy first checked to checked'''

Torunit copies its settings to the remaining selected rows.

This allows the same structure to be applied to unrelated events or divisions.

== Select Same Event ==

Check one row and select:

'''Select Same Event'''

Torunit selects all rows belonging to the same event.

This is useful before applying a bulk operation.

== Clear Checks ==

Clears the row-selection checkboxes.

It does not intentionally clear the round plan.

== Clear Round Entries ==

Clears the round-planning values on the page after confirmation.

Use this carefully.

The current implementation resets round counts and several default values and clears other row inputs.

Because this action autosaves, the cleared values become the current round plan.

== Min/heat ==

The '''Min/heat''' setting establishes the scheduling gap associated with round heats.

The current default is:

<code>4 minutes</code>

The field accepts quarter-minute increments.

For example:

<code>0.25</code>

represents 15 seconds.

This allows high-volume sprint meets to use smaller per-heat timing increments when necessary.

This value concerns schedule timing rather than qualification mathematics.

== Save Round Plan ==

Select '''Save Round Plan''' to save the current configuration immediately.

The status area may display:

* Unsaved changes...
* Saving...
* Saved ✓
* Save error

== Autosave ==

Changes to GDE rows automatically schedule a save after a short delay.

The following actions also trigger autosave:

* Editing anticipated entries
* Changing round settings
* Changing advancement settings
* Changing the Min/heat value
* Creating or removing traveling groups
* Bulk-copy operations
* Clearing round entries

A manual Save Round Plan button remains available.

== Sort ==

The rows may be reorganized without changing their underlying round settings.

Available sort orders are:

* '''Event → Gender → Division'''
* '''Gender → Event → Division'''
* '''Division → Event → Gender'''

Sorting is a viewing tool. It does not change the event or division identity of a row.

== Top / Return ==

Because the Rounds page can be long, the toolbar contains an '''↑ Top''' button.

Selecting it returns to the top of the page.

The button then changes to:

'''↩ Return'''

Selecting Return restores the previous scroll position.

== Relationship to scheduling ==

The Rounds page tells Torunit how many competition stages must exist before the schedule is constructed.

Its settings influence:

* Number of heats
* Number of rounds
* Size of later rounds
* Qualification structure
* Timing requirements
* Combined-event grouping

The schedule should not invent a different advancement plan.

The Meet Director's explicit round decisions should remain authoritative.

== Current implementation notes ==

The following items should be reviewed as Torunit development continues:

* The page correctly detects invalid track advancement mathematics and marks the row invalid, but the current save function does not appear to block an invalid row from being saved. Invalid round plans should not silently become authoritative.
* Verify whether invalid rows should block only their own save or the entire Round Plan save.
* Verify field-event automatic Q-mark entry format and downstream interpretation.
* Verify the intended distinction between “number qualifying to final” and “number receiving final three attempts” for all supported field-event formats.
* '''Clear Round Entries''' currently clears substantially more than just the number of rounds. Confirm that it is intended to clear anticipated counts, field Q marks, field finalist values, and traveling-group information as well.
* Confirm that the approximate 16-athlete target for combined-event traveling groups remains the desired operational rule.
* The full Rounds page and the simplified rounds controls on [[Participants]] should remain coordinated so they cannot establish contradictory sources of truth.

== See also ==

* [[Participants]]
* [[Create Meet]]
* [[Venue]]
* [[Schedule]]
* [[Macro Scheduler]]
* [[Combined Events]]

[[Category:Meet Director]]
[[Category:Rounds]]
[[Category:Schedule]]
[[Category:Meet planning]]

← Older revision		Revision as of 10:20, 7 August 2026
Line 492:		Line 492:

	* [[Participants]]		* [[Participants]]
	* [[Create Meet]]		* [[Create-Meet]]
	* [[Venue]]		* [[Venue]]
	* [[Schedule]]		* [[Schedule]]

Rounds - Revision history

Trackinfo: /* Lanes */

Trackinfo at 22:23, 9 September 2026

Trackinfo: /* See also */