2Timer
← Back to 2Timer

2Timer Help

Practical guides for humans, with structure that is easy for AI systems to parse.

Field Events

Purpose

Explain how field events work in 2Timer, including the dedicated field-input workflow, attempt series, marks, outcomes, and wind handling.

Prerequisites

  • Meet created as indoor or outdoor T&F.
  • Event discipline set correctly for throws, horizontal jumps, or vertical jumps.
  • Entries already created for the event.

Attempt Series

Field events in 2Timer use attempt series or height progression as the primary result-entry model.

Each attempt or height row can store:

  • a mark
  • an outcome such as valid, foul, pass, no height, or no mark
  • a wind reading when applicable

The best valid mark or cleared height becomes the athlete’s scoring result, while the full series stays available for review, tie-break support, and reporting.

Vertical Tie-Breaks And Jump-Offs

For high jump and pole vault style workflows, 2Timer now applies ordinary automatic tie-break logic from the saved height series:

  • best cleared height decides first
  • if that is tied, fewer attempts at the best cleared height wins
  • if that is still tied, fewer misses through the best cleared height wins
  • if athletes are still tied after that, the tie stands unless officials resolve it externally

When officials run a jump-off for first place, you can record the outcome from the vertical field-input workflow instead of faking extra series rows.

2Timer stores that as an official tie resolution for the tied athletes and uses it when assigning places. The affected entries can also show short official notes such as JO or JO 2nd in results and reports.

If you later make a meaningful edit to one of the tied athletes’ vertical series or final mark, 2Timer clears the old jump-off resolution so the event can be reviewed again against the new underlying data.

Field Input Workflow

For race-day entry, use the Field Input action from the event’s Entries page.

2Timer opens a flight-level input surface instead of making you edit one athlete at a time:

  • horizontal jumps and throws use an attempt grid with one row per athlete
  • vertical jumps use a height grid with one column per height
  • flights can be switched from the same input surface
  • keyboard-first movement is supported with Tab, Shift+Tab, Enter, Shift+Enter, and arrow keys
  • Escape restores the current cell to its last committed value, and Ctrl+Z / Cmd+Z undoes the last committed change
  • the best mark updates from the series as you save entries
  • tied vertical results can be resolved from the same workflow when officials complete a jump-off

The single-athlete edit page still exists for cleanup and exception handling, but the main intended workflow is now event-level field input.

Outcome Types

Depending on the event, operators may record:

  • valid mark
  • foul
  • pass
  • no height
  • no mark

These outcomes let the results page reflect what actually happened without forcing every attempt into a numeric distance or height.

Wind Readings

Outdoor horizontal jumps and certain sprint/hurdle races support wind readings in meters per second.

Use wind when:

  • the event is an outdoor wind-eligible discipline
  • your officiating workflow requires wind to appear in reports

For field events, wind belongs to the attempt series when the discipline supports it. If results came in through FinishLynx LFF, 2Timer keeps that per-attempt context on the entry.

2Timer treats blank wind as NWI (“No Wind Instrument”), not as zero. 0 is a real measured reading and stays distinct from a missing reading.

For track events that support heat-level wind, use the wind field on the Entries page once you are filtered to a single heat. For horizontal jumps, wind stays attached to the attempt series.

The wind field accepts quick operator shorthand:

  • leave it blank for NWI
  • type digits without punctuation, such as 12 for +1.20 m/s or -34 for -3.40 m/s
  • type a normal decimal such as +1.8 or -0.4 if you prefer

After save, 2Timer displays wind in signed +/- m/s form. It can flag wind-aided performances for awareness, but it does not prevent result entry.

Entering Marks

Marks can be entered from the event-level field input or from the single-entry editor.

Typical operator flow:

  1. Open the field event on the Entries page.
  2. Click Field Input.
  3. Pick the flight if the event has more than one.
  4. Enter attempts or height tokens across the grid.
  5. Record fouls, passes, no-heights, and no-marks explicitly instead of leaving cells ambiguous.
  6. Review the derived best mark or best height before closing.

For English-measured horizontal jumps, compact shorthand such as 18625 can be entered and will normalize to 18-6.25.

Horizontal vs Vertical Entry

Horizontal jumps and throws are optimized around attempts across each athlete row. Use this for long jump, triple jump, shot put, discus, javelin, and similar events.

Vertical jumps are optimized around bar heights. Add or edit the active heights at the top of the grid, then enter the athlete’s result token at each height.

Common Pitfalls

  • Wrong discipline: wind, field-input layout, and series formatting depend on the event type being correct.
  • Opening the single-entry editor for bulk race-day entry: use Field Input from the event’s Entries page for the faster flight workflow.
  • Missing unit expectation: indoor and outdoor meets should agree on metric vs English display.
  • Partial attempt entry: if only some attempts are entered, the displayed best mark may be incomplete.
  • Treating blank wind as zero: blank means NWI, while 0 means the gauge read zero.

Related Pages