2Timer
← Back to 2Timer

2Timer Help

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

Purging Results and Resetting State

Purpose

Explain how to clear result-related state safely when you want to re-import timing data, re-score a meet, or remove bad result data without rebuilding the meet from scratch.

When to Use This Page

Use the result reset tools when:

  • you imported bad reads or bad results
  • you want to re-import timing files
  • you want to keep entries, heats, lanes, and seeding but clear the scoring/output state
  • you need a broader meet purge for selected categories such as athletes, events, connectors, or reads

The Two Purge Levels

2Timer has two different purge surfaces inside a meet.

Purge results

The Purge results page is the narrower and safer option when the meet structure should stay in place.

Its goal is:

  • clear results-related state
  • keep entries
  • keep heat/lane assignments
  • keep seeding and general meet structure

This is the best option when the meet setup is still good and only the result layer needs to be reset.

Purge database

The broader Purge database page removes selected meet data categories more aggressively.

This can affect:

  • athletes
  • teams
  • entries
  • reads
  • events
  • groups
  • leagues
  • waves
  • divisions
  • connectors
  • markers
  • chips

Use this only when you intentionally want to remove those categories from the meet.

Where to Find It

From an open meet, use:

  • Reset Results… for result-focused cleanup
  • Purge Database… for broader category deletion

Purge Results

What it is for

Use Purge results when you want to preserve setup and seeding while clearing the result layer.

What it can clear

The page includes result-focused categories such as:

  • Entry results This includes times, places, result status, splits, notes, flags, and field-series marks.
  • Timing reads Saved Lynx, chip timing, and other inbound raw read records.
  • Heat metadata Per-heat result metadata such as wind readings.
  • Tie-break results Round-level adjudication metadata such as tie resolutions.
  • Connector activity counters Imported-read counts, last-read timestamps, publish totals, and related activity summaries.
  • Field-event setup helpers Optional setup helpers such as vertical-jump bar progressions.

Important dependencies

Some result-reset choices automatically require others.

Examples:

  • clearing Entry results also forces the related result metadata and connector activity cleanup
  • clearing Timing reads also forces connector activity cleanup

This prevents partial cleanup that leaves stale summaries behind.

Confirmation

You must type RESET RESULTS to confirm.

Purge Database

What it is for

Use Purge database when you need to remove selected categories from the meet itself, not just the results layer.

Category examples

  • Athletes removes athlete records for the meet
  • Teams removes teams and clears related assignments
  • Entries, results, and relay legs removes all entry rows and their result state
  • Reads removes saved raw timing reads
  • Events removes events and also requires dependent cleanup for entries and markers
  • Connectors removes meet-level connector configurations
  • Chips removes chip definitions
  • Waves, Groups, Divisions, and Leagues remove those configuration layers

Important dependencies

Some categories automatically require related cleanup.

Example:

  • deleting Events also requires Entries and Markers

The UI handles these dependencies automatically so you do not leave orphaned references behind.

Confirmation

You must type PURGE to confirm.

How to Choose the Right Reset

Choose Purge results when:

  • the event structure is still correct
  • athlete and entry setup should stay
  • seeded heats and lanes should stay
  • you mainly need to remove bad results or reads

Choose Purge database when:

  • the meet setup itself needs selected categories removed
  • you want to clear structural data such as events, athletes, connectors, or teams
  • a narrower results reset is not enough

Recommended Workflow Before Purging

  1. Export a .2t backup if the meet is still usable.
  2. Decide whether the problem is results-only or structure-level.
  3. Choose the narrowest purge that solves the problem.
  4. Read the dependency badges before confirming.
  5. Purge.
  6. Re-import or rebuild only the pieces you intended to replace.

Common Scenarios

Bad chip timing import, but entries and seeding are correct

Use Purge results and clear:

  • timing reads
  • entry results
  • related metadata as required

Then re-import timing data.

Wind, tie-resolution, or field-result layer is wrong

Use Purge results so you can keep the meet structure while removing the result layer.

Event definitions were created incorrectly

Use Purge database if the event structure itself needs to be removed.

Connector setup was wrong and you want to start over

Use Purge database and clear connectors, then recreate them cleanly.

Common Mistakes

  • using full meet purge when a results-only reset would have been enough
  • forgetting that deleting events also removes dependent event-linked data
  • purging reads without understanding that connector activity summaries will also reset
  • skipping backup export before destructive cleanup

Verification Checklist

  • You picked the correct purge level: results-only or broader meet purge.
  • You understand the auto-selected dependency categories.
  • You confirmed with the typed phrase intentionally.
  • After purge, the meet now contains only the data you expected to keep.
  • Re-import or rebuild starts from the cleaner state you intended.

Related Pages

Metadata

  • Last Updated: 2026-04-18
  • Version: 0.1
  • Status: Active