BotScan v0.15.11 — Contest Log Analysis

1. Input and eligibility

BotScan reads selected Cabrillo logs in the protected interface and processes them through the controlled review workflow. The core parses Cabrillo headers and QSO lines, removes exact repeated QSO-line artifacts from behavioral metrics, separates non-scored records, rejects Multi-Op categories for Single-Op review, and analyzes only logs with enough cleanly parsed QSOs.

2. Metrics

The analysis combines file integrity, rest breaks, continuous operating blocks, frequency-change rate, run/S&P texture, minute-level frequency spread, band movement, rate context, duplicate/reworked-station context and frequency-detail quality. Each metric is interpreted by mode and contest profile, not as a single global rule.

3. Peer comparison

Each contest and category has its own historical peer profile. BotScan compares the uploaded log against matching Single-Op groups by contest, year, mode, power, band and assistance where available, so EA-RTTY, CQ-160-CW, CQ-WW, WPX, WAE, ARRL and IARU are not judged with one generic threshold set.

4. Evidence logic

BotScan avoids relying on one weak signal. RED-level review requires hard timing, scanner/no-run structure, hard minute-level spread, or multiple independent evidence families. In RTTY Single-Op review, 5+ distinct logged frequencies in one minute remains a high-priority hard spread signal. Frequency-spread display now starts at 4+ and dynamically reveals higher 7+/8+ levels only when they are present. Three-frequency minutes are retained only as internal/informational context. In CW, isolated single-band 5-frequency minutes are treated as aggressive S&P context; repeated 5+ or any 6+ minute remains high-priority review. In SSB, stable dual-run/2BSIQ and aggressive S&P are handled separately, and SSB scatter is compared against the matching historical peer-group peer reference/max before it affects review level. Fast duplicates and same-band reworked stations remain context only and do not create RED by themselves.

5. Batch ranking context

In batch mode, claimed score is used only to show pre-adjudication rank inside the loaded category group. Automation Evidence is calculated separately from claimed rank.

6. Limitations

Cabrillo timestamps are usually minute-level, so the tool is a screening layer. Strong flags should be followed with higher-resolution evidence when available: ADIF seconds, raw RBN timing, audio, station layout, operator declarations and written explanation.