Local contest-log screening for automation-like operating patterns.
Rows are review signals, not final adjudication. Methodology is available below.
Calibration reference corpus
Historical log/QSO footprint behind BotScan
CW · RTTY · SSB
LOGS
—
reference logs analyzed
QSOs
—
reference QSOs processed
DATASETS
—
contest/year datasets
PROFILES
—
contest/mode profiles
BotScan was built and calibrated against a large Single-Op reference corpus across CW, RTTY and SSB. The cards show the log/QSO footprint used to validate the detection model and the published review library. Local file and folder scans are analyzed in the browser and are not transmitted.
Peer comparison is category-aware: contest, year, mode, power, band and assistance are used where available. Automation Evidence is independent from claimed rank. Logger/CREATED-BY clustering is context only and never adds score by itself.
1Drop a Cabrillo log to analyze
📄
Drop a Cabrillo log here, or click to select
Accepts .log, .cbr, .txt — single-op logs only
Your browser may describe folder selection as an upload. Local files are analyzed in this browser session and are not transmitted.
Public Results Library
Detailed public results are available for selected major contest/year datasets from 2020 onward. Older historical scans may be shown as summary-only context. Local file and folder scans are analyzed in the browser and are not transmitted.
Waiting for public library…
1. Choose contest
Choose a contest family to select mode and year.
Waiting for public library…
Batch scan results
Contest / year / category
Waiting for logs…
Waiting for logs…
Sorted by Automation Evidence first, then Review Priority, claimed rank and score.
Click a row to open the full review. Default view shows review-relevant cases. Rank is claimed/pre-adjudication and is computed from CLAIMED-SCORE inside each loaded category group. JSON is kept as the technical/dev evidence export; CSV/PDF are for easier human review.
2File integrity
3Automation-like pattern markers
4Full peer-group comparison
5Detailed operating statistics
Methodology
Cabrillo contest-log review methodology.
BotScan is a first-stage analytical detector. It highlights logs that deserve deeper review; it does not replace committee judgment.
1. Input and eligibility
BotScan reads selected Cabrillo logs locally in the browser. 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 loaded 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.