Venue

The Venue page describes the physical facilities available to conduct the meet.

Venue settings tell Torunit how many competition areas are available, which facilities may operate simultaneously, which facilities interfere with one another, and how field events will be conducted.

These settings are particularly important when Torunit builds the meet schedule. A schedule cannot realistically place two events at the same time if both require the same physical space.

The Venue page may also contain maps and information about public or practice use of the facility.

Who should use this page?

Every Meet Director or designated assistants should review the Venue page.

The page will guide the staff for set up and all of the visitors at your meet where to go for the things they need, without them needing to bother you.

For a simple meet, only a small number of settings may need attention.

A larger meet may need detailed configuration of:

• Track lanes
• Multiple field-event facilities
• Throwing cages
• Facility conflicts
• Field-event competition format
• Venue maps
• Public and practice access

Creating a detailed interactive venue map is optional. See Interactive Map Designer.

Relationship to Create-Meet

The primary meet venue is initially identified on Create-Meet.

The Venue page describes the competition facilities available at that location in greater detail.

A meet may also use more than one physical location. For example:

• A stadium for track and field events
• A cross-country course
• A road-race course
• A separate race-walk course
• A throwing facility at another location

For ease of operation it will default to an outdoor track but you can select any other option or mix and match for multiple locations.

Saving

Venue settings are saved automatically.

There is no normal Save button that must be pressed after every change.

A status area at the bottom of the page reports the result of the save.

Uploaded venue maps use their own upload process and are managed separately from the normal Venue autosave.

Track

Number of oval lanes

Enter the number of lanes available all the way around the oval.

Torunit uses this information when determining how many athletes may compete in a conventional laned race and when constructing later scheduling information.

Available selections currently range from 4 through 12 lanes.

The number entered here should describe the lanes that are physically available for competition.

If a particular lane cannot be used, identify it under Lanes to exclude rather than reducing the total number of oval lanes. You might use this if one lane is damaged. Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

Number of sprint lanes

Enter the number of lanes available on the straightaway used for sprint and hurdle events.

The number of sprint lanes may differ from the number of oval lanes.

For example, a facility might have:

• 8 oval lanes
• 9 sprint lanes

Torunit can therefore use the appropriate capacity for the type of race being scheduled.

Lanes to exclude

Enter any lanes that physically exist but cannot be used for competition.

Separate multiple lane numbers with commas.

Example:

1,8

An excluded lane remains part of the physical facility but should not be treated as available competition capacity.

Possible reasons include:

• Surface damage
• Construction
• Equipment obstruction
• Safety concerns
• A temporary meet-specific restriction

Sometimes, in order to conform with Championship rules, you will use 8 lanes on a 9 lane track. By disabling lane 1 you can force this. Usually it will be better to do this on the event level.

Throwing cages

How many throwing cages will you use?

Enter the number of throwing cages that will be available during the meet.

The current page allows one through three cages.

If you have more than one, it would be best to name them. To Run It will default to Cage 1, Cage 2 etc. but unless you identify them on the map visiting competitors probably won't know what cage is which, at least until they start reading signs. Using geographic identification might help, though not everyone knows north from south at an unfamiliar venue. Perhaps name a landmark like near the baseball field or near the flagpole.

This setting applies to events that require a cage, such as discus, hammer, weight throw, super weight, or ultra weight when those events are offered.

Cage names

When more than one throwing cage is available, give each cage a useful name.

Examples:

• North
• South
• Stadium
• Upper Field

Torunit can then distinguish the facilities during scheduling instead of treating every cage as the same physical location.

The resulting facility names may appear as:

• Cage North
• Cage South

Use names that officials and meet staff will recognize.

How will you divide them?

When multiple cages are available, indicate the general way they will be used.

Current choices are:

• Men/Women
• Hammer/Discus
• Divisions
• Other

This describes the intended operational division of the available cages.

The actual schedule may still assign events according to the needs of the meet.

Field-event competition format

Attempts per event

Select the standard number or progression of attempts used in horizontal jumps and throwing events.

Current choices are:

• 3 attempts
• 4 attempts
• 3+3
• 3+2+1
• 6 attempts

3 attempts

Each competitor receives three attempts. Combined events (Decathlon, Heptathlon, Pentathlon) use 3 attempts. Most preliminary rounds use 3 attempts but make sure your intent is 3 separate attempts as opposed to 3 attempts preceding a 3 attempt final. See 3+3 and 3+2+1 as options for those situations.

4 attempts

Each competitor receives four attempts.

6 attempts

Each competitor receives six attempts. Use this if you have 6 attempts with no elimination or reorganization.

3+3

Competitors initially receive three attempts.

A selected number of competitors then advance and receive three additional attempts.

When this format is selected, Torunit asks:

How many advance to final?

Enter the number of competitors who should receive the additional three attempts.

3+2+1

Competitors advance through successive stages of the competition.

When this format is selected, Torunit asks:

• How many get the last 3 attempts?
• How many advance to the final round?
• What order should be used for the final round?

The final-round order may currently be:

• First place first
• First place last

The exact advancement rules should agree with the meet's rulebook and any meet-specific competition rules.

Use Imperial Measurements (ft/in)

All marks with be converted, this is the measurement system you will use for your meet. Select this when field-event measurements will be recorded using feet and inches.

When this is not selected, Torunit will use metric measurement.

The appropriate measurement system may depend on the meet's governing organization and competition level. While all rulebooks since 1980 call for metric, many American high school meets maintain traditional imperial measurements.

Field-event facilities

To Run It asks how many physical facilities will actually be used for each type of field event offered by the meet. This will become public information. Competitors want to know what they will be using.

Only facilities relevant to the meet's selected events need to be configured.

For example, if a meet that does not offer Pole Vault does not need a Pole Vault facility.

Combined events also require real facilities. If a combined event includes Shot Put, High Jump, Long Jump, or another field discipline, its component event must use an actual ring, pit, runway, or other competition facility.

Horizontal Jumps

Enter the number of horizontal-jump facilities available for Long Jump and/or Triple Jump.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one facility will be used, give the facilities useful names.

Examples:

• North
• South
• Home Straight
• Back Straight

If both Long Jump and Triple Jump use the same physical runway, the facility should describe the actual shared runway rather than inventing separate facilities.

Wind readings

Select Wind readings when wind measurements will be taken for the applicable horizontal-jump events. You can use a separate reporter for the wind readings, or you can do it on one reporter phone.

Wind measurement requirements depend on the competition and governing rules.

High Jump

Enter the number of High Jump facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one High Jump pit is available, name the individual facilities.

Examples:

• HJ North
• HJ South

These become separate physical resources that Torunit can consider during scheduling.

Pole Vault

Enter the number of Pole Vault facilities that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own. Temporary pole vault runways are becoming more common. Some competitors will want to know what they are jumping off of.

If more than one Pole Vault pit is available, name the individual facilities.

Examples:

• North
• South
• Home Straight
• Back Straight

Shot Put

Enter the number of Shot Put rings that will be used.

If more than one ring is available, name the individual facilities.

Examples:

• Shot North
• Shot South
• Upper Ring

Javelin

Enter the number of Javelin facilities or sectors that will be used.

Take note of the surface. The system will default to the same surface as the track but you can change it. To Run It supplies some suggestions but you can write your own.

If more than one is available, name the individual facilities.

Examples:

• North
• South
• Home Straight
• Back Straight

Weight Throw — Shares Hammer cage

When Weight Throw or a related weight event is offered, indicate whether it uses the same physical cage as Hammer Throw.

This is important because two events that share one physical cage cannot be scheduled as though they have independent facilities.

Sometimes the Weight Throws will have their own cages, or share the Shot Put ring. If a Weight Throw is conducted outdoors for an Indoor meet, that might be a good item to note.

Facility conflicts

A facility conflict tells Torunit that two activities cannot freely operate at the same time.

This information is used to prevent the scheduler from treating every competition area as independent merely because it has a different name.

There are two types of conflict:

• Hard conflicts
• Conditional conflicts

Hard conflicts

A hard conflict means that the two selected activities or facilities cannot operate simultaneously.

Select the first facility or event, select the conflicting facility or event, and choose Add.

The conflict appears as a chip below the controls.

Examples might include:

• A javelin sector crossing the track
• A throwing sector overlapping another throwing area
• A runway occupying an area required by another event
• Two events requiring the same physical competition space

Hard conflicts should describe actual operational restrictions at the facility.

Do not create a hard conflict merely because running the two events together would be inconvenient. A hard conflict means the simultaneous use is physically or operationally unacceptable.

Conditional conflicts

A conditional conflict describes two facilities that may be used simultaneously only when sufficient physical separation exists.

This is particularly useful where throwing or jumping areas overlap only under certain circumstances.

Select:

1. The first facility or event
2. The available distance in metres
3. The second facility or event
4. Add

The resulting rule tells Torunit that simultaneous use depends on the available space and the capabilities required by the entered athletes.

For example, two throwing sectors might be usable simultaneously for younger divisions whose expected distances remain well inside the available area, but unsafe for an elite competition throwing at each other.

The current Venue page refers to the map's Measure tool for determining available distances.

See Interactive Map Designer#Measuring distances.

Venue maps

A detailed interactive map is not required to operate a meet.

Many Meet Directors will already have a facility diagram, school map, parking map, or other document that adequately communicates the venue.

Torunit therefore supports uploaded static maps as well as the optional Interactive Map Designer below.

Add a venue map

Venue maps may currently be uploaded as:

• JPG
• JPEG
• PNG
• PDF

Multiple maps may be uploaded for the same meet.

This allows separate documents to be provided for different purposes.

Examples:

• Facility Map
• Parking Map
• Bus Drop-off
• Team Camp Map
• Spectator Entrance Map

Label your upload

Give the map a descriptive name.

The label should tell users what information the map contains rather than merely identifying it as "Map."

Good examples:

• Facility Map
• Team Parking
• Bus Drop-off
• Competition Areas
• Spectator Parking

Show on public ad page

Select this when the uploaded map should be available on the meet's public information page.

A map may therefore be retained by the meet without necessarily being published for public use.

Upload Map

Uploads the selected map file to Torunit.

The uploaded map then appears in the list of maps for the meet.

Uploaded maps for this meet

Previously uploaded maps are listed on the Venue page.

Each map may be managed individually.

Map name

The map's label may be changed after upload.

Show on ad page

Controls whether that individual map is publicly displayed.

View

Opens the uploaded map.

Use this to verify that the correct document was uploaded and is readable.

Save

Saves changes to the map's name or public-display setting.

Delete

Deletes the uploaded map.

Deletion should be treated as permanent. Make sure the correct map is being removed.

Interactive Facility Map — Optional

Torunit includes an interactive facility-map system for Meet Directors who want to create a more detailed operational map.

Most meets do not need to create an interactive map.

An uploaded PDF or image may be entirely sufficient for a local meet.

The interactive map is intended for meets that benefit from more detailed operational planning or public navigation.

Possible uses include identifying:

• Competition facilities
• Entrances
• Parking
• Bus drop-off
• Team camps
• Clerk of Course
• Warm-up areas
• Medical facilities
• Restrooms
• Concessions
• Awards
• Security locations
• Volunteer locations
• VIP areas
• Emergency access
• Other meet-specific locations

The Map Designer may also be used to measure distances when establishing conditional facility conflicts.

For complete instructions, see Interactive Map Designer.

Public facility information

The lower portion of the Venue page records information about use of the facility outside the meet itself.

This information can help athletes, coaches, and other users understand whether the venue is normally available for training or public use.

Is this facility ever available for public use?

Select:

• Yes
• No

Select Yes when members of the public, athletes, clubs, or teams may use the facility under some circumstances.

Public availability does not necessarily mean unrestricted access.

What hours?

Enter the times during which the facility is normally available.

Example:

Weekdays 6–8am, Sat 2–6pm

Hours may be approximate if access varies.

Under what circumstances?

Explain any restrictions or requirements associated with public use.

Examples include:

• Prior approval required
• Fee required
• Coach supervision required
• Team use only
• Seasonal restrictions
• School-hours restrictions
• Permit required

This field is intended to explain circumstances that cannot be represented adequately by a simple Yes/No answer.

Public access contact

Enter the person or organization that should be contacted about use of the facility.

Available fields are:

• Name
• Email
• Phone

This contact concerns access to the facility rather than general questions about the current meet.

Last updated

The page displays the month and year associated with the current public-access information.

Public-access information should be reviewed periodically because facility policies can change.

Practice facilities available

Identify specialized facilities that may be available for practice.

Current selections are:

• Pole Vault
• High Jump
• Throwing Cage
• Javelin

Availability should not be interpreted as permission to use the facility without approval.

The public-access conditions and contact information should explain any restrictions.

Multiple competition locations

Some meets use facilities at more than one physical location.

Examples include:

• Track and field at a stadium with Race Walk on a separate course
• A road race beginning away from the stadium
• Cross Country at a separate course
• Throws conducted at a secondary field
• Competition spread across multiple nearby facilities

Torunit is intended to allow each physical location to be identified and then used by the scheduling and operational systems.

Current status: Multiple-location configuration is not yet complete.

When completed, each location should be treated as a real operational resource rather than merely as descriptive text.

This section should be expanded when the multiple-location system is completed.

How Venue information affects scheduling

Venue configuration supplies physical constraints to the scheduling system.

Examples include:

• Available track lanes affect heat capacity.
• Separate sprint and oval lane counts may produce different capacities.
• Excluded lanes reduce usable capacity.
• Multiple pits, rings, runways, or cages may allow simultaneous field events.
• A single shared facility prevents incompatible simultaneous use.
• Hard conflicts prohibit combinations that cannot safely operate together.
• Conditional conflicts describe combinations whose simultaneous use depends on available space.
• Combined-event components use the same real facilities as standalone events.

The Venue page therefore describes what the facility can physically support.

The scheduler determines when those resources will actually be used.

Current implementation notes

The following items should be reviewed as Torunit development continues:

• Multiple competition locations are not yet fully implemented.
• The existing interactive mapping system is scheduled for substantial redevelopment and should not drive the architecture of the Venue page.
• The current embedded map and its persistence/publishing behavior should be reviewed as part of that map redevelopment rather than repaired piecemeal here.
• The existing lane-change JavaScript contains a placeholder hook for future validation or UI behavior.
• Static venue-map upload, rename, public/private status, viewing, and deletion should continue to remain independent of the interactive Map Designer.
• Venue should remain usable without requiring the Interactive Map Designer.

See also

• Create-Meet
• Interactive Map Designer
• Schedule
• Macro Scheduler
• Micro/Daily Scheduler
• Combined Events
• Registration
• Live Meet